Show HN: Self-Validating Email Aliases for Postfix

by m3047 on 11/2/2019, 6:33 PM with 26 comments
  • by notadev on 11/2/2019, 11:49 PM

    I sort do this a different way. I have a custom domain and use that with Google's G Suite. I set the catch-all email to my email. Then everything I sign up with gets a different email address, like amazon@<mydomain>. I use a password manager to track all the different emails/passwds. This has helped me catch the water company giving out my email. I got junk mail asking me to sign up with my email utilities-water@<mydomain>. If a particular email starts getting spam, I just blacklist the To: address.

  • by teddyh on 11/2/2019, 11:31 PM

    Why require a patched Postfix merely to use a localhost address and port as a lookup table? I would assume that a unix domain socket should be acceptable?

  • by m3047 on 11/5/2019, 5:09 PM

    I want to thank HN and the HN community for the awesome free exposure. It means a tremendous amount to a niche open source project. I'm sure I can attribute 6 clones and 20 GitHub stars to this, hopefully some of those turn into users and possibly even contributors. Thanks again...

  • by edoceo on 11/2/2019, 11:44 PM

    You can point alias_maps to a SQL table too. So adding and removing alias can be done on the fly. No patching.

    One can also use UAE, the '+' symbol after the user portion in postfix - don't need new alias. Then use a dedicated UAE base address "spam+VENDOR@example.com".

  • by steve19 on 11/2/2019, 8:58 PM

    This is quite clever. I have avoided wildcards because I have not wanted to deal with the increased spam sent by bots to random (jane@ eve@) or not so random addresses (webmaster@).

  • by 1996 on 11/2/2019, 9:06 PM