[MGNLMAIL-76] Unique Content-ID for mail attachments Created: 08/Sep/16  Updated: 03/Aug/18

Status: Open
Project: Magnolia Mail Module
Component/s: None
Affects Version/s: 5.3
Fix Version/s: None

Type: Improvement Priority: Neutral
Reporter: Diana Racho Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Date of First Response:

 Description   

According to RFC 2392 Content-ID of every attachment has to be unique.

https://tools.ietf.org/html/rfc2392

Currently only the name of the attachement field is used for Content-ID.



 Comments   
Comment by Viet Nguyen [ 03/Aug/18 ]

According to your RFC:

A "mid" URL with only a "message-id" refers to an entire message.
With the appended "content-id", it refers to a body part within a
message, as does a "cid" URL. The Content-ID of a MIME body part is
required to be globally unique. However, in many systems that store
messages, body parts are not indexed independently their context
(message). The "mid" URL long form was designed to supply the
context needed to support interoperability with such systems.

--> then this's not a mandatory requirement. Systems still working without this 'unique' feature for years so let's put this to improvement backlog.

Generated at Mon Feb 12 06:03:24 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.