I hadn't thought about this before, but someone told me that the renewal emails I send out for The Perl Review get a high enough SpamAssassin score, about 3.5ish, to be blocked and probably never seen.
That's no good. Since we're about to start our third year of print issues, it's time for most subscribers to renew. If you haven't seen your renewal message, you can still renew online without it, but I'd also like to know if a message titled "The Perl Review: Time to renew" showed up in your spam folder so I can fix that for next time.
I checked my code and found it didn't have the parts i thought I had put in last time, including names in the To and From fields. I also got a report that the email might be missing Message-ID. If anyone would like to help me investigate this, please send your raw message with headers to me (it's the reply address on the email).
This is actually a big deal in the magazine industry as people tyr to figure out how to get around bulk mailings and giving money to the post office.
What SpamAssassin tests? (Score:1)
What SpamAssassin tests does the mail match?
This is actually a big deal in the magazine industry as people tyr to figure out how to get around bulk mailings and giving money to the post office.
SpamAssassin isn't that mysterious. It's easy to find out what the tests match on, and therefore you can chang
Re:What SpamAssassin tests? (Score:1)
This claims to be from Copperfasten Mail Firewall but they seem to be SpamAssassin rules. As was mentioned message id and to/from names are missing.
Re: (Score:1)
Anyway, it's expected that occasional non-spam will score about 3.3 points -- and a newsletter sent to many subscribers would be quite typical for that score range.
The SA default threshold is 5, which is quite a bit higher than 3.3; anyone using a threshold that low needs to expect to spend some time monitoring for false positives, and rescuing and whitelisting th
Re: (Score:1)
no prob (Score:1)
I'd say with a To, From and MEssage-ID, though, you should be 99% of the way there....
Re:no prob (Score:2)
It looks like SPF_NEUTRAL gets a pretty high score, so I'll have to think about that.
Re:no prob (Score:1)
it has got a pretty high correlation with spam; 95% of the SPF_NEUTRAL hits fire on spam these days (3.2% of spam, only 0.16% of ham). still, it's nonintuitive.
Notifications (Score:1)
Re:Notifications (Score:2)
Your subscription, however, ends with the issue after the next one, so you're okay right now.
Re:Notifications (Score:1)
Re:Notifications (Score:1)