An NDR? Let's parse it shall we...

SMTP -- Hopefully we all know what this is. If not, please step away
from the Exchange server.

550 - Permanent Fatal Error described in RFC2821. You have read that
right? Being a mail admin and all it's kinda important. 

5.7.1 - Enhanced error reporting. Why someone felt this shite was
enhanced is beyond me, but look it up in the RFCs, since this thread ran
over 10 responses it probably can't hurt. 

Now let's get down to brass tacks shall we?

Relaying denied - Damn Clyde, that seems pretty straightforward. The
server no likey relay. Now is it happening for all domains? According to
your earlier post it isn't. You don't specifically state users can send
to other domains, but then there's lots of stuff not stated. But hey at
least you included the NDR, eventually... that's more than some people
do. 

You must check for new mail before sending - Well, that's a POP Before
AUTH sounding error message. When did they add that to Exchange. Oh
wait... they didn't. So if Exchange isn't telling you to POP Before
AUTH, some other server must be... but what server and why?

Search for the recipient's address in the SMTP protocol logs on the
Exchange server. I'm sure those are enabled and logging is cranked right
up. What is the IP address of the server being contacted? Figure out who
owns that. Compare the DNS results on the Exchange server to DNS results
for the domain elsewhere. 

We parsed through another NDR using nslookup yesterday, track that one
down and take a look. I might have done that again here, but no domain
was provided that I can see so... kinda tough. 

So let's talk about the troubleshooting steps so far. When everything
else is working but something for one user and just to a couple of
domains, don't assume your server is broken and start changing settings
willy nilly. 

>I enable allow all computers to
> authenticate
> for relay on the SMTP connected 

So you changed your server to be an open relay? Yeah, that's probably
not good. Out of the box, Exchange only allows authenticated users to
relay. Probably shouldn't change that without a. a very good reason and
b. knowing exactly what the change you are making does. 

>and allow added the recipients domain to
> the
> recipient policy as per some documentations. 

As others have noted, unless you are responsible for a domain, adding it
to your recipient policy is generally not a good idea. That doesn't seem
to scale well does it? Adding millions of domains to your recipient
policies so you can send them e-mail? We'd all use Lotus Notes if
Exchange sucked that bad... well, no we wouldn't but still, that'd
really suck. 

So after you enable SMTP logging, add the appropriate parameters to log
and check the SMTP logs you'll have some decent information to start
troubleshooting with. 

> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:bounce-
> [EMAIL PROTECTED] On Behalf Of Theo Odartei
> Posted At: Friday, September 17, 2004 2:15 PM
> Posted To: swynk
> Conversation: exchange2003 non-delivery after joined to exchange2000
admin
> group
> Subject: RE: exchange2003 non-delivery after joined to exchange2000
admin
> group
> 
> The moment I removed it, I went back to the original message of
> " You do not have permission to send to this recipient.  For
assistance,
> contact your system administrator. #5.7.1 smtp;550 5.7.1 .. Relaying
> denied: You must check for new mail before sending"
> 
> 
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of
> Fyodorov, Andrey FTL
> Sent: September 17, 2004 3:10 PM
> To: Exchange Discussions
> Subject: RE: exchange2003 non-delivery after joined to exchange2000
> admin group
> 
> ***I had a feeling*** that you added those domains to your Exchange
> server's
> recipient policy. Take them out. By putting a domain name into YOUR
> recipient policy you declare that YOUR server is responsible for that
> domain. When you send mail to that domain, your Exchange server sees
it
> in
> its own recipient policy and tries to find the address locally, in its
> own
> AD instead of trying to send the message to the Internet.
> 
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of
Theo
> Odartei
> Sent: Friday, September 17, 2004 3:06 PM
> To: Exchange Discussions
> Subject: RE: exchange2003 non-delivery after joined to exchange2000
> admin
> group
> 
> 
> Yes it worked with yahoo but not from my domain. However I made two
> changes
> and I noticed that has changed the error to
> ""The e-mail account does not exist at the organization this message
was
> sent to.  Check the e-mail address, or contact the recipient directly
to
> find out the correct address"" I enable allow all computers to
> authenticate
> for relay on the SMTP connected and allow added the recipients domain
to
> the
> recipient policy as per some documentations. \
> 
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of
> Fyodorov, Andrey FTL
> Sent: September 17, 2004 2:54 PM
> To: Exchange Discussions
> Subject: RE: exchange2003 non-delivery after joined to exchange2000
> admin
> group
> 
> Are those domains outside of your organization?
> 
> Can you send to those addresses from a third-party place like hotmail
or
> yahoo?
> 
> Try to validate these addresses using http://www.dnsreport.com - just
> plug
> the e-mail address on the right side and click Mail Test.
> 
> 
> 
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of
Theo
> Odartei
> Sent: Friday, September 17, 2004 2:38 PM
> To: Exchange Discussions
> Subject: RE: exchange2003 non-delivery after joined to exchange2000
> admin
> group
> 
> 
> 
> Two of my users are having a problem sending mail to a couple of
domains
> error is "The e-mail account does not exist at the organization this
> message
> was sent to" I have applied every suggestion from Microsoft but
nothing
> seem
> to work. I even used my account to send but no luck. Anyone have any
> idea?




_________________________________________________________________
List posting FAQ:       http://www.swinc.com/resource/exch_faq.htm
Web Interface: 
http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchange&text_mode=&lang=english
To unsubscribe send a blank email to [EMAIL PROTECTED]
Exchange List admin:    [EMAIL PROTECTED]
To unsubscribe via postal mail, please contact us at:
Jupitermedia Corp.
Attn: Discussion List Management
475 Park Avenue South
New York, NY 10016

Please include the email address which you have been contacted with.

Reply via email to