Re: Re: More about the SPF RRTYPE

Frank Ellermann <[email protected]>
Newsgroups gmane.mail.spam.spf.discuss
Message-ID <CAHhFybp50jdYORio6RHGZcuhDaToxt3kB7oALM0WvbwPvDwZ5A@mail.gmail.com>
On 18 August 2011 20:37, Scott Kitterman wrote:

> The _spf approach would make wild carding impossible (_spf.*.exmple.com),
> but I'm not sure I really care.  Someone may.

nslookup -q=txt *.claranet.de
nslookup -q=txt xyzzy.claranet.de

I guess I care at least as far as xyzzy.claranet.de is affected... ;-)
But I can't tell how popular such "catchall" constructs still are in 2011,
or rather how unpopular they are today.

My "experiment" to report all spam to wrong@xyzzy at SpamCop failed years
ago when I hit SpamCop report limits, or when I got spam faster than I
could report it, or when Clara.Net sometimes disabled this catchall when
their server couldn't handle the resulting traffic anymore.

Some days ago I saw a mail to nur-fuer-heiko@xyzzy used *once* in NetNews
(German mail abuse newsgroup) before I knew SPF, or maybe even before SPF
existed.  Whatever spammers do with their address lists, removing "cruft"
is obviously not their top priority.  If the spammer spent real money for
the list containing nur-fuer-heiko@xyzzy or any part-of-message-id@xyzzy
(s)he's entitled for a full refund as far as I'm concerned.

-Frank
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.