On Fri, 3 May 2002, Daniel Pittman wrote: > SpamAssassin, at least, should be scanning inline parts no matter > their depth in the hierarchy. Attachment parts probably only want > scanning when they are the only, or first, part in a message.
Given a multipart/related part, any part that is referred to by CID from within the part identified by the start= parameter, should be examined. Given any of multipart/alternative, multipart/mixed, or multipart/parallel there's no way to determine which part(s) an MUA might decide to display. You can probably skip those with "Content-Disposition: attachment", but the absence of "inlne" is not an indicator. (I've seen an MUA that will display any HTML part and leave the text parts as attachments, even in a multipart/mixed and regardless of the order in which they appear.) So the best idea is to scan them unless the content-type indicates that wouldn't be fruitful. Then apply the above recursively to nested multiparts, and be sure it works for message/rfc822 subparts (including messages whose top-level content-type is message/rfc822). _______________________________________________________________ Have big pipes? SourceForge.net is looking for download mirrors. We supply the hardware. You get the recognition. Email Us: [EMAIL PROTECTED] _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
