• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Resolved Postfix 550 5.7.1 Command rejected

skywalllker

New Pleskian
My server was fine for the past few months. However, starting 2 days ago, some client complaining they can't received any emails and the sender's emails was bounced. Here's the example of bounced mail:

I'm sorry to have to inform you that your message could not be delivered to one or more recipients. It's attached below.

Final-Recipient: rfc822; john@mydomain.com
Action: failed
Status: 5.7.1 (Command rejected)
Remote-MTA: dns; plesk.myserver.com
Diagnostic-Code: smtp; 550 5.7.1 Command rejected


I have to edit /etc/postfix/main.cf and comment out line below:
#smtpd_milters = inet:localhost:12768

Restart the postfix and it's working fine again. My question is, what is the cause of this problem? Could be the Plesk auto update somehow mess up the config?

Thanks!
 
The above referenced KB says:

Resolution

Check and correct the following entries in /etc/postfix/main.cf file:

# grep -ir milt /etc/postfix/main.cf
smtpd_milters = , inet:127.0.0.1:12768
non_smtpd_milters =


But it is not clear what the correct entry should be.
Also I believe the configurations are different for Debian and Red Hat.
 
Check and correct the following entries in /etc/postfix/main.cf file:

The KB - article suggests to CHECK your own "main.cf" - file AND IF the result differs from the one you see in the KB - article, pls. CORRECT it with the given example. ;)
 
My problem was with grey listing, rejecting for some IPs
Disabled.
/usr/local/psa/bin/grey_listing --update-server -status off
 
I have a weirder case.. I am seeing Command rejected blurb for Incoming mail..

In the example below, the incoming mail from 85.95.239.48 is rejected.. I have many others like this.. Many customers complain that they cannot receive email from specific people.

I am enclosing an entire section.. Email address beginnings are replaced with XXX

Mar 5 04:57:33 jedi postfix/smtpd[58742]: warning: hostname mail.alserotours.com does not resolve to address 85.95.239.48
Mar 5 04:57:33 jedi postfix/smtpd[58742]: connect from unknown[85.95.239.48]
Mar 5 04:57:33 jedi courier-imapd: Connection, ip=[::ffff:186.235.79.58]
Mar 5 04:57:33 jedi postfix/smtpd[58742]: D4DA724A16E7: client=unknown[85.95.239.48]
Mar 5 04:57:34 jedi postfix/cleanup[53939]: D4DA724A16E7: message-id=<bdb11d80-edcc-a256-1b33-b19034c27376@creditforum.se>
Mar 5 04:57:34 jedi /usr/lib64/plesk-9.0/psa-pc-remote[6816]: handlers_stderr: SKIP
Mar 5 04:57:34 jedi /usr/lib64/plesk-9.0/psa-pc-remote[6816]: SKIP during call 'limit-out' handler
Mar 5 04:57:34 jedi check-quota[58780]: Starting the check-quota filter...
Mar 5 04:57:34 jedi /usr/lib64/plesk-9.0/psa-pc-remote[6816]: handlers_stderr: SKIP
Mar 5 04:57:34 jedi /usr/lib64/plesk-9.0/psa-pc-remote[6816]: SKIP during call 'check-quota' handler
Mar 5 04:57:34 jedi spf[58781]: Starting the spf filter...
Mar 5 04:57:34 jedi spf[58781]: SPF result: neutral
Mar 5 04:57:34 jedi spf[58781]: SPF status: PASS
Mar 5 04:57:34 jedi /usr/lib64/plesk-9.0/psa-pc-remote[6816]: handlers_stderr: PASS
Mar 5 04:57:34 jedi /usr/lib64/plesk-9.0/psa-pc-remote[6816]: PASS during call 'spf' handler
Mar 5 04:57:34 jedi postfix/cleanup[53939]: D4DA724A16E7: milter-reject: END-OF-MESSAGE from unknown[85.95.239.48]: 5.7.1 Command rejected; from=<XXX@creditforum.se> to=<XXX@albeyoglu.net> proto=ESMTP helo=<mail.alserotur.com>
Mar 5 04:57:34 jedi postfix/smtpd[58742]: disconnect from unknown[85.95.239.48]
 
Mar 5 04:57:34 jedi postfix/cleanup[53939]: D4DA724A16E7: milter-reject: END-OF-MESSAGE from unknown[85.95.239.48]: 5.7.1 Command rejected;

Did you find a solution/reason? facing exactly the same.

EDIT: greylisting is not enabled
 
Last edited:
Back
Top