http://permalink.gmane.org/gmane.comp.horde.sync hourly 1 1901-01-01T00:00+00:00 http://gmane.org/img/gmane-25t.png http://gmane.org http://permalink.gmane.org/gmane.comp.horde.sync/2888 <pre> Quoting Lukas Gradl &lt;horde&lt; at &gt;ssn.at&gt;: This is client specific, but most clients use what is called "smart forward" and "smart reply" - which is just a fancy way of saying that only the new body text (the reply or forward text that the user enters with the new email) is sent to the server, along with the message id/folder information. The server then is responsible for fetching the replied to/forwarded message and constructing the entire email to send. Basically, the original body is never sent from the client to the server anyway, so this would work regardless of if the client received the body or not. This is almost certainly a client/display issue. The other users who have reported this problem have provided sync logs that show correctly formatted wbxml being sent to the client. In other words, the client is receiving the information but for some reason, it is not displaying it. Additionally, the code path for generating and sending the data to the client is *exactly* the same</pre> Michael J Rubinsky 2013-05-09T15:52:24 http://permalink.gmane.org/gmane.comp.horde.sync/2887 <pre> Zitat von Michael J Rubinsky &lt;mrubinsk&lt; at &gt;horde.org&gt;: Just made a strange discovery: While working on getting a synclog I discovered that when you forward one of the mails without body to another address I discovered that the forwarded message contains a body. So - how is forwarding handled by horde/activesync: If it is done by the phone itself this means that the mail is synced correctly to the phone is a display-problem and not a sync-problem. I'm still trying to get a synclog... regards Lukas </pre> Lukas Gradl 2013-05-09T15:23:19 http://permalink.gmane.org/gmane.comp.horde.sync/2886 <pre>Quoting Lukas Gradl &lt;horde&lt; at &gt;ssn.at&gt;&gt; Hi! I would need a sync log for the device captured during the sync. That being said, I have test devices running WinMo 6.5, WP 7.10, and WP 8.0 and they all work as expected. Mike Sent from mobile. Lukas Gradl &lt;horde&lt; at &gt;ssn.at&gt; wrote: </pre> Michael J Rubinsky 2013-05-08T17:46:50 http://permalink.gmane.org/gmane.comp.horde.sync/2885 <pre>Hi! We've a problem with a Windows Phone 7.5 device (Nokia Lumia 800) connected to Horde (5.0.4) via ActiveSync (Protocol Version 12.1). Mails transferred via initial sync are displayed correctly, Mail arriving at a later time show headers only. Unfortunatly I don't have access to the phone and we don't have another Windows phone to compare. Android and iOS are working as expected. I've found http://bugs.horde.org/ticket/12203 so it seems that I'm not the only one with that problem. Any hints what to do next? regards Lukas </pre> Lukas Gradl 2013-05-08T17:11:21 http://permalink.gmane.org/gmane.comp.horde.sync/2884 <pre>Citeren Arjen de Korte &lt;arjen+horde&lt; at &gt;de-korte.org&gt;: I spoke too soon. No more errors, but no more synchronization either. I'll revert to the Horde_ActiveSync-2.3.6 and wait for the next beta release instead. </pre> Arjen de Korte 2013-05-06T19:15:35 http://permalink.gmane.org/gmane.comp.horde.sync/2883 <pre>Citeren Michael J Rubinsky &lt;mrubinsk&lt; at &gt;horde.org&gt;: That indeed seems to do the job. I noticed there are quite a few changes between Horde_ActiveSync-2.4.0beta1 and Git master, so you're probably right about the other errors that have been fixed. Great. </pre> Arjen de Korte 2013-05-06T19:08:38 http://permalink.gmane.org/gmane.comp.horde.sync/2882 <pre> Quoting Arjen de Korte &lt;arjen+horde&lt; at &gt;de-korte.org&gt;: Not sure what to tell you. I just now installed the current git activesync over a framework_5_0 install and it worked fine. Probably one of the other errors that was recently fixed in Git as well. Will probably put out another beta release in the not too distant future. </pre> Michael J Rubinsky 2013-05-06T17:19:34 http://permalink.gmane.org/gmane.comp.horde.sync/2881 <pre>Citeren Michael J Rubinsky &lt;mrubinsk&lt; at &gt;horde.org&gt;: Will there be a new release of Horde_ActiveSync shortly? I tried patching /Horde/ActiveSync/Driver/Base.php (remove parameter), but although it fixed the Fatal error, I still can't connect with ActiveSync anymore. I can't even make it past the authentication. I see the following rather non-descript message in the ActiveSync log: 2013-05-06T18:42:54+02:00 INFO: [13980] Horde_Core_ActiveSync_Driver::authenticate() attempt for That's it, nothing else. </pre> Arjen de Korte 2013-05-06T16:50:07 http://permalink.gmane.org/gmane.comp.horde.sync/2880 <pre> Quoting Arjen de Korte &lt;arjen+horde&lt; at &gt;de-korte.org&gt;: This was an oversight and is fixed in Git. </pre> Michael J Rubinsky 2013-05-06T13:38:05 http://permalink.gmane.org/gmane.comp.horde.sync/2879 <pre>Citeren Michael J Rubinsky &lt;mrubinsk&lt; at &gt;horde.org&gt;: After upgrading to Horde_ActiveSync-2.4.0beta1, I can't connect with ActiveSync and get the following messages in the server logs (for each Ping/Sync): [Sat May 04 21:12:34 2013] [error] [client 192.168.1.126] PHP Fatal error: Declaration of Horde_Core_ActiveSync_Driver::getCurrentPolicy() must be compatible with that of Horde_ActiveSync_Driver_Base::getCurrentPolicy() in /usr/share/php5/PEAR/Horde/Core/ActiveSync/Driver.php on line 12 Installed packages, channel pear.horde.org: =========================================== Package Version State Horde_ActiveSync 2.4.0beta1 beta Horde_Core 2.4.3 stable I'm not much of a PHP programmer, but an egrep on 'function getCurrentPolicy' reveals what might be wrong: # egrep -R "function getCurrentPolicy" Core/ActiveSync/Driver.php: public function getCurrentPolicy() ActiveSync/Driver/Base.php: abstract public function getCurrentPolicy($de</pre> Arjen de Korte 2013-05-05T19:37:18 http://permalink.gmane.org/gmane.comp.horde.sync/2878 <pre> Quoting Arjen de Korte &lt;arjen+horde&lt; at &gt;de-korte.org&gt;: It ActiveSync 2.4.0 shouldn't require Core 2.5.0. The reverse, however, might be true. What interface change did you find that would require Core 2.5.0? If this is, indeed, true, it is a bug and must be corrected before final release. </pre> Michael J Rubinsky 2013-05-05T13:12:15 http://permalink.gmane.org/gmane.comp.horde.sync/2877 <pre>I looks like Horde_ActiveSync-2.4.0beta1 requires the (to be released) Horde_Core-2.5.0 because of changes in the interface. It might be helpful to add this dependency. </pre> Arjen de Korte 2013-05-05T09:07:38 http://permalink.gmane.org/gmane.comp.horde.sync/2876 <pre>Am 05.04.2013 21:51, schrieb Michael J Rubinsky: Thanks again Mike. That clears up a few of my questions. But I need to get more into it, because i am still wondering why its working fine with calendar events but not birthdays. Thank you for your time. Patrick </pre> lists.horde.org< at >pqaudio.de 2013-04-06T13:10:48 http://permalink.gmane.org/gmane.comp.horde.sync/2875 <pre>Quoting "lists.horde.org&lt; at &gt;pqaudio.de" &lt;lists.horde.org&lt; at &gt;pqaudio.de&gt;&gt; Am 05.04.2013 18:47, schrieb mrubinsk&lt; at &gt;horde.org: mike Sent from mobile lists.horde.org&lt; at &gt;pqaudio.de wrote: </pre> mrubinsk< at >horde.org 2013-04-05T19:43:25 http://permalink.gmane.org/gmane.comp.horde.sync/2874 <pre>time. Even "full day" events in the calendar have a defined start and end time - as well as a flag for indicating to the client that it's a full day event. Birthdays, on the other hand, have neither. This is way it's a problem that the protocol requires that the birthday be a full UTC datetime field (containing both the date and the time component) while it doesn't specify what specific time birthdays should set the time component to. Can the application not simply make the decision to put 00:00:00? Simon </pre> Simon Brereton 2013-04-06T13:59:32 http://permalink.gmane.org/gmane.comp.horde.sync/2873 <pre>Quoting "lists.horde.org&lt; at &gt;pqaudio.de" &lt;lists.horde.org&lt; at &gt;pqaudio.de&gt;&gt; Hi, This is a known issue with the ActiveSync protocol. It has been discussed before either on the dev list or bug tracker. A google search for something like 'contact birthday activesync issues' should also turn up tons of postings related to various clients. mike Sent from mobile lists.horde.org&lt; at &gt;pqaudio.de wrote: </pre> mrubinsk< at >horde.org 2013-04-05T16:47:09 http://permalink.gmane.org/gmane.comp.horde.sync/2872 <pre> Quoting "lists.horde.org&lt; at &gt;pqaudio.de" &lt;lists.horde.org&lt; at &gt;pqaudio.de&gt;: It works for calendar events because they begin and end at a discreet time. Even "full day" events in the calendar have a defined start and end time - as well as a flag for indicating to the client that it's a full day event. Birthdays, on the other hand, have neither. This is way it's a problem that the protocol requires that the birthday be a full UTC datetime field (containing both the date and the time component) while it doesn't specify what specific time birthdays should set the time component to. </pre> Michael J Rubinsky 2013-04-06T13:38:19 http://permalink.gmane.org/gmane.comp.horde.sync/2871 <pre>Hi, when horde sents a contact with active sync to my mobile phone, the date of birth is shifted by one hour into the past. As we only need the know the date for birthdays, we don't have extra data like a timestamp stored within the database. But we have a varchar field with a size of 10 to store iso formatted dates. But thats no problem, PHP will threat those dates with a timestamp of 00:00:00. All dates of birth in the database (table `horde_contacts`, fieldname `object_bday`) are right. But a look into the ActiveSync Log file offers, that somewhere must be done some date/time calculation magic that a birthday eg. "1980-03-10" is exported as "1980-03-09T23:00:00.000Z" But this only occurs, when a contact is synced from horde to my mobile phone. The other direction works fine, also calendar entries are synced as expected. My php default date/time zone is set to 'Europe/Berlin'. Online research and a lot of debug approaches did not help. Now i'm unsure if its a horde problem or maybe some misconfigurati</pre> lists.horde.org< at >pqaudio.de 2013-04-05T16:01:30 http://permalink.gmane.org/gmane.comp.horde.sync/2870 <pre>Am 05.04.2013 18:47, schrieb mrubinsk&lt; at &gt;horde.org: Thank you Mike. I found those articles before. I am not deep enough in the active sync thing, but to be honest, i can't see why its neccessary to convert birth dates between different time zones before i sync them with my phone. In any case, i have to get more into it. Thanks again. Patrick </pre> lists.horde.org< at >pqaudio.de 2013-04-05T19:21:13 http://permalink.gmane.org/gmane.comp.horde.sync/2869 <pre> Quoting Simon Brereton &lt;simon.buongiorno&lt; at &gt;gmail.com&gt;: Yes. That's exactly what we do...and the cause of the problem. Since it's UTC, the client adjusts to the local/configured timezone. Depending on the timezone, the can cause the birthday to be shifted to a different calendar day. </pre> Michael J Rubinsky 2013-04-06T15:23:47 http://permalink.gmane.org/gmane.comp.horde.sync/2868 <pre> Quoting Michael J Rubinsky &lt;mrubinsk&lt; at &gt;horde.org&gt;: I should also mention that this is further complicated by the fact that different clients treat birthdays differently. E.g., some Android clients will *transmit* birthdays as occuring at 06:00:00 UTC, some other Android clients treat the field as a text field. Yet others treat it as-is and simply display the date without first converting it, while others treat it as a true activesync datetime field. The bottom line is any logic done on the server (such as first translating the birthday to 00:00:00 local time before converting to UTC) to transmit a birthday "correctly" on a particular device can break the birthday display on other devices and, possibly even cause the birthday of any contact that has been edited on the device to be corrupted on the server. IMO, this is a flaw in the protocol. The birthday field should either be a straight text field, actual event object attached to the contact object, or a specific time should have b</pre> Michael J Rubinsky 2013-04-06T15:37:10 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.comp.horde.sync