• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Postfix: mapping outgoing IP address with SASL username

Miguel_Tellería

Basic Pleskian
[Plesk 12.0.18 on CentOS 6, Postfix 2.8.17]

Dear all,

I would like to have the outgoing IP address for submitted emails at the 587 port to be based on the SASL username (or the domain part of it at least).

I observe that Postfix uses the sender_dependent_default_transport_maps to choose the IP based on the MAIL FROM: part (thanks to a mapping maintained by Plesk in /var/spool/postfix/plesk/sdd_transport_maps).

However the MAIL FROM: is specified by the client submitter and cannot be verified in any way. And not only for security reasons, also for a specific use case of a local web app we need to use the SASL username instead of the sender.

If the change cannot be done globally, we are open to create a new submission process in master.cf with whichever options needed in order to have at least this web app be routed their email in this specific way.

Thanks in advance for any suggestion.

Regards,

Miguel Telleria
 
Back
Top