On Tue, 2009-02-03 at 13:43 -0500, [email protected] wrote: > I installed libmapi 0.8 and started rewriting exchange2mbox in order > to produce single files that I can cat&pipe into procmail and that > include the complete headers, so I can actually reply to emails. Works > ok, however there are many emails where body.length seems to be zero, > so nothing besides the header is downloaded. If I try openchangeclient > --fetchmail on these mails I get an "invalid message" error.
Hi Dirk, "invalid message" errors are generally displayed when the message openchangeclient deals with is either a meeting request or mail delivery report. > I need some directions here. For starters I'm wondering whether the > implementation of exchange2mbox is actually a good starting pint or > not. It seems to be a bit old Does old code necessarily means bad code? ;-) > and since it doesn't output any email addresses (only display names) > I'm wondering whether it was ever meant to be used in a production > system. It was originally a tool I wrote during an afternoon at SambaXP 2006, so no it was not meant to be used in production system - as it is. For the TNEF problem you mention in further mail, Brad should normally be working on this issue at some point. That's one of the last mapitest unit test still failing. > I would appreciate it if someone could give me some pointers in the > right direction or some sample code to build upon. What kind of pointer/code sample are you looking for? > P.S. Programming language is another question. I'm not a C enthusiast > at all. Are the Python bindings usable, or is that still work in > progress? Still WIP. Cheers, Julien. -- Julien Kerihuel [email protected] OpenChange Project Manager GPG Fingerprint: 0B55 783D A781 6329 108A B609 7EF6 FE11 A35F 1F79
signature.asc
Description: This is a digitally signed message part
_______________________________________________ devel mailing list [email protected] http://mailman.openchange.org/listinfo/devel
