The "HexEncodeMessageID" that you link to (and this happens in links such as https://mail.google.com/mail/#inbox/14197d2548c9da1a ), unfortunately, differs from the RFC822 message identifier (which happens in the message source).
I donβt know how to get a direct email link using RFC822 message id, but you can find the specific RFC822 message id in Gmail (see GMail doc ):
in:anywhere rfc822msgid:SomeID@SomeID.mail
You can turn this into a link:
https://mail.google.com/mail/#search/in%3Aanywhere+rfc822msgid%3ASomeID@SomeID.mail
(Remember that the message identifier must be URL-encoded . You can also just enter a search in your GMail and copy the resulting URL afterwards.)
The problem with this link is that it does not send you directly to the mail, but to the search results page with one hit. But this may be good enough for some applications.
Benefit: RFC822 is the same in your account and the sender's account. Therefore, if you want to refer to this letter in an email / chat, you can specify this link for the search (provided that the recipient also uses GMail). With "HexEncodeMessageID" this will not work, because in each account it is different from the others (according to my own experiments).
Last: the link only works when you are already logged in.
Dominique unruh
source share