EV will not archive e-mail alerts from sharepoint

[Nate_D1]

Has anyone ran into an issue where vault will not archive the alert e-mails from sharepoint?

We are running EV9 (very soon to be EV10) and sharepoint 2007 and when a user gets an email alert (for example, an item added to a document library, modification to a item, etc.) those email alerts error out with: "Cannot move the items. The item cannot be moved. It was either already moved or deleted, or access was denied." (with a manual move). I am not sure how they behave when they hit the automatic archive threshold (for us is 90 days).  Other emails can be archived manually with no issue.

Im at a bit of a loss on how to troubleshoot this, or what the issue might be. When I compare the message properties of a sharepoint alert vs. a standard email message they look alot different. For example,

a standard plain-text email:

Received: from xxxxxxxx by xxxxxxxxx with
Microsoft SMTP Server id 0; Thu, 13 Sep 2012 06:00:53 -0700
thread-index: Ac2Rr89IFyBDLxGhSLySRBnB2iq/jA==
Thread-Topic: Daily Storage Alert!
From: <xxxxxxxxx>
To: <xxxxxxxxx>
Subject: Daily Storage Alert!
Date: Thu, 13 Sep 2012 06:00:54 -0700
Message-ID: <2C49884B540741CAABxxxxxxxxxl>
MIME-Version: 1.0
Content-Type: text/plain  (I think this is the ‘type’ of message)
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft CDO for Windows 2000
Content-Class: urn:content-classes:message
Importance: normal
Priority: normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.1.7601.17609
Return-Path: xxxxxxxxx
X-Auto-Response-Suppress: DR, OOF, AutoReply
 

And here is the properties of a sharepoint alert email:

Received: from 000000000 by
000000000 (000000000) with mapi; Thu, 13 Sep 2012 09:32:03
-0700
Content-Type: application/ms-tnef; name="winmail.dat" (This type is quite different looking)
Content-Transfer-Encoding: binary
From: 000000000
To: 000000000
Content-Class: Sharing
Date: Thu, 13 Sep 2012 09:32:03 -0700
Subject: FW: Mike's Weekly NWR Simulation Report
Thread-Topic: Mike's Weekly NWR Simulation Report
Thread-Index: Ac2McpZbOXJP0weXTtioMn4fQU000000000TQhA=
Message-ID: <9C10004F750EE641AAF742B6E3694CFA03E5000000000>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-Exchange-Organization-SCL: -1
X-MS-TNEF-Correlator: <9C10004F750EE641AAF742B6E3694CFA03E000000000>
x-sharing-capabilities: 809
x-sharing-flavor: 30B
x-sharing-instance-guid: C2EF00000000074986CBD2263FE98E39
x-sharing-provider-guid: ADF0060000000000C000000000000046
x-sharing-provider-name: SharePoint
x-sharing-provider-url: http://www.microsoft.com/sharepoint/
x-sharing-remote-path: http://000000000/Mikes%20Weekly%20NWR%20Simulation%20Report
x-sharing-remote-name: Weekly NWR Simulation Report
x-sharing-remote-uid: {EEC5D902000000000D5837E38171}
x-sharing-remote-store-uid: http://000000000/WholesaleActivityRR
x-sharing-remote-type: documents
x-sharing-config-url: stssync://sts/?ver=1.1&type=documents&cmd=add-folder&base-url=http%3A%2F%2F000000000%2Fsites%2Fteams%2Fmore%2FWholesaleActivityRR&list-url=Mikes%20Weekly%20NWR%20Simulation%20Report&guid=%7bEEC5000000000%2d4056%2dACBC%2dCD5837E38171%7d&site-name=Wholesale%20Activity%20Risk%20Reporting&list-name=Weekly%20NWR%20Simulation%20Report
x-sharing-browse-url: http://000000000/WholesaleActivityRR/Mikes%20Weekly%20NWR%20Simulation%20Report
x-sharing-local-type: IPF.Document
MIME-Version: 1.0
 

Any thoughts on this?

[JesusWept3]

Whats the message class on it? im guessing its an IPF.Document?

[Nate_D1]

In the second message at the bottom it says:

"x-sharing-local-type: IPF.Document"

I would guess so too! Im not sure how to check other than that. :(

[TonySterling]

In Outlook right click the header bar in the Inbox and choose Field Chooser.  Then select All mail fields can drag Message Class to the header bar.  This will display the message class for the items.

[Nate_D1]

That works, thanks! 99% of the messages I am seeing are IPM.Note, however the message type of the sharepoint alerts are IPM.Sharing

[TonySterling · Accepted solution]

Ok, you can add that Message Class to EV on the Directory properties page.  Then enable it in the archive policy and EV will archive it.

[Rob_Wilcox1]

As Tony says..

It's not anything to do with the headers and so on with the message - EV doesn't worry about those too much.  The part that is the 'issue' is that the message class is NOT the regular IPM.NOTE, so you have to add it into the Directory properties, and then in to the Mailbox Archiving Policy/Policies.

[Nate_D1]

Hey Guys, Thanks for the responses! I am not sure where you are talking about with the 'directory properties'. I found where I would be able to enable it (in the message classes tab, on the properties of the mailbox policy).

Could either of you elaborate a bit?

Thanks!

[Nate_D1]

Doh, nevermind. I literally found it seconds after I hit 'save'.

Thanks guys!

[Rob_Wilcox1]

That happens to me alot too. For clarity, you right click on your Directory node in the VAC, and go to properties. There is a message classes tab, when you can add new message classes. Then you can enable them in your policy.