DLP: How come there is no incident of SMTP type in the Enforce Server administration console?

I need a solution

I have created a test policy for Network Prevent for Email, and violated it subsequently.

The incident can be sent to and seen in Splunk.

How come there is no incident of this type shown in the Enforce Server administration console?

And there is no such type of SMTP for “Protocol or Endpoint Monitoring” 





Network Prevent: SMTP Block not working

I need a solution

I would like help on the issue which I’m facing right now is that the email are still being sent out to the receiving party despite the SMTP block response rule. I have verified that on the incident, the response rule action has been taken according to its history. 

FYI, the Network Prevent for Email is inline mode between a Messaging Gateway and Exchange and not in Trial mode.



Unable to connect to SMTP server

I need a solution

Hi, everyone.

I encountered the following the error “Couldn’t connect to the SMTP server using the specified settings. Please re-enter the SMTP settings.” when entering the SMTP setting in the General Settings on Enforce console.

However, the settings are properly entered and I can log into Exchange OWA using the credentials. I am also able to telnet to the SMTP server via port 25.



System Email: dlp.mail@example.com

User ID: exampledlp.mail

Password: ********

I need urgent solution on this.



cluster4.us.messagelabs.com[]:25: Service Temporarily Unavailable OR delay parameter is long.

I need a solution


I am Matsumoto, the mail administrator.
I work for a Japanese company.

I can’t mail to “messagelabs.com”. I would like you to investigate.

From(SMTP Server):


Error example:

1.Delay long.
 cluster4.us.messagelabs.com[]:25, delay=3628, delays=3625/0.02/2/0.36, dsn=2.0.0, status=sent

2.Service Temporarily Unavailable.
 cluster4a.us.messagelabs.com[]:25, delay=72, delays=0.02/0/69/2.8, dsn=4.0.0, status=deferred (host cluster4a.us.messagelabs.com[] said: 421 Service Temporarily Unavailable …

From cluster4 to cluster4a?

There was no problem at this site.


I think that it is probably blocked.
Or, the evaluation of IP may be dropped.



SMTP warnings and forwarded impossible email from spam quarantine

I need a solution

Dear Syymantec Support,

I have two problems with the Symantec Message Gateway. First of all, on the mxtoolbox.com the smtp test has two warnings since there is SMG:

Test                                  Result

SMTP Banner Check       Reverse DNS does not match SMTP Banner

SMTP TLS                       Warning – Does not support TLS.

On the other hands, if i want to forward an e-mail from spam quarantine, then i get this message: “Cannot release the message. It has either been released already or a deivery error occurred. Please Check Brigtmail Log for details.”

The Brigtmail Log says: “Feb 20 2018 19:40:07 [http-bio-443-exec-9] [QuarantineManager] ERROR – error.quarantine.unable.release.delivery javax.mail.MessagingExpection: Could not connenct to SMTP host: …. “

I hope you can help solve this problem. Thanks in advance.



Outbound SMTP proxy mails do not match any policy

I do not need a solution (just sharing information)

When trying to send an email via outgoing SMTP proxy in Symantec Encryption server (internal placement), mails do not match any mail policy, and are delivered unencrypted. 

Attempts are performed by telneting to port 25 from Linux console.

Event when configuring first rule in Default policy – If any of the following are true: – Service type is SMTP Outbound the mails are not matched.

The same ruleset works as expected with Symantec Encryption Desktop clients.

What am I missing?

Many thanks



501 Error when trying to send via smtp outbound mail proxy

I need a solution

When trying to send email via Encryption Server outbound SMTP proxy, the following error occurs:

helo host
250 crypto.coyote.com
mail from: will@coyote.com
501 Syntax error in parameters or arguments

The same error appears when trying to send inbound mail via smtp inbound proxy. What am I missing? Best



501 Connection rejected by policy Issue

I need a solution


We are currently having an issue with 2 new VPS. All our clients who are sending to emails to some of their recipients are receiving the following message:

SMTP error from remote mail server after initial connection: 501 Connection rejected by policy [7.7] 3911, please visit www.messagelabs.com/support for more details about this error message.

The IPs are: and

We have just ordered these servers and started using these IPs. It looks like these IPs have been blacklisted previously by the old owner. We have checked with http://ipremoval.sms.symantec.com/lookup/ and the tools says: “does not have a negative reputation and therefore cannot be submitted for investigation. ” but our clients keep receiving the 501 error.

Can someone please investigate to whitelist these two IPs.