Issue mailling server

[mehdi ala]

Hi Im still a noob but i have a problem with my dedicated server postfix 2 days ago i have 45 domains and all of them stoped receiving or sending email with no bounce no error of connection or anything in client end.

but when i check the mail log after sending an email i found this error :

Nov 5 16:46:16 servername postfix/smtpd[6355]: connect from unknown[ipadress]
Nov 5 16:46:17 servername postfix/smtpd[6355]: 8A02719C059A: client=unknown[ipadress], sasl_method=DIGEST-MD5, sasl_username=contact@@hotel-plaza.com
Nov 5 16:46:17 servername postfix/cleanup[6501]: 8A02719C059A: message-id=<[email protected]>
Nov 5 16:46:17 servername check-quota[6504]: Starting the check-quota filter...
Nov 5 16:46:17 servername /usr/lib64/plesk-9.0/psa-pc-remote[906]: handlers_stderr: SKIP
Nov 5 16:46:17 servername /usr/lib64/plesk-9.0/psa-pc-remote[906]: SKIP during call 'check-quota' handler
Nov 5 16:46:17 servername dk_sign[6506]: Starting the dk_sign filter...
Nov 5 16:46:17 servername /usr/lib64/plesk-9.0/psa-pc-remote[906]: handlers_stderr: PASS
Nov 5 16:46:17 servername /usr/lib64/plesk-9.0/psa-pc-remote[906]: PASS during call 'dd51-domainkeys' handler
Nov 5 16:46:17 servername postfix/qmgr[1284]: 8A02719C059A: from=<[email protected]>, size=620, nrcpt=1 (queue active)

Nov 5 16:46:17 servername postfix/error[5795]: 8A02719C059A: to=<[email protected]>, relay=none, delay=0.44, delays=0.37/0/0/0.06, dsn=4.4.2, status=deferred (delivery temporarily suspended: lost connection with 127.0.0.1[127.0.0.1] while sending DATA command)

Please can someone help me with this issue ??

 

[IgorG]

The issue is caused when Plesk Email Security extension is installed because skip_name_resolve directive on /etc/my.cnf breaks 127.0.0.1 resolution into localhost:

status=deferred (delivery temporarily suspended: lost connection with 127.0.0.1[127.0.0.1] while sending DATA command)

Our team of developers confirmed this as Plesk Email Security bug with ID EXTCERT-3178, which will be fixed in future extension updates.
As a workaround, you can comment out the skip_name_resolve directive and restart the MySQL service.