> On Sep 10, 2018, at 1:58 AM, Stefan Bauer <cubew...@googlemail.com> wrote:
> 
> So each sender's instance is an own smtp-line in master.cf ?

Yes, one for each sender "class".

> 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

Almost, you need to remove the whitespace around the "=" sign in master.cf
option overrides (or use "-o { option = value }" in sufficiently recent
Postfix versions. http://www.postfix.org/master.5.html).

> 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?

Yes.

> If so - will all settings from main.cf be used as well for additional 
> smtp-instances?
> 
> like smtp_tls_security_level encrypt ?

Anything you don't override applies to the custom transports also.
The only "exception" is concurrency settings, which are really
queue manager parameters not transport parameters, and have names
of the form "<transportname>_...", e.g. smtp_destination_concurrency_limit,
... those need to be set per-transport, or else you get e.g.
"default_destination_concurrency_limit", ...

-- 
        Viktor.

Reply via email to