Samuel Penn writes:
Given that the above was a red herring, is there anything else I can do
to find out why esmtpd is giving:
courieresmtpd: CRIT: authdaemon: s_connect() failed: No such file or directory
courieresmtpd: error,relay=127.0.0.1,from=<>,to=<[EMAIL PROTECTED]>: 450 Service temporarily unavailable.
authdaemond.plain is running, and connecting to the IMAP server works fine.
Both the IMAP server and the mail server use the same authdaemon module. If one connects the other one should also connect. The above error message claims that it can't find the filesystem socket.
The only way I can see this happening would be if you were upgrading from an older version of Courier, and the newer version was compiled with different options that specified different directories; then when installing the new version something went wrong and not all files were installed, so the IMAP server is one version, and the mail server is another version.
pgpBKfDo3Xs4Y.pgp
Description: PGP signature
