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! score JMQ_SPF_NEUTRAL_ALL 0.5 endif
-- Kevin A. McGrail VP Fundraising, Apache Software Foundation Chair Emeritus Apache SpamAssassin Project https://www.linkedin.com/in/kmcgrail - 703.798.0171 On Tue, Sep 18, 2018 at 12:16 PM Giovanni Bechis <giova...@paclan.it> wrote: > 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 >
