Open Bug 679667 Opened 13 years ago Updated 11 years ago

Headers-only messages are not distinguishable from messages which have been downloaded

Categories

(SeaMonkey :: MailNews: Message Display, enhancement)

enhancement
Not set
normal

Tracking

(Not tracked)

UNCONFIRMED

People

(Reporter: davian818, Unassigned)

Details

User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.1; Trident/4.0; Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1) ; .NET CLR 2.0.50727; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729; .NET CLR 1.1.4322; .NET4.0C)

Steps to reproduce:

Downloaded header for message.


Actual results:

Incomplete message has the same icon as normal one.


Expected results:

It should be clearly shown as inclomplete message.
Karsten, we have no such provisions for this in UI, correct? 
Would we even want/accept such a thing?
 
I don't recall ever seeing a request like this before.
Summary: Headers-only messages are not distinguishable → Headers-only messages are not distinguishable from messages which have been downloaded
On which version was this seen? MSIE is of no interest to Mozilla developers, and SeaMonkey 2.2 is obsolete. Version → Trunk on the assumption that this is ongoing behaviour, which started at some point lost in the mists of time (Netscape 4 or earlier, maybe), and which never ceased to be. Please correct me if I'm wrong.

There are messages (usually spam) which are sent without a body; I suppose this bug report is not about _that_ kind of headers-only messages. Otherwise, I don't use IMAP, and I have SeaMonkey Mail configured to download the full headers & body of POP, MoveMail and RSS/Atom messages. About NNTP newsgroup messages I am less sure, but I indeed don't see any difference between messages which have been fully downloaded and those (if any) only whose /headers/ have been downloaded.
Severity: normal → enhancement
Component: MailNews: General → MailNews: Message Display
OS: Windows XP → All
Hardware: x86 → All
Version: SeaMonkey 2.2 Branch → Trunk
You need to log in before you can comment on or make changes to this bug.