lowest numbered MX record points to local host

[Silverado]

OK... OK.. I know this has been posted in here before.
But I haven't found a solution.
/scripts/mailperm doesn't work... and I am not sure where to add.. edit delete.. etc.. anything to get this accepting.
Here is the entire error:

Message 19G6vP-00077j-00 is no longer frozen
delivering message 19G6vP-00077j-00
LOG: 0 MAIN
lowest numbered MX record points to local host: Notmydomain.com
LOG: 0 MAIN
== user@notmydomain.com R=lookuphost defer (-1): lowest numbered MX record points to local host
LOG: 0 MAIN

Any idea or suggestions what I need to edit or add in exim or localdomains is appreciated.

[Juanra]

dig notmydomain.com MX

If it's not your domain and you can't change its DNS config there's not much you can do.

[Silverado]

Thanks anyway. I figured it out.

Wasn't that bad really.

[Silverado]

Not sure of the overall effect... but I just added the domain name to /etc/localdomains...... then I went to the mail queue in WHM click on deliver now and it went out instantly.. once the first one did when I refreshed the queue all the others were gone as well.

[Juanra]

Well if the domain is local the it should be in localdomains. If it's not local, you could get that error if the MX record points to 127.0.0.1 for example. It's not that strange to find domains configured like that.

[Silverado]

Originally posted by Juanra
Well if the domain is local the it should be in localdomains. If it's not local, you could get that error if the MX record points to 127.0.0.1 for example. It's not that strange to find domains configured like that.

Adding the domain (it's not local) did solve the problem.. but how would I change (where as well) or fix the abouve quote.

[Juanra]

Read this: http://www.exim.org/pipermail/exim-u...15/018251.html

[Nico]

We are having the same problem here. New accounts are not being added to /etc/localdomains. You can add it and it will start working, but if you run /scripts/mailperm it will remove the entries that were manually entered and you are back to square one. We have a ticket open about this and Cpanel support says to run /scripts/updatenow and /scripts/upcp. I doubt that will correct it though.

[Silverado]

I fixed mine just by adding it in.. hopefully I won't have to run the mailperm script again.... it didn't help much anyway... but it did fix our problems.
Thanks for the tip about mailperm wiping it out.

[c4host]

I looked carefully at one of my sites havint this error and saw he was emailing to

root@www.hisname.com

If mailed there I get an error If I mailed nomrally without the www .he got the message and no errors

[Nico]

Originally posted by Nico
We are having the same problem here. New accounts are not being added to /etc/localdomains. You can add it and it will start working, but if you run /scripts/mailperm it will remove the entries that were manually entered and you are back to square one. We have a ticket open about this and Cpanel support says to run /scripts/updatenow and /scripts/upcp. I doubt that will correct it though.

Just as I suspected this did not correct the problem. I just submitted a new ticket and did not receive and autoresponse with a ticket number. It appears the previous ticket is now closed.

cPanel.net Support Ticket Number: 13890

[Nico]

Cpanel Support found the problem with our case for all interested:

For some reason these domains are in the /etc/remotedomains file
which causes them to not be added back to /etc/localdomains when mailperm is run. If the mx servers for those domains are indeed supposed to be the server itself the delete those domains from there and add to /etc/localdomains, they should not be deleted on subsequent mailperm runs.

cPanel.net Support Ticket Number: