Deuxfleurs/aerogramme
15
0
Fork 1
Code Issues 33 Pull requests 1 Projects 11 Releases 5 Wiki Activity

RFC6154 SPECIAL-USE (IMAP4REV2 subset) #49

New issue
Open
opened 2023-12-29 18:28:52 +00:00 by quentin · 1 comment
quentin commented 2023-12-29 18:28:52 +00:00
Owner
Copy link

Some IMAP message stores include special-use mailboxes, such as those
used to hold draft messages or sent messages. Many mail clients
allow users to specify where draft or sent messages should be put,
but configuring them requires that the user know which mailboxes the
server has set aside for these purposes. This extension adds new
optional mailbox attributes that a server may include in IMAP LIST
command responses to identify special-use mailboxes to the client,
easing configuration.

Related to #38 and RFC5464 METADATA.

imap_codec support:

  • minimal form: NOT REQUIRED (YES)
  • full form: NO (no support for LIST-EXTENDED or METADATA)

relevant part in imap4rev2: https://www.rfc-editor.org/rfc/rfc9051.html#section-7.3.1
see also: https://www.iana.org/assignments/imap-mailbox-name-attributes/imap-mailbox-name-attributes.xhtml

> Some IMAP message stores include special-use mailboxes, such as those used to hold draft messages or sent messages. Many mail clients allow users to specify where draft or sent messages should be put, but configuring them requires that the user know which mailboxes the server has set aside for these purposes. This extension adds new optional mailbox attributes that a server may include in IMAP LIST command responses to identify special-use mailboxes to the client, easing configuration. Related to #38 and RFC5464 METADATA. imap_codec support: - minimal form: NOT REQUIRED (YES) - full form: NO (no support for LIST-EXTENDED or METADATA) relevant part in imap4rev2: https://www.rfc-editor.org/rfc/rfc9051.html#section-7.3.1 see also: https://www.iana.org/assignments/imap-mailbox-name-attributes/imap-mailbox-name-attributes.xhtml
quentin added the
cat
feature
 label 2023-12-29 18:29:04 +00:00
quentin added this to the IMAP4REV2 project 2023-12-29 18:29:06 +00:00
quentin changed title from RFC6154 SPECIAL-USE to RFC6154 SPECIAL-USE (minimal form) 2023-12-29 18:29:33 +00:00
quentin added this to the 0.2.0 milestone 2023-12-29 18:29:38 +00:00
quentin changed title from RFC6154 SPECIAL-USE (minimal form) to RFC6154 SPECIAL-USE (IMAP4REV2 subset) 2023-12-29 18:45:07 +00:00
quentin added the
blocked
vendor
 label 2024-01-03 20:16:49 +00:00
quentin commented 2024-01-20 10:56:32 +00:00
Author
Owner
Copy link

A very minimal implementation has been done but it must be improved

A very minimal implementation has been done but it must be improved
quentin removed this from the 0.2.0 milestone 2024-01-20 10:56:43 +00:00
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
caldav
bug/thunderbird
feat/condstore
autorelease
albatros
quentin
0.3.0
0.2.2
0.2.1
0.2.0
0.1.0
0.0.1-ci.1
Labels
Clear labels   
blocked
another_issue
Blocked by another issue

  
blocked
design
Blocked due to Aerogramme's design

  
blocked
vendor
Blocked due to missing 3rd party lib support

  
cat
bug
It's a bug!

  
cat
correctness
Correctness issue

  
cat
feature
New things

  
cat
maintainance
The ecosystem is evolving, we want to follow it

  
cat
performance
Performance testing/validation/optimisation

  
cat
testing
Testing is great to ensure that your software is not buggy

  
cat
thinking
Some idea

  
cat
ux
User/operator experience issue

  
mua
mutt
Mutt related issues

  
mua
thunderbird
Thunderbird Desktop related issues

  
prio
high

  
prio
low
low priority

  
prio
mid

No labels
blocked
another_issue
blocked
design
blocked
vendor
cat
bug
cat
correctness
cat
feature
cat
maintainance
cat
performance
cat
testing
cat
thinking
cat
ux
mua
mutt
mua
thunderbird
prio
high
prio
low
prio
mid
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
IMAP4REV2
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: Deuxfleurs/aerogramme#49
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?