Thanks. Had to add the path but now
http://spamassassin.apache.org/updates/MIRRORED.BY is exempted from SSL
redirection. This will help with older clients.
--
Kevin A. McGrail
VP Fundraising, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project
I forgot about KAM.cf, just grepped in rulesrc and found nothing.
Giovanni
On 09/18/18 19:01, Kevin A. McGrail wrote:
> It's in KAM.cf, I believe:
>
> # SPF THAT DOESN'T REALLY CARE IF EMAIL IS A FORGERY
> ifplugin Mail::SpamAssassin::Plugin::AskDNS
> askdns JMQ_SPF_NEUTRAL_ALL
It's in KAM.cf, I believe:
# SPF THAT DOESN'T REALLY CARE IF EMAIL IS A FORGERY
ifplugin Mail::SpamAssassin::Plugin::AskDNS
askdns JMQ_SPF_NEUTRAL_ALL _SENDERDOMAIN_ TXT /^v=spf1 .+\?all$/
describe JMQ_SPF_NEUTRAL_ALL SPF set to ?all!
scoreJMQ_SPF_NEUTRAL_ALL 0.5
endif
--
Kevin A.
Hi,
I noticed that Google servers started blocking emails with "suspicious spf
records" like for example:
"v=spf1 include:musvc.com include:turbo-smtp.com mx a +all".
Any idea on how to write a rule to catch something like that ?
Thanks & Cheers
Giovanni
On Tue, 18 Sep 2018 08:20:38 +0100
Marisa Clardy wrote:
> Hello,
>
> How I'd do it is with this regex:
>
> /^(apache(\r|\n)+)+$/s
Owing to the way the normalized body is stored, this kind of thing won't
work with body rules - that's what the thread is about. It can work with
rawbody rules, but
On Tue, Sep 18, 2018 at 07:41:09AM -0400, Kevin A. McGrail wrote:
> Hi Bill, I think it might be an older wget or LWP or what not that can't
> deal with MIRRORED.BY being https. Michael from linuxmagic also
> reported a similar issue.
>
> Can anyone help with a .htaccess that exempts the
Hi Bill, I think it might be an older wget or LWP or what not that can't
deal with MIRRORED.BY being https. Michael from linuxmagic also
reported a similar issue.
Can anyone help with a .htaccess that exempts the MIRRORED.BY?
Current lines:
Redirect /favicon.ico
