NDR New exchange install

0 pts.
Tags:
Exchange security
Microsoft Exchange
NDR New exchange install have been running a fresh exchange install for 2 weeks. The users were able to send and recieve mail fine. Now they get a NDR instanly after they send any email. Would it be, because the domain they are sending it to is block by the ISP? I just turned on message filtering in the default smtp virtual server. I checked Apply sender filter, recipient filter, sender ID filter, and intelligent message filter. Do you think this will help? I also changed the diagnostics logging for SMTP protocol, queuing engine, and connection manager to maximum all the rest are medium. Where are these logs? Here is the errors. Your message did not reach some or all of the intended recipients. Subject: Request for stucco sample Sent: 12/7/2006 11:17 AM The following recipient(s) could not be reached: username@yahoo.com on 12/7/2006 11:17 AM You do not have permission to send to this recipient. For assistance, contact your system administrator. MSEXCH:MSExchangeIS:/DC=local/DC=archilogix:SERVER Event Type: Error Event Source: MSExchangeTransport Event Category: SMTP Protocol Event ID: 7010 Date: 12/7/2006 Time: 3:59:23 PM User: N/A Computer: SERVER Description: This is an SMTP protocol log for virtual server ID 1, connection #152. The client at "66.36.241.109" sent a "rcpt" command, and the SMTP server responded with "550 5.7.1 Unable to relay for Not.abuse.see.www.DNSreport.com.from.IP.67.164.67.45@DNSreport.com ". The full command sent was "rcpt TO:<Not.abuse.see.www.DNSreport.com.from.IP.67.164.67.45@DNSreport.com>". This will probably cause the connection to fail. For more information, click http://www.microsoft.com/contentredirect.asp. Event Type: Error Event Source: MSExchangeTransport Event Category: SMTP Protocol Event ID: 7004 Date: 12/7/2006 Time: 4:02:15 PM User: N/A Computer: SERVER Description: This is an SMTP protocol error log for virtual server ID 1, connection #153. The remote host "64.142.7.162", responded to the SMTP command "rcpt" with "550 5.7.1 <username@yahoo.com>... Relaying denied. Proper authentication required. ". The full command sent was "RCPT TO:<username@yahoo.com> ". This will probably cause the connection to fail.
ASKED: December 8, 2006  11:49 AM
UPDATED: December 11, 2006  10:46 AM

Answer Wiki

Thanks. We'll let you know when a new response is added.

c:windowssystem32logs is the default SMTP log location.

You could be black listed, check out www.dnsstuff.com and look for your domain in the black lists.

We had similar issue when we did not have a reverse lookup on our MX record. Or the filters you setup could be incorrectly configured.

Discuss This Question: 1  Reply

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
  • Petroleumman
    Hello, Unfortunatley this is not one of those cut and dry errors with a single cause and solution. This error can be generated because of a number of reasons. That said, let's look at your scenario, new install. Possibly you overlooked some basic security measures during configuration which may have resulted in your server being blacklisted. Check the following settings to confirm your server is not an open relay; Open Exchange System Manager and navigate to your smtp virtual servers properties. Click the access tab and then relay. Confirm you have placed a check in the box "Allow all computers which successfully authenticate to relay regardless of the list above". Leaving this unchecked can result in your server becoming an open relay. This is a sure fire way to quickly get blacklisted! You confirm that you have your server properly locked down and have checked the blacklist status of your server (www.spews.org amongst others can help)check that you have an SPF (sender policy framwork) record set up on your external DNS. This type of record is quickly becoming a requirement with newer mail organizations. What it does essentially is confirm that you are who you say you are to another mail server. Many organizations such as Yahoo, MSN, Hotmail etc. are now starting to require this type of record as a means of thwarting spam. Not having this record could result in your error. If not the cause, having this record listed with your external DNS is a good thing as it may save some headaches down the road. Everything is clean to this point? Now look at how your mail is sent. Do you relay through an ISP? Use a Smarthost? Have an antivirus application running etc.? Any of these could be the source of the error. Try turning off any that apply one by one and test. If the problem goes away with any one of these then you've started to narrow down the culprit. Contact your Smarthost provider, ISP or AV vendor for assistance. Depending on the vendor, you may need to push them to help, but persistance will prevail. We had a personal experience with this error at our company when sending mail to Hotmail accounts and after several days of trial and error found the culprit to be with our Symantec corporate AV solution. Upgrading to the latest version which had some bug fixes for Exchange helped resolve the issue. As for Exchange server's mail filters, these are all good tools to help keep control the flow of and/or the source of inbound mail to your server but have no affect on what your sending out. It's outbound mail that is responsible for the NDR's. Hopefully some of this will help you out. Good luck!
    0 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Thanks! We'll email you when relevant content is added and updated.

Following