Wednesday, May 23, 2012 5:09 PM
we are unable to send messages to one domain members. I see - 54 5.7.1 Delivery not authorized 1. People on other side say they even does not see our messages to be comming. They also use Exchange.
Single domain, single forest, single Exchange 2010 server.
I used nslookup to find MX record and tryed to telnet to the smtp, and it works fine. But why messages are not delivered? How could I troubleshoot this?
- Edited by natip Wednesday, May 23, 2012 5:44 PM
Wednesday, May 23, 2012 6:18 PM
How many users are having a problem, is it only one user or all users?
Thursday, May 24, 2012 5:06 AMall users unable to reach that domain, is it something wrong with dns? or they are blocking us even they are not see our coming emails??
- Edited by natip Thursday, May 24, 2012 5:08 AM
Thursday, May 24, 2012 5:27 AMModerator
Please contact that domain administrator to check if your server ip is in blacklist.
Please check smtp log and post it here.
Thursday, May 24, 2012 8:29 AM
This error can occur if an Exchange 2010 transport rule rejects a message because the message matched conditions that are configured on the transport rule.
Refer the below article for your reference
The remote server might have other rules defined that are rejecting your message
Try to telnet from your exchange server to host ip holding mx record of the remote domain
Thursday, May 24, 2012 8:38 AM
We do not have Transport rules,
I tryed to telnet to remote MX address and it works fine.
Should remote exchange server check Transport rules also?
and if they say they are fine? is anything I can troubleshoot on my side?
Thursday, May 24, 2012 9:02 AMEnable logging on the send connector, should give you more info, may have enough to say the issue is with the remote host.
Thursday, May 24, 2012 9:31 AM
Check remote server Transport rules also check is there any antispam agent installed on remote server.
Thursday, May 24, 2012 11:54 AM
Diagnostic information for administrators:
Generating server: IS OUR INTERNAL FQDN.
And if thier server checks for IP of this FQDN they can not resolve this.
Is any way to change this - Generating server: to point to our MX?
Thursday, May 24, 2012 12:05 PMelse what they say it may be letter header, but we have problem only with this domain as far I know,
Thursday, May 24, 2012 12:27 PM
Can you post the full NDR?
Did you check the Send Connector logs?
I assume you have your PTR record setup? Check on MX toolbox
Thursday, May 24, 2012 1:01 PM
- Edited by natip Thursday, May 24, 2012 2:35 PM
Thursday, May 24, 2012 1:11 PM
How was you connecting, was this send connector log for the NDR?
Seems like that ISP in Lithuania is not allowing your server to send to it.
Thursday, May 24, 2012 1:25 PM
send connector log? yes I guess,
should I contact ISP about this? I still cant understant where is the problem
Thursday, May 24, 2012 1:36 PM
Sukh, why "Seems like that ISP in Lithuania is not allowing your server to send to it." ?
Thursday, May 24, 2012 1:55 PM
That IP 184.108.40.206 belong to an ISP, which is not accepting your connection, so I would contact them 1st, do you use the below ISP?
Do you use a smart host or DNS lookups?
ISP of this IP [?]: State Enterprise Infostruktura Organization: Centrine Projektu Valdymo Agentura
Thursday, May 24, 2012 2:24 PM
- Edited by natip Friday, May 25, 2012 11:55 AM
Thursday, May 24, 2012 2:27 PMWell that IP is not accepting, ask them why? Ask them to check their logs