This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author vinay.sajip
Recipients vinay.sajip, zmk
Date 2012-03-30.18:32:55
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1333132375.71.0.659324104618.issue14452@psf.upfronthosting.co.za>
In-reply-to
Content
> the RFC specifies that the BOM should prefix only unstructured
> message part, but current Python implementation puts it in the
> middle of structured part, thus confusing RFC-compliant receivers.

How do you work that out? The implementation puts the BOM before the message part:

        prio = '<%d>' % self.encodePriority(...)
        prio = prio.encode('utf-8')
        msg = msg.encode('utf-8')
        if codecs:
            msg = codecs.BOM_UTF8 + msg
        msg = prio + msg

Perhaps I've misunderstood you or the RFC5424, but I don't quite see how. I'll mark this as "pending" and "invalid" awaiting a clarification from you (ideally with a specific example).
History
Date User Action Args
2012-03-30 18:32:55vinay.sajipsetrecipients: + vinay.sajip, zmk
2012-03-30 18:32:55vinay.sajipsetmessageid: <1333132375.71.0.659324104618.issue14452@psf.upfronthosting.co.za>
2012-03-30 18:32:55vinay.sajiplinkissue14452 messages
2012-03-30 18:32:55vinay.sajipcreate