101985 - offline:News only: Disk Space pref "Do not download messages locally larger than x kb" is invoked even if the pref is not set

Status: RESOLVED WORKSFORME

(SeaMonkey :: MailNews: Backend, defect)

Description

[grylchan]

Commercial branch builds
 2001-09-19-05-0.9.4/ win nt 4.0
 2001-09-19-04-0.9.4/ linux 2.2
 2001-09-19-08-0.9.4/ mac 9.1

Spun off bug 96335. I think should be same fix but instead of
size we have to do line count?

Anyways, if you have pref "Do not download messages locally larger than x kb"
for newsgroups checked and the user downloads a newsgroup with messages greater
than x kb, the result is all messages get downloaded instead of messages
only less than x kb.

Comment 1

[Hans Schleichert]

A similar bug exists in version 2001-10-11-17 on WinNT, for POP mail accounts.
Check the box at "do not download messages...", enter a number in the kB field,
then uncheck the box again. This results in messages larger than the specified
number not being downloaded. At least true for a mail account that is NOT the
default account.

Comment 2

[grylchan]

Adding note to commentator, please try a more current build.
Using 2002011803 build, the disk space pref works fine in pop mail
accounts. Behaves as expected when checked/not checked.

Comment 3

[Hans Schleichert]

You have a point. However, as I reported in bug 118783, every single nightly
build since the 0.9.7 milestone crashes when I try to run it. True for the most
recent build (23 Jan) too.

Comment 4

[Robert Kaiser]

This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 5

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.

Because of this, we're resolving the bug as EXPIRED.

If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.

Query tag for this change: EXPIRED-20100420

Comment 6

[Karsten Düsterloh]

WFM.