6.0.0-git
2019-07-18

[#14932] Do not decode TNEF attachments if AS client is Outlook
Summary Do not decode TNEF attachments if AS client is Outlook
Queue Synchronization
Queue Version Git master
Type Bug
State Unconfirmed
Priority 3. High
Owners
Requester pachis83 (at) gmail (dot) com
Created 2019-07-01 (17 days ago)
Due
Updated 2019-07-01 (17 days ago)
Assigned
Resolved
Milestone
Patch Yes

History
2019-07-01 11:11:31 pachis83 (at) gmail (dot) com Comment #1
Type ⇒ Bug
State ⇒ Unconfirmed
Priority ⇒ 3. High
Summary ⇒ Do not decode TNEF attachments if AS client is Outlook
Queue ⇒ Synchronization
Milestone ⇒
Patch ⇒ Yes
New Attachment: Message.php Download
Reply to this comment
MS Outlook is able to handle TNEF data by itself but horde stack 
always decodes TNEF data, even in ActiveSync connections.

As a result, TNEF data with a Task event is received as a VTODO file 
(or VTASK??? I don't remember) wich Outlook can't handle.

TNEF decoding is ok for non MS activesync clients, but when outlook is 
used, TNEF data should be avoided.

In my case all the AS clients are Outlook type so I disabled TNEF 
decoding commenting lines 311, 313, 414, 415, 417 in 
ActiveSync/lib/Horde/ActiveSync/Imap/Message.php (attached).

Regards.






Saved Queries