[pfx] Re: cyrus_sasl_config_path is ignored

Christoph Zimmermann via Postfix-users: > The setting for cyrus_sasl_config_path is ignored. Apparently, ignored by the Cyrus SASL library. > Specifying this in main.cf doesn't have any effect as only the standard > locations are > searched for smtpd.conf as the following strace snippet shows:

[pfx] Re: rbl override doesn't work perhaps due to sender using relay

That should work. Thanks https://www.postfix.org/access.5.html Feb 24, 2024 8:05:00 AM Matus UHLAR - fantomas via Postfix-users : >>> On 24.02.24 00:49, lists--- via Postfix-users wrote: I have set up rbl_override for the sender's domain. > [...] smtpd_recipient_restrictions = >>>

[pfx] Re: rbl override doesn't work perhaps due to sender using relay

On 24.02.24 07:43, lists--- via Postfix-users wrote: https://www.dnswl.org/?page_id=15 I get your point but this is for a different blocking list. That is spamcop and spamassassin have different blocking lists. you can still use postscreen which supports multiple weighed block/allow lists,

[pfx] Re: rbl override doesn't work perhaps due to sender using relay

On 24.02.24 00:49, lists--- via Postfix-users wrote: I have set up rbl_override for the sender's domain. [...] smtpd_recipient_restrictions = [...] check_client_access hash:/etc/postfix/rbl_override, reject_rbl_client bl.spamcop.net, check_policy_service unix:private/policy Feb 24, 2024

[pfx] Re: rbl override doesn't work perhaps due to sender using relay

On 2024-02-24 at 10:43:36 UTC-0500 (Sat, 24 Feb 2024 07:43:36 -0800 (PST)) lists--- via Postfix-users is rumored to have said: https://www.dnswl.org/?page_id=15 I get your point but this is for a different blocking list. That is spamcop and spamassassin have different blocking lists. What

[pfx] Re: rbl override doesn't work perhaps due to sender using relay

https://www.dnswl.org/?page_id=15 I get your point but this is for a different blocking list. That is spamcop and spamassassin have different blocking lists. What I really need is a way to make the rbl_override work for the domain name that has been related. I am going to review my logs and

[pfx] Re: rbl override doesn't work perhaps due to sender using relay

lists--- via Postfix-users skrev den 2024-02-24 09:49: check_client_access hash:/etc/postfix/client_checks, check_sender_access hash:/etc/postfix/sender_checks, check_client_access hash:/etc/postfix/rbl_override, reject_rbl_client bl.spamcop.net, check_policy_service

[pfx] Re: rbl override doesn't work perhaps due to sender using relay

Sorry for the top post but I am using my phone. The rbl_override file only contains domain names with "space OK". If I whitelisted that IP address, I would be whitelisting a Microsoft address that I assume has multiple users. Also that relay IP address isn't static. Feb 24, 2024 6:03:54 AM

[pfx] Re: cyrus_sasl_config_path is ignored - PLEASE IGNORE

Should have read the documentation before :-) (https://www.postfix.org/SASL_README.html#server_cyrus). Didn't know that it actually applied to original Debian as well... Perhaps worth updating the docs? Thanks, Chris On 24.02.24 14:41, Christoph Zimmermann wrote: The setting for

[pfx] Re: rbl override doesn't work perhaps due to sender using relay

On 24.02.24 00:49, lists--- via Postfix-users wrote: I have set up rbl_override for the sender's domain. However it occasionally gets blocked by spamcop. The user owns a domain but relays the mail from outlook. Here is the bounce message the user received: Remote server returned '550

[pfx] cyrus_sasl_config_path is ignored

The setting for cyrus_sasl_config_path is ignored. Specifying this in main.cf doesn't have any effect as only the standard locations are searched for smtpd.conf as the following strace snippet shows: openat(AT_FDCWD, "/etc/postfix/sasl/smtpd.conf", O_RDONLY) = -1 ENOENT (No such file or

[pfx] rbl override doesn't work perhaps due to sender using relay

I have set up rbl_override for the sender's domain. However it occasionally gets blocked by spamcop. The user owns a domain but relays the mail from outlook. Here is the bounce message the user received: ** Remote server returned '550 5.7.514 Decision Engine classified the mail item