Avatar of Jake Pratt
Jake Pratt
Flag for United States of America asked on

SMTP Error when scheduling run of BO

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?
SAPCrystal ReportsExchange

Avatar of undefined
Last Comment
Jake Pratt

8/22/2022 - Mon

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

Simon Butler (Sembee)

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.

Jake Pratt

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.
This is the best money I have ever spent. I cannot not tell you how many times these folks have saved my bacon. I learn so much from the contributors.
Mike McCracken

From the BO knowledge base.  


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

Jake Pratt

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.
Simon Butler (Sembee)

Log in or sign up to see answer
Become an EE member today7-DAY FREE TRIAL
Members can start a 7-Day Free trial then enjoy unlimited access to the platform
Sign up - Free for 7 days
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
Not exactly the question you had in mind?
Sign up for an EE membership and get your own personalized solution. With an EE membership, you can ask unlimited troubleshooting, research, or opinion questions.
ask a question
Jake Pratt

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/
Get an unlimited membership to EE for less than $4 a week.
Unlimited question asking, solutions, articles and more.