Slash Boxes
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

use Perl Log In

Log In

[ Create a new account ]

merlyn (47)

AOL IM: realmerlyn (Add Buddy, Send Message)
Yahoo! ID: realmerlyn (Add User, Send Message)

See my home page [].

Journal of merlyn (47)

Thursday November 10, 2005
03:05 PM

when email goes bad, for CPAN user JDHEDDEN

[ #27533 ]
I'm trying to contact cpan user JDHEDDEN. But when I try the address, given spam protected in his just-released module (

Jerry D. Hedden, <jdhedden AT 1979 DOT usna DOT com>

), I get

Hi. This is the James mail server at linux.
I'm afraid I wasn't able to deliver your message to the following addresses.
This is a permanent error; I've given up. Sorry it didn't work out.  Below
I include the list of recipients and the reason why I was unable to deliver
your message.
554 refused mailfrom because of SPF policy

which is bogus. I hate being able to not reach someone, especially when I want to contribute to their public work.

But even worse, this is probably an example of an overly agressive spam filter. I remember the net before spam. I long for those days.

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
More | Login | Reply
Loading... please wait.
  • What's happening is that his server is using strict SPF [] rules, and the domain of your email address doesn't implement SPF (or the IP you used is not allowed by your domain). Given that SPF is fairly new, I would not recommend using strict rules, but that's the way it goes...
    • Well, I was able to reach him directly at the indicated bounced address. So the problem is more likely that he has a forwarding system that doesn't rewrite the "from" (the big flaw in these systems like SPF), and didn't bother testing it.
      • Randal L. Schwartz
      • Stonehenge
      • And to followup to myself, yes, he has SPF enabled on his ultimate mailbox, but his "public" mailbox is a naive forwarder, and this breaks SPF.

        The problem is squarely his fault. He should change his ultimate mailbox, disable SPF on his mailbox, or fix his forwarder. Maybe he wasn't aware of his problem before, but he certain is aware now.

        • Randal L. Schwartz
        • Stonehenge