![]() ![]() ![]() the Exchange Transport service would not stay running. unless AV scanning transport services were disabled. Even after fixing that issue (days later) a whole other host of issues with the product surfaced. Luckily, I was able to perform a (non-standard) procedure to roll-back the product to the prior version. at 4 am all inbound and outbound email stops processing! The issue this time. #GFI MAILESSENTIALS NO USERS UPDATE#Ī failed AV engine update on a DIFFERENT AV scan engine tanked the product. 45 minutes in the queue, only to be told to leave a message and I will be contacted. I thankfully was able to find the cause of the issue in their tech support forum. because if it was up to their support desk. I speak the truth, and had to get the word out. We have used this for years on an Exchange 2003 box. Required a lot of management in terms of tweaking settings to adapt to new spam tactics, finding false positives, and patching bugs. Support was good but it was time consuming to get them the information they needed. Otherwise was stable and extensive logging ensured I could track down just about everything. Recent versions introduced a fairly clunky web interface, although its search functions are fast. If I leave the web interface open on the server overnight, there is a memory error in Internet Explorer. To its credit, recent versions of MailEssentials introduced an ability to customize which users use which filters. For example, the SPF filter is too aggressive because increasingly companies are not properly configuring SPF in DNS. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |