Bug#494746: cyrus-imapd-2.2: connect(/var/run/cyrus/socket/lmtp) failed: Permission, denied

[Magnus Danielson]

Henrique de Moraes Holschuh wrote:
> On Sun, 20 Dec 2009, Magnus Danielson wrote:
>> Regardless which is safest, the cyrus-imapd package needs to set it
>> up correctly in order for cyrus and postfix to interoperate.
> 
> [...]
> 
>> That would work, but then the cyrus-imapd (or other suitable cyrus
>> package) should do this, not me and all other users that want to use
>> postfix and cyrus imap together.
> 
> Please understand that Cyrus IMAP is not a simple, plug-and-play system.
> And it is not geared towards a single-user single-box install, either.

Please understand that it is not a single-user system.

> The local admin (i.e. you) is supposed to configure it correctly for his
> needs.

Fully aware of this, but fusing together correct and up-to-date 
information about how current cyrus should fit into current postfix as 
they are packaged, isn't crystal clear.

> If you'd like us to improve the documentation shipped with the package,
> please give us suggestions.

I will look over the documentation again.

> As for taking steps to automatically let Exim and Postfix talk to the
> LMTP socket, I am not sure if it is a good idea.  Not only that is
> utterly pointless as far as auto-setup goes, as you still need to do a
> lot of stuff to get Cyrus to accept mail from postfix/Exim, it is also
> something that wouldn't be useful in the more typical Cyrus setup, where
> clustering is involved (and the MTA is not in the same box).
> 
> And adding a new system group on package install, adding exim and
> postfix users to it, requesting that the same be done on the postfix and
> exim packages... it is not something we will do unless there is a clear
> and strong advantage to the package usability.  I am not convinced of
> that.

Keeping the link between say postfix and cyrus working over time and 
upgrades is one of a myrriad details that a local admin has to attend 
to. The best way to handle that would be separate packages. I can accept 
that cyrus-imap is not the best package for a solution, but not 
addressing a way to ease the integration is not a good solution either.

> Let's see what the other Cyrus maintainers think of this issue.
> 

Regardless, the proposed solution at least survives upgrade, where as 
the comment on chmod to 755 for the socket directory will break on upgrade.

Cheers,
Magnus