|
You are here: Home>> Feedback Loop>> ARF
What is ARF?
- ARF- Abuse Reporting Format.
ARF is intended to standardize Feedback Loop emails. This effort will help prevent feedback loop recipients from requiring multiple parsers for various mailers' FBL reports.
What is the difference between the traditional AOL Feedback Loop format and ARF?
The traditional format is a MIME multipart message with one empty text part and one message/rfc822 part with the original message being complained about. Parts of the header of the message being complained about are redacted out, where normally the AOL ScreenName recipient would be present.
ARF is defined in a internet draft located at http://www.mipassoc.org/arf/ . ARF messages have three mime parts, one part for general information, one machine parsable and meta data part, and the last part as the original message being complained about. The original message is redacted to protect clear text occurrences of AOL screen names and email addresses.
ARF can not be read in most major e-mail clients. The format assumes that parsing and decoding will be done via script. Please do not contact AOL with questions about reading ARF FBL emails.
What is there to note about the AOL implementation of the Abuse Reporting Format?
AOL will not fill the Reported-URI field in the second mime part. ARF messages from AOL will have the Subject as defined in the original draft, with the connecting IP shown, and not the original subject of the email being complained about.
What is AOL's future plan regarding ARF?
AOL is eliminating its traditional feedback loop format in favor of ARF. On September 2, 2008, AOL will convert all existing feedback loops to ARF. Concurrently, the option to subscribe for a non-ARF loop will be removed.
How do I sign up for ARF?
You can sign up for ARF by filling out the normal Feedback Loop form. Any existing loops going to the same feedback loop email address will be converted to ARF.
What if I want to test the new abuse reporting format while still using the traditional Feedback format?
All feedback loops will be converted to ARF on September 2, 2008. It is possible to test ARF while maintaining your traditional feedback loop by applying for multiple loops directed to different email addresses. Note: When you sign up for an ARF loop to a particular email address, any other feedback loops directed to that address will also be converted to ARF!
*****EXAMPLE REPORT*****
From: <scomp@aol.net>
Date: Thu, 8 Mar 2005 17:40:36 EDT
Subject: Email Feedback Report for IP 10.67.41.167
To: <aaolfeedback@example.net>
MIME-Version: 1.0
Content-Type: multipart/report; report-type=feedback-report; boundary="part1_13d.2e68ed54_boundary"
--part1_13d.2e68ed54_boundary
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
This is an email abuse report for an email message received from IP 10.67.41.167 on Thu, 8 Mar 2005 14:00:00 EDT.
For more information about this format please see http://www.mipassoc.org/arf/.
--part1_13d.2e68ed54_boundary
Content-Type: message/feedback-report
Feedback-Type: abuse
User-Agent: SomeGenerator/1.0
Version: 0.1
--part1_13d.2e68ed54_boundary
Content-Type: message/rfc822
Content-Disposition: inline
From: <somemailer@example.net>
Received: from mailserver.example.net (mailserver.example.net [10.67.41.167])
by example.com with ESMTP id M63d4137594e46; Thu, 08 Mar 2005 14:00:00 -0400
To: <Undisclosed Recipients>
Subject: Earn money
MIME-Version: 1.0
Content-type: text/plain
Message-ID: 8787KJKJ3K4J3K4J3K4J3.mail@example.net
Date: Thu, 02 Sep 2004 12:31:03 -0500
Content
--part1_13d.2e68ed54_boundary--
| 
