Mail for Exchange

m (→Why feature XXX is presented in S60 and not presented in N900?)
m (→Server certificate is valid and trusted byt MfE fails to sync)
Line 98: Line 98:
Unfortunately, there is no way to disable certificates check at the client side in the current MfE release.
Unfortunately, there is no way to disable certificates check at the client side in the current MfE release.
-
==== Server certificate is valid and trusted byt MfE fails to sync ====
+
==== Server certificate is valid and trusted but MfE fails to sync ====
Check [https://bugs.maemo.org/show_bug.cgi?id=7357 this bug.]
Check [https://bugs.maemo.org/show_bug.cgi?id=7357 this bug.]

Revision as of 14:45, 6 January 2010

Contents

Mail For Exchange (MfE) Heartbeat and FAQ

This page answers the questions which are commonly asked by new N900 MfE users. It is mostly based on the analysis of the MfE support thread.

This page is planned to be updated for every new MfE release.

Current version of the page describes the MfE software which can be found in sales box (sales release).

Compatibility

What server versions are supported by N900 MfE client?

MS Exchange 2007 with service packs on top. MS Exchange 2010 also works fine according to the users reports.

What server versions are NOT supported by N900 MfE client?

  • MS Exchange 2003 (is supported in the first MfE update which is not available for public yet).
  • All non-MS services (e.g., google).

How can I check is my server version supported or not?

  1. Take the logs following the steps described in the section How can I turn the logging ON or OFF?
  2. Grep (search) for "MS-ASProtocolVersions:" in the logs. If it contains "12.1" token, there is no problem with the version of your sever (if it is MS Exchange server, not something else).

Why feature XXX is presented in S60 and not presented in N900?

S60 and Maemo MfE are different MfE implementations.

The table below tries to summarize the most important differences between S60 and Maemo MfE implementations.

Feature S60 status Maemo status
E-Mail YES, subfolders are not synced YES, subfolders are synced
Calendar YES YES
Tasks YES YES
Meeting invitations replying YES NO
Corporate address book (GAL) YES NO (is supported in the first MfE update which is not available for public yet)
Exchange servers support 2003, 2007 2007 (2003 is supported in the first MfE update which is not available for public yet)
Autodiscover YES YES
Provisioning support Partly YES NO

Lack of provisioning support in N900 MfE implementation is the most common root cause for inability to use N900 MfE with corporate Exchange servers in North America. See Provisioning for additional details.

Known issues

Provisioning

N900 is considered to be "non provisioning device" from Exchange server PoV. It basically means that it can not be managed from Exchange server - administrator can not wipe your device, request you to use autolock and so on. Basically, all the provisioning data received from the server is ignored and the server is informed that N900 MfE does not support this feature.

Exchange administrator can configure the server in 2 ways - he/she can allow to use non-provisioning devices or disallow. In the second case N900 MfE will not work as server will reject the connection.

Post with Exchange server 2003 management console

SSL-related errors

The error message is displayed "Exchange server requires secure connection or account is disabled".

This infamous error message is caused by the fact that server certificate is untrusted from Maemo MfE client PoV.

Possible root causes and workarounds:

Server certificate is either self-signed or signed by the non-trusted authority (root certificate is not visible in N900 "Certificates" application).

In this case, the server certificate shall be added to N900 certificate storage. Check this message and the thread after it for additional details.

Keep in mind - self-signed certificate shall have "CA" field. Otherwise, N900 certificate manager will not allow to install it.

Another important hint about importing certificates.

Unfortunately, there is no way to disable certificates check at the client side in the current MfE release.

Server certificate is valid and trusted but MfE fails to sync

Check this bug.

Troubleshooting

How can I turn the logging ON or OFF?

In order to turn the logs ON:

  1. Install syslog and reboot the device
  2. open terminal
  3. Execute the command: sudo gainroot
  4. Execute the command: cat /dev/null > /var/log/syslog
  5. Execute the following commands:
    1. gconftool-2 -s --type=int /apps/activesync/AsDaemon/Syslog/MinLogLevel 0
    2. gconftool-2 -s --type=int /apps/activesync/modest/Syslog/MinLogLevel 0
    3. gconftool-2 -s --type=int /apps/activesync/AsProvider/Syslog/MinLogLevel 0
    4. gconftool-2 -s --type=int /apps/activesync/AsBackup/Syslog/MinLogLevel 0
    5. gconftool-2 -s --type=int /apps/activesync/asapplet/Syslog/MinLogLevel 0
    6. gconftool-2 -s --type=int /apps/activesync/AsStatusApplet/Syslog/MinLogLevel 0
  6. Reboot the device
  7. Initiate the synchronization session

/var/log/syslog will contain the logs. In order to filter only activesync-specific logs the following command can be used: 

     grep activesync /var/log/syslog

In order to turn the logs OFF, execute the following commands from xterm: 

    gconftool-2 -u /apps/activesync/AsDaemon/Syslog/MinLogLevel
    gconftool-2 -u /apps/activesync/modest/Syslog/MinLogLevel
    gconftool-2 -u /apps/activesync/AsProvider/Syslog/MinLogLevel
    gconftool-2 -u /apps/activesync/AsBackup/Syslog/MinLogLevel
    gconftool-2 -u /apps/activesync/asapplet/Syslog/MinLogLevel
    gconftool-2 -u /apps/activesync/AsStatusApplet/Syslog/MinLogLevel

After device reboot the logs will not be collected.

Retrieved from "http://wiki.maemo.org/Mail_for_Exchange"