| Summary | Add option to enable automatic generation of Read Receipt/Disposition-Notification responses from EAS connected clients. |
| Queue | Synchronization |
| Queue Version | Git master |
| Type | Enhancement |
| State | Resolved |
| Priority | 1. Low |
| Owners | mrubinsk (at) horde (dot) org |
| Requester | hn (at) axxedia-it (dot) de |
| Created | 10/01/2015 (3565 days ago) |
| Due | |
| Updated | 12/10/2015 (3495 days ago) |
| Assigned | 10/01/2015 (3565 days ago) |
| Resolved | 12/10/2015 (3495 days ago) |
| Milestone | |
| Patch | No |
State ⇒ Resolved
Version ⇒ Git master
commit 2c538ffe04241f742a2073fe4a19d7e3a74b6380
Author: Michael J Rubinsky <mrubinsk@horde.org>
Date: Thu Dec 10 01:44:08 2015 -0500
Request: 14122Support sending MDM via ActiveSync access.Honors IMP's mdn_send pref and/or hooks.
.../Core/lib/Horde/Core/ActiveSync/Connector.php | 18 +++
.../Core/lib/Horde/Core/ActiveSync/Driver.php | 18 +++
framework/Core/lib/Horde/Core/ActiveSync/Mdn.php | 121
++++++++++++++++++++
framework/Core/package.xml | 6 +-
4 files changed, 161 insertions(+), 2 deletions(-)
http://github.com/horde/horde/commit/2c538ffe04241f742a2073fe4a19d7e3a74b6380
commit 4610152d908503782fbed8b78739b31a34fab634
Author: Michael J Rubinsky <mrubinsk@horde.org>
Date: Thu Dec 10 01:41:24 2015 -0500
Expose IMP_Indices::mdnCheck via the API.
Needed for
Request: 14122imp/lib/Api.php | 14 ++++++++++++++
1 files changed, 14 insertions(+), 0 deletions(-)
http://github.com/horde/horde/commit/4610152d908503782fbed8b78739b31a34fab634
choice is a bad thing. I normally do not send any RR at all, because
no one must know when I read my email.
Having that said, there are users who cannot live without RR. Maybe
you could implement it like it is done in imp, where you can define
one or more domains that are enabled for automatic RR.
Summary ⇒ Add option to enable automatic generation of Read Receipt/Disposition-Notification responses from EAS connected clients.
Assigned to Michael Rubinsky
it's the server's responsibility to do this. I purposely did not
implement this since there is no EAS client policy or user setting in
the client that would allow turning this off. I'd be against anything
that sends a RR without giving the user a chance to prevent one from
being sent.
What we can do, is create a user preference for automatically sending
them from EAS that defaults to FALSE. The administrator can still lock
the preference if he desires to force this feature.
Priority ⇒ 1. Low
State ⇒ New
Patch ⇒ No
Milestone ⇒
Queue ⇒ Synchronization
Summary ⇒ Read receipt does not work with Outlook 2013 EAS / ActiveSync devices
Type ⇒ Enhancement
anymore since we moved from Outlook 2007 to Outlook 2013. I did some
testing and found out, that read receipts do work, when they are sent
to recipients not using Outlook 2013 EAS / ActiveSync devices with
Horde, so most external recipients get the request to send a receipt.
All internal users never see the read receipt request, and so the
feature does not work. The same happens when an outsider sends an
e-mail to us with the read receipt request enabled and Outlook 2013
receives the message. It is not sending an answer back.
I was digging a bit on the Internet and found a similar problem in
Zimbra. It is described in this bug report:
https://bugzilla.zimbra.com/show_bug.cgi?id=83736
What I learned from the above mentioned bug report is, that It seems
like ActiveSync handles the read receipt messaging on the server side,
so it seems to me that Horde ActiveSync does not have this implemented
yet?
Can anyone confirm this? Are there plans on implementing that feature
or is there a workaround / parameter available to enable this
funtionality?
Best regards,
Hendrik