Re: Order of handling whitelist/blacklist
> On Mar 28, 2024, at 12:18 PM, Matus UHLAR - fantomas > wrote: > >>> On 27.03.24 20:56, Philip Prindeville via users wrote: >>>> I have something that looks like: >>>> >>>> whitelist_from_rcvd v...@yandex.ru vger.kernel.org >>>> >>>> blacklist_from *@yandex.ru >>>> >>>> And I only ever seem to see the 2nd rule being hit, but not the first. >>>> >>>> What is the order of evaluation? Mail::SpamAssassin::Conf doesn't say >>>> that I could find. >>>> >>>> You'd think the first would happen first, since it's more specific. >>>> >>>> Or, maybe that both would happen. > >>> On Mar 28, 2024, at 2:39 AM, Matus UHLAR - fantomas >>> wrote: >>> they both should happen. >>> note that the second argument must be Received: header provided by trusted >>> server, so that argument depends on proper TrustPath set up >>> >>> https://cwiki.apache.org/confluence/display/SPAMASSASSIN/TrustPath > > On 28.03.24 11:55, Philip Prindeville via users wrote: >> My config also has: >> >> trusted_networks 192.168.6.0/24 >> trusted_networks 192.168.8.0/24 >> trusted_networks 127.0.0.1/32 >> >> So I don't think that's the problem. >> >> What are some steps to troubleshoot how the white/black-listing is happening? > > can you show us the headers? Here or somewhere on pastebin? > No need, but thanks. Got my head out of my butt. I had somehow missed that vger.kernel.org as a "multihomed" (or "anycast", depending on how you look at it) had ceased to exist as an outbound relay for the LKML's and been replaced by (am|ny|sv|sy).mirrors.kernel.org back around Dec 19 last year. When I switched to: whitelist_from_rcvd v...@yandex.ru mirrors.kernel.org things started working again. -Philip
Re: Order of handling whitelist/blacklist
> On Mar 28, 2024, at 12:18 PM, Matus UHLAR - fantomas > wrote: > >>> On 27.03.24 20:56, Philip Prindeville via users wrote: >>>> I have something that looks like: >>>> >>>> whitelist_from_rcvd v...@yandex.ru vger.kernel.org >>>> >>>> blacklist_from *@yandex.ru >>>> >>>> And I only ever seem to see the 2nd rule being hit, but not the first. >>>> >>>> What is the order of evaluation? Mail::SpamAssassin::Conf doesn't say >>>> that I could find. >>>> >>>> You'd think the first would happen first, since it's more specific. >>>> >>>> Or, maybe that both would happen. > >>> On Mar 28, 2024, at 2:39 AM, Matus UHLAR - fantomas >>> wrote: >>> they both should happen. >>> note that the second argument must be Received: header provided by trusted >>> server, so that argument depends on proper TrustPath set up >>> >>> https://cwiki.apache.org/confluence/display/SPAMASSASSIN/TrustPath > > On 28.03.24 11:55, Philip Prindeville via users wrote: >> My config also has: >> >> trusted_networks 192.168.6.0/24 >> trusted_networks 192.168.8.0/24 >> trusted_networks 127.0.0.1/32 >> >> So I don't think that's the problem. >> >> What are some steps to troubleshoot how the white/black-listing is happening? > > can you show us the headers? Here or somewhere on pastebin? > No need, but thanks. Got my head out of my butt. I had somehow missed that vger.kernel.org as a "multihomed" (or "anycast", depending on how you look at it) had ceased to exist as an outbound relay for the LKML's and been replaced by (am|ny|sv|sy).mirrors.kernel.org back around Dec 19 last year. When I switched to: whitelist_from_rcvd v...@yandex.ru mirrors.kernel.org things started working again. -Philip
Re: Order of handling whitelist/blacklist
> On Mar 28, 2024, at 2:39 AM, Matus UHLAR - fantomas wrote: > > On 27.03.24 20:56, Philip Prindeville via users wrote: >> I have something that looks like: >> >> whitelist_from_rcvd v...@yandex.ru vger.kernel.org >> >> blacklist_from *@yandex.ru >> >> And I only ever seem to see the 2nd rule being hit, but not the first. >> >> What is the order of evaluation? Mail::SpamAssassin::Conf doesn't say that >> I could find. >> >> You'd think the first would happen first, since it's more specific. >> >> Or, maybe that both would happen. > > they both should happen. > note that the second argument must be Received: header provided by trusted > server, so that argument depends on proper TrustPath set up > > https://cwiki.apache.org/confluence/display/SPAMASSASSIN/TrustPath > -- > Matus UHLAR - fantomas, uh...@fantomas.sk ; http://www.fantomas.sk/ > Warning: I wish NOT to receive e-mail advertising to this address. > Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu. > One OS to rule them all, One OS to find them, > One OS to bring them all and into darkness bind them My config also has: trusted_networks 192.168.6.0/24 trusted_networks 192.168.8.0/24 trusted_networks 127.0.0.1/32 So I don't think that's the problem. What are some steps to troubleshoot how the white/black-listing is happening? Thanks
Order of handling whitelist/blacklist
Hi. I have something that looks like: whitelist_from_rcvd v...@yandex.ru vger.kernel.org blacklist_from *@yandex.ru And I only ever seem to see the 2nd rule being hit, but not the first. What is the order of evaluation? Mail::SpamAssassin::Conf doesn't say that I could find. You'd think the first would happen first, since it's more specific. Or, maybe that both would happen.
