Comment 3 for bug 798607

Sandra, Marco,

Let me first re-assign this bug to the normal addons, as the oulook plugin is now located in the official addons (this old project is kind of deprecated and not watched anymore, so the bug was not picked up in our bug triage process).

Secondly, thanks for the great analysis Marco. Looking at Microsoft's KB [1] about the error message does not yield much more info except that it could be triggered by accessing a missing property... indeed.
Based on the scenario you are describing and the availability of the PR_TRANSPORT_MESSAGE_HEADERS(_W) properties, we should thus be able to make the plugin handle more gracefully the various cases (around here: [2]).
Perhaps in the case of local exchange messages (within PR_TRANSPORT_MESSAGE_HEADERS_W if I understand correctly), there is another header value with a unique ID we could use instead of the usual Message-ID. If you have any further info or references about these headers and their values, do not hesitate to comment.

In any case, I'm correcting the bug status to indicate that it is currently under investigation by OPW.

Thanks!

[1] http://support.microsoft.com/kb/179639
[2] http://bazaar.launchpad.net/~openerp/openobject-addons/6.0/view/head:/outlook/plugin/openerp-outlook-plugin/tiny_xmlrpc.py#L154