rockshox

Same problem here on an ASUS RT-N66U (latest firmware) and ESET Nod32 7.0.302.26. Problem occurs with both Internet Explorer and Chrome. Excluding the IP of the router under Web and Email > Protocol Filtering > Excluded IP Addresses corrects the problem.

Probably related to the bug that has been in ESET for quite some time that resends threats to ERA multiple times long after they occurred. As an example I have one right now I'm looking at in ERA that shows Date Received "3 Months Ago" but Date Occurred "5 Months ago". However if I look further back in the logs I can see the same threat was already reported 5 months ago, so something triggers the client to resend it. I've seen the problem through all the variants of NOD32 version 4 and now ESET Antivirus 5. I've always just ignored it as it happens once in awhile, but I'm guessing this could be triggering your e-mails on threats that have already occurred.

Can we get an official reply from ESET that ESET products do not contain governmental backdoors (for any government)? While I can see several moderator responses, nobody actually answered the question and said that there was definitely not a backdoor for governmental use. Saying that it does not contain malware is great and expected, but if a backdoor existed, it would not be considered "malware" by the people who wrote it. With all the "governmental spying" issues in the news these days. It would be good to have some peace of mind with ESET products.

When you create a package in ERAC it is not modifying the MSI files that you select when creating a new pacakge. If you are making your changes, and then copying the MSI that you loaded to create the package to a computer, you are not copying a modified MSI file. ERAC creates a package located under: C:\ProgramData\ESET\ESET Remote Administrator\Server\packages\install_v3\<package name here>\package_nt64.nip (for 64-bit). If I remember correctly you can take this package, rename it to package_nt64.exe and then run it from a computer and it will install per the settings created when making the package.

Yes, I don't know what happened either as I've made changes to policies for our different products for years. I've never seen it mark every single item for every product on it's own. I am running the latest version of both ERAS and ESMX. I was able to fix the problem by unmarking everything, saving the policy. I then reopened the same policy and imported the backup and it correctly imported the config.

Thanks for the information. I set this up and tested it this morning with about 12 domains, seemed to work fine. I then created a comma separated list of the complete whitelist (about 70 items) that I was attempting to use. Copied that into Allowed Senders List in ESET Configuration Editor. The mail servers checked in and grabbed the new list, but then immediately started giving errors about web protection and other things which was odd. I went back to my policy and found that EVERY single setting for every single product was now marked to be sent to the client and it sent the default settings to both my mail servers. Luckily, I made a backup before the changes so I figured no problem, I'll unmark everything and import from my backup. It appears my current EMSX policy is now corrupted as every time I import from my backed up policy it marks EVERY single setting for EVERY single product. If I create a new policy and apply my backup xml file, it works fine and brings in all my settings correctly. However if I apply that same XML to my existing Policy it checks every single setting and marks it to deploy.

Update - If I add the whitelist addresses/domains one at a time from the GUI they add to the list correctly. I could go through and add the domains/e-mail addresses manually but I really should be able to copy/paste them into the approvedsenders file without it erasing them and reverting back every time.

Hello - I am in the process of cleaning up our anti-spam settings and getting some domains added to whitelisting. We are running EMSX 4.5.10011. In the past, I have manually edited the approvedsenders file and restarted the antispam module and all was good. However, when I try and do that now, all my changes are removed and the settings revert back to the way they were before. Can the approvedsenders file still be updated manually?