* Stefan Bauer <cubew...@googlemail.com>:
> Am Sonntag, 9. September 2018 schrieb Wietse Venema :
> > Instead, you can use transport_maps to choose between different
> > Postfix SMTP clients (with different configurations) based on the
> > recipient address or domain.
> >
> > You can use the access map or header/body_checks FILTER action
> > ("FILTER name-of-transport:", without a domain after the ":") to
> > choose delivery methods based on other message properties, with
> > some loss of elegance.
>
> I see no way to combine both. I want to enforce tls for sender1 to
> google.com but not for sender2 to google.com.
Use two Postfix instances to deal with it. Single messages out first, then
route them as desired:
The first instance accepts the message and uses a ?_destination_recipient_limit
of 1 to hand the message over to the second instance.
In the second instance create (at least) a second smtp service (e.g.
mandatorytls), which enforces TLS to any destination.
Use a suited map type, search for a sender or recipient and let the query
result "FILTER mandatorytls". It will tell Postfix to use the TLS only smtp
service.
p@rick
--
[*] sys4 AG
https://sys4.de, +49 (89) 30 90 46 64
Schleißheimer Straße 26/MG,80333 München
Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263
Vorstand: Patrick Ben Koetter, Marc Schiffbauer, Wolfgang Stief
Aufsichtsratsvorsitzender: Florian Kirstein
