It appears that Brotman, Alex <[email protected]> said: >* Section 2.6.2 says the message has to comply with both RFC5322 and RFC2045. >What's going on here? Why is it required to be MIME? >Could it not be a plain message that happens to contain XML? Or are we trying >to say there has to be a text/xml part that contains >the report, and maybe other parts that provide additional information for >humans? This question might be answered by the next >paragraph, in which case this might just need some copy editing. > >I feel like I’m reading this is meant to be an attachment with that specified >type, but isn’t explicitly stated. I’m not >sure if that’s the expectation of others on the list. > >This is what I thought, but it's not really stated clearly. If we're both >right, I think we should be explicit that the report is >expected to be in a MIME-encoded text/xml part (if uncompressed) or >application/gzip (if compressed), and the remaining MIME >structure of the message is at the discretion of the generator; the only thing >the receiver cares about is that one part. > >I’ll make this more explicit as being expected to be an attachment.
It needs to be a MIME part of application/gzip. It would be OK if that were the only part in the message rather than an attachment so long as it's got the proper type. In practice you have to sniff the attachments since some are still ZIP even though they say application/gzip or vice versa but let's not go there. R"s, John _______________________________________________ dmarc mailing list -- [email protected] To unsubscribe send an email to [email protected]
