K9MailAndExchange

cketti edited this page Feb 8, 2017 · 10 revisions

Configure K-9 Mail to work with Exchange

K-9 uses WebDAV to communicate with Exchange. As of Exchange 2010, WebDAV is no longer supported. For this reason, K-9 is unable to work with Exchange 2010 at this time. It will be a major effort to correct this issue.

The parts of K-9 that connect and authenticate with Exchange were rewritten in version 3.400. These changes were tested with Exchange 2007 using form-based authentication. The following is a basic description of these options. For a more in depth discussion of how K-9 communicates with Exchange, see the following blog post.

Configuring K-9 Mail

  1. When creating a new account, enter your email address and password in the corresponding fields and press Next.
  2. On the next screen, press the 'Exchange (WebDAV)' button.
  3. Enter your Exchange server configuration as follows:
    • Username: domain\username
    • Exchange server: mail.company.com
    • Security type: select your security type, hopefully 'SSL (always)'
    • Port: populated automatically
    • Mailbox alias: I have found that you should typically set this to your email address. Leaving it blank will use your username, which also works for some Exchange installations.

The following options are "advanced" options, and users should not need to change them from the defaults.

  • OWA path: leave this field blank - defaults to /Exchange
  • Authentication path: leave this field blank - defaults to /exchweb/bin/auth/owaauth.dll

NOTE: Setting your 'OWA path' to "owa" is incorrect! If you enter values into either 'OWA path' or 'Authentication path' and then open an issue, the first thing I will tell you is to leave them blank. Please, save me the trouble.

If you receive a 501 error in your logcat output after K-9 authenticates successfully, try setting your 'Mailbox alias' to your email address. Note that WebDAV is not enabled by default on Exchange server 2007, and must be enabled for K-9 to work. If you receive a 403 error in your logcat output, chances are WebDAV has not been enabled.