Symptom
Getting an error message when a report is scheduled and emailed to an external domain.
"address error. CrystalEnterprise.Smtp: SMTP_E_MAILBOX_UNAVAILABLE_2(550)"
Environment
BusinessObjects Enterprise XI 3.1
Windows 2003 Server
Microsoft Exchange Server 2007
Cause
Application server unable to relay off Exchange Server 2007.
Resolution
With the new IP address added to the Exchange server – let’s say it is 192.168.1.17, and the app server that needs to relay is 192.168.1.100, fire up Exchange shell and use the following command:
New-ReceiveConnector -Name RelayConnector -usage Custom -Bindings ’192.168.1.17:25′ -fqdn server.domain.com -RemoteIPRanges 192.168.1.100 -server MYEXCHANGESERVER -permissiongroups ExchangeServers -AuthMechanism ‘TLS, ExternalAuthoritative’
What this does:
- Creates a new Receive Connector called RelayConnector
- Specifies the usage type Custom
- Binds the Receive Connector to port 25 on IP address 192.168.1.17
- Gives it the FQDN of server.domain.com
- Allows only the host with the IP address 192.168.1.100 to connect to it (specified by the RemoteIPRanges parameter)
- Additionally, and most importantly, it assigns the ExchangeServers permission group to it, and disables authentication. When you select ExternalAuthoritative for authentication, you’re telling Exchange that you completely trust the IP address(es) or subnets specified in the RemoteIPRanges parameter (192.168.1.100) and you have another authentication mechanism outside of Exchange, such as IPSec, to authenticate.
This also bypasses all security for messages received from that IP address. Because Exchange treats all hosts specified in RemoteIPRanges as trusted, it doesn’t apply anti-spam filters, doesn’t enforce message size limits, resolves P2 headers, and allows sending on behalf of users. Going back to Exchange Server 2003, this is somewhat similar to adding the sending host’s address to Connection Filtering‘s Global Accept list.
Keywords
"address error. CrystalEnterprise.Smtp: SMTP_E_MAILBOX_UNAVAILABLE_2(550)" , KBA , BI-BIP-PUB , Publishing and scheduling in InfoView/BI launch pad , Problem