• 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.

Plesk 12 breaks localhost smtp relaying

HostaHost

Regular Pleskian
Fresh installs of Plesk 12 are not including the typical

mynetworks = 127.0.0.0/8 [::1]/128

in the postfix main.cf that prior versions included. This breaks locally executing apps that use localhost as an SMTP server for outbound relay without authentication.

Is there a way to correct this via the control panel, or is manually editing the file the only way?
 
Outgoing antispam can't count emails which were sent by smtp without authorization. Therefore it was restricted.
Usually scripts uses sendmail, therefore most of users noticed nothing. Those who send emails with login/passwords noticed nothing too.
As possible workaround you may add 127.0.0.0/8 [::1]/128 to white list. But emails will pass Outgoing Antispam in this case.
 
The primary issue we ran into is with users who do not host their email locally. If they enable the mail service for the domain, in order to create an account to auth against, then email can't reach their domain since it will be attempted locally rather than where the MX records point. If mail isn't enabled, then there's no way to auth. Creating a bogus domain just for the purpose of creating email accounts for applications to auth off of is kind of a poor workaround.
 
Back
Top