Jake Pratt
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?
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?
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.
Simon.
Simon.
ASKER
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.
From the BO knowledge base.
https://scn.sap.com/thread/1955058
Basic solution he found was to add the BO Server IP address to the Exchange server.
mlmcc
https://scn.sap.com/thread/1955058
Basic solution he found was to add the BO Server IP address to the Exchange server.
mlmcc
ASKER
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.
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.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
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/
Open in new window
Link:http://technet.microsoft.com/en-us/library/bb232021(v=exchg.141).aspx