Symantec Email Submission Client (SESC) does not process email spam submission after Exchange Client Access Server (CAS) reboot or iisreset
Last Updated October 26, 2013
A user has put email into the SESC spam submission folder. The email is not removed from the folder into the Deleted Items folder.
One of the following occurred:
The CAS server was rebooted. IIS on the CAS server was restarted. Exchange did a mailbox server failover. The user's mailbox was moved from one server to another.
The following event is on the Exchange server when Exchange Web Services is started:
Log Name: Application Source: MSExchange Web Services Date: 4/11/2012 7:37:16 AM Event ID: 2 Task Category: Core Level: Information Keywords: Classic User: N/A Computer: WIN-P5723T9FPJQ.benexchange2010.internal Description: The Exchange Web Services started successfully.
Only SESC subscriptions after this event are processed. All previous subscriptions are gone.
SESC uses Exchange Web Services "Push Subscriptions" (see Exchange Web Services – Subscriptions and Notifications for more information). The subscriptions are maintained on the CAS server. If one of the situations listed above occurs the CAS server loses the subscriptions. Therefore SESC does not receive a notification when email is put into the spam submission folder.
Symantec is aware of this issue. This article is updated as more information is available. Subscribe to this article to receive updates.
SESC creates new subscriptions during a scheduled subscription update. This typically occurs at 12:00 AM server time and is configurable. Use the following steps to have SESC create new subscriptions immediately:
1. Open the SESC console. 2. Open the System Update pane. 3. Check the appropriate Exchange servers in the Select servers tree. 4. Check the Perform force subscription checkbox. 5. Check the Perform pending submissions along with update checkbox. 6. Click the Update button.