Old server to new - 451 Temporary local problem

GoWilkes

Well-Known Member
Sep 26, 2006
438
8
168
cPanel Access Level
Root Administrator
I've moved my site to a new server (both semi-managed servers belonging to me), and changed the DNS and A records on the old server to point to the new IP.

A few times a day, though, the old server sends an email to me as "root"; mainly updates on cron jobs, and the rare occasion that someone is still seeing the old site through the old server.

When this email is sent, though, I'm not getting it. Instead, I get this:

Code:
Delay reason: SMTP error from remote mail server after RCPT TO:<[email protected]>:
    host example.com [987.65.43.21]: 451 Temporary local problem - please try later
(Where 987.65.43.21 is the IP of the new server.)

Both servers have the same SPF record:

v=spf1 +a +mx +ip4:123.45.67.89 +ip4:987.65.43.21 -all

(Where 123.45.67.89 is the IP of the old server.)

I found a thread from 2008 on this error that said to make sure that the domain is in /etc/localdomains. It's not, but it is in /etc/remotedomains, which is where I think it should be at this point since it's now on a different server (but I really don't know the significance of these files).

Any other suggestions?
 

GoWilkes

Well-Known Member
Sep 26, 2006
438
8
168
cPanel Access Level
Root Administrator
I recognize that domains have SPF records; I was trying to say that the account on both servers has an identical SPF record.

The old server will be decommissioned at the end of next month. I'm leaving it online long enough for slow internet providers to update their DNS records. The local cable company (Charter) has been known to take up to 6 weeks!
 

Infopro

Well-Known Member
May 20, 2003
17,113
507
613
Pennsylvania
cPanel Access Level
Root Administrator
Twitter
I'm not sure I understand why you'd edit DNS on the old server, instead of editing the nameservers at the Domain Name Registrar to point the domain to the new server?

You might check the domain for issues here:
/http://www.intodns.com/

And check for clues here, on the old server that's not sending email:
WHM » Email » Mail Delivery Reports
 

GoWilkes

Well-Known Member
Sep 26, 2006
438
8
168
cPanel Access Level
Root Administrator
I edited both. Changing the DNS on the old server showed up almost immediately, but like I mentioned before, it can take up to 6 weeks for the nameservers on the domain name to show up globally.

The only warning at intodns.com was:

Your SOA EXPIRE number is: 3600000. That is NOT OK

I'm guessing this is the default set by cPanel, though, since I've never changed it. And maybe the reason some internet providers to take forever to update?
 

GoWilkes

Well-Known Member
Sep 26, 2006
438
8
168
cPanel Access Level
Root Administrator
I found several of the emails in Mail Delivery Reports, but it didn't really give me any more information:

Code:
Event:	defer warning
User:	root
Domain:	
Sender:	[email protected]
Sent Time:	Mar 23, 2014 4:19:04 AM
Sender Host:	localhost
Sender IP:	127.0.0.1
Authentication:	localuser
Spam Score:	
Recipient:	[email protected]
Delivered To:	
Delivery User:	account
Delivery Domain:	example.com
Router:	lookuphost
Transport:	remote_smtp
Out Time:	Mar 23, 2014 4:19:04 AM
ID:	1WRdcU-0008AB-LE
Delivery Host:	example.com
Delivery IP:	987.65.43.21
Size:	569 bytes
Result:	SMTP error from remote mail server after RCPT TO:<[email protected]>: host example.com [987.65.43.21]: 451 Temporary local problem - please try later
I don't know if it's being rejected from the new server, or if it never makes it from the old server? I do know, though, that it sends a firewall report to my Gmail, and that's going through just fine, so it's either this specific account, or potentially the fact that the account exists on the both servers?
 

cPanelPeter

Technical Analyst III
Staff member
Sep 23, 2013
575
20
143
cPanel Access Level
Root Administrator
Twitter
Hello,

You may want to update the DNS on the old server and set it to Remote Delivery instead of Local Delivery. That will update the settings and make sure that the domain in question (or hostname) is not in /etc/localdomains but in /etc/remotedomains.