After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 633121 - Fetch also Content-class message header
Fetch also Content-class message header
Status: RESOLVED FIXED
Product: evolution-mapi
Classification: Applications
Component: Mail
2.91.x
Other Linux
: Normal major
: ---
Assigned To: evolution-mapi-maint
evolution-mapi-maint
Depends on:
Blocks:
 
 
Reported: 2010-10-25 18:01 UTC by Reid Thompson
Modified: 2010-12-13 10:41 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
proposed ema patch (3.41 KB, patch)
2010-11-02 13:22 UTC, Milan Crha
committed Details | Review

Description Reid Thompson 2010-10-25 18:01:20 UTC
Evolution-mapi shows these for Show All Headers
To: Reid Thompson <Reid.Thompson@xxx.com>
Subject: FW: Ateb - Costco: Initial Discussion File Transfer from Windows to Tumbleweed
Reply-to: asdfdfd addfdf <adfdsf.dsfdfda@dfdfdf.com>
From: sdfdfdf sdfdf <sdfdf.dfdf@sdfsdf.com>
Message-id: <7C0800F63CCF4149AC0FC5EE2A04122607B169EA@asdfsadfasdfadf.com>
Content-type: multipart/mixed; boundary="=-h4P/ZsfaQKD3Yml4+d7h"
Date: Mon, 25 Oct 2010 13:35:34 -0400
Mime-version: 1.0

-----
Mutt shows these for all headers

X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by asdfadsfadf.com 
	id <01CB746A.CF6C5924@asdfasdfasdf.com>; Mon, 25 Oct 2010 13:34:00 -0400
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01CB746A.CF6C5924"
Content-class: urn:content-classes:calendarmessage
Subject: FW: Ateb - Costco: Initial Discussion File Transfer from Windows to Tumbleweed
Date: Mon, 25 Oct 2010 13:33:59 -0400
Message-ID: <7C0800F63CCF4149AC0FC5EE2A04122607B169EA@asdfasdfasdf.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Ateb - Costco: Initial Discussion File Transfer from Windows to Tumbleweed
Thread-Index: ActxWxkpUvwwa97ISlmQSo9asErf7gDAGPCwAAAAaEAAA9N/kA==
From: "dasfasdf sdafsdf" <asddsf.sdafdf@asdfasd.com>
Sender: "asdfsdf asdfdsf" <asdfdsf.sdfdsf@asdasdf.com>
To: "Reid Thompson" <asdf.asdfasdf@asdf.com>
Content-Length: 9929
Lines: 240

---
in particular, i filter on Content-class: to pipe/parse ics meeting requests to an external program.
Comment 1 Milan Crha 2010-11-02 12:24:05 UTC
How does the mutt connect to your exchange server? The problem is that there is no 1:1 header vs. mapi property mapping in evolution-mapi, so it fails to add all interesting. For cases where exists transport headers are used these, but otherwise are done mappings which are not complete.
Comment 2 Milan Crha 2010-11-02 13:22:44 UTC
Created attachment 173694 [details] [review]
proposed ema patch

for evolution-mapi;

Is it OK to just add the Content-class header? I realized that this one is not shown in my transport headers on the server, but can be fetched from the server separately. Which this patch basically does ( + fixes a memory leak).
Comment 3 Reid Thompson 2010-11-02 19:07:03 UTC
mutt is connecting via imap. 
The mapi interface requires that you explicitly ask for each header??  It doesn't provide a means to 'just get all the headers'??   yuck.

I'll try to get this applied and tested as quickly as possible -- I just got overrun with some issues that are going to keep me pretty busy for the next several days.
Comment 4 Milan Crha 2010-11-03 07:30:43 UTC
(In reply to comment #3)
> mutt is connecting via imap. 
> The mapi interface requires that you explicitly ask for each header??  It
> doesn't provide a means to 'just get all the headers'??   yuck.

You can get all properties stored on the server for an item (message/event/task/...), but these are MAPI properties, which are supposed to be transferred to MIME message. And this mapping (between MAPI property and MIME message header) is up to the reader - evolution-mapi in this case. When you are connecting to your server through IMAP then this all is done by the server, and they have it implemented much better :) Of course, it would be easier if they provide a MAPI interface to directly communicate on MIME level, but that will most likely never happen. (Not talking about MAPI being deprecated since exchange server 2010.)

> I'll try to get this applied and tested as quickly as possible

Thanks, let me know and I will either fix any issues you may encounter or commit it.
Comment 5 Reid Thompson 2010-12-10 14:01:39 UTC
(In reply to comment #4)

> > I'll try to get this applied and tested as quickly as possible
> 
> Thanks, let me know and I will either fix any issues you may encounter or
> commit it.

sorry for the long delay - between work and sorting out build issues on my box it's been a month since i've gotten a successful new build.  I just kicked off a build with the patch applied.  Hopefully I can have you an answer in a few days.
Comment 6 Reid Thompson 2010-12-10 17:13:50 UTC
test meeting request contains the header:
Content-Class: urn:content-classes:calendarmessage

patch appears to meet my requirements.  meeting requests can be identified via the header and filtered appropriately.  Thanks - reid
Comment 7 Milan Crha 2010-12-13 10:40:14 UTC
Thanks for testing. I'm slightly adjusting summary and committing it.

Created commit 6974e6e in ema master (2.91.4+)
Created commit 1d17e26 in ema gnome-2-32 (0.32.2+)