'Mailbox unknown' unpon LMTP delivery
mark at air.co.jp
Tue Jul 1 22:41:50 EDT 2003
It seems odd that lmtpd would be looking for user^username...
What is the unixhierarchysep setting in your imapd.conf file?
A setting of "yes" means '/' is the hierarchy separator rather than '.'.
When the separator has been set to '/', dot '.' characters in mailbox
names are mapped to caret '^' and user mailbox must be created as
On Tue, 01 Jul 2003 21:39:55 +0200, Henning Holtschneider <hh at loca.net> wrote...
> --On Montag, 23. Juni 2003 14:40 +0200 Henning Holtschneider <hh at loca.net>
> > I'm running Cyrus IMAP 2.1.13 on top of Postfix. Mail is being delivered
> > from Postfix into Cyrus using an LMTP unix socket. My users have email
> > addresses like firstname.lastname at domain.tld. The login names/mailbox
> > names are unique user ids like "jdoe123". I created a virtual transport
> > map in Postfix to map "firstname.lastname at domain.tld" to
> > "username at domain.tld". Howerver, incoming messages can't be delivered to
> > the mailboxes. Cyrus complains:
> I've finally been able to track down the problem to this: the mailboxes are
> being created as user.username which results in a directory user.username
> being created and the mailbox being added to a DB file (as far as I can see
> from the source code). However, lmtpd is looking for user^username (^
> instead of . as the seperator). Why is Cyrus trying to use another
> seperator when delivering incoming messages?
> __ _ __ __ Henning Holtschneider
> / / ___ _______ _/ |/ /__ / /_ <henning at loca.net>
> / /__/ _ \/ __/ _ `/ / -_) __/
> /____/\___/\__/\_,_/_/|_/\__/\__/ ...net happens!
Mark Keasling <mark at air.co.jp>
More information about the Info-cyrus