What hassle? With a bit of organization there's no real hassle. My addresses are all in /etc/aliases on the mail server and have a time stamped comment in front of them naming the company / website.
I can easily take this "db" with me on my smartphone. Or could make it available with a simple interface. As we use Joplin already to share data between family members, that's the place the list of addresses lives for lookups from family members.
The benefit isn't primarily for deletion, which is a nice side effect, but to easily recognize phishing to the "wrong" email addresses. Certain deletions are done automatically for addresses where I put a timestamp in, e.g. me.dhl24c@example.com will be from the third quarter of 2024 and can be removed at the end of 2024.
Comments
What hassle? With a bit of organization there's no real hassle. My addresses are all in /etc/aliases on the mail server and have a time stamped comment in front of them naming the company / website.
I can easily take this "db" with me on my smartphone. Or could make it available with a simple interface. As we use Joplin already to share data between family members, that's the place the list of addresses lives for lookups from family members.
The benefit isn't primarily for deletion, which is a nice side effect, but to easily recognize phishing to the "wrong" email addresses. Certain deletions are done automatically for addresses where I put a timestamp in, e.g. me.dhl24c@example.com will be from the third quarter of 2024 and can be removed at the end of 2024.
You made my point better than I could with the rest of your post.
Enable catchall and you don't need to do all of that work.
It's not "much work" it's a script. That was a tiny bit of work but that's a long, long time ago :-)
As for "catch all" that makes addresses available which are otherwise not available and get rejected.