Izzy

Quick update: Have tried installing the latest Microsoft Office patch and this has not helped to resolve the problem. Latest version of Outlook: 1801 (Build 9001.2171, Click-to-Run) (Monthly Channel).

More users affected by this today - I assume some update from Microsoft is causing this and it becomes apparant after each client installs the update...? FYI: This could be a coincidence but it seems that those users affected by this ESET issue are also unable to forward attachments from plain text e-mails (even with ESET disabled). This sounds similar to an an issue that .msi installations of Office 2016 were experiencing following the January KB4011626 update and MS issued a patch for that: "https://support.microsoft.com/en-gb/help/4011626/descriptionofthesecurityupdateforoutlook2016january9-2018" The patch cannot be applied to Office 365 installations. Our Outlook Versions are: 1801 (Build 9001.2138 & Build 9001.2144, Click-to-Run) (Monthly Channel).

We're using Exchange Version 15.0 (Build 1130.7). Outlook Version 1801 (Build 9001.2138 Click-to-Run) (Monthly Channel). Only some users with this setup are currently affected - others aren't. Another user started to have this problem today (they were fine yesterday). If' I'm able to get on a affected PC and try a different mail server I'll report back.

Hi Marcos, Yes disabling those two options ('sent' and 'add addresses from outgoing messages') on ESET Endpoint Security allows our affected users to send e-mail whilst keeping ESET going for incoming email. Thanks.

Hi, We're using: Eset Endpoint Security 6.6.2072.2 (and 6.6.2072.0); Windows 8.1; MS Outlook 2016 (Office 365, 16.0.9001.2102, 64-bit) - and some of our users are experiencing this issue. I have tried just disabling the scanning of sent email but that does not help. Disabling the integration of Eset with Outlook does help. Hoping the will be an update soon. Is this the best place to lookout for any fix?