So far today I've received 117 instances of this kind of spam.
They all have 10 to 14 bad header traits that are easy to catch with procmail, so they were easily filtered into my bitbucket.
For folks who don't want to set up procmail, there are two common traits that SpamAssassin can filter on.
The first is the From: address. It's always infoxxxx@something, where xxxx is four random characters. Ideally, you could Blocklist From info????@, and SpamAssassin would put it all in Graymail. However, Member Tools won't accept ? as a legal character, so the best you can do is Blocklist From info*@, and that's likely to cause too many false positives.
The second trait is the SpamAssassin rule INVALID_DATE. Every instance of this kind of spam has an invalid date because the first character after Date: is not a space. The default score for INVALID_DATE is 0.432. If you adjust the score for INVALID_DATE to a value greater than your spam threshold, SpamAssassin will catch every instance of this type of spam.
They all have 10 to 14 bad header traits that are easy to catch with procmail, so they were easily filtered into my bitbucket.
For folks who don't want to set up procmail, there are two common traits that SpamAssassin can filter on.
The first is the From: address. It's always infoxxxx@something, where xxxx is four random characters. Ideally, you could Blocklist From info????@, and SpamAssassin would put it all in Graymail. However, Member Tools won't accept ? as a legal character, so the best you can do is Blocklist From info*@, and that's likely to cause too many false positives.
The second trait is the SpamAssassin rule INVALID_DATE. Every instance of this kind of spam has an invalid date because the first character after Date: is not a space. The default score for INVALID_DATE is 0.432. If you adjust the score for INVALID_DATE to a value greater than your spam threshold, SpamAssassin will catch every instance of this type of spam.
Statistics: Posted by legenda — Sun Dec 15, 2024 2:26 pm