New account email bug

[webquarry]

Here is something that DA does that is most annoying:

Let's say the client@domain.com wants to open a hosting account and that he wants to move domain.com to that account.

DA cannot send the account access info to client@domain.com because as soon as it creates the account, the server believes that domain.com is local to itself.

Is there any elegant way around this chicken-and-egg problem now?

What about changing the order that DA creates and account in? Could it first do a dry run to check to see if the account CAN be created, then send the email, THEN actually create the account?

[Chrysalis]

look here

I had the same issue myself, someone did before me and they found the solution, I strongly reccomend DA to implement this change as the default.

go down to where it says 'begin routers' in /etc/exim.conf

(in mine around like 660)

edit these lines so they look like this

OLD

lookuphost:
driver = dnslookup
domains = ! +local_domains
ignore_target_hosts = 127.0.0.0/8
transport = remote_smtp
no_more

NEW


lookuphost:
driver = dnslookup
ignore_target_hosts = 127.0.0.0/8
self = pass
same_domain_copy_routing = true
transport = remote_smtp
no_more


this makes it do a proper mx lookup instead of assuming the local server is the correct one.

[webquarry]

Hmm. my exim.conf looks like this:

lookuphost:
driver = dnslookup
domains = ! +local_domains
ignore_target_hosts = 127.0.0.0/8
condition = "${perl{check_limits}}"
transport = remote_smtp
no_more


That is a tad different than what you have.

I'm no exim expert. is changing that to:

lookuphost:
driver = dnslookup
ignore_target_hosts = 127.0.0.0/8
condition = "${perl{check_limits}}"
self = pass
same_domain_copy_routing = true
transport = remote_smtp
no_more

Going to be ok?

[Chrysalis]

should be ok I think, backup old config restart exim and run tests if all is well then you done it correct.

[DamnSkippy]

So, this is from August of last year, is this still an issue or has it been changed in an update to DA?

[Chrysalis]

this isnt from august, its from this month and it is still an issue yes.

[nobaloney]

I'm considering making this change to the exim.conf file.

I've asked on the exim forum to see if there are any good reasons to not do it.

Jeff

[webquarry]

That would be great Jeff. I like your exim.conf file but this really is a problem.

[Chrysalis]

There is one downside to this change jeff, for local domains it does a MX lookup instead of just instantly sending the email, so this will create a higher load and delay for sending emails. But I think this is a lot better then sending emails to the wrong destination.

[webquarry]

I've been running for a while here on a server that hosts 350 domains. So far no noticable load level increases.