[feedback-report] [Fwd: ARF feedback.]
J.D. Falk
jdfalk at yahoo-inc.com
Tue Jul 5 12:24:11 PDT 2005
Forwarding by request.
-------- Original Message --------
Subject: ARF feedback.
Date: Sat, 2 Jul 2005 14:41:08 -0700
From: Vipul Ved Prakash <vipul at cloudmark.com>
To: <jdfalk at yahoo-inc.com>
JD,
Somehow still can't get to ARF list, so I am sending feedback directly
to you. These points are based my experience with Razor/SpamNet that
supports submission of messages to us:
"Message-Truncated" header
There will be instance when the message to be reported is
too big and the client is not willing to report the entire
message. It could be argued that the recipient does not want
to get multiple 5Mb reports for large spam/worm emails. A
new header could be used to indicate that the message was
truncated at a particular length. For instance, a reporting
agent could be programmed with a max limit, say 64Kb and for
messages that exceed 64Kb, it would add a header:
Message-Truncated: 65535
and truncate the message at 65535 bytes. This could be an
optional header.
Formats other than RFC822
I pointed this out in the BOF at INBOX, and I don't want to
belabor this point, but I think it is important to support
formats other than RFC822. Outlook, for instance, provides
the message through MAPI in form of multiple "buckets". In
many cases, a single MIME part is presented as multiple
buckets (HTML version, text version, etc), and re-creation
of original RFC822 is mostly impossible. I understand that
Outlook support is not the primary focus at this stage, but
there should be a provision in the spec to include outliers
like Outlook. For Outlook this could be done through a MIME
header like message/outlook, that comprises of multiple
message/outlookbuckets.
Other clients like Eudora and mail.app also modify the
original message, but they retain the RFC822 format. For
these the UserAgent hint is sufficient to indicate that the
reported message is different from the original one.
Supressing Headers
Razor and Cloudmark clients support an option to supress
headers and only report the message. I think this is an
important privacy option, since headers can contain internal
routing information that might be considered private by some
organizations. Header suppression could also be support by a
MIME header like message/rfc822-noheaders.
Cheers,
Vipul
--
J.D. Falk, Anti-spam Product Manager, Yahoo! Mail
jdfalk at yahoo-inc.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mipassoc.org/pipermail/abuse-feedback-report/attachments/20050705/6e094b4b/attachment.html
More information about the abuse-feedback-report
mailing list