Discuss This Question: 3  Replies There was an error processing your information. Help Desk » Inventory » Monitor » Community » Home Exchange 2003, can't send mail.

This rules out any network / server / IP Block issues. We send our own mail using smtp. Under Exchange System Mannger, Connectors and created a new Connector and under "Forward all mail through this connector to the following smart host" I used my ISP's Mail address and now It seems to be a classical "relay not allowed" problem on server, or other server issue, and not a client problem.

Verify the recipient information, generating server and the diagnostic information from the NDR After obtaining the NDR, check the delivery status notification and the server generating NDR to resolve the issue. Home The Team Contact us -MS Exchange Guru Disclaimer MSExchangeGuru on YouTube « Virtual Tech Conference sessions on Exchange server 2013 Troubleshooting Backpressure in Exchange Server » Exchange Server - If there is one, try disabling it Exchange 2003: E-mails stuck in queue Use the exchange system manager to check the queue. Backpressure: Backpressure issues account to most of the email queue building issues.

Help Desk » Inventory » Monitor » Community » Search IT Knowledge Exchange Join / Login IT Knowledge Exchange a TechTarget Expert Community Questions & Answers Discussions Blogs Tags Welcome to https://community.spiceworks.com/topic/29834-exchange-2003-i-can-send-but-i-can-t-receive Performing the NSLookup Go to Command Prompt Key in NSLOOKUP and Press Enter Enter server {required IP of DNS server} Press Enter Enter the following Set q=MX Now if you enter Is your email id [email protected] Error in Queue – An SMTP protocol error occurred.

Please enter a reply. http://kelcours.com/exchange-2003/exchange-2003-cannot-receive.html I have direct SAT via STP singapore. Backpressure events look like this: Log Name: Application Source: MSExchangeTransport Date: 4/17/2013 7:00:34 AM Event ID: 15004 Task Category: ResourceManager Level: Warning Keywords: Classic User: N/A Computer: HUBServerName Description: Resource pressure I actually got some non deliverable mail from lunarpages.

IT: so here's your MX record breakdown:   > set q=mx > mail.netprofession.net Non-authoritative answer: mail.netprofession.net  canonical name = mail.mxes.net > set q=a > mail.mxes.net Name:    mail.mxes.net Address:  216.86.168.198   The first step in resolving this error is to check the recipient address and send the message again.

Also, examine the SMTP recipient policy and ensure that each mail domain This error can also occur if you try to accept anonymous messages from the Internet by using a Hub Transport server that has not been configured to do this. Check This Out Ask a question, help others, and get answers from the community Discussions Start a thread and discuss today's topics with top experts Blogs Read the latest tech blogs written by experienced

My Internal EMail is ok. MX --> server 1 2. Control Panel, Mail icon.

If this is the case, Outlook may not have updated the recipient cache correctly.

Privacy statement  © 2016 Microsoft. Internet works perfectly fine. For more information about transport rules, see Understanding Transport Rules. 5.7.1 Unable to relay The sending e-mail system is not allowed to send a message to an e-mail system where that Please try again later.

thanks for the help ! Everything else seems fine, i have tried google search after google search but cannot seem to find anything relevant. Find out the time from which the user started facing the issue and if the user was able to send emails prior to that. this contact form Thanks.

Except changing over the ADSL Modem (which i dont think is the problem), and Re-installing ISA and/or Exchange (which i don't really want to do) Any help would be greatly appreciated. Please let me know your outbound mailflow.   Some information may help you troubleshoot the issue:   Non-Delivery Report Issues http://technet.microsoft.com/en-us/library/bb397219.aspx   Mike   Marked as answer by Mike Shen Thursday, Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the This ensures that MX record has been properly configured Make sure that NCSA logging is enabled and find errors in them.

Register Hereor login if you are already a member E-mail User Name Password Forgot Password? Posted July 29th, 2013 under Exchange 2003, Exchange 2007, Exchange 2010, Exchange 2013. I was actually at a complete loss! This outage lasted for around 5 hours.I need to provide the details about to Problem Management: 1.

Prior to the Send/Receive process the email does sit in the outbound queue (Outbox). Repeat the above section's procedures for different types of errors. Check if NIC specified for the receive connector is correct. Examine and correct the legacy DN of the recipient's mailbox.