NOD32 v4 - Special Character Conversion

We're running an SBS 2008 Server with Remote Administrator.

The Workstations run NOD32 v4 with Windows XP, Outlook 2003 and 2007 across various machines.

When sending a new email with the following text:-

Ok’s, I’ve re-installed the A/V.
• It’s a fresh email’s
• Is it still convert’n ?

The recipient gets hyphens, apostrophies, bullet points, etc. converted to other special characters, they'll see the following:-

Ok s, I ve re-installed the A/V.
 It s a fresh email s
 Is it still convert n ?

There is actually a question mark with a box around it where the apostrophies were (not visable here).

When NOD32 is un-installed from the workstation, the problem does not occur. However when re-installing NOD32, the problem re-occurs.

Is there an issue with special character conversion with NOD32, if so, what is the fix / work around.

 

Hello,

Make sure you have the latest version 4.0.474 installed on the clients. The POP3 Compatibility setting is the next thing I would try adjusting to see if the problem can be a quick fix. On a test client, open the ESET software and access the Advanced Setup window by pressing F5. Then navigate to Antivirus and antispyware -> Email client protection -> POP3, POP3S -> Compatibility. Change the setting to Maximum compatibility and then try to replicate the problem.

 

Does disabling integration with MS Outlook make a difference? If so, enable integration and disable scanning of outgoing email to see if it helps.

 

Thanks for the prompt feedback, tried all suggested options, results as follows:-
1. Un-installed and Re-installed version 4.0.474 of A/V Business Edition: Problem still present.
2. Adjusted / tested with all levels of the POP3, POP3S Compatability options: Problem still present in all adjusted levels.
3. Within Advanced Options, Email Client Protection --> Email Clients, un-checked the "Sent Items": Problem Resolved.

Given that our Exchange Server will scan outgoing messages, I'm not overly concerned that the outgoing mail on the clients is not being scanned. At the risk of not sounding grateful, this solution is essentially a work around which is Ok temporarily, however I would love to see a permenant solution that actually resolves NOD32 from changing the characters.