Author r.david.murray
Recipients abhilash.raj, ajaksu2, barry, christian.heimes, etiffany, moijes12, r.david.murray
Date 2014-06-05.15:30:30
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1401982230.95.0.868106516804.issue634412@psf.upfronthosting.co.za>
In-reply-to
Content
No, there is no requirement that attachment names be unique, and in fact no requirement that attachments (inline attachments, which is mostly what we are dealing with for 'related') have names at all.  I have seen messages in the wild that had more than one attachment with the same name, and it revealed a bug in the system I was working on at the time :)

Building the dictionary is not *hard*.  I am not satisfied with the code shown in 
 
  https://docs.python.org/3/library/email-examples.html#examples-using-the-provisional-api

I think there should be a more elegant way to spell the multipart/related creation parts of that example.  Feeding a dictionary in as the entire 'related' part would be better, but in order to create that dictionary you have to explicitly create MIMEPart subparts and store them in the dict.  That may be what we end up doing, but I think it would be nice if there was a more intuitive way to spell it.  

Especially since as it stands you have to explicitly munge the CIDs.  You shouldn't have to do that, the library should take care of that for you.
History
Date User Action Args
2014-06-05 15:30:31r.david.murraysetrecipients: + r.david.murray, barry, christian.heimes, ajaksu2, etiffany, moijes12, abhilash.raj
2014-06-05 15:30:30r.david.murraysetmessageid: <1401982230.95.0.868106516804.issue634412@psf.upfronthosting.co.za>
2014-06-05 15:30:30r.david.murraylinkissue634412 messages
2014-06-05 15:30:30r.david.murraycreate