[prev in list] [next in list] [prev in thread] [next in thread]
List: postfix-users
Subject: Re: round robin map with ipv4 and ipv6
From: Wietse Venema <wietse () porcupine ! org>
Date: 2020-02-14 13:58:30
Message-ID: 48Jw2Z3qRtzJrNv () spike ! porcupine ! org
[Download RAW message or body]
Emanuel:
[ Charset windows-1252 converted... ]
>
> El 12/2/20 a las 20:14, Wietse Venema escribi?:
> > Emanuel:
> >> Is it possible to create different files with different IP addresses so
> >> that when sending an email they are sent from different round maps?
> > You would use master.cf entries with different smtp_bind_address or
> > smtp_bind_address6 settings, and select one with a filter command.
> >
> > With master.cf entries
> >
> > /etc/postfix/master.cf:
> > relay-1 unix - - n - - smtp
> > -o smtp_bind_address=1.2.3.1
> > relay-2 unix - - n - - smtp
> > -o smtp_bind_address=1.2.3.2
> > relay-3 unix - - n - - smtp
> > -o smtp_bind_address=1.2.3.3
> > relay-4 unix - - n - - smtp
> > -o smtp_bind_address=1.2.3.4
> >
> > Then you need a nested table which requires a restriction class.
> >
> > /etc/postfix/main.cf:
> > smtpd_client_restrictions = check_client_access
> > inline:{
> > { 200.58.x.x = class1 }
> > { 200.58.x.y = class2 }
> > }
> >
> > restriction_classes = class1, class2
> > class1 = check_client_access randmap:{filter relay-1:, filter relay-2:}
> > class2 = check_client_access randmap:{filter relay-3:, filter relay-4:}
> >
> > Instead of inline:{}, a hash or pcre table would work too.
>
> YES.! i need this!
>
> so I can call a file and indicate the class, this is very useful?
>
> /etc/postfix/main.cf:
> smtpd_client_restrictions = check_client_access
> inline:{
> { hash:/etc/postfix/bad_client = class1 }
> { hash:/etc/postfix/bad_client = class2 }
> }
No, I wrote INSTEAD OF inline:{}, a hash or pcre table would work.
Wietse
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic