Message-IDs are required to have a specific format which is a subset of an email address and to be globally unique. That is, no two different messages must ever have the same Message-ID. A common technique used by many message systems is to use a time and date stamp along with the local host's domain name, e.g., email@example.com. On the other hand, if two messages have the same Message-ID, they are presumed to be the same one and one version is discarded. But, as Google MTAs (message transfer agents) mangle the badly formed ones of Outlook, several same messages may coexist with original and mangled ones and create problems in referencing each other for threading.
Mails to public mailing-lists can be found via their Message-ID by using links from various services:
http://mid.gmane.org/alpine.BSF.firstname.lastname@example.org https://marc.info/?i=Prayer.email@example.com http://firstname.lastname@example.org https://www.freebsd.org/cgi/mid.cgi?db=mid&id=199802242058.MAA24843@monk.via.net https://lists.debian.org/msgid-search/20050606213954.GC884@finlandia.infodrom.north.de http://lists.debconf.org/cgi-lurker/keyword.cgi?doc-url=/lurker&format=en.html&query=id:email@example.com https://www.w3.org/mid/alpine.BSF.firstname.lastname@example.org http://email@example.com
- RFC 2392 Content-ID and Message-ID Uniform Resource Locators
- RFC 2111 Content-ID and Message-ID Uniform Resource Locators (Obsolete)
- RFC 5322 Internet Message Format
- Recommendations for generating Message IDs
|This Internet-related article is a stub. You can help Wikipedia by expanding it.|