2 Dec
2009
2 Dec
'09
9:53 p.m.
On Wed, Dec 02, 2009 at 02:12:35PM +0100, Sandra Kachelmann wrote:
hi
i'm working for a company that uses exchange as a corporate
mailserver. unfortunately the admin boneheads don't allow me to
connect via imap. however, i managed to create connectivity via
openexchange (libmapi). i can list all my folders, retrieve mails and
so on. the ideal solution for me however would be to use imap. a bit
of research led me to perdition. if i could have something like a
local imap2mapi proxy this would solve my problem. perdition would
have to use libmapi (http://www.openchange.org/) as backend and
translate imap commands to mapi (vice versa).
has this been discussed before? is something like that planed? are
there better ways or other solutions available to my problem?
any input is gratefully appreciated.
Hi Sandra,
interesting problem :-)
At the current time perdition doesn't support translation between protocols
because after the authentication phase it understands nothing about
how the underlying protocols work - it just blindly passes bytes around.
For this reason if mapi support was added to perdition the best fit
for the current code-base would simply be a mapi-to-mapi proxy,
adding to the existing imap-to-imap and pop-to-pop capabilities
of perdition. I note that mapiproxy[1] seems to already implements
a mapi-to-mapi[1].
To implement an imap-to-mapi or mapi-to-imap proxy would require perdition
to be extended in order to understand both imap and mapi after the
authentication phase, and how to map between the two protocols. To be
honest I don't know enough about mapi to know if this is even possible. But
I suspect that rather than modifying perdition it would be somewhat easier
write something from scratch to investigate the idea.
[1] http://mapiproxy.openchange.org/