Simple feature request that will never happen: All Internet emails have a GUID field, and all users who have a copy of a unique message have that one GUID for it.
Why can't there by an "email:$MessageId" URI scheme and why can't Outlook handle these URIs with 1) open that message if I have it; or 2) "You did not receive that message."
I've looked into part of this before. Outlook has message URLs, specific to YOUR database, and they break if you move a message to another folder. Useless.
Obvious use-case: "Did you get that memo? Here's the URI."
@progo
The issue then comes if you never recieved the original email, but had it forwarded to you...
You would want your clients to also check the References and In-Reply-To headers as a fallback.
@everlastingrocks yeah, forward as new text screws it all up. Good point.
@everlastingrocks Does "forward as new message" usually have a header referencing the original message ID? It'd make sense if it did but I wasn't aware of it.
@everlastingrocks I wish I was allowed and enabled to use Thunderbird at work. :^( I'm sure I could program this for my own use, in Thunderbird, in a weekend or less.
@everlastingrocks They do not trust me to run my own software. My "new" laptop has been in purgatory for 4 months because I refuse to sign the local sysadmin privileges user agreement from Infosec.
Mixed in this document is a requirement that all employees with local assigned-laptop admin access MUST get permission for every installed piece of software from the head of Infosec.
This is not how FOSS works not how software developers work. The rest of my department signed and disregarded it.
@everlastingrocks I attempted to negotiate. (The actual policy signing refusal started over a year ago.) No one will negotiate with me, and my bosses are on my side and taking FOREVER to get anywhere with this problem.
@everlastingrocks Don't get me started.
Specifically right here it's "no IMAP for you". They couldn't get it working with our Duo "2FA".