AlaskanWolf

Well-Known Member
Aug 11, 2001
535
0
316
Fremont CA
It seems its system wide, I have had nothing but problems with this one server. More the one occation, users are complaining that they are not getting their forwarded email and if it does come, it dumps it all at once.

Any suggestions would be ideal as 90% of my tickets are email problems atm
 

Annette

Well-Known Member
PartnerNOC
Aug 12, 2001
445
0
316
Look in /var/spool/exim/msglog for a message with the same ID as the mail that has been deferred. That shouls at least give you an indication as to what the underlying problem is. Just looking at the log iteself in this instance doesn\'t provide enough information.
 

Annette

Well-Known Member
PartnerNOC
Aug 12, 2001
445
0
316
Is the recipient domain hosted on your box or elsewhere? When you do a local nslookup on the recipient domain, what do you get?
 

AlaskanWolf

Well-Known Member
Aug 11, 2001
535
0
316
Fremont CA
the recipient (final forwarding domain) is not on our system, i get this when i do a nslookup

Name: nh.ultranet.com
Address: 207.172.11.21
 
B

bdraco

Guest
[quote:5c5564b62f][i:5c5564b62f]Originally posted by AlaskanWolf[/i:5c5564b62f]

user complaining that emails are not reaching their forward, when i send a test email, i get this error in the logs:

2001-10-22 12:46:27 15vl1n-0004Ic-00 &= [email protected] H=mta-2.gci.net [208.138.130.83] P=esmtp S=1707 id=007e01c15b32$127a1e50$$
2001-10-22 12:46:27 15vl1n-0004Ic-00 == [email protected] &[email protected]& routing defer (-42): retry time not reached[/quote:5c5564b62f]

That means the the address has failed so many times that exim gave up delivering to it for a few hours... This prevents someone from mail bombing a non-existant address to drive up the server load.. You could just thaw out all the messages in WHM's mail q manager..