Mail routing problems on Chevelle

PrinceZordar · #1 04-09-2006, 02:02 PM

Twice in the past week one of my hosts reports an error routing mail (I have removed the e-mail addresses):

This message was created automatically by mail delivery software.

A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:

unrouteable mail domain "aol.com"
unrouteable mail domain "aol.com"
unrouteable mail domain "supernet.com"
unrouteable mail domain "aol.com"
unrouteable mail domain "iezpc.com"
unrouteable mail domain "aol.com"
unrouteable mail domain "qnet.com"
unrouteable mail domain "cs.com"
unrouteable mail domain "yahoo.com"

Is this a problem with Chevelle, some other issue, or another form of the SpamCop problem again?

-Z

esl · #2 04-09-2006, 02:04 PM

For a quicker response you should open a trouble ticket so that a system admin can look into this for you.

PrinceZordar · #3 04-09-2006, 03:47 PM

Quote:

Originally Posted by esl

For a quicker response you should open a trouble ticket so that a system admin can look into this for you.

I've had to do that in the past, but due to the nature of this problem (same domain having multiple problems where none of my other hosts are seeing it) I wanted to see if anyone else was having this issue before I bothered tech support. The more I look into this, the more I think it might be her mailing list traffic is hitting a threshold (max messages per hour to a domain) than an actual host problem.

-Z

esl · #4 04-09-2006, 03:49 PM

Okay, I understand.

MikeC · #5 04-09-2006, 04:05 PM

If more than 200 emails are being sent within an hour, you're most likely hitting the cap. See http://forums.hostgator.com/showthread.php?t=2605 for more details.

On the other hand, we (and one of our customers) are seeing sporadic 'unrouteable mail domains' and we're not sending lots of mail. On 4/3/06 support indicated there had apparently been a corruption of 'resolv.conf' on the server (hummer) and that it had been fixed. Unfortunately, we're still seeing the issue sporadically. So we've opened another ticket with support and we'll see where it goes from there.....

MC