[Tickets #12797] Re: HTML code in description table with Outlook 2013 and ActiveSync

noreply at bugs.horde.org noreply at bugs.horde.org
Mon Oct 28 15:23:10 UTC 2013


DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/12797
------------------------------------------------------------------------------
  Ticket             | 12797
  Updated By         | Michael Rubinsky <mrubinsk at horde.org>
  Summary            | HTML code in description table with Outlook 2013 and
                     | ActiveSync
  Queue              | Synchronization
  Version            | Git master
  Type               | Bug
-State              | Feedback
+State              | Assigned
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             | Michael Rubinsky
------------------------------------------------------------------------------


Michael Rubinsky <mrubinsk at horde.org> (2013-10-28 15:23) wrote:

> This is my installation:
>
> pear install horde/horde_role
> pear run-scripts horde/horde_role
> pear install -a -B horde/webmail
> mysql -u root -p
> create database horde;
> webmail-install

Well, you created this ticket under "Git Master" which is NOT what you  
have installed.

> Nothing else... :-(
>
> I've configured apache to work with a REAL (trial) ssl cert because  
> without it outlook could not discover and authenticate with  
> activcesync
>
>>
>> Same here.
>>
>> This is very bizarre. Various Microsoft, Exchange, and Outlook
>> forums, as well as official Microsoft support channels, all indicate
>> that HTML/RTF text is NOT used for items that are synchronized over
>> ActiveSync - only with true Exchange connectivity or local IMAP/POP3
>> accounts.
>
> Maybe you have make a good work, Outlook thinks that Horde is a REAL  
> Exchange server.. :-D

Heh, that would be nice, but they talk completely different protocols.  
OL will not talk ActiveSync to a real Exchange server (not without  
some hacks to the registry anyway).

Anyway,  I see Nag still needs to be fixed to handle the incoming HTML  
data if it's present.





More information about the bugs mailing list