Comments on: unrouteable mail domain

By: james033

james033 — Sat, 11 Jun 2011 23:23:21 +0000

awesome blog theme! How long have you been blogging for ? you make blogging look easy. Visit domain yahoo..The overall look of your website is excellent, let alone the content

By: The Dino

The Dino — Thu, 24 Jan 2008 23:14:52 +0000

Thanks for those tips… I just Googled for that term as you suggested and here we go… I need to contact my hosting company… I am paying much more than you here for hosting and cannot contact my forum members… that is strange…

By: Ravi

Ravi — Thu, 05 Jul 2007 20:11:53 +0000

Dear Che

iam using cpanel how can i configure to stop “unrouteable mail domain”

By: rapidweb

rapidweb — Fri, 04 May 2007 13:41:59 +0000

Thanks for your help.

This has cleared things up for me so much!

:-)

By: albert

albert — Wed, 11 Apr 2007 01:56:14 +0000

I could not agree more. I had the same thing with SINGHOSTER.COM. I have told the webhost that we have a legitimate mailing list, but he is such a nut case that he classified me as a SPAMMER. And I was sending out a miserable 50 emails per hour.

After having paid up for 1 year and using the site for only 1 mth, he decided to freeze my emails and I could not even check for emails. Email for support results it nothing. I ask for evidence and he could not even produce it…

What recourse do we have against such nut cases ?

Be warned…

By: Amanda

Amanda — Wed, 28 Feb 2007 17:28:04 +0000

Thanks Che! This fixed my problem.

By: Curt

Curt — Tue, 19 Dec 2006 16:59:25 +0000

Thanks so much for this! I recently changed ISPs for a client who was having problems using the NetFirms webmail interface. Now she’s with Elite, using Horde and she’s getting this message b/c of the limit. She didn’t actually get to their limit of 100 emails an hour per domain, but she was pretty close. Although I understand it, it’s hard to explain to someone who’s response is "I never had this problem with Yahoo." AUGH!

By: Che

Che — Mon, 04 Dec 2006 16:56:15 +0000

this unrouteable mail domain problem took me for frekin forever to figure out. in my case it was fixed by turning off the option to "Track the origin of messages sent though the mail server by adding the X-Source headers (exim 4.34+ required)" in WHM. I’ve seen other posts that talk about "preventing user nobody from emailing" or enabling / disabling SuExec. hope this helps someone :)

By: toby

toby — Mon, 28 Aug 2006 09:38:19 +0000

I agree with you that limiting outgoing email on customers' accounts can be necessary depending on the type of hosting plan. However Site5 erred in that:

* this rate limit was not advertised,
* the error message I received had nothing to do with the "actual" error, causing me hours of pointless troubleshooting, and
* the rate they used (150/hour) is way too low for someone who sends out *opt-in* mailing lists.

While the last point may be subjective, the first two are just plain bad customer service, which is why I left.

By: Doug

Doug — Mon, 28 Aug 2006 07:52:43 +0000

I am operating a hosting company myself and it is totally impossible to stop hackers from using insecure scripts on customer accounts to send spam. Now if you do not have a limit the mail server will just send out like 100.000 emails and as a result of this you will end up on all the spam blacklists and your customers will be totally unable to send emails to anyone for 24 hours or more as a result of this. Limiting the amount of emails that can be sent is absolutely something that hosts have to do in the customer`s interest.