Posts: 11
Joined: 15.Jul.2004
From: USA
Status: offline
Hi all,
I cannot send emails to yahoo.com or aol.com. Our domain has a PTR record, meaning it has a reverse DNS record for the domain. When performing nslookup, it resolves to the proper IP addy. There's only one MX record for this domain.
The system is SBS MS Exchange Svr 2003. It's behind a Pix firewall. I can send mails to other domains, just not these two.
I do not receive any NDRs messages. However, when I go to look at the queue and I cancel one my emails to yahoo, this is what I get This message was rejected due to the current administrative policy by the destination server. Please retry at a later time. If that fails, contact your system administrator. <paradigmventure.com #4.3.2>
I check out at least 3 different sites to verify that I'm not blacklisted.
I can telnet to yahoo.com to get a response. I can also telnet to the mail server from another public source and that works as well.
Posts: 20
Joined: 27.Jul.2004
From: Portugal
Status: offline
hi... have you solved the problem?
I'm having a similar problem with my Exchange Server... I cannot send email to some domains (hotmail.com, msn.com and others included) and they stay in the queue until a timeout NDR is issued. I get these error messages while they're in the queue: - The semaphore timeout period has expired - The connection was dropped by the remote host - Unable to bind to the destination server in DNS - The connection was dropped due to an SMTP protocol event sink
however, I can nslookup all the domains...
also, sometimes I get this error at system's event viewer:
Event ID: 2013 SMTP could not connect to any DNS server. Either none are configured, or all are down.
Event ID: 2012 SMTP could not connect to the DNS server '192.168.10.10'. The protocol used was 'UDP'. It may be down or inaccessible
Posts: 20
Joined: 27.Jul.2004
From: Portugal
Status: offline
the server name is certainly not the problem... it is a simple word...
also, I'm behind a firewall but it worked fine so far. The problem started to happen almost a week ago and I have this server up and running since January without a single problem...
I think the problem might be at the DNS server or at my ISP firewall... They're now checking it...
Posts: 5
Joined: 29.Jul.2004
From: Southern California
Status: offline
I'm having the exact same proble so I don't know if I would be of much help. Now that you have added the reverse entry, can you telnet to yahoo (command: telnet mail.yahoo.com 25).
For me, when I reboot the Exchange Server then all of the messages in queue get released and go to the problematic domains (which are different than your - msn.com, hotmail.com and others). Are you experiencing this also?
Posts: 20
Joined: 27.Jul.2004
From: Portugal
Status: offline
that's strange...
I can't telnet yahoo (although mails sent to yahoo.com are not among the ones with problems) on port 25, but instead I CAN telnet mail.hotmail.com and hotmail.com IS among the domains with problems...
can someone explain this? :-\
and, unlike your server, when I reboot the Exchange Server, nothing changes on the queue: the emails stay there...
I got the same problem I've searched lots of documents by using google.com . Found one guy said that he resolve this problem by call the msn.com tech support. It is a msn.com problem, not our Exchange server?
Posts: 11
Joined: 15.Jul.2004
From: USA
Status: offline
Check the microsoft DNS resolution issues. To work around this issue, turn off the EDNS0 feature in Windows Server 2003. To do this, follow these steps: Install the Dnscmd.exe program from the Windows Server 2003 Support Tools. To install the Windows Support Tools, right-click Suptools.msi in the Support\Tools folder on the Windows Server 2003 CD-ROM, and then click Install. Follow the steps in the Windows Support Tools Setup Wizard to complete the installation of the Windows Support Tools. At a command prompt, type the following command, and then press ENTER: dnscmd /config /enableednsprobes 0
Note Type a 0 (zero) and not the letter "O" after "enableednsprobes" in this command.
The following information appears:Registry property enableednsprobes successfully reset. Command completed successfully. After you run this command, Windows Server 2003 DNS no longer advertises its EDNS0 capabilities. As a result, the Windows Server 2003 DNS server will not be sent UDP packets that are larger than 512 bytes.
Posts: 11
Joined: 15.Jul.2004
From: USA
Status: offline
Also, make sure you are not blacklisted or on the open relay list. Make sure reverse DNS has a record for your domain name. Check to make sure that you can telnet to the mail server for yahoo.com or hotmail.com. Turn off any filters that you may have on the Exchange settings or any SPAM service you may have.
Hi Guys, I got my problem RESOLVED finally . My problem is: cannot send email to msn.com or hotmail.com. The email (which is being sent to msn.com or hotmail.com) is also stuck in the ôQueuesö. My problem is caused by the external DNS server, I always use an old Internet DNS server but it works fine for all the sites except connecting to Hotmail by SMTP. When I change it to a new Internet DNS server, problem resolved. Here is the location of changing the external DNS server: Open your ôExchange system managerö-> ôAdministrative groupsö->öFirst Administrative groupö->öServersö-ôYour Serverö->öProtocolsö->öSMTPö->Right Click ôDefault Virtual Serverö->öPropertiesö->öDeliveryö->Press öAdvancedö Button->Press ôConfigureö Button near the ôConfigure external DNS serversö-> Then remove your old DNS server and add a new one.
I think you should call your ISP and ask them for a GOOD DNS server address. Hope this information will resolve your problem as well.
Posts: 1
Joined: 16.Aug.2004
From: Durban, South Africa
Status: offline
I have exactly the same problem as described by you guys. The domain that my Exchange server is having problems with is Microsoft.com. When a mail addressed to Microsoft.com is submitted all other mails get held up in the queue. The mails are sent when the server is restarted.
If I leave the message in the queue long enough I get the ndr with the message saying This message was rejected due to the current administrative policy by the destination server. Please retry at a later time. If that fails, contact your system administrator. To resolve this situation -
Enable SMTP logging on your default virtual server. To turn on Diagnostics Logging on the MSExchangeTransport service, follow these steps: 1. Start Exchange System Manager. 2. Expand Servers, right-click Your_ Server_Name, and then click Properties. 3. Click the Diagnostics Logging tab, and then click MSExchangeTransport under Services. 4. Under Categories, click the category that you want to log. 5. Under Logging Level, click the appropriate logging level for the issue that you are investigating: o None o Minimum o Medium o Maximum Note: to see event messages turn up the logging level to medium or high. Check to see if you receive the following event messages in Events viewer with event logging turned on.
Event ID 7004 ============
This is an SMTP protocol error log for virtual server ID 1, connection #29. The remote host "E2k3server1.foo.com", responded to the SMTP command "xexch50" with "504 Need to authenticate first ". The full command sent was "XEXCH50 2336 3 ". This will probably cause the connection to fail.
The message is generated when the responding server in the 7004 event does not understand the XEXCH 50 command from your exchange 2003 server, or a firewall blocks the exchange of blobs between the exchange servers.
Note: This is normal if they server indicated in the 7004 is an out_of_ org server or internet servers (E2k or E2k3). Exchange 5.5 with 5.5.2657.72 or higher IMCs will respond back to this with a 7004 event " 505 Authentication required" This is normal when sending to Exchange 55. servers. You can configure this behavior with the HKLM\ System\CurrentControlSet\Services\SMTPSVC\XEXCH50\SuppressExternal to 1.(DWORD) to control Exchange from attempting to send XEXCH50 outside of the org.
|
My Subscription |
My Forums |
Address Book |
Member List |
Search |
FAQ |
Ticket List |
Log Out
Printable Version
All Forums >> [Microsoft Exchange 2003] >> Message Routing >> Cannot send mail to certain domains 
Cannot send mail to certain domains - 
![[Frown]](/image/smiles/frown.gif)
RE: Cannot send mail to certain domains - ![[Confused]](/image/smiles/confused.gif)
I've searched lots of documents by using google.com . Found one guy said that he resolve this problem by call the msn.com tech support. It is a msn.com problem, not our Exchange server?
![[Smile]](/image/smiles/smile.gif)
. My problem is: cannot send email to msn.com or hotmail.com. The email (which is being sent to msn.com or hotmail.com) is also stuck in the ôQueuesö. My problem is caused by the external DNS server, I always use an old Internet DNS server but it works fine for all the sites except connecting to Hotmail by SMTP. When I change it to a new Internet DNS server, problem resolved. Here is the location of changing the external DNS server: Open your ôExchange system managerö-> ôAdministrative groupsö->öFirst Administrative groupö->öServersö-ôYour Serverö->öProtocolsö->öSMTPö->Right Click ôDefault Virtual Serverö->öPropertiesö->öDeliveryö->Press öAdvancedö Button->Press ôConfigureö Button near the ôConfigure external DNS serversö-> Then remove your old DNS server and add a new one.![[Cool]](/image/smiles/cool.gif)
New Messages
No New Messages
Hot Topic w/ New Messages
Hot Topic w/o New Messages
Locked w/ New Messages
Locked w/o New Messages
Post New Thread
