Wanted: Network Administrators

See great job listings on the jobs Page

Problem sending and receiving a message from one domain to another, not received on secondary domain - Message Delay

Good Day,

I am trying to send a message from domain1.com to domain2.com.
When I send the message to domain2.com from domain1.com, I am seeing the following;

-=-=-=-=-=-=-=-=-=-
Message 1
-=-=-=-=-=-=-=-=-=-

Delivery Status Notification (Delay)

Delivery to the following recipients has been delayed.

-=-=-=-=-=-=-=-=-=--=-=-=-=-=-=-=-=-=--=-=-=-=-=-=-=-=-=--=-=-=-=-=-=-=-=-=-
then I will see this reply;

-=-=-=-=-=-=-=-=-=-
Message 2
-=-=-=-=-=-=-=-=-=-
Your message did not reach some or all of the intended recipients.
The following recipient(s) cannot be reached:

Could not deliver the message in the time limit specified. Please retry or contact your administrator.

-=-=-=-=-=-=-=-=-=--=-=-=-=-=-=-=-=-=--=-=-=-=-=-=-=-=-=--=-=-=-=-=-=-=-=-=-
From the Exchange Management Console, we have an SMTP Connector for McAfee e500, using DNS to route to each address space on connector.

The Address Space for this SMTP Connection is set to all-> *

When I perform an nslookup for domain2.com, I am receiving a non-authoritatuive answer for domain2.com domain.

If I perform nslookup

>set querytype=soa
>domain2.com

I see the primary name server correctly, matching what is shown from dnsstuff.com as well.
Tried smtpdiag from the local Exchange server on domain1.com, to test connection back to email@domain2.com.

Results:

Seeing SOA Serial number match: Passed
Warning: The TCP DNS query returned no results.
No MX or A recordes were found for the local domain.
If the records are not configured, incoming mail can fail to be delivered to this server.Both TCP and UDP queries succeeded. Remote DNS passwed.
Connecting to the server failed. Error 10060.
Failed to submit mail to smtp1.domain2.com
Failed to submit mail to smtp2.domain2.com
Failed to submit mail to smtp3.domain2.com

Failed to submit mail to smtp4.domain2.com
----------------------------------------------------------------------------
- Upon checking the Primary and Secondary DNS Server, I confirmed that there were no Conditional Forwarders for domain2.com on either DNS server.

- There was no Address Space for domain2.com in the SMTP connector. But this shouldn't matter since we were allowing * on the address space?


Q1. Whether or not I need to setup a conditional forwarder in the DNS for domain2.com in the Primary and Secondary DNS servers?
and/or
Q2. Whether or not I need to add the domain2.com Address Space to the SMTP connector.


Q3. Is there another configuration step that I am missing to get this to work?

Thanks for taking the time to read through my issue and offer possible solutions to this problem.


Thanks,

it_work_account_09

Need to support users over the internet? click here try our remote control online beta






June 11th, 2012 2:25pm
You don't find an MX record for domain2.com, and that's troubling. If there's no MX record for domain2.com but you know the SMTP server(s) responsible for that mail, then you should create an SMTP connector with domain2.com as the address space and
the responaible SMTP server(s) as the smart hosts.Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Need to support users over the internet? click here try our remote control online beta






June 11th, 2012 2:35pm
Thanks for the reply Ed, that is what I wanted to confirm.

Regards,

it_work_account_09

There is an amazing pack of free network admin tools. click here to download it






June 25th, 2012 7:13am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics