We help IT Professionals succeed at work.

Unable to receive or send to certain domain

CTGSE
CTGSE asked
on
884 Views
Last Modified: 2012-05-05
Using Windows Small Business Server 2003

Domain is setup and everything has been working fine.
However, we are unable to send or receive email that routes thru the mail server mx.coxmail.com.
I have ran DNS checks on my domain and theirs and have yet to find a problem.

When I send email to someone on that mail server I get no kickbacks or messages. Nothing.

When someone on the mx.coxmail.com server sends mail to a known good address of mine they get a kickback as follows.
"
This Message was undeliverable due to the following reason:

The following destination addresses were unknown (please check the
addresses and re-mail the message):

<test@<mydomain>.com>

Please reply to <Postmaster@<mydomain>.com>
if you feel this message to be in error.



--------------------------------------------------------------------------------

Reporting-MTA: dns; dukecmmtao05.coxmail.com
Arrival-Date: Wed, 1 Oct 2008 17:04:51 -0400
Received-From-MTA: dns; dukecmimpo03.coxmail.com (68.99.120.137)

Final-Recipient: RFC822; <test@<mydomain>.com>
Action: failed
Status: 5.1.1
"

Any help will be appreciated. Thanks


Comment
Watch Question

Commented:
This one is on us!
(Get your first solution completely free - no credit card required)
UNLOCK SOLUTION

Author

Commented:
Thanks for the reply.

I turned on diagnostic logging for the transport after I created a new smtp connector for just the problem domains with the mx.coxmail.com ip as the smart host. The connector seems to work fine, but the message still doesn't make it to them.

I contacted Cox and setup a test account on that particular mail server. In the test account test21@test.omhcoxmail.com I cannot email my domain. I get the same kickback immediately.

I added the test domain to the smtp connector and tried sending it an email. These are the only 2 logs in the application log referring to the test email I sent. They are info logs, no errors.
"
SMTP GetNextHop returned hr=0x0 in 0ms.
 DestAddr=<test.omhcoxmail.com>, Type=<SMTP>
 MsgType=0x0, NextHopType=OTHER_ROUTING_GROUP
 Type=<SMTP>, Class=<test.omhcoxmail.com>, SchedId=0x1
 RouteAddr=<[68.99.120.4]>
 Connector=<024d0f35-bcf2-4804-825f-abfd6a106422>
***********************************
Following connector now is ok to connect to its target bridge head. CN=coxmail test connector,CN=Connections,CN=first routing group,CN=Routing Groups,CN=first administrative group,CN=Administrative Groups,CN=<my domain>,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=<my domain>,DC=local
"

I disabled the portion of AVG for exchange in hopes that that might fix but to no avail.

No spam filtering is being utilized at this time.

I also created a new AD account called test and I am able to send to it from any email account except the test21@test.omhcoxmail.com account which is on the mx.coxmail.com mail server.

Additional thoughts and ideas greatly appreciated.

Author

Commented:
Sorry, forgot to mention the queues are empty.

Commented:
do you or they get any kind of bounce back?

Author

Commented:
On my domain side I get no bouncebacks whatsoever.

On the test21@test.omhcoxmail.com account I get the same bounceback when sending to my domain.
"
This Message was undeliverable due to the following reason:

The following destination addresses were unknown (please check the
addresses and re-mail the message):

<test@<mydomain>.com>

Please reply to <Postmaster@<mydomain>.com>
if you feel this message to be in error.

--------------------------------------------------------------------------------

Reporting-MTA: dns; dukecmmtao05.coxmail.com
Arrival-Date: Wed, 1 Oct 2008 17:04:51 -0400
Received-From-MTA: dns; dukecmimpo03.coxmail.com (68.99.120.137)

Final-Recipient: RFC822; <test@<mydomain>.com>
Action: failed
Status: 5.1.1
"

Author

Commented:
Well, I was able to get it fixed and it has been working for a couple weeks now. It turned out that the isp still had <mydomain> on their mail server as if they were still hosting the email. Therefore whenever anyone else on that mail server tried to send to us it naturally didn't have any of the new email accounts I had setup in our exchange server. Plus their server does the normal reverse dns check for spam. This is why when I sent to anyone on that mail server it would do a a record lookup and think my email was spam because it wasn't coming from their mail server. So the server dropped the email w/o a kickback.

Thanks for the help, I'm awarding you the points because without doing your suggestion I would not have been able to hold the isp tech on the line till a resolution was discovered. Thanks Again!

Author

Commented:
It didn't fix the problem directly, but it did lead to the solution. Thanks!
Unlock the solution to this question.
Join our community and discover your potential

Experts Exchange is the only place where you can interact directly with leading experts in the technology field. Become a member today and access the collective knowledge of thousands of technology experts.

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

OR

Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.