Re: [Email-SIG] Some parsing/generation issues of email in Python 3

2016-06-08 Thread Hans-Peter Jansen
On Mittwoch, 8. Juni 2016 10:14:16 Barry Warsaw wrote: > On Jun 08, 2016, at 11:56 AM, Hans-Peter Jansen wrote: > >All these issues were harvested in less than halve an hour. What really > >troubles me is the quietness around here in the light of this experience. > >Doesn't

[Email-SIG] Some parsing/generation issues of email in Python 3

2016-06-08 Thread Hans-Peter Jansen
Dear audience, when coming back to this list, I couldn't believe my eyes because of the low volume level, but after rechecking with the archives, I have to accept, it is that quiet here, a bit too quiet from my POV. Hmm. Well, I'm in the course of replacing a special purpose postfix email

Re: [Email-SIG] Some parsing/generation issues of email in Python 3

2016-06-12 Thread Hans-Peter Jansen
Hi Matt, thanks for your hints. On Sonntag, 12. Juni 2016 13:01:13 Matthew Dixon Cowles wrote: > Pete, > > > Note, that the subject line is missing. In my real filter, it left > > the current execution frame, and execution continued one or two > > level up the stack. > > The only thing I've

Re: [Email-SIG] Some parsing/generation issues of email in Python 3

2016-06-10 Thread Hans-Peter Jansen
On Donnerstag, 9. Juni 2016 18:37:54 Hans-Peter Jansen wrote: > On Mittwoch, 8. Juni 2016 10:37:41 R. David Murray wrote: > > Right, in my previous note I was talking about people not using the > > new policies. The compat32 code is probably being used by a lot of >

Re: [Email-SIG] Some parsing/generation issues of email in Python 3

2016-06-09 Thread Hans-Peter Jansen
On Mittwoch, 8. Juni 2016 10:37:41 R. David Murray wrote: > > Right, in my previous note I was talking about people not using the > new policies. The compat32 code is probably being used by a lot of > people and seems to be working well, including having fixed some header > parsing and folding