On Tue, 2006-01-10 at 19:13 -0800, Jeff Lasman wrote: > I think I've figured out what we (or rather the control panel) can do: > > When the user site is configured by the automation system, do things > in this order: > > 1) send the welcome email > 2) configure the DNS > 3) add the new domain(s) to local_domains
What I'd be inclined to do is give the customer a configuration switch to flip when they've changed their DNS. Then either have that same switch add the domain to local_domains, or filter local_domains on @mx_any so that it happens automatically when the DNS changes... domainlist not_local_domains = !lsearch;SOME_FILE domainlist local_domains = !+not_local_domains : @mx_any In general, beware of propagation delay if you're using @mx_any for things like this -- but if your local nameservers are authoritative (or change to being authoritative at the correct time) then that's fine. You could even have a separate tool which monitors the root nameservers until the DNS is delegated to you (or monitors their nameservers until the MX records point at you), and flips that 'configuration switch' automatically rather than making them do it themselves. -- dwmw2 -- ## List details at http://www.exim.org/mailman/listinfo/exim-users ## Exim details at http://www.exim.org/ ## Please use the Wiki with this list - http://www.exim.org/eximwiki/
