Summary | ActiveSync - Server does not support binary message data |
Queue | Synchronization |
Queue Version | FRAMEWORK_5_2 |
Type | Bug |
State | Resolved |
Priority | 1. Low |
Owners | mrubinsk (at) horde (dot) org |
Requester | samuel.wolf (at) wolf-maschinenbau (dot) de |
Created | 03/06/2015 (3810 days ago) |
Due | |
Updated | 06/02/2015 (3722 days ago) |
Assigned | 05/29/2015 (3726 days ago) |
Resolved | 06/01/2015 (3723 days ago) |
Github Issue Link | |
Github Pull Request | |
Milestone | |
Patch | No |
https://github.com/horde/horde/commit/f7641fe6054d9d0378806f0d139cbe16e678ae2f
State ⇒ Resolved
release on Monday since I'm working another unrelated issue I hope to
include in the release.
commit 73d396d723ece691e3b034edd8f01b1247a27a64
Author: Michael J Rubinsky <mrubinsk@horde.org>
Date: Mon Jun 1 00:22:43 2015 -0400
If we fail do to a missing capability, retry after rebuilding the part.
Some clients send user uneditable text (such as auto-generated html
signatures) that exceed the maximum line length, thus require
BINARYMIME to be supported in the sending server. Check that any
failures are not due to this by trying again after rebuilding
the MIME part sent from the client.
Fix for
Bug: 13901framework/Core/lib/Horde/Core/ActiveSync/Mail.php | 33
+++++++++++++++++++++
1 files changed, 33 insertions(+), 0 deletions(-)
http://github.com/horde/horde/commit/73d396d723ece691e3b034edd8f01b1247a27a64
to fix this on the horde side.
State ⇒ Assigned
to fix this on the horde side.
part to wrap the text/html data, as long as the message isn't signed
or encrypted.
line breaks (CR/LF). 8Bit data MUST be less than 998 characters per
line. Anything longer MUST be treated as binary. (RFC 2045 [2.8]).
This MIGHT be the way you entered your HTML signature yourself, or
maybe it's the client's fault. If you are able to manually enter the
HTML for the HTML signature, be sure to add some linebreaks in it.
in the debug log.
Text format is plain, but device send anyway in HTML :-(
I guess it is time for a new device, because it make no sense for me
to fix this on the horde side.
State ⇒ Feedback
The client is sending the HTML data as one long line without any line
breaks (CR/LF). 8Bit data MUST be less than 998 characters per line.
Anything longer MUST be treated as binary. (RFC 2045 [2.8]).
This MIGHT be the way you entered your HTML signature yourself, or
maybe it's the client's fault. If you are able to manually enter the
HTML for the HTML signature, be sure to add some linebreaks in it.
Either way, we should be able to capture the error and retry once
after searching for and truncating any lines in text/html parts. Would
rather not mangle the pure message from the client unless absolutely
necessary though.
error happens.
Send you by mail the log file.
Is the <br> after </html> the problem?
[...] <!--a75c305b1c0a6022--></body></html><br>
full message source in the log.
error happens.
full message source in the log. If you can get that and send it to me,
I can try to see if there is any workaround.
FWIW, my email server is also missing that extension, so I should be
able to duplicate the error if I have a sample message.
(RFC 6152). Not 100% sure what part of the message requires it, since
I don't have the raw message, but that is what the error code is
telling you.
or binarymime extensions when they are required.
Trying 127.0.0.1...
Connected to 127.0.0.1.
Escape character is '^]'.
220 mailserver.intern ESMTP Postfix (Debian/GNU)
EHLO mailserver.intern
250-mailserver.intern
250-PIPELINING
250-SIZE 157286400
250-VRFY
250-ETRN
250-STARTTLS
250-ENHANCEDSTATUSCODES
250-8BITMIME
250 DSN
QUIT
221 2.0.0 Bye
[...]
2015-05-26T10:50:42+02:00 DEBUG: [14623] I </ComposeMail:ClientId>
2015-05-26T10:50:42+02:00 DEBUG: [14623] I <ComposeMail:MIME>
2015-05-26T10:50:42+02:00 DEBUG: [14623] I [2801 bytes of content]
2015-05-26T10:50:42+02:00 DEBUG: [14623] I </ComposeMail:MIME>
2015-05-26T10:50:42+02:00 DEBUG: [14623] I </ComposeMail:SendMail>
2015-05-26T10:50:42+02:00 INFO: [14250] Maximum memory usage for
ActiveSync request: 23855104 bytes.
2015-05-26T10:50:42+02:00 ERR: Server does not support binary message data.
2015-05-26T08:50:42+00:00 INFO: [14248]
Horde_Core_ActiveSync_Driver::authenticate() attempt for samuel
2015-05-26T08:50:42+00:00 INFO: [14385]
Horde_Core_ActiveSync_Driver::authenticate() attempt for samuel
2015-05-26T10:50:42+02:00 INFO: [14248] PING request received for user samuel
2015-05-26T10:50:42+02:00 INFO: [14248] Device entry exists for
HTCXXXXXX, updating userAgent and version.
[...]
I found no way to copy the message from the device (move to an other
folder doesn't work).
@ Mike, I send you a screenshot from the message (sorry, I think this
does not help, or?).
Interesting was, as soon I remove the signature the mail was send
successfully.
State ⇒ No Feedback
or binarymime extensions when they are required. The question is
what about that email requires those extensions? Without seeing the
email data it's hard to say. Are you sending to an EAI (Email
Address Internationalization) address? It would be helpful to see
the raw
Looking, but do not found anything expected normal text in this mail.
I guess it make no sense to search the problem with this information,
please close this ticket.
If I have the problem again I will provide more informations on this ticket.
Assigned to Michael Rubinsky
State ⇒ Feedback
ERR: Server does not support binary message data.
or binarymime extensions when they are required. The question is what
about that email requires those extensions? Without seeing the email
data it's hard to say. Are you sending to an EAI (Email Address
Internationalization) address? It would be helpful to see the raw
email data of such an email.
Priority ⇒ 1. Low
State ⇒ Unconfirmed
New Attachment: ActiveSync_Debug.txt
Patch ⇒ No
Milestone ⇒
Queue ⇒ Synchronization
Summary ⇒ ActiveSync - Server does not support binary message data
Type ⇒ Bug
a text mail over ActiveSync, debug log attached.
I have no idea what's wrong with this mail, was a new mail over the
smartphone without a attachment.
Found this in the logfile:
ERR: Server does not support binary message data.