Skip to main content

Email Notifications w/ Symantec Drive Encryption Standalone (without Management Server) 10.3

Thread needs solution

I'm trying to use email notifications (DRP and job status) in Acronis Backup 11.5 build 43800 on an ASUS N550JK laptop running Windows 10 Pro.  The system disk is encrypted with Symantec Drive Encryption Standalone (without Management Server) 10.3 MP11 (aka PGP Desktop w/ Whole Disk Encryption).

When sending a test message I immediately get a socket reset error; the Acronis KB suggests that the port is blocked at the firewall and that port access should be configured and tested from other applications (e.g., telnet).

My PGP license includes message encryption, and left to its own devices, it will intercept and proxy all traffic on ports 25, 463, and 587 (and maybe others).  I have ensured that messaging is disabled in PGP and I have verified that I can connect to my mail server on all 3 of the ports listed above and that I can send mail using telnet, Windows Mail, Zimbra Desktop Client, and Thunderbird.  

For good measure, I did all testing twice: once with all Windows Firewall profiles running and again with the firewall completely disabled.   I then expanded testing to 2 other systems: a Dell Latitude and a Dell Inspiron.  

This issue is consistent in testing across all 3 systems, all running clean Widows installs with *only* driver packages, PGP, and Acronis Backup installed. (To be very clear, the drives were wiped and Windows 10 was installed using media downloaded directly from Microsoft.)

If I decrypt the disks and uninstall PGP, Acronis Backup sends email without a problem.  The issue is clearly a conflict of some sort between Acronis Backup and PGP, and appears to be specific to Acronis Backup.  Acronis Backup absolutely will send email while PGP is installed - but no other clients have a problem.  

Other than switching to another encryption provider, can anybody offer any advice?

TIA,

-j

 

0 Users found this helpful

Hello,

We use standard SMTP to send messages, so it's really wierd that you're seeing an error only in Acronis and not in other SMTP clients. Do all the different clients you tried use the same settings as Acronis?

I would suggest running Wireshark and filtering on the port you use to see details on why/how this is being blocked. We have instructions on doing this in our KB at the following link: https://kb.acronis.com/content/1763