Exchange Serv 2k can send but can’t receive

0 pts.
Tags:
Exchange 2000
Exchange Server ActiveSync
Installation
Mail protocols
Microsoft Exchange
Outlook
SMTP
Tech support
Hi I am having an exchange server 2000 running on windows 2k server terminal, and I followed the steps in the article in: http://www.msexchange.org/tutorials/MF002.html to set up the server to send and receive external emails and it is sending but not receiving. I get this message when I try to send from outside: ******************************************************** Your message did not reach some or all of the intended recipients. Subject: RE: test Sent: 30/12/2004 10:00 AM The following recipient(s) could not be reached: Administrator on 30/12/2004 10:01 AM You do not have permission to send to this recipient. For assistance, contact your system administrator. <mymailserver.com #5.7.1 smtp;550 5.7.1 Unable to relay for Administrator@servertosetup.com> user1@servertosetup.com on 30/12/2004 10:01 AM You do not have permission to send to this recipient. For assistance, contact your system administrator. <mymailserver.com #5.7.1 smtp;550 5.7.1 Unable to relay for user1@servertosetup.com> ******************************************************** the MX entry is successful on the domain regstration company, I can ping it and telnet to port 25. The Exchange server uses the DNS IPs supplied by the domain registration company. The port forwarding on the Netgear router (FVS318 Prosafe VPN Firewall) is configured, and the internal DNS has a host entry mail pointing to the internal address of the mail server, any help is appreciated, thank you, Manal
ASKED: December 29, 2004  9:32 PM
UPDATED: January 24, 2005  8:45 PM

Answer Wiki

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

MSKB article# 289553

SYMPTOMS
When you attempt to send mail to an Exchange 2000 Server recipient or Exchange Server 2003 recipient, the message may not be delivered. The sender may receive a non-delivery report (NDR) from the system administrator similar to the following:
The following recipient(s) could not be reached:

User1@domain.com on 11/01/00 8:14 AM

The originator does not have permission to submit message
dns;Sendingdomain.com failed 5.7.1 smtp;550
5.7.1 Unable to relay for User1@domain.com

CAUSE
While there are several causes for this error, the most common one is that there may be no recipient policy for the expected domain in the Exchange 2000 organization or the Exchange 2003 organization.

RESOLUTION
Add a recipient policy for the expected domain. To do so:

1. In Exchange System Manager, expand the Recipients object, then expand the Recipient Policies object.

2. In the right-hand pane, right-click the Default Policy, and then click Properties. Click the E-Mail Addresses tab.

3. Click Add to add a new SMTP address.

4. In the SMTP Address Properties dialog box, in the Address field, enter
@expecteddomain.com
where @expecteddomain.com is the domain that then sender is attempting to send to. Click Apply, and then click OK.

5. In the Default Policy Properties dialog box, click the E-Mail Address tab, and then click to select the check box next to the SMTP address that you just created.

6. Click Apply. Click OK when you receive the following notification:
The e-mail Addresses of type(s) [smtp] have been modified. Do you want to update all corresponding recipient e-mail addresses to match these new address(es)?

NOTES: If you would like to make the new SMTP address the default reply-to address for all users in your Exchange 2000 organization, click the new address, click Set as Primary, click Apply, and then click OK.

If you want to update these addresses immediately, force the Recipient Update Service to update your Exchange server and organization.

Discuss This Question: 5  Replies

 
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
    Hi, If you've tried the above advice and assigned a recipient policy to the domain and still are getting your error, take a look at the Relay Restrictions tab (Exchange Systems Manager -> Administrative Groups -> Exchange Domain -> Servers -> Your Servername -> Protocols -> SMTP -> Virtual Server) right click your virtual server and choose Properties, click the Access tab and click the Relay button. Make sure you have the "Allow all computers which successfully authenticate to relay regardless of the list above." option checked. It is a good idea while your there to make sure you have the "Only the List Below" radio button checked under "Select Which Computers may Relay Through This Virtual Server" section and have your Exchange server's IP address listed and Access Granted displayed. This will lock your server down preventing it from being used as an open relay. This should resolve your problem. Good Luck!
    0 pointsBadges:
    report
  • Mhelal
    Thank you so much, the first solution was already there, and the second solution solved the receiving problem, now I can receive on this server, but I couldn't remember the change that I have done, and disabled the sending now :) it sounds funny, I think I just added in the configure button (in the smtp virtual server properties - delivery tab, clicking on advanced, then clicking on configure), external dns addresses as given to us by the domain registration company + out local dns ips, thanks you for your help,
    0 pointsBadges:
    report
  • Mhelal
    no, it just took too long to send, I received email from the administrator@testdomain.com; I am still testing the remaining users, thank you again,
    0 pointsBadges:
    report
  • Petroleumman
    Good Morning, Under the 'Advanced Delivery' tab - Configure External DNS, you want to list ONLY addresses to your external DNS hosts (where your public MX records reside). Do Not include ip's which point to your AD DNS source. You want to keep AD DNS and public DNS seperate. Be sure to include the addresses for redundant servers as well. Your ISP or DNS host will provide you a list of the primary and all secondary servers. Also, make sure you have an entry listed in the 'Fully Qualified Domain Name' field as well. You can click the 'Check DNS' button to confirm that your entry is valid. Exchange 2000 or 2003 does not require a reboot after changes but should you experience a lag in your delivery time after making changes, it dosen't hurt to stop and start the SMTP service to force a refresh or even reboot the entire server. If you still have latency issues and feel you have configured your server correctly,compare the delivery time between internal mail and external (internet mail). If your problem is with the internet mail only, ping the external DNS servers and check your response times. If your getting time outs or delayed response, contact your DNS host as they may be having an issue. Good Luck!
    0 pointsBadges:
    report
  • Mhelal
    Hi petroleumman and all When I fist done the previous changes, it delayed the sending outside, but then it successfuly sent, but after a while it stopped sending at all, and return delivery failure messages to all domains I am trying to send to. As you said, I pinged the domain for the mail servers I am sending to, and they are reachable, I send my ISP dns servers, and they reply back, and I removed any local dns servers, and restarted the server, and the problem persists, Will you or anyone gove more ideas to trouble shoot this one, thank you very much for your help, Manal
    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