[Tickets #14122] Read receipt does not work with Outlook 2013 EAS / ActiveSync devices

noreply at bugs.horde.org noreply at bugs.horde.org
Thu Oct 1 10:34:35 UTC 2015


BITTE NICHT AUF DIESE NACHRICHT ANTWORTEN. NACHRICHTEN AN DIESE  
E-MAIL-ADRESSE WERDEN NICHT GELESEN.

Ticket-URL: https://bugs.horde.org/ticket/14122
------------------------------------------------------------------------------
  Ticket           | 14122
  Erstellt Von     | hn at axxedia-it.de
  Zusammenfassung  | Read receipt does not work with Outlook 2013 EAS /
                   | ActiveSync devices
  Warteschlange    | Synchronization
  Version          | FRAMEWORK_5_2
  Typ              | Enhancement
  Status           | New
  Priorität        | 1. Low
  Milestone        |
  Patch            |
  Zuständige       |
------------------------------------------------------------------------------


hn at axxedia-it.de (2015-10-01 10:34) hat geschrieben:

Today a user called me and asked why the read receipts are not working  
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






More information about the bugs mailing list