MAPI backend (was: Offtopic: Forwarding in MS Outlook)

[Roman Belenov <roman@nstl.nnov.ru>]

[-- Attachment #1: Type: text/plain, Size: 965 bytes --]

If anybody is interested in writing MAPI-based mail fetcher, here is a
program I made for personal usage from PMSEU utility
(http://www.genusa.com/utils/pmseu.htm). It is written in Visual Basic
(it was first time I've done something with this dialect - never used
Basic since my schooldays :-). All parameters are hardwired; some
command line/config file parsing should make this utility quite usable.

The original program seems to be in public domain (although I'm not a
lawyer); I don't claim any rights on my code too. Anyway IMHO it
should be rewritten in C++ (should not be too hard since COM
interfaces are almost the same) and given proper interface (like
GNUish command-line parsing), so it can be made decent part of Emacs;
I don't sure I'll do it myself (the "get a disclaimer from your
employer if relevant" part seems to be the hardest - there were no
precedents in the company I'm working for and it seems that procedure
will be quite complicated).


[-- Attachment #2: Type: text/plain, Size: 1249 bytes --]



Andrew Innes <andrewi@gnu.org> writes:

> A better solution would be to write a variant of movemail.exe that uses
> MAPI to get mail directly from the Exchange server.  When I first
> started at my current job last summer, I thought I would have to do
> this, but then found out the POP3 service was actually installed and it
> was a DNS problem stopping me from seeing it.  So I never got as far as
> writing this program, although a month before that there was some
> discussion about it.  The mail is archived here:
> 
>   http://www.egroups.com/messagesearch/ntemacs-users?query=mapi
> 
> But if you are willing to work on it (necessity and all that), then I
> can offer some help.  Even though I have POP access to Exchange, I would
> actually prefer to have direct MAPI access, because the POP service
> seems to take it upon itself to reformat messages, wrapping long lines
> and omitting some "inline" attachments, and generally doing things that
> irritate me.
> 
> We could also provide the sending part of the MAPI solution, and make
> the whole thing part of Emacs proper, if you are willing to assign
> copyright to the FSF (and get a disclaimer from your employer if
> relevant).
> 
> AndrewI
> 
> 

-- 
 							With regards, Roman.