• We value your experience with Plesk during 2024
    Plesk strives to perform even better in 2025. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2024.
    Please take this short survey:

    https://pt-research.typeform.com/to/AmZvSXkx
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

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