Cannot send mail: can't read SMFIC_OPTNEG reply packet header: Connection reset by peer

Created:

2017-04-18 11:50:35 UTC

Modified:

2017-08-08 13:25:49 UTC

0

Was this article helpful?


Have more questions?

Submit a request

Cannot send mail: can't read SMFIC_OPTNEG reply packet header: Connection reset by peer

Applicable to:

  • Plesk for Linux
  • Plesk Onyx for Linux

Symptoms

Cannot send mail. The following errors can be found in /var/log/maillog :

Apr 14 20:17:23 web103 postfix/smtpd[81825]: warning: milter inet:127.0.0.1:12768: can't read SMFIC_OPTNEG reply packet header: Connection reset by peer
Apr 14 20:17:23 web103 postfix/smtpd[81825]: warning: milter inet:127.0.0.1:12768: read error in initial handshake
Apr 14 20:24:58 web103 postfix/smtpd[70070]: NOQUEUE: milter-reject: CONNECT from unknown[203.0.113.2]: 451 4.7.1 Service unavailable - try again later; proto=SMTP
Apr 14 20:24:58 web103 postfix/smtpd[70070]: NOQUEUE: milter-reject: EHLO from unknown[203.0.113.2]: 451 4.7.1 Service unavailable - try again later; proto=SMTP helo=<[203.0.113.2]>
Apr 14 20:24:58 web103 postfix/smtpd[70070]: NOQUEUE: milter-reject: MAIL from unknown[203.0.113.2]: 451 4.7.1 Service unavailable - try again later; from=<john.doe@example.com> proto=ESMTP helo=<[203.0.113.2]>

Cause

The cause of such behavior is either that Postfix configuration file /etc/postfix/main.cf was customized or something was added as an argument for one of the postfix processes in /etc/postfix/master.cf .

As a result milter does not recognize headers passed by Postfix.

Resolution

Execute the command:

# /usr/local/psa/admin/sbin/mchk --without-spam

Have more questions? Submit a request
Please sign in to leave a comment.