for me a unique identifier can be generated as follows:
key: epoch time of mail (from date field)
But at the same time, the user can receive several letters.
key: epoch time of mail + MailSize
At a certain time, the receiver identifier can receive different letters of the same size
KEY: epoch time of mail + MailSize + Recieveing ββIP address of the server (can be obtained from the field: received):
At a certain time, the receiver identifier can receive different messages of the same size from the same ip.
key: epoch time of mail + MailSize + Recieveing ββIP address of the server (can receive from the received: field) + md5sum mail.
The duplication possibility for this key is very very low.
The message identifier is usually the identifier of the device that sent the message, or it may be something else, it depends entirely on the domain and may be the same for different letters and may not exist at all.
uid is what the imap server monitors for mail identity. but if the mail was deleted or moved between them, as well as the server code, it is possible that other mail can be assigned with the same uid.
Anshul
source share