Michal Sladek mic...@sladkovi.eu added the comment:
Changing code to:
encodedSubject = '=?utf-8?b?{0}?='.format(base64Subject)
still works properly with smtp.seznam.cz server
--
___
Python tracker rep...@bugs.python.org
R. David Murray rdmur...@bitdance.com added the comment:
I think the next thing to do would be to replace the call to send_message with
code that calls BytesGenerator to write the message out to disk, and diff the
output of the two versions (normal subject and hand-encoded subject). Maybe
Martin v. Löwis mar...@v.loewis.de added the comment:
I digged a little bit further. The data being sent is
'Content-Type: multipart/mixed;
boundary1981330074035035012==\r\nMIME-Version: 1.0\r\nFrom:
rzro...@seznam.cz\r\nTo: msla...@volny.cz\r\nSubject:
Martin v. Löwis mar...@v.loewis.de added the comment:
I also attach a stand-alone version. To run this locally, run
smtpdX.Y.py -dn localhost:2525
--
Added file: http://bugs.python.org/file24844/a.py
___
Python tracker rep...@bugs.python.org
R. David Murray rdmur...@bitdance.com added the comment:
OK, got it. When I created BytesParser I turned the 'NL' constant into a class
attribute, but in the line that handles Header objects in BytesParser I failed
to change NL to self._NL. So when send_message calls flatten with
Roundup Robot devn...@psf.upfronthosting.co.za added the comment:
New changeset d0bf40ff20ef by R David Murray in branch '3.2':
#14062: fix BytesParser handling of linesep for Header objects
http://hg.python.org/cpython/rev/d0bf40ff20ef
New changeset 7617f3071320 by R David Murray in branch
R. David Murray rdmur...@bitdance.com added the comment:
Thanks for the bug report. I thought we had tests for processing Header
objects when serializing a message using BytesParser, but clearly we didn't.
And thanks Tatiana and Martin for issue review and testing.
--
resolution: -
Tatiana Al-Chueyr tatiana.alchu...@gmail.com added the comment:
Hi msladek!
I tried to reproduce your bug using Python 3.2.2 on MacOS X, but didn't manage
- all worked fine. I used gmail both to send and receive the message, on SSL:
smtpPort = '465'
smtpSrv = 'smtp.gmail.com'
As I'm
Michal Sladek mic...@sladkovi.eu added the comment:
I tested the code again. Using Gmail SMTP server produces correct results,
using server smtp.seznam.cz leads to a problem (I should mention here, that
Seznam is the largest free mail provider in the Czech Republic). Here are the
differences
R. David Murray rdmur...@bitdance.com added the comment:
It makes no sense that changing how Subject is generated would affect the later
formatting of the mime header. There is no coupling that I'm aware of in the
code.
I notice that your handcrafted version uses uppercase for the charset
New submission from Michal Sladek mic...@sladkovi.eu:
Hello!
I think there is a problem when adding UTF-8 subject to email message. I wrote
following function (its code is based on examples I found in offical docs)
which should send an email with UTF-8 subject, UTF-8 plain text body and
Changes by Martin v. Löwis mar...@v.loewis.de:
--
nosy: +loewis
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue14062
___
___
Python-bugs-list
Changes by Éric Araujo mer...@netwok.org:
--
nosy: +r.david.murray
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue14062
___
___
Python-bugs-list
13 matches
Mail list logo
