Does anyone know how to limit the notify response rules? In order to prevent users being overwhelmed with popups and notifications, is there a way I can, for example, have the notify popup appear once a day. We are going to start moving some of our new policies into prevent, but before we do that, we are going to use the system to notify them that their actions will soon be prevented.
Thanks
RJK
Hi,
one of our customers is facing an issue with SEP 14 MP2.
We have migrated from SEP 12.1.6 MP7 and performed a new SEP 14 installation.
Customer used NAC before and had the setting in “General settings” activated.
We exported the domain in SEP 12 and imported in SEP 14
After installation of a new client with default installation package from 14, we see “Network Access Control” in client UI. Is there any option to disable it later on or via database script?
Thanks in advance!
Hello, i started to testing SEP for our organization, and it have much difficulty
1. How can i installate SEP client to our PCs with use ADDS OU, where i choose OU with users' PCs, and SEPM automaticly installate clients to the stations, after that i want to SEPM will automatilcy monitoring this OU and after adding new PC to the OU clients automaticly will be installate.And first question is very important, how can i automatically deploy clients to select OU
2. How can i use automatic update clients by using only SEPM server without LiveUpdate inside our organization
3. How can i change clients' manage server to other manage server. I need to transfer (migrate) clients to other SEPM server
Hi All,
We have a windows 2016 web server which runs RDP, Database Server & IIS.
We have added the applications, Configured the database able to connect to all of the servers services as expected (Windows Firewall configured to permit WebServer/RDP access etc)
We install Symantec Endpoint Protection 14 on to this system. After this we are no longer able to connect to these services.
Assumed that the Symantic Endpoint Firewall was the issue so we configured the Endpoint Protection firewall to permit Port 80,443 and RDP - First Rule in the List.
We are still unable to access these services over the network.
We therefore disabled the network protection. Still unavilable.
Disabled all aspects of the Symantic Endpoint protection. Still Unavilable.
Uninstalled Symantic endpoint protection. Services are running but are Still Unavilable. Checked the windows firewall for incoming rules which are present.
This is a virtual machine so we revert to the backup snapshot we took - Services are now avilable and working. Install Symantic again, Same symtoms.
Is defiently SEP which is causing the issues and its not a configuration issue with the firewall as proven by the uninstall of symantic still causing the issues.
At all states we are able to ping the system and the system is able to access external/internal services.
If anyone has any suggestions it would be apprivated. I'd raise a case but waiting on symantic to add my license details out my symantic account.
Thanks
Joe.
Hey All,
Does anyone know how to limit the users to only one notification per day? We are looking to implement some new policies and before we put them in block mode, we would like to notifiy the users of their actions. However, we don't want users getting multiple notifications. Just one a day (as a reminder).
Thanks
Greetings,
Its my understanding that the Symantec Messaging Gateway accepts quarantined Emails on a specified port. We found that it can be used as an open relay using that port. Is there a way to filter what hosts the gateway will accept quaratined Emails on? The only options we see are to change the port or disable it.
Thank You,
Has anyone experienced the error Symantec Endpoint Protection Manager could not update Intrusion Prevention Signatures 14.0 since about September 6th with SEPM Version 14.0 MP2? I had the same issue with SEP 12.1 RU6 last month. See https://www.symantec.com/connect/forums/could-not-update-client-intrusion-detection-system-signatures-121-ru6 and the issue was fixed automatically after a couple of weeks. I am not seeing any info on this with 14.0 MP2. Both intrusion prevention signatures 14.0 and 14.0 MP2 are stuck on 9/6/2017 r21? I would love to know why this keep happening. Please fix or tell me how to fix it.
Thanks for your help!
Hi,
I am in the process of deploying SEE. Everything looks like it installed correctly and I was able to create my installer. I have the installer loaded onto a test PC and its in the process of encrypting the drive. Under Check-In, the last communication with the server shows "Never Connected to Server". Under the agent if I select check in it says "Communication is taking too long. Try again later"
It looks like some sort of security issue on my server/IIS. When I browse to https://appserver.ad.mydomain:1001//GECommunicatio... from the network it says the site cannot be reached. If I try from a browser on the IIS server it will connect but I am asked to supply credentials. Once I input credentials, I see a GECOmmunicationWS webpage.
Has anyone any ideas on how I can rectify this?
Thanks in advance
Poco
Hello Symantec team!
We recently identified a bug in one of our clients that was infected by a malicious script that started firing several spam.
We have solved the problem, but note that some outgoing emails are being blocked.
I searched our main IP for investigation at (http://ipremoval.sms.symantec.com/lookup/) and there is no blocking, even though they are getting the following error:
Delivery Host: cluster5.us.messagelabs.com
SMTP error from remote mail server after initial connection: 501 Connection rejected by policy [7.7] 12606, please visit www.messagelabs.com/support for more details about this error message.
Our main shipping IP is:
204.12.202.18
And the other IPs we also use:
204.12.202.19
204.12.202.20
204.12.202.21
I thank you for your help.
I've been noticing many of our endpoints' IPS signatures are out-of-date. Upon closer inspection, they are all machines who were recently upgraded to Windows 10 (clean install) and using a new SEP installation package running v14.0.0 MP2 (14.0.2415.0200). We tested pushing out the update from v12 to v14 for a few users, and they are also now not getting updated IPS signatures, including at least one Windows 7 machine. Is there an issue in v14 with IPS signatures that we should know about?
I installed SEP on 3 workstations at our Church. I installed it as the built-in Administrator account.
After doing so, I can log in as other users, but can no longer use the built-in admin account anymore. When I log in, the screne constantly flickers and expllorer crashes every other second and I can't browse around or open any applications.
After uninstalling SEP, the problem goes away. If I re-install it, the problem comes back again.
Strange thing though: This only happened on 2 of the 3 computers. Not rhyme or reason as to why.
Any suggestions on how I can get this resolved?
Hi,
We enable Full Definitions Download and allow our client to download the full definition via internet, we enable this because some clients are outdated and had problem on downloading the full definition on their local GUPs.
Question:
-Is there a script or way to schedule the enable and disable of "Full Definition Download"
-What else might be the problem why client are not downloading the full definition on their local GUPs?
Hello,
I was just wondering if its possible to use borth the cloud manager and the on premise manager. I would like to use the On Premise one myself but we have techs that would be better using the cloud one.
Thank You
Hi,
I thought I would get the ball rolling. The next upgrade of Win 10 is scheduled to be released sometime in October 2017. I know the release of SEP 14 RU1 is imminent. It looks like RU1 will resolve many current SEP issues. What is Symantec's time-line for support of the next Win 10 release? Hopefully RU1 will clear up many bugs in SEP but it is a bit discouraging this is coming right before a new Win 10 release. I have been reading Microsoft is hardening security in this next release and IMHO SEP will have conflicts that will need to be addressed.
Thanks,
CQ
(Using Symantec Encryption Desktop 10.4.0)
Hi, we have a team that needs to add pgp encryption to a functional mailbox to which all the team members have access(using outlook to access said mailbox). Some users already have their own private email protected by PGP. Some users have "send as" access for the functional mailbox and some other users "read only" access. How would we go about securing this mailbox using PGP?
Thanks in advance.
Is there a "Supported storage device and protocol" table also for SPE 7.9?
Can I use Windows Server 2012 platform with RPC for EMC NAS Integration?
Hi Symantec,
We operate a cloud-based SaaS service which allows our users to manage marketing emails to their customers.
We have been finding that several recipients have been receiving multiple copies of email sent out, and upon investigating from our end, the connection to the messagelabs.com servers are either refusing connection, or simply timing out. That wouldn't necessarily be a problem as our mail server will simply mark the email as 'bounced', however, it would appear that the recipients are actually receiving some (if not all) of these emails.
You can see from a log extract below that our mail server attempts to connect to many different servers of yours and each one exhibits a similar problem. In many cases, even though it claims to accept the message, the session simply times out after 60 seconds, thus resulting in another retry.
I have checked that our outbound IP (in this case 46.37.186.167) is not listed on your blocklist (http://ipremoval.sms.symantec.com/lookup/).
Log extract:
[2017.09.12] 11:34:04 [11411] Sending remote mail for bounce-10-1259-6749-6638686-177@clarity-marketing.com
[2017.09.12] 11:34:04 [11411] Initiating connection to 216.82.242.34
[2017.09.12] 11:34:04 [11411] Connecting to 216.82.242.34:25 (Id: 1)
[2017.09.12] 11:34:04 [11411] Binding to local IP 172.27.226.13:0 (Id: 1)
[2017.09.12] 11:34:04 [11411] Connection to 216.82.242.34:25 from 172.27.226.13:55517 succeeded (Id: 1)
[2017.09.12] 11:34:04 [11411] RSP: 220 ***************************************
[2017.09.12] 11:34:04 [11411] CMD: EHLO mail3.claritygo.com
[2017.09.12] 11:34:04 [11411] RSP: 250-server-9.tower-73.messagelabs.com
[2017.09.12] 11:34:04 [11411] RSP: 250-XXXXXXXA
[2017.09.12] 11:34:04 [11411] RSP: 250-PIPELINING
[2017.09.12] 11:34:04 [11411] RSP: 250 8BITMIME
[2017.09.12] 11:34:04 [11411] CMD: MAIL FROM:<bounce-10-1259-6749-6638686-177@clarity-marketing.com>
[2017.09.12] 11:34:04 [11411] RSP: 250 OK
[2017.09.12] 11:34:04 [11411] CMD: RCPT TO:<sian.dutton@havaspeople.com>
[2017.09.12] 11:34:05 [11411] RSP: 250 OK
[2017.09.12] 11:34:05 [11411] CMD: DATA
[2017.09.12] 11:34:05 [11411] RSP: 354 go ahead
[2017.09.12] 11:35:05 [11411] The smtp session has timed out.
[2017.09.12] 11:35:05 [11411] Initiating connection to 216.82.251.37
[2017.09.12] 11:35:05 [11411] Connecting to 216.82.251.37:25 (Id: 2)
[2017.09.12] 11:35:05 [11411] Binding to local IP 172.27.226.13:0 (Id: 2)
[2017.09.12] 11:35:05 [11411] Connection to 216.82.251.37:25 from 172.27.226.13:55773 succeeded (Id: 2)
[2017.09.12] 11:35:05 [11411] RSP: 220 ****************************************
[2017.09.12] 11:35:05 [11411] CMD: EHLO mail3.claritygo.com
[2017.09.12] 11:35:05 [11411] RSP: 250-server-3.tower-153.messagelabs.com
[2017.09.12] 11:35:05 [11411] RSP: 250-XXXXXXXA
[2017.09.12] 11:35:05 [11411] RSP: 250-PIPELINING
[2017.09.12] 11:35:05 [11411] RSP: 250 8BITMIME
[2017.09.12] 11:35:05 [11411] CMD: MAIL FROM:<bounce-10-1259-6749-6638686-177@clarity-marketing.com>
[2017.09.12] 11:35:05 [11411] RSP: 250 OK
[2017.09.12] 11:35:05 [11411] CMD: RCPT TO:<sian.dutton@havaspeople.com>
[2017.09.12] 11:35:06 [11411] RSP: 250 OK
[2017.09.12] 11:35:06 [11411] CMD: DATA
[2017.09.12] 11:35:06 [11411] RSP: 354 go ahead
[2017.09.12] 11:36:06 [11411] The smtp session has timed out.
[2017.09.12] 11:36:06 [11411] Initiating connection to 216.82.242.37
[2017.09.12] 11:36:06 [11411] Connecting to 216.82.242.37:25 (Id: 3)
[2017.09.12] 11:36:06 [11411] Binding to local IP 172.27.226.13:0 (Id: 3)
[2017.09.12] 11:36:06 [11411] Connection to 216.82.242.37:25 from 172.27.226.13:56185 succeeded (Id: 3)
[2017.09.12] 11:36:06 [11411] RSP: 220 ****************************************
[2017.09.12] 11:36:06 [11411] CMD: EHLO mail3.claritygo.com
[2017.09.12] 11:36:06 [11411] RSP: 250-server-16.tower-99.messagelabs.com
[2017.09.12] 11:36:06 [11411] RSP: 250-XXXXXXXA
[2017.09.12] 11:36:06 [11411] RSP: 250-PIPELINING
[2017.09.12] 11:36:06 [11411] RSP: 250 8BITMIME
[2017.09.12] 11:36:06 [11411] CMD: MAIL FROM:<bounce-10-1259-6749-6638686-177@clarity-marketing.com>
[2017.09.12] 11:36:06 [11411] RSP: 250 OK
[2017.09.12] 11:36:06 [11411] CMD: RCPT TO:<sian.dutton@havaspeople.com>
[2017.09.12] 11:36:06 [11411] RSP: 250 OK
[2017.09.12] 11:36:06 [11411] CMD: DATA
[2017.09.12] 11:36:07 [11411] RSP: 354 go ahead
[2017.09.12] 11:37:07 [11411] The smtp session has timed out.
[2017.09.12] 11:37:07 [11411] Initiating connection to 216.82.250.51
[2017.09.12] 11:37:07 [11411] Connecting to 216.82.250.51:25 (Id: 4)
[2017.09.12] 11:37:07 [11411] Binding to local IP 172.27.226.13:0 (Id: 4)
[2017.09.12] 11:37:07 [11411] Connection to 216.82.250.51:25 from 172.27.226.13:56510 succeeded (Id: 4)
[2017.09.12] 11:37:07 [11411] RSP: 220 *****************************************
[2017.09.12] 11:37:07 [11411] CMD: EHLO mail3.claritygo.com
[2017.09.12] 11:37:07 [11411] RSP: 250-server-13.tower-108.messagelabs.com
[2017.09.12] 11:37:07 [11411] RSP: 250-XXXXXXXA
[2017.09.12] 11:37:07 [11411] RSP: 250-PIPELINING
[2017.09.12] 11:37:07 [11411] RSP: 250 8BITMIME
[2017.09.12] 11:37:07 [11411] CMD: MAIL FROM:<bounce-10-1259-6749-6638686-177@clarity-marketing.com>
[2017.09.12] 11:37:07 [11411] RSP: 250 OK
[2017.09.12] 11:37:07 [11411] CMD: RCPT TO:<sian.dutton@havaspeople.com>
[2017.09.12] 11:37:08 [11411] RSP: 250 OK
[2017.09.12] 11:37:08 [11411] CMD: DATA
[2017.09.12] 11:37:08 [11411] RSP: 354 go ahead
[2017.09.12] 11:38:08 [11411] The smtp session has timed out.
[2017.09.12] 11:38:08 [11411] Initiating connection to 216.82.242.131
[2017.09.12] 11:38:08 [11411] Connecting to 216.82.242.131:25 (Id: 5)
[2017.09.12] 11:38:08 [11411] Binding to local IP 172.27.226.13:0 (Id: 5)
[2017.09.12] 11:38:09 [11411] Exception connecting to 216.82.242.131 (Id: 5)
[2017.09.12] 11:38:09 [11411] System.Net.Sockets.SocketException (0x80004005): No connection could be made because the target machine actively refused it 216.82.242.131:25
[2017.09.12] 11:38:09 [11411] Binding to local ip '172.27.226.13' failed. Switched binding to primary local ip.
[2017.09.12] 11:38:09 [11411] Connecting to 216.82.242.131:25 (Id: 6)
[2017.09.12] 11:38:09 [11411] Connection to 216.82.242.131:25 from 172.27.226.9:56821 succeeded (Id: 6)
[2017.09.12] 11:38:09 [11411] RSP: 220 ***************************************
[2017.09.12] 11:38:09 [11411] CMD: EHLO mail.claritygo.com
[2017.09.12] 11:38:10 [11411] RSP: 250-server-6.tower-76.messagelabs.com
[2017.09.12] 11:38:10 [11411] RSP: 250-XXXXXXXA
[2017.09.12] 11:38:10 [11411] RSP: 250-PIPELINING
[2017.09.12] 11:38:10 [11411] RSP: 250 8BITMIME
[2017.09.12] 11:38:10 [11411] CMD: MAIL FROM:<bounce-10-1259-6749-6638686-177@clarity-marketing.com>
[2017.09.12] 11:38:10 [11411] RSP: 250 OK
[2017.09.12] 11:38:10 [11411] CMD: RCPT TO:<sian.dutton@havaspeople.com>
[2017.09.12] 11:38:10 [11411] RSP: 250 OK
[2017.09.12] 11:38:10 [11411] CMD: DATA
[2017.09.12] 11:38:10 [11411] RSP: 354 go ahead
[2017.09.12] 11:39:10 [11411] The smtp session has timed out.
[2017.09.12] 11:39:10 [11411] Initiating connection to 216.82.241.195
[2017.09.12] 11:39:10 [11411] Connecting to 216.82.241.195:25 (Id: 7)
[2017.09.12] 11:39:10 [11411] Binding to local IP 172.27.226.13:0 (Id: 7)
[2017.09.12] 11:39:10 [11411] Connection to 216.82.241.195:25 from 172.27.226.13:57076 succeeded (Id: 7)
[2017.09.12] 11:39:10 [11411] RSP: 220 *****************************************
[2017.09.12] 11:39:10 [11411] CMD: EHLO mail3.claritygo.com
[2017.09.12] 11:39:10 [11411] RSP: 250-server-10.tower-119.messagelabs.com
[2017.09.12] 11:39:10 [11411] RSP: 250-XXXXXXXA
[2017.09.12] 11:39:10 [11411] RSP: 250-PIPELINING
[2017.09.12] 11:39:10 [11411] RSP: 250 8BITMIME
[2017.09.12] 11:39:10 [11411] CMD: MAIL FROM:<bounce-10-1259-6749-6638686-177@clarity-marketing.com>
[2017.09.12] 11:39:11 [11411] RSP: 250 OK
[2017.09.12] 11:39:11 [11411] CMD: RCPT TO:<sian.dutton@havaspeople.com>
[2017.09.12] 11:39:11 [11411] RSP: 250 OK
[2017.09.12] 11:39:11 [11411] CMD: DATA
[2017.09.12] 11:39:11 [11411] RSP: 354 go ahead
[2017.09.12] 11:40:11 [11411] The smtp session has timed out.
[2017.09.12] 11:40:11 [11411] Initiating connection to 216.82.250.83
[2017.09.12] 11:40:11 [11411] Connecting to 216.82.250.83:25 (Id: 8)
[2017.09.12] 11:40:11 [11411] Binding to local IP 172.27.226.13:0 (Id: 8)
[2017.09.12] 11:40:11 [11411] Connection to 216.82.250.83:25 from 172.27.226.13:57383 succeeded (Id: 8)
[2017.09.12] 11:40:11 [11411] RSP: 220 ****************************************
[2017.09.12] 11:40:11 [11411] CMD: EHLO mail3.claritygo.com
[2017.09.12] 11:40:11 [11411] RSP: 250-server-5.tower-120.messagelabs.com
[2017.09.12] 11:40:11 [11411] RSP: 250-XXXXXXXA
[2017.09.12] 11:40:11 [11411] RSP: 250-PIPELINING
[2017.09.12] 11:40:11 [11411] RSP: 250 8BITMIME
[2017.09.12] 11:40:11 [11411] CMD: MAIL FROM:<bounce-10-1259-6749-6638686-177@clarity-marketing.com>
[2017.09.12] 11:40:12 [11411] RSP: 250 OK
[2017.09.12] 11:40:12 [11411] CMD: RCPT TO:<sian.dutton@havaspeople.com>
[2017.09.12] 11:40:12 [11411] RSP: 250 OK
[2017.09.12] 11:40:12 [11411] CMD: DATA
[2017.09.12] 11:40:12 [11411] RSP: 354 go ahead
[2017.09.12] 11:41:12 [11411] The smtp session has timed out.
[2017.09.12] 11:41:12 [11411] Initiating connection to 216.82.251.35
[2017.09.12] 11:41:12 [11411] Connecting to 216.82.251.35:25 (Id: 9)
[2017.09.12] 11:41:12 [11411] Binding to local IP 172.27.226.13:0 (Id: 9)
[2017.09.12] 11:41:12 [11411] Connection to 216.82.251.35:25 from 172.27.226.13:57665 succeeded (Id: 9)
[2017.09.12] 11:41:12 [11411] RSP: 220 ****************************************
[2017.09.12] 11:41:12 [11411] CMD: EHLO mail3.claritygo.com
[2017.09.12] 11:41:13 [11411] RSP: 250-server-3.tower-151.messagelabs.com
[2017.09.12] 11:41:13 [11411] RSP: 250-XXXXXXXA
[2017.09.12] 11:41:13 [11411] RSP: 250-PIPELINING
[2017.09.12] 11:41:13 [11411] RSP: 250 8BITMIME
[2017.09.12] 11:41:13 [11411] CMD: MAIL FROM:<bounce-10-1259-6749-6638686-177@clarity-marketing.com>
[2017.09.12] 11:41:13 [11411] RSP: 250 OK
[2017.09.12] 11:41:13 [11411] CMD: RCPT TO:<sian.dutton@havaspeople.com>
[2017.09.12] 11:41:13 [11411] RSP: 250 OK
[2017.09.12] 11:41:13 [11411] CMD: DATA
[2017.09.12] 11:41:13 [11411] RSP: 354 go ahead
[2017.09.12] 11:42:13 [11411] The smtp session has timed out.
[2017.09.12] 11:42:13 [11411] Initiating connection to 216.82.250.99
[2017.09.12] 11:42:13 [11411] Connecting to 216.82.250.99:25 (Id: 10)
[2017.09.12] 11:42:13 [11411] Binding to local IP 172.27.226.13:0 (Id: 10)
[2017.09.12] 11:42:14 [11411] Connection to 216.82.250.99:25 from 172.27.226.13:57915 succeeded (Id: 10)
[2017.09.12] 11:42:14 [11411] RSP: 220 ****************************************
[2017.09.12] 11:42:14 [11411] CMD: EHLO mail3.claritygo.com
[2017.09.12] 11:42:14 [11411] RSP: 250-server-7.tower-126.messagelabs.com
[2017.09.12] 11:42:14 [11411] RSP: 250-XXXXXXXA
[2017.09.12] 11:42:14 [11411] RSP: 250-PIPELINING
[2017.09.12] 11:42:14 [11411] RSP: 250 8BITMIME
[2017.09.12] 11:42:14 [11411] CMD: MAIL FROM:<bounce-10-1259-6749-6638686-177@clarity-marketing.com>
[2017.09.12] 11:42:14 [11411] RSP: 250 OK
[2017.09.12] 11:42:14 [11411] CMD: RCPT TO:<sian.dutton@havaspeople.com>
[2017.09.12] 11:42:14 [11411] RSP: 250 OK
[2017.09.12] 11:42:14 [11411] CMD: DATA
[2017.09.12] 11:42:14 [11411] RSP: 354 go ahead
[2017.09.12] 11:43:15 [11411] The smtp session has timed out.
[2017.09.12] 11:43:15 [11411] Initiating connection to 216.82.251.36
[2017.09.12] 11:43:15 [11411] Connecting to 216.82.251.36:25 (Id: 11)
[2017.09.12] 11:43:15 [11411] Binding to local IP 172.27.226.13:0 (Id: 11)
[2017.09.12] 11:43:15 [11411] Connection to 216.82.251.36:25 from 172.27.226.13:58223 succeeded (Id: 11)
[2017.09.12] 11:43:15 [11411] RSP: 220 ****************************************
[2017.09.12] 11:43:15 [11411] CMD: EHLO mail3.claritygo.com
[2017.09.12] 11:43:15 [11411] RSP: 250-server-8.tower-152.messagelabs.com
[2017.09.12] 11:43:15 [11411] RSP: 250-XXXXXXXA
[2017.09.12] 11:43:15 [11411] RSP: 250-PIPELINING
[2017.09.12] 11:43:15 [11411] RSP: 250 8BITMIME
[2017.09.12] 11:43:15 [11411] CMD: MAIL FROM:<bounce-10-1259-6749-6638686-177@clarity-marketing.com>
[2017.09.12] 11:43:15 [11411] RSP: 250 OK
[2017.09.12] 11:43:15 [11411] CMD: RCPT TO:<sian.dutton@havaspeople.com>
[2017.09.12] 11:43:15 [11411] RSP: 250 OK
[2017.09.12] 11:43:15 [11411] CMD: DATA
[2017.09.12] 11:43:16 [11411] RSP: 354 go ahead
[2017.09.12] 11:44:16 [11411] The smtp session has timed out.
[2017.09.12] 11:44:16 [11411] Initiating connection to 216.82.242.147
[2017.09.12] 11:44:16 [11411] Connecting to 216.82.242.147:25 (Id: 12)
[2017.09.12] 11:44:16 [11411] Binding to local IP 172.27.226.13:0 (Id: 12)
[2017.09.12] 11:44:16 [11411] Connection to 216.82.242.147:25 from 172.27.226.13:58495 succeeded (Id: 12)
[2017.09.12] 11:44:16 [11411] RSP: 220 ****************************************
[2017.09.12] 11:44:16 [11411] CMD: EHLO mail3.claritygo.com
[2017.09.12] 11:44:16 [11411] RSP: 250-server-11.tower-95.messagelabs.com
[2017.09.12] 11:44:16 [11411] RSP: 250-XXXXXXXA
[2017.09.12] 11:44:16 [11411] RSP: 250-PIPELINING
[2017.09.12] 11:44:16 [11411] RSP: 250 8BITMIME
[2017.09.12] 11:44:16 [11411] CMD: MAIL FROM:<bounce-10-1259-6749-6638686-177@clarity-marketing.com>
[2017.09.12] 11:44:16 [11411] RSP: 250 OK
[2017.09.12] 11:44:16 [11411] CMD: RCPT TO:<sian.dutton@havaspeople.com>
[2017.09.12] 11:44:16 [11411] RSP: 250 OK
[2017.09.12] 11:44:16 [11411] CMD: DATA
[2017.09.12] 11:44:17 [11411] RSP: 354 go ahead
[2017.09.12] 11:45:17 [11411] The smtp session has timed out.
[2017.09.12] 11:45:17 [11411] Initiating connection to 216.82.251.230
[2017.09.12] 11:45:17 [11411] Connecting to 216.82.251.230:25 (Id: 13)
[2017.09.12] 11:45:17 [11411] Binding to local IP 172.27.226.13:0 (Id: 13)
[2017.09.12] 11:45:17 [11411] Connection to 216.82.251.230:25 from 172.27.226.13:58756 succeeded (Id: 13)
[2017.09.12] 11:45:17 [11411] RSP: 220 *****************************************
[2017.09.12] 11:45:17 [11411] CMD: EHLO mail3.claritygo.com
[2017.09.12] 11:45:18 [11411] RSP: 250-server-12.tower-555.messagelabs.com says EHLO to 46.37.186.167:58756
[2017.09.12] 11:45:18 [11411] RSP: 250-8BITMIME
[2017.09.12] 11:45:18 [11411] RSP: 250-XXXXXXXA
[2017.09.12] 11:45:18 [11411] RSP: 250 PIPELINING
[2017.09.12] 11:45:18 [11411] CMD: MAIL FROM:<bounce-10-1259-6749-6638686-177@clarity-marketing.com>
[2017.09.12] 11:45:18 [11411] RSP: 250 2.0.0 MAIL FROM accepted
[2017.09.12] 11:45:18 [11411] CMD: RCPT TO:<sian.dutton@havaspeople.com>
[2017.09.12] 11:45:18 [11411] RSP: 421 Service Temporarily Unavailable
[2017.09.12] 11:45:18 [11411] CMD: QUIT
Hello,
I recently took over a new environment and I'm running into an issue that the old admin wasn't able to solve. I've worked with some encryption programs before, but never directly with Symantec Encryption Desktop.At any rate, when users change their passwords in AD, the Full Disk encryption boot doesn't get an updated password...and they have to continue to use their old, old-old, or in some cases old-old-old passwords.
I am running Symatec Encryption Server 3.3.2 MP13 (Build 21495).
Dear Support,
I've a Mailserver and i receive the following in my Logfile.
Cause your Mailcluster dosn't tell me a reason why, i don't know why.
--->
Sep 15 13:56:52 lvps83-169-22-79 postfix/smtp[12581]: connect to cluster4.eu.messagelabs.com[85.158.143.35]:25: Connection timed out
Sep 15 13:56:52 lvps83-169-22-79 postfix/smtp[12582]: connect to cluster4.eu.messagelabs.com[85.158.143.35]:25: Connection timed out
Sep 15 13:56:52 lvps83-169-22-79 postfix/smtp[12583]: connect to cluster4.eu.messagelabs.com[85.158.137.68]:25: Connection timed out
Sep 15 13:57:22 lvps83-169-22-79 postfix/smtp[12581]: connect to cluster4.eu.messagelabs.com[85.158.137.68]:25: Connection timed out
Sep 15 13:57:22 lvps83-169-22-79 postfix/smtp[12582]: connect to cluster4.eu.messagelabs.com[193.109.254.147]:25: Connection timed out
Sep 15 13:57:22 lvps83-169-22-79 postfix/smtp[12583]: connect to cluster4.eu.messagelabs.com[193.109.254.147]:25: Connection timed out
Sep 15 13:57:52 lvps83-169-22-79 postfix/smtp[12581]: connect to cluster4.eu.messagelabs.com[85.158.139.211]:25: Connection timed out
Sep 15 13:57:52 lvps83-169-22-79 postfix/smtp[12582]: connect to cluster4.eu.messagelabs.com[85.158.137.68]:25: Connection timed out
Sep 15 13:57:52 lvps83-169-22-79 postfix/smtp[12583]: connect to cluster4.eu.messagelabs.com[85.158.143.35]:25: Connection timed out
Sep 15 13:58:22 lvps83-169-22-79 postfix/smtp[12581]: connect to cluster4.eu.messagelabs.com[193.109.254.147]:25: Connection timed out
Sep 15 13:58:22 lvps83-169-22-79 postfix/smtp[12582]: connect to cluster4.eu.messagelabs.com[85.158.139.211]:25: Connection timed out
Sep 15 13:58:22 lvps83-169-22-79 postfix/smtp[12583]: connect to cluster4.eu.messagelabs.com[85.158.139.211]:25: Connection timed out
Sep 15 13:58:52 lvps83-169-22-79 postfix/smtp[12581]: connect to cluster4a.eu.messagelabs.com[85.158.139.103]:25: Connection timed out
Sep 15 13:58:52 lvps83-169-22-79 postfix/smtp[12582]: connect to cluster4a.eu.messagelabs.com[216.82.251.230]:25: Connection timed out
Sep 15 13:58:52 lvps83-169-22-79 postfix/smtp[12583]: connect to cluster4a.eu.messagelabs.com[216.82.251.230]:25: Connection timed out
Sep 15 13:58:52 lvps83-169-22-79 postfix/smtp[12582]: F3D2AA0E28: to=<palettenabteilung.aschaffenburg@de.dsv.com>, relay=none, delay=372286, delays=372136/0.02/150/0, dsn=4.4.1, status=deferred (connect to cluster4a.eu.messagelabs.com[216.82.251.230]:25: Connection timed out)
<--
Regards
Markus Lembke
Hello SMG community,
This is an FYI... My company tried to renew its licensing for SMG 10.6 and our Symantec Sales account manager answered with this very simple sentence "Messaging Gateway is an end-of-life product that has been discontinued". Being very surprised, I tried to confirm with Symantec support but apparently they had no clue of what I was asking them.
So far, I have 2 different sources at Symantec confirming the product is EOL - excluding their own support.
Did I miss something? Has Symantec already announced EOL of SMG?
Cheers,
X.