Tickets :: [#12565] Handling of shared sent and drafts folders

6.0.0-alpha14

7/2/25

Summary	Handling of shared sent and drafts folders
Queue	IMP
Queue Version	Git master
Type	Bug
State	Resolved
Priority	1. Low
Owners	slusarz (at) horde (dot) org
Requester	thomas.jarosch (at) intra2net (dot) com
Created	08/13/2013 (4341 days ago)
Due
Updated	04/02/2014 (4109 days ago)
Assigned
Resolved	04/02/2014 (4109 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch	No

04/02/2014 07:14:06 AM	Thomas Jarosch	Comment #5	Reply to this comment
This restriction has been removed due to the new Tree code in IMP 6.2. cool!

04/02/2014 03:19:53 AM	Michael Slusarz	Comment #4 Assigned to Michael Slusarz State ⇒ Resolved	Reply to this comment
This restriction has been removed due to the new Tree code in IMP 6.2.

08/14/2013 08:59:01 AM	Thomas Jarosch	Comment #3	Reply to this comment
[Show Quoted Text - 12 lines][Hide Quoted Text] The namespace RFC (RFC 2342) explicitly states that these kind of personal mailboxes (e.g. Sent, Trash) must appear within a personal namespace: Clients often attempt to create mailboxes for such purposes as maintaining a record of sent messages (e.g. "Sent Mail") or temporarily saving messages being composed (e.g. "Drafts"). For these clients to inter-operate correctly with the variety of IMAP4 servers available, the user must enter the prefix of the Personal Namespace used by the server. Using the NAMESPACE command, a client is able to automatically discover this prefix without manual user configuration. I think the intention of the above RFC paragraph is to mention that the folders _normally_ reside in the personal namespace. Also it points out that a client should not try to use a "Drafts" folder without any prefix and should always use something like "INBOX/Drafts". Though it does not pose any restriction on where these folder actually are. Why should it? I've checked Thunderbird, Outlook 2010 and kmail. All of them allow me to select any folder I wish. The NAMESPACE RFC 2342 was co-written by a Microsoft guy in 1998. Googling around shows that Outlook 2013 / Office 365 still supports having a shared sent folder. So I guess we are too strict on this one. Would it cause any harm to enable shared folders for this?

08/13/2013 05:57:47 PM	Michael Slusarz	Comment #2	Reply to this comment
We don't support special mailboxes outside of the personal namespace. This is intentional. The namespace RFC (RFC 2342) explicitly states that these kind of personal mailboxes (e.g. Sent, Trash) must appear within a personal namespace: Clients often attempt to create mailboxes for such purposes as maintaining a record of sent messages (e.g. "Sent Mail") or temporarily saving messages being composed (e.g. "Drafts"). For these clients to inter-operate correctly with the variety of IMAP4 servers available, the user must enter the prefix of the Personal Namespace used by the server. Using the NAMESPACE command, a client is able to automatically discover this prefix without manual user configuration.

08/13/2013 09:03:10 AM	Thomas Jarosch	Comment #1 Priority ⇒ 1. Low Type ⇒ Bug Summary ⇒ Handling of shared sent and drafts folders Queue ⇒ IMP Milestone ⇒ Patch ⇒ No State ⇒ Unconfirmed	Reply to this comment
Hi, I'm using a prefs hook to set the drafts and sent folder. In a shared working environment, some users want to have one shared folder for their sent items. So the sent items folder points to "user/common_user/Outbox". Sent messages are successfully stored in that folder. When you click on the folder in the UI, it does not show the contents of the folder. Instead an empty folder is shown. Also imp does not allow you to select a shared folder for drafts and sent items in the folder dropdown. Any reason for this limitation? Cheers, Thomas