On Tue, 29 Aug 2006, Stuart D. Gathman wrote:
On Tue, 29 Aug 2006, wayne wrote:
In the past, I have talked with spamcop folks about SPF issues. They
may well be willing to make some changes. It may be very possible
that they would be willing to publish "v=spf1 -all" records on the
domains that are used exclusively for spamtraps. I think it is highly
doubtful that they will be willing to stop counting backscatter as a
listable offense.
Ok, I will request that. I wonder if spammers would simple stop forging
domains with -all? I suppose that would be a good thing...
In my book, a DSN is not backscatter if the sender provides no way
to recognize forgeries.
I can't find where to request that. They simply bring up their FAQ
about why DSNs to forged email are bad. Duhhh. Be nice if they
provided a way to detect the forged email. They say their clients asked
them to block backscatter. If publishing a -all SPF record is too hard,
you'd think they would use SRS or BATV to block the backscatter.
I'm trying to think of a policy that will keep everyone happy.
Send DSN only for SPF NONE? Those senders are the ones who can't
get the SMTP REJECT. They suggest a reasonable workaround: send
DSNs from a different IP. I think I can make pymilter do that.
Sigh - not like I had nothing to work on.
--
Stuart D. Gathman <stuart(_at_)bmsi(_dot_)com>
Business Management Systems Inc. Phone: 703 591-0911 Fax: 703 591-6154
"Confutatis maledictis, flammis acribus addictis" - background song for
a Microsoft sponsored "Where do you want to go from here?" commercial.
-------
Sender Policy Framework: http://www.openspf.org/
Archives at http://archives.listbox.com/spf-discuss/current/
To unsubscribe, change your address, or temporarily deactivate your
subscription,
please go to
http://v2.listbox.com/member/?listname=spf-discuss(_at_)v2(_dot_)listbox(_dot_)com