On Feb 9, 2010, at 11:20 AM, Alessandro Vesely wrote:
On 09/Feb/10 19:29, Chris Lewis wrote:
Alessandro Vesely wrote:
form abuse(_at_)domain is standardized by rfc 2142. Some people (e.g.
Abusix) may plan to send machine generated complaints at such addresses.
And they'll learn very very soon that that doesn't work.
Been there/done that in a limited fashion, and even in that limited
fashion, it don't work.
Why not, _what_ goes wrong?
Do NOT assume that TiS buttons have anything to do whatsoever with
RFC2142, standardized role accounts, or whois "abuse-mailbox" entries.
Filter tuning doesn't, nor do FBLs (ARF'd or otherwise). While abuse@
_may_ get derivations of TiS reports via ARF in some specific cases that
are pre-arranged in advance, in no sense should we encourage such role
accounts to be target for a raw MUA (or even MTA) stream of complaints.
It seems to me that a simple filter could determine ARF/non-ARF quality of a
message in a fraction of the time that spamassassing would take to process
it, assuming abuse@ boxes are whitelisted.
You (and others) are obsessing about the MIME format of inbound email, which is
something of a scarlet fish.
Any real ISP is going to be getting ARF formatted reports from all over the
place, most solicited, some not. So it's not really much more meaningful than
the mail coming in as MIME or in German, or with an attachment.
What you need to be able to identify is who sent it to you, for what purpose,
under what agreement and what you need to do with the data in it. Those are
entirely orthogonal to the trivial implementation detail of the MIME structure
of the email. Once you've done that, then you know what you need to do with the
mail, and the details of how it's formatted become relevant.
Cheers,
Steve
_______________________________________________
Asrg mailing list
Asrg(_at_)irtf(_dot_)org
http://www.irtf.org/mailman/listinfo/asrg