MimeUtils ParseMessageId function not working as expected about mimekit

[jstedfast]

I would recommend sending a bug report to intheloop.io for malformating the message-id with 2 @ symbols.

There's very little value in changing the MineUtils.ParseMessageId() method to simply .TrimStart('<').TrimEnd('>') because you can do that yourself easily.

[lukapor]

I only give an example of msg id - this happens to one of our customer not in domain intheloop.io.

I already do workaround if I dont get parsed value I do trim as you suggested.

But this problem is also appears when we want to load eml file (eml contains header for example Message-ID: <00E19E93-513A-4A2B-964B-BB0372099DB6@@domain.si> ) into MimeMessage class.

MimeMessage property MessageId is null this I think is a bug. Other eml parser let say MailBee library parse this MessagId format.

I know that msg-id according RFC 2822 - @ is not valid in definition in dot-atom-text.

I know that workaround is also to check Headers is MessageId is null, but i think that we must get message id which is defined in eml. Maybe setter of unvalid msg-id should fail, but reading eml message id not.

[jstedfast]

Are all of the parse errors caused by "@@" being in the msg-id? Or are there other syntax errors causing the parse failures as well?

[jstedfast]

I can't understand why it's so hard for so many mass-mailers to get the syntax of a Message-ID correct.

Here's another example: issue #849

[vdona8]

Hi, I'm having a problem in fetching email same content like subject and body but different UID and Message-Id but in my inbox its only one, Resulting in Entry Duplication in Database because my checker to prevent duplicate entry is the two of them the UID or Message-Id