From: Matthias A. <mat...@gm...> - 2014-08-31 20:10:40
|
Am 30.08.2014 um 15:59 schrieb Alex DuBois: > I've noticed that over the last several years Microsoft Exchange has > been replacing other corporate email solutions at a steady pace. When > I say that, I'm referring to client access, not the core. That in > itself is not a problem since, as you mentioned, it has built-in IMAP > and POP support. The problem that I've run into is that many IT > departments are refusing to enable IMAP or POP capability. Because of > that, many Exchange users can only access their email accounts with MS > Outlook or Outlook Web Access/App. > > I've tried Davmail, but I think that a native solution built into Mutt > would perform better and would be easier for Mutt users to set up. > > Would adding MAPI support to fetchmail only enable receiving via MAPI, > or would support be added for sending as well? The former - fetchmail purely fetches. However I'm not sure if it even builds these days. If you want to give it a spin, you need to check out from Git, or have me generate a tarball for you. You need OpenChange and its developer stuff installed, along with the usual C compilers and GNU autoconf, automake and gettext, and openssl developer files. If you want to try it, clone from one of the addresses shown in the box at the top of https://gitorious.org/fetchmail/fetchmail/commits/BRANCH_MAPI If you haven't cloned, try git clone --branch BRANCH_MAPI URL-FROM-GITORIOUS LOCAL_DIR (replace the last two strings here!) Then do: autoreconf -i mkdir _build cd _build ../configure -C --enable-MAPI > I am able to test against an Exchange 2010 installation. Let me know what you get; best to do this through the fet...@li... mailing list. The list has an information page at <https://lists.sourceforge.net/lists/listinfo/fetchmail-devel/>. |