Kirill Elagin added the comment:
Ah, I’m so dumb. Of course the tests work as there are multiple addresses but
still just one field.
Here is the test for multiple fields.
--
Added file: http://bugs.python.org/file39263/multiple_fields_test.patch
R. David Murray added the comment:
Ah, but that is intentional. Those fields can only appear once per message,
per the RFC. The new email API will raise an error if you attempt to add them
more than once. Perhaps we should raise an error instead of ignoring the
duplicates, given that we
Kirill Elagin added the comment:
Oh, I see now.
It is a good idea to raise an error either in `send_message` or at the moment
when a second `To`/`Cc`/`Bcc` header is added to the message.
--
resolution: - not a bug
status: open - closed
___
Python
R. David Murray added the comment:
Can you write a test that shows the failure? There is an existing test that
demonstrates sending to multiple addresses (testSendMessageWithAddresses), so
you must have found an edge case that isn't tested. (Either that, or the
existing test is broken.)
Changes by Ned Deily n...@acm.org:
--
nosy: +barry, r.david.murray -ned.deily
stage: - patch review
versions: +Python 3.5
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue24066
___
Kirill Elagin added the comment:
x_x
--
keywords: +patch
Added file: http://bugs.python.org/file39219/multiple_to.patch
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue24066
___
New submission from Kirill Elagin:
If I have a message with multiple `To` headers and I send it using
`send_message` not specifying `to_addrs`, the message gets sent only to one of
the recipients.
I’m attaching my patch that makes it send to _all_ the addresses listed in
`To`, `Cc` and
Ned Deily added the comment:
Kirill, the patch is missing.
--
nosy: +ned.deily
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue24066
___
___
