[EMAIL PROTECTED] wrote:
>
> Kenneth Murchison writes:
> >
> >OK, let's try this and see what happens (grasping at straws):
>
> >$ su cyrus
> >$ /usr/cyrus/bin/deliver -l
>
> Thanks. I believe we've got it. It said:
>
> connect failed: No such file or directory
> 421 4.3.0 deliver: connect failed
>
> I found a typo in /etc/imapd.conf:
>
> < lmtpsocket: /var/run/imap/ltmp
> ---
> > lmtpsocket: /var/run/imap/lmtp
>
> I also got an empty mail message. I didn't realize that deliver was
> used, since my sendmail local mailer is writing to the LMTP socket
> directly.
It doesn't. Because lmtpd is listening on a named pipe, the easiest way
to connect to it directly is via deliver. If you're using the
cyrusv2.mc file as an example, then you are probably setup correctly
(provided you have the pipe name correct).
> I also notice a new message in imap.log, which I've never
> seen before, but I've seen on the mailing list:
>
> Nov 14 14:33:46 setup16 master[9266]: [ID 970914 local6.debug] process
> 9900 exited, signaled to death by 11
Hmmm. This *might* be caused by cyrus and sasl being linked against two
different versions of Berkeley DB. Or it could be caused by incorrect
permissions on the /var/imap/deliverdb tree.
You didn't see these errors before, with sendmail talking LMTP directly?
> So, this is progress. Thanks very much. This one was hard to find.
No problem. I hate seeing people unable to use code that I've worked
on.
Ken
--
Kenneth Murchison Oceana Matrix Ltd.
Software Engineer 21 Princeton Place
716-662-8973 x26 Orchard Park, NY 14127
--PGP Public Key-- http://www.oceana.com/~ken/ksm.pgp
