Matus UHLAR - fantomas:
> >> how?
> >>
> >> if you define different smtp transports with different smtp_bind_address
> >> defined in master.cf, the sender_dependent_default_transport_maps should
> >> do
> >> what you want.
> 
> On 29.05.20 15:17, George wrote:
> >Thanks for your response. My problem is that I do not know what to use in
> >the file where sender_dependent_default_transport_maps is defined.
> >
> >Do I set it like this:
> >@domain1_from_webserver1.com mastercf_transport1:
> >@domain2_from_webserver1.com mastercf_transport1:
> >@domain1_from_webserver2.com mastercf_transport2:
> >@domain1_from_webserver2.com mastercf_transport2:
> 
> do you have mastercf_transport1 and mastercf_transport2 defined in
> master.cf?
> 
> >Or is there any way for me to define the incoming webserver IP in
> >sender_dependent_default_transport_maps?
> 
> http://www.postfix.org/postconf.5.html#sender_dependent_default_transport_maps
> 
> The tables are searched by the envelope sender address and @domain.
> 
> so you can only configure sending user and sending domain there...

It is possible to use the 'filter' command for this.

/etc/postfix/main.cf
    smtpd_client_restrictions = 
        check_client_access hash:/etc/postfix/client_access

/etc/postfix/client_access:
    1.2.3.4     filter smtp-for-4:
    1.2.3.5     filter smtp-for-5:

/etc/postfix/master.cf:
    smtp-for-4 .. .. .. .. .. .. smtp
        -o smtp_bind_address=x.x.x.x
    smtp-for-5 .. .. .. .. .. .. smtp
        -o smtp_bind_address=y.y.y.y

This is supported as of Postfix 2.7.

The 'filter' feature can also be used for rate limits > 1/s by using
paralel deliveries, for IP address reputations (see below) and more.

        Wietse

Fragment from the release notes:

[Feature 20100117] The FILTER action in access maps or header/body_checks
now supports sender reputation schemes that dynamically choose the
SMTP source IP address. Typically, mail is split into classes, and
all mail in class X is sent out from an SMTP client IP address that
is reserved for class X.

This is implemented by specifying FILTER actions with empty next-hop
destinations in access maps or header/body_checks, and by configuring
in master.cf one Postfix SMTP client for each SMTP source IP address,
where each client has its own "-o myhostname" and "-o smtp_bind_address"
settings.

Reply via email to