Doesn't spamc/spamd need block/welcomeliist support???

2024-03-20 Thread Bill Cole
I'm not sure how I've not noticed before, but unless I'm missing 
something, there is no way to replicate the [block,welcome]list 
functionalities of the spamassassin script when using the spamc/spamd 
interface.


Does anyone see it hiding somewhere that I don't?

Does anyone have any rationale for this missing functionality?

I don't expect that it would be difficult to add. (Something I've 
believed every time I've taken on a coding task...)


--
Bill Cole
b...@scconsult.com or billc...@apache.org
(AKA @grumpybozo and many *@billmail.scconsult.com addresses)
Not Currently Available For Hire


RE: [WARNING] RE: Help with rule matching when it shouldn't

2024-03-20 Thread Erickarlo Porro
I figured out why my RETURNPATH rule was matching. My example was too sanitized 
and I was actually trying to find multiple domains in my regex. So it would 
always match due to the fact that it would always not equal the other domain I 
was looking for.

From: Erickarlo Porro 
Sent: Wednesday, March 20, 2024 10:02 AM
To: users@spamassassin.apache.org
Subject: RE: Help with rule matching when it shouldn't

I want to catch “yahoo” anywhere in the header so that it matches if its in the 
name or in the address. So I would want to match 
ya...@gmail.com

Regarding "__RETURNPATH_IS", I have the rule set to “!~” so shouldn’t that rule 
only match if that header has anything but yahoo.com? I did notice that I had a 
typo when I wrote the email due to the period but my rule actually looks like 
this:
header __RETURNPATH_IS Return-Path !~ /yahoo\.com$/i
My intention is to find emails that have a specific company name in the From 
header but the return path does not include their domain. So like in my 
theoretical example, if someone emails me from 
ya...@gmail.com and the return path does include 
yahoo.com then don’t match but if someone emails me from 
ya...@othercompany.com but the return path does 
not include yahoo.com, match my rule.

From: Jimmy mailto:thana...@gmail.com>>
Sent: Tuesday, March 19, 2024 7:45 PM
To: users@spamassassin.apache.org
Subject: Re: Help with rule matching when it shouldn't

The correct syntax for the header rule should be:

header __FROM_ADDRESS From:addr =~ /\@yahoo\.com/i

This rule will specifically match email addresses containing 
"@yahoo.com" while excluding addresses like 
"ya...@gmail.com".

Regarding the example provided, the "__RETURNPATH_IS" rule should indeed be 
triggered since it matches "yahoo.com" in the return-path. If 
you're uncertain about the intended behavior of the rules, please clarify the 
requirements so we can adjust the rules accordingly.

Jimmy

On Wed, Mar 20, 2024 at 4:52 AM Erickarlo Porro 
mailto:epo...@earthcam.com>> wrote:
Could someone help me figure out why my custom rule is matching when it should 
not be matching?

This is my current setup:
header __FROM_ADDRESS From =~ /yahoo/i
header __RETURNPATH_IS Return-Path !~ /yahoo.com$/i

meta   NOT_IT (__FROM_ADDRESS && __RETURNPATH_IS)
describe NOT_IT Sender is not correct
score  NOT_IT 4.0


Take these headers as an exmaple:
From: ya...@gmail.com
Return-path: ya...@yahoo.com

If I send an email that would have those headers Spamassassin is getting a hit 
for my NOT_IT rule but that should not match because __RETURNAPTH_IS should not 
get a hit.

How can I troubleshoot this?




RE: Help with rule matching when it shouldn't

2024-03-20 Thread Erickarlo Porro
I want to catch “yahoo” anywhere in the header so that it matches if its in the 
name or in the address. So I would want to match 
ya...@gmail.com

Regarding "__RETURNPATH_IS", I have the rule set to “!~” so shouldn’t that rule 
only match if that header has anything but yahoo.com? I did notice that I had a 
typo when I wrote the email due to the period but my rule actually looks like 
this:
header __RETURNPATH_IS Return-Path !~ /yahoo\.com$/i
My intention is to find emails that have a specific company name in the From 
header but the return path does not include their domain. So like in my 
theoretical example, if someone emails me from 
ya...@gmail.com and the return path does include 
yahoo.com then don’t match but if someone emails me from 
ya...@othercompany.com but the return path does 
not include yahoo.com, match my rule.

From: Jimmy 
Sent: Tuesday, March 19, 2024 7:45 PM
To: users@spamassassin.apache.org
Subject: Re: Help with rule matching when it shouldn't

The correct syntax for the header rule should be:

header __FROM_ADDRESS From:addr =~ /\@yahoo\.com/i

This rule will specifically match email addresses containing 
"@yahoo.com" while excluding addresses like 
"ya...@gmail.com".

Regarding the example provided, the "__RETURNPATH_IS" rule should indeed be 
triggered since it matches "yahoo.com" in the return-path. If 
you're uncertain about the intended behavior of the rules, please clarify the 
requirements so we can adjust the rules accordingly.

Jimmy


On Wed, Mar 20, 2024 at 4:52 AM Erickarlo Porro 
mailto:epo...@earthcam.com>> wrote:
Could someone help me figure out why my custom rule is matching when it should 
not be matching?

This is my current setup:
header __FROM_ADDRESS From =~ /yahoo/i
header __RETURNPATH_IS Return-Path !~ /yahoo.com$/i

meta   NOT_IT (__FROM_ADDRESS && __RETURNPATH_IS)
describe NOT_IT Sender is not correct
score  NOT_IT 4.0


Take these headers as an exmaple:
From: ya...@gmail.com
Return-path: ya...@yahoo.com

If I send an email that would have those headers Spamassassin is getting a hit 
for my NOT_IT rule but that should not match because __RETURNAPTH_IS should not 
get a hit.

How can I troubleshoot this?




Re: Help with rule matching when it shouldn't

2024-03-20 Thread Matus UHLAR - fantomas

On 20.03.24 06:44, Jimmy wrote:

Regarding the example provided, the "__RETURNPATH_IS" rule should indeed be
triggered since it matches "yahoo.com" in the return-path. If you're
uncertain about the intended behavior of the rules, please clarify the
requirements so we can adjust the rules accordingly.


Note that Return-Path may not exist at the time spam is filtered as it is 
often added when mail is delivered to mailbox.



On Wed, Mar 20, 2024 at 4:52 AM Erickarlo Porro  wrote:


Could someone help me figure out why my custom rule is matching when it
should not be matching?



This is my current setup:

header __FROM_ADDRESS From =~ /yahoo/i

header __RETURNPATH_IS Return-Path !~ /yahoo.com$/i



meta   NOT_IT (__FROM_ADDRESS && __RETURNPATH_IS)

describe NOT_IT Sender is not correct

score  NOT_IT 4.0





Take these headers as an exmaple:

From: ya...@gmail.com

Return-path: ya...@yahoo.com



If I send an email that would have those headers Spamassassin is getting a
hit for my NOT_IT rule but that should not match because __RETURNAPTH_IS
should not get a hit.



How can I troubleshoot this?


--
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.
"The box said 'Requires Windows 95 or better', so I bought a Macintosh".