• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • (Plesk for Windows):
    MySQL Connector/ODBC 3.51, 5.1, and 5.3 are no longer shipped with Plesk because they have reached end of life. MariaDB Connector/ODBC 64-bit 3.2.4 is now used instead.
  • Our UX team believes in the in the power of direct feedback and would like to invite you to participate in interviews, tests, and surveys.
    To stay in the loop and never miss an opportunity to share your thoughts, please subscribe to our UX research program. If you were previously part of the Plesk UX research program, please re-subscribe to continue receiving our invitations.
  • 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.

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