Re: Assist with a spam message, check_sender_access and check_client_access targets

2023-01-20 Thread Jaroslaw Rafa
Dnia 20.01.2023 o godz. 15:25:56 Scott Techlist pisze: > X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on > myhost.myservername.com > X-Virus-Scanned: amavisd-new at myservername.com > X-Spam-Flag: NO > X-Spam-Score: 1.451 > X-Spam-Level: * > X-Spam-Status: No, score=1.451

RE: Assist with a spam message, check_sender_access and check_client_access targets

2023-01-20 Thread Scott Techlist
Re: Raf >In other words, check_sender_access tests the address >that ended up being stored in the From_ mbox pseudo header: > > From > bounce-91040_html-994996332-142678-514026815-45...@bounce.s11.mc.pd25.com > Fri Jan 20 12:40:11 2023 > >And check_client_access doesn't check any headers at

Re: Assist with a spam message, check_sender_access and check_client_access targets

2023-01-20 Thread raf
On Fri, Jan 20, 2023 at 03:53:25PM -0600, Noel Jones wrote: > On 1/20/2023 3:25 PM, Scott Techlist wrote: > > I'm fuzzy on if I can block a message like the one below one using > > check_sender_access or check_client_access. > > check_sender_access is the envelope sender address, the >

Re: relay transport ignore

2023-01-20 Thread raf
On Fri, Jan 20, 2023 at 03:25:39PM +0100, Matteo Cazzador wrote: > Hi, this is the postconf -n (i'm using virtualmin with virtual domain) > > *# postconf* > > alias_database = hash:/etc/aliases > alias_maps = hash:/etc/aliases > allow_percent_hack = no > append_dot_mydomain = no > biff = no >

Re: backop-transport maps

2023-01-20 Thread Wietse Venema
natan: > W dniu 20.01.2023 o?15:04, Wietse Venema pisze: > > natan: > >> Hi > >> I try to run "backup" transport maps like: > >> > >> smtpd_sender_login_maps = > >> #first-main database > >> proxy:mysql:/etc/postfix/mysql_sender_login_maps.cf > >> #second-backup > >>

Re: backop-transport maps

2023-01-20 Thread natan
W dniu 20.01.2023 o 15:04, Wietse Venema pisze: natan: Hi I try to run "backup" transport maps like: smtpd_sender_login_maps = #first-main database proxy:mysql:/etc/postfix/mysql_sender_login_maps.cf #second-backup proxy:mysql:/etc/postfix/mysql_sender_login_maps-backup.cf Both

Re: relay transport ignore

2023-01-20 Thread Matteo Cazzador
Hi, this is the postconf -n (i'm using virtualmin with virtual domain) *# postconf* alias_database = hash:/etc/aliases alias_maps = hash:/etc/aliases allow_percent_hack = no append_dot_mydomain = no biff = no broken_sasl_auth_clients = yes compatibility_level = 2 header_checks =

Re: backop-transport maps

2023-01-20 Thread Wietse Venema
natan: > Hi > I try to run "backup" transport maps like: > > smtpd_sender_login_maps = > #first-main database > proxy:mysql:/etc/postfix/mysql_sender_login_maps.cf > #second-backup > proxy:mysql:/etc/postfix/mysql_sender_login_maps-backup.cf > > Both databases are the same because they

backop-transport maps

2023-01-20 Thread natan
Hi I try to run "backup" transport maps like: smtpd_sender_login_maps = #first-main database    proxy:mysql:/etc/postfix/mysql_sender_login_maps.cf #second-backup    proxy:mysql:/etc/postfix/mysql_sender_login_maps-backup.cf Both databases are the same because they are synchronized (cluser