So each sender's instance is an own smtp-line in master.cf ? If so - does it work like this?
src_domain1 unix - - n - - smtp -o smtp_tls_policy_maps = hash:/etc/postfix/tls_policy -o syslog_name=src_domain1 tls_policy: domain-that-does-not-support-tls.tld none and in main.cf sender_dependent_default_transport_maps = hash:/etc/postfix/sender_transport sender_transport: @src_domain1 src_domain1: Is that correct? If so - will all settings from main.cf be used as well for additional smtp-instances? like smtp_tls_security_level encrypt ? Am So., 9. Sep. 2018 um 21:51 Uhr schrieb Viktor Dukhovni < [email protected]>: > > > > On Sep 9, 2018, at 3:39 PM, Stefan Bauer <[email protected]> > wrote: > > > > I see no way to combine both. I want to enforce tls for sender1 to > google.com but not for sender2 to google.com. > > I assume you don't literally mean "google.com", since they support > TLS, and you can just enforce TLS to "google.com" for both and be > done. > > For domains where you're less certain of ongoing TLS support, you > can try to deal with this by choosing different transports for > mail from sender1 vs. mail from sender2, via > sender_default_transport_maps. In sender1's instance of the > smtp(8) transport, the TLS policy will be mandatory for > "example.com" recipients, while in sender2'd instance of > the smtp(8) transport it will be opportunistic. > > -- > -- > Viktor. > >
