The operation cannot be performed because the message has been changed

[ltfish]

I have used OutlookPrivacyPlugin for a long time, and this is an annoying issue.

When I'm reading/writing emails for a bit longer period of time (e.g. 10 minutes), Outlook 2013 pops up a message box saying that "The operation cannot be performed because the message has been changed." It also occurred when I want to move an old email to another folder. It happens on my IMAP folders, and I'm not sure whether it happens in other folders.

The behavior has been around for quite some versions, and is easily reproducible.

My workaround for now is simply restarting the Outlook, or disable OutlookPrivacyPlugin :-( . I grabbed the code today and wanted to find the root cause. I'll be really grateful if you have any idea of what might be going on.

Thanks!

[Meddington]

Is this any email or emails marked for encrypt/sign?

[Meddington]

I was able to reproduce this issue, looking into it.

[ltfish]

There is no email marked for encryption or signing in the current folder. There are a few encrypted ones in the same email account though.

[Meddington]

The only time I can reproduce this is if I create a new email, select encrypt, then let it sit for 10 minutes. Then I receive the error when I hit send. I haven't seen it any other time.

My guess is a draft was saved and somehow modified so when send occurs the open email and draft are seen as different. Just a guess though.

I haven't seen it with the moving emails through different folders.

I also haven't had to restart the plugin. Once the error has occurred it doesn't occur again unless I let another new email sit for 10 minutes with encrypt selected. Doesn't affect other emails non-marked for encryption.

Could you clarify exactly what your seeing? Does this error only occur when moving an email or when an email has been decrypted and let sit for a while? Or does it occur all the time after using outlook for a while?

[ltfish]

Sorry for the long delay.

I can't reliably reproduce this issue. It usually occurs on my machine when a) I write an email, let it sit for 10 minutes or more - without clicking encrypt or sign - and try to send the email, and b) I mark an email as read, and try to move the email to another folder. After several weeks' testing, I'm 80% sure that It does not happen when the plugin is disabled.

My guess is that some internal state about emails become inconsistent, and the state cannot be seen on the UI. I haven't had time to dig into the code, but I'll do it once I'm have some free time.