Hi, we are migrating from exchange 2003 to Exchange 2010. On the new server, messages are getting processed, as the header is being added. But the DisclaimIt body is not being added. In the trace log I get the following lines:

2011-07-04 09:04:32 (#5268): The category of the message is 'Unknown'.
2011-07-04 09:04:32 (#5268): The message was not processed because its category is not supported: Unknown.

Any thoughts? Thanks much!

BTW, It is working through OWA, just not through Outlook 2007..

Hello,

I sounds as if you can easily reproduce the problem. Please perform the following steps:

-Enable trace logging and message logging (Log processed messages & Log ignored messages) on the server.
-Send one or more messages to reproduce the problem.
-Disable trace logging and message logging.
-Send me the compressed content of the folder <InstallDir>\Diagnostics and tell me the sender and recipient addresses of the test messages.

-Franz

Yep, very reproducible. Sent to support email address. Thanks!

Thank you for sending me the requested data.

I analyzed the MAPI-messages and noticed that the MAPI-message-class is "IPM.Note.Default" instead of the standard IPM message-class "IPM.Note". This explains why DisclaimIt does not process such MAPI-messages.

The message-class "IPM.Note.Default" is used when a custom message form is used as replacement for the default global message form (see http://msdn.microsoft.com/en-us/library/bb176910(v=office.12).aspx ).

Are you aware of the use of such a custom global form or is it a left-over from an older Exchange environment?

-Franz

Yes, apparently they have been using a custom form for some time. It did work in exchange2003/disclaimit 3.x.. I understand there is differences in the versions. Is there a workaround for this?

>I understand there is differences in the versions.

Yes, DisclaimIt 4.x is a completely new implementation. It doesn't contain any code from 3.x.

>Is there a workaround for this?

Not with DisclaimIt 4.x. While it would be possible to add support for messages with non-standard IPM message classes to a future version, I'm vary of going this way because you don't just know what's the content of such messages. For more information about restrictions and risks of using a global custom form, please read http://support.microsoft.com/kb/241235/en-us .

I would suggest that the company reconsiders the use of their global custom form. Do they still know why they implemented this solution many, many years ago? ;-)

-Franz

Yes, they are a law firm, and they added a field to track client numbers. I appreciate the input, and we'll see what we can work out.

I'm currently finalizing the next version, v4.6. I'll consider to add a new configuration setting which will allow to specify additional IPM messages classes to process ('at your own risk').

I expect to release the next version within this month.

-Franz

Hello,

DisclaimIt 4.6 has been released.

With this new version you can now configure support for a custom form being used as default form.

Please read the topic "How to Configure Support for Messages with Non-Standard MAPI Identifiers" in the product documentation for more information about how to configure this feature. The example information in step 3.) applies to your case (IPM.Note.Default).


-Franz