A new installation of SAS Digital Marketing might fail to send e-mails to legitimate e-mail addresses.

The sdm_server.log file might show the following error messages:

java.lang.Exception: Email send failure for "user.name@xxx.com".
Reason - No such file or directory.
Check your source table for invalid email addresses.
       at com.xxx.email.send.EmailTransmitter.send(EmailTransmitter.java:332)

If you want to spool the sending of e-mails, you can work around this issue by creating \spool and \pending directories in the following location:

../config/Lev1/Applications/SASCustomerIntelligence/SASDigitalMarketing

The following excerpt from the SAS^® Customer Intelligence Deployment Guide explains how to use the standard method of sending e-mails:

This issue is caused by the incorrect setting of the mail transport agent (MTA) during configuration. To work around the issue log on to the Digital Marketing Studio client and select Tools ► Server Configuration and from the dialog box choose Send Options. Select the host under SMTP E-Mail Servers and click the Edit button to change the value. Click OK to save your changes.

Operating System and Release Information

Product Family	Product	System	Product Release		SAS Release
			Reported	Fixed*	Reported	Fixed*
SAS System	SAS Digital Marketing	Microsoft® Windows® for x64	6.1_M1	6.3	9.3 TS1M2	9.4 TS1M1
		Microsoft Windows 8 Enterprise 32-bit	6.1_M1	6.3	9.3 TS1M2	9.4 TS1M1
		Microsoft Windows 8 Enterprise x64	6.1_M1	6.3	9.3 TS1M2	9.4 TS1M1
		Microsoft Windows 8 Pro 32-bit	6.1_M1	6.3	9.3 TS1M2	9.4 TS1M1
		Microsoft Windows 8 Pro x64	6.1_M1	6.3	9.3 TS1M2	9.4 TS1M1
		Microsoft Windows 8.1 Enterprise 32-bit	6.1_M1	6.3	9.3 TS1M2	9.4 TS1M1
		Microsoft Windows 8.1 Enterprise x64	6.1_M1	6.3	9.3 TS1M2	9.4 TS1M1
		Microsoft Windows 8.1 Pro	6.1_M1	6.3	9.3 TS1M2	9.4 TS1M1
		Microsoft Windows 8.1 Pro 32-bit	6.1_M1	6.3	9.3 TS1M2	9.4 TS1M1
		Microsoft Windows Server 2003 Datacenter Edition	6.1_M1		9.3 TS1M2
		Microsoft Windows Server 2003 Enterprise Edition	6.1_M1		9.3 TS1M2
		Microsoft Windows Server 2003 Standard Edition	6.1_M1		9.3 TS1M2
		Microsoft Windows Server 2003 for x64	6.1_M1		9.3 TS1M2
		Microsoft Windows Server 2008	6.1_M1	6.3	9.3 TS1M2	9.4 TS1M1
		Microsoft Windows Server 2008 R2	6.1_M1	6.3	9.3 TS1M2	9.4 TS1M1
		Microsoft Windows Server 2008 for x64	6.1_M1	6.3	9.3 TS1M2	9.4 TS1M1
		Microsoft Windows Server 2012 Datacenter	6.1_M1	6.3	9.3 TS1M2	9.4 TS1M1
		Microsoft Windows Server 2012 R2 Datacenter	6.1_M1	6.3	9.3 TS1M2	9.4 TS1M1
		Microsoft Windows Server 2012 R2 Std	6.1_M1	6.3	9.3 TS1M2	9.4 TS1M1
		Microsoft Windows Server 2012 Std	6.1_M1	6.3	9.3 TS1M2	9.4 TS1M1
		Microsoft Windows XP Professional	6.1_M1		9.3 TS1M2
		Windows 7 Enterprise 32 bit	6.1_M1	6.3	9.3 TS1M2	9.4 TS1M1
		Windows 7 Enterprise x64	6.1_M1	6.3	9.3 TS1M2	9.4 TS1M1
		Windows 7 Home Premium 32 bit	6.1_M1	6.3	9.3 TS1M2	9.4 TS1M1
		Windows 7 Home Premium x64	6.1_M1	6.3	9.3 TS1M2	9.4 TS1M1
		Windows 7 Professional 32 bit	6.1_M1	6.3	9.3 TS1M2	9.4 TS1M1
		Windows 7 Professional x64	6.1_M1	6.3	9.3 TS1M2	9.4 TS1M1
		Windows 7 Ultimate 32 bit	6.1_M1	6.3	9.3 TS1M2	9.4 TS1M1
		Windows 7 Ultimate x64	6.1_M1	6.3	9.3 TS1M2	9.4 TS1M1
		Windows Vista	6.1_M1		9.3 TS1M2
		Windows Vista for x64	6.1_M1		9.3 TS1M2
		64-bit Enabled AIX	6.1_M1	6.3	9.3 TS1M2	9.4 TS1M1
		64-bit Enabled HP-UX	6.1_M1	6.3	9.3 TS1M2	9.4 TS1M1
		64-bit Enabled Solaris	6.1_M1	6.3	9.3 TS1M2	9.4 TS1M1
		HP-UX IPF	6.1_M1	6.3	9.3 TS1M2	9.4 TS1M1
		Linux for x64	6.1_M1	6.3	9.3 TS1M2	9.4 TS1M1
		Solaris for x64	6.1_M1	6.3	9.3 TS1M2	9.4 TS1M1

* For software releases that are not yet generally available, the Fixed Release is the software release in which the problem is planned to be fixed.