transport >> 550 5.7.1 Unable to relay

by Ron » Sun, 28 Dec 2003 07:54:15 GMT

We currently have three active email domains on our server
and have been attempting to add another one for several
days now. Internal email to addresses in NewDomain.com
work flawlessly. Whenever someone externally attempts to
send an email to NewDomain.com they receive an error '550
5.7.1 Unable to relay for XXXX@XXXXX.COM '.

We have set Recipient Policies, POP3 Virtual Server, SMTP
Virtual Server, SMTP Connectors and IP Packet Filters
(POP3, SMTP). Attached is a Word document with those
settings.

What steps can be taken to get this fourth mail domain to
work?

Thank you, Ron


transport >> 550 5.7.1 Unable to relay

by Mark Fugatt [MVP] » Sun, 28 Dec 2003 13:14:26 GMT


Did you check the checkbox on the Recipient Policy.

--
Mark Fugatt
Exchange MVP
http://www.exchangetrainer.com
http://www.msexchange.org

transport >> 550 5.7.1 Unable to relay

by Ron » Tue, 30 Dec 2003 02:07:42 GMT

Mark,

Yes, it is set. Still no luck.

Ron

transport >> RE: 550 5.7.1 Unable to relay

by Kenwood » Sun, 11 Jan 2004 10:38:56 GMT


Hello Ron,

Thank you for your post.

Unfortunately I can't see the document, so I can't see your settings. It is possible one of your other settings is conflicting
with the ability to receive email. Remove all settings pertaining to this new domain. The ONLY place that needs to be set
for the ability to receive mail is the Recipient policy. The other areas you mentioned have other purposes, and are not
used to receive email, and in the case of the connector can actually negatively affect the ability to use that SMTP
namespace. Connectors are for outbound/external mail only.

Kenny Wood
CISSP, MCSE
PSS Security
Microsoft Corporation
--

This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to
the terms specified at http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this message are best directed to the newsgroup/thread
from which they originated.
{\rtf1\ansi\ansicpg1252\deff0\deflang1033{\fonttbl{\f0\fnil\fprq2\fcharset0 MS Sans Serif;}}
\viewkind4\uc1\pard\f0\fs20 Hello Ron,
\par
\par Thank you for your post.
\par
\par Unfortunately I can't see the document, so I can't see your settings. It is possible one of your other settings is conflicting with the ability to receive email. Remove all settings pertaining to this new domain. The ONLY place that needs to be set for the ability to receive mail is the Recipient policy. The other areas you mentioned have other purposes, and are not used to receive email, and in the case of the connector can actually negatively affect the ability to use that SMTP namespace. Connectors are for outbound/external mail only.
\par
\par Kenny Wood
\par CISSP, MCSE
\par PSS Security
\par Microsoft Corporation
\par --
\par
\par This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm
\par
\par Note: For the benefit of the community-at-large, all responses to this message are best directed to the newsgroup/thread from which they originated.
\par }

transport >> 550 5.7.1 Unable to relay

by Darin Roulston [MSFT] » Wed, 14 Jan 2004 04:15:59 GMT

Ron,
Does inbound mail pass through any other servers before hitting yours? To
ensure that it is indeed Exchange that is rejecting mail to the new domain I
would test by telnetting directly to Exchange locally over port 25 (follow
Q153119 for instructions). If it is Exchange that is rejecting (550 relay
prohibited) then ensure that you check the box on the recipient policy, also
right-click and apply the policy. If it still isn't taking effect you may
want to turn up logging for the MSExchangeMU service to max then restart the
System Attendant. Restarting the System Attendant forces the metabase update
service to reinitialize and any problems with writing the changes you've
made to the Active Directory down to the Metabase may be reported in your
application log.

--
Darin Roulston
Microsoft PSS

Please do not send e-mail directly to this alias. This alias is for
newsgroup purposes only.

This posting is provided "AS IS" with no warranties, and confers no rights

transport >> RE: 550 5.7.1 Unable to relay

by Ron » Thu, 22 Jan 2004 06:48:07 GMT

Kenny,

Thank you for your response. I have attempted what you
recommended and still receive the same error. It is
strange that two email domains work perfectly and when I
add another with the exact settings except for IP Address
and domain, it fails. It works internally but any email
from outside the organization bounces.

Ron

your settings. It is possible one of your other settings
is conflicting
pertaining to this new domain. The ONLY place that needs
to be set
The other areas you mentioned have other purposes, and are
not
can actually negatively affect the ability to use that
SMTP
only.
confers no rights. Use of included script samples are
subject to
http://www.microsoft.com/info/cpyright.htm
responses to this message are best directed to the
newsgroup/thread

transport >> 550 5.7.1 Unable to relay

by rkoester » Thu, 22 Jan 2004 10:11:44 GMT


Darin,

