Emon Attempt to save changes in email failed error

Getting 100s of these in the log and have yet to find any real information on the cause or solution. Can anyone tell me anything about it?

 

Hi Breach, welcome to Wilders.

Do you draw in a HTTP account such as Hotmail or Yahoo?

I receive the same errors and this is the cause as far as I know...

Time Module Event User
19/10/2005 22:26:37 PM EMON Attempt to save changes in email failed (message from "xxx @ xxx.com.au", for "xxx @ hotmail.com", with subject "xxx", sent on 10/18/2005 17:06). NT AUTHORITY\SYSTEM

Cheers

 

Here is the exact message

10/19/2005 14:38:31 PM - During execution of EMON - Microsoft Outlook email monitor on the computer xxxxxx, the following warning occurred: Attempt to save changes in email failed (message from "xxxxxx@xxxxxxxxx.com", for "xxxxxxxxxxx", with subject "xxxxxxxxxxxxxxxx", sent on 10/19/2005 14:34).

The "message from" was another private domain address.

My company just installed the NOD32 server and clients just the other day to one of our clients, they run an exchange server for thier mail handling. Appologies, I should have mentioned that bit first

 

Anyone have an idea? Some of my clients are getting hit with 100s of these errors a day and I still have no idea why this is happening.

 

I do not have an EMON compatible e-mail client on my computer. However, do you notice any sort of pattern to these messages? Do they have attachments, for example? Also, are the EMON settings set at their default values?

 

I'll have someone from Eset respond.

Cheers

 

Hello Breach,

MS Outlook sometimes returns senseless messages and EMON is simply reporting them in it's log. On the other hand, have your clients got any adware/spyware resident scanners running? It's possible that another scanner could be modifying any suspicious files which is confusing EMON. As a test, could you try switching off the notification that EMON puts on incoming email?

Bandicoot.

 

I also get a heap of "Attempt to save changes in email" warnings.

I'm new to NOD32, but learning fast. I'm rolling out the Enterprise version and have setup about 30 NOD32 clients so far. Only a few exhibit this problem - some are Outlook 2000 and some are Outlook 2003.

Initially, I thought the problem resulted from our fairly esoteric mail setup. I have an MDaemon mail server, and the Outlook clients sync using MDaemon Outlook Connector. This is configured as an Outlook Information Service plug-in which uses IMAP4 to sync all folders (including non mail folders - Contacts, Caledar, Tasks...) with the mail server. This works really well and is a good alternative to Exchange Server.

I have turned off Scan outgoing email because of another problem with duplicate Sent Items. NOD32 won't let me turn off both Scan incoming email and Scan outgoing email, So I'm considering turning EMON off on the problem clients - I have Kapersky scanning mail on the mail server anyway.

I'm still trying to spot the difference between the clients that exhibit this problem, and those that do not. I have also noticed the warnings seem to come in bursts - sometimes no warnings for hours (or days even) then a bundle.

 

G'day Paul,
I know this is a very old post, but just on the off chance

I have an almost identical configuration using MDaemon, KAV and Nod32, and I get random errors exactly the same, have you found a fix for this, I have just ignored it as the client's not complaining......
I thought it may have been the Outlook Connector.

Cheers Ben.

 

My understanding is that the client uses MS Outlook to retrieve emails from MDaemon via POP3 and EMON intermittently reports this error, right?

 

G'day Marcos,
The clients are using MAPI/IMAP for their mail, they use the "Outlook Connector" which fools Outloook into thinking it's talking with Exchange server, and therefore allows for the "Groupware" functions, shared contacts etc.
The OC talks IMAP to MDaemon and translates it to MAPI for Outlook and viceversa.
More details are here:
http://www.altn.com/products/default.asp/product_id/Outlook+Connector
And yes it does seem random.
The clients don't complain, and it doesn't seem to cause any big issues, but we get sent an admin alert from Nod32.

Cheers Ben.

 

Is there something specific about these emails? E.g. if it happens only with certain html emails whilst all plain-text emails are ok.