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.
  • Since the same thing happened to me yesterday. Lots of bounce mail, subscription confirmation requests, and some "You sent us a virus" mail, all apparently originating from their webmaster account.

    Wonder if someone's using CPAN e-mail addresses or something.
    • Nope. Mine were to modperl @ sergeant.org, whereas my CPAN stuff comes direct to matt @ sergeant.org. I've never used modperl in direct mailings, so it must have been picked up by some crawler. Maybe the site deserved the attack, but I (and everyone else) certainly didn't.

      Intruigingly there's an article at the top of Slashdot right now talking about a very similar incident, but not the same.
    • For a few weeks, I've been getting occasional messages "from" perl5-porters-subscribe, Tim Bunce, and others in the Perl community that really aren't from them at all, but from mail servers in Poland and Russia, often containing viruses. I've even gotten a few bounces (and stories from other people) of messages I've apparently "sent" to others, showing similar characteristics.
  • I added this to my .procmailrc:

    :0
    * lusoglobal
      IN/spam

    That caught it. Yesterday was a bad day for email for me too--tchrist fixed a config bug on one of his training machines that caused it to finally be able to deliver about 9 months of 6-hourly cron messages on CPAN updates. I filtered those from my mailbox after 250ish and then added another procmail entry to shitcan the rest.

    I love procmail. Between procmail and spamassassin, I'm a happy bunny boy.

    --Nat