This is on a Small Business Server 2000 box using IIS, ISA, and
Exchange on the same server.

Recipient Policies check out as per your recommendation.

How does one go about turninp up logging for the MSExchangeMU service
to max?

Ron






rkoester
------------------------------------------------------------------------
Posted via http://www.mcse.ms
------------------------------------------------------------------------
View this thread: http://www.mcse.ms/message219267.html

Similar Threads

1. 550 5.7.1 Unable to relay & 550 5.1.1 RESOLVER.ADR.ExRecipNotFound - Microsoft Exchange Server

2. 550 5.7.1 Unable to relay & 550 5.1.1 RESOLVER.ADR.ExRecipNotF

No Spelling mistakes, ive found some good information regarding the 5.1.1 
issue. I believe it happened since i deleted the mailbox and created it 
several times. It works normally through OWA. The issue is related to the 
smtp address saved in the AD. 

Regarding the other issue, i guess we were blacklisted somewhere...

Thank you,
-- 



"Ed Crowley [MVP]" wrote:

> Check the spelling of those users' SMTP addresses.
> -- 
> Ed Crowley MVP
> "There are seldom good technological solutions to behavioral problems."
> ..
> 
> "Goldenberg" < XXXX@XXXXX.COM > wrote in message 
> news: XXXX@XXXXX.COM ...
> >I have the following:
> >
> > - Exchange server 2007 on top of W2k3 server installed on one machine.
> > - Relaying to the ISP smart host, configured on the Send Connector.
> > - Different domains configured in the accepted domain list and recepient
> > policies
> > - All emails are wokring on all domains internal and external, incoming 
> > and
> > outgoing except for 2 specific users on domain.com. These 2 specific users
> > can receive only external emails. If i send internal email to one of these 
> > 2
> >  XXXX@XXXXX.COM , i receive this message:
> >
> > "Delivery has failed to these recipients or distribution lists"
> >
> > #550 5.1.1 RESOLVER.ADR.ExRecipNotFound; not found ##
> >
> > Moreover, if i send an email from one of these 2  XXXX@XXXXX.COM  to 
> > hotmail
> > or any other address, it doesnt deliver to destination nor i get a
> > notification failure knowing that the queues at the server are clean in
> > addition to that there is no mail filter application.
> >
> > I tried to use the SMTP commands to send a test email as follows:
> > - I telnet the server port 25
> > - helo
> > - mail from:  XXXX@XXXXX.COM 
> > - rcpt to:  XXXX@XXXXX.COM 
> >
> > i receive this message:
> >
> > "550 5.7.1 Unable to relay"
> >
> > I hope i have listed all the information required to help me.
> >
> > Thank you,
> > 
> 
> 

3. Configure for Open Relay: 550 5.7.1 Unable to relay for someone@somewhere.com - Manage MS Exchange Server

4. SMTP server responded with "550 5.7.1 Unable to relay

We currently have a Windows SBS 2003 server.  Exchange has been installed and 
working correctly on the server.  We had a domain miltonconstruction.com.  We 
are forwarding all of our mail over to a new domain name miltonhayes.com.  I 
added the domain as the default domain in the recipient policy.  The mail 
goes out with the correct domain name on the email, however if you try to 
send or reply to the new domain (miltonhayes.com) it gives the following 
error message:

This is an SMTP protocol log for virtual server ID 1, connection #6. The 
client at "64.233.178.249" sent a "rcpt" command, and the SMTP server 
responded with "550 5.7.1 Unable to relay for  XXXX@XXXXX.COM   ". The 
full command sent was "rcpt TO:< XXXX@XXXXX.COM >".  This will probably 
cause the connection to fail. 

I called the web hosting company and they said that the mx record for both 
of the domains is pointed to our IP.  Does anybody know what might be causing 
this issue and how to resolve?  

Thanks

5. 550 5.7.1 Unable to relay problem - Manage MS Exchange Server

6. #5.7.1 smtp;550 5.7.1 Unable to relay

For the past week, we've been getting these NDR's.  It happens from multiple 
domains, but randomly.  Sending an email will fail one time, then work when 
it is resent.

You do not have permission to send to this recipient.  For assistance, 
contact your system administrator.
<ourdomain.com #5.7.1 smtp;550 5.7.1 Unable to relay for 
 XXXX@XXXXX.COM >

Nothing has changed on our end.  I'm not sure what is going on.  Can anyone 
help shed some light?

Thanks! 


7. #5.7.1 smtp;550 5.7.1 unable to relay from reporting services - Manage MS Exchange Server

8. 550 5.7.1 Unable to relay

Hi, I have Exchange 2003 server enterprise on a w2k sp4 server. I have more than a thounsan users a I have one who is continously receiving a 5.7.1 message from the server. (550 5.7.1 Unable to relay for name@domain) He is using Outlook XP as a client. Anyone has a idea ???