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.
  • If your focus in on saving the bandwidth (man, that's a lotta e-mail!), then you need to do as much upfront testing as possible (before the client gets to the "data" section of their e-mail). You may also not want to REJECT, which would double the bandwidth with bouncebacks (not sure if the original message is bounced back, too).

    I love Postfix -- they have some really great UCE [porcupine.org] measures. I had some problems with "A or MX record" thing (reject_unknown_client?) -- that would block things like stories that
    • For Postfix, I reject during the SMTP handshake, not bouncing it with checks later. Amavis doesn't bounce it either... we just swallow the spam. And I don't bounce anything from my procmail tests or clamscan tests. The only bounces I generate are $baduser@stonehenge.com (provided they aren't a spammed-to-death address).
      --
      • Randal L. Schwartz
      • Stonehenge
  • If you want an rbl feed of this list, or a URL to a private text file containing the IPs (both updated once a minute), please let me know (merlyn@stonehenge.com).

    The caveat is that there might be false positives. It's useful as an outright smtp block, or at a place where you can return "try again later" to an incoming SMTP connection, but not at a point where you've already accepted the mail. You want a legit mailer to retry, but the bad guys mailers will not.

    --
    • Randal L. Schwartz
    • Stonehenge