Using classic Outlook for Windows in business environments
I work as an Exchange admin / Outlook support person and can confirm, I'm seeing this issue trending upwards over the last year or so, getting worse and worse over time. It's at its max right now with more and more users noticing the issue. The problem is, it's not always an easy to notice issue so it gets overlooked often (that's my personal hunch). The next problem is, Outlook's logging, mailbox audit logging, M365 Unified Audit Logging - all fail to capture the details other than the ones that make it look like the user used Outlook today to create and send the message.
I've seen cases where the impacted users had messages stuck in their Outbox. In those cases, sometimes, but not every time, the resent message(s) would be one of the ones within the set of stuck in Outbox messages. But not always.
Another common trait I've seen is that the messages are generated from MS Word, by going to File > Share > and sending the .docx as an attachment. In these cases, sometimes the subject is blank, and sometimes the subject is exactly verbatim the document file name. Sometimes, the resent message has the document file name for the subject, but the original sent message had no subject. Again, it's not a Word-source email in all cases I've seen. I did noticed that both @Gerard Vanhaver and @James Millward pointed out that they saw this issue relating to MS Word / MS Excel. Slightly different use case in either's report, but still in line with what I've described just above. Like, is this some kind of problem stemming from New Outlook new gracefully jiving with traditional rest-of-the-Office-suite of apps? Sure looks like it to me.
In many of the cases, the users have or are using New Outlook. These issues certainly popped up well after "New Outlook" was revealed with the slider to try it.
I think the mechanism that make the "Undo Send" feature possible, might be related to this issue. I've had some users find their "Save sent item to" setting mysteriously set to the Drafts folder, even though they are sure they never set it that way. The only thing I know of that does that behavior is the "Undo Send" feature. Right now I'm advising impacted users to consider changing the Undo Send feature from 10s to 0s to try and disable it. This is just a theory.
I've had one case with MS Support and it proved to be impossible for them to support. Since the issue cannot be reproduced on demand, and since all the evidence erroneously paints a fictious story, we had no way to prove that we even have a problem. But now that we have so many reports of this issue, and because the internet doesn't lie and we see tons of other people raising this issue, we're re-opening our support case.
If anyone can share any insights, or even just chime in to try and show the number of people facing this issue, that would be great.