I somehow got the idea that there was
systematic misrouting (e.g. the typo was in various mail-handling scripts, not even directly accessible by service-users).
I'm actually strangely comforted that there are consciencious (or at least non-/dev/nulling)
postmaster@s still out there. Twenty or thirty years ago I would regularly send the (copious) 419 emails I received on to the postmaster@ for the header-identifiable mediating sources (as sole owner of my own subdomain, I could indeed pick up things sent speculatively to
<anything[1]>@mySubdomain.myISP.co.uk). I didn't get many actual replies[2], but I like to think that the respective admin/subordinate gained a benefit from my 'report'. I've long since stopped doing this[3], as Eternal September became Web2.0 and even (unrelated to the above) sending mail to the current contact address on the AppStore tends to often enough ellicit a "we don't monitor this address, please use Twitter/Facebook/log into our forums/etc to contact us" autoresponse. Which I don't feel is right, though I do understand why they might do that.
I actually admire this domain-admin[4]. Maybe the fact we know about it is a little rash (for various reasons) or even not entirely due to pure-heartedness, or indeed the true and faifhful culmination of never being actually listened to behind the scenes. Having had a mere taste of the great power/responsibility involved, I can definitely imagine being there, in that position, and technically better to do this than to wipe my hands and abdigate all responsibility from the off.
[1] Grossly outnumbering anything spammily sent to any name@ I actually 'published' out there for actual use. Clearly there was even then a tendncy to automatically probe with
whatever@domain.one being merged with
regardless@domain.two (or possibly some composite/procedural pre-@ names), just because it was an easy way to land on more 'private' and less outward going individuals' mailboxes that might yet be pysychologically unimmunised against such things.
[2] Occasionally something automated clearly set up as a spam-trap of its own, perhaps demanding an "I am not a bot" confirmation of some kind to allow delivery to continue to the genuine human-read mailbox.
[3] Save for "Hi, it's ISP here click on <
obviousfakelinkISP@randombusiness-or-blogsite.obviousforeignTLD> regarding your bill/the imminent deletion of your email account", which I pack up and send to the publicised
phishing@actual.ISP.domain address, when they arrive in various mailboxes I 'manage' or am asked to monitor. No replies for them, either, but the ISPs involved do(/did once?) say they invited such things. Presumably to know what to autofilter.
[4] Ok, so he also sounds just as much a 'details person' as I am, when I can be. And receiving actual clear 'leakage' from a .mil account is something I haven't had for a while[5], but I could see how you'd want to keep an eye out for such things wandering through 'my domain' if they did. No matter whether I thought my hat was white, black or some form of grey. Exactly which shade of hat he has resolved to wear, behind the scenes, would just be a matter of opportunism. The error(s) already having been made by others.
[5] I know someone who managed to 'gain' a .mil domain, back when we were both in university. Not sure how. But he was banned from the academic network (without direct supervision/escorting) for more local nephariousness