Hi Dirk,

On Tue, 2009-02-03 at 13:43 -0500, [email protected] wrote:
> Just joined the list...
> 
> When I ditched Windows about two years ago, importing email from my MS 
> infested employer was one of the easier things: our Exchange server had POP 
> enabled, so fetchmail + procmail did the import job and delivered into 
> Maildir. Two months later the company got sold, IT got "restructured" and we 
> had to switch to "their" Exchange 2003 system. No more POP, but they still 
> had OWA. I wrote a Perl LWP script to get the mail and pipe it into procmail 
> again. Worked fine. Now the company got sold once more (could be good news, 
> actually) and we had to switch mail systems again. This time it's Exchange 
> 2007 inside a VPN. They still have OWA (locked inside the VPN), but OWA'07 
> seems to be useless for grabbing emails. Luckily, there is Openchange. This 
> will allow many penguins to survive in an otherwise un-inhabitable corporate 
> world. :-)
> 
> 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.
> 
> 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 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. I would appreciate it if someone could give me some 
> pointers in the right direction or some sample code to build upon. I'd rather 
> keep my current backend (Dovecot IMAP and Thunderbird), so I'm not really 
> interested in Evolution plugins. The only thing I'm trying to implement for 
> is an application that reliably grabs emails in plain old ASCII MIME and 
> prints them to files.
Have you looked at the fetchmail backend for MAPI that was written as
part of the Summer of Code this year?  That may well fit your needs.

Cheers,

Jelmer
-- 
Jelmer Vernooij <[email protected]>

Attachment: signature.asc
Description: This is a digitally signed message part

_______________________________________________
devel mailing list
[email protected]
http://mailman.openchange.org/listinfo/devel

Reply via email to