[feedback-report] ARF and MIME attachments
Matthew Elvey
matthew at elvey.com
Sat Jun 3 23:01:53 PDT 2006
As has been discussed before, It doesn't make sense for an ARF that
uses MIME to be used for messages currently sent by end-users to the
addresses that abuse.net gives out, typically abuse@<domain>. As long
as ARF is using MIME, this needs to be explicit in the draft, for
example:
"ARF is not to be sent to the legacy standard abuse email address.
Instead it should only be sent to addresses that the sender anticipates
will be prepared to handle it, such as arfreports@<domain>"
((Alternately, MIME could be abandoned... I'm not clear that the
benefits of MIME outweigh the costs.
Whether the advice is sound or not, it's true that it is common and
widely taken advice to refuse email containing MIME attachments.
The need to delimit things could easily be done with simple delimiters
other than the ones MIME uses.
(This is obviously true; MIME is generally just a set of delimiters in
ASCII text; that's the only thing that SMTP servers universally
support.)
Is there supposed to be some way that reporters will discover whether
ARF (or mail with attachments) is supported?
AFAIK, no.
What are the pluses of MIME? Existing, tested, probably reusable code
and functionality. Is it worth it? ))
More information about the abuse-feedback-report
mailing list