4 ms·

How did you end up resolving the issue with too many generated emails addresses? I built and use my own domain inbox which buckets emails by email addresses (ht

• megous 4y ago
  - Simple PHP web page for adding and listing existing aliases to/from a database. Adding a new alias has to be quick. Type in a description, and copy out the generated alias to clipboard for use elsewhere. - Startup script that fetches the aliases from DB and modifies a mail client configuration so that all randomly generated addresses are annotated with a short descriptive text indicating to whom the address was issued and makes it so that replying sets the From header to the alias. This combo works well for me.
  • yonrg 4y ago
    Actually, I do not actively generate, meaning create, a new addresses. I use a filter I'm the delivery process in Exim which truncates a suffix from the local name.
    • megous 4y ago
      Keeping track of addresses is still worth it, regardless of how they're implemented.
• yonrg 4y ago
  My way dealing with email has converged over the years to the following. First, there two different kind of on-demand addresses. 1. Registration, these emails are stored in the password manager 2. Throw away, one time addresses Second, I maintain a two mail folder method: inbox and archive. Sent mails are put into inbox, too. This makes mail threads a whole. From there they are either purged if spam or moved over to archive. From here I can answer your question, how I manage all those generated addresses. The folders are indexed. So I am able to find anything (if not encrypted). In particular I can retrieve all my used addresses.