[issue13955] email: RFC 2822 has been obsoleted by RFC 5322

2012-02-12 Thread R. David Murray
R. David Murray added the comment: Hmm. I misread this. You are, in fact correct, but I don't think there is anything comprehensive to do here. As I make changes and have actually checked then against RFC 5322, I'm either changing or adding that RFC number to the comments and docs. --

[issue13955] email: RFC 2822 has been obsoleted by RFC 5322

2012-02-06 Thread R. David Murray
R. David Murray added the comment: 5322 is still a draft, according to the IETF. That said, we are paying attention to 5322. -- nosy: +r.david.murray resolution: -> invalid stage: -> committed/rejected status: open -> closed ___ Python tracker

[issue13955] email: RFC 2822 has been obsoleted by RFC 5322

2012-02-06 Thread Tshepang Lekhonkhobe
Changes by Tshepang Lekhonkhobe : -- nosy: +tshepang ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mai

[issue13955] email: RFC 2822 has been obsoleted by RFC 5322

2012-02-06 Thread Samuel Bronson
New submission from Samuel Bronson : As you can see by looking at or , RFC 2822 has been obsoleted by RFC 5322. It would probably be a good idea to update the email package to support it, if in fact anything needs changin