Received: from mrout3.yahoo.com (mrout3.yahoo.com [216.145.54.173]) by sb7.songbird.com (8.12.11/8.12.11) with ESMTP id k18NqeOK022883 for ; Wed, 8 Feb 2006 15:52:40 -0800 Received: from [66.228.167.95] (jdfalk-mac.corp.yahoo.com [66.228.167.95]) by mrout3.yahoo.com (8.13.4/8.13.4/y.out) with ESMTP id k18NnXpM013763 for ; Wed, 8 Feb 2006 15:49:34 -0800 (PST) DomainKey-Signature: a=rsa-sha1; s=serpent; d=yahoo-inc.com; c=nofws; q=dns; h=message-id:date:from:organization:user-agent:mime-version:to: subject:references:in-reply-to:content-type:content-transfer-encoding; b=F77omR5FpMKw6o9zKKhLr3un3Oqv0jOCe+WWFHe4h87rpgG3MS5OaD6d6QVrCCYC Message-ID: <43EA838A.1000503@yahoo-inc.com> Date: Wed, 08 Feb 2006 15:49:30 -0800 From: "J.D. Falk" Organization: Yahoo! User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.12) Gecko/20050923 Thunderbird/1.0.7 Mnenhy/0.6.0.104 MIME-Version: 1.0 To: abuse-feedback-report@mipassoc.org Subject: Re: [feedback-report] MIME question References: <43EA769D.7050307@yahoo-inc.com> <86A65657-96C5-474D-BD9F-9FFA2192D198@SKYLIST.net> In-Reply-To: <86A65657-96C5-474D-BD9F-9FFA2192D198@SKYLIST.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-SongbirdInformation: support@songbird.com for more information X-Songbird: Found to be clean X-Songbird-From: jdfalk@yahoo-inc.com X-BeenThere: abuse-feedback-report@mipassoc.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Public forum for discussion on the feedback-report draft List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Feb 2006 23:53:00 -0000 On 2006-02-08 15:14, Ian Ragsdale wrote: > It depends on what parser and how they use it. > > Assuming they recursively descend into any multipart part of the > message, then yes. An ARF message is easily recognizable as a > multipart message (content-type of "multipart/report"), so if they > don't completely ignore multipart types that they don't recognize > then they should find it. Most parsers that I've worked with make it > easy to treat all multipart parts the same way, so I'd say that it's > pretty likely. So, the statement "most MIME parsers should be able to read ARF without extra development work" would be valid. Sweet. -- J.D. Falk, Anti-Spam Product Manager Yahoo! Communications Platform Team Received: from mail.skylist.com (mail.skylist.net [69.56.15.206]) by sb7.songbird.com (8.12.11/8.12.11) with ESMTP id k18NFsoa018427 for ; Wed, 8 Feb 2006 15:15:54 -0800 X-Spam-Checker-Version: SpamAssassin 2.64 (2004-01-11) on mail.skylist.net X-Spam-Status: No, hits=-4.9 required=5.0 tests=BAYES_00 autolearn=ham version=2.64 X-Spam-Level: X-TFF-CGPSA-Version: 1.3.2 X-TFF-CGPSA-Filter: Scanned Received: from [64.20.226.11] (account ian.ragsdale@skylist.com HELO [64.20.226.11]) by mail.skylist.com (CommuniGate Pro SMTP 4.3) with ESMTPSA id 35137712; Wed, 08 Feb 2006 17:14:56 -0600 In-Reply-To: <43EA769D.7050307@yahoo-inc.com> References: <43EA769D.7050307@yahoo-inc.com> Mime-Version: 1.0 (Apple Message framework v746.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <86A65657-96C5-474D-BD9F-9FFA2192D198@SKYLIST.net> Content-Transfer-Encoding: 7bit From: Ian Ragsdale Subject: Re: [feedback-report] MIME question Date: Wed, 8 Feb 2006 17:14:54 -0600 To: "J.D. Falk" X-Mailer: Apple Mail (2.746.2) X-SongbirdInformation: support@songbird.com for more information X-Songbird: Found to be clean X-Songbird-From: ian@skylist.net Cc: abuse-feedback-report@mipassoc.org X-BeenThere: abuse-feedback-report@mipassoc.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Public forum for discussion on the feedback-report draft List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Feb 2006 23:15:57 -0000 It depends on what parser and how they use it. Assuming they recursively descend into any multipart part of the message, then yes. An ARF message is easily recognizable as a multipart message (content-type of "multipart/report"), so if they don't completely ignore multipart types that they don't recognize then they should find it. Most parsers that I've worked with make it easy to treat all multipart parts the same way, so I'd say that it's pretty likely. Ian On Feb 8, 2006, at 4:54 PM, J.D. Falk wrote: > Here's where I show that I still don't entirely grok MIME. > > Say somebody writes a parser that looks for a message/rfc822 part > in a report, and ignores any other MIME types. If they get an ARF > report, will that parser be able to continue to pull out the rfc822 > part and ignore the new ARF stuff without any new logic? > Received: from m.wordtothewise.com (goliath.word-to-the-wise.com [208.187.80.130]) by sb7.songbird.com (8.12.11/8.12.11) with ESMTP id k18NC3Ob017874 for ; Wed, 8 Feb 2006 15:12:03 -0800 Received: from [10.3.2.16] (184.word-to-the-wise.com [208.187.80.184]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by m.wordtothewise.com (Postfix) with ESMTP id 4C20DFF96 for ; Wed, 8 Feb 2006 15:11:24 -0800 (PST) Mime-Version: 1.0 (Apple Message framework v746.2) In-Reply-To: <43EA769D.7050307@yahoo-inc.com> References: <43EA769D.7050307@yahoo-inc.com> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Steve Atkins Subject: Re: [feedback-report] MIME question Date: Wed, 8 Feb 2006 15:11:23 -0800 To: abuse-feedback-report@mipassoc.org X-Mailer: Apple Mail (2.746.2) X-SongbirdInformation: support@songbird.com for more information X-Songbird: Found to be clean X-Songbird-From: steve@word-to-the-wise.com X-BeenThere: abuse-feedback-report@mipassoc.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Public forum for discussion on the feedback-report draft List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Feb 2006 23:12:10 -0000 On Feb 8, 2006, at 2:54 PM, J.D. Falk wrote: > Here's where I show that I still don't entirely grok MIME. > > Say somebody writes a parser that looks for a message/rfc822 part > in a report, and ignores any other MIME types. If they get an ARF > report, will that parser be able to continue to pull out the rfc822 > part and ignore the new ARF stuff without any new logic? Yes. (In the field, though, some scomp parsers don't really handle MIME, rather they get overly chummy with the specific details of the message). Cheers, Steve Received: from mrout3.yahoo.com (mrout3.yahoo.com [216.145.54.173]) by sb7.songbird.com (8.12.11/8.12.11) with ESMTP id k18MufKC015867 for ; Wed, 8 Feb 2006 14:56:41 -0800 Received: from [66.228.167.95] (jdfalk-mac.corp.yahoo.com [66.228.167.95]) by mrout3.yahoo.com (8.13.4/8.13.4/y.out) with ESMTP id k18MsOEg095440 for ; Wed, 8 Feb 2006 14:54:24 -0800 (PST) DomainKey-Signature: a=rsa-sha1; s=serpent; d=yahoo-inc.com; c=nofws; q=dns; h=message-id:date:from:organization:user-agent:mime-version:to: subject:content-type:content-transfer-encoding; b=rZKDSG9dwhM4opEhq3h8HkMfhdREUa82Wsii2gLOYrp9ZkwLDdFExH5ZF5RZ8dWr Message-ID: <43EA769D.7050307@yahoo-inc.com> Date: Wed, 08 Feb 2006 14:54:21 -0800 From: "J.D. Falk" Organization: Yahoo! User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.12) Gecko/20050923 Thunderbird/1.0.7 Mnenhy/0.6.0.104 MIME-Version: 1.0 To: abuse-feedback-report@mipassoc.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-SongbirdInformation: support@songbird.com for more information X-Songbird: Found to be clean X-Songbird-From: jdfalk@yahoo-inc.com Subject: [feedback-report] MIME question X-BeenThere: abuse-feedback-report@mipassoc.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Public forum for discussion on the feedback-report draft List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Feb 2006 22:57:00 -0000 Here's where I show that I still don't entirely grok MIME. Say somebody writes a parser that looks for a message/rfc822 part in a report, and ignores any other MIME types. If they get an ARF report, will that parser be able to continue to pull out the rfc822 part and ignore the new ARF stuff without any new logic? -- J.D. Falk, Anti-Spam Product Manager Yahoo! Communications Platform Team