| Summary | Server does not support binary message data |
| Queue | Horde Framework Packages |
| Type | Bug |
| State | Resolved |
| Priority | 1. Low |
| Owners | mrubinsk (at) horde (dot) org |
| Requester | aaronp (at) critd (dot) com |
| Created | 04/08/2016 (3373 days ago) |
| Due | |
| Updated | 03/26/2019 (2291 days ago) |
| Assigned | 05/27/2016 (3324 days ago) |
| Resolved | 06/14/2016 (3306 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No |
New Attachment: view.txt
happen again for me with the latest Horde suite as of today. In
particular, the attached message will stall-out an apache process when
submitted as spam using the email/digest method, and will report the
binary error like the original bug report when submitted as
email/redirect method.
Many of our users have received this message, and it's caused us some
trouble with locked-up apache processes. We've temporarily switched to
use the null spam driver until this gets resolved.
Queue ⇒ Horde Framework Packages
State ⇒ Resolved
Taken from
commit be112497921ae5edbd12d14f754674eec8b7b10a
Author: Michael J Rubinsky <mrubinsk@horde.org>
Date: Tue Jun 14 12:12:06 2016 -0400
Bug: 14324Be more graceful with rfc822/message attachment failures.If the message fails to send, check that it's not because of a broken
rfc822/message attachement - most likely a too long header line. This is
done by re-encoding the attachment as a base64 encoded
application/octet-stream part. Not ideal, but we don't want to alter the
original message in anyway, and this at least allows it to be forwarded.
framework/Mime/lib/Horde/Mime/Part.php | 53
++++++++++++++++++++++++++++++++++
1 file changed, 53 insertions(+)
http://github.com/horde/horde/commit/be112497921ae5edbd12d14f754674eec8b7b10a
specifically the 'List-Unsubscribe' header, which breaks the 998
maximum length for 8bit data.
Still not sure how to work around/deal with this though.
State ⇒ Assigned
tidy), but I can reproduce the SMTP error.
New Attachment: 13 Projects to Help You Escape to Nature.eml
directly to our test account. I've attached a complete copy by viewing
the email in IMP, clicking on the plus symbol, and selecting Save.
This fresh example is giving us the same problems (described below),
which is to say it cannot be forwarded using our SMTP servers. Also,
all the links after the header text, which for this example is "13
Projects to Help You Escape to Nature", are not clickable. All the
images are clickable in Thunderbird.
State ⇒ Feedback
like it's simply the content of one of the mime parts.
State ⇒ Assigned
Assigned to
Priority ⇒ 1. Low
Type ⇒ Bug
Summary ⇒ Server does not support binary message data
Queue ⇒ IMP
Milestone ⇒
Patch ⇒ No
New Attachment: instructables.txt
State ⇒ Unconfirmed
http://marc.info/?l=imp&m=146011321630966&w=2
Basically we've found an HTML message that won't render correctly in
Horde5/IMP6, but does seem to render correctly in most or all other
clients including Horde3/IMP4. This message also refuses to be
forwarded, as it complains that "Server does not support binary
message data". I think it's related to
ticket 13901.We're using SMTP, and our SMTP servers are running sendmail 8.15.2. I
don't think sendmail supports BINARYMIME. Here's what it does support:
250-ENHANCEDSTATUSCODES
250-PIPELINING
250-8BITMIME
250-SIZE 28940698
250-DSN
250-AUTH LOGIN PLAIN
250-STARTTLS
250-DELIVERBY
250 HELP
I've attached the unencoded message that was forwarded to me. I'm
prepared to blame the original sender, but I think it's strange that
no other client seems to have the same issue. Thoughts?