On 8/30/14 2:59 AM, Matthias Andree wrote: > Am 30.08.2014 um 06:09 schrieb wandns: >> >> I'd like to add MAPI support to Mutt. > > Why does one need that? As far as I understand all MAPI-compatible > servers can be made talk IMAP. > > I once had a contributor offering MAPI support for fetchmail, as Google > Summer of Code student, and he did something, but he never got it to a > state or was responsive enough so that this could be tested or > integrated, and I was never offered a test account on Exchange server so > I could test and finish the work myself...
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? I am able to test against an Exchange 2010 installation. Thanks for your input. AD
signature.asc
Description: OpenPGP digital signature
