I created an accounting system for self-employment activities that does everything: invoicing, tracking expenses and assets, capital cost allowance depreciation of assets.
I have a web app called Tamarind (acronym for throwaway mail alias randomization is not defeatable). I can create randomized e-mail aliases there which instantly go live. Likewise, delete them. Each entry is associated with a memo field that can contain URL's (these get rendered into links). Also a date of creation. The UI lets you edit the order: selecgt entries by checkbox and move them up and down, or to the top or bottom. There is a regex search box. It can authenticate the user using SASL or IMAP4. It works by editing a mail aliases file; your mail server has to know to include that one. It can work with the main /etc/aliases; Tamarind will avoid modifying any parts of the file it doesn't know about, confining itself to the area between its markers.
I have a web app called Tamarind (acronym for throwaway mail alias randomization is not defeatable). I can create randomized e-mail aliases there which instantly go live. Likewise, delete them. Each entry is associated with a memo field that can contain URL's (these get rendered into links). Also a date of creation. The UI lets you edit the order: selecgt entries by checkbox and move them up and down, or to the top or bottom. There is a regex search box. It can authenticate the user using SASL or IMAP4. It works by editing a mail aliases file; your mail server has to know to include that one. It can work with the main /etc/aliases; Tamarind will avoid modifying any parts of the file it doesn't know about, confining itself to the area between its markers.