• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 768
  • Last Modified:

Unable to receive or send to certain domain

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


0
CTGSE
Asked:
CTGSE
  • 5
  • 2
1 Solution
 
BertlingCommented:
have you checked the exchange logs on your server to see what is happening to the out bound mail?
check the queues to see if there is a queue for this domain,

you could for testing purposes create a SMTP connector which directly routes mail to the problimatic domain. using the IP address as a smart host and secifying the address space as the problimatic domain.

also plz advise if they have thecorrect spelling for sure, and can they send to a different email address in your organisation?

are you or them using any spam filtering?
0
 
CTGSEAuthor 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.
0
 
CTGSEAuthor Commented:
Sorry, forgot to mention the queues are empty.
0
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

 
BertlingCommented:
do you or they get any kind of bounce back?
0
 
CTGSEAuthor 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
"
0
 
CTGSEAuthor 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!
0
 
CTGSEAuthor Commented:
It didn't fix the problem directly, but it did lead to the solution. Thanks!
0

Featured Post

Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

  • 5
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now