| Summary | Reply from Android 4.1.2 -> BAD HEADER SECTION, MIME error: error: unexpected end of preamble |
| Queue | Synchronization |
| Queue Version | Git master |
| Type | Bug |
| State | Resolved |
| Priority | 2. Medium |
| Owners | mrubinsk (at) horde (dot) org |
| Requester | samuel.wolf (at) wolf-maschinenbau (dot) de |
| Created | 11/25/2014 (3873 days ago) |
| Due | |
| Updated | 11/25/2014 (3873 days ago) |
| Assigned | |
| Resolved | 11/25/2014 (3873 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No |
Assigned to Michael Rubinsky
State ⇒ Resolved
out today.
commit 038b6386610b0546c7b7d729abeeca0606867943
Author: Michael J Rubinsky <mrubinsk@horde.org>
Date: Tue Nov 25 01:24:58 2014 -0500
Must explicitly remove the Content-Type parameter from smart requests.
Some change in the MIME library changed the need for this apparently.
In Smart requests, the incoming Content-Type only applies to the reply
text, and not the final MIME message we construct server-side. This
used to be automatically dealt with somewhere...
Bug: 13720framework/Core/lib/Horde/Core/ActiveSync/Mail.php | 6 ++++++
1 files changed, 6 insertions(+), 0 deletions(-)
http://github.com/horde/horde/commit/038b6386610b0546c7b7d729abeeca0606867943
Horde is up-to-date.
pear install -f horde/Horde_Core-2.16.1 horde/Horde_Imap_Client-2.25.3
horde/Horde_ListHeaders-1.1.5 horde/Horde_Mail-2.4.0
horde/Horde_Mime-2.4.5 horde/Horde_Smtp-1.6.0
horde/Horde_ActiveSync-2.20.1
Not sure which one is the root cause.
Priority ⇒ 2. Medium
Patch ⇒ No
Milestone ⇒
Queue ⇒ Synchronization
Summary ⇒ Reply from Android 4.1.2 -> BAD HEADER SECTION, MIME error: error: unexpected end of preamble
Type ⇒ Bug
State ⇒ Unconfirmed
Horde show "no content", but there is content in the message source.
Found a entry from amavis:
X-Amavis-Alert: BAD HEADER SECTION, MIME error: error: unexpected end
of preamble
Any idea whats wrong?
Horde is up-to-date.