Tese

Requirement has simply been neglected by ESET for over three years now. It's not even mentioned as 'being investigated/working on it'. Alternative solution through real-time scanning is not sufficient/no solution (besides the fact that I still cannot see whether my incoming mails were scanned real-time). I understand that MacOS <> Windows, but it is based on BSD (Berkeley Unix). So how hard can it be?

Because my iMac needs some time to connect to my WiFi-network at startup, I frequently receive a log entry "Date Time - ESET Daemon - Error updating Antivirus modules: Server not found. root". This is an indication that the ESET Daemon hasn't been able to update for lack of an Internet connection after user logon. I have an automatic update entry in the Scheduler with the following settings: Automatic update after user logon; Update; Event triggered; The first time the product starts each day; Minimum task interval 00:00:00 (no limit); Run the task as soon as possible. Can I make the 'Automatic Update after user logon' start with a short delay (one minute or so), in order for updating to start after my iMac has made a connection to my WiFi? Thanks in advance...

@foneil: I forgot to mention that I am still on OS X 10.6.8 (Snow Leopard), not 10.12 Sierra. Unfortunately my 2008 iMac can't run Sierra.

Just installed version 6.3.70.0 over 6.1.12.0, instead of 6.2.6.0. Will see if I encounter any problems.

I will get in touch with ESET customer service regarding my issue. To be continued...

I am using Thunderbird 45.2.0 for Mac. I'll try to replicate your ESET protection summary check above...

I was recently notified that there is a new update for Cybersecurity. The new version is 6.2.6.0. However after I installed this version, it won't run (no eset_proxies or eset_daemon running). I even fully uninstalled the previous version 6.1.12.0 and then installed version 6.2.6.0, but this didn't work either. Has anybody been able to get the new version running?

I was recently notified that there is a new update for Cybersecurity. The new version is 6.2.6.0. However after I installed this version, it won't run (no eset_proxies or eset_daemon running). I even fully uninstalled the previous version 6.1.12.0 and then installed version 6.2.6.0, but this didn't work either. Has anybody been able to get the new version running?

Unfortunately mailboxes are not scanned in CS and CSP in real-time protection. Furthermore in e-mail protection it is advised against having your mailboxes scanned even if CS could scan IMAPS or POPS. So if your email client uses mailboxes instead of separate files for each individual email and you are using IMAPS or POPS, your email is still not scanned! Which takes us back to square one: 'No IMAPS or POP3S scanning ESET for Mac??' Unless somebody has an other solution/workaround?

Slow system shutdown seems to be fixed on 6.1.12.0. However system sleep (Alt-Cmd-Eject) now seems to take forever!? So one thing solved, but gaining a new issue. Can anybody confirm this?

Although I still use Snow Leopard, I get frequent freezes while surfing. I am on Cyber Security 6.1.12.0. I constantly keep my ESET event log open to catch: ESET Daemon - Cannot write to socket: Broken pipe (and ESET Daemon - Child process proxy[xxxxx] did not handle signal 5, restart in 0 seconds). To prevent a system freeze and a required forced power down, I restart the eset_proxy through "sudo killall -9 esets_proxy" in Terminal. @Gabrie: I don't think your "ps -ax | grep esets_proxy" is required. A "sudo killall -9 esets_proxy" will suffice.

Hi Bollicoogee, ESET should work with IMAP. So also Outlook with IMAP. The only thing is that ESET won't handle a secure IMAP-connection . I don't know if Outlook requires a secure connection? An IMAP server typically listens on port number 143. IMAP over SSL (IMAPS) is assigned the port number 993. So ESET's e-mail settings shouldn't include port 993. Check Outlook's specs whether IMAP requires an SSL-connection. Even if downloading e-mail securely isn't scanned by ESET, the e-mail will be scanned in most cases when it is written to the hard disk. This depends on the mailbox-format used by Outlook. If single e-mails are stored as individual files, ESET will most likely be able to scan such a file. If the mailbox consists of multiple e-mails in one single file, ESET will probably not scan an additional e-mail you received. Hope this answers your question or steers you in the right direction? Tese

I have had freezes during surfing at least since 5.0.115.0 (my memory doesn't go back further). None of the v6 releases solved this issue. Highly annoying. To prevent having to hard-reset my iMac, I constantly keep the Activity Monitor and the event log of ESET Cyber Security open. Whenever a "Protoscan Proxy Agent - Cannot write to socket: Broken pipe" appears I have to do a "sudo killall -9 esets_proxy" in Terminal. This happens several times a day. Version 6.0.14.3 released recently didn't solve this issue.

I am not sure whether it has already been mentioned, but I would like the logging to be improved. Looking at the events log, virus definition updates whether succeeded or failed are not listed. If virus definition updates would be logged as well I would know for sure whether those definitions are up-to-date and the update process itself is functioning properly. Currently I only get these update pop-ups. So no update history is available anywhere.

Possible answers to: 3. As I understand it, ESET will not delete an entire mailbox if a single virus file had been detected. The reason for excluding mailboxes from being scanned by default, is due to the fact that mailboxes containing a large number of emails, can become huge. If a single email is put in quarantine, the structure of a mailbox might become corrupted/unstable. So to be sure your mailbox cannot become corrupted, ESET by default excludes mailboxes from being scanned. The cause of this issue is that Apple Mail saves all emails in a single mailbox file, instead of having one file per email. 1. Although I use Thunderbird, which also keeps all emails contained in a single mailbox, you might want to use my approach for scanning your mailboxes occasionally. To prevent a mailbox from becoming corrupted, I make a copy of the mail folder (i.e. /Library/Mail) to a separate location. Then I apply a scan on this copy through the appropriate context menu option. To be sure that all files are scanned thoroughly I had to change the context menu scan profile to include all objects in the ThreatSense Engine setup and at least set Heuristics and Advanced Heuristics under "Scan Options". I hope this helps.