6.0.0-beta1
7/9/25

[#13719] Problem with OOF on ActiveSync Start-Enddate
Summary Problem with OOF on ActiveSync Start-Enddate
Queue Synchronization
Queue Version FRAMEWORK_5_2
Type Bug
State Resolved
Priority 1. Low
Owners mrubinsk (at) horde (dot) org
Requester tomnet (at) tbuhl (dot) ch
Created 11/24/2014 (3880 days ago)
Due
Updated 01/05/2015 (3838 days ago)
Assigned 12/16/2014 (3858 days ago)
Resolved 01/03/2015 (3840 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch No

History
01/05/2015 07:12:53 PM Michael Rubinsky Comment #14 Reply to this comment
No, not permissions.

It looks like the pirum server is unable to rebuild due to a broken 
dependency in at least one package, on the now EOL'd pear.phpunit.de 
channel.

I'll look at this when I'm back home and not ssh'ing via my phone.
01/05/2015 05:30:31 PM samuel (dot) wolf (at) wolf-maschinenbau (dot) de Comment #13 Reply to this comment
Horde_Core 2.18.1 and Horde_ActiveSync 2.23.1
Is there some reason (permission?) why this update is not available 
over pear.horde.org?
01/03/2015 03:37:46 AM Michael Rubinsky Comment #12
State ⇒ Resolved
Reply to this comment
Horde_Core 2.18.1 and Horde_ActiveSync 2.23.1
01/03/2015 03:36:46 AM Git Commit Comment #11 Reply to this comment
Changes have been made in Git (master):

commit cf2cc2bb31d7b8dc0d587694b3ca872901694fd2
Author: Michael J Rubinsky <mrubinsk@horde.org>
Date:   Fri Jan 2 22:36:22 2015 -0500

     [mjr] Improve/fix support for handling OOF messages in ActiveSync 
(Bug #13719).

  framework/Core/package.xml |    2 ++
  1 files changed, 2 insertions(+), 0 deletions(-)

http://github.com/horde/horde/commit/cf2cc2bb31d7b8dc0d587694b3ca872901694fd2
01/03/2015 03:36:41 AM Git Commit Comment #10 Reply to this comment
Changes have been made in Git (master):

commit 37abe9ce7eb2949f0a55d921882c9fa3ba53e33f
Author: Michael J Rubinsky <mrubinsk@horde.org>
Date:   Fri Jan 2 22:35:56 2015 -0500

     [mjr] Improve/fix support for handling OOF messages (Bug #13719).

  framework/ActiveSync/package.xml |    4 ++--
  1 files changed, 2 insertions(+), 2 deletions(-)

http://github.com/horde/horde/commit/37abe9ce7eb2949f0a55d921882c9fa3ba53e33f
12/16/2014 03:11:28 PM Michael Rubinsky Comment #9
State ⇒ Assigned
Reply to this comment
The log looks good. I'll have a look to see what information is 
actually making it to Ingo's API to be sure the issue isn't in Ingo.
12/16/2014 02:40:39 PM tomnet (at) tbuhl (dot) ch Comment #8
New Attachment: 4E696E65363842304442453135453833.txt Download
Reply to this comment
For the archive :)
The mentioned attachement didn't make th trough yesterday...

-- Tom
12/15/2014 09:54:27 PM tomnet (at) tbuhl (dot) ch Comment #7 Reply to this comment
I just installed the latest ActiveSync Version and it still doesn't 
work as expected.
But i didn't see the protocol error any more.
I added another log of an unsuccessful ActiveSync (Unsuccessful in the 
sense that ingo didn't catch the changes made on the mobile side.)
I still file a bug tomorrow with nine, because the client shows 
nonstandart behaviour, something i think shouldn't be taken care of 
server side.
--Tom


12/15/2014 06:54:20 PM Michael Rubinsky Comment #6
State ⇒ Resolved
Reply to this comment
Not really a Horde bug, but "fixed" in Horde_ActiveSync 2.21.0
12/15/2014 06:53:34 PM Git Commit Comment #5 Reply to this comment
Changes have been made in Git (master):

commit d392c14dd37b69c0d7cdb651121cb1fca8c52dc0
Author: Michael J Rubinsky <mrubinsk@horde.org>
Date:   Mon Dec 15 13:50:57 2014 -0500

     Refactor DEVICEINFORMATION requests and workaround Bug: 13719 in the
     process.

  .../Horde/ActiveSync/Message/DeviceInformation.php |   73 +++++++++++
  .../lib/Horde/ActiveSync/Message/Oof.php           |   61 +++++++++
  .../lib/Horde/ActiveSync/Message/OofMessage.php    |   64 +++++++++
  .../lib/Horde/ActiveSync/Request/Settings.php      |  137 
++++++--------------
  framework/ActiveSync/package.xml                   |   14 ++-
  5 files changed, 247 insertions(+), 102 deletions(-)

http://github.com/horde/horde/commit/d392c14dd37b69c0d7cdb651121cb1fca8c52dc0
12/15/2014 06:24:12 PM Michael Rubinsky Comment #4 Reply to this comment
Thanks Mike, for looking into this!
I'l file a bug with the Nine Folks then...!

--Tom
I'm currently trying to come up with a workaround as well.
12/15/2014 05:51:31 PM tomnet (at) tbuhl (dot) ch Comment #3 Reply to this comment
Thanks Mike, for looking into this!
I'l file a bug with the Nine Folks then...!

--Tom

12/15/2014 05:05:14 PM Michael Rubinsky Comment #2
State ⇒ Not A Bug
Reply to this comment
This actually has nothing to do with Start/End Time. It's a bug in 
Nine that is triggered by an empty response text. The empty value, 
instead of being sent as the empty tag (<Settings:ReplyMessage />) It 
is being sent as an Opening and Closing tag with no content. This 
isn't correct.

You can test this yourself by selecting to send the same (non-empty) 
message to both internal and external users.


11/25/2014 07:51:54 AM Michael Rubinsky State ⇒ Assigned
Assigned to Michael Rubinsky
 
11/24/2014 08:06:34 PM tomnet (at) tbuhl (dot) ch Comment #1
Priority ⇒ 1. Low
State ⇒ Unconfirmed
New Attachment: OOF.txt Download
Patch ⇒ No
Milestone ⇒
Queue ⇒ Synchronization
Summary ⇒ Problem with OOF on ActiveSync Start-Enddate
Type ⇒ Bug
Reply to this comment
Basically, OOF works according to settings from Volker Then
"In Nine, you have to uncheck "Send replies only during this time 
period"; and check "Send same replies to outside organization" as well 
as "Send automatic replies to senders outside my organization" and on 
the bottom uncheck "Send only to my Contacts"."
If i activate Start-Enddate, i get an error on the client.
(See attached Activesync log)

Saved Queries