----- Forwarded message from [EMAIL PROTECTED] -----
Date: Thu, 22 Feb 2007 15:51:09 -0700
From: Kevin Konowalec <[EMAIL PROTECTED]>
Subject: MIME weirdness followup
To: [EMAIL PROTECTED]
Okay I figured out what the problem was. Someone had put the line
fixes we proposed for Ticket #4753 into production and that's what
caused the problem. While it fixes the attachment issue it also
mungs with the message. I noticed that #4753 has been resolved in
the bugtracker so I can only assume there was more added than just
commenting out the lines in horde/lib/Horde/MIME/Part.php and horde/
imp/lib/MIME/Contents.php for it to work.
From: Webmail Administrator <[EMAIL PROTECTED]>
Date: February 22, 2007 10:19:21 AM MST (CA)
To: [email protected]
Subject: MIME weirdness
Horde: 3.1.2
Imp: H3 (4.1.2)
Suddenly out of nowhere I'm getting a rash of users complaining
about mime-encoding problems when using Imp. They say there's all
kinds of '=A0' and '=20' and the like in messages they open in Imp.
When they open the same message in another client there's no
problem. I haven't made any changes to the system in a LONG time.
Has anyone else seen something like this happen and if so what has
to be done to fix it?
As an addendum I opened up a message that I saw this happening in
and it says that there are alternative parts for the message. When
I click it (text/plain) it opens up perfectly fine. Something else
I noticed is that there is a section that is set as quoted (marked
by '>' at the beginning of the lines) which does not show up in the
message as displayed by imp. Something's definitely gone weird.
----- End forwarded message -----
-chuck
--
"we are plastered to the windshield of the bus that is time." - Chris
--
IMP mailing list - Join the hunt: http://horde.org/bounties/#imp
Frequently Asked Questions: http://horde.org/faq/
To unsubscribe, mail: [EMAIL PROTECTED]
