On Fri, May 10, 2024 at 08:47:26PM -0400, Jason Hirsh via Postfix-users wrote:
> I am running Postfix/Dovecot/MySQL mail server. It was doing ok
> until I tried to improve it.
Reverting back to the "unimproved" prior state may be the best course of
action.
> May 10 20:11:27 triggerfish postfix/lmtp[47754]: 172816542AC3:
> to=<ja...@theoceanwindow.com>, orig_to=<operator>, relay=none, delay=38307,
> delays=38307/0.01/0/0, dsn=4.4.1, status=deferred (connect to
> triggerfish.theoceanwindow.com[private/dovecot-lmtp]: Connection refused)
The Dovecot LMTP delivery agent is not listening on the
/var/spool/postfix/private/dovecot-lmtp
unix-domain socket. Either that's not the right path, or there's a
problem on the dovecot side.
> I am pretty sure I did something wrong with TLS/SSL.
Certainly not on the Postfix side, but perhaps dovecot is expecting to
find a working certificate and private key for that service, and that's
why it is not up and running. However, with a unix-domain socket, in
the access-restricted "private/" directory there's really not much point
in TLS certs. You should configure dovecot LMTP to not bother with TLS.
Ai was working in certificates, I have been at the so long my eye are crossed
> root@triggerfish:/home/jason # postconf -n
Nothing to see here. The issue is not in the Postfix configuration.
> Any ideas or pointers or random thoughts would be appreciated
The issue is on the dovecot side, and you should seek help on the
dovecot list, rather than here.
--
Viktor.
_______________________________________________
Postfix-users mailing list -- postfix-users@postfix.org
To unsubscribe send an email to postfix-users-le...@postfix.org
