451 Temporary local problem

[TCSLEA]

Try this...

Read this entire post before trying anything....


Try editing your /etc/localdomains to your liking. In mine, I included every actual and parked domain on the server, as well as the hostname for the server.

Then try removing the file /etc/remotedomains:

rm /etc/remotedomains

Then put an empty remotedomains back:

touch /etc/remotedomains


You should now have a good localdomains, and an empty remotedomains.

Try running /scripts/mailperm now... when I did this, it left the localdomains file alone. I'm guessing that the contents of the remotedomains file may have a bearing on the contents of the localdomains file.

Do this at your own risk, though... I don't know what other affects this could have. I just saw in the script that it looked at the remotedomains file. I also noticed there are two options available, neither of which I tried:

/scripts/mailperm --skiplocaldomains
/scripts/mailperm --skipserverperm

Chris

 

[khoonchee]

Hello,

What entry should I have in the resolv.conf file ? Currently it listed only nameserver 127.0.0.1 as the main entry in the sender server

I have tried most of the commands and steps in this thread but unfortunately none of them fix the issue

 

[TCSLEA]

Originally posted by khoonchee
What entry should I have in the resolv.conf file ? Currently it listed only nameserver 127.0.0.1 as the main entry in the sender server

That file has the list of nameservers for your server. If that's your only entry, I think it indicates your server is also acting as it's own nameserver.

Normally you will want at least two name servers. I use 3 for example, which includes my own server (running bind) as well as two other servers at the ISP where I co-locate.

My resolv.conf looks like this:

nameserver ip.of.my.server (and 127.0.0.1 works too)
nameserver ip.of.other.nameserver
nameserver ip.of.another.nameserver

In fact, many registrars won't accept DNS changes unless you provide them with at least two name servers.

As for that error, make sure your /etc/localdomains has every single domain name being hosted on your server. If it's missing one, that domain will likely get that error when sending email.

 

[khoonchee]

Hello,

Thanks for the reply.

Yup, both the sender's domain and recipient's domain is in the /etc/localdomains file ...

 

[jsteel]

Check your 'FROM:' header envelope in your transcript. If it is blank (no valid sender), exim will reject it with a 451 error. Lack of a valid sender is a common method used by spammers. We see this issue with a lot of customers using scripts to send email. When they don't place a valid 'FROM:' address in the emails they generate, it always fails with the 451; as soon as they add a valid sender the problem goes away.

 

[NNNils]

I did all the things suggested in this topic, but still have the following problem:

When sending mail from server A to server B I get:

R=lookuphost defer (-1): host lookup did not complete


When sending mail from server B to server A I get:

R=lookuphost T=remote_smtp defer (0): SMTP error from remote mailer after RCPT TO:: host domain.com [x.x.x.x]: 451 Temporary local problem - please try later

Any help?

 

[NNNils]

Found it!!!!!

the name of 64.5.32.92 is server1.domain.com

there was a domain.com zone on 205.214.86.12

after deleting, it works fine.

 

[myusername]

Similar fix here!

The sites that were having issues with mail delivery used:

nsx.somedomain.com
nsy.somedomain.com

These sites were on host A

Host A could not deliver mail correctly to any host A- Z to any site using :

nsx.somedomain.com
nsy.somedomain.com

I looked in Host A's zones and sure enough, there was a zone for somedomain.com, that did not list correct ns listings.

The server was looking locally, instead of quering gtld.net and all digs were failing.

removing somedomain.com from the zones fixed all that. now it digs the correct nameserver instead of the local one, or gtld.net and things "appear" to be working.

crossing fingers.