servers are created with hostmaster, postmaster, webmaster and abuse aliases pointing to the server admin at-time-of-creation.
if you edit the virtual server to set a new contact address, then the code should do this:
if servertemplate has mail aliases, loop through them
if template.mailaliasdestination == "${EMAILTO}"
look for that alias on the server (and on all sub-servers/alias servers) and update them to point to the new contact address
this is a simple fix but very important.
also on the same subject: if you go into "edit mail aliases" on a server (doesn't matter if it's the main server or a sub-server), and change an alias such as "hostmaster" to point to something else, then it should look to see if this is a template-based alias, and if so should replicate the change to all other parent/child servers in the whole hierarchy for that user. alright, this latter idea doesn't suit everyone at all times, so more thought would have to go into how it could be implemented without messing with the ability to do per-domain customization. but anyway, something like this would prevent getting the default/important records desynced between related domains.
both of these suggestions will of course overwrite any custom values, and may therefore fall under "the lesser of two evils" but i definitely say that updating "${EMAILTO}"-based records on contact address change is an important, useful feature which will be the desired behavior for almost 100% of usage cases. only do it for "${EMAILTO}"-derived records, though.
Comments
Submitted by JamieCameron on Mon, 02/18/2013 - 12:46 Comment #1
Changing all aliases that point to the old admin address could be a bit presumptuous, because the admin might want email to the postmaster to go to the old address still (assuming it is still valid).
Submitted by aitte on Mon, 02/18/2013 - 13:32 Comment #2
i am well aware of the danger of overwriting custom values and mentioned as much in the initial post.
so, implement it as follows:
imagine that the old contact address was "foo" and the new one is "guy@bar.com" (no relation to gay@bar.com, that is his brother)
when changing the contact address of the main virtual server:
voila.
Submitted by JamieCameron on Tue, 02/19/2013 - 20:45 Comment #3
That makes sense .. I'll make this change in the next release.
Submitted by Issues on Tue, 03/05/2013 - 20:46 Comment #4
Automatically closed -- issue fixed for 2 weeks with no activity.