Re: [Tools-discuss] Draft email aliases aren't forever

[Carsten Bormann <[e-mail]>]

On 2022-05-12, at 00:49, Martin Thomson <[e-mail]> wrote:
> 
> In this case >> 4 times harder.  I didn't search, though I should have, but that would increase the multiplier a great deal.  I wasn't looking for a new job, just to notify people of a security vulnerability in their (proposed) protocol as a courtesy.

Indeed, my strongest sympathy.

I just replied somewhere else on a message from 2016.
If there would have been draft aliases in there, I would have had to do the above (or, more likely, after each non-delivery report forward a copy of the original mail to the non-recipient, as anybody replying to my message would have to do).

That said, a datatracker button “give me the current addresses of the people that are on that draft” would be an 80 % solution.  This could be done on demand; no lengthy lists of 50000 (*) drafts to slog through periodically.

(Bonus: I don’t have to live with the, er, no longer quite reality-adapted alias forwarding.)

Grüße, Carsten

(*) That’s the number I have on my laptop; haven’t looked at the number datatracker has.

PS.:
> I guess that is one way to fix the bug.  Is there an index missing on that database table?

(Has the era of databases with indexes reached mail agents yet?
I haven’t done anything here since virtusertable was the thing to look up in the docs, and 50000 lines of virtusertable sounds like a non-starter.)