Exchange 2010 Smtp Error 550 5.7.1
(עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeOnline20132010Other VersionsLibraryForumsGalleryEHLO Blog Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered by: Exchange 2010 5.7.1 unable to relay Previous Versions of Exchange > Exchange Server 2010 Question 0 Sign in to vote I'm trying to allow email notification from my application server to relay off exchange 2010. it only gives me an error when i try to email an external address. here's what happened when i telnet to port 25. EHLO MAIL FROM:testA@ourdomain.ORG 250 2.1.0 Sender OK RCPT TO:test@HOTMAIL.COM 550 5.7.1 Unable to relay 451 4.7.0 Timeout waiting for client inputGerald Rama Tuesday, March 29, 2011 6:49 PM Reply | Quote Answers 1 Sign in to vote check out http://exchangeserverpro.com/how-to-configure-a-relay-connector-for-exchange-server-2010 Marked as answer by Novak Wu Friday, April 08, 2011 6:16 AM Tuesday, March 29, 2011 6:53 PM Reply | Quote All replies 1 Sign in to vote check out http://exchangeserverpro.com/how-to-configure-a-relay-connector-for-exchange-server-2010 Marked as answer by Novak Wu Friday, April 08, 2011 6:16 AM Tuesday, March 29, 2011 6:53 PM Reply | Quote 0 Sign in to vote As an additional information, I would like to share you the following article to configure a relay connecter. http://blogs.technet.com/b/exchange/archive/2006/12/28/3397620.aspx Thanks. NovakPlease remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Friday, April 01, 2011 2:52 AM Reply | Quote 0 Sign in to vote Hi Gerald, In Addition with above folks. This error message os expected one. Default receive connector only allow you to relay message to internal users (anonymous accesss on default receive connector). For relay to internet users, you must have to create one new receive connector and configure it for relay. Configure your nre receive connector as per below
Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Server Fault Questions Tags Users Badges Unanswered Ask Question _ Server Fault is a question and answer site for system and network administrators. 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 https://social.technet.microsoft.com/Forums/exchange/en-US/ab3105d5-2948-4a35-8291-81f644ac8957/exchange-2010-571-unable-to-relay?forum=exchange2010 up and rise to the top Exchange 2010 550 5.7.1 unable to relay up vote 0 down vote favorite I have a website application that needs to send email via our Exchange servers. It sends email internally fine, but when sending to an external address I get the 550 5.7.1 unable to relay error. I followed this guide to create a connector to allow relay. Unfortunately, all http://serverfault.com/questions/399775/exchange-2010-550-5-7-1-unable-to-relay office email was trying to use that connector and was not being routed correctly. It also appeared as though it opened it up for spammers to use. This is obviously unacceptable and a secure method is needed. exchange smtp authentication share|improve this question asked Jun 18 '12 at 14:18 isorfir 103113 add a comment| 3 Answers 3 active oldest votes up vote 0 down vote accepted In your new scope did you only setup the IP of the web server as being able to send mail? If you limit the connector to only receive mail from your webserver that should take care of it. Alternatively if you can setup your web app to use authenticated SMTP sessions you wouldn't need a new connector. share|improve this answer answered Jun 18 '12 at 14:26 tparker 512 I was actually able to do both, looks like we were on the same track. Thanks tparker. –isorfir Jun 18 '12 at 15:15 add a comment| up vote 2 down vote This problem occurs because by default the receive connector in Exchange Server 2007 does not have its default domain value set. This is unlike the behavior in Exchange 2000 or 2003 where it auto
got me frustrated not because I couldn't solve right away but because I've come across this before but forgot what http://terenceluk.blogspot.com/2011/10/unable-to-relay-mail-to-external-domain.html I did to solve it so now that I've resolved the issue, http://exchangeserverpro.com/how-to-configure-a-relay-connector-for-exchange-server-2010/ I figure I'd blog it so I can reference this blog in the future. I encountered the problem when I completed the setup of a new Kiwi Syslog server which allowed me to send VMware Data Recovery reports and logs to and in turn email recipients so exchange 2010 they would know whether the daily backups were successful or not. The environment had Exchange Server 2010 as their messaging service and I've configured numerous Exchange Receive Connectors for mail relaying for various devices but as I completed my syslog configuration and executed a test email to be sent to my email address, the email never came. I initially exchange 2010 smtp thought it was something minor such as firewall or IP address so I went ahead and checked the obvious. After going through the configuration numerous times to verify I haven't made any mistakes, I realized that I wasn't anywhere closer to solving the problem. Seeing how I wasn't really getting anywhere, I began reviewing the logs from the syslog server which showed the following: 2011-10-05 16:45:10 PI Message to: tluk@ccs.bm, adminterence@domain.bm2011-10-05 16:45:10 PI Message from: vdr01@domain.bm2011-10-05 16:45:10 PI Subject: Syslog message from vc03 - vDR traffic2011-10-05 16:45:10 PI Date: Wed, 05 Oct 2011 16:45:10 -03002011-10-05 16:45:20 PI Mail error: 550 5.7.1 Unable to relay Then I proceeded to turn on verbose logging on the Exchange 2010 Hub Transport server's receive connector handling the connection and navigated to the path: C:\Program Files\Microsoft\Exchange Server\V14\TransportRoles\Logs\ProtocolLog\SmtpReceive … where the log was written: Opening up the logs showed the following: #Software: Microsoft Exchange Server#Version: 14.0.0.0#Log-type: SMTP Receive Protocol Log#Date: 2011-10-05T19:17:57.149Z#Fields: date-time,connector-id,session-id,sequence-number,local-endpoint,remote-endpoint,event,data,context2011-10-05T19:17:57.149Z,CAS01\VC03,08CE51AA847AC9C0,0,10.10.1.59:25,10.10.1.53:49654,+,,2011-10-05T19:17:57.149Z,CAS01\VC03,08CE51AA847AC9C0,1,10.10.1.59:25,10.10.1.53:49654,*,SMTPSubmit SMTPAcceptAnySender SMTPAcceptAuthoritativeDomainSender AcceptRoutingHeaders,Set Session Permissions2011-10-05T19:17:57.149Z,CAS01\VC03,08CE51AA847AC9C0,2,10.10.1.59:25,10.10.1.53:49654,>,"220 CAS01.domainnet.com Microsoft ESMTP MAIL Service ready at Wed, 5 Oct 2011 16:17:56 -0300",2011-10-05T19:17:57.164Z,CAS01\VC03,08CE51AA847AC9C0,3,10.10.1.59:25,10.10.1.53:49654,<,EHLO vc03,2011-10-05T19:17:57.164Z,CAS01\VC03,08CE51AA847AC9C0
Availability Migration You are here: Home / Tutorials / How to Configure a Relay Connector for Exchange Server 2010How to Configure a Relay Connector for Exchange Server 2010 August 19, 2010 by Paul Cunningham 271 Comments In most Exchange Server 2010 environments there will be the need to allow relaying for certain hosts, devices or applications to send email via the Exchange server. This is common with multi-function devices such as network attached printer/scanners, or applications such as backup software that send email reports. SMTP communication is handled by the Hub Transport server in an Exchange organization. The transport service listens for SMTP connections on it's default Receive Connector. However, this connector is secured by default to not allow anonymous connections (ie, the type of connection most non-Exchange systems will be making). You can see this in effect if you telnet to the server on port 25 and try to initiate unauthenticated SMTP communications. 220 EX3.exchangeserverpro.local Microsoft ESMTP MAIL Service ready at Wed, 18 Au g 2010 19:42:27 +1000 helo 250 EX3.exchangeserverpro.local Hello [192.168.0.9] mail from: somebody@hotmail.com 530 5.7.1 Client was not authenticated For some Hub Transport servers that are internet-facing, anonymous connections may already be enabled. In those cases relay would still be denied but will behave differently than the first example. 220 EX3.exchangeserverpro.local Microsoft ESMTP MAIL Service ready at Wed, 18 Au g 2010 20:01:44 +1000 helo 250 EX3.exchangeserverpro.local Hello [192.168.0.9] mail from: somebody@hotmail.com 250 2.1.0 Sender OK rcpt to: somebody@gmail.com 550 5.7.1 Unable to relay You'll note that relay is denied if I try to send from an @hotmail.com address to an @gmail.com address, because neither is a valid domain for the Exchange organization. But with Anonymous Users enabled on the Receive Connector I can send from an @hotmail.com address to a valid local address. 220 EX3.exchangeserverpro.local Microsoft ESMTP MAIL Service ready at Wed, 18 Au g 2010 20:05:54 +1000 helo 250 EX3.exchangeserverpro.local Hello [192.168.0.9] mail from: somebody@hotmail.com 250 2.1.0 Sender OK rcpt to: alan.reid@exchangeserverpro.local 250 2.1.5 Recipient OK data 354 Start mail input; end with . test . 250 2.6.0 [In ternalId=2] Queued mail for delivery However if I try to relay out to an external recipient, the Exchange server does not allow it. 220 EX3.exchangeserverpro.local Microsoft ESMT