[Tickets #13709] Re: Unable to sendemail using ActiveSync with Android devices

[noreply at bugs.horde.org]

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

Ticket URL: https://bugs.horde.org/ticket/13709
------------------------------------------------------------------------------
  Ticket             | 13709
  Updated By         | Joerg.Pulz at frm2.tum.de
  Summary            | Unable to sendemail using ActiveSync with Android
                     | devices
  Queue              | Horde Framework Packages
  Type               | Bug
  State              | Not A Bug
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


Joerg.Pulz at frm2.tum.de (2014-11-24 13:02) wrote:

Hi again,

i stumbled over the same behavior again and can now provide some more details.

Composing a new mail on my Android device and sending this one is working.
Answering a mail on my Android device is not working, but it seems to  
be related to the mail i try to answer.
If I answer a mail I've sent from my device before it works, but I  
have at least one other mail I can't answer with the error:
<horde.log>
EMERG: HORDE Server does not support binary message data. [pid .... on  
line 596 of "/..../horde/libs/Horde/Smtp.php"]

<device.log>
2014-11-24T13:40:43+01:00 INFO: [9686] SMARTREPLY request received for  
user .....
2014-11-24T13:40:43+01:00 INFO: [9686] Device entry exists for .....,  
updating userAgent and version.
2014-11-24T13:40:43+01:00 INFO: [9686] Request being handled for  
device: ....., Supporting protocol version: 14.1, Using  
Horde_ActiveSync v2.x.y-git
2014-11-24T13:40:43+01:00 INFO: [9686] GET VARIABLES: Array
(
     [Cmd] => SmartReply
     [User] => .....
     [DeviceId] => .....
     [DeviceType] => Android
)

2014-11-24T13:40:43+01:00 INFO: [9686] Handling SENDMAIL command with Wbxml.
2014-11-24T13:40:43+01:00 DEBUG: [9686] I  <ComposeMail:SmartReply>
2014-11-24T13:40:43+01:00 DEBUG: [9686] I   <ComposeMail:ClientId>
2014-11-24T13:40:43+01:00 DEBUG: [9686] I     SendMail-116931579868476
2014-11-24T13:40:43+01:00 DEBUG: [9686] I   </ComposeMail:ClientId>
2014-11-24T13:40:43+01:00 DEBUG: [9686] I   <ComposeMail:SaveInSentItems />
2014-11-24T13:40:43+01:00 DEBUG: [9686] I   <ComposeMail:Source>
2014-11-24T13:40:43+01:00 DEBUG: [9686] I    <ComposeMail:ItemId>
2014-11-24T13:40:43+01:00 DEBUG: [9686] I      426997
2014-11-24T13:40:43+01:00 DEBUG: [9686] I    </ComposeMail:ItemId>
2014-11-24T13:40:43+01:00 DEBUG: [9686] I    <ComposeMail:FolderId>
2014-11-24T13:40:43+01:00 DEBUG: [9686] I      F6d875398
2014-11-24T13:40:43+01:00 DEBUG: [9686] I    </ComposeMail:FolderId>
2014-11-24T13:40:43+01:00 DEBUG: [9686] I   </ComposeMail:Source>
2014-11-24T13:40:43+01:00 DEBUG: [9686] I   <ComposeMail:MIME>
2014-11-24T13:40:43+01:00 DEBUG: [9686] I     [1085 bytes of content]
2014-11-24T13:40:43+01:00 DEBUG: [9686] I   </ComposeMail:MIME>
2014-11-24T13:40:43+01:00 DEBUG: [9686] I  </ComposeMail:SmartReply>
2014-11-24T13:40:43+01:00 ERR: Server does not support binary message data.

Here are some details of the problematic mail i try to answer (some  
parts stripped for privacy):
##### start
From: someone <... at ...>
To: Joerg Pulz <Joerg.Pulz at frm2.tum.de>
Date: Mon, 24 Nov 2014 13:20:14 +0100
Subject: .....
Thread-Topic:.....
Thread-Index: AdAH4P4h3JsrvGu7QKGY2ASKzfv5sg==
Message-ID: <375CC0FA-6150-47D6-A6ED-96F98C651DDF at kit.edu>
Accept-Language: de-DE, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: de-DE, en-US
Content-Type: multipart/alternative;
	boundary="_000_375CC0FA615047D6A6ED96F98C651DDFkitedu_"
MIME-Version: 1.0
X-Greylist: .....

--_000_375CC0FA615047D6A6ED96F98C651DDFkitedu_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

Plain message text.

--_000_375CC0FA615047D6A6ED96F98C651DDFkitedu_
Content-Type: text/html; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

HTML message text.

--_000_375CC0FA615047D6A6ED96F98C651DDFkitedu_--
##### end

I can provide the full mail directly on request.

Please reopen this ticket and increase priority, because when a mail  
is in the "Outbox" that produces the above mentioned error I'm unable  
to send any other mail using my Android device until I delete the  
problematic one from "Outbox".

Thanks for your help
Joerg