Gfi mailessentials blocking internal email

#GFI MAILESSENTIALS BLOCKING INTERNAL EMAIL INSTALL#
#GFI MAILESSENTIALS BLOCKING INTERNAL EMAIL UPDATE#
#GFI MAILESSENTIALS BLOCKING INTERNAL EMAIL SOFTWARE#
#GFI MAILESSENTIALS BLOCKING INTERNAL EMAIL DOWNLOAD#

The set up of the software and rules were easy, the GUI (html page) for the end-users could use some work, and seems to hurt more than it helps. I was hoping it would have worked as-is and no back-end editing would have been needed. They fixed the mdb file and returned it to me. mdb file that ME uses and a report from their software.

I called their technical support and they asked that I send over the.

I'd get false positives, but that's a problem with all spam filters until you teach the white-list.Р”Р„fter three weeks of 'approve' or 'whitelist and approve' choices made on the messages, I realized from a rather heated employee that they weren't getting any e-mails they thought should be coming through. It was catching spam and even some virus/malicious messages as well. I installed it using their instructions, and started using it right away.

#GFI MAILESSENTIALS BLOCKING INTERNAL EMAIL DOWNLOAD#

I've been using the freebie download for about a month and it has had its problems. I would strongly recommend using anything else. So, there are currently no specific plans to change the implementation.' This is what technical support 'This is the way the sanitize function works at the moment is how the functionality was designed and implemented in MailEssentials.This is not a bug or a fault in the software. We block credit card numbers from being sent via email using their content filtering and the 'Sanitize and Approve' 'FEATURE' takes only the credit card numbers we didn't want to be sent out and sends them in a report to the recipient instead of sending the email without the CC numbers like one would assume the feature does. On top of that you cannot sort spam items to easily remove items with the same subject line or by the same sender. Makes it a nightmare if you have had a large amount of spam quarantined. The quarantine folder only views 10 items by default and after changing to a higher number and dealing with them it reverts back to 10 items. Now I would use a hosted antispam solution like Appriver. Originally we chose this over hosted antispam solutions because we had so many alias domains and the hosted solutions at the time had licensing models that made this unaffordable. So you can pick and choose depending on the amount of spam a user gets. But if you turn it off for everyone, suddenly you are at risk of a lot of phishing spam. For example, the SPF filter is too aggressive because increasingly companies are not properly configuring SPF in DNS. To its credit, recent versions of MailEssentials introduced an ability to customize which users use which filters. If I leave the web interface open on the server overnight, there is a memory error in Internet Explorer. Recent versions introduced a fairly clunky web interface, although its search functions are fast. Otherwise was stable and extensive logging ensured I could track down just about everything.

Support was good but it was time consuming to get them the information they needed. Required a lot of management in terms of tweaking settings to adapt to new spam tactics, finding false positives, and patching bugs. We have used this for years on an Exchange 2003 box. I speak the truth, and had to get the word out. because if it was up to their support desk. I thankfully was able to find the cause of the issue in their tech support forum. 45 minutes in the queue, only to be told to leave a message and I will be contacted.

#GFI MAILESSENTIALS BLOCKING INTERNAL EMAIL UPDATE#

a failed AV engine update on a DIFFERENT AV scan engine tanked the product. at 4 am all inbound and outbound email stops processing! The issue this time. Luckily, I was able to perform a (non-standard) procedure to roll-back the product to the prior version. Even after fixing that issue (days later) a whole other host of issues with the product surfaced. unless AV scanning transport services were disabled. the Exchange Transport service would not stay running. they dumped their 'VIPRE' AV scan engine, and did not transition the licensing and product correctly. The version was clearly not ready for primetime.

#GFI MAILESSENTIALS BLOCKING INTERNAL EMAIL INSTALL#

my users were so inundated with SPAM that I opted to install it within days of release. Normally, I would not install an update so close to its release date, but. Their most recent release (version 21) have caused me over 2 weeks of grief. Spam and Malware getting through has gotten worse and worse in this time as well. their updates to their AV scan engines have tanked the product. support (I have always have had active maintenance) was able to get me through their issues and get me going again. It started with software updates going bad occasionally. In the past 2 years, the product and company has gone downhill. I have used GFI MailEssentials for years, since Exchange 2003.

Gfi mailessentials blocking internal email