• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is 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.

Qmail SMTP no longer has AUTH ==> open relay

A

alanwbaker

Guest
Recently my provider advised me that I have an open mail relay, so I ran some web-based open-relay checkers and it is indeed open (Akk!)

In PLESK System > Server > Mail > Preferences > Relaying...
the authorization button is selected and the SMTP box is checked.
Presumably psa-qmail-1.03-rh9.build75050824.12 has qmail-smtpd-auth compiled in and these selections activate it.

A) Is this correct?

To see what capabilities the mail server actually offers, I did...

telnet localhost 25
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
220 abcd.org ESMTP
ehlo xyz.org
250-sjpc.org
250-STARTTLS
250-PIPELINING
250 8BITMIME

Uh-oh. No AUTH. When I set this up two years ago it also offered...
250-AUTH=LOGIN CRAM-MD5 PLAIN
250-AUTH LOGIN CRAM-MD5 PLAIN

I replied with an invalid auth string...
auth AGJha2VyMgBhc2RmYXNkZmFzZGY=
And qmail replied...
503 you are already authenticated

B) To prevent an open relay, shouldn't qmail offer AUTH? If so, how do I restore this capability?

advTHANKSance
Alan
 
Back
Top