I would like deliver not to automatically create subfolders for mails
addressed to user+some_strange_name at domain.com, but nevertheless
automatically create INBOX for new users. I'm not sure whether a new
option like -M or -m -m would be appropriate, i.e., whether anyone
needs the current -m behaviour.
It looks to me like one would need to change
mailbox_open_or_create_synced()
if (box != NULL || no_mailbox_autocreate)
return box;
to something like (assuming an enum mailbox_autocreate
{_never,_inbox,_always}
if (box != NULL)
return box;
if (mailbox_autocreate == mailbox_autocreate_never || strcasecmp
(mailbox, "INBOX") != 0)
return NULL;
On Mon, 2008-09-01 at 15:19 +0200, Edgar Fu? wrote:> I would like deliver not to automatically create subfolders for mails > addressed to user+some_strange_name at domain.com, but nevertheless > automatically create INBOX for new users. I'm not sure whether a new > option like -M or -m -m would be appropriate, i.e., whether anyone > needs the current -m behaviour.If a namespace has inbox=yes, Dovecot always makes sure the INBOX exists so it's autocreated if necessary. Is this not working with you? -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part URL: <http://dovecot.org/pipermail/dovecot/attachments/20080901/e4d63da6/attachment-0002.bin>
> Is this not working with you?Ouch. I should have read the log more carefully. The problem was that for this particular test user, the mail directory didn't exist and of course deliver was unable to create cur in that non-existing directory. Sorry for the noise.