On Tue, 2008-06-24 at 13:19 -0700, Andrew Roberts wrote:
On Mon, 23 Jun 2008, Timo Sirainen wrote:
The difference is that nowadays deliver supports namespaces. How have you configured them? For example if you have INBOX/ prefix for all your private mailboxes, you'd have to save the mail to INBOX/spam, not spam.
That's funny. I had figured that deliver 1.1 didn't fully support namespaces since I couldn't get it to work. Silly me.
On our setup, postfix pipes to "deliver -d ${user}@${nexthop} -n -m ${extension}" and this works as expected so long as the mailbox is in the private namespace. If we try user+shared.test@domain, deliver logs "save failed to shared.test: Mailbox doesn't exist: test" and "saved mail to INBOX". Is there something that should be changed with the config below to get deliver to deliver to other namespaces?
Set mail_debug=yes and see what it logs. Does it show that deliver reads all the namespaces correctly?
Now, how to do this automatically?
As for the original question about 1.0 > 1.1 transition for configs with non-empty prefixes for their inbox namespaces: Why not have deliver prepend the prefix of the inbox namespace to the extension when the extension does not contain any separator characters?
This would preserve the old 1.0 behavior without changing anything when the namespace is specified as part of the extension.
That's kind of a partial solution since it doesn't fix if there are subfolders. Also this kind of a behavior change feels like it could break things and cause all kinds of unwanted behavior..