Urgent help - exim problems

Status
Not open for further replies.

vashti

Member
Jun 30, 2003
19
0
151
Hello all

For some reason, email has stopped working (sort of):

1. email from an account on the server to another account on the server can be recieved and sent without problem.

2. email from an account on the server to an email account *not* on the server results in:

The message could not be sent because one of the recipients was rejected by the server. The rejected e-mail address was '[email protected]'. Subject 'test', Account: 'mail.email-on-problem-server.com', Server: 'ip.ad.re.ss', Protocol: SMTP, Server Response: '451 Temporary local problem - please try later', Port: 25, Secure(SSL): No, Server Error: 451, Error Number: 0x800CCC79
3. email from an account *not* on the server to an account on the problem server is not received at all:

Final-Recipient: rfc822;[email protected]
Action: failed
Status: 5.5.0
Diagnostic-Code: smtp;550-Verification failed for <[email protected]>
550-unrouteable mail domain "not-on-problem-server.com"
550 Sender verify failed
What have I done to try to remedy this:

1. Searched these Forums for hours
2. /scripts/exim4 (no change)
3. rm exim.conf and then /scripts/exim4 (no change)
4. /scripts/exim4 again (no change)

I don't know what more to do now.

I am willing to pay by Paypal for resolution to this, as I am 100% stuck. please help!
 

vashti

Member
Jun 30, 2003
19
0
151
I have also tried

/scripts/restoreeximtodefaults (again no change)...

Help! Paypal not a problem!
 

vashti

Member
Jun 30, 2003
19
0
151
I have now also rebooted the server. This has not fixed it either...

FYI, I am running:

WHM 9.1.0 cPanel 9.1.0-S73
RedHat 7.2 - WHM X v2.1.2
 

elleryjh

Well-Known Member
Apr 12, 2003
475
0
166
Sounds like a dns problem, not a mail server problem.

Make sure resolv.conf is set correctly.
 

vashti

Member
Jun 30, 2003
19
0
151
Originally posted by elleryjh
Sounds like a dns problem, not a mail server problem.

Make sure resolv.conf is set correctly.
Hi elleryjh, thanks for that. I have tried this and it looks good - I have two servers actually and the one that is OK (accetping/sending emails etc) has the exact same resolv.conf settings as the one that is not OK...

Any more ideas would be great please!
 

vashti

Member
Jun 30, 2003
19
0
151
Originally posted by elleryjh
what happens when you run the command

dig google.com
; <<>> DiG 9.2.1 <<>> google.com
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 57644
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;google.com. IN A

;; Query time: 1 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Sat Mar 27 20:05:43 2004
;; MSG SIZE rcvd: 28
 

elleryjh

Well-Known Member
Apr 12, 2003
475
0
166
That means you can't get to google. Definetly a dns problem.

Probably best to contact your data center for this problem.
 

vashti

Member
Jun 30, 2003
19
0
151
Thank you for your help, I will post back when (if) I can find resolution to this.
 

Website Rob

Well-Known Member
Mar 23, 2002
1,501
1
318
Alberta, Canada
cPanel Access Level
Root Administrator
Originally posted by vashti
Hi elleryjh, thanks for that. I have tried this and it looks good - I have two servers actually and the one that is OK (accetping/sending emails etc) has the exact same resolv.conf settings as the one that is not OK...

Any more ideas would be great please!
That is probably the problem. The Server that is not OK should be using it's own Base IP, not one for another Server.

Change resolv.conf of the problem Server to look like:

nameserver 127.0.0.1
nameserver (enter Server BaseIP)

Restart Bind and you should be OK.
 

masgra

Registered
Nov 24, 2003
2
0
151
/scripts/restoreeximtodefaults

This is what finally fixed this for us. After 4 hours of working my way through every suggested fix for this issue '/scripts/restoreeximtodefaults ' finally did it.

This appears to be an ongoing issue. We have just updated to 9.8.0 C13 and all our clients emails started getting this 451 error, which first appeared as a Horde 'Auth.php' error.

Anyway, all is ok now.
 
Status
Not open for further replies.