Summary | boundary parameter missing in multipart messages |
Queue | IMP |
Queue Version | 4.1.3 |
Type | Bug |
State | Not A Bug |
Priority | 2. Medium |
Owners | |
Requester | zaphod (at) lpt (dot) fi |
Created | 10/27/2006 (6799 days ago) |
Due | |
Updated | 10/29/2006 (6797 days ago) |
Assigned | 10/29/2006 (6797 days ago) |
Resolved | 10/29/2006 (6797 days ago) |
Github Issue Link | |
Github Pull Request | |
Milestone | |
Patch | No |
represented there.
address this problem.
Thanks!
Taken from Michael Slusarz
headers. If you look at the lowest Received header of the attached
test message, you can see that it is incorrectly truncated. This has
probably happened to the Content-Type header as well. I noticed the
same thing with a few other headers that were continued over several
lines - only the first one appears in the message, the rest of them
disappear somewhere.
But now it seems that this is probably not a Horde bug, but an issue
with PHP. I copied the entire Horde installation tree to another
machine with an older version of PHP and there it worked like a charm.
I have been having all kinds of trouble with this particular
installation of PHP and I'm trying to install the latest snapshot of
PHP but now the installation fails with segfault at the installation
of Pear. But that's completely another story...
You shouldn't waste your time any more on this one, because now I
don't think it has anything to do with the Horde or Imp code.
Assigned to Michael Slusarz
State ⇒ Assigned
New Attachment: message source.txt
with IMP, reading them, or both? Can you upload a message example?
multiple MIME parts. I'll attach a test message that illustrates the
problem. Watch the Content-Type header. It is missing the boundary
string after the semicolon. It says simply:
Content-Type: multipart/mixed;
And because of that, no mail client can read any of the parts. If one
adds the boundary string manually to the header, it becomes readable.
For some unknown reason the boundary string never gets appended to the
Content-Type header although it appears in the body of the message.
I've tried to read through the code to pinpoint the problem, but I
just don't have enough time.
And there's also another problem with horde giving me an occasional
blank page, but that's probably PHP related as there are errors about
"too many open files" in the log...
State ⇒ Feedback
with IMP, reading them, or both? Can you upload a message example?
with apache-1.3.34+ssl_1.57 and php-5.1.6. PHP configured as follows:
./configure --with-apxs=/p/www/apache-ssl/bin/apxs --with-gettext --with-dom
--with-imap=../imap-2006.DEV.SNAP-0609091921 --with-mcrypt -with-iconv
--enable-mbstring=all --enable-mbregex --with-mysql --with-zlib
Priority ⇒ 2. Medium
State ⇒ Unconfirmed
Queue ⇒ IMP
Summary ⇒ boundary parameter missing in multipart messages
Type ⇒ Bug
users started complaining about attachments not working. I digged a
little into it and noticed that in Multipart-type MIME-messages there
is no boundary-parameter included in the Content-Type header. This
happens when sending or forwarding multipart messages.
The parts themselves do have the boundary string in place, but it is
missing from the headers.