Email recipients might not see SAS Digital Marketing broadcast content and responses might not be tracked when a Bulk Email Server Servlet (BESS) server is situated behind a firewall.

Also, connections from SAS Digital Marketing Studio might fail when there is a firewall between the client machine and the SAS Digital Marketing web application.

When firewalls are used between servers, you might use the customsocketfactory parameters to restrict ports that are to be opened. This functionality is not working. Ephemeral ports continue to be used incorrectly. With debug logging set, you might see the following type of errors in the SASDigitalMarktetingTracking6_3.log file and the SDM_Server.log file:

| 2014-09-09 13:13:23,065 DEBUG [] [] [] BulkEmailSocketFactory  Socket creation request received for host: jpntsuxe.jpn.sas.com, port: 40512
| 2014-09-09 13:13:23,065 DEBUG [] [] [] BulkEmailSocketFactory  Socket creation request received for host: jpntsuxe.jpn.sas.com, port: 40512
| 2014-09-09 13:14:26,072 ERROR [] [] [] CachedConnection  Bind unsuccessful.
java.rmi.RemoteException: Connection refused to host: jpntsuxe.jpn.sas.com; nested exception is:
      java.net.ConnectException: Connection timed out

Click the Hot Fix tab in this note to access the hot fix for this issue.

Operating System and Release Information

A fix for this issue for SAS Digital Marketing 6.3 is available at: