19408 - [REGRESSION]IMAP only: Message content does not display in the message pane

Status: VERIFIED INVALID

(MailNews Core :: Backend, defect, P3)

Description

[fenella]

Win_nt 4.0 (1999-11-19-09 M12)
Steps:
1. Launch messenger using the Task|Mail
2. From my IMAP account, click on the Inbox
3. Select a message.

Actual result: The message only display the header information such as:
Subject
From
Date
And the detailed such as: Return-Path, Received, Resent Date, Message ID,
X-mailer, content type...
There is a scroll bar, but it does not scroll to the body content

Expected result: It should not show the detailed information and should show the
body content.

Can not test Linux today, build not start up

This happens on IMAP, not POP

On Mac, this problem does not exists

Esther tried to re-produce it on hers. She also used nsmail-2 server, her
machine has different problem that she could not get to load her mail folder.

Comment 1

[Phil Peterson]

David, can you look at this?

Comment 2

[lchiang]

Fenella, do you have an IMAP log? What shows up in the DOS console?

Comment 3

[rickg]

Assuming we can reproduce this bug, it's definitely a PDT+ bug.

Comment 4

[David :Bienvenu]

I've never been able to reproduce this.

Comment 5

[David :Bienvenu]

I've also seen a bunch of other people read imap messages on a variety of
platforms, so I think I'll need a lot more information about how to reproduce
this before I'll be able to do anything.

Comment 6

[David :Bienvenu]

Lisa, have you ever seen this? has anyone else seen this? I tried new profile,
existing profile, all sorts of messages, I don't see this problem.

Comment 7

[lchiang]

Unfortunately, I can't try this because I have another bug where I can't even
start the program :-(

I'll take a look at Fenella's system.

Comment 8

[David :Bienvenu]

Rich, do you have any idea why you would see the extra headers, like Resent
From:, Return path, message-id in the header area? This sounds like it might be
a libmime problem, unless the imap code is giving libmime bad data, like a extra
blank line in the message. A protocol log would be quite useful.

Comment 9

[lchiang]

Due to the long (extra headers) being seen, Fenella ran into bug
http://bugzilla.mozilla.org/show_bug.cgi?id=18407. I confirmed that.

The long extra headers don't show up on Esther's system. Fenella, do you have
your pref set to display ALL headers?  Once we find out, we can resolve this bug
as a dup of 18407 and file a new bug on headers, if needed.

Comment 10

[rhp (gone)]

Sounds like bad data....but I'd like to see a screen shot to help me understand
what is going on. Can someone attach a screen shot to this bug report and I can
take a look at it.

- rhp

Comment 11

[lchiang]

Pref set to display headers as all after migration from 4.x.  Closing as
invalid.