For months I've been running point for the #SpamAssassin team in the world's worst game of whack-a-mole. The scrapers of random URLs (in our case 'detail' views) have at times managed to stall rule maintenance intermittently.
So if you're hosting email on a shit ISP, make a better choice.
@blindcoder
Have a look at
/etc/spamassassin/local.cf
whitelist_from *@anymail.com
If spamassassin works with amavis you will find more settings in
/etc/amavis/conf.d/20-debian_defaults
Search for $whitelist_sender or @whitelist_sender_maps. These entries are self-explanatory.
In the same [โฆ]
Bonus points for the double phishy
XXX-workers-dev.translate.goog
XXX-vercel-app.translate.goog
XXX--ipfs-dweb-link.translate.goog
and 2000 more I have. Seriously. #spamassassin should be rejecting /translate.goog URLs too >_<!!!
Whew. I think I finally got spamass-milter talking to spamd. At least, there's no errors in the logs and my test emails arrive in a reasonable time frame.
Now just to wait for more spam.
#Postfix #SpamAssassin
Screenshot of the source code for an email message that has been identified as spam by SpamAssassin.
I finally got my first bit of legitimate spam (is that even a thing?) since installing SpamAssassin on my mail server. SpamAssissin did its job and correctly tagged the message as spam.
Honestly, when I first set up my mail server, I thought I'd get a lot [โฆ]
[Original post on darkmoon.social]
Woohoo! I got spamassassin working. Now to wait for some more spam. I never thought that would be something I'd write. ๐
#ServerAdmin #SpamAssassin #Spam #Postfix