Re: [marf] Including Mail fields in IODEF

"Panos Kampanakis (pkampana)" <> Sun, 03 March 2013 22:37 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 60AC321F88C1; Sun, 3 Mar 2013 14:37:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -10.598
X-Spam-Status: No, score=-10.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id dr41mYSW0Zm7; Sun, 3 Mar 2013 14:37:04 -0800 (PST)
Received: from ( []) by (Postfix) with ESMTP id ABD5D21F88BF; Sun, 3 Mar 2013 14:37:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;;; l=21339; q=dns/txt; s=iport; t=1362350224; x=1363559824; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=iGg9gjCTBheDSlzIYA07Wu+PTPYqcVwwQVtlQrbxPY4=; b=XEOCIx1BhfoqyILmtpeXvrKsbuyhWGd4lujs9LRVTCUvtcLg1kUyq4Wd nug1b8HfYlv/EgKguQb1Q4SnfaShfICiOdViQgiuu5hUWoRW4gxtbf+B2 9RTH4H4lt9SNcNC9pVcWLRnNYmkVNcfxaLBU8EdxDgfHjNwV9oxoViSde w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos; i="4.84,774,1355097600"; d="scan'208,217"; a="183005571"
Received: from ([]) by with ESMTP; 03 Mar 2013 22:37:02 +0000
Received: from ( []) by (8.14.5/8.14.5) with ESMTP id r23Mb2Na007233 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sun, 3 Mar 2013 22:37:02 GMT
Received: from ([]) by ([]) with mapi id 14.02.0318.004; Sun, 3 Mar 2013 16:37:02 -0600
From: "Panos Kampanakis (pkampana)" <>
To: "Murray S. Kucherawy" <>
Thread-Topic: [marf] Including Mail fields in IODEF
Thread-Index: AQHOF+7Za9kyjHSIHUueKEyqFsBb8piUjOJQ
Date: Sun, 3 Mar 2013 22:37:01 +0000
Message-ID: <>
References: <> <> <> <> <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_1C9F17D1873AFA47A969C4DD98F98A75187BDAxmbrcdx10ciscocom_"
MIME-Version: 1.0
X-Mailman-Approved-At: Sun, 03 Mar 2013 19:43:10 -0800
Cc: "" <>, "" <>
Subject: Re: [marf] Including Mail fields in IODEF
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Message Abuse Report Format working group discussion list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Sun, 03 Mar 2013 22:37:09 -0000

Thank you Murray.

The "<arf:EmailMessage>
   Received: from
        ( [])
        by with ESMTP id M63d4137594e46;
        Thu, 08 Mar 2005 14:00:00 -0400
   From: &lt;;
   To: &lt;Undisclosed Recipients&gt;
   Subject: Earn money
   MIME-Version: 1.0
   Content-type: text/plain
   Date: Thu, 02 Sep 2004 12:31:03 -0500

   Spam Spam Spam
   Spam Spam Spam
   Spam Spam Spam
   Spam Spam Spam

that I see in looks like just an email message. I don't see "feedback-type" or other ARF fields for example that would make it a ARF.

draft-vesely-mile-mail-abuse-00.txt seems to define a header and then have the option for the actual message (EmailMessage). Am I reading it wrong?


From: Murray S. Kucherawy []
Sent: Sunday, March 03, 2013 4:10 AM
To: Panos Kampanakis (pkampana)
Cc: Moriarty, Kathleen;;
Subject: Re: [marf] Including Mail fields in IODEF

The issue with MARF inside IODEF is that the receiver needs to know that the payload being provided inside an EmailMessage element is itself an ARF report, and not the message that caused the report in the first place.  You certainly could crack open the EmailMessage content and see if conforms to the ARF specification to tell which kind of report you've gotten, but that seems inelegant.
I suppose then another option is an extension element that indicates you've received an ARF payload rather than the actual offending message.

Also of note: An ARF can contain the offending message or only the offending message's header, and still be compliant.  If your application needs the whole message, you'll have to add some additional stipulations someplace.

On Fri, Mar 1, 2013 at 1:52 PM, Panos Kampanakis (pkampana) <<>> wrote:
I think MARF provides more functionality and should be leverage for emails in IODEF.
I also think we need to resurrect within MILE since MARF was concluded..

-----Original Message-----
From:<> [<>] On Behalf Of Moriarty, Kathleen
Sent: Thursday, February 21, 2013 5:19 AM
Subject: [mile] Including Mail fields in IODEF


Cross posting with MAIL and MARF -

In MILE related work, I have come across use cases that would like to include DKIM and SPF information in addition to specific mail fields (like the ones Chris lists below).  We would like some help to figure out the best approach.  Should we embed ARF and MARF RFC extensions to accommodate this need or should we look at updating RFC5901?  Both take the approach of including an email message as opposed to using XML to tag each field and allow for this in the data model (in my opinion, that is fine and reduces bloat, but there may be other opinions).

There was a draft published last year (link included below) that includes MARF in an IODE extension.

From: Harrington, Christopher
Sent: Wednesday, February 20, 2013 2:57 PM
To: Moriarty, Kathleen;<>
Subject: RE: Mail fields

I'm for the simplest solution as always. These are the indicator types that we routinely share. I would use these as a base:

Email address (denoting if it is to or from) Email Subject Email attachment name Email attachment hash X-Mailer (from header) Hyperlink in email

It's also very common to share the whole header. Bad guys routinely forge them and put extra header items that can be used as indicators.  Although not an indicator sharing the entire email as an .eml or .msg file is also pretty common.



-----Original Message-----
From:<> [<>] On Behalf Of Moriarty, Kathleen
Sent: Wednesday, February 20, 2013 2:58 AM
Subject: [mile] Mail fields


In looking at the updated rfc5070bis and coming across some requests for handling certain types of exchanges, I am curious to hear how others think we should handle mail related indicators and incidents.  A couple of commonly exchanged fields were added into the Record class.  You can still extend out using RFC5901 and include a full mail message, but if you wanted to include DKIM or Sender Policy Framework, you need something else.  The IETF group MARF already solved these issues.

MARF uses the email tags rather than XML and there was a draft that embedded MARF content into IODEF (contains an example), can be found here:

Since mail is already marked and can be parsed, would this be a better option to use what MARF has already done to solve the question on how to exchange this data?  Other options would be to update RFC5901 or to extend IODEF further.  I prefer the use of MARF.  It is already in use by mail operators, so there is adoption.

mile mailing list<>
mile mailing list<>
marf mailing list<>