Symantec Email Submission Client (SESC) does not process email spam submission when the To or From field does not contain an email address

Article:TECH188981  |  Created: 2012-05-17  |  Updated: 2013-10-25  |  Article URL http://www.symantec.com/docs/TECH188981
NOTE: If you are experiencing this particular known issue, we recommend that you Subscribe to receive email notification each time this article is updated. Subscribers will be the first to learn about any releases, status changes, workarounds or decisions made.
Article Type
Technical Solution


Issue



There are spam submissions in the SESC spam submission folder.  The spam submissions stay in the submission folder and are not processed by SESC. The SESC console shows the Failed counter increasing.  This counter is displayed at the top of the SESC console.

Conditions

  • The To or From field of the email does not have an email address.

The following is an example:

MIME-Version: 1.0
Subject: Spam test
X-Advertisement: spam
From: foo@barfoo.com

To: "John Doe"

This is a Spam Test Message

http://www.example.com/url-1.blocked/
http://www.example.com/URL-2.blocked/

Another example:

MIME-Version: 1.0
Subject: Spam test
X-Advertisement: spam
To: foo@foo.com
From: "John Doe"

This is a Spam Test Message

http://www.example.com/url-1.blocked/
http://www.example.com/URL-2.blocked/

 


Error



  • The SESC debug logs show the following error sequence (once for each pending submission)

[::]2012-05-02 09:12:29,154, [25], ERROR, Symantec.Submission.Common.HTTPClient.HttpPostRequest, Exception caught while getting HTTP response.
 Exception:

 System.Net.WebException: The remote server returned an error: (412) Precondition Failed.
   at System.Net.HttpWebRequest.GetResponse()
   at Symantec.Submission.Common.HTTPClient.HttpPostRequest.PostRequest()

Default location for SESC debug log is C:\Program Files\Symantec\SESC\1.0\Logs\log.txt.

 


Cause



The Symantec online submission site is currently accepting submissions when there is no email address.


Solution



This issue is resolved as of May 21, 2012.

 


Supplemental Materials

SourceETrack
Value2783541


Article URL http://www.symantec.com/docs/TECH188981


Terms of use for this information are found in Legal Notices