You're right, that is a good simplification of that option to make it less tech dependent:
* Generate addresses with that process (that can be done in the head)
* Programmatically verify the incoming addresses to filter junk/not (hopefully not difficult with postfix, just use the “standard” config-in-db setup with a stored procedure to do the mapping instead of a simple SELECT so you can check the checksum (in fact, it should be possible with a SELECT but I expect the syntax will be more messy that way))
* Still have a whitelist for addresses previously used, unless using a new sub-domain for this setup
* Still send mismatches to a junk folder not /dev/null in case of mistakes
I might go that way when I finally get around to rebuilding & migrating my mail server(s)…
* Generate addresses with that process (that can be done in the head)
* Programmatically verify the incoming addresses to filter junk/not (hopefully not difficult with postfix, just use the “standard” config-in-db setup with a stored procedure to do the mapping instead of a simple SELECT so you can check the checksum (in fact, it should be possible with a SELECT but I expect the syntax will be more messy that way))
* Still have a whitelist for addresses previously used, unless using a new sub-domain for this setup
* Still send mismatches to a junk folder not /dev/null in case of mistakes
I might go that way when I finally get around to rebuilding & migrating my mail server(s)…