+------------------------------------------------------+ | Funambol Community Edition Version 9.0 Release Notes | +------------------------------------------------------+ ---------------- (1) Introduction ---------------- This document is organized as follows: - section 2 contains an overview of the Funambol product components and new features included in this release - section 3 describes the supported environments - section 4 lists the bugs fixed for this release - section 5 contains a list of known issues and of suggested workarounds --------------------------- (2) Components and features --------------------------- The components of the Funambol product in Version 9.0 are: +-----------------------------------+---------+ | Funambol Server Package (*) | 9.0.0 | +-----------------------------------+---------+ | Funambol Administration Tool | 9.0.0 | +-----------------------------------+---------+ | Funambol SDK | 9.0.0 | +-----------------------------------+---------+ | Java ME Email Client | 8.5.3 | +-----------------------------------+---------+ | BlackBerry Email Client | 8.5.3 | +-----------------------------------+---------+ | BlackBerry Sync Client | 9.0.1 | +-----------------------------------+---------+ | Windows Mobile Sync Client | 9.0.1 | +-----------------------------------+---------+ | iPhone Sync Client (**) | 9.0.1 | +-----------------------------------+---------+ | Outlook Sync Client | 9.0.1 | +-----------------------------------+---------+ | Symbian Sync Client | 9.0.1 | +-----------------------------------+---------+ | Mac OS Sync Client | 8.7.3 | +-----------------------------------+---------+ | Android Sync Client (***) | 9.0.1 | +-----------------------------------+---------+ | Clients SDK | 9.0.0 | +-----------------------------------+---------+ | Phone Pack | 9.0.0 | +-----------------------------------+---------+ | JSON Connector | 8.7.0 | +-----------------------------------+---------+ | Open-Xchange Connector (****) | 7.0.3 | +-----------------------------------+---------+ | Exchange Connector (****) | 7.0.1 | +-----------------------------------+---------+ (*) Funambol Carrier Edition includes all of the following components: AJAX Portal, Server API, DS Service, Inbox Listener Service, PIM Listener Service, Push Connection Service (CTP Server), Email Connector, Foundation Connector, Smart Sender, Logging Module, OTASettings Module, Product Activation Module, Carrier Edition Database, Management Tools. (**) This component is not included in the package but can be downloaded from the Apple AppStore (***) This component is not included in the package but can be downloaded from the Android Market (****) This component is not included in the package but but is available for download from https://www.forge.funambol.org/download/ New features: ------------- Funambol Version 9.0 delivers important new capabilities to extend Funambol's lead in the mobile cloud sync space: - Server: * HTTP-based Send Log (from clients to server) - iPhone Sync Client: * Login/Logout (in place of account setting) * Sync All/Cancel Sync * Reset (in place of cleanup) * HTTP-based Send Log feature * Logging improvements (log rotation, context info) * Resize of contacts' pictures for Contacts sync * Removal of one-way sync for Contacts sync * Support for iOS4 - Android Sync Client: * Address books import (from other accounts into Funambol address book) * Capability to set Funambol as default address book * Login/Logout (in place of account setting) * Capability to switch from Multi-source to Single-source UI based on source support server side * Removal of one-way sync for contacts sync * Support for Android 2.2 - BlackBerry Sync Client: * Login/Logout (in place of account screen) * Capability to switch from Multi-source to Single-source UI based on source support server side * Removal of one-way sync for contacts, calendar, tasks, notes sync * Support for BBOS 6 * Discontinued support for BBOS 4.3 - Symbian Sync Client: * Flexibility in handling of sync sources in UI: capability to add/remove sources and to change the order (build time) * Autoscroll to include the syncing source * Removal of one-way sync for contacts, calendar&tasks, notes sync * Support for Symbian^3 - Windows Mobile Sync Client: * Removal of one-way sync for contacts, calendar, tasks, notes, briefcase sync - Outlook Sync Client: * Capability to handle vCards without all fields filled * Removal of one-way sync for contacts, calendar, tasks, notes sync Additional improvements have been applied to the all components of the product in the form of bug fixes or in the form of low level re-engineering, resulting in optimized product performance and robustness. -------------------------- (3) Supported environments -------------------------- This section describes the environments that are supported by Funambol Carrier Edition Version 8.7. Server ------ Operating systems: - GNU/Linux 32/64 bit distributions Databases: - PostgreSQL 8.3 - PostgreSQL 8.4 - MySQL 5.0 - MySQL 5.1 - Oracle 10g (Phone Pack only) JDK: - 1.6 Clients ------- Outlook versions: - XP - 2003 - 2007 - 2010 (32bit) running on: - Windows XP - Windows Vista - Windows 7 Mac OS versions: - Mac OS X 10.5 (Leopard) - Mac OS X 10.6 (Snow Leopard) Windows Mobile versions: - 5.0 - 6 - 6.1 - 6.5 Symbian versions: - S60 3rd Ed. - S60 3rd Ed. FP1 - S60 3rd Ed. FP2 - S60 5th Ed. - ^3 ** NEW BlackBerry versions: - BBOS 4.5 - BBOS 4.6 - BBOS 4.7 - BBOS 5.0 (Sync Client only; not supported for the Email Client) - BBOS 6.0 ** NEW (Sync Client only; not supported for the Email Client) iPhone versions: - 3.x - 4.x ** NEW Android versions: - 2.0 - 2.1 - 2.2 ** NEW JavaME Email Client supported platforms: - Symbian S60 3rd Ed. - Symbian S60 3rd Ed. FP1 - Symbian S60 3rd Ed. FP2 - Sony Ericsson JP7 and above (no touchscreen) - Motorola P2K High-End devices (no touchscreen) - Samsung High-End devices (no touchscreen) - LG High-End devices (no touchscreen) ------------- (4) Bug fixes ------------- This section lists the bug fixes that are included in Funambol Carrier Edition Version 9.0 compared with earlier versions, grouped by component. Funambol Server bug fixes ------------------------- 7596 - Email SMS push is not working for Symbian devices 9520 - getExceptionCode() returns 'null' 9732 - OTA password logged in clear 10132 - Inbox Listener cluster does not work properly 10133 - PIM Listener cluster does not work properly 10216 - Unable to download attachment with name containing non ascii characters 10232 - Changing the phone model in the portal UI does not reset the Email Client sms push 10236 - Changing the phone number in the portal UI, but actually not changing the phone, disables the Email Client sms push 10238 - Error converting vcard to contact BlackBerry Sync Client bug fixes ---------------------------- 7245 - Work 2 and Home 2 phone numbers on bb contact records left empty 7390 - Cannot change sources URI 8857 - Exceptions in allday recurring events are not correctly propagated to BB client 9563 - Daily-allday-recurrent events exception deletes are, on device, applied to the day before 9742 - APN guess does not work on some Arabic countries 9966 - Wrong newline encoding 9968 - Problem with Calendar recurrance rule when set on last day of the month 10110 - C2S push is triggered also for disabled sources 10118 - For tasks and notes C2S push not works 10181 - Mistake in reminder for calendar events from server to client 10243 - BB uses two different sync sessions for MD5 authentication Windows Mobile Sync Client bug fixes ---------------------------- 8864 - Slow sync duplicates contacts which have only email address iPhone Sync Client bug fixes ---------------------------- 5876 - Wrong autocompletion of the Server Field 9686 - Deletes received from server are not shown in status bar during sync 9694 - After editing the server field in Account screen, pressing Done nothing happens 9765 - User agent is the old version 9969 - iPhone Sync Client is closed unexpectedly if server URL (in the account screen settings) contains special chars (not in UTF-8 charset) 10100 - Status code 213 is logged as "failed" 10201 - iPhone Sync Client randomly crashs due to the refresh of the UI Outlook Sync Client bug fixes ----------------------------- 10260 - Yearly recurring events not added in Outlook 2003 and 2007 (Error inserting recurrence property 'Interval') Symbian Sync Client bug fixes ----------------------------- 6455 - Contacts and Notes show "Not synchronized" even though they have been synched... 8425 - Messy timestamp when upgrading client 9295 - Auto-update msg says \'plug-in\' 9558 - "Cancel Sync" is not responsive enough... 9559 - "Cancel sync" results in "Last sync failed" message... 9567 - Sync status is not reset after cleanup 9763 - Autostart not working if client installed on memory card 10010 - The application can't be closed from the Task List Android Sync Client bug fixes ----------------------------- 8969 - The Home screen is not correctly refreshed after cancelling the first sync warning 9175 - In Funambol contacts missing birthday and anniversary fields 9710 - Aggregated contacts cannot be edited ** 9719 - OS Android 2.2: creation of a new contact is confused ** 9722 - Sometimes is impossible to access options if automatic sync is on ** 9754 - Address book label customization ** 9924 - Ignoring remote database name 9927 - Image not being imported 9947 - Install and not configure Funambol Client, cause in new contact to ask for configure funambol client 9952 - If device is turned off, information about sync direction is lost 10061 - 'Go to Contacts' command does not work on Samsung Galaxy 10171 - Need to lock main UI screen to avoid messages inconsistency during sync 10184 - A sync triggered by the OS blocks client usage on Galaxy S 10195 - Bandwidth saver setting not saved 10229 - Android sync client not working over https 10248 - Pictures Sync does not work on Samsung Galaxy 10286 - URL mapping is incorrect 10424 - Client crashes on Galaxy S Mesmerize when editing contacts ---------------- (5) Known issues ---------------- This section describes the remaining known issues that are still present in Funambol Carrier Edition Version 8.5. These are of lower importance, or have been partially fixed eliminating the most serious aspects of the issue. As for bug fixes, known issues are grouped by Funambol component. An arrow symbol (-->) indicates the suggested workaround, if available. Funambol Server known issues ---------------------------- * 2732 - Envelope is not updated with 'forward' arrow on mail server. At the moment, the email connector is able to set the forwarded flag for messages from server to client. This does not work for all the email servers (as forward flag information is not handled by mail servers the same way, or could not be handled at all). Furthermore: forwarded flag for messages from device to server is not managed. --> No workaround available * 4194 - vCardParser does not handle lower case property names. The parser has been modified to be case-insensitive, except for the PHOTO tag. This means that, if the card includes a photograph of the contact, and the tag is for some reason in lowercase, the photograph will not be synced correctly (while the rest of the card fields will). --> No workaround available * 4215 - Wrong sync type required by the server. If the client asks for a one way sync from server and the anchors are inconsistent with this type of sync, the server replies forcing a full (slow) sync instead of a refresh from server. The same happens with one way from client. The server forces a full sync instead of a refresh from client. --> No workaround available * 5471 - Email connector: some deletes are getting dropped by the client during intermittent connectivity. During periods of bad connectivity some messages deleted on the server are not deleted on the device. This happens when the connectivity is bad enough for the retention period of the messages in the email connector cache to expire without a successful sync. --> Request a reset inbox / cleanup from the client. iPhone Sync Client known issues ------------------------------- * 5898 - 'Group/Forlder' information is lost --> No workaround available Android Sync Client known issues -------------------------------- * When the app is installed the very first time, Contacts that don't belong to the Funambol account must be manually imported in order to be synchronized. * Only one funambol account can be managed on the device by the client. Changing account produce a deletion of all contacts and a replacement of them with the ones coming from the new account. * Uninstalling the application produces the Funambol account to be deleted from the device and all contacts belonging to it are lost. If the service used to sync is a demo service it is suggested to export the Funambol contacts to another account before uninstalling the app in order all contacts not to be lost. * Due to device's restrictions the pictures folder to sync is not selectable but it is the one created as default on the device's SD card (it is the same shown in the native "Gallery" application). * 8953 - If the port specified in the server URL is wrong, check credentials goes into a loop --> Check the port * 9100 - Work phone fields are not the same from device to portal and from portal to device --> No workaround available * 10272 - Some pictures are not synced to the server (specially those taken just after the client installation) --> This is an issue of some phones, which uses a wrong timestamp for pictures. A workaround might be to wait a while after installation (one hour should be enough) before taking pictures. Another workaround is to mark the 'Sync older pictures' checkbox, so all pictures in the device will be transferred, not only those taken after client installation. * 10440 - On some phones only (e.g. HTC Incredible) the client crashes while taking few pictures in a row. --> This seems to happen only when the option "push client changes to the server" is enabled. Workarounds could be either to disable that option and transfer the pictures either with a manual sync or a scheduled sync; or as an alternative do not take pictures in a row: exit the camera app after each shot. BlackBerry Sync Client known issues ----------------------------------- * Mobile2 and home fax on bbos5.0. The root of the issue has to do with how the BlackBerry handles the vcard fields. They both behave in the same way: - If the user defines only Home Fax on device, Home Fax is stored as Fax on the portal. - If the user defines both Home Fax and Work Fax on device, only Work Fax is stored on portal as Fax. - When we receive any update from server on device, in the contact the Mobile Field 2 and the Home Fax field are lost. Only MOBILE and WORK FAX fields will be updated. --> Use other fields as much as possible. * During sign-up from mobile, some BlackBerry phones when connected via WiFi and without a SIM are not properly detected. --> Select manually the proper phone model. * 8111 - Work Phone 2 and Home Phone 2 are not synced between the device and server in both directions --> Use other fields as much as possible * 8341 - Issues syncing pictures with some special characters --> Do not use special characters * 9134 - Task categories are not correctly synced from server to device --> No workaround available * 10079 - [BBOS 6.0] On phones like BlackBerry Torch, the client is not able to send deleted contact items to the server --> Delete items from the portal interface or through other clients. Symbian Sync Client known issues -------------------------------- * C2S push for notes is not available --> Operating system issue * The "Cleanup" command for notes is not available --> Operating system issue * The "Go To" command for notes is not available --> Operating system issue * 7246 - Nokia N85 and N97 with old firmware versions could have issues in receiving calendar items. --> An update of the firmware is strongly recommended to fix the issue. Windows Mobile Sync Client known issues --------------------------------------- * On WM, sometimes sync calendar without change on device or on server. The issue is present only when the setting mode is Push Service: after a push from the server, the client sometimes starts another sync a short time after even if no changes were made. --> No workaround available * 8965 - Sync email does not work on SAMSUNG GT-I8000 (Omnia II) running Windows Mobile version 6.5. The email headers are downloaded but the email body is empty for every email. --> No workaround available. This device is shipped with a heavily customized version of PocketOutLook client by Samsung which creates compatibility issues. Java ME/BlackBerry Email Client known issues --------------------------------- * On Nokia 7610 (and possibly other similar devices) the Drafts folder does not work properly --> Device issue * On Nokia 7610 (and possibly other similar devices) it is not possible to change the account setting --> Re-download the client from the portal, once logged in with the new account. * Touchscreen is not fully supported --> Use keypad where available * No sound can be played in untrusted mode by Sprint branded devices --> Play Sound option has been removed * Motorola devices do not support (device limitation for jsr75 support) --> No workaround available * Memory limitations for some low-tier devices --> The following limitations are applied to low-tier devices: - The maximum number of contacts is fixed to 100 - The maximum number of message is fixed to 30 - There is no log functionality and related options/screens - There are no help screens - Data is transmitted in uncompressed mode only (gzip compression has been removed) - MaxMsgSize is reduced to 8K - There is no 'Send Photo' functionality * 3772 - On Motorola RAZR V8, sometimes the cancel key appears in place of the get mail key. If you start a synchronization and press the "Option" key before it is terminated, when the sync terminates the Options drop down menu is closed and the "cancel" key is still there in place of the "Get mail" key. If you press the "Cancel" key another sync will start. --> No workaround available * 4561 - Navigating emails with the trackball (moving left/right to fetch previous/next) may results in skipping emails (like jumping from the first to the fourth). This may result in a lowered user experience. --> No workaround available * 4943 - Email body for messages forwarded or replied to from device is truncated on the recipient's end, as is shown on the device. Since the Funambol Email Client only downloads up to 2 kBytes of the body of messages, and the Funambol server does not retain the message, forwarding or replying to the message results in the original message being truncated to the size downloaded to the client. --> No workaround available * 5046 - Scheduled sync with wrong timing on some Nokia Symbian devices. This issue has been confirmed on the Nokia E65 and 6120. If the user exits the mail client, but with a sync scheduled every hour, the first sync actually starts after 15 minutes. --> No workaround available * 5162 - Open tunnel - max timeout error. Sometimes the error above occurs on BlackBerry devices, and in this case the Funambol applications (both Sync and Email client) cannot connect. --> This seems to be an issue with the BlackBerry software platform. See: http://www.blackberryforums.com/developerforum/ 107174-max-connection-open-tunnel.html * 5215 - Date/time display on Inbox emails are not updated during time switch to/from daylight saving time if you have the device on and client open. --> If the user restarts the application, the correct date/time is picked up. * 5245 - Browse Links option is not finding all links. Seems to be related to a link preceded by and followed by special chars, such as parentheses and brackets. The Java ME Email Client has a feature that parses the text of a message to extract links (URLs) embedded in the message. This allows the user to more easily launch the device browser and follow the links. One issue with this feature is that if the links are surrounded by special characters such as parenthesis or brackets, the parser does not recognize the string as a link. --> No workaround available * 5365 - No scheduled sync after recharge of the device. A Funambol Email Client for BlackBerry that is configured to sync at regular intervals will stop syncing after the connection is not established in conditions of extremely low battery levels. In this case the firmware refuses the request to establish the connection to save power. Once this happens, the Funambol client will not start syncing again even if the battery is recharged. --> To restart regular sync, reboot the device (taking out the battery). * 6149 - A media access exception is sometimes thrown when the Email Client is installed (BlackBerry OS version 4.3.x). This is due to the particular version of the Blackberry OS disallowing by default access to media for applications. --> After installing the client, the user needs to go to Advanced Options > Application, select Funambol, press Edit Permissions and allow media access for the Funambol client if it is not enabled. * 6323 - Wrong behavior after stopping a sync. This happens if a sync is stopped because of a network problem or similar occurrences. After this, deleting and reading some emails on the client, then starting a new sync (which is a fast sync) yields inconsistent results: messages that have been deleted re-appear, read flags are not correct. --> A reset of the inbox fixes the problem * 6510 - On LG KE970, the client cannot open attachments. --> No workaround available. * 7293 - On BlackBerry devices with OS 4.3 or earlier, the automatic credentials from Portal do not work --> Credentials need to be manually entered * 7905 - Changing display name on the client does not take effect. Changing the display name in Settings > Account Settings in the client does not take effect, unless the user also enters an email address. Both fields are used to specify the From: field of the outgoing emails (that by default is the one stored in the server). So, only changing the display name does nothing. --> Enter both display name and email address in the account settings. Outlook Sync Client known issues -------------------------------- * Errors accessing Outlook may happen on some machines, due to the Windows Update package KB939683 for WinMedia11 (2007-09-04). So far not reproduced by dev (reported by community). --> Uninstall Windows Update KB939683 and reboot * Some recurring events cannot be added to Outlook: for example monthly recurrence every 3 months with an occurrence falling on 30th of February --> No workaround available * OutlookXP(2002): Outlook profiles window is unnecessarily displayed --> Dismiss the profiles windows and proceed. * "ReminderSoundFile" property of event is not transferred correctly if the field is never initialized. --> Open the event, open the 'Reminder Sound' window, click on 'Play this sound' option 2 times (so it will be unchecked and then checked again), click OK and save the event. * 4016 - Outlook 2003 connector fills DB field 'File as' with wrong data. If you do the following: - open Outlook, go to "Tools > Options > Contact Options" - select as default "FileAs": "Last, First (Company)", click OK - create a contact with FrstName, LastName and Company fields not empty - save the contact In Outlook UI the FileAs is shown like "Last, First, Company" and it's inconsistent with the FileAs shown if you open the contact. When the client asks for the FileAs field during synchronization, Outlook returns "Last, First\nCompany" (\n is the line break) and it's wrong. --> Outlook issue * 4198 - Outlook scheduled sync issue in Windows Vista: 'cannot schedule' error. Using Scheduled Sync, after the first sync, in Tools -> Options the 'Synchronize every' Scheduler option is unchecked. After checking the option again and trying to save it to 5 minutes, pressing OK the following message is displayed: 'Cannot schedule'. --> Uninstall the Outlook Sync Client and reinstall the latest version. * 6276 - Outlook client message: COM pointer error. This is a problem that occasionally may happen in the Funambol Outlook Sync Client. COM pointer errors originate in the Windows COM module, used by the Funambol Client to access Microsoft Outlook APIs and data. --> There could be different reasons for the error, as the COM module may be used by other applications at the same time. 1. Activate the Outlook window: if a wizard window to configure your profile is shown, this is the cause of the problem. Solution: follow the wizard until the end, when your profile is configured try to sync again. 2. Check if Outlook is working correctly and not stuck. If it does not respond, close Outlook and check if the process "OUTLOOK.EXE" is still running from the Windows Task Manager (if yes, you can terminate the process from there). 3. If you have an antivirus software installed, disable it and try again: some antivirus software recognize the attempt of the Funambol Sync Client to access the Outlook application as a malicious action, so they block it. 4. If you have some other Outlook add-ins installed, disable or remove them and try again. An add-in can access Outlook in a (wrong) way that could block other applications to do the same. 5. "Google Desktop Search" and "Nokia PC Suite" may conflict with Funambol Outlook Sync Client. This doesn't happen for all the users, but you may need to uninstall them and try again. Note: any software accessing Outlook data can potential create a conflict, these 2 applications are known to do so in some cases. 6. Finally, try to reinstall Microsoft Outlook. Sometimes Outlook becomes unstable and does not work perfectly. If ALL of the above points does not help, please send an email to Funambol detailing: - the exact version of Funambol Outlook Client used - the exact version of both Microsoft Windows and Microsoft Outlook used - a list (if possible) of any software installed on your machine - the full log of Funambol Outlook Client (set the log level to debug) - any other information about your system, that you consider relevant * 9756 - Client does not work on Outlook2010 64bit version --> Follow Microsoft recommendations: even if Windows is 64 bits, the recommended version of Outlook is 32 bits. Mac OS Sync Client known issues ------------------------------- * 8799 - iPhone field is not handled by Client --> Do not use that field * 8833 - Menubar does not start if the user logs in with an other account on the machine --> Shutdown the machine JSON Connector known issues ------------------------------- * 9720 - Birthday in contacts is off one day --> No workaround available. * 9723 - Timezone conversion is not performed by the JSON connector. If the phone is not able to handle timezones, the server is able to make the needed conversion for it. With JSON connector, this mechanism is not working. --> No workaround available. * 9735 - Json Connector does not handle tasks recurrency --> No workaround available. Open-Xchange Connector known issues ------------------------------- * 4029-4032-4034 - Failed update on server of Recurrent Event (daily/weekly) for a precise number of appointments. --> No workaround available. Exchange Connector known issues ------------------------------- * Push is not supported. --> No workaround available. * Sync of subfolders is not supported. --> No workaround available. * 4828 - Sync of recurring tasks is not supported. --> No workaround available. Other known issues ------------------ * Motorola V600, V505, V500, V400: contacts/events with language specific characters are sent empty by the device --> Device issue * Nokia 6020: endless loop when syncing contacts --> Device issue * Motorola PEBL, V505: deleting all fields for a contact, the server sends an empty contact but the phone doesn't delete all fields --> Device issue * Nokia 6101: phone’s First name and the Last name are within just one field (Name) so if you delete the Last name in the Name field, the Name contains just the First name and seeing the vCard we cannot distinguish whether it’s the First name or the Last name --> Device issue * Sony Ericsson K750i: - the phone randomly starts a slow sync. This can cause duplication if the twin fields are changed - the reminder is not deleted --> Device issue * Sony Ericsson P900i: OTA settings cannot configure server's address port (only port 80 can be set correctly) --> Device issue * Nokia 6600, 6630, 6670, 6680: modifications made on server's side for 'memo/anniversary' events (originally created on device) are not updated on the device --> Device issue * Motorola V3xx RAZR: picture is not updated for contacts coming from Outlook -> To modify a contact's picture from Outlook, create a new contact on Outlook with the new picture and delete the old one, then sync with the Outlook Sync Client and then with the device. * Exchange Connector: Sony Ericsson K750 is not supported --> No workaround available * 2732 - Exchange Connector: Envelope is not updated with 'forward' arrow on the mail server. At the moment, the email connector is able to set the forwarded flag for messages from server to client. This does not work for all the email servers (as forward flag information is not handled by mail servers the same way, or could not be handled at all). Furthermore: forwarded flag for messages from device to server is not managed. --> No workaround available * 4029 - Open-Xchange Connector: Failed update on server of Recurrent Event (daily) for a precise number of appointments. --> No workaround available * 4032 - Open-Xchange Connector: Failed update on server of Recurrent Task (weekly) for a precise number of appointments. --> No workaround available * 4034 - Open-Xchange Connector: Failed update on server of Recurrent Task (daily) for a precise number of appointments. --> No workaround available * 4725 - On the device some fields of Tasks are not updated. Syncing tasks between Outlook and several types of devices results in some fields being left behind (not always the same). This is in part because the fields are not supported by the target device, and in part because of an issue supporting the Status field of a task in the Outlook Sync Client. Devices also may not show the task category, and reminder. --> No workaround available * 6977 - Hotmail mail server shows a behavior that is pretty different from other mail servers since it does allow login to each account only every 15 minutes (or 5 minutes for premium accounts). As a consequence of this the InboxListener cannot access the mail server and the user cannot sync emails until the session has expired. --> No workaround available Copyright (c) 2011 Funambol