Link to home
Create AccountLog in
Avatar of jonha134
jonha134

asked on

Exchange 2010 emails not properly sent to a certain domain

For some reason mails are not properly sent to the domain company.com from our Exchange 2010 server. After a while the sender gets a 4.4.7 timeout respone.

This is the log from company.com exchange server:
Incoming SMTP call from 192.x.x.x.x at 16:50:48.
Reverse DNS Lookup for x.x.x.x initiated at 16:50:48.
Reverse DNS Lookup for x.x.x.x completed at 16:50:48.
Address x.x.x.x resolves to mail.ourdomain.com.
<<< 220 mail-gw4.company.com
>>> EHLO mail.ourdomain.com
<<< 250-mail.company.com
250-SIZE 52428800
250-ETRN
250-STARTTLS
250-ENHANCEDSTATUSCODES
250-X-IMS 5 -1
250-DSN
250-VRFY
250-AUTH LOGIN
250-AUTH=LOGIN
250 8BITMIME
>>> STARTTLS
<<< 220 2.0.0 Ready for SSL/TLS
>>> EHLO mail.ourdomain.com
<<< 250-mail.company.com
250-SIZE 52428800
250-ETRN
250-ENHANCEDSTATUSCODES
250-X-IMS 5 -1
250-DSN
250-VRFY
250-AUTH LOGIN
250-AUTH=LOGIN
250 8BITMIME
Incoming SMTP (SSL/TLS) call from mail.ourdomain.com completed at 16:50:48.

Open in new window


This is the log from our send connector:
attempting to connect	
220 mail-gw4.company.com	
EHLO mail.ourdomain.com	
250-mail.company.com	
250-SIZE 52428800	
250-ETRN	
250-STARTTLS	
250-ENHANCEDSTATUSCODES	
250-X-IMS 5 -1	
250-DSN	
250-VRFY	
250-AUTH LOGIN	
250-AUTH=LOGIN	
250 8BITMIME	
STARTTLS	
220 2.0.0 Ready for SSL/TLS	
Sending certificate	
CN=mail.ourdomain.com, OU=TRUSTZONE UC SSL, OU=Provided by TRUSTZONE, OU=ourdomain.com, O=OURDOMAIN.COM, STREET=N/A, L=CITY, S=CITY, PostalCode=11111, C=SE	Certificate subject
CN=USERTrust Legacy Secure Server CA, O=The USERTRUST Network, L=Salt Lake City, S=UT, C=US	Certificate issuer name
652E7D2F2F04B	Certificate serial number
45A9BA9BE77A6	Certificate thumbprint
mail.ourdomain.com	Certificate alternate names
Received certificate	
2BC19BC1CA369	Certificate thumbprint
EHLO mail.ourdomain.com	
Remote	

Open in new window


What could be the issue?
Avatar of Manpreet SIngh Khatra
Manpreet SIngh Khatra
Flag of India image

Have they made any changes to their firewall or gateway servers ?
Are you having any issues with sending email to any other external domain ?
Hope they arent blacklisted :)

- Rancy
If there is a timeout issue only for a particular domain, here is what i would check.

1) if my DNS is able to resolve it correctly (i.e if my send connector uses DNS to route emails, if it is set to Smart host - I'll check the IP Address of my smart host)

2) If using gmail or hotmail email gets delivered to the other domain

3) If the above two are set correctly, I'd simply recommend to create a new send connector, set the recipient domain's MX Record as its smart host, add the recipient domain as address space. And you're set.

Regards,
Exchange_Geek
Avatar of jonha134
jonha134

ASKER

Thanks for quick and helpful advice.

The problem is only for a specific domain (company.com) as far as I know.

company.com can receive email from all other domains except our.

Our send connector is using DNS. Using nslookup q=MX on the Exchange server it can correctly determine the mailhost of company.com.

I tried to set up a send connector specificallly for the troublesome domain:
FQDN response: mail.ourdomain.com
Address space: SMTP *.company.com
Network: Route through smart host: mail-gw4.company.com
Source server: [our exchange server]
This did not help, the issue remains the same.

Any other suggestions?
ASKER CERTIFIED SOLUTION
Avatar of Exchange_Geek
Exchange_Geek
Flag of India image

Link to home
membership
Create an account to see this answer
Signing up is free. No credit card required.
Create Account
Great, thanks!

It turned out that the antivirus control on the Firewall for some reason interrupted the communication.

Regards,
Jonas