{"id":1636,"date":"2011-01-05T23:40:10","date_gmt":"2011-01-05T21:40:10","guid":{"rendered":"http:\/\/www.limilabs.com\/blog\/?p=1636"},"modified":"2015-02-17T14:25:48","modified_gmt":"2015-02-17T12:25:48","slug":"unique-id-in-pop3-protocol","status":"publish","type":"post","link":"https:\/\/www.limilabs.com\/blog\/unique-id-in-pop3-protocol","title":{"rendered":"Unique ID in POP3 protocol"},"content":{"rendered":"<p>RFC 1939 specification says:<\/p>\n<p><em>&#8220;The unique-id of a message is an arbitrary server-determined string, [&#8230;], which uniquely identifies a message within a maildrop and which persists across sessions.&#8221;<\/em><\/p>\n<p><em>&#8220;The server <strong>should<\/strong> never reuse an unique-id in a given maildrop, for as long as the <strong>entity using the unique-id exists<\/strong>.&#8221;<\/em><\/p>\n<p>So in theory if the email is deleted server may reuse the same unique-id.<\/p>\n<p><em>&#8220;While it is generally preferable for server implementations to store arbitrarily assigned unique-ids in the maildrop, this specification is intended to permit unique-ids to be calculated as a hash of the message.<\/em><\/p>\n<p><em>Clients should be able to handle a situation where two identical copies of a message in a maildrop have the same unique-id.&#8221;<\/em><\/p>\n<p>Mail.dll will not throw exception in such case, but please note, that internally Mail.dll uses dictionaries to store unique-ids and Pop3.GetAll() method will not return duplicates.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>RFC 1939 specification says: &#8220;The unique-id of a message is an arbitrary server-determined string, [&#8230;], which uniquely identifies a message within a maildrop and which persists across sessions.&#8221; &#8220;The server should never reuse an unique-id in a given maildrop, for as long as the entity using the unique-id exists.&#8221; So in theory if the email [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[4],"tags":[33,42],"class_list":["post-1636","post","type-post","status-publish","format-standard","hentry","category-mail-dll","tag-email-component","tag-pop3"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.limilabs.com\/blog\/wp-json\/wp\/v2\/posts\/1636"}],"collection":[{"href":"https:\/\/www.limilabs.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.limilabs.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.limilabs.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.limilabs.com\/blog\/wp-json\/wp\/v2\/comments?post=1636"}],"version-history":[{"count":5,"href":"https:\/\/www.limilabs.com\/blog\/wp-json\/wp\/v2\/posts\/1636\/revisions"}],"predecessor-version":[{"id":4902,"href":"https:\/\/www.limilabs.com\/blog\/wp-json\/wp\/v2\/posts\/1636\/revisions\/4902"}],"wp:attachment":[{"href":"https:\/\/www.limilabs.com\/blog\/wp-json\/wp\/v2\/media?parent=1636"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.limilabs.com\/blog\/wp-json\/wp\/v2\/categories?post=1636"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.limilabs.com\/blog\/wp-json\/wp\/v2\/tags?post=1636"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}