Cyrus IMAP Presentation

[Michael Fair]

> Having Cyrus setup it's lmtp socket under /var/spool/postfix (but not
> /public or /private) is the right thing to do. I say this because
> often postfix runs in a chroot env and won't access the lmtp socket if
> it's outside of /var/spool/postfix

This isn't true in the slightest and making it look
like a gateway into the Cyrus software is actually 
inside postfix (by way of putting it in the chroot 
jail) is more confusing than "right".  If this was
the only thing Postfix could do, then yes I'd agree.
But even then I would encourage making it a hard link
to wherever Cyrus' socket was.

However Postfix is not that limited, in master.cf 
the lmtp line has an option as to whether the lmtp 
transport is chrooted or not.  Make sure that option
is set to 'n' and the Cyrus lmtp delivery socket can 
be anywhere you want.  Since the outside world isn't
contacting the LMTP transport directly (like it does
with the smtp/smtpd transports) it's not as important
to trap this one in a chroot jail.

I've always left Cyrus' socket on my Debian system at:
/var/run/cyrus/socket/lmtp
and then used: lmtp:unix:/var/run/cyrus/socket/lmtp
as my mailbox_transport in Postfix.

But I would be just as happy using any other 
appropriate Cyrus owned directory.

This particular socket is a gateway into the Cyrus
system and as such its location should reflect that.

In the end it becomes administrator's preference,
but in terms of accurately trying to model what's
happening, the MTA is theoretically only one agent
that might want to use that socket.  There could
be several agents that want to deliver mail into
the Cyrus mail store and as such they should each
contact a socket that is part of the Cyrus system.

My 2 bits.
-- Michael --