Plesk: Postfix & authenticated SMTP on an alternative port – login failed, generic failure

Want to help support this blog? Try out Oh Dear, the best all-in-one monitoring tool for your entire website, co-founded by me (the guy that wrote this blogpost). Start with a 10-day trial, no strings attached.

We offer uptime monitoring, SSL checks, broken links checking, performance & cronjob monitoring, branded status pages & so much more. Try us out today!

Profile image of Mattias Geniar

Mattias Geniar, January 07, 2012

Follow me on Twitter as @mattiasgeniar

If you want to run your Postfix config in Plesk on an alternative port and still have authenticated SMTP as a possibility, you need to make a small change to the Postfix config.

The KB to add an extra SMTP port to Postfix says to add the following in your Postfix’s master.cf file.

<IP_Address>: inet n -- -- – – smtpd -o smtpd_proxy_filter=127.0.0.1:10025

That won’t be enough for authenticated SMTP, as it doesn’t run chrooted like that. If you want to add that, change the line to this:

<IP_Address>: inet n – n -- – smtpd -o smtpd_proxy_filter=127.0.0.1:10025

That way, your logs won’t fill up with:

warning: SASL authentication failure: cannot connect to saslauthd server: No such file or directory

warning: unknown[193.239.211.227]: SASL login authentication failed: generic failure

The solution has also been suggested to the KB, they may add it overtime directly.



Want to subscribe to the cron.weekly newsletter?

I write a weekly-ish newsletter on Linux, open source & webdevelopment called cron.weekly.

It features the latest news, guides & tutorials and new open source projects. You can sign up via email below.

No spam. Just some good, practical Linux & open source content.