A client of mine has a web service where a simple web page can be made
via a browser to crete an identity for them online. Build a page with
web tools, toggle a setting to add DNS records, update the registrar
to point to the NS's, and they have a live webpage in short order.
They want to be able to allow an info@ email address that will only
forward to some other account. There is no need for pop/imap login, i...@example.com
will simply forward to users-des...@theiremail.com
Any suggestions on the simplest way to approach this. I was thinking
postfix with MySql backed data store. Today I read that RHEL is
behind on postfix, and I think does not have MySql support in their
rpm's. I have zero access to a staging server.
If this turns into a high volume site, would file based aliases fall
apart after a certain amount? I also see maintaining a alias mapping
via a file managed by a web service to be prone to error. If anything
I wold store the mappings in a database, and write them out clean on
schedule. What are the upper limits of how many forwards I should
feel comfortable maintaing as a local file?
Any other suggestions on methodology?
--
Scott * If you contact me off list replace talklists@ with scott@ *
