Re: Difficulty getting OLEVBMacro rules to work

On Fri, 30 Oct 2020 22:17:07 + (UTC) Jason Wong wrote: > I turned on loadplugin Mail::SpamAssassin::Plugin::OLEVBMacro in the > v343.pre file. ... > Oct 30 17:58:57.955 [23115] dbg: plugin: loading > Mail::SpamAssassin::Plugin::OLEVBMacro from @INC > > When I run make test, it passes: ... >

Re: different Return-Path: and From:

For future reference if you want to start a new thread, compose a new email to the list address. Don't reply to a random post and replace the subject and body. Traditional threading is based on headers, and isn't affected by changing the subject. On Fri, 30 Oct 2020 16:02:52 +0100 Marc Roos wrot

Difficulty getting OLEVBMacro rules to work

Hi all, I'm running SpamAssassin version 3.4.4 on Perl version 5.30.3. I turned on loadplugin Mail::SpamAssassin::Plugin::OLEVBMacro in the v343.pre file. I have both Archive::Zip and IO::String installed. If I check my rules with spamassassin --lint -D, the plugin is being loaded: Oct 30 17:5

Re: different Return-Path: and From:

Hi > I had a phishing mail skip my spf check. The spf check was done on > the Return-Path and not the From:. Is a default convention? How does > spamassassin treat a different Return-Path and From in a message? You have to distinguish the 'envelope' of the email, the addresses technically neede

RE: different Return-Path: and From:

> so you want your own messages blocked everywhere? I do not know yet. I can assume this different on something like a mailing list. It is irritating that the From has a credible name, in this case from a bank.

different Return-Path: and From:

I had a phishing mail skip my spf check. The spf check was done on the Return-Path and not the From:. Is a default convention? How does spamassassin treat a different Return-Path and From in a message?