Symptoms
The standalone Spam Quarantine server fails to process incoming quarantine messages.
End-users are unable to log in to the standalone Spam Quarantine console via Directory Data Service (DDS) authentication.
The dds.log log files contain errors similar to the following stack trace:
Aug 02 2026 17:16:49 [SmtpWorker-12] [SpamMessageHandler] ERROR - Quarantine failed to resolve email address [email protected]. DDS has encountered an error.
com.symantec.smg.controlcenter.BrightmailException: null ; nested exception is:
com.symantec.smg.controlcenter.directoryintegration.DDSClientException: An invalid profile ID was used to access the Directory Data Service. Check the Control Center and DDS logs for details. DDS error code: 800205
at com.symantec.smg.controlcenter.directoryintegration.DDSClientHelper.quarantineResolveAddress(DDSClientHelper.java:570)
at com.symantec.smg.controlcenter.quarantine.spam.SpamMessageHandler.headers(SpamMessageHandler.java:157)
...
Caused by: com.symantec.smg.controlcenter.directoryintegration.DDSClientException: An invalid profile ID was used to access the Directory Data Service. Check the Control Center and DDS logs for details. DDS error code: 800205This error occurs when the Directory Data Service configuration profile on the Control Center becomes corrupted or out of sync with the standalone Quarantine host, causing requests to reference an unresolvable or invalid DDS profile ID (DDS error code: 800205).
Log in to the Symantec Messaging Gateway Control Center.
Navigate to Administration > Directory Integration.
Select your configured LDAP Directory Data Source.
Disable the Directory Data Service function for Quarantine Resolution / Authentication and click Save.
Re-edit the Directory Data Source, re-enable the Directory Data Service function, and click Save.
Verify if quarantine message processing and user logins resume successfully.
In the Control Center, navigate to Administration > Settings > Logs.
Under the Directory Data Service section, set the log level to Debug.
Click Save.
Reproduce the issue by sending a test quarantined email or attempting a user login.
Navigate to Administration > Utilities > Diagnostics.
Select the quarantine host and generate a Diagnostic Package containing the full log set.
Open a case with Broadcom Support and attach the gathered diagnostic logs.
Note: Currently, the backend engineering team is investigating the root cause of this issue. This article will be updated once a fix is available.