On 05/Feb/12 06:39, Murray S. Kucherawy wrote:
>> From: ietf.org On Behalf Of Alessandro Vesely
>
>>> @@ -311,19 +324,19 @@
>>>
>>>     10.  Published abuse mailbox addresses SHOULD NOT reject messages not
>>>          in the ARF format, as generation of ARF messages can
>>> -        occasionally be unavailable or not applicable.
>> 
>> Paragraph 10, for receivers, should terminate here.
> 
> Do you think the rest of what's there now is incorrect?

It is not incorrect, it is in the wrong paragraph.  Indeed, paragraph
11 starts with "This is" as a want to be a continuation of #10.

>> The rest of paragraph 10 and paragraph 11 (for senders) are confusing
>> and need additional rewording, IMHO.
> 
> Please provide substitute text.

  Experience suggests use of ARF is advisable in most contexts.
  Automated recipient systems can handle abuse reports sent in ARF
  format at least as well as any other format such as plain text,
  with or without a copy of the message attached. That holds even for
  systems that didn't ask for ARF format reports, provided that
  reports are generated with use by recipients not using automated
  ARF parsing in mind. Anyone sending unsolicited reports in ARF
  format can legitimately presume that recipients will only be able
  to access the human readable (first, text/plain) part of it, and
  MAY include all information needed also in this part. Further, they
  MAY ensure that the report is readable when viewed as plain text,
  to give low-end ticketing systems as much assistance as possible.

>> Non-actionable reports could still be useful for collecting
>> statistics, whose evaluation may eventually result in a better
>> sending.  This is especially true for spf- or dkim-reporting.
> 
> I think this fits under "take action on it".

Yes, in a slightly indirect sense.

BTW, publishing a _report address /is/ opt-in, isn't it?

>> Should we say that the 3rd mime part of non-actionable reports should
>> be "text/rfc822-headers"?
> 
> Why?

To be more lightweight.
_______________________________________________
marf mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/marf

Reply via email to