• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Plesk 9.2.3 - Problem with email

E

EulogioE

Guest
Hi, updated to version 9.2.3 and since then I have problems with the mail, I got several errors;

1:
XXX.XXX.XXX.XXX does not like recipient.
Remote host said: 550-Your message was rejected by this system and was not delivered.
550-Reason: Messages from your location are rejected, bad go missing identifier (HELO).
2:
XXX.XXX.XXX.XXX does not like recipient.
Remote host said: 504 5.5.2 <server>: Helo command rejected: need fylly-qualified hostname.

The update was a few weeks ago and since then come the problems. (The directions are well written, as it always worked but now does not work)
Why do these problems occur?
A greeting.
 
Make sure that you have correct hostname in FQDN format in /var/qmail/control/me file.
 
Yes that's right - the problem comes from a faulty content of the /var/qmail/control/me file.

This happens mostly every time I run an update/upgrade of Plesk. Last it happened updating from 9.2.3 to actual 9.3.0.
Normally the content is the domain name of the server, in my case hxxxxxx.servercompetenz.de (a Strato VServer).
After any update/upgrade, the me file just contains hxxxxxx.

Some email servers then return "Bad HELO...", block the email and place the domains of my customers on their blacklist. AARGR - you always have to remember to edit the me file directly after the update and to send emails around asking to delete from blacklist whenever it happened again.

Have not found any reason for that appearance nor a point where to place any corrections.
Plesk still shows the proper server name...

Any fix known for that?

With greetings!
 
Back
Top