From bugs at horde.org Mon Mar 12 07:39:40 2012 From: bugs at horde.org (bugs at horde.org) Date: Mon, 12 Mar 2012 08:39:40 +0100 Subject: [Tickets #11068] Re: Recursive event on android or ios 5 In-Reply-To: References: Message-ID: <20120312083948.Horde.GdAxPc_2HjZPXahEHE9SgpA@bugs.horde.org> DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED. Ticket URL: http://bugs.horde.org/ticket/11068 ------------------------------------------------------------------------------ Ticket | 11068 Updated By | Jan Schneider Summary | Recursive event on android or ios 5 Queue | Horde Groupware Version | 4.0.6 Type | Bug -State | Unconfirmed +State | Assigned Priority | 2. Medium Milestone | Patch | -Owners | +Owners | Michael Rubinsky ------------------------------------------------------------------------------ From bugs at horde.org Mon Mar 12 09:31:49 2012 From: bugs at horde.org (bugs at horde.org) Date: Mon, 12 Mar 2012 09:31:49 +0000 Subject: [Tickets #11069] wrong utf-8 encondigs at html viewer Message-ID: DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED. Ticket URL: http://bugs.horde.org/ticket/11069 ------------------------------------------------------------------------------ Ticket | 11069 Created By | ak at lps.komi.ru Summary | wrong utf-8 encondigs at html viewer Queue | Horde Framework Packages Version | Git master Type | Bug State | Unconfirmed Priority | 3. High Milestone | Patch | Owners | ------------------------------------------------------------------------------ ak at lps.komi.ru (2012-03-12 09:31) wrote: When we are using "View HTML data in new window" function the framework creates DOMDocument to make cleaning and de-XSS. There is a problem here with utf-8 (discussed php.net/manual/en/domdocument.loadhtml.php) I found the bug and fixed in my distribution (PEAR/Horde/Domhtml.php line 68): Use $doc->loadHTML('' . Horde_String::convertCharset($text, $charset, 'UTF-8')); instead of $doc->loadHTML($this->_xmlencoding . Horde_String::convertCharset($text, $charset, 'UTF-8')); From bugs at horde.org Mon Mar 12 10:20:48 2012 From: bugs at horde.org (bugs at horde.org) Date: Mon, 12 Mar 2012 10:20:48 +0000 Subject: [Tickets #11070] event display on 25.03.2012 is off by one hour Message-ID: DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED. Ticket URL: http://bugs.horde.org/ticket/11070 ------------------------------------------------------------------------------ Ticket | 11070 Created By | thpo+horde at dotrc.de Summary | event display on 25.03.2012 is off by one hour Queue | Kronolith Version | 3.0.15 Type | Bug State | Unconfirmed Priority | 1. Low Milestone | Patch | Owners | ------------------------------------------------------------------------------ thpo+horde at dotrc.de (2012-03-12 10:20) wrote: All events on that day are displayed one hour earlier. Yunosh pointed out (in IRC), that this is the day if DST switch. From bugs at horde.org Mon Mar 12 10:33:17 2012 From: bugs at horde.org (bugs at horde.org) Date: Mon, 12 Mar 2012 10:33:17 +0000 Subject: [Tickets #11070] Re: event display on 25.03.2012 is off by one hour In-Reply-To: References: Message-ID: <20120312103320.Horde.nYXSDM_2HjZPXdDwyXmC-vA@bugs.horde.org> DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED. Ticket URL: http://bugs.horde.org/ticket/11070 ------------------------------------------------------------------------------ Ticket | 11070 Updated By | c.denis at mrduck.fr Summary | event display on 25.03.2012 is off by one hour Queue | Kronolith Version | 3.0.15 Type | Bug State | Unconfirmed Priority | 1. Low Milestone | Patch | Owners | ------------------------------------------------------------------------------ c.denis at mrduck.fr (2012-03-12 10:33) wrote: Events between 00:00 and 1:59 are displayed correctly. From 2:00 until 24:00 the event is displayed one hour too early in week view in kronolith. Events that cross this time are saved correctly though: an event form 1:30 to 2:30 is saved as 1:30 to 3:30, but displayed as 1:30 to 2:00. From bugs at horde.org Mon Mar 12 11:36:37 2012 From: bugs at horde.org (bugs at horde.org) Date: Mon, 12 Mar 2012 11:36:37 +0000 Subject: [Tickets #11068] Re: Recursive event on android or ios 5 In-Reply-To: References: Message-ID: <20120312113640.Horde.ukyLD8_2HjZPXd-IcoGQRbA@bugs.horde.org> DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED. Ticket URL: http://bugs.horde.org/ticket/11068 ------------------------------------------------------------------------------ Ticket | 11068 Updated By | melian.the.queen at gmail.com Summary | Recursive event on android or ios 5 Queue | Horde Groupware Version | 4.0.6 Type | Bug State | Assigned Priority | 2. Medium Milestone | Patch | Owners | Michael Rubinsky ------------------------------------------------------------------------------ melian.the.queen at gmail.com (2012-03-12 11:36) wrote: I can help you: Recurrent with reminder on android don't sync, on ios 5 sync recurrent work but is set 2 events ... event on j date and 1 event on the day of reminder ... From bugs at horde.org Mon Mar 12 12:31:09 2012 From: bugs at horde.org (bugs at horde.org) Date: Mon, 12 Mar 2012 12:31:09 +0000 Subject: [Tickets #11071] Splitting long content into multiple messages Message-ID: DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED. Ticket URL: http://bugs.horde.org/ticket/11071 ------------------------------------------------------------------------------ Ticket | 11071 Created By | thomas at trethan.net Summary | Splitting long content into multiple messages Queue | Synchronization Version | Git master Type | Enhancement State | New Priority | 1. Low Milestone | Patch | Owners | ------------------------------------------------------------------------------ thomas at trethan.net (2012-03-12 12:31) wrote: Are there any plans for implementing splitting of long data into multiple messages? Newer smartphones are able to use larger images for contact photos. Unfortunately Horde skips entries, when data exceeds MaxMsgSize, so most contacts won't get synced. From bugs at horde.org Mon Mar 12 12:56:48 2012 From: bugs at horde.org (bugs at horde.org) Date: Mon, 12 Mar 2012 13:56:48 +0100 Subject: [Tickets #11072] Set system configuration in Horde_Role Message-ID: DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED. Ticket URL: http://bugs.horde.org/ticket/11072 ------------------------------------------------------------------------------ Ticket | 11072 Created By | Jan Schneider Summary | Set system configuration in Horde_Role Queue | Horde Base Version | Git master Type | Enhancement State | Assigned Priority | 2. Medium Milestone | 5 Patch | Owners | Jan Schneider, Horde Developers ------------------------------------------------------------------------------ Jan Schneider (2012-03-12 13:56) wrote: Test setting the system configuration instead of the user configuration when setting the horde_dir variable in Horde_Role. From bugs at horde.org Mon Mar 12 13:40:48 2012 From: bugs at horde.org (bugs at horde.org) Date: Mon, 12 Mar 2012 13:40:48 +0000 Subject: [Tickets #11068] Re: Recursive event on android or ios 5 In-Reply-To: References: Message-ID: <20120312134052.Horde.4lEZbc_2HjZPXfzkIBfSKUA@bugs.horde.org> DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED. Ticket URL: http://bugs.horde.org/ticket/11068 ------------------------------------------------------------------------------ Ticket | 11068 Updated By | Michael Rubinsky Summary | Recursive event on android or ios 5 Queue | Horde Groupware Version | 4.0.6 Type | Bug -State | Assigned +State | Feedback Priority | 2. Medium Milestone | Patch | Owners | Michael Rubinsky ------------------------------------------------------------------------------ Michael Rubinsky (2012-03-12 13:40) wrote: I cannot reproduce this. Tested on iPad, iPhone, iPod Touch (all latest iOS 5) as well as Galaxy Nexus (4.0.2) as well as the Android Emulator on 4.0.2 and 4.0.3. Recurring events are successfully sync'd in both directions. Tested on both latest stable code (git master), latest development code (git develop) as well as a private local branch with other major changes. To further debug this issue, I will need at least a dedicated sync log captured while the issue is occurring. Additionally, a network capture can also be beneficial. See http://wiki.horde.org/ActiveSync for further information. From bugs at horde.org Mon Mar 12 14:02:20 2012 From: bugs at horde.org (bugs at horde.org) Date: Mon, 12 Mar 2012 14:02:20 +0000 Subject: [Tickets #11071] Re: Splitting long content into multiple messages In-Reply-To: References: Message-ID: <20120312140223.Horde.LHMnaM_2HjZPXgHvDW1SGpA@bugs.horde.org> DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED. Ticket URL: http://bugs.horde.org/ticket/11071 ------------------------------------------------------------------------------ Ticket | 11071 Updated By | thomas at trethan.net Summary | Splitting long content into multiple messages Queue | Synchronization Version | Git master Type | Enhancement State | New Priority | 1. Low Milestone | Patch | Owners | +New Attachment | SyncSplit.patch ------------------------------------------------------------------------------ thomas at trethan.net (2012-03-12 14:02) wrote: I managed to successfully implement partial sending of large objects via SyncML by extending the Horde sync functionalities. It was not necessary to refactor the whole code, I just adapted and added a view things and it works fine (see attached SyncSplit.patch). Tested it with Horde 4.0.14 and a Samsung Galaxy S II running the Synthesis Std client for Android. Surely more tests on other devices will be necessary, unfortunately I don't have that much possibilites... thomas at trethan.net (2012-03-12 14:02) uploaded: SyncSplit.patch http://bugs.horde.org/h/services/download/?module=whups&actionID=download_file&file=SyncSplit.patch&ticket=11071&fn=%2FSyncSplit.patch From bugs at horde.org Mon Mar 12 14:24:23 2012 From: bugs at horde.org (bugs at horde.org) Date: Mon, 12 Mar 2012 14:24:23 +0000 Subject: [Tickets #11025] Re: Horde_Auth out of date In-Reply-To: References: Message-ID: <20120312142426.Horde.gp6AXs_2HjZPXgcalb3SQ8A@bugs.horde.org> DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED. Ticket URL: http://bugs.horde.org/ticket/11025 ------------------------------------------------------------------------------ Ticket | 11025 Updated By | Michael Rubinsky Summary | Horde_Auth out of date Queue | Horde Base Version | 4.0.13 Type | Bug -State | Assigned +State | Not A Bug Priority | 1. Low Milestone | Patch | Owners | Ralf Lang (B1 Systems GmbH) ------------------------------------------------------------------------------ From bugs at horde.org Mon Mar 12 15:49:09 2012 From: bugs at horde.org (bugs at horde.org) Date: Mon, 12 Mar 2012 15:49:09 +0000 Subject: [Tickets #11049] Re: horde git repositories are not accessible through http://git.horde.org In-Reply-To: References: Message-ID: <20120312154916.Horde.YAARMs_2HjZPXhr8DEaDO1A@bugs.horde.org> DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED. Ticket URL: http://bugs.horde.org/ticket/11049 ------------------------------------------------------------------------------ Ticket | 11049 Updated By | vilius at lnk.lt Summary | horde git repositories are not accessible through | http://git.horde.org Queue | Horde.org Servers Version | Git Type | Bug State | Assigned Priority | 2. Medium Milestone | Patch | Owners | Horde Developers ------------------------------------------------------------------------------ vilius at lnk.lt (2012-03-12 15:49) wrote: As of couple of days ago Chora is completely unavailable. A fatal error has occurred chora is not activated. Details have been logged for the administrator. From bugs at horde.org Mon Mar 12 17:38:45 2012 From: bugs at horde.org (bugs at horde.org) Date: Mon, 12 Mar 2012 17:38:45 +0000 Subject: [Tickets #10991] Re: Allday events are not correctly synchronized In-Reply-To: References: Message-ID: <20120312173847.Horde.r9lxX8_2HjZPXjSnfKQ3rIA@dev.horde.org> DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED. Ticket URL: http://bugs.horde.org/ticket/10991 ------------------------------------------------------------------------------ Ticket | 10991 Updated By | Git Commit Summary | Allday events are not correctly synchronized Queue | Synchronization Version | Git master Type | Bug State | Unconfirmed Priority | 2. Medium Milestone | Patch | Owners | ------------------------------------------------------------------------------ Git Commit (2012-03-12 17:38) wrote: Changes have been made in Git (develop): commit 2b00e61bf937b5f7d94f9ecb72e51e83fa65bd6d Author: Michael J Rubinsky Date: Mon Mar 12 13:33:27 2012 -0400 Always convert to local timezone when importing from AS events. Possible fix for Bug: 10991 kronolith/lib/Event.php | 7 +++++-- 1 files changed, 5 insertions(+), 2 deletions(-) http://git.horde.org/horde-git/-/commit/2b00e61bf937b5f7d94f9ecb72e51e83fa65bd6d From bugs at horde.org Mon Mar 12 17:42:53 2012 From: bugs at horde.org (bugs at horde.org) Date: Mon, 12 Mar 2012 17:42:53 +0000 Subject: [Tickets #10991] Re: Allday events are not correctly synchronized In-Reply-To: References: Message-ID: <20120312174254.Horde.dSfnDc_2HjZPXjWepgP3rGA@dev.horde.org> DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED. Ticket URL: http://bugs.horde.org/ticket/10991 ------------------------------------------------------------------------------ Ticket | 10991 Updated By | Git Commit Summary | Allday events are not correctly synchronized Queue | Synchronization Version | Git master Type | Bug State | Unconfirmed Priority | 2. Medium Milestone | Patch | Owners | ------------------------------------------------------------------------------ Git Commit (2012-03-12 17:42) wrote: Changes have been made in Git (master): commit c5c4d75a0c0de4fd231b1bdff8a0812a87fbf427 Author: Michael J Rubinsky Date: Mon Mar 12 13:33:27 2012 -0400 Always convert to local timezone when importing from AS events. Possible fix for Bug: 10991 kronolith/lib/Event.php | 7 +++++-- 1 files changed, 5 insertions(+), 2 deletions(-) http://git.horde.org/horde-git/-/commit/c5c4d75a0c0de4fd231b1bdff8a0812a87fbf427 From bugs at horde.org Mon Mar 12 17:48:30 2012 From: bugs at horde.org (bugs at horde.org) Date: Mon, 12 Mar 2012 17:48:30 +0000 Subject: [Tickets #10991] Re: Allday events are not correctly synchronized In-Reply-To: References: Message-ID: <20120312174831.Horde.0qw_P8_2HjZPXjbvqr8ydKA@bugs.horde.org> DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED. Ticket URL: http://bugs.horde.org/ticket/10991 ------------------------------------------------------------------------------ Ticket | 10991 Updated By | Michael Rubinsky Summary | Allday events are not correctly synchronized Queue | Synchronization Version | Git master Type | Bug -State | Unconfirmed +State | Feedback Priority | 2. Medium Milestone | Patch | -Owners | +Owners | Michael Rubinsky ------------------------------------------------------------------------------ Michael Rubinsky (2012-03-12 17:48) wrote: Can you see if the following change fixes this for you? http://github.com/horde/horde/commit/c5c4d75a0c0de4fd231b1bdff8a0812a87fbf427 From bugs at horde.org Mon Mar 12 17:49:09 2012 From: bugs at horde.org (bugs at horde.org) Date: Mon, 12 Mar 2012 17:49:09 +0000 Subject: [Tickets #10991] Re: Allday events are not correctly synchronized In-Reply-To: References: Message-ID: <20120312174910.Horde.q-u7V8_2HjZPXjcW4Cuia-A@dev.horde.org> DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED. Ticket URL: http://bugs.horde.org/ticket/10991 ------------------------------------------------------------------------------ Ticket | 10991 Updated By | Git Commit Summary | Allday events are not correctly synchronized Queue | Synchronization Version | Git master Type | Bug State | Feedback Priority | 2. Medium Milestone | Patch | Owners | Michael Rubinsky ------------------------------------------------------------------------------ Git Commit (2012-03-12 17:49) wrote: Changes have been made in Git (develop): commit c5c4d75a0c0de4fd231b1bdff8a0812a87fbf427 Author: Michael J Rubinsky Date: Mon Mar 12 13:33:27 2012 -0400 Always convert to local timezone when importing from AS events. Possible fix for Bug: 10991 kronolith/lib/Event.php | 7 +++++-- 1 files changed, 5 insertions(+), 2 deletions(-) http://git.horde.org/horde-git/-/commit/c5c4d75a0c0de4fd231b1bdff8a0812a87fbf427 From bugs at horde.org Mon Mar 12 17:58:43 2012 From: bugs at horde.org (bugs at horde.org) Date: Mon, 12 Mar 2012 17:58:43 +0000 Subject: [Tickets #11068] Re: Recursive event on android or ios 5 In-Reply-To: References: Message-ID: <20120312175852.Horde.EohQBs_2HjZPXjlcwrVVHoA@bugs.horde.org> DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED. Ticket URL: http://bugs.horde.org/ticket/11068 ------------------------------------------------------------------------------ Ticket | 11068 Updated By | melian.the.queen at gmail.com Summary | Recursive event on android or ios 5 Queue | Horde Groupware Version | 4.0.6 Type | Bug State | Feedback Priority | 2. Medium Milestone | Patch | Owners | Michael Rubinsky ------------------------------------------------------------------------------ melian.the.queen at gmail.com (2012-03-12 17:58) wrote: in the activesync log: 2012-03-12T18:47:31+01:00 ERR: No timezone found for the given offsets 2012-03-12T18:47:29+01:00 DEBUG: I 2012-03-12T18:47:29+01:00 DEBUG: I xP///wAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAoAAAAEAAMAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA$ 2012-03-12T18:47:29+01:00 DEBUG: I all over seems to be ok > I cannot reproduce this. Tested on iPad, iPhone, iPod Touch (all > latest iOS 5) as well as Galaxy Nexus (4.0.2) as well as the Android > Emulator on 4.0.2 and 4.0.3. Recurring events are successfully > sync'd in both directions. > > Tested on both latest stable code (git master), latest development > code (git develop) as well as a private local branch with other > major changes. > > To further debug this issue, I will need at least a dedicated sync > log captured while the issue is occurring. Additionally, a network > capture can also be beneficial. > > See http://wiki.horde.org/ActiveSync for further information. > > From bugs at horde.org Mon Mar 12 18:15:57 2012 From: bugs at horde.org (bugs at horde.org) Date: Mon, 12 Mar 2012 18:15:57 +0000 Subject: [Tickets #11068] Re: Recursive event on android or ios 5 In-Reply-To: References: Message-ID: <20120312181558.Horde.n2h8Ds_2HjZPXj1eeOKlKbA@bugs.horde.org> DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED. Ticket URL: http://bugs.horde.org/ticket/11068 ------------------------------------------------------------------------------ Ticket | 11068 Updated By | Michael Rubinsky Summary | Recursive event on android or ios 5 Queue | Horde Groupware Version | 4.0.6 Type | Bug State | Feedback Priority | 2. Medium Milestone | Patch | Owners | Michael Rubinsky ------------------------------------------------------------------------------ Michael Rubinsky (2012-03-12 18:15) wrote: > in the activesync log: > > 2012-03-12T18:47:31+01:00 ERR: No timezone found for the given offsets That would definitely cause a problem. What timezone is the device set to? From bugs at horde.org Mon Mar 12 18:24:46 2012 From: bugs at horde.org (bugs at horde.org) Date: Mon, 12 Mar 2012 18:24:46 +0000 Subject: [Tickets #11068] Re: Recursive event on android or ios 5 In-Reply-To: References: Message-ID: <20120312182447.Horde.fi7ra8_2HjZPXj9vkg81IxA@bugs.horde.org> DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED. Ticket URL: http://bugs.horde.org/ticket/11068 ------------------------------------------------------------------------------ Ticket | 11068 Updated By | melian.the.queen at gmail.com Summary | Recursive event on android or ios 5 Queue | Horde Groupware Version | 4.0.6 Type | Bug State | Feedback Priority | 2. Medium Milestone | Patch | Owners | Michael Rubinsky ------------------------------------------------------------------------------ melian.the.queen at gmail.com (2012-03-12 18:24) wrote: By Network or manually set to +01 (belgium, no paris) causse the error (on android / no tested for the moment the double events for iphone) (tested in parrallel tine 2.0 and sync work perfect but i want horde :p) >> in the activesync log: >> >> 2012-03-12T18:47:31+01:00 ERR: No timezone found for the given offsets > > That would definitely cause a problem. > > What timezone is the device set to? From bugs at horde.org Mon Mar 12 19:10:15 2012 From: bugs at horde.org (bugs at horde.org) Date: Mon, 12 Mar 2012 19:10:15 +0000 Subject: [Tickets #11068] Re: Recursive event on android or ios 5 In-Reply-To: References: Message-ID: <20120312191022.Horde.nIg8P8_2HjZPXkoeJ5PFObA@bugs.horde.org> DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED. Ticket URL: http://bugs.horde.org/ticket/11068 ------------------------------------------------------------------------------ Ticket | 11068 Updated By | melian.the.queen at gmail.com Summary | Recursive event on android or ios 5 Queue | Horde Groupware Version | 4.0.6 Type | Bug State | Feedback Priority | 2. Medium Milestone | Patch | Owners | Michael Rubinsky ------------------------------------------------------------------------------ melian.the.queen at gmail.com (2012-03-12 19:10) wrote: Just changed my timezone to New York ... same bug on the iphone double events is set up ... 2012-03-12T20:07:39+01:00 INFO: Horde_ActiveSync_Driver_Horde::logon attempt for: kevinlj 2012-03-12T20:07:39+01:00 DEBUG: [androidc195282820] SYNC request received for user kevinlj 2012-03-12T20:07:39+01:00 DEBUG: [androidc195282820] loadDeviceInfo: kevinlj 2012-03-12T20:07:39+01:00 INFO: Request being handled for device: androidc195282820 Supporting protocol version: 2.5 2012-03-12T20:07:39+01:00 INFO: [androidc195282820] Handling SYNC command. 2012-03-12T20:07:39+01:00 DEBUG: [androidc195282820] Checking policykey for device Key: 0 User: kevinlj 2012-03-12T20:07:39+01:00 DEBUG: [androidc195282820] loadDeviceInfo: kevinlj 2012-03-12T20:07:39+01:00 DEBUG: Policykey: 0 verified. 2012-03-12T20:07:39+01:00 DEBUG: I 2012-03-12T20:07:39+01:00 DEBUG: I 2012-03-12T20:07:39+01:00 DEBUG: I 2012-03-12T20:07:39+01:00 DEBUG: I 2012-03-12T20:07:39+01:00 DEBUG: I Calendar 2012-03-12T20:07:39+01:00 INFO: [androidc195282820] Syncing folder class: Calendar 2012-03-12T20:07:39+01:00 DEBUG: I 2012-03-12T20:07:39+01:00 DEBUG: I 2012-03-12T20:07:39+01:00 DEBUG: I {4f5e2f2a-e0b0-4096-bb65-4135c0a80101}5 2012-03-12T20:07:39+01:00 DEBUG: I 2012-03-12T20:07:39+01:00 DEBUG: I 2012-03-12T20:07:39+01:00 DEBUG: I Calendar 2012-03-12T20:07:39+01:00 INFO: [androidc195282820] Folder server id: Calendar 2012-03-12T20:07:39+01:00 DEBUG: I 2012-03-12T20:07:39+01:00 DEBUG: I 2012-03-12T20:07:39+01:00 DEBUG: I 2012-03-12T20:07:39+01:00 DEBUG: I 2012-03-12T20:07:39+01:00 DEBUG: I 4 2012-03-12T20:07:39+01:00 DEBUG: I 2012-03-12T20:07:39+01:00 DEBUG: I 2012-03-12T20:07:39+01:00 DEBUG: I 2012-03-12T20:07:39+01:00 DEBUG: I 4 2012-03-12T20:07:39+01:00 DEBUG: I 2012-03-12T20:07:39+01:00 DEBUG: I 2012-03-12T20:07:39+01:00 DEBUG: I 7 2012-03-12T20:07:39+01:00 DEBUG: I 2012-03-12T20:07:39+01:00 DEBUG: I 2012-03-12T20:07:39+01:00 DEBUG: [androidc195282820] Loading state for synckey {4f5e2f2a-e0b0-4096-bb65-4135c0a80101}5 2012-03-12T20:07:39+01:00 DEBUG: I 2012-03-12T20:07:39+01:00 DEBUG: I 2012-03-12T20:07:39+01:00 DEBUG: I 2012-03-12T20:07:39+01:00 DEBUG: I 6461576b-d57d-4b78-91d1-65c3c2ccd566 2012-03-12T20:07:39+01:00 DEBUG: I 2012-03-12T20:07:39+01:00 DEBUG: I 2012-03-12T20:07:39+01:00 DEBUG: I 2012-03-12T20:07:39+01:00 DEBUG: I LAEAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAsAAAABAAIAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAMAAAACAAIAAAAAAAAAxP///w== 2012-03-12T20:07:39+01:00 DEBUG: I 2012-03-12T20:07:39+01:00 DEBUG: I 2012-03-12T20:07:39+01:00 DEBUG: I 1 2012-03-12T20:07:39+01:00 DEBUG: I 2012-03-12T20:07:39+01:00 DEBUG: I 2012-03-12T20:07:39+01:00 DEBUG: I 20120607T040000Z 2012-03-12T20:07:39+01:00 DEBUG: I 2012-03-12T20:07:39+01:00 DEBUG: I 2012-03-12T20:07:39+01:00 DEBUG: I 20120608T040000Z 2012-03-12T20:07:39+01:00 DEBUG: I 2012-03-12T20:07:39+01:00 DEBUG: I 2012-03-12T20:07:39+01:00 DEBUG: I 20120312T190738Z 2012-03-12T20:07:39+01:00 DEBUG: I 2012-03-12T20:07:39+01:00 DEBUG: I 2012-03-12T20:07:39+01:00 DEBUG: I Anniversaire K??vin 2012-03-12T20:07:39+01:00 DEBUG: I 2012-03-12T20:07:39+01:00 DEBUG: I 2012-03-12T20:07:39+01:00 DEBUG: I 2012-03-12T20:07:39+01:00 DEBUG: I kevinlj at l33t5p34k.synology.me 2012-03-12T20:07:39+01:00 DEBUG: I 2012-03-12T20:07:39+01:00 DEBUG: I 2012-03-12T20:07:39+01:00 DEBUG: I 2012-03-12T20:07:39+01:00 DEBUG: I 5 2012-03-12T20:07:39+01:00 DEBUG: I 2012-03-12T20:07:39+01:00 DEBUG: I 2012-03-12T20:07:39+01:00 DEBUG: I 6 2012-03-12T20:07:39+01:00 DEBUG: I 2012-03-12T20:07:39+01:00 DEBUG: I 2012-03-12T20:07:39+01:00 DEBUG: I 7 2012-03-12T20:07:39+01:00 DEBUG: I 2012-03-12T20:07:39+01:00 DEBUG: I 2012-03-12T20:07:39+01:00 DEBUG: I 2012-03-12T20:07:39+01:00 DEBUG: I 1440 2012-03-12T20:07:39+01:00 DEBUG: I 2012-03-12T20:07:39+01:00 DEBUG: I 2012-03-12T20:07:39+01:00 DEBUG: I 6461576b-d57d-4b78-91d1-65c3c2ccd566 2012-03-12T20:07:39+01:00 DEBUG: I 2012-03-12T20:07:39+01:00 DEBUG: I 2012-03-12T20:07:39+01:00 DEBUG: I 2 2012-03-12T20:07:39+01:00 DEBUG: I 2012-03-12T20:07:39+01:00 DEBUG: I 2012-03-12T20:07:39+01:00 DEBUG: I 0 2012-03-12T20:07:39+01:00 DEBUG: I 2012-03-12T20:07:39+01:00 DEBUG: I 2012-03-12T20:07:39+01:00 DEBUG: I 2 2012-03-12T20:07:39+01:00 DEBUG: I 2012-03-12T20:07:39+01:00 DEBUG: I 2012-03-12T20:07:39+01:00 DEBUG: Horde::changeMessage(Calendar, ) 2012-03-12T20:07:43+01:00 DEBUG: ActiveSync_Driver_Horde::_smartStatMessage:Calendar:20120312200742.UtZCUUzNsHNPXkl_iWZ0TDA at l33t5p34k.synology.me 2012-03-12T20:07:43+01:00 DEBUG: Updating state during change 2012-03-12T20:07:43+01:00 DEBUG: I 2012-03-12T20:07:43+01:00 DEBUG: I 2012-03-12T20:07:43+01:00 DEBUG: [androidc195282820] Processed 1 incoming changes 2012-03-12T20:07:43+01:00 DEBUG: I 2012-03-12T20:07:43+01:00 DEBUG: I 2012-03-12T20:07:43+01:00 DEBUG: I 2012-03-12T20:07:43+01:00 INFO: [androidc195282820] Beginning SYNC Response. 2012-03-12T20:07:43+01:00 DEBUG: [androidc195282820] Initializing message diff engine for Calendar 2012-03-12T20:07:43+01:00 DEBUG: Horde_ActiveSync_Driver_Horde::getServerChanges(Calendar, 1331579119, 1331579263, 1330369663) 2012-03-12T20:07:43+01:00 DEBUG: [androidc195282820] Found 1 message changes, checking for PIM initiated changes. 2012-03-12T20:07:43+01:00 DEBUG: ActiveSync_Driver_Horde::_smartStatMessage:Calendar:20120312200742.UtZCUUzNsHNPXkl_iWZ0TDA at l33t5p34k.synology.me 2012-03-12T20:07:43+01:00 DEBUG: [androidc195282820] Ignoring PIM initiated change for 20120312200742.UtZCUUzNsHNPXkl_iWZ0TDA at l33t5p34k.synology.me(PIM TS: 1331579263 Stat TS: 0 2012-03-12T20:07:43+01:00 DEBUG: Generating new synckey. Old synckey: {4f5e2f2a-e0b0-4096-bb65-4135c0a80101}5 2012-03-12T20:07:43+01:00 DEBUG: New synckey generated: {4f5e2f2a-e0b0-4096-bb65-4135c0a80101}6 2012-03-12T20:07:43+01:00 DEBUG: O 2012-03-12T20:07:43+01:00 DEBUG: O 2012-03-12T20:07:43+01:00 DEBUG: O 2012-03-12T20:07:43+01:00 DEBUG: O 2012-03-12T20:07:43+01:00 DEBUG: O Calendar 2012-03-12T20:07:43+01:00 DEBUG: O 2012-03-12T20:07:43+01:00 DEBUG: O 2012-03-12T20:07:43+01:00 DEBUG: O {4f5e2f2a-e0b0-4096-bb65-4135c0a80101}6 2012-03-12T20:07:43+01:00 DEBUG: O 2012-03-12T20:07:43+01:00 DEBUG: O 2012-03-12T20:07:43+01:00 DEBUG: O Calendar 2012-03-12T20:07:43+01:00 DEBUG: O 2012-03-12T20:07:43+01:00 DEBUG: O 2012-03-12T20:07:43+01:00 DEBUG: O 1 2012-03-12T20:07:43+01:00 DEBUG: O 2012-03-12T20:07:43+01:00 DEBUG: O 2012-03-12T20:07:43+01:00 DEBUG: O 2012-03-12T20:07:43+01:00 DEBUG: O 2012-03-12T20:07:43+01:00 DEBUG: O 6461576b-d57d-4b78-91d1-65c3c2ccd566 2012-03-12T20:07:43+01:00 DEBUG: O 2012-03-12T20:07:43+01:00 DEBUG: O 2012-03-12T20:07:43+01:00 DEBUG: O 20120312200742.UtZCUUzNsHNPXkl_iWZ0TDA at l33t5p34k.synology.me 2012-03-12T20:07:43+01:00 DEBUG: O 2012-03-12T20:07:43+01:00 DEBUG: O 2012-03-12T20:07:43+01:00 DEBUG: O 1 2012-03-12T20:07:43+01:00 DEBUG: O 2012-03-12T20:07:43+01:00 DEBUG: O 2012-03-12T20:07:43+01:00 DEBUG: O 2012-03-12T20:07:43+01:00 DEBUG: O 2012-03-12T20:07:43+01:00 DEBUG: [androidc195282820] Saving state: Array ( [0] => {4f5e2f2a-e0b0-4096-bb65-4135c0a80101}6 [1] => a:0:{} [2] => androidc195282820 [3] => 1331579263 [4] => Calendar [5] => kevinlj ) 2012-03-12T20:07:43+01:00 DEBUG: O 2012-03-12T20:07:43+01:00 DEBUG: O 2012-03-12T20:07:43+01:00 INFO: User kevinlj logged off >> in the activesync log: >> >> 2012-03-12T18:47:31+01:00 ERR: No timezone found for the given offsets > > That would definitely cause a problem. > > What timezone is the device set to? From bugs at horde.org Mon Mar 12 20:22:09 2012 From: bugs at horde.org (bugs at horde.org) Date: Mon, 12 Mar 2012 20:22:09 +0000 Subject: [Tickets #11068] Re: Recursive event on android or ios 5 In-Reply-To: References: Message-ID: <20120312202214.Horde.4TJ0JM_2HjZPXlr2FQBSqMA@bugs.horde.org> DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED. Ticket URL: http://bugs.horde.org/ticket/11068 ------------------------------------------------------------------------------ Ticket | 11068 Updated By | Michael Rubinsky Summary | Recursive event on android or ios 5 Queue | Horde Groupware Version | 4.0.6 Type | Bug State | Feedback Priority | 2. Medium Milestone | Patch | Owners | Michael Rubinsky ------------------------------------------------------------------------------ Michael Rubinsky (2012-03-12 20:22) wrote: > Just changed my timezone to New York ... same bug on the iphone > double events is set up ... What bug? This sync log looks fine, without the error you had previously. What do you mean by "double events"? This log shows exactly one event being sent from the device to the server, with the server sending an ack that it added the event one time. From bugs at horde.org Mon Mar 12 20:37:49 2012 From: bugs at horde.org (bugs at horde.org) Date: Mon, 12 Mar 2012 20:37:49 +0000 Subject: [Tickets #11068] Re: Recursive event on android or ios 5 In-Reply-To: References: Message-ID: <20120312203750.Horde.FfLwCs_2HjZPXl6eeeIyqDA@bugs.horde.org> DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED. Ticket URL: http://bugs.horde.org/ticket/11068 ------------------------------------------------------------------------------ Ticket | 11068 Updated By | Michael Rubinsky Summary | Recursive event on android or ios 5 Queue | Horde Groupware Version | 4.0.6 Type | Bug -State | Feedback +State | Resolved Priority | 2. Medium Milestone | Patch | Owners | Michael Rubinsky ------------------------------------------------------------------------------ Michael Rubinsky (2012-03-12 20:37) wrote: > in the activesync log: > > 2012-03-12T18:47:31+01:00 ERR: No timezone found for the given offsets > > 2012-03-12T18:47:29+01:00 DEBUG: I > 2012-03-12T18:47:29+01:00 DEBUG: I > xP///wAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAoAAAAEAAMAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA$ > 2012-03-12T18:47:29+01:00 DEBUG: I > > all over seems to be ok This is fixed by these commits: http://lists.horde.org/archives/commits/2012-March/014272.html From bugs at horde.org Mon Mar 12 20:38:09 2012 From: bugs at horde.org (bugs at horde.org) Date: Mon, 12 Mar 2012 20:38:09 +0000 Subject: [Tickets #11068] Re: Recursive event on android or ios 5 In-Reply-To: References: Message-ID: <20120312203810.Horde.KThhZs_2HjZPXl6yQeSCqDA@bugs.horde.org> DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED. Ticket URL: http://bugs.horde.org/ticket/11068 ------------------------------------------------------------------------------ Ticket | 11068 Updated By | Michael Rubinsky Summary | Recursive event on android or ios 5 -Queue | Horde Groupware +Queue | Synchronization -Version | 4.0.6 +Version | Git master Type | Bug State | Resolved Priority | 2. Medium Milestone | Patch | Owners | Michael Rubinsky ------------------------------------------------------------------------------ From bugs at horde.org Mon Mar 12 21:23:30 2012 From: bugs at horde.org (bugs at horde.org) Date: Mon, 12 Mar 2012 21:23:30 +0000 Subject: [Tickets #11068] Re: Recursive event on android or ios 5 In-Reply-To: References: Message-ID: <20120312212331.Horde.GHi3GM_2HjZPXmlTfN_DxpA@bugs.horde.org> DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED. Ticket URL: http://bugs.horde.org/ticket/11068 ------------------------------------------------------------------------------ Ticket | 11068 Updated By | melian.the.queen at gmail.com Summary | Recursive event on android or ios 5 Queue | Synchronization Version | Git master Type | Bug State | Resolved Priority | 2. Medium Milestone | Patch | Owners | Michael Rubinsky ------------------------------------------------------------------------------ melian.the.queen at gmail.com (2012-03-12 21:23) wrote: Set Up the event with entire day and add a reminder 24 hours before add 2 entrie on the web interfaces i test with your patchand comment here :) Thanks >> Just changed my timezone to New York ... same bug on the iphone >> double events is set up ... > > What bug? This sync log looks fine, without the error you had > previously. What do you mean by "double events"? This log shows > exactly one event being sent from the device to the server, with the > server sending an ack that it added the event one time. From bugs at horde.org Tue Mar 13 02:05:57 2012 From: bugs at horde.org (bugs at horde.org) Date: Tue, 13 Mar 2012 02:05:57 +0000 Subject: [Tickets #11068] Re: Recursive event on android or ios 5 In-Reply-To: References: Message-ID: <20120313020559.Horde.OxRFBM_2HjZPXquHYaVj9UA@bugs.horde.org> DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED. Ticket URL: http://bugs.horde.org/ticket/11068 ------------------------------------------------------------------------------ Ticket | 11068 Updated By | melian.the.queen at gmail.com Summary | Recursive event on android or ios 5 Queue | Synchronization Version | Git master Type | Bug State | Resolved Priority | 2. Medium Milestone | Patch | Owners | Michael Rubinsky ------------------------------------------------------------------------------ melian.the.queen at gmail.com (2012-03-13 02:05) wrote: Ok i apply the patch and the sync work. Set a recurrent event all year the 07 juin with a reminder 24 hours before. he sync 2 events: the 06 juin and the 07 juin. the reminder set has a events? You can see the screenshot of the web calendar http://www.imagup.com/data/1146269797.html and the log: 2012-03-13T02:53:35+01:00 DEBUG: [androidc195282820] SYNC request received for user kevinlj 2012-03-13T02:53:35+01:00 DEBUG: [androidc195282820] loadDeviceInfo: kevinlj 2012-03-13T02:53:35+01:00 INFO: Request being handled for device: androidc195282820 Supporting protocol version: 2.5 2012-03-13T02:53:35+01:00 INFO: [androidc195282820] Handling SYNC command. 2012-03-13T02:53:35+01:00 DEBUG: [androidc195282820] Checking policykey for device Key: 0 User: kevinlj 2012-03-13T02:53:35+01:00 DEBUG: [androidc195282820] loadDeviceInfo: kevinlj 2012-03-13T02:53:35+01:00 DEBUG: Policykey: 0 verified. 2012-03-13T02:53:35+01:00 DEBUG: I 2012-03-13T02:53:35+01:00 DEBUG: I 2012-03-13T02:53:35+01:00 DEBUG: I 2012-03-13T02:53:35+01:00 DEBUG: I 2012-03-13T02:53:35+01:00 DEBUG: I Calendar 2012-03-13T02:53:35+01:00 INFO: [androidc195282820] Syncing folder class: Calendar 2012-03-13T02:53:35+01:00 DEBUG: I 2012-03-13T02:53:35+01:00 DEBUG: I 2012-03-13T02:53:35+01:00 DEBUG: I {4f5e2f2a-e0b0-4096-bb65-4135c0a80101}7 2012-03-13T02:53:35+01:00 DEBUG: I 2012-03-13T02:53:35+01:00 DEBUG: I 2012-03-13T02:53:35+01:00 DEBUG: I Calendar 2012-03-13T02:53:35+01:00 INFO: [androidc195282820] Folder server id: Calendar 2012-03-13T02:53:35+01:00 DEBUG: I 2012-03-13T02:53:35+01:00 DEBUG: I 2012-03-13T02:53:35+01:00 DEBUG: I 2012-03-13T02:53:35+01:00 DEBUG: I 2012-03-13T02:53:35+01:00 DEBUG: I 4 2012-03-13T02:53:35+01:00 DEBUG: I 2012-03-13T02:53:35+01:00 DEBUG: I 2012-03-13T02:53:35+01:00 DEBUG: I 2012-03-13T02:53:35+01:00 DEBUG: I 4 2012-03-13T02:53:35+01:00 DEBUG: I 2012-03-13T02:53:35+01:00 DEBUG: I 2012-03-13T02:53:35+01:00 DEBUG: I 7 2012-03-13T02:53:35+01:00 DEBUG: I 2012-03-13T02:53:35+01:00 DEBUG: I 2012-03-13T02:53:35+01:00 DEBUG: [androidc195282820] Loading state for synckey {4f5e2f2a-e0b0-4096-bb65-4135c0a80101}7 2012-03-13T02:53:35+01:00 DEBUG: I 2012-03-13T02:53:35+01:00 DEBUG: I 2012-03-13T02:53:35+01:00 DEBUG: I 2012-03-13T02:53:35+01:00 DEBUG: I ad61be54-8564-42a3-8439-e0de9e2c37df 2012-03-13T02:53:35+01:00 DEBUG: I 2012-03-13T02:53:35+01:00 DEBUG: I 2012-03-13T02:53:35+01:00 DEBUG: I 2012-03-13T02:53:35+01:00 DEBUG: I xP///wAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAoAAAAEAAMAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAMAAAAFAAIAAAAAAAAAxP///w== 2012-03-13T02:53:35+01:00 DEBUG: I 2012-03-13T02:53:35+01:00 DEBUG: I 2012-03-13T02:53:35+01:00 DEBUG: I 1 2012-03-13T02:53:35+01:00 DEBUG: I 2012-03-13T02:53:35+01:00 DEBUG: I 2012-03-13T02:53:35+01:00 DEBUG: I 20120606T220000Z 2012-03-13T02:53:35+01:00 DEBUG: I 2012-03-13T02:53:35+01:00 DEBUG: I 2012-03-13T02:53:35+01:00 DEBUG: I 20120607T220000Z 2012-03-13T02:53:35+01:00 DEBUG: I 2012-03-13T02:53:35+01:00 DEBUG: I 2012-03-13T02:53:35+01:00 DEBUG: I 20120313T015329Z 2012-03-13T02:53:35+01:00 DEBUG: I 2012-03-13T02:53:35+01:00 DEBUG: I 2012-03-13T02:53:35+01:00 DEBUG: I Anniversaire K??vin 2012-03-13T02:53:35+01:00 DEBUG: I 2012-03-13T02:53:35+01:00 DEBUG: I 2012-03-13T02:53:35+01:00 DEBUG: I 2012-03-13T02:53:35+01:00 DEBUG: I kevinlj at l33t5p34k.synology.me 2012-03-13T02:53:35+01:00 DEBUG: I 2012-03-13T02:53:35+01:00 DEBUG: I 2012-03-13T02:53:35+01:00 DEBUG: I 2012-03-13T02:53:35+01:00 DEBUG: I 5 2012-03-13T02:53:35+01:00 DEBUG: I 2012-03-13T02:53:35+01:00 DEBUG: I 2012-03-13T02:53:35+01:00 DEBUG: I 6 2012-03-13T02:53:35+01:00 DEBUG: I 2012-03-13T02:53:35+01:00 DEBUG: I 2012-03-13T02:53:35+01:00 DEBUG: I 7 2012-03-13T02:53:35+01:00 DEBUG: I 2012-03-13T02:53:35+01:00 DEBUG: I 2012-03-13T02:53:35+01:00 DEBUG: I 2012-03-13T02:53:35+01:00 DEBUG: I 1440 2012-03-13T02:53:35+01:00 DEBUG: I 2012-03-13T02:53:35+01:00 DEBUG: I 2012-03-13T02:53:35+01:00 DEBUG: I ad61be54-8564-42a3-8439-e0de9e2c37df 2012-03-13T02:53:35+01:00 DEBUG: I 2012-03-13T02:53:35+01:00 DEBUG: I 2012-03-13T02:53:35+01:00 DEBUG: I 2 2012-03-13T02:53:35+01:00 DEBUG: I 2012-03-13T02:53:35+01:00 DEBUG: I 2012-03-13T02:53:35+01:00 DEBUG: I 0 2012-03-13T02:53:35+01:00 DEBUG: I 2012-03-13T02:53:35+01:00 DEBUG: I 2012-03-13T02:53:35+01:00 DEBUG: I 2 2012-03-13T02:53:35+01:00 DEBUG: I 2012-03-13T02:53:35+01:00 DEBUG: I 2012-03-13T02:53:35+01:00 DEBUG: Horde::changeMessage(Calendar, ) 2012-03-13T02:53:37+01:00 DEBUG: ActiveSync_Driver_Horde::_smartStatMessage:Calendar:20120313025336.VY_XAEzNsHNPXqig4Fp0USA at l33t5p34k.synology.me 2012-03-13T02:53:37+01:00 DEBUG: Updating state during change 2012-03-13T02:53:37+01:00 DEBUG: I 2012-03-13T02:53:37+01:00 DEBUG: I 2012-03-13T02:53:37+01:00 DEBUG: [androidc195282820] Processed 1 incoming changes 2012-03-13T02:53:37+01:00 DEBUG: I 2012-03-13T02:53:37+01:00 DEBUG: I 2012-03-13T02:53:37+01:00 DEBUG: I 2012-03-13T02:53:37+01:00 INFO: [androidc195282820] Beginning SYNC Response. 2012-03-13T02:53:37+01:00 DEBUG: [androidc195282820] Initializing message diff engine for Calendar 2012-03-13T02:53:37+01:00 DEBUG: Horde_ActiveSync_Driver_Horde::getServerChanges(Calendar, 1331580707, 1331603617, 1330394017) 2012-03-13T02:53:37+01:00 DEBUG: [androidc195282820] Found 1 message changes, checking for PIM initiated changes. 2012-03-13T02:53:37+01:00 DEBUG: ActiveSync_Driver_Horde::_smartStatMessage:Calendar:20120313025336.VY_XAEzNsHNPXqig4Fp0USA at l33t5p34k.synology.me 2012-03-13T02:53:37+01:00 DEBUG: [androidc195282820] Ignoring PIM initiated change for 20120313025336.VY_XAEzNsHNPXqig4Fp0USA at l33t5p34k.synology.me(PIM TS: 1331603617 Stat TS: 0 2012-03-13T02:53:37+01:00 DEBUG: Generating new synckey. Old synckey: {4f5e2f2a-e0b0-4096-bb65-4135c0a80101}7 2012-03-13T02:53:37+01:00 DEBUG: New synckey generated: {4f5e2f2a-e0b0-4096-bb65-4135c0a80101}8 2012-03-13T02:53:37+01:00 DEBUG: O 2012-03-13T02:53:37+01:00 DEBUG: O 2012-03-13T02:53:37+01:00 DEBUG: O 2012-03-13T02:53:37+01:00 DEBUG: O 2012-03-13T02:53:37+01:00 DEBUG: O Calendar 2012-03-13T02:53:37+01:00 DEBUG: O 2012-03-13T02:53:37+01:00 DEBUG: O 2012-03-13T02:53:37+01:00 DEBUG: O {4f5e2f2a-e0b0-4096-bb65-4135c0a80101}8 2012-03-13T02:53:37+01:00 DEBUG: O 2012-03-13T02:53:37+01:00 DEBUG: O 2012-03-13T02:53:37+01:00 DEBUG: O Calendar 2012-03-13T02:53:37+01:00 DEBUG: O 2012-03-13T02:53:37+01:00 DEBUG: O 2012-03-13T02:53:37+01:00 DEBUG: O 1 2012-03-13T02:53:37+01:00 DEBUG: O 2012-03-13T02:53:37+01:00 DEBUG: O 2012-03-13T02:53:37+01:00 DEBUG: O 2012-03-13T02:53:37+01:00 DEBUG: O 2012-03-13T02:53:37+01:00 DEBUG: O ad61be54-8564-42a3-8439-e0de9e2c37df 2012-03-13T02:53:37+01:00 DEBUG: O 2012-03-13T02:53:37+01:00 DEBUG: O 2012-03-13T02:53:37+01:00 DEBUG: O 20120313025336.VY_XAEzNsHNPXqig4Fp0USA at l33t5p34k.synology.me 2012-03-13T02:53:37+01:00 DEBUG: O 2012-03-13T02:53:37+01:00 DEBUG: O 2012-03-13T02:53:37+01:00 DEBUG: O 1 2012-03-13T02:53:37+01:00 DEBUG: O 2012-03-13T02:53:37+01:00 DEBUG: O 2012-03-13T02:53:37+01:00 DEBUG: O 2012-03-13T02:53:37+01:00 DEBUG: O 2012-03-13T02:53:37+01:00 DEBUG: [androidc195282820] Saving state: Array ( [0] => {4f5e2f2a-e0b0-4096-bb65-4135c0a80101}8 [1] => a:0:{} [2] => androidc195282820 [3] => 1331603617 [4] => Calendar [5] => kevinlj ) 2012-03-13T02:53:37+01:00 DEBUG: O 2012-03-13T02:53:37+01:00 DEBUG: O 2012-03-13T02:53:37+01:00 INFO: User kevinlj logged off >> in the activesync log: >> >> 2012-03-12T18:47:31+01:00 ERR: No timezone found for the given offsets >> >> 2012-03-12T18:47:29+01:00 DEBUG: I >> 2012-03-12T18:47:29+01:00 DEBUG: I >> xP///wAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAoAAAAEAAMAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA$ >> 2012-03-12T18:47:29+01:00 DEBUG: I >> >> all over seems to be ok > > This is fixed by these commits: > > http://lists.horde.org/archives/commits/2012-March/014272.html > From bugs at horde.org Tue Mar 13 04:09:01 2012 From: bugs at horde.org (bugs at horde.org) Date: Tue, 13 Mar 2012 04:09:01 +0000 Subject: [Tickets #11068] Re: Recursive event on android or ios 5 In-Reply-To: References: Message-ID: <20120313040902.Horde.BhaLKs_2HjZPXsheZHMWftA@bugs.horde.org> DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED. Ticket URL: http://bugs.horde.org/ticket/11068 ------------------------------------------------------------------------------ Ticket | 11068 Updated By | Michael Rubinsky Summary | Recursive event on android or ios 5 Queue | Synchronization Version | Git master Type | Bug State | Resolved Priority | 2. Medium Milestone | Patch | Owners | Michael Rubinsky ------------------------------------------------------------------------------ Michael Rubinsky (2012-03-13 04:09) wrote: That looks like Bug: 10991 which should also be fixed by the patch attached to that ticket. From bugs at horde.org Tue Mar 13 05:39:10 2012 From: bugs at horde.org (bugs at horde.org) Date: Tue, 13 Mar 2012 05:39:10 +0000 Subject: [Tickets #11068] Re: Recursive event on android or ios 5 In-Reply-To: References: Message-ID: <20120313053912.Horde.fOCpRc_2HjZPXt2AmUmwJBA@bugs.horde.org> DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED. Ticket URL: http://bugs.horde.org/ticket/11068 ------------------------------------------------------------------------------ Ticket | 11068 Updated By | melian.the.queen at gmail.com Summary | Recursive event on android or ios 5 Queue | Synchronization Version | Git master Type | Bug State | Resolved Priority | 2. Medium Milestone | Patch | Owners | Michael Rubinsky ------------------------------------------------------------------------------ melian.the.queen at gmail.com (2012-03-13 05:39) wrote: Thanks it's fixed now. this post can be closed > That looks like Bug: 10991 which should also be fixed by the patch > attached to that ticket. From bugs at horde.org Tue Mar 13 05:45:04 2012 From: bugs at horde.org (bugs at horde.org) Date: Tue, 13 Mar 2012 05:45:04 +0000 Subject: [Tickets #10991] Re: Allday events are not correctly synchronized In-Reply-To: References: Message-ID: <20120313054506.Horde.gH0qM8_2HjZPXt7iG0vSYPA@bugs.horde.org> DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED. Ticket URL: http://bugs.horde.org/ticket/10991 ------------------------------------------------------------------------------ Ticket | 10991 Updated By | Michael Rubinsky Summary | Allday events are not correctly synchronized Queue | Synchronization Version | Git master Type | Bug -State | Feedback +State | Resolved Priority | 2. Medium Milestone | Patch | Owners | Michael Rubinsky ------------------------------------------------------------------------------ From bugs at horde.org Tue Mar 13 08:59:57 2012 From: bugs at horde.org (bugs at horde.org) Date: Tue, 13 Mar 2012 08:59:57 +0000 Subject: [Tickets #11073] Charset is not set for the "View Source" Message-ID: DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED. Ticket URL: http://bugs.horde.org/ticket/11073 ------------------------------------------------------------------------------ Ticket | 11073 Created By | ak at lps.komi.ru Summary | Charset is not set for the "View Source" Queue | IMP Version | Git master Type | Bug State | Unconfirmed Priority | 3. High Milestone | Patch | Owners | ------------------------------------------------------------------------------ ak at lps.komi.ru (2012-03-13 08:59) wrote: One more needful thing for non-latin alphabet's users. When there is generates view of "View Source" [actionID=view_source] there is setting of the content type of 'text/plain' without charset. For correctness file /webroot/imp/view.php, lines after 194 should be: case 'view_source': $msg = $contents->fullMessageText(array('stream' => true)); rewind($msg); while (!feof($msg)) { $line=fgets($msg, 4096); if ($line !== false){ if (strlen($line)==0) break 1; if (strpos($line ,"charset=")>0 && ($pos=strpos($line ,";"))>0){$ct=substr($line,$pos);break 1;} } } fseek($msg, 0, SEEK_END); $headertext='text/plain'; if (isset($ct))$headertext.=$ct; $browser->downloadHeaders('Message Source', $headertext, true, ftell($msg)); INSTEAD OF case 'view_source': $msg = $contents->fullMessageText(array('stream' => true)); fseek($msg, 0, SEEK_END); $browser->downloadHeaders('Message Source', 'text/plain', true, ftell($msg)); From bugs at horde.org Tue Mar 13 09:39:03 2012 From: bugs at horde.org (bugs at horde.org) Date: Tue, 13 Mar 2012 03:39:03 -0600 Subject: [Tickets #11069] Re: wrong utf-8 encondigs at html viewer In-Reply-To: References: Message-ID: <20120313033908.Horde.R9H0F8_2HjZPXxW8PDMSxmA@bugs.horde.org> DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED. Ticket URL: http://bugs.horde.org/ticket/11069 ------------------------------------------------------------------------------ Ticket | 11069 Updated By | Michael Slusarz Summary | wrong utf-8 encondigs at html viewer Queue | Horde Framework Packages Version | Git master Type | Bug -State | Unconfirmed +State | Not A Bug Priority | 3. High Milestone | Patch | Owners | ------------------------------------------------------------------------------ Michael Slusarz (2012-03-13 03:39) wrote: No. You can't go inserting HTML tags into HTML data, because you are overwriting the contents of the HTML data. Not to mention there is no reproducible issue here. At a minimum, someone would have to provide a failing test case. This is most likely due to an out-of-date libxml anyway. From bugs at horde.org Tue Mar 13 09:45:58 2012 From: bugs at horde.org (bugs at horde.org) Date: Tue, 13 Mar 2012 03:45:58 -0600 Subject: [Tickets #10967] Re: Wrong sorting by date in IMP In-Reply-To: References: Message-ID: <20120313034600.Horde.NoZjOM_2HjZPXxdYyC-izRA@bugs.horde.org> DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED. Ticket URL: http://bugs.horde.org/ticket/10967 ------------------------------------------------------------------------------ Ticket | 10967 Updated By | Michael Slusarz Summary | Wrong sorting by date in IMP Queue | IMP Version | 5.0.17 Type | Bug State | Not A Bug Priority | 1. Low Milestone | Patch | -Owners | +Owners | Horde Developers ------------------------------------------------------------------------------ Michael Slusarz (2012-03-13 03:45) wrote: The sorting is exactly right. Your messages: UID 840 = Mon, 01 Feb 2010 18:41:58 +0100 UID 842 = Sat, 19 Dec 2009 21:47:03 +0100 UID 845 = Sat, 19 Dec 2009 21:47:03 +0100 UID 1165 = Wed, 18 Aug 2010 08:55:56 +0200 Sure enough, the sorting is correct: C: 3 UID SORT (ARRIVAL) US-ASCII UNDELETED S: * SORT 840 842 845 1165 And can be verified since UIDs are always increasing in a mailbox based on arrival date. There is no attempt to sort by *message* date in this log. Arrival date != message date. From bugs at horde.org Tue Mar 13 09:46:36 2012 From: bugs at horde.org (bugs at horde.org) Date: Tue, 13 Mar 2012 03:46:36 -0600 Subject: [Tickets #10893] Re: Invalid context menu on folders In-Reply-To: References: Message-ID: <20120313034638.Horde.h-XfM8_2HjZPXxd_ELuyxuA@bugs.horde.org> DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED. Ticket URL: http://bugs.horde.org/ticket/10893 ------------------------------------------------------------------------------ Ticket | 10893 Updated By | Michael Slusarz Summary | Invalid context menu on folders Queue | IMP Version | 5.0.16 Type | Bug State | Not A Bug Priority | 2. Medium Milestone | Patch | Owners | ------------------------------------------------------------------------------ Michael Slusarz (2012-03-13 03:46) wrote: > Screencast doesn't helped? No. From bugs at horde.org Tue Mar 13 09:49:37 2012 From: bugs at horde.org (bugs at horde.org) Date: Tue, 13 Mar 2012 03:49:37 -0600 Subject: [Tickets #11061] Re: missing index 'auth' /usr/share/pear/.../Mail.php In-Reply-To: References: Message-ID: <20120313034944.Horde.p2QQMc_2HjZPXxg4ZRKivmA@bugs.horde.org> DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED. Ticket URL: http://bugs.horde.org/ticket/11061 ------------------------------------------------------------------------------ Ticket | 11061 Updated By | Michael Slusarz Summary | missing index 'auth' /usr/share/pear/.../Mail.php Queue | Horde Groupware Webmail Edition Version | 4.0.6 Type | Bug -State | Unconfirmed +State | Not A Bug Priority | 1. Low Milestone | Patch | Owners | ------------------------------------------------------------------------------ Michael Slusarz (2012-03-13 03:49) wrote: Your horde/conf.php is not correct. If using SMTP, the 'auth' params is a required value. From bugs at horde.org Tue Mar 13 09:55:32 2012 From: bugs at horde.org (bugs at horde.org) Date: Tue, 13 Mar 2012 03:55:32 -0600 Subject: [Tickets #11073] Re: Charset is not set for the "View Source" In-Reply-To: References: Message-ID: <20120313035533.Horde.MNT-PM_2HjZPXxmVVJPS29A@bugs.horde.org> DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED. Ticket URL: http://bugs.horde.org/ticket/11073 ------------------------------------------------------------------------------ Ticket | 11073 Updated By | Michael Slusarz Summary | Charset is not set for the "View Source" Queue | IMP Version | Git master Type | Bug -State | Unconfirmed +State | Not A Bug Priority | 3. High Milestone | Patch | Owners | ------------------------------------------------------------------------------ Michael Slusarz (2012-03-13 03:55) wrote: > One more needful thing for non-latin alphabet's users. > When there is generates view of "View Source" [actionID=view_source] > there is setting of the content type of 'text/plain' without charset. > For correctness file /webroot/imp/view.php, lines after 194 should be: > > case 'view_source': > $msg = $contents->fullMessageText(array('stream' => true)); > rewind($msg); > while (!feof($msg)) { > $line=fgets($msg, 4096); > if ($line !== false){ > if (strlen($line)==0) break 1; > if (strpos($line ,"charset=")>0 && ($pos=strpos($line > ,";"))>0){$ct=substr($line,$pos);break 1;} > } > } No. A MIME message could theoretically have a different charset for each part - you can't just choose the first part and use that as the charset. Additionally, the charset is worthless information since most messages will be encoded in US-ASCII. The charset parameter of Content-Type deals with the UNencoded data. To accurately download the contents of a message, you need to use the "Save As" feature. View Source is not meant to be a canonical representation of the data. From bugs at horde.org Tue Mar 13 10:00:59 2012 From: bugs at horde.org (bugs at horde.org) Date: Tue, 13 Mar 2012 10:00:59 +0000 Subject: [Tickets #11069] Re: wrong utf-8 encondigs at html viewer In-Reply-To: References: Message-ID: <20120313100104.Horde.cwaUFc_2HjZPXxrghmeC34A@bugs.horde.org> DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED. Ticket URL: http://bugs.horde.org/ticket/11069 ------------------------------------------------------------------------------ Ticket | 11069 Updated By | ak at lps.komi.ru Summary | wrong utf-8 encondigs at html viewer Queue | Horde Framework Packages Version | Git master Type | Bug State | Not A Bug Priority | 3. High Milestone | Patch | Owners | ------------------------------------------------------------------------------ ak at lps.komi.ru (2012-03-13 10:00) wrote: 1)libxml2 is the lattest availible via remi/epel/centos repos on Cenos5: it is 2.6.26. 2) Do you think that adding to the beginning of html content of string "" is more corect that adding of ? BTW it is also a hack,that creates ambiguous content. 3)I am not overwrite the html content -I just add more to the begginning of content, I suppose 3)It is easy to proof - but I dont plan to do test cases for such thing, I can just send 2 e-mails with attachments- html content and image with screenshot of correct rendering. 4) my solution works fine, and I know that many non-latin users need ANY solution that works! From bugs at horde.org Tue Mar 13 10:16:44 2012 From: bugs at horde.org (bugs at horde.org) Date: Tue, 13 Mar 2012 10:16:44 +0000 Subject: [Tickets #11073] Re: Charset is not set for the "View Source" In-Reply-To: References: Message-ID: <20120313101645.Horde.3VKWDs_2HjZPXx6N8bLy5sA@bugs.horde.org> DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED. Ticket URL: http://bugs.horde.org/ticket/11073 ------------------------------------------------------------------------------ Ticket | 11073 Updated By | ak at lps.komi.ru Summary | Charset is not set for the "View Source" Queue | IMP Version | Git master Type | Bug State | Not A Bug Priority | 3. High Milestone | Patch | Owners | ------------------------------------------------------------------------------ ak at lps.komi.ru (2012-03-13 10:16) wrote: 1)Mime message have content type neither a 'text/plain' nor a 'text/html', but ussually 'multipart/mixed' and some others. AND this patch puts charset only for the content type with a charset inside 'content type' header, i.e. for 'text/plain' and 'text/html' ! 2)If you are sending just text/plain than Apache adds defaultcharset itself, as I know 3)User offten cant change charset at the browser (for exaple me)when you are using window without toolbars and menues. Sic! 4)About rare or nor rare cases. Now it is very offten when autogenerated mail goes "Content-encoding: 8bit" with not latin1 and so on with first 7bit chars. Ask more people from not latin alphabet countries. 5)" Save as" is not the best solution, but it works. >> One more needful thing for non-latin alphabet's users. >> When there is generates view of "View Source" [actionID=view_source] >> there is setting of the content type of 'text/plain' without charset. >> For correctness file /webroot/imp/view.php, lines after 194 should be: >> >> case 'view_source': >> $msg = $contents->fullMessageText(array('stream' => true)); >> rewind($msg); >> while (!feof($msg)) { >> $line=fgets($msg, 4096); >> if ($line !== false){ >> if (strlen($line)==0) break 1; >> if (strpos($line ,"charset=")>0 && ($pos=strpos($line >> ,";"))>0){$ct=substr($line,$pos);break 1;} >> } >> } > > No. A MIME message could theoretically have a different charset for > each part - you can't just choose the first part and use that as the > charset. Additionally, the charset is worthless information since > most messages will be encoded in US-ASCII. The charset parameter of > Content-Type deals with the UNencoded data. > > To accurately download the contents of a message, you need to use > the "Save As" feature. View Source is not meant to be a canonical > representation of the data. From bugs at horde.org Tue Mar 13 10:24:28 2012 From: bugs at horde.org (bugs at horde.org) Date: Tue, 13 Mar 2012 11:24:28 +0100 Subject: [Tickets #11069] Re: wrong utf-8 encondigs at html viewer In-Reply-To: References: Message-ID: <20120313112430.Horde.jc82B8_2HjZPXyBeyilS56A@bugs.horde.org> DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED. Ticket URL: http://bugs.horde.org/ticket/11069 ------------------------------------------------------------------------------ Ticket | 11069 Updated By | Jan Schneider Summary | wrong utf-8 encondigs at html viewer Queue | Horde Framework Packages Version | Git master Type | Bug State | Not A Bug Priority | 3. High Milestone | Patch | Owners | ------------------------------------------------------------------------------ Jan Schneider (2012-03-13 11:24) wrote: > 1)libxml2 is the lattest availible via remi/epel/centos repos on > Cenos5: it is 2.6.26. This IS outdated. See http://www.horde.org/apps/horde/docs/INSTALL#prerequisites From bugs at horde.org Tue Mar 13 10:53:28 2012 From: bugs at horde.org (bugs at horde.org) Date: Tue, 13 Mar 2012 04:53:28 -0600 Subject: [Tickets #11073] Re: Charset is not set for the "View Source" In-Reply-To: References: Message-ID: <20120313045330.Horde.QWsdUc_2HjZPXycqE_Flq1A@bugs.horde.org> DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED. Ticket URL: http://bugs.horde.org/ticket/11073 ------------------------------------------------------------------------------ Ticket | 11073 Updated By | Michael Slusarz Summary | Charset is not set for the "View Source" Queue | IMP Version | Git master Type | Bug State | Not A Bug Priority | 3. High Milestone | Patch | Owners | ------------------------------------------------------------------------------ Michael Slusarz (2012-03-13 04:53) wrote: Again, no. Here's a message that will be completely broken in the display: Content-Type: text/plain; charset=iso-2022-jp Content-Transfer-Encoding: base64 The output message will be garbage Here's another message that will be completely broken: Content-Type: multipart/mixed; boundary=1 --1 Content-Type: text/plain; charset=iso-8859-1 [Text] --1 Content-Type: text/plain; charset=utf-8 [Text] --1-- Again, if you want a quick display of the part's contents THAT MAY **NOT** BE 100% ACCURATE, you can use View Source. If you need the EXACT CONTENTS, you MUST use save as. We do NOT guarantee that View Source outputs an accurate representation of the data. Because that is impossible to do in the browser (or, for that matter, any text editor). That's because MIME messages are NOT designed to be viewed as a single file! A MIME message != a discrete file as is commonly used in an OS. From bugs at horde.org Tue Mar 13 11:14:44 2012 From: bugs at horde.org (bugs at horde.org) Date: Tue, 13 Mar 2012 11:14:44 +0000 Subject: [Tickets #11073] Re: Charset is not set for the "View Source" In-Reply-To: References: Message-ID: <20120313111447.Horde.CjxQD8_2HjZPXywnmckFsuA@bugs.horde.org> DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED. Ticket URL: http://bugs.horde.org/ticket/11073 ------------------------------------------------------------------------------ Ticket | 11073 Updated By | ak at lps.komi.ru Summary | Charset is not set for the "View Source" Queue | IMP Version | Git master Type | Bug State | Not A Bug Priority | 3. High Milestone | Patch | Owners | ------------------------------------------------------------------------------ ak at lps.komi.ru (2012-03-13 11:14) wrote: 1)The difference b/w patched and unpatched version is only to use charset from headers of message (Not from mime-part cludge inside message as you put on 2-3 example!) instead of charset that Apache will put by default. That is ALL/ 2) For your examples: for the first there will be no visible changes, I suppose (as base64 enconding means only 7 bit chars). Anyway it will not be worse than default charset put by webserver. With second and third examples patch will not alter content type, as I scan only rfc-822 headers (before first empty line) and these charset are out of scope- these are mime's! > Again, no. Here's a message that will be completely broken in the display: > > Content-Type: text/plain; charset=iso-2022-jp > Content-Transfer-Encoding: base64 > > The output message will be garbage > > Here's another message that will be completely broken: > > Content-Type: multipart/mixed; boundary=1 > > --1 > Content-Type: text/plain; charset=iso-8859-1 > > [Text] > > --1 > Content-Type: text/plain; charset=utf-8 > > [Text] > > --1-- > > > Again, if you want a quick display of the part's contents THAT MAY > **NOT** BE 100% ACCURATE, you can use View Source. If you need the > EXACT CONTENTS, you MUST use save as. > > We do NOT guarantee that View Source outputs an accurate > representation of the data. Because that is impossible to do in the > browser (or, for that matter, any text editor). That's because MIME > messages are NOT designed to be viewed as a single file! A MIME > message != a discrete file as is commonly used in an OS. From bugs at horde.org Tue Mar 13 12:00:15 2012 From: bugs at horde.org (bugs at horde.org) Date: Tue, 13 Mar 2012 12:00:15 +0000 Subject: [Tickets #11053] Re: Problems replying/forwarding messages with attachments on pop-ups In-Reply-To: References: Message-ID: <20120313120017.Horde.1VM9I8_2HjZPXzbRtxc1yVA@bugs.horde.org> DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED. Ticket URL: http://bugs.horde.org/ticket/11053 ------------------------------------------------------------------------------ Ticket | 11053 Updated By | goncalo.queiros at portugalmail.net Summary | Problems replying/forwarding messages with attachments | on pop-ups Queue | IMP Version | Git master Type | Bug State | Unconfirmed Priority | 1. Low Milestone | Patch | Owners | ------------------------------------------------------------------------------ goncalo.queiros at portugalmail.net (2012-03-13 12:00) wrote: I use the master branch, not the develop one. I can't test this on the horde demo, because the "From" is always invalid, but on my computer i can reproduce it every time. Eve you opened the message in a new window (pop up) before you click on the reply/forward? >> Open a message in a new window, and press reply/forward (add any >> attachment, if the message hasn't any), and press send. >> >> The message will be sent, but imp will try to delete the attachments >> after the message is sent, which will show errors to the user. > > Is this truly seen in git (e.g. IMP 6 develop)? I can't reproduce. From bugs at horde.org Tue Mar 13 12:00:46 2012 From: bugs at horde.org (bugs at horde.org) Date: Tue, 13 Mar 2012 12:00:46 +0000 Subject: [Tickets #11053] Re: Problems replying/forwarding messages with attachments on pop-ups In-Reply-To: References: Message-ID: <20120313120048.Horde.USUqS8_2HjZPXzbwHjmVxzA@bugs.horde.org> DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED. Ticket URL: http://bugs.horde.org/ticket/11053 ------------------------------------------------------------------------------ Ticket | 11053 Updated By | goncalo.queiros at portugalmail.net Summary | Problems replying/forwarding messages with attachments | on pop-ups Queue | IMP Version | Git master Type | Bug State | Unconfirmed Priority | 1. Low Milestone | Patch | Owners | ------------------------------------------------------------------------------ goncalo.queiros at portugalmail.net (2012-03-13 12:00) wrote: Sorry, Eve = Have :-) > I use the master branch, not the develop one. > I can't test this on the horde demo, because the "From" is always > invalid, but on my computer i can reproduce it every time. > > Eve you opened the message in a new window (pop up) before you click > on the reply/forward? > >>> Open a message in a new window, and press reply/forward (add any >>> attachment, if the message hasn't any), and press send. >>> >>> The message will be sent, but imp will try to delete the attachments >>> after the message is sent, which will show errors to the user. >> >> Is this truly seen in git (e.g. IMP 6 develop)? I can't reproduce. > From bugs at horde.org Tue Mar 13 13:35:37 2012 From: bugs at horde.org (bugs at horde.org) Date: Tue, 13 Mar 2012 14:35:37 +0100 Subject: [Tickets #11053] Re: Problems replying/forwarding messages with attachments on pop-ups In-Reply-To: References: Message-ID: <20120313143539.Horde.BH72O8_2HjZPX00royWV3-A@bugs.horde.org> DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED. Ticket URL: http://bugs.horde.org/ticket/11053 ------------------------------------------------------------------------------ Ticket | 11053 Updated By | Jan Schneider Summary | Problems replying/forwarding messages with attachments | on pop-ups Queue | IMP Version | Git master Type | Bug -State | Unconfirmed +State | Assigned Priority | 1. Low Milestone | Patch | -Owners | +Owners | Michael Slusarz ------------------------------------------------------------------------------ Jan Schneider (2012-03-13 14:35) wrote: I can confirm this. The sendMessage request succeeds, but the deleteAttache request triggers this error: Fatal error: Call to a member function getName() on a non-object in /home/jan/horde-git/imp/lib/Ajax/Application.php on line 1342 Call Stack # Time Memory Function Location 1 0,0161 650792 {main}( ) ../ajax.php:0 2 0,5570 12960712 IMP_Ajax_Application->doAction( ) ../ajax.php:60 3 0,5570 12960712 Horde_Core_Ajax_Application->doAction( ) ../Application.php:95 4 0,5571 12961344 call_user_func ( array (0 => class IMP_Ajax_Application { public $notify = TRUE; protected $_mbox = NULL; protected $_queue = class IMP_Ajax_Queue { protected $_flag = array (...); protected $_poll = array (...); protected $_quota = FALSE }; protected $_suppress = NULL; protected $_readOnly = array (0 => 'html2Text', 1 => 'text2Html'); protected $_action = 'deleteAttach'; protected $_app = 'imp'; protected $_defaultDomain = NULL; protected $_vars = class Horde_Variables { protected $_expected = array (...); protected $_sanitized = FALSE; protected $_vars = array (...) } }, 1 => 'deleteAttach') ) ../Application.php:95 5 0,5571 12961344 IMP_Ajax_Application->deleteAttach( ) ../Application.php:95 From bugs at horde.org Tue Mar 13 17:36:11 2012 From: bugs at horde.org (bugs at horde.org) Date: Tue, 13 Mar 2012 18:36:11 +0100 Subject: [Tickets #11074] Refactor Imap_Client_DateTime Message-ID: DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED. Ticket URL: http://bugs.horde.org/ticket/11074 ------------------------------------------------------------------------------ Ticket | 11074 Created By | Jan Schneider Summary | Refactor Imap_Client_DateTime Queue | Horde Framework Packages Version | Git develop Type | Enhancement State | Assigned Priority | 1. Low Milestone | Patch | Owners | Michael Slusarz ------------------------------------------------------------------------------ Jan Schneider (2012-03-13 18:36) wrote: Now that we require PHP 5.3 and DateTime supports serialization, most of Imap_Client_DateTime may be obsolete. From bugs at horde.org Tue Mar 13 17:53:01 2012 From: bugs at horde.org (bugs at horde.org) Date: Tue, 13 Mar 2012 17:53:01 +0000 Subject: [Tickets #11075] plupload and jquery.mobile license and source code are not included Message-ID: DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED. Ticket URL: http://bugs.horde.org/ticket/11075 ------------------------------------------------------------------------------ Ticket | 11075 Created By | math.parent at gmail.com Summary | plupload and jquery.mobile license and source code are | not included Queue | Horde Base Version | Git master Type | Bug State | Unconfirmed Priority | 1. Low Milestone | Patch | Owners | ------------------------------------------------------------------------------ math.parent at gmail.com (2012-03-13 17:53) wrote: While uploading latest horde 4 to Debian, it was rejected because of missing copyright info: js/jquery.mobile/ contains compressed js and css files js/plupload/ contains several compressed js and one presumly sourceless swf file Can you please add an "src" directory including the uncompressed js and css files and the swf source file? Thanks Ref.: http://lists.alioth.debian.org/pipermail/pkg-horde-hackers/2012-March/007014.html From bugs at horde.org Tue Mar 13 18:38:05 2012 From: bugs at horde.org (bugs at horde.org) Date: Tue, 13 Mar 2012 12:38:05 -0600 Subject: [Tickets #11074] Re: Refactor Imap_Client_DateTime In-Reply-To: References: Message-ID: <20120313123807.Horde.iHgQfM_2HjZPX5QPemzkGjA@bugs.horde.org> DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED. Ticket URL: http://bugs.horde.org/ticket/11074 ------------------------------------------------------------------------------ Ticket | 11074 Updated By | Michael Slusarz Summary | Refactor Imap_Client_DateTime Queue | Horde Framework Packages Version | Git develop Type | Enhancement State | Assigned Priority | 1. Low Milestone | Patch | Owners | Michael Slusarz ------------------------------------------------------------------------------ Michael Slusarz (2012-03-13 12:38) wrote: I was looking at this yesterday. The only issue comes with the fact that internally in this object it is doing things like fixing common parsing issues with bad dates. It's probably cleaner to do this when instantiating the object rather than having a utility function return a DateTime object. We might be able to optimize by moving the date checking code into the constructor though. From bugs at horde.org Wed Mar 14 06:12:33 2012 From: bugs at horde.org (bugs at horde.org) Date: Wed, 14 Mar 2012 06:12:33 +0000 Subject: [Tickets #11053] Re: Problems replying/forwarding messages with attachments on pop-ups In-Reply-To: References: Message-ID: <20120314061235.Horde.QuWmTM_2HjZPYDbTIpgiWgA@dev.horde.org> DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED. Ticket URL: http://bugs.horde.org/ticket/11053 ------------------------------------------------------------------------------ Ticket | 11053 Updated By | Git Commit Summary | Problems replying/forwarding messages with attachments | on pop-ups Queue | IMP Version | Git master Type | Bug State | Assigned Priority | 1. Low Milestone | Patch | Owners | Michael Slusarz ------------------------------------------------------------------------------ Git Commit (2012-03-14 06:12) wrote: Changes have been made in Git (master): commit c05da3d7fef551ac8dd73d41f48aa507f988982e Author: Michael M Slusarz Date: Wed Mar 14 00:12:05 2012 -0600 Bug #11053: Clear attachment list if message send was successful. imp/js/compose-dimp.js | 5 +++++ 1 files changed, 5 insertions(+), 0 deletions(-) http://git.horde.org/horde-git/-/commit/c05da3d7fef551ac8dd73d41f48aa507f988982e From bugs at horde.org Wed Mar 14 06:13:13 2012 From: bugs at horde.org (bugs at horde.org) Date: Wed, 14 Mar 2012 00:13:13 -0600 Subject: [Tickets #11053] Re: Problems replying/forwarding messages with attachments on pop-ups In-Reply-To: References: Message-ID: <20120314001314.Horde.puOtas_2HjZPYDb6e5Qk8zA@bugs.horde.org> DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED. Ticket URL: http://bugs.horde.org/ticket/11053 ------------------------------------------------------------------------------ Ticket | 11053 Updated By | Michael Slusarz Summary | Problems replying/forwarding messages with attachments | on pop-ups Queue | IMP Version | Git master Type | Bug -State | Assigned +State | Resolved Priority | 1. Low Milestone | Patch | Owners | Michael Slusarz ------------------------------------------------------------------------------ Michael Slusarz (2012-03-14 00:13) wrote: This should fix. From bugs at horde.org Wed Mar 14 06:19:38 2012 From: bugs at horde.org (bugs at horde.org) Date: Wed, 14 Mar 2012 00:19:38 -0600 Subject: [Tickets #11073] Re: Charset is not set for the "View Source" In-Reply-To: References: Message-ID: <20120314001940.Horde.Hyy9Ys_2HjZPYDh8Pe1U8zA@bugs.horde.org> DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED. Ticket URL: http://bugs.horde.org/ticket/11073 ------------------------------------------------------------------------------ Ticket | 11073 Updated By | Michael Slusarz Summary | Charset is not set for the "View Source" Queue | IMP Version | Git master Type | Bug State | Not A Bug Priority | 3. High Milestone | Patch | Owners | ------------------------------------------------------------------------------ Michael Slusarz (2012-03-14 00:19) wrote: > With second and third examples patch will not alter content type, as > I scan only rfc-822 headers (before first empty line) and these > charset are out of scope- these are mime's! Exactly. RFC822 Headers MUST be in ASCII. So sending in US-ASCII (or UTF-8, or ISO-8859-1) is perfectly fine. From bugs at horde.org Wed Mar 14 08:53:57 2012 From: bugs at horde.org (bugs at horde.org) Date: Wed, 14 Mar 2012 08:53:57 +0000 Subject: [Tickets #11076] One Time Password Module Implementation - request for comment Message-ID: DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED. Ticket URL: http://bugs.horde.org/ticket/11076 ------------------------------------------------------------------------------ Ticket | 11076 Created By | c.denis at mrduck.fr Summary | One Time Password Module Implementation - request for | comment Queue | Horde Framework Packages Version | Git develop Type | Enhancement State | New Priority | 1. Low Milestone | Patch | 1 Owners | ------------------------------------------------------------------------------ c.denis at mrduck.fr (2012-03-14 08:53) wrote: Dear Dev-Team, as announced in #10980, I am trying to provide a first version of a hash-chain implementation for one time passwords. This is my personal reason why I would need the Dual_Auth module described previously. Nevertheless the modules are both fully functional on their own. With this otp module a user can log in to horde with another password every time and thus protect his credentials if he has to log in from an untrusted location such as an airport internet terminal. ATM this uses the same table as Auth_Sql (horde_users) with two additional fields. If requested this can of course be changed to use its own table. ALTER TABLE `horde_users` ADD `hash_chain_pwd` VARCHAR( 60 ) NOT NULL ALTER TABLE `horde_users` ADD `hash_chain_index` INT( 50 ) NOT NULL I am posting this at this state mainly to get feedback on the idea and the implementation. I am by all means willing to improve it from a security, architectural, or even style point of view. Further additions in terms of support in the passwd application, warnings when the password list runs empty and integration in the configuration page are planned if this is of common interest. Any comment is appreciated. Best regards, Carl c.denis at mrduck.fr (2012-03-14 08:53) uploaded: otp.patch http://bugs.horde.org/h/services/download/?module=whups&actionID=download_file&file=otp.patch&ticket=11076&fn=%2Fotp.patch From bugs at horde.org Wed Mar 14 08:54:31 2012 From: bugs at horde.org (bugs at horde.org) Date: Wed, 14 Mar 2012 08:54:31 +0000 Subject: [Tickets #11076] Re: One Time Password Module Implementation - request for comment In-Reply-To: References: Message-ID: <20120314085432.Horde.kZdXCs_2HjZPYFzIRg0lOpA@bugs.horde.org> DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED. Ticket URL: http://bugs.horde.org/ticket/11076 ------------------------------------------------------------------------------ Ticket | 11076 Updated By | alexandra.simon at hotmail.com Summary | One Time Password Module Implementation - request for | comment Queue | Horde Framework Packages Version | Git develop Type | Enhancement State | New Priority | 1. Low Milestone | Patch | 1 Owners | ------------------------------------------------------------------------------ c.denis at mrduck.fr (2012-03-14 08:53) wrote: Dear Dev-Team, as announced in #10980, I am trying to provide a first version of a hash-chain implementation for one time passwords. This is my personal reason why I would need the Dual_Auth module described previously. Nevertheless the modules are both fully functional on their own. With this otp module a user can log in to horde with another password every time and thus protect his credentials if he has to log in from an untrusted location such as an airport internet terminal. ATM this uses the same table as Auth_Sql (horde_users) with two additional fields. If requested this can of course be changed to use its own table. ALTER TABLE `horde_users` ADD `hash_chain_pwd` VARCHAR( 60 ) NOT NULL ALTER TABLE `horde_users` ADD `hash_chain_index` INT( 50 ) NOT NULL I am posting this at this state mainly to get feedback on the idea and the implementation. I am by all means willing to improve it from a security, architectural, or even style point of view. Further additions in terms of support in the passwd application, warnings when the password list runs empty and integration in the configuration page are planned if this is of common interest. Any comment is appreciated. Best regards, Carl c.denis at mrduck.fr (2012-03-14 08:53) uploaded: otp.patch http://bugs.horde.org/h/services/download/?module=whups&actionID=download_file&file=otp.patch&ticket=11076&fn=%2Fotp.patch From bugs at horde.org Wed Mar 14 12:09:13 2012 From: bugs at horde.org (bugs at horde.org) Date: Wed, 14 Mar 2012 12:09:13 +0000 Subject: [Tickets #11053] Re: Problems replying/forwarding messages with attachments on pop-ups In-Reply-To: References: Message-ID: <20120314120915.Horde.360NEM_2HjZPYIprf3FGmCA@dev.horde.org> DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED. Ticket URL: http://bugs.horde.org/ticket/11053 ------------------------------------------------------------------------------ Ticket | 11053 Updated By | Git Commit Summary | Problems replying/forwarding messages with attachments | on pop-ups Queue | IMP Version | Git master Type | Bug State | Resolved Priority | 1. Low Milestone | Patch | Owners | Michael Slusarz ------------------------------------------------------------------------------ Git Commit (2012-03-14 12:09) wrote: Changes have been made in Git (develop): commit c05da3d7fef551ac8dd73d41f48aa507f988982e Author: Michael M Slusarz Date: Wed Mar 14 00:12:05 2012 -0600 Bug #11053: Clear attachment list if message send was successful. imp/js/compose-dimp.js | 5 +++++ 1 files changed, 5 insertions(+), 0 deletions(-) http://git.horde.org/horde-git/-/commit/c05da3d7fef551ac8dd73d41f48aa507f988982e From bugs at horde.org Wed Mar 14 14:58:16 2012 From: bugs at horde.org (bugs at horde.org) Date: Wed, 14 Mar 2012 14:58:16 +0000 Subject: [Tickets #11045] Re: Listshares cache is not beeing used when previous result is an empty array In-Reply-To: References: Message-ID: <20120314145820.Horde.r2l2Cc_2HjZPYLIMJXIQfYA@bugs.horde.org> DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED. Ticket URL: http://bugs.horde.org/ticket/11045 ------------------------------------------------------------------------------ Ticket | 11045 Updated By | goncalo.queiros at portugalmail.net Summary | Listshares cache is not beeing used when previous | result is an empty array Queue | Horde Framework Packages Version | Git master Type | Bug State | Resolved Priority | 1. Low Milestone | Patch | 1 Owners | Michael Rubinsky ------------------------------------------------------------------------------ goncalo.queiros at portugalmail.net (2012-03-14 14:58) wrote: List shares is now caching a false value if $sharelist is empty. $this->_listcache[$key] = empty($sharelist) ? false : $sharelist; The problem is that on the first run the method will return false, but on the second run, because of: return is_array($this->_listcache[$key]) ? $this->_listcache[$key] : array(); it will return an empty array. Shouldn't it always return an empty array? From bugs at horde.org Wed Mar 14 15:14:00 2012 From: bugs at horde.org (bugs at horde.org) Date: Wed, 14 Mar 2012 16:14:00 +0100 Subject: [Tickets #11045] Re: Listshares cache is not beeing used when previous result is an empty array In-Reply-To: References: Message-ID: <20120314161403.Horde.zv7NO8_2HjZPYLW7aoJQhaA@bugs.horde.org> DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED. Ticket URL: http://bugs.horde.org/ticket/11045 ------------------------------------------------------------------------------ Ticket | 11045 Updated By | Jan Schneider Summary | Listshares cache is not beeing used when previous | result is an empty array Queue | Horde Framework Packages Version | Git master Type | Bug State | Resolved Priority | 1. Low Milestone | Patch | 1 Owners | Michael Rubinsky ------------------------------------------------------------------------------ Jan Schneider (2012-03-14 16:14) wrote: This has been fixed already. From bugs at horde.org Wed Mar 14 17:05:52 2012 From: bugs at horde.org (bugs at horde.org) Date: Wed, 14 Mar 2012 17:05:52 +0000 Subject: [Tickets #11045] Re: Listshares cache is not beeing used when previous result is an empty array In-Reply-To: References: Message-ID: <20120314170557.Horde.GqriXs_2HjZPYM-1CU6Qm8A@bugs.horde.org> DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED. Ticket URL: http://bugs.horde.org/ticket/11045 ------------------------------------------------------------------------------ Ticket | 11045 Updated By | goncalo.queiros at portugalmail.net Summary | Listshares cache is not beeing used when previous | result is an empty array Queue | Horde Framework Packages Version | Git master Type | Bug State | Resolved Priority | 1. Low Milestone | Patch | 1 Owners | Michael Rubinsky ------------------------------------------------------------------------------ goncalo.queiros at portugalmail.net (2012-03-14 17:05) wrote: Sorry forgot to check the develop branch > This has been fixed already. From bugs at horde.org Wed Mar 14 17:06:01 2012 From: bugs at horde.org (bugs at horde.org) Date: Wed, 14 Mar 2012 17:06:01 +0000 Subject: [Tickets #11077] S/MIME does not correctly sign non-ascii text Message-ID: DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED. Ticket URL: http://bugs.horde.org/ticket/11077 ------------------------------------------------------------------------------ Ticket | 11077 Created By | mm at FreeBSD.org Summary | S/MIME does not correctly sign non-ascii text Queue | IMP Version | 5.0.19 Type | Bug State | Unconfirmed Priority | 2. Medium Milestone | Patch | Owners | ------------------------------------------------------------------------------ mm at FreeBSD.org (2012-03-14 17:06) wrote: If I compose a message containing non-ascii characters (e.g. german Umlauts - ???) the produce S/MIME signature is not valid. From bugs at horde.org Wed Mar 14 18:02:12 2012 From: bugs at horde.org (bugs at horde.org) Date: Wed, 14 Mar 2012 18:02:12 +0000 Subject: [Tickets #11043] Re: Clear filter do not work 100% In-Reply-To: References: Message-ID: <20120314180224.Horde.dIxuVc_2HjZPYN0wXjFAsxA@dev.horde.org> DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED. Ticket URL: http://bugs.horde.org/ticket/11043 ------------------------------------------------------------------------------ Ticket | 11043 Updated By | Git Commit Summary | Clear filter do not work 100% Queue | Gollem Version | 2.0.1 Type | Bug State | Unconfirmed Priority | 1. Low Milestone | Patch | Owners | ------------------------------------------------------------------------------ Git Commit (2012-03-14 18:02) wrote: Changes have been made in Git (master): commit 690e83f3e90f05d7b4d6e4c7f0ad04f471950b64 Author: Jan Schneider Date: Wed Mar 14 19:01:06 2012 +0100 [jan] Fix removing filter (Bug #11043). gollem/docs/CHANGES | 1 + gollem/manager.php | 22 ++++++++++++---------- gollem/package.xml | 2 ++ 3 files changed, 15 insertions(+), 10 deletions(-) http://git.horde.org/horde-git/-/commit/690e83f3e90f05d7b4d6e4c7f0ad04f471950b64 From bugs at horde.org Wed Mar 14 18:02:26 2012 From: bugs at horde.org (bugs at horde.org) Date: Wed, 14 Mar 2012 19:02:26 +0100 Subject: [Tickets #11043] Re: Clear filter do not work 100% In-Reply-To: References: Message-ID: <20120314190227.Horde.7SxzFc_2HjZPYN0zWGvAs3A@bugs.horde.org> DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED. Ticket URL: http://bugs.horde.org/ticket/11043 ------------------------------------------------------------------------------ Ticket | 11043 Updated By | Jan Schneider Summary | Clear filter do not work 100% Queue | Gollem Version | 2.0.1 Type | Bug -State | Unconfirmed +State | Resolved Priority | 1. Low Milestone | Patch | -Owners | +Owners | Jan Schneider ------------------------------------------------------------------------------ From bugs at horde.org Wed Mar 14 18:39:24 2012 From: bugs at horde.org (bugs at horde.org) Date: Wed, 14 Mar 2012 18:39:24 +0000 Subject: [Tickets #11078] Change the default value for 'mailbox_start' preference Message-ID: DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED. Ticket URL: http://bugs.horde.org/ticket/11078 ------------------------------------------------------------------------------ Ticket | 11078 Created By | vilius at lnk.lt Summary | Change the default value for 'mailbox_start' preference Queue | IMP Version | Git master Type | Enhancement State | New Priority | 1. Low Milestone | Patch | 1 Owners | ------------------------------------------------------------------------------ vilius at lnk.lt (2012-03-14 18:39) wrote: Now that IMP defaults to dynamic view there is more sense to show first page instead of first unseen message. Because the other way around user is almost always presented with one unseen message on mailbox start even if he has more unread messages. I found that this can be confusing at least. Patch attached. vilius at lnk.lt (2012-03-14 18:39) uploaded: 0001-Change-the-default-value-for-mailbox_start-preferenc.patch http://bugs.horde.org/h/services/download/?module=whups&actionID=download_file&file=0001-Change-the-default-value-for-mailbox_start-preferenc.patch&ticket=11078&fn=%2F0001-Change-the-default-value-for-mailbox_start-preferenc.patch From bugs at horde.org Wed Mar 14 19:14:21 2012 From: bugs at horde.org (bugs at horde.org) Date: Wed, 14 Mar 2012 19:14:21 +0000 Subject: [Tickets #11043] Re: Clear filter do not work 100% In-Reply-To: References: Message-ID: <20120314191424.Horde.6mjZQs_2HjZPYO4QfohQe3A@dev.horde.org> DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED. Ticket URL: http://bugs.horde.org/ticket/11043 ------------------------------------------------------------------------------ Ticket | 11043 Updated By | Git Commit Summary | Clear filter do not work 100% Queue | Gollem Version | 2.0.1 Type | Bug State | Resolved Priority | 1. Low Milestone | Patch | Owners | Jan Schneider ------------------------------------------------------------------------------ Git Commit (2012-03-14 19:14) wrote: Changes have been made in Git (develop): commit 690e83f3e90f05d7b4d6e4c7f0ad04f471950b64 Author: Jan Schneider Date: Wed Mar 14 19:01:06 2012 +0100 [jan] Fix removing filter (Bug #11043). gollem/docs/CHANGES | 1 + gollem/manager.php | 22 ++++++++++++---------- gollem/package.xml | 2 ++ 3 files changed, 15 insertions(+), 10 deletions(-) http://git.horde.org/horde-git/-/commit/690e83f3e90f05d7b4d6e4c7f0ad04f471950b64 From bugs at horde.org Thu Mar 15 10:06:31 2012 From: bugs at horde.org (bugs at horde.org) Date: Thu, 15 Mar 2012 10:06:31 +0000 Subject: [Tickets #11058] Re: S/MIME signed messages cannot be verified if body contains 8-bit characters In-Reply-To: References: Message-ID: <20120315100634.Horde.3cyNSs_2HjZPYb8qPvFzxIA@bugs.horde.org> DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED. Ticket URL: http://bugs.horde.org/ticket/11058 ------------------------------------------------------------------------------ Ticket | 11058 Updated By | mm at FreeBSD.org Summary | S/MIME signed messages cannot be verified if body | contains 8-bit characters Queue | IMP Version | 5.0.19 Type | Bug State | Unconfirmed Priority | 2. Medium Milestone | Patch | Owners | ------------------------------------------------------------------------------ mm at FreeBSD.org (2012-03-15 10:06) wrote: The problem is not in postfix but in Horde/Mime/Part.php, function send(), starting on line 1669. There is code that detects if MTA supports 8BITMIME (RFC 1652) or BINARYMIME (RFC 3030) extensions and re-encodes the mimePart. A S/MIME part cannot be reencoded from quoted-printable to anything else because it breaks the signature. One of possible solutions would be to extend the send function by giving it a new boolean parameter to use only 7bit encoding (quoted-printable) for S/MIME signed messages and set this parameter on sign time. From bugs at horde.org Thu Mar 15 10:23:15 2012 From: bugs at horde.org (bugs at horde.org) Date: Thu, 15 Mar 2012 10:23:15 +0000 Subject: [Tickets #11079] dynamic view problem Message-ID: DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED. Ticket URL: http://bugs.horde.org/ticket/11079 ------------------------------------------------------------------------------ Ticket | 11079 Created By | thierry.voyat at ac-amiens.fr Summary | dynamic view problem Queue | Kronolith Version | 3.0.15 Type | Bug State | Unconfirmed Priority | 2. Medium Milestone | Patch | 1 Owners | ------------------------------------------------------------------------------ thierry.voyat at ac-amiens.fr (2012-03-15 10:23) wrote: The dynamic view for agenda hangs with this error on my apache server : PHP Fatal error: Call to a member function api() on a non-object in ... horde/kronolit h/templates/index/index.inc on line 142 On line 142 of kronolith/templates/index/index.inc, you use "$c->api()" but $c is not an object but an array of one object element. This bug seems to be introduced from kronolith-3.0.13 Patch attached Thanks From bugs at horde.org Thu Mar 15 10:25:54 2012 From: bugs at horde.org (bugs at horde.org) Date: Thu, 15 Mar 2012 10:25:54 +0000 Subject: [Tickets #11079] Re: dynamic view problem In-Reply-To: References: Message-ID: <20120315102556.Horde.ay7VYM_2HjZPYcO0F_2zw5A@bugs.horde.org> DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED. Ticket URL: http://bugs.horde.org/ticket/11079 ------------------------------------------------------------------------------ Ticket | 11079 Updated By | thierry.voyat at ac-amiens.fr Summary | dynamic view problem Queue | Kronolith Version | 3.0.15 Type | Bug State | Unconfirmed Priority | 2. Medium Milestone | Patch | 1 Owners | +New Attachment | kronolith_capi.patch ------------------------------------------------------------------------------ thierry.voyat at ac-amiens.fr (2012-03-15 10:25) wrote: The patch thierry.voyat at ac-amiens.fr (2012-03-15 10:25) uploaded: kronolith_capi.patch http://bugs.horde.org/h/services/download/?module=whups&actionID=download_file&file=kronolith_capi.patch&ticket=11079&fn=%2Fkronolith_capi.patch From bugs at horde.org Thu Mar 15 18:10:12 2012 From: bugs at horde.org (bugs at horde.org) Date: Thu, 15 Mar 2012 18:10:12 +0000 Subject: [Tickets #11080] Horde Admin FAQ bug? Message-ID: DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED. Ticket URL: http://bugs.horde.org/ticket/11080 ------------------------------------------------------------------------------ Ticket | 11080 Created By | pas at unh.edu Summary | Horde Admin FAQ bug? Queue | Horde.org Servers Version | Web Server Type | Bug State | Unconfirmed Priority | 1. Low Milestone | Patch | Owners | ------------------------------------------------------------------------------ pas at unh.edu (2012-03-15 18:10) wrote: http://wiki.horde.org/FAQ/Admin/Config contains a suggested: $this->applications['horde']['name'] => _("Whatever"); for registry.local.php in the Horde config directory. This gives me a syntax error. Changing the '=>' to '='. seems to work better. From bugs at horde.org Thu Mar 15 19:17:23 2012 From: bugs at horde.org (bugs at horde.org) Date: Thu, 15 Mar 2012 20:17:23 +0100 Subject: [Tickets #11080] Re: Horde Admin FAQ bug? In-Reply-To: References: Message-ID: <20120315201729.Horde.7fBRBc_2HjZPYkBJ1FwkVoA@bugs.horde.org> DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED. Ticket URL: http://bugs.horde.org/ticket/11080 ------------------------------------------------------------------------------ Ticket | 11080 Updated By | Ralf Lang (B1 Systems GmbH) Summary | Horde Admin FAQ bug? Queue | Horde.org Servers Version | Web Server Type | Bug -State | Unconfirmed +State | Resolved Priority | 1. Low Milestone | Patch | Owners | ------------------------------------------------------------------------------ Ralf Lang (B1 Systems GmbH) (2012-03-15 20:17) wrote: Thank you. Fixed. From bugs at horde.org Thu Mar 15 19:22:31 2012 From: bugs at horde.org (bugs at horde.org) Date: Thu, 15 Mar 2012 20:22:31 +0100 Subject: [Tickets #10880] Re: Rdo: Make *- to-one-relations aware of "no relation" state In-Reply-To: References: Message-ID: <20120315202232.Horde.isxSPc_2HjZPYkF4eoOkRXA@bugs.horde.org> DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED. Ticket URL: http://bugs.horde.org/ticket/10880 ------------------------------------------------------------------------------ Ticket | 10880 Updated By | Ralf Lang (B1 Systems GmbH) Summary | Rdo: Make *- to-one-relations aware of "no relation" | state Queue | Horde Framework Packages Version | Git master Type | Enhancement State | Feedback Priority | 1. Low Milestone | Patch | -Owners | +Owners | Ralf Lang (B1 Systems GmbH) ------------------------------------------------------------------------------ From bugs at horde.org Fri Mar 16 17:11:32 2012 From: bugs at horde.org (bugs at horde.org) Date: Fri, 16 Mar 2012 17:11:32 +0000 Subject: [Tickets #11070] Re: event display on 25.03.2012 is off by one hour In-Reply-To: References: Message-ID: <20120316171139.Horde.IuhfJM_2HjZPY3RL3mpRKiA@dev.horde.org> DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED. Ticket URL: http://bugs.horde.org/ticket/11070 ------------------------------------------------------------------------------ Ticket | 11070 Updated By | Git Commit Summary | event display on 25.03.2012 is off by one hour Queue | Kronolith Version | 3.0.15 Type | Bug State | Unconfirmed Priority | 1. Low Milestone | Patch | Owners | ------------------------------------------------------------------------------ Git Commit (2012-03-16 17:11) wrote: Changes have been made in Git (master): commit b0a084157222e7b228bbdd22a2b057f3acf17d59 Author: Jan Schneider Date: Fri Mar 16 18:10:59 2012 +0100 [jan] Fix positioning of events on DST changing dates (Bug #11070). kronolith/docs/CHANGES | 1 + kronolith/js/kronolith.js | 3 ++- kronolith/package.xml | 2 ++ 3 files changed, 5 insertions(+), 1 deletions(-) http://git.horde.org/horde-git/-/commit/b0a084157222e7b228bbdd22a2b057f3acf17d59 From bugs at horde.org Fri Mar 16 17:13:09 2012 From: bugs at horde.org (bugs at horde.org) Date: Fri, 16 Mar 2012 18:13:09 +0100 Subject: [Tickets #11078] Re: Change the default value for 'mailbox_start' preference In-Reply-To: References: Message-ID: <20120316181312.Horde.MVrWfM_2HjZPY3Sok4NhKQA@bugs.horde.org> DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED. Ticket URL: http://bugs.horde.org/ticket/11078 ------------------------------------------------------------------------------ Ticket | 11078 Updated By | Jan Schneider Summary | Change the default value for 'mailbox_start' preference Queue | IMP Version | Git master Type | Enhancement -State | New +State | Feedback Priority | 1. Low Milestone | Patch | 1 Owners | ------------------------------------------------------------------------------ Jan Schneider (2012-03-16 18:13) wrote: I fail to see why this makes a difference whether we are on the dynamic or traditional view. From bugs at horde.org Fri Mar 16 17:14:34 2012 From: bugs at horde.org (bugs at horde.org) Date: Fri, 16 Mar 2012 18:14:34 +0100 Subject: [Tickets #11070] Re: event display on 25.03.2012 is off by one hour In-Reply-To: References: Message-ID: <20120316181435.Horde.qY_PC8_2HjZPY3T7tSRBNRA@bugs.horde.org> DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED. Ticket URL: http://bugs.horde.org/ticket/11070 ------------------------------------------------------------------------------ Ticket | 11070 Updated By | Jan Schneider Summary | event display on 25.03.2012 is off by one hour Queue | Kronolith Version | 3.0.15 Type | Bug -State | Unconfirmed +State | Resolved Priority | 1. Low -Milestone | +Milestone | 3.0.16 Patch | -Owners | +Owners | Jan Schneider ------------------------------------------------------------------------------ Jan Schneider (2012-03-16 18:14) wrote: We were calculating the top position based on the elapsed time since midnight, which doesn't work on days with DST switching. From bugs at horde.org Fri Mar 16 17:47:22 2012 From: bugs at horde.org (bugs at horde.org) Date: Fri, 16 Mar 2012 17:47:22 +0000 Subject: [Tickets #11078] Re: Change the default value for 'mailbox_start' preference In-Reply-To: References: Message-ID: <20120316174724.Horde.fIkLd8_2HjZPY3ysPVQhPqA@bugs.horde.org> DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED. Ticket URL: http://bugs.horde.org/ticket/11078 ------------------------------------------------------------------------------ Ticket | 11078 Updated By | vilius at lnk.lt Summary | Change the default value for 'mailbox_start' preference Queue | IMP Version | Git master Type | Enhancement State | Feedback Priority | 1. Low Milestone | Patch | 1 Owners | +New Attachment | confusing.png ------------------------------------------------------------------------------ vilius at lnk.lt (2012-03-16 17:47) wrote: 1. Attaching a screenshot. As you can see, even if I have 2 or more unread messages I'm always presented only with one unread message on the start. And user doesn't have any indication where other unread messages are, because in most such cases scrollbar scale is too small. 2. This setting was useful in traditional mode because it helped to find a particular page with unread messages. This is irrelevant now as there are no more pages. 3. This brings IMP inline with other email clients. E.i. newest messages are always on top Gmail style. vilius at lnk.lt (2012-03-16 17:47) uploaded: confusing.png http://bugs.horde.org/h/services/download/?module=whups&actionID=download_file&file=confusing.png&ticket=11078&fn=%2Fconfusing.png From bugs at horde.org Fri Mar 16 18:44:42 2012 From: bugs at horde.org (bugs at horde.org) Date: Fri, 16 Mar 2012 19:44:42 +0100 Subject: [Tickets #11078] Re: Change the default value for 'mailbox_start' preference In-Reply-To: References: Message-ID: <20120316194445.Horde.cstOC8_2HjZPY4odtHDhQxA@bugs.horde.org> DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED. Ticket URL: http://bugs.horde.org/ticket/11078 ------------------------------------------------------------------------------ Ticket | 11078 Updated By | Jan Schneider Summary | Change the default value for 'mailbox_start' preference Queue | IMP Version | Git master Type | Enhancement State | Feedback Priority | 1. Low Milestone | Patch | 1 Owners | ------------------------------------------------------------------------------ Jan Schneider (2012-03-16 19:44) wrote: We should instead tweak the positioning then to jump so that the newest unread message is at the bottom. Chances are better to have more than this unread message in the current view then. That being said, I won't mind defaulting to the first page in the prefs, I've been using that setting since 12 years anyway. :) From bugs at horde.org Sat Mar 17 02:49:21 2012 From: bugs at horde.org (bugs at horde.org) Date: Sat, 17 Mar 2012 02:49:21 +0000 Subject: [Tickets #11070] Re: event display on 25.03.2012 is off by one hour In-Reply-To: References: Message-ID: <20120317024926.Horde.VYe_LM_2HjZPY-u2qYnRquA@dev.horde.org> DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED. Ticket URL: http://bugs.horde.org/ticket/11070 ------------------------------------------------------------------------------ Ticket | 11070 Updated By | Git Commit Summary | event display on 25.03.2012 is off by one hour Queue | Kronolith Version | 3.0.15 Type | Bug State | Resolved Priority | 1. Low Milestone | 3.0.16 Patch | Owners | Jan Schneider ------------------------------------------------------------------------------ Git Commit (2012-03-17 02:49) wrote: Changes have been made in Git (develop): commit b0a084157222e7b228bbdd22a2b057f3acf17d59 Author: Jan Schneider Date: Fri Mar 16 18:10:59 2012 +0100 [jan] Fix positioning of events on DST changing dates (Bug #11070). kronolith/docs/CHANGES | 1 + kronolith/js/kronolith.js | 3 ++- kronolith/package.xml | 2 ++ 3 files changed, 5 insertions(+), 1 deletions(-) http://git.horde.org/horde-git/-/commit/b0a084157222e7b228bbdd22a2b057f3acf17d59 From bugs at horde.org Sat Mar 17 11:47:05 2012 From: bugs at horde.org (bugs at horde.org) Date: Sat, 17 Mar 2012 11:47:05 +0000 Subject: [Tickets #11081] Sent mail has the body misplaced in the headers Message-ID: DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED. Ticket URL: http://bugs.horde.org/ticket/11081 ------------------------------------------------------------------------------ Ticket | 11081 Created By | ben at bristolwireless.net Summary | Sent mail has the body misplaced in the headers Queue | Horde Framework Packages Version | Git master Type | Bug State | Unconfirmed Priority | 2. Medium Milestone | Patch | Owners | ------------------------------------------------------------------------------ ben at bristolwireless.net (2012-03-17 11:47) wrote: Here the headers of a mail sent when using Horde_Mail 1.1.0, the result is the same when using 1.0.3. Naturally the mail is unreadable by any mail clients with this format, the body appearing somewhere in the headers. Downgrading to Horde_Mail 1.0.2 fixes the problem and mail can be sent in the correct way again. Any debugging strategies I could use to find out what's wrong with this would be gratefully used. Domain names have been changed to protect the innocent: Return-path: Envelope-to: bengreen at localhost Delivery-date: Sat, 17 Mar 2012 11:08:55 +0000 Received: from localhost ([127.0.0.1]) by received.co.uk with esmtp (Exim 4.72) (envelope-from ) id 1S8rVH-0000Ds-Pr for bengreen at localhost; Sat, 17 Mar 2012 11:08:55 +0000 X-Quarantine-ID: X-Virus-Scanned: Debian amavisd-new at otherexample.net X-Amavis-Alert: BAD HEADER SECTION, Improper folded header field made up entirely of whitespace (char 20 hex): Received: ...tent-Disposition: inline\n \n yes, a fart\n [...] X-Spam-Flag: NO X-Spam-Score: -4.914 X-Spam-Level: X-Spam-Status: No, score=-4.914 tagged_above=-999 required=4 tests=[AM:BOOST=-7, AWL=-1.155, BAYES_00=-1.9, EMPTY_MESSAGE=2.32, MISSING_HEADERS=1.021, MISSING_SUBJECT=1.799, MSGID_FROM_MTA_HEADER=0.001] autolearn=no Received: from received.co.uk ([127.0.0.1]) by localhost (received.co.uk [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fhs4Dp2rTM5r for ; Sat, 17 Mar 2012 11:08:55 +0000 (GMT) Received: from mailserv.psand.net ([194.164.97.5]) by received.co.uk with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.72) (envelope-from ) id 1S8rVG-0000Dn-Vv for bengreen at otherexample.net; Sat, 17 Mar 2012 11:08:54 +0000 Received: from www-data by mailserv.psand.net with local (Exim 4.72) (envelope-from ) id 1S8rVG-0003c6-0x for bengreen at otherexample.net; Sat, 17 Mar 2012 11:08:54 +0000 Date: Sat, 17 Mar 2012 11:08:54 +0000 Message-Id: Received: from cpc10-aztw24-2-0-cust114.aztw.cable.virginmedia.com (cpc10-aztw24-2-0-cust114.aztw.cable.virginmedia.com [82.45.35.115]) by slackmail.co.uk (Horde Framework) with HTTP; Sat, 17 Mar 2012 11:08:53 +0000 Date: Sat, 17 Mar 2012 11:08:53 +0000 Message-ID: <20120317110853.Horde.bhzyWWOelG9PZHDF8uVRJ7A at slackmail.co.uk> From: Ben Green To: "bengreen at otherexample.net" Subject: this is the subject of the message User-Agent: Internet Messaging Program (IMP) H4 (5.0.19) Content-Type: text/plain; charset=ISO-8859-1; format=flowed; DelSp=Yes MIME-Version: 1.0 Content-Disposition: inline This is the body of the message, and my signature. == From Ben Green From: www-data From bugs at horde.org Sat Mar 17 11:52:51 2012 From: bugs at horde.org (bugs at horde.org) Date: Sat, 17 Mar 2012 11:52:51 +0000 Subject: [Tickets #11082] avoiding lots of empty ldap connections Message-ID: DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED. Ticket URL: http://bugs.horde.org/ticket/11082 ------------------------------------------------------------------------------ Ticket | 11082 Created By | dom.lalot at gmail.com Summary | avoiding lots of empty ldap connections Queue | Turba Version | Git master Type | Enhancement State | New Priority | 1. Low Milestone | Patch | 1 Owners | ------------------------------------------------------------------------------ dom.lalot at gmail.com (2012-03-17 11:52) wrote: Hello, The construct method of the ldap driver is doing a connect/bind. Most of the time there is no search and there is an unbind after. I propose to add an init method which is called if _ds==null in order to use just connects when searching or writing information. Dom dom.lalot at gmail.com (2012-03-17 11:52) uploaded: patchTurba.txt http://bugs.horde.org/h/services/download/?module=whups&actionID=download_file&file=patchTurba.txt&ticket=11082&fn=%2FpatchTurba.txt From bugs at horde.org Sat Mar 17 15:14:14 2012 From: bugs at horde.org (bugs at horde.org) Date: Sat, 17 Mar 2012 15:14:14 +0000 Subject: [Tickets #11083] Activesync showing only 6 contacts out of 400+ Message-ID: DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED. Ticket URL: http://bugs.horde.org/ticket/11083 ------------------------------------------------------------------------------ Ticket | 11083 Created By | horde at kyoshiro.org Summary | Activesync showing only 6 contacts out of 400+ Queue | Turba Version | 3.0.12 Type | Bug State | Unconfirmed Priority | 2. Medium Milestone | Patch | Owners | ------------------------------------------------------------------------------ horde at kyoshiro.org (2012-03-17 15:14) wrote: Hi, I've been struggling for a few weeks now, trying to make contacts synchronization work via activesync on my Android phone (xPeria X10), without success. It seems to be able to synchronize 6 (random) contacts but no more. To be more precise, I'm using an LDAP as container for a personal adressbook. I've setup turba to map : '__key' => 'dn', '__uid' => 'cn', Entries look like this in my LDAP : dn: cn=blah blah,ou=addressbook,cn=kyoshiro,ou=users,dc=kyoshiro,dc =org objectClass: top objectClass: person objectClass: organizationalPerson objectClass: inetOrgPerson givenName: blah sn: blah cn: blah blah mail: ... I had an issue in the dedicated log file for my device saying : 2012-03-17T13:29:38+01:00 ERR: Internal Horde Error: multiple turba objects with same objectId. 2012-03-17T13:29:38+01:00 DEBUG: [androidc1376193414] Saving state: Array ( [0] => {4f625e28-fca4-44da-9d51-40e958be147c}788 [1] => a:494:{i:0;a:3:{s:2:"id";s:12:"Some Friend";s:4:"type";s:6:"change";s:5:"flags";s:10:"NewMessage";}i:1;... [2] => androidc1376193414 [3] => 1331987377 [4] => Contacts [5] => kyoshiro ) I upgraded to the latest PEAR version and the serialize and ERR line seem not to appear in the logfiles anymore, but there's still only 6 contacts on my phone. I've attached the current log of what happens when I ask my device to resync contacts. Please let me know if you need more data on this issue. Thanks ! Regards horde at kyoshiro.org (2012-03-17 15:14) uploaded: androidc1376193414.txt http://bugs.horde.org/h/services/download/?module=whups&actionID=download_file&file=androidc1376193414.txt&ticket=11083&fn=%2Fandroidc1376193414.txt From bugs at horde.org Sat Mar 17 16:02:36 2012 From: bugs at horde.org (bugs at horde.org) Date: Sat, 17 Mar 2012 16:02:36 +0000 Subject: [Tickets #11083] Re: Activesync showing only 6 contacts out of 400+ In-Reply-To: References: Message-ID: <20120317160238.Horde.kxHiJc_2HjZPZLWeehnAc-A@bugs.horde.org> DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED. Ticket URL: http://bugs.horde.org/ticket/11083 ------------------------------------------------------------------------------ Ticket | 11083 Updated By | Michael Rubinsky Summary | Activesync showing only 6 contacts out of 400+ Queue | Turba Version | 3.0.12 Type | Bug -State | Unconfirmed +State | Not A Bug Priority | 2. Medium Milestone | Patch | -Owners | +Owners | Michael Rubinsky ------------------------------------------------------------------------------ Michael Rubinsky (2012-03-17 16:02) wrote: The UID value MUST be a globally unique identifier. The error is telling you that more than one entry in your datastore has the same UID value. From bugs at horde.org Sat Mar 17 16:30:25 2012 From: bugs at horde.org (bugs at horde.org) Date: Sat, 17 Mar 2012 16:30:25 +0000 Subject: [Tickets #11083] Re: Activesync showing only 6 contacts out of 400+ In-Reply-To: References: Message-ID: <20120317163028.Horde.xQzORc_2HjZPZLwkJkYAeoA@bugs.horde.org> DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED. Ticket URL: http://bugs.horde.org/ticket/11083 ------------------------------------------------------------------------------ Ticket | 11083 Updated By | horde at kyoshiro.org Summary | Activesync showing only 6 contacts out of 400+ Queue | Turba Version | 3.0.12 Type | Bug State | Not A Bug Priority | 2. Medium Milestone | Patch | Owners | Michael Rubinsky ------------------------------------------------------------------------------ horde at kyoshiro.org (2012-03-17 16:30) wrote: > The UID value MUST be a globally unique identifier. The error is > telling you that more than one entry in your datastore has the same > UID value. Yes, but it is a unique identifier : ~$ grep 'cn:' slapcat.ldif > cn.list ~$ grep 'cn:' slapcat.ldif |sort -u > cn2.list ~$ wc -l cn* 524 cn2.list 524 cn.list Plus, at the moment I don't have this error in my log anymore, so I don't understand why it's not syncing :/ LDAP is great for handling accounts and providing detailed information about each user. And in this case using "uid" as a globally unique identifier is easy. But in my case, I'm using LDAP as a storage for a personal LDAP, so these entries don't have any uid since they're not real users. I decided to use "cn" as identifier, and even if someday something could lead to a non unique issue, it's not the case at the moment. I'm a bit lost, I don't really understand why - even now this issue is gone - sync is only working for a few contacts. You can see the log I attached in my previous post for more information. Thanks From bugs at horde.org Sat Mar 17 16:58:03 2012 From: bugs at horde.org (bugs at horde.org) Date: Sat, 17 Mar 2012 17:58:03 +0100 Subject: [Tickets #11081] Re: Sent mail has the body misplaced in the headers In-Reply-To: References: Message-ID: <20120317175806.Horde.K2vNJs_2HjZPZMKeOA9QejA@bugs.horde.org> DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED. Ticket URL: http://bugs.horde.org/ticket/11081 ------------------------------------------------------------------------------ Ticket | 11081 Updated By | Jan Schneider Summary | Sent mail has the body misplaced in the headers Queue | Horde Framework Packages Version | Git master Type | Bug -State | Unconfirmed +State | Not A Bug Priority | 2. Medium Milestone | Patch | Owners | ------------------------------------------------------------------------------ Jan Schneider (2012-03-17 17:58) wrote: Use SMTP not Sendmail From bugs at horde.org Sat Mar 17 16:58:42 2012 From: bugs at horde.org (bugs at horde.org) Date: Sat, 17 Mar 2012 16:58:42 +0000 Subject: [Tickets #11083] Re: Activesync showing only 6 contacts out of 400+ In-Reply-To: References: Message-ID: <20120317165843.Horde.PsliOc_2HjZPZMLD01UheXA@bugs.horde.org> DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED. Ticket URL: http://bugs.horde.org/ticket/11083 ------------------------------------------------------------------------------ Ticket | 11083 Updated By | Michael Rubinsky Summary | Activesync showing only 6 contacts out of 400+ Queue | Turba Version | 3.0.12 Type | Bug State | Not A Bug Priority | 2. Medium Milestone | Patch | Owners | Michael Rubinsky ------------------------------------------------------------------------------ Michael Rubinsky (2012-03-17 16:58) wrote: >> The UID value MUST be a globally unique identifier. The error is >> telling you that more than one entry in your datastore has the same >> UID value. > > Yes, but it is a unique identifier : > ~$ grep 'cn:' slapcat.ldif > cn.list > ~$ grep 'cn:' slapcat.ldif |sort -u > cn2.list > ~$ wc -l cn* > 524 cn2.list > 524 cn.list Then you have to find out why Turba's search functions return more than one result for for the UID field see Turba_Api#export() in turba/lib/Api.php. > Plus, at the moment I don't have this error in my log anymore, so I > don't understand why it's not syncing :/ Because you already have done the initial SYNC. After the first SYNC, only changes reported by the history system are taken into account. You can clear the ActiveSync binding to your device from either the user ActiveSync prefs, or the device list in the administrative section. This will re-do the initial sync. From bugs at horde.org Sat Mar 17 19:56:06 2012 From: bugs at horde.org (bugs at horde.org) Date: Sat, 17 Mar 2012 19:56:06 +0000 Subject: [Tickets #11078] Re: Change the default value for 'mailbox_start' preference In-Reply-To: References: Message-ID: <20120317195608.Horde.8XwPQM_2HjZPZOxYWVF1uSA@bugs.horde.org> DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED. Ticket URL: http://bugs.horde.org/ticket/11078 ------------------------------------------------------------------------------ Ticket | 11078 Updated By | vilius at lnk.lt Summary | Change the default value for 'mailbox_start' preference Queue | IMP Version | Git master Type | Enhancement State | Feedback Priority | 1. Low Milestone | Patch | 1 Owners | ------------------------------------------------------------------------------ vilius at lnk.lt (2012-03-17 19:56) wrote: I think this deserves public opinion on IMP mailing list. I'll post it. And while at it I would like to propose changing sortdir as well. From bugs at horde.org Sat Mar 17 22:07:57 2012 From: bugs at horde.org (bugs at horde.org) Date: Sat, 17 Mar 2012 22:07:57 +0000 Subject: [Tickets #11084] in reply is no photo Message-ID: DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED. Ticket URL: http://bugs.horde.org/ticket/11084 ------------------------------------------------------------------------------ Ticket | 11084 Created By | bueno at balticom.lv Summary | in reply is no photo Queue | IMP Version | 4.3.6 Type | Bug State | Unconfirmed Priority | 1. Low Milestone | Patch | Owners | ------------------------------------------------------------------------------ bueno at balticom.lv (2012-03-17 22:07) wrote: The problem is that when I get the message with the attached pictures and try to answer it and the pictures are not shown, in what could be the problem? bueno at balticom.lv (2012-03-17 22:07) uploaded: imp.jpg http://bugs.horde.org/h/services/download/?module=whups&actionID=download_file&file=imp.jpg&ticket=11084&fn=%2Fimp.jpg From bugs at horde.org Sun Mar 18 17:39:40 2012 From: bugs at horde.org (bugs at horde.org) Date: Sun, 18 Mar 2012 17:39:40 +0000 Subject: [Tickets #11085] PGP Encrypted e-mails are only encrypted with the senders public key Message-ID: DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED. Ticket URL: http://bugs.horde.org/ticket/11085 ------------------------------------------------------------------------------ Ticket | 11085 Created By | peter.meier+horde at immerda.ch Summary | PGP Encrypted e-mails are only encrypted with the | senders public key Queue | IMP Version | Git master Type | Bug State | Unconfirmed Priority | 3. High Milestone | Patch | 1 Owners | ------------------------------------------------------------------------------ peter.meier+horde at immerda.ch (2012-03-18 17:39) wrote: https://github.com/duritong/horde/commit/060d02e78824a420235e23327c5883b0ee28fcf2 All e-mails that should be encrypted got only be encrypted with the senders public key. This happened, because $to wasn't an array of addresses but rather an array of AddressObjects, leading to the following warning, when sending an encrypted e-mail: WARN: HORDE [imp] PHP ERROR: array_flip() [function.array-flip]: Can only flip STRING and INTEGER values! [pid 1982 on line 1352 of "/var/www/vhosts/horde.example.com/www/imp/lib/Compose.php"] However, this also means that all the recipients are omitted and the e-mail is only encrypted with the senders public key. This patch converts the address objects to e-mail addresses before passing them to the PGP library. From bugs at horde.org Sun Mar 18 22:25:59 2012 From: bugs at horde.org (bugs at horde.org) Date: Sun, 18 Mar 2012 22:25:59 +0000 Subject: [Tickets #11086] SELECT without \r\n (complaint from imapproxy about imp) Message-ID: DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED. Ticket URL: http://bugs.horde.org/ticket/11086 ------------------------------------------------------------------------------ Ticket | 11086 Created By | dpa-bugs at aegee.org Summary | SELECT without \r\n (complaint from imapproxy about | imp) Queue | IMP Version | 5.0.19 Type | Bug State | Unconfirmed Priority | 1. Low Milestone | Patch | Owners | ------------------------------------------------------------------------------ dpa-bugs at aegee.org (2012-03-18 22:25) wrote: Horde/Imap/Client/Socket.php contains parseCommandArrayCallback ... $this->_sendLine($data, array( 'literaldata' => true, 'notag' => true )); ... and function _sendLine does ... if (is_resource($data)) { rewind($data); stream_copy_to_stream($data, $this->_stream); } else { fwrite($this->_stream, $out); // Line 3820 if (empty($options['literaldata'])) { fwrite($this->_stream, "\r\n"); } } if ($literalplus || !empty($options['literaldata'])) { return; } ... which might lead to a situation, where fwrite does not concatenate \r\n at the end of the send command. Or at least I see in the horde logs the message: 2012-03-18T23:12:10+01:00 NOTICE: HORDE [imp] PHP ERROR: fwrite() [function.fwrite]: send of 8 bytes failed with errno=32 Broken pipe [pid 26632 on line 3820 of "/usr/lib64/php/Horde/Imap/Client/Socket.php"] 2012-03-18T23:12:10+01:00 DEBUG: HORDE 1. require() /mnt/new/home/htdocs/webmail/imp/index.php:19 2. IMP_Imap->openMailbox() /mnt/new/home/htdocs/webmail/imp/mailbox.php:86 3. IMP_Imap->__call() /mnt/new/home/htdocs/webmail/imp/mailbox.php:86 4. call_user_func_array() /mnt/new/home/htdocs/webmail/imp/lib/Imap.php:343 5. Horde_Imap_Client_Base->openMailbox() 6. Horde_Imap_Client_Socket->_openMailbox() /usr/lib64/php/Horde/Imap/Client/Base.php:889 7. Horde_Imap_Client_Socket->_sendLine() /usr/lib64/php/Horde/Imap/Client/Socket.php:876 8. Horde_Imap_Client_Socket->_parseResponse() /usr/lib64/php/Horde/Imap/Client/Socket.php:3840 9. Horde_Imap_Client_Socket->_getLine() /usr/lib64/php/Horde/Imap/Client/Socket.php:4185 10. Horde_Imap_Client_Socket->_readData() /usr/lib64/php/Horde/Imap/Client/Socket.php:3913 11. Horde_Imap_Client_Base->logout() /usr/lib64/php/Horde/Imap/Client/Socket.php:4078 12. Horde_Imap_Client_Socket->_logout() /usr/lib64/php/Horde/Imap/Client/Base.php:717 13. Horde_Imap_Client_Socket->_sendLine() /usr/lib64/php/Horde/Imap/Client/Sock\et.php:665 14. fwrite() /usr/lib64/php/Horde/Imap/Client/Socket.php:3820 15. Horde::errorHandler() I use imapproxyd between IMP and cyrus imap, and in imapproxyd logs at the same time: Mar 18 22:12:09 AEGEEserv in.imapproxyd[25119]: LOGIN: 'headoffice' (127.0.0.1:54496) on new sd [9] Mar 18 22:12:10 AEGEEserv in.imapproxyd[25119]: LOGOUT: 'headoffice' from server sd [9] Mar 18 22:12:10 AEGEEserv in.imapproxyd[25119]: LOGIN: 'headoffice' (127.0.0.1:54498) on existing sd [9] Mar 18 22:12:10 AEGEEserv in.imapproxyd[25119]: Handle_Select_Command: Sanity check failed! SELECT command from client sd [8] has no CRLF after it. Mar 18 22:12:10 AEGEEserv in.imapproxyd[25119]: LOGOUT: 'headoffice' from server sd [9] Mar 18 22:12:10 AEGEEserv in.imapproxyd[25119]: LOGIN: 'headoffice' (127.0.0.1:54500) on existing sd [9] Mar 18 22:12:12 AEGEEserv in.imapproxyd[25119]: LOGOUT: 'headoffice' from server sd [9] Mar 18 22:12:13 AEGEEserv in.imapproxyd[25119]: LOGIN: 'headoffice' (127.0.0.1:54501) on existing sd [9] Mar 18 22:12:14 AEGEEserv in.imapproxyd[25119]: LOGOUT: 'headoffice' from server sd [9] Do you think this error message "Handle_Select_Command: Sanity check failed! SELECT command from client sd [8] has no CRLF after it." from imapproxyd is justified and imp sends wrong commands, or imapproxyd behaves incorrectly, and imp is right? From bugs at horde.org Sun Mar 18 22:41:53 2012 From: bugs at horde.org (bugs at horde.org) Date: Sun, 18 Mar 2012 23:41:53 +0100 Subject: [Tickets #11087] Infinite loop in Horde_Imap_Client_Cache Message-ID: DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED. Ticket URL: http://bugs.horde.org/ticket/11087 ------------------------------------------------------------------------------ Ticket | 11087 Created By | Jan Schneider Summary | Infinite loop in Horde_Imap_Client_Cache Queue | Horde Framework Packages Version | Git master Type | Bug State | Assigned Priority | 1. Low Milestone | Patch | Owners | Michael Slusarz ------------------------------------------------------------------------------ Jan Schneider (2012-03-18 23:41) wrote: 1 0,0252 679544 {main}( ) ../ajax.php:0 2 3,4903 44304168 IMP_Ajax_Application->doAction( ) ../ajax.php:60 3 3,4904 44304168 Horde_Core_Ajax_Application->doAction( ) ../Application.php:95 4 3,4904 44304800 call_user_func ( array (0 => class IMP_Ajax_Application { public $notify = TRUE; protected $_mbox = class IMP_Mailbox { public $cache = array (...); public $changed = 1; protected $_import = NULL; protected $_mbox = 'INBOX.horde.apps' }; protected $_queue = class IMP_Ajax_Queue { protected $_flag = array (...); protected $_poll = array (...); protected $_quota = FALSE }; protected $_suppress = NULL; protected $_readOnly = array (0 => 'html2Text', 1 => 'text2Html'); protected $_action = 'viewPort'; protected $_app = 'imp'; protected $_defaultDomain = NULL; protected $_vars = class Horde_Variables { protected $_expected = array (...); protected $_sanitized = FALSE; protected $_vars = array (...) } }, 1 => 'viewPort') ) ../Application.php:95 5 3,4904 44304800 IMP_Ajax_Application->viewPort( ) ../Application.php:95 6 3,9209 50200504 IMP_Ajax_Application->_viewPortData( TRUE, ??? ) ../Application.php:732 7 3,9505 50425656 IMP_Views_ListMessages->listMessages( array ('change' => TRUE, 'mbox' => 'INBOX.horde.apps', 'applyfilter' => NULL, 'cache' => NULL, 'cacheid' => NULL, 'delhide' => NULL, 'initial' => NULL, 'qsearch' => NULL, 'qsearchfield' => NULL, 'qsearchfilter' => NULL, 'qsearchflag' => NULL, 'qsearchflagnot' => NULL, 'qsearchmbox' => NULL, 'rangeslice' => NULL, 'requestid' => NULL, 'sortby' => NULL, 'sortdir' => NULL, 'slice_start' => 1, 'slice_end' => 131) ) ../Application.php:2000 8 4,1516 51269000 IMP_Views_ListMessages->_getOverviewData( class IMP_Mailbox { public $cache = array ('n' => array (0 => '.', 2 => 'INBOX.', 4 => 1), 'd' => 'horde.apps', 'ro' => FALSE, 'a' => 'lrswipakxte'); public $changed = 1; protected $_import = NULL; protected $_mbox = 'INBOX.horde.apps' }, array (0 => 1, 1 => 2, 2 => 3, 3 => 4, 4 => 5, 5 => 6, 6 => 7, 7 => 8, 8 => 9, 9 => 10, 10 => 11, 11 => 12, 12 => 13, 13 => 14, 14 => 15, 15 => 16, 16 => 17, 17 => 18, 18 => 19, 19 => 20, 20 => 21, 21 => 22, 22 => 23, 23 => 24, 24 => 25, 25 => 26, 26 => 27, 27 => 28, 28 => 29, 29 => 30, 30 => 31, 31 => 32, 32 => 33, 33 => 34, 34 => 35, 35 => 36, 36 => 37, 37 => 38, 38 => 39, 39 => 40, 40 => 41, 41 => 42, 42 => 43, 43 => 44, 44 => 45, 45 => 46, 46 => 47, 47 => 48, 48 => 49, 49 => 50, 50 => 51, 51 => 52, 52 => 53, 53 => 54, 54 => 55, 55 => 56, 56 => 57, 57 => 58, 58 => 59, 59 => 60, 60 => 61, 61 => 62, 62 => 63, 63 => 64, 64 => 65, 65 => 66, 66 => 67, 67 => 68, 68 => 69, 69 => 70, 70 => 71, 71 => 72, 72 => 73, 73 => 74, 74 => 75, 75 => 76, 76 => 77, 77 => 78, 78 => 79, 79 => 80, 80 => 81, 81 => 82, 82 => 83, 83 => 84, 84 => 85, 85 => 86, 86 => 87, 87 => 88, 88 => 89, 89 => 90, 90 => 91, 91 => 92, 92 => 93, 93 => 94, 94 => 95, 95 => 96, 96 => 97, 97 => 98, 98 => 99, 99 => 100, 100 => 101, 101 => 102, 102 => 103, 103 => 104, 104 => 105, 105 => 106, 106 => 107, 107 => 108, 108 => 109, 109 => 110, 110 => 111, 111 => 112, 112 => 113, 113 => 114, 114 => 115, 115 => 116, 116 => 117, 117 => 118, 118 => 119, 119 => 120, 120 => 121, 121 => 122, 122 => 123, 123 => 124, 124 => 125, 125 => 126, 126 => 127, 127 => 128, ...) ) ../ListMessages.php:391 9 4,1518 51270096 IMP_Mailbox_List->getMailboxArray( array (0 => 1, 1 => 2, 2 => 3, 3 => 4, 4 => 5, 5 => 6, 6 => 7, 7 => 8, 8 => 9, 9 => 10, 10 => 11, 11 => 12, 12 => 13, 13 => 14, 14 => 15, 15 => 16, 16 => 17, 17 => 18, 18 => 19, 19 => 20, 20 => 21, 21 => 22, 22 => 23, 23 => 24, 24 => 25, 25 => 26, 26 => 27, 27 => 28, 28 => 29, 29 => 30, 30 => 31, 31 => 32, 32 => 33, 33 => 34, 34 => 35, 35 => 36, 36 => 37, 37 => 38, 38 => 39, 39 => 40, 40 => 41, 41 => 42, 42 => 43, 43 => 44, 44 => 45, 45 => 46, 46 => 47, 47 => 48, 48 => 49, 49 => 50, 50 => 51, 51 => 52, 52 => 53, 53 => 54, 54 => 55, 55 => 56, 56 => 57, 57 => 58, 58 => 59, 59 => 60, 60 => 61, 61 => 62, 62 => 63, 63 => 64, 64 => 65, 65 => 66, 66 => 67, 67 => 68, 68 => 69, 69 => 70, 70 => 71, 71 => 72, 72 => 73, 73 => 74, 74 => 75, 75 => 76, 76 => 77, 77 => 78, 78 => 79, 79 => 80, 80 => 81, 81 => 82, 82 => 83, 83 => 84, 84 => 85, 85 => 86, 86 => 87, 87 => 88, 88 => 89, 89 => 90, 90 => 91, 91 => 92, 92 => 93, 93 => 94, 94 => 95, 95 => 96, 96 => 97, 97 => 98, 98 => 99, 99 => 100, 100 => 101, 101 => 102, 102 => 103, 103 => 104, 104 => 105, 105 => 106, 106 => 107, 107 => 108, 108 => 109, 109 => 110, 110 => 111, 111 => 112, 112 => 113, 113 => 114, 114 => 115, 115 => 116, 116 => 117, 117 => 118, 118 => 119, 119 => 120, 120 => 121, 121 => 122, 122 => 123, 123 => 124, 124 => 125, 125 => 126, 126 => 127, 127 => 128, ...), array ('headers' => TRUE, 'type' => '1') ) ../ListMessages.php:425 10 4,1961 51488160 IMP_Imap->fetch( 'INBOX.horde.apps', class Horde_Imap_Client_Fetch_Query { protected $_data = array (9 => TRUE, 10 => TRUE, 12 => TRUE, 13 => TRUE, 8 => array ('imp' => array (...))) }, array ('ids' => class Horde_Imap_Client_Ids { protected $_ids = array (0 => 71531, 1 => 71528, 2 => 71507, 3 => 71498, 4 => 71477, 5 => 71475, 6 => 71473, 7 => 71079, 8 => 71078, 9 => 70964, 10 => 70935, 11 => 70933, 12 => 70751, 13 => 70653, 14 => 70623, 15 => 70585, 16 => 70584, 17 => 70438, 18 => 70414, 19 => 70467, 20 => 70465, 21 => 70463, 22 => 70411, 23 => 70462, 24 => 70426, 25 => 70422, 26 => 70410, 27 => 70423, 28 => 70408, 29 => 70407, 30 => 70406, 31 => 70405, 32 => 70402, 33 => 70340, 34 => 70285, 35 => 70181, 36 => 70137, 37 => 70065, 38 => 69998, 39 => 69999, 40 => 69979, 41 => 69975, 42 => 69953, 43 => 69945, 44 => 69944, 45 => 69887, 46 => 69815, 47 => 69814, 48 => 69765, 49 => 69749, 50 => 69731, 51 => 69704, 52 => 69685, 53 => 69670, 54 => 69700, 55 => 69665, 56 => 69657, 57 => 69656, 58 => 69659, 59 => 69658, 60 => 69655, 61 => 69654, 62 => 69648, 63 => 69738, 64 => 69647, 65 => 69646, 66 => 69638, 67 => 69636, 68 => 69634, 69 => 69819, 70 => 69412, 71 => 69375, 72 => 69373, 73 => 69285, 74 => 69084, 75 => 69080, 76 => 68952, 77 => 68925, 78 => 68724, 79 => 68617, 80 => 68251, 81 => 67974, 82 => 67973, 83 => 67762, 84 => 67760, 85 => 67767, 86 => 67747, 87 => 67699, 88 => 67687, 89 => 67624, 90 => 67603, 91 => 67596, 92 => 67544, 93 => 67597, 94 => 67543, 95 => 67542, 96 => 67538, 97 => 67536, 98 => 67535, 99 => 67532, 100 => 67370, 101 => 63540, 102 => 61343, 103 => 61310, 104 => 61076, 105 => 60397, 106 => 60270, 107 => 58511, 108 => 58126, 109 => 58001, 110 => 57991, 111 => 57948, 112 => 57935, 113 => 57228, 114 => 57088, 115 => 56706, 116 => 56686, 117 => 56636, 118 => 56619, 119 => 55273, 120 => 55077, 121 => 54990, 122 => 54937, 123 => 52953, 124 => 51842, 125 => 51823, 126 => 51818, 127 => 51812, ...); protected $_sequence = FALSE; protected $_utilsClass = 'Horde_Imap_Client_Utils' }) ) ../List.php:170 11 4,1961 51488912 IMP_Imap->__call( 'fetch', array (0 => 'INBOX.horde.apps', 1 => class Horde_Imap_Client_Fetch_Query { protected $_data = array (9 => TRUE, 10 => TRUE, 12 => TRUE, 13 => TRUE, 8 => array (...)) }, 2 => array ('ids' => class Horde_Imap_Client_Ids { protected $_ids = array (...); protected $_sequence = FALSE; protected $_utilsClass = 'Horde_Imap_Client_Utils' })) ) ../List.php:170 12 4,1961 51489544 call_user_func_array ( array (0 => class Horde_Imap_Client_Socket { protected $_tag = 4; protected $_stream = resource(356) of type (stream); public $cache = class Horde_Imap_Client_Cache { protected $_base = ...; protected $_cache = class Horde_Cache { ... }; protected $_data = array (...); protected $_loaded = array (...); protected $_params = array (...); protected $_slicemap = array (...); protected $_update = array (...) }; public $cacheFields = array (9 => 'HICenv', 10 => 'HICflags', 8 => 'HIChdrs', 11 => 'HICdate', 12 => 'HICsize', 1 => 'HICstruct'); public $changed = TRUE; protected $_debug = NULL; protected $_fetchDataClass = 'Horde_Imap_Client_Data_Fetch'; protected $_init = array ('enabled' => array (...), 'namespace' => array (...), 's_charset' => array (...), 'imapproxy' => TRUE, 'authmethod' => 'LOGIN', 'capability' => array (...)); protected $_isAuthenticated = TRUE; protected $_isSecure = FALSE; protected $_mode = 1; protected $_params = array ('encryptKey' => array (...), 'hostspec' => 'localhost', 'log' => NULL, 'port' => 1143, 'secure' => FALSE, 'timeout' => 30, 'password' => ' ?i\002T?S?', 'statuscache' => TRUE, 'username' => 'jan', 'cache' => array (...), '_passencrypt' => TRUE); protected $_selected = class Horde_Imap_Client_Mailbox { protected $_utf7imap = TRUE; protected $_utf8 = 'INBOX.horde.apps' }; protected $_temp = array ('no_cap' => TRUE, 'loginerr' => 'LOGIN_AUTHENTICATIONFAILED', 'loginerrmsg' => 'Der E-Mail-Server hat Authentifizierung zur??ckgewiesen.', 'referral' => NULL, 'fr_ob' => class stdClass { ... }, 'fetchresp' => class stdClass { ... }, 'parsestatuserr' => NULL, 'proxyreuse' => TRUE, 'mailbox' => array (...), 'literal8' => array (...), 'threadparse' => array (...), 'myrights' => class Horde_Imap_Client_Data_Acl { ... }, 'headers_caching' => array (...)); protected $_utils = class Horde_Imap_Client_Utils { }; protected $_utilsClass = 'Horde_Imap_Client_Utils' }, 1 => 'fetch'), array (0 => 'INBOX.horde.apps', 1 => class Horde_Imap_Client_Fetch_Query { protected $_data = array (9 => TRUE, 10 => TRUE, 12 => TRUE, 13 => TRUE, 8 => array (...)) }, 2 => array ('ids' => class Horde_Imap_Client_Ids { protected $_ids = array (...); protected $_sequence = FALSE; protected $_utilsClass = 'Horde_Imap_Client_Utils' })) ) ../Imap.php:343 13 4,1961 51490288 Horde_Imap_Client_Base->fetch( 'INBOX.horde.apps', class Horde_Imap_Client_Fetch_Query { protected $_data = array (9 => TRUE, 10 => TRUE, 12 => TRUE, 13 => TRUE, 8 => array ('imp' => array (...))) }, array ('ids' => class Horde_Imap_Client_Ids { protected $_ids = array (0 => 71531, 1 => 71528, 2 => 71507, 3 => 71498, 4 => 71477, 5 => 71475, 6 => 71473, 7 => 71079, 8 => 71078, 9 => 70964, 10 => 70935, 11 => 70933, 12 => 70751, 13 => 70653, 14 => 70623, 15 => 70585, 16 => 70584, 17 => 70438, 18 => 70414, 19 => 70467, 20 => 70465, 21 => 70463, 22 => 70411, 23 => 70462, 24 => 70426, 25 => 70422, 26 => 70410, 27 => 70423, 28 => 70408, 29 => 70407, 30 => 70406, 31 => 70405, 32 => 70402, 33 => 70340, 34 => 70285, 35 => 70181, 36 => 70137, 37 => 70065, 38 => 69998, 39 => 69999, 40 => 69979, 41 => 69975, 42 => 69953, 43 => 69945, 44 => 69944, 45 => 69887, 46 => 69815, 47 => 69814, 48 => 69765, 49 => 69749, 50 => 69731, 51 => 69704, 52 => 69685, 53 => 69670, 54 => 69700, 55 => 69665, 56 => 69657, 57 => 69656, 58 => 69659, 59 => 69658, 60 => 69655, 61 => 69654, 62 => 69648, 63 => 69738, 64 => 69647, 65 => 69646, 66 => 69638, 67 => 69636, 68 => 69634, 69 => 69819, 70 => 69412, 71 => 69375, 72 => 69373, 73 => 69285, 74 => 69084, 75 => 69080, 76 => 68952, 77 => 68925, 78 => 68724, 79 => 68617, 80 => 68251, 81 => 67974, 82 => 67973, 83 => 67762, 84 => 67760, 85 => 67767, 86 => 67747, 87 => 67699, 88 => 67687, 89 => 67624, 90 => 67603, 91 => 67596, 92 => 67544, 93 => 67597, 94 => 67543, 95 => 67542, 96 => 67538, 97 => 67536, 98 => 67535, 99 => 67532, 100 => 67370, 101 => 63540, 102 => 61343, 103 => 61310, 104 => 61076, 105 => 60397, 106 => 60270, 107 => 58511, 108 => 58126, 109 => 58001, 110 => 57991, 111 => 57948, 112 => 57935, 113 => 57228, 114 => 57088, 115 => 56706, 116 => 56686, 117 => 56636, 118 => 56619, 119 => 55273, 120 => 55077, 121 => 54990, 122 => 54937, 123 => 52953, 124 => 51842, 125 => 51823, 126 => 51818, 127 => 51812, ...); protected $_sequence = FALSE; protected $_utilsClass = 'Horde_Imap_Client_Utils' }) ) ../Imap.php:343 14 4,2080 51759544 Horde_Imap_Client_Cache->get( class Horde_Imap_Client_Mailbox { protected $_utf7imap = TRUE; protected $_utf8 = 'INBOX.horde.apps' }, array (0 => 71531, 1 => 71528, 2 => 71507, 3 => 71498, 4 => 71477, 5 => 71475, 6 => 71473, 7 => 71079, 8 => 71078, 9 => 70964, 10 => 70935, 11 => 70933, 12 => 70751, 13 => 70653, 14 => 70623, 15 => 70585, 16 => 70584, 17 => 70438, 18 => 70414, 19 => 70467, 20 => 70465, 21 => 70463, 22 => 70411, 23 => 70462, 24 => 70426, 25 => 70422, 26 => 70410, 27 => 70423, 28 => 70408, 29 => 70407, 30 => 70406, 31 => 70405, 32 => 70402, 33 => 70340, 34 => 70285, 35 => 70181, 36 => 70137, 37 => 70065, 38 => 69998, 39 => 69999, 40 => 69979, 41 => 69975, 42 => 69953, 43 => 69945, 44 => 69944, 45 => 69887, 46 => 69815, 47 => 69814, 48 => 69765, 49 => 69749, 50 => 69731, 51 => 69704, 52 => 69685, 53 => 69670, 54 => 69700, 55 => 69665, 56 => 69657, 57 => 69656, 58 => 69659, 59 => 69658, 60 => 69655, 61 => 69654, 62 => 69648, 63 => 69738, 64 => 69647, 65 => 69646, 66 => 69638, 67 => 69636, 68 => 69634, 69 => 69819, 70 => 69412, 71 => 69375, 72 => 69373, 73 => 69285, 74 => 69084, 75 => 69080, 76 => 68952, 77 => 68925, 78 => 68724, 79 => 68617, 80 => 68251, 81 => 67974, 82 => 67973, 83 => 67762, 84 => 67760, 85 => 67767, 86 => 67747, 87 => 67699, 88 => 67687, 89 => 67624, 90 => 67603, 91 => 67596, 92 => 67544, 93 => 67597, 94 => 67543, 95 => 67542, 96 => 67538, 97 => 67536, 98 => 67535, 99 => 67532, 100 => 67370, 101 => 63540, 102 => 61343, 103 => 61310, 104 => 61076, 105 => 60397, 106 => 60270, 107 => 58511, 108 => 58126, 109 => 58001, 110 => 57991, 111 => 57948, 112 => 57935, 113 => 57228, 114 => 57088, 115 => 56706, 116 => 56686, 117 => 56636, 118 => 56619, 119 => 55273, 120 => 55077, 121 => 54990, 122 => 54937, 123 => 52953, 124 => 51842, 125 => 51823, 126 => 51818, 127 => 51812, ...), array (0 => 'HICenv', 1 => 'HIChdrs', 2 => 'HICsize'), '995370855' ) ../Base.php:2425 15 4,2080 51760024 Horde_Imap_Client_Cache->_loadUids( 'INBOX.horde.apps', array (0 => 71531, 1 => 71528, 2 => 71507, 3 => 71498, 4 => 71477, 5 => 71475, 6 => 71473, 7 => 71079, 8 => 71078, 9 => 70964, 10 => 70935, 11 => 70933, 12 => 70751, 13 => 70653, 14 => 70623, 15 => 70585, 16 => 70584, 17 => 70438, 18 => 70414, 19 => 70467, 20 => 70465, 21 => 70463, 22 => 70411, 23 => 70462, 24 => 70426, 25 => 70422, 26 => 70410, 27 => 70423, 28 => 70408, 29 => 70407, 30 => 70406, 31 => 70405, 32 => 70402, 33 => 70340, 34 => 70285, 35 => 70181, 36 => 70137, 37 => 70065, 38 => 69998, 39 => 69999, 40 => 69979, 41 => 69975, 42 => 69953, 43 => 69945, 44 => 69944, 45 => 69887, 46 => 69815, 47 => 69814, 48 => 69765, 49 => 69749, 50 => 69731, 51 => 69704, 52 => 69685, 53 => 69670, 54 => 69700, 55 => 69665, 56 => 69657, 57 => 69656, 58 => 69659, 59 => 69658, 60 => 69655, 61 => 69654, 62 => 69648, 63 => 69738, 64 => 69647, 65 => 69646, 66 => 69638, 67 => 69636, 68 => 69634, 69 => 69819, 70 => 69412, 71 => 69375, 72 => 69373, 73 => 69285, 74 => 69084, 75 => 69080, 76 => 68952, 77 => 68925, 78 => 68724, 79 => 68617, 80 => 68251, 81 => 67974, 82 => 67973, 83 => 67762, 84 => 67760, 85 => 67767, 86 => 67747, 87 => 67699, 88 => 67687, 89 => 67624, 90 => 67603, 91 => 67596, 92 => 67544, 93 => 67597, 94 => 67543, 95 => 67542, 96 => 67538, 97 => 67536, 98 => 67535, 99 => 67532, 100 => 67370, 101 => 63540, 102 => 61343, 103 => 61310, 104 => 61076, 105 => 60397, 106 => 60270, 107 => 58511, 108 => 58126, 109 => 58001, 110 => 57991, 111 => 57948, 112 => 57935, 113 => 57228, 114 => 57088, 115 => 56706, 116 => 56686, 117 => 56636, 118 => 56619, 119 => 55273, 120 => 55077, 121 => 54990, 122 => 54937, 123 => 52953, 124 => 51842, 125 => 51823, 126 => 51818, 127 => 51812, ...), '995370855' ) ../Cache.php:288 16 4,2114 51860992 Horde_Imap_Client_Cache->deleteMsgs( 'INBOX.horde.apps', array (0 => 71477, 1 => 71475, 2 => 71473, 3 => 71079, 4 => 71078, 5 => 70964, 6 => 70935, 7 => 70933, 8 => 70751, 9 => 70653, 10 => 70623, 11 => 70585, 12 => 70584, 13 => 70438, 14 => 70414, 15 => 70467, 16 => 70465, 17 => 70463, 18 => 70411, 19 => 70462, 20 => 70426, 21 => 70422, 22 => 70410, 23 => 70423, 24 => 70408, 25 => 70407, 26 => 70406, 27 => 70405, 28 => 70402, 29 => 70340, 30 => 70285, 31 => 70181, 32 => 70137, 33 => 70065, 34 => 69998, 35 => 69999, 36 => 69979, 37 => 69975, 38 => 69953, 39 => 69945, 40 => 69944, 41 => 69887, 42 => 69815, 43 => 69814, 44 => 69765, 45 => 69749) ) ../Cache.php:531 17 4,2115 51877384 Horde_Imap_Client_Cache->_loadUids( 'INBOX.horde.apps', array (0 => 71477, 1 => 71475, 2 => 71473, 3 => 71079, 4 => 71078, 5 => 70964, 6 => 70935, 7 => 70933, 8 => 70751, 9 => 70653, 10 => 70623, 11 => 70585, 12 => 70584, 13 => 70438, 14 => 70414, 15 => 70467, 16 => 70465, 17 => 70463, 18 => 70411, 19 => 70462, 20 => 70426, 21 => 70422, 22 => 70410, 23 => 70423, 24 => 70408, 25 => 70407, 26 => 70406, 27 => 70405, 28 => 70402, 29 => 70340, 30 => 70285, 31 => 70181, 32 => 70137, 33 => 70065, 34 => 69998, 35 => 69999, 36 => 69979, 37 => 69975, 38 => 69953, 39 => 69945, 40 => 69944, 41 => 69887, 42 => 69815, 43 => 69814, 44 => 69765, 45 => 69749), ??? ) ../Cache.php:438 18 4,2123 51894872 Horde_Imap_Client_Cache->deleteMsgs( 'INBOX.horde.apps', array (0 => 71477, 1 => 71475, 2 => 71473, 3 => 71079, 4 => 71078, 5 => 70964, 6 => 70935, 7 => 70933, 8 => 70751, 9 => 70653, 10 => 70623, 11 => 70585, 12 => 70584, 13 => 70438, 14 => 70414, 15 => 70467, 16 => 70465, 17 => 70463, 18 => 70411, 19 => 70462, 20 => 70426, 21 => 70422, 22 => 70410, 23 => 70423, 24 => 70408, 25 => 70407, 26 => 70406, 27 => 70405, 28 => 70402, 29 => 70340, 30 => 70285, 31 => 70181, 32 => 70137, 33 => 70065, 34 => 69998, 35 => 69999, 36 => 69979, 37 => 69975, 38 => 69953, 39 => 69945, 40 => 69944, 41 => 69887, 42 => 69815, 43 => 69814, 44 => 69765, 45 => 69749) ) ../Cache.php:531 19 4,2125 51911264 Horde_Imap_Client_Cache->_loadUids( 'INBOX.horde.apps', array (0 => 71477, 1 => 71475, 2 => 71473, 3 => 71079, 4 => 71078, 5 => 70964, 6 => 70935, 7 => 70933, 8 => 70751, 9 => 70653, 10 => 70623, 11 => 70585, 12 => 70584, 13 => 70438, 14 => 70414, 15 => 70467, 16 => 70465, 17 => 70463, 18 => 70411, 19 => 70462, 20 => 70426, 21 => 70422, 22 => 70410, 23 => 70423, 24 => 70408, 25 => 70407, 26 => 70406, 27 => 70405, 28 => 70402, 29 => 70340, 30 => 70285, 31 => 70181, 32 => 70137, 33 => 70065, 34 => 69998, 35 => 69999, 36 => 69979, 37 => 69975, 38 => 69953, 39 => 69945, 40 => 69944, 41 => 69887, 42 => 69815, 43 => 69814, 44 => 69765, 45 => 69749), ??? ) ../Cache.php:438 ...and so on.