DSN and 4.62.9 problem

[Kai Schaetzl]

One more comment.
There are other occasions where watermarking rejects legitimate messages.  
Sent a complaint to abuse at oneandone.net today. Got back the typical 
automated confirmation from <> with a correct in-reply-to but not quoting 
everything else (of, course, why should they?). milter-null (that I'm 
currently testing) marked it as "DSN or MDN for message that did not 
originate here".

This whole anti-backscatter stuff is based on the idea that the only stuff 
coming from <> are delayed DSNs, and that's simply not true. I guess it 
works great if you are in the middle of a backscatter storm from a joejob, 
but it doesn't work as a daily production solution. And in the case of a 
backscatter storm you could just reject all messages from <> without 
producing much more false positives than watermarking does.

Kai

-- 
Kai Schätzl, Berlin, Germany
Get your web at Conactive Internet Services: http://www.conactive.com