Hello,
I just upgraded to Dovecot 2.2.13 from the 2.0 version branch- so far everything is working great.
I wanted to take advantage of the mailbox option to auto create and auto subscribe users to a Sent and Trash folder (using the support for the special use flags), but ideally, I only want to do this for new mailboxes, and not for all the mailboxes that already exist on the system.
The reason for this is because all the existing users likely already have a sent-mail folder configured, and I don't want to implement this, and have their sent-mail folder switched to this new one.
When I set this up on my test system, I noticed that the new sent and trash folders appeared in my existing mailbox, and when I checked the account on my iPhone, it switched my sent-mail folder away from my "normal" sent-mail folder, and I couldn't change it back.
Is there a way to do this ONLY when dovecot creates a new mailbox?
Thanks,
Mike
On 08/01/2014 04:54 PM, Mike Pultz wrote:
I wanted to take advantage of the mailbox option to auto create and auto subscribe users to a Sent and Trash folder (using the support for the special use flags), but ideally, I only want to do this for new mailboxes, and not for all the mailboxes that already exist on the system.
I guess this could be done with extra fields: http://wiki2.dovecot.org/UserDatabase/ExtraFields
The syntax being something like namespace/inbox/mailbox/Sent/special_use=\Sent ..? Or something like that. Note the userdb_import facility for passing multiple options.
**I wonder if it wouldn't be useful to be able to create configuration sections and activate them with a single, simple extra field rather than pass the entire section itself? In a similar manner to protocol imap { }, maybe we can have $extra_options1 == "yes" { } and pass extra_options1 = yes as an extra field?
On 02 Aug 2014, at 00:26, Gedalya gedalya@gedalya.net wrote:
On 08/01/2014 04:54 PM, Mike Pultz wrote:
I wanted to take advantage of the mailbox option to auto create and auto subscribe users to a Sent and Trash folder (using the support for the special use flags), but ideally, I only want to do this for new mailboxes, and not for all the mailboxes that already exist on the system.
I guess this could be done with extra fields: http://wiki2.dovecot.org/UserDatabase/ExtraFields
The syntax being something like namespace/inbox/mailbox/Sent/special_use=\Sent ..? Or something like that. Note the userdb_import facility for passing multiple options.
**I wonder if it wouldn't be useful to be able to create configuration sections and activate them with a single, simple extra field rather than pass the entire section itself? In a similar manner to protocol imap { }, maybe we can have $extra_options1 == "yes" { } and pass extra_options1 = yes as an extra field?
Maybe, but could be a lot of work. For this case however it's easy. Create two namespaces:
namespace inbox { prefix = inbox = yes mailbox Sent { auto = create } # ..etc.. } namespace old { prefix = inbox = yes disabled = yes }
Then in the extra field you can just set namespace/inbox/disabled=yes and namespace/old/disabled=no
participants (3)
-
Gedalya
-
Mike Pultz
-
Timo Sirainen