On Wed, Jun 17, 2015 at 10:35:33PM -0400, Steve Matzura wrote:

> Here's a set of maillog entries showing attempted delivery of a
> message from me to an address in /etc/virtual:
> 
> Jun 18 01:48:26 <machine-name> postfix/smtpd[30639]: connect from
> p3plsmtpa07-03.prod.phx3.secureserver.net[173.201.192.232]
> Jun 18 01:48:27 <machine-name> postfix/smtpd[30639]: lost connection
> after STARTTLS from p3plsmtpa07-03.prod.phx3.secureserver.net[173.201.192.232]

The TLS handshake failed or similar.  There would normally be more
errors in the log related to this, perhaps you're not postin the
relevant "smtpd" log entries.

> Jun 18 01:48:27 <machine-name> postfix/cleanup[30642]: 4CA5B8CB6:
> message-id=<20150618014827.4CA5B8CB6@<my-FQDN>>

Likely a postmaster notice was sent (adjust notify_classes).

> Jun 18 01:48:27 <machine-name> postfix/qmgr[28319]: 4CA5B8CB6:
> from=<double-bounce@<my-FQDN>>, size=929, nrcpt=1 (queue active)

Yep, a postmaster notice.

> This next entry mentions Dovecot, I'll deal with that elsewhere. I
> suspect it's the cause of the problem.
> 
> Jun 18 01:48:27 <machine-name> postfix/lmtp[30644]: 4CA5B8CB6:
> to=<postmaster@<my-domain>>, orig_to=<postmaster>, relay=none,
> delay=0.02, delays=0.02/0/0/0, dsn=4.4.1, status=deferred (connect to
> <my-FQDN>[private/dovecot-lmtp]: No such file or directory)

Dovecot is not listening on the configured socket.

-- 
        Viktor.

Reply via email to