Should I expect any problems with multiple unix LMTP sockets?
On my system packages cyrus-imap makes LMTP socket available to mail
group. I created second unix LMTP socket available to lmtp group to
allow *SOME* users submit directly via LMTP.
I use "hackish" perl script to make Net::SMTP wor
Okay, we were originally having problems with the deliver program connecting
to LMTP via UNIX file sockets. We thought about going to TCP sockets and
use deliver, but from what I saw in the source code, it may be that deliver
only support UNIX file sockets.
This meant that we needed to dump deli
--On Sunday, August 26, 2001 3:55 PM -0400 Lawrence Greenfield
<[EMAIL PROTECTED]> wrote:
> Does this correspond to /usr/sbin/sendmail being invoked by a user
> process (not from a network I/O message)?
Sendmail is still invoked as root and runs that way. However, deliver
runs as user cyrus an
Does this correspond to /usr/sbin/sendmail being invoked by a user
process (not from a network I/O message)?
This is a pretty weird thing to be happening, and I don't think that
this message can be caused by a listen queue overflow.
I'd guess some process is invoking /usr/sbin/sendmail not as ro
We are seeing a lot of messages getting deferred in our sendmail logs
when deliver is executed. Basically, deliver is exitting with EX_TEMPFAIL.
Looking at the cyrus logs, I can correlate most of those failures to the
following message:
deliver: connect(/var/imap/socket/lmtp) failed: Permission
