282979 - Need info regarding size of truncated messages

Status: NEW

(SeaMonkey :: MailNews: Message Display, enhancement)

Description

[ssfeit]

User-Agent:       Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.7.3) Gecko/20040910
Build Identifier: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.7.3) Gecko/20040910

The notification that a message has been truncated because it exceeds the limit
set in the preferences gives no clue as to the size of the monster lurking on
the server waiting to be downloaded.  As a result, it doesn't give the user an
idea as to whether he wants to download the whole package then or wait until later.

If i have my limit set at 300k and it is 500k, I might decide to go for it. 
However, if it is 5 MEGs, I might want to get back to it after I have looked at
the rest of my incoming mail.  As it now stands, there is no way of knowing
until you actually go after it.

Reproducible: Always

Steps to Reproduce:
1.Set preferences to limit message size to the number of your choice.
2. Wait for an incoming message that exceeds the limit.
3.

Actual Results:  
Got a message indicating that there is an oversize message waiting for me but it
doesn't give me a clue as to how big it is.

Expected Results:  
If the software is able to determine if the message exceeds the limit, I am
assuming that it knows how big it is in total. 

Putting something in the truncation notification that indicates how big it is
would be an elegant touch.

Comment 1

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 2

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.

Comment 3

[:aceman]

Nice catch!