Nicolas Estibals nicolas.estib...@gmail.com added the comment:
Thanks for your help and the interesting discussion with this issue.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue12147
___
Roundup Robot devnull@devnull added the comment:
New changeset 0f5ea42fb46c by R David Murray in branch '3.2':
#12147: make send_message correctly handle Sender and Resent- headers.
http://hg.python.org/cpython/rev/0f5ea42fb46c
New changeset b8cec4f3faaa by R David Murray in branch 'default':
R. David Murray rdmur...@bitdance.com added the comment:
I tweaked the patch a bit (mostly style/cosmetic) and added some additional
tests. Thanks, Nicolas!
--
resolution: - fixed
stage: patch review - committed/rejected
status: open - closed
___
Nicolas Estibals nicolas.estib...@gmail.com added the comment:
Sorry for the late, my week-end was more busy than expected. Here is the
corrected version of the patch.
--
Added file: http://bugs.python.org/file22511/send_message_rfc2822_v2.patch
___
Nicolas Estibals nicolas.estib...@gmail.com added the comment:
Hi,
Treating this as a bug is a good news, if we don't user of the function will
ask for python 3.3
I also think the part concerning the Sender header is pretty clear and we can
fix it easily.
About the Resent-* fields, I'm not
R. David Murray rdmur...@bitdance.com added the comment:
Section 3.6.6 says:
Resent fields are strictly informational. They MUST NOT be used in
the normal processing of replies or other such automatic actions on
messages.
Further, since there is no specified order for the headers
R. David Murray rdmur...@bitdance.com added the comment:
Note that that RFC language is clearly directed at automatic processing on
*receipt*, not during sending. The RFC doesn't address automatic processing
during sending, it leaves that the to the SMTP RFC.
--
Nicolas Estibals nicolas.estib...@gmail.com added the comment:
I wasn't aware of the problem of guessing which are the correct Resent-* field,
tthis does not seem to be that easy, however taking only the first one should
be a good heuristic for next release.
I think we now agree on the
R. David Murray rdmur...@bitdance.com added the comment:
I think we can treat this as a bug. However...
What if there is more than one set of Resent- headers? I think that it is not
possible to guarantee we only look at the most recent set, since the RFC
provides no way to identify a set.
New submission from Nicolas Estibals nicolas.estib...@gmail.com:
smtplib.send_message permits to send messages that are in python Message
representation by selecting smtp's from and to in the message headers. Most
of the time the implementation is correct but if the message is bounced
Changes by Jesús Cea Avión j...@jcea.es:
--
nosy: +jcea
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue12147
___
___
Python-bugs-list mailing list
R. David Murray rdmur...@bitdance.com added the comment:
Thanks for the patch. Adding support for this is a good idea. There could be
a question about whether this constitutes a bug fix or a feature; I'll canvass
some other devs and see if we have a consensus on it.
It may take me a bit to
Changes by R. David Murray rdmur...@bitdance.com:
--
assignee: - r.david.murray
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue12147
___
___
13 matches
Mail list logo
