in reply to SPF for Perl Monks domains

I have never received any (spoofed or other) e-mail from the perlmonks domain other than the initial welcome message IIRC. Is this really a problem?

CountZero

"If you have four groups working on a compiler, you'll get a 4-pass compiler." - Conway's Law

Replies are listed 'Best First'.
Re: Re: SPF for Perl Monks domains
by Fletch (Bishop) on May 15, 2004 at 01:42 UTC

    All it takes is one. I don't know what spammer I've ever ticked off but I've received joe-job bounces for my personal domain. Or unfortuately these days, one person with a Wintendo email client with a perlmonks email in their address book.

    And yes, it breaks forwarding. But there's a proposal for working around that, and with the potential for stopping spam it's worth a minimal breakage.

      I use mail forwarding, and I don't have a problem with Spam. Mind you, I don't know how many emails my server deletes as spam, but it can't be that many, it will display a message about "NN new messages on servers" and fetch around that many messages.

      Still, when your proposal for fixing mail forwarding becomes an established standard, let's discuss the possibility again. Alternately, refuse all mail from perlmonks ... how many messages do you receive from there, anyway?

      --
      TTTATCGGTCGTTATATAGATGTTTGCA

        Alternately, refuse all mail from perlmonks

        It is what I would like to do, but by means of SPF. That way, legitimate mail is not blocked. Without SPF, I would now add perlmonks.org to the blacklist, and would then probably forget about it. If perlmonks.org then would start providing email services for monks, I'd have a problem. SPF moves the administration from the receiving to the supposedly sending end; so only one person has to update the information when it changes, instead of system administrators of all systems that have it blocked.

        Juerd # { site => 'juerd.nl', plp_site => 'plp.juerd.nl', do_not_use => 'spamtrap' }