Fri, 10 Apr 2026 17:02:31 +0000 https://bugs.horde.org/ticket/10022 Nokia N900 ActiveSync for calendar doesn't work If I configure a Nokia N900 [0] for calendar syncing the phone tries to sync and stops after a few seconds with status "Stopped". Address syncing works well on the phone (See resloved Bug #9757). Attached is a network dump and the Horde activesync.log of a tried calendar sync. Pleas tell me, if I can provide you more information to solve the problem. One thing I could do additionally, is to enable logging on the N900. horde.log 2011-05-01T16:34:25+02:00 NOTICE: HORDE [imp] Login success for test.user@example.net (Horde user test.user@example.net) [194.230.155.22] to {localhost:143 [imap]} [pid 17555 on line 202 of "/var/www/horde4/imp/lib/Auth.php"] 2011-05-01T16:34:27+02:00 NOTICE: HORDE [imp] Login success for test.user@example.net (Horde user test.user@example.net) [194.230.155.22] to {localhost:143 [imap]} [pid 17555 on line 202 of "/var/www/horde4/imp/lib/Auth.php"] 2011-05-01T16:34:28+02:00 NOTICE: HORDE [imp] Login success for test.user@example.net (Horde user test.user@example.net) [194.230.155.22] to {localhost:143 [imap]} [pid 17555 on line 202 of "/var/www/horde4/imp/lib/Auth.php"] 2011-05-01T16:34:28+02:00 NOTICE: HORDE [turba] PHP ERROR: Undefined offset: 1 [pid 17555 on line 302 of "/var/www/horde4/pear/php/Net/DNS2.php"] access.log 194.230.155.22 - test.user@example.net [01/May/2011:16:34:25 +0200] "POST /Microsoft-Server-ActiveSync?Cmd=FolderSync&DeviceId=356938031943765&DeviceType=SmartPhone HTTP/1.1" 200 166 "-" "N900/1.1" 194.230.155.22 - test.user@example.net [01/May/2011:16:34:27 +0200] "POST /Microsoft-Server-ActiveSync?Cmd=Sync&DeviceId=356938031943765&DeviceType=SmartPhone HTTP/1.1" 200 82 "-" "N900/1.1" [0] http://wiki.maemo.org/Mail_For_Exchange_%28MfE%29_Heartbeat_and_FAQ Sun, 01 May 2011 15:26:29 +0000 https://bugs.horde.org/ticket/10022#t64323 This looks like another symptom of Bug: 9733 Tue, 03 May 2011 22:04:26 +0000 https://bugs.horde.org/ticket/10022#t64425 I can confirm that it now works with patch [0] applied from Bug: 9733 [0] http://git.horde.org/horde-git/-/commit/a65072badbcb509690ca009bb0770ca1c641e393 Mon, 16 May 2011 14:59:36 +0000 https://bugs.horde.org/ticket/10022#t64683