On Tue, Sep 09, 2008 at 03:09:16PM +0200, Matus UHLAR - fantomas wrote:
> On 09.09.08 14:36, Janne Peltonen wrote:
> > But on the other hand... If IMP knows it's unable to view text/html
> > parts (because of its configuration), shouldn't it choose the text/plain
> > part of a MIME multipart / alte
On 09.09.08 14:36, Janne Peltonen wrote:
> But on the other hand... If IMP knows it's unable to view text/html
> parts (because of its configuration), shouldn't it choose the text/plain
> part of a MIME multipart / alternative message? Of course, as it can
> view the text/html parts, only not inlin
On Mon, Sep 08, 2008 at 11:04:47AM -0600, Michael M Slusarz wrote:
>> I (or one of my colleagues) will probably file a proper bug report once
>> we got a permission from the user to use her message as an example. We
>> tried to render the message using IMP 3.0, Pine, Mutt and Mozilla
>> thunderbird
Quoting Janne Peltonen <[EMAIL PROTECTED]>:
...OH NO. I just re-read the problem report, and that's exactly what
that user had tried. And the real problem was, the user couldn't see the
message body (which, indeed, was in html) at all in the Message view,
she only saw the headers (containing the
On Mon, Sep 08, 2008 at 11:59:23AM -0400, Chuck Hagenbuch wrote:
> Quoting Janne Peltonen <[EMAIL PROTECTED]>:
>
>> This is probably a stupid question and I've just been too tired to
>> understand what would be the right place to look for instructions, but -
>> how do I enable URL parsing & renderi
