You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I'm trying to send an email where multiple attachments with the same name, the receiver thinks that it is always the same attachment and shows the same content for all attached files.
I have tested this with versions 6.5.2 and 8.3.1.
In my opinion, the problem is the assignment of the BodyPart ID in org.simplejavamail.converter.internal.mimemessage.MimeMessageHelper.getBodyPartFromDatasource(AttachmentResource, String) (line 288) where the Content-ID header of the part is based solely on the filename of the attachment. I suggest to always add a UUID at the end to ensure uniqueness.
The text was updated successfully, but these errors were encountered:
…h identical names don't refer to the same content
bbottema
changed the title
Multiple attachments with same name get the same Content-ID
Multiple attachments with same name get the same Content-ID, causing them to refer to the same file content
Nov 26, 2023
bbottema
changed the title
Multiple attachments with same name get the same Content-ID, causing them to refer to the same file content
Bug: Multiple attachments with same name get the same Content-ID, causing them to refer to the same file content
Nov 26, 2023
When I'm trying to send an email where multiple attachments with the same name, the receiver thinks that it is always the same attachment and shows the same content for all attached files.
I have tested this with versions 6.5.2 and 8.3.1.
In my opinion, the problem is the assignment of the BodyPart ID in
org.simplejavamail.converter.internal.mimemessage.MimeMessageHelper.getBodyPartFromDatasource(AttachmentResource, String)
(line 288) where the Content-ID header of the part is based solely on the filename of the attachment. I suggest to always add a UUID at the end to ensure uniqueness.The text was updated successfully, but these errors were encountered: