Alas (and this may be an issue that you’d need to log upstream) that action seems to have broken emailed links. As an example in mailing list mode a link I received was https://community.openstreetmap.org/t/how-to-see-only-english-threads/102529/3 and if I follow that link I just see " This topic will be automatically deleted in 7 days.".
Making this a separate topic to keep track of it.
We’ll need to think who can support this if reporters can’t do themselves.
Similarly, I noticed yesterday that I had to edit Privacy expectations when mapping points of interest to fix a link to a post that had gotten moved to a different topic. It wound up looking like a plain-text link and pointing to a very different message in the original topic.
Faced with the broken link, I couldn’t recall which post I had linked to, so had to use the Wayback Machine to find it again. I got pretty lucky; the Wayback Machine doesn’t normally index single-page applications like Discourse very well.
A redirect would be nice, as would a notification that the post you’ve linked to has been moved. But a permalink URL is poorly coupled to the original post – it ends in the post’s index within the topic, which isn’t stable in cases like this. So I suspect Discourse would be unable to keep close track of inbound links.
I’m unsure if quoting the intended post would’ve avoided breakage in my case. The quotation syntax would still refer to a post index, but it would also contain the quoted text.