> On Sep 10, 2018, at 2:25 AM, A. Schulze wrote:
>
> you may route messages from sender1 to a second postfix instance
> and configure that instance to enforce tls to $destination for _any_ sender
So far, it looks like a single instance with per-sender-class
transports will suffice.
--
> On Sep 10, 2018, at 1:58 AM, Stefan Bauer 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
Stefan Bauer:
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
("
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 non
> On Sep 9, 2018, at 3:51 PM, Viktor Dukhovni
> wrote:
>
> 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.
I should mention that this only scale
* Stefan Bauer :
> 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_check
> On Sep 9, 2018, at 3:39 PM, Stefan Bauer 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 bo
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 na
Thank you. Before diving deeper into this, you're saying it is possible
with postfix to setup a static routing (with maps / tables) in the form:
mails from Domain-A or specific SASL-user to DOMAIN Z with enforced TLS
mails from Domain-B or specific SASL-user to DOMAIN Z with none TLS
Is that corr
Stefan Bauer:
> Hi,
>
> is there a way to specify on a per user basis (sasl authenticated user) if
> TLS should be none or may or encrypted for a specific recipient domain?
There is no "per-recipient map" version for Postfix SMTP client
parameters (or most other parameters). It does not make sens
Hi,
is there a way to specify on a per user basis (sasl authenticated user) if
TLS should be none or may or encrypted for a specific recipient domain?
I would like to have the user to decide if his mail to a specific domain
should be TLS encrypted and then maybe bounce back but let other users
ma
11 matches
Mail list logo
