Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • 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.

    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

    • X-Spam-Status: No, score=3.335 tagged_above=-999 required=5 tests=[DNS_FROM_RFC_ABUSE=0.479, MSGID_FROM_MTA_ID=0.927, NO_REAL_NAME=0.55, SPF_NEUTRAL=1.379]

      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.
      • Those do look a *lot* like SA rules, which is odd -- the copperfasten web site doesn't mention SA! As an SA developer, I find this interesting...

        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