We help IT Professionals succeed at work.

SMTP Error when scheduling run of BO

Jake Pratt
Jake Pratt asked
Last Modified: 2014-05-08
I am getting the following error when trying to schedule a instance of a BO that sends an email to an SMTP address outside our network.  "address error. [CrystalEnterprise.Smtp]: [Error sending address(es) to SMTP server. Return code: [SMTP 550 - Requested action not taken: mailbox unavailable.]. Reason: [abc@123.com, eft@123.com].]"

I have successfully run the objects when they send to an internal Exchange address, but outside SMTP fails.  I can ping the Exchange Server from the SAP BO server and I have a Receive Connector in the Exchange server that allows SMTP relay from the SAP BO server.  I'm not quite sure what else to check.  Any thoughts?
Watch Question

Do you receive connector was configured with this permission.

Get-ReceiveConnector "Anonymous Relay" | Add-ADPermission -User "NT AUTHORITY\ANONYMOUS LOGON" -ExtendedRights "Ms-Exch-SMTP-Accept-Any-Recipient"

Open in new window

Most Valuable Expert 2014

Is it the same error for any address? The error is rather generic and could just be a rejection for another reason, such as the format of the message. Try using a completely different provider as the end point.



Good suggestion.  I'm also trying to add the addresses as internet contacts and make them part of an internal distribution group.  Then I'll try sending to the internal distribution group address.
Mike McCrackenSenior Consultant
Most Valuable Expert 2011
Top Expert 2013

From the BO knowledge base.  


Basic solution he found was to add the BO Server IP address to the Exchange server.



BO Server IP is already added to the Exchange Server via the receive connector that I list in the description, so I don't think that is the issue.  Also, the connector allows anonymous relay, so it shouldn't be an authentication problem.  

My workaround is functioning, but I'd don't like workarounds, so still trying to get to the root of the problem.  For the workaround, I added both external addresses as Internet Contact on the Exchange Server.  I then created a distribution group in Exchange whose only members are the two contacts I created.  The distribution group of course has it's own internal email address.  I can relay to the DG and the message is going out just fine.  However, the problem remains when I try to relay directly to any external SMTP address.  I've tried several different addresses and get an error on all of them.
Most Valuable Expert 2014
This one is on us!
(Get your first solution completely free - no credit card required)


We are on Exchange 2010. I tried recreating the connector as outlined in this article and it worked. http://exchangeserverpro.com/how-to-configure-a-relay-connector-for-exchange-server-2010/

Gain unlimited access to on-demand training courses with an Experts Exchange subscription.

Get Access
Why Experts Exchange?

Experts Exchange always has the answer, or at the least points me in the correct direction! It is like having another employee that is extremely experienced.

Jim Murphy
Programmer at Smart IT Solutions

When asked, what has been your best career decision?

Deciding to stick with EE.

Mohamed Asif
Technical Department Head

Being involved with EE helped me to grow personally and professionally.

Carl Webster
CTP, Sr Infrastructure Consultant
Empower Your Career
Did You Know?

We've partnered with two important charities to provide clean water and computer science education to those who need it most. READ MORE

Ask ANY Question

Connect with Certified Experts to gain insight and support on specific technology challenges including:

  • Troubleshooting
  • Research
  • Professional Opinions
Unlock the solution to this question.
Join our community and discover your potential

Experts Exchange is the only place where you can interact directly with leading experts in the technology field. Become a member today and access the collective knowledge of thousands of technology experts.

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.


Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.