128845 - Add an "Automatically download new message headers" option for newsgroup server

Status: RESOLVED FIXED

(MailNews Core :: Networking: NNTP, enhancement)

Description

[Pratik]

Currently, Mozilla does not download new newsgroup headers while checking for ng
postings. Can we have an option "Automatically download new message headers"
under Server Settings->Check for new messages every x minutes. This option would
be enabled only if "Check for new messagges.." is checked.

The current implementation leads to the following problem

1. You're reading n.p.m.general and have "Check for new messages" enabled.
2. Mozilla decides to check for new ng postings and sees that there are 3 new
postings.
3. The count in account pane gets updated but you wil not be able to see those
ng messages until you click on Get messages or press Ctrl-T or go to another ng
and come back to n.p.m.general

With the requested option checked, Mozilla would download the headers.

More discussion regarding this can be found in the threads "Praise from Caesar,
and a Suggestion" in n.p.m.general and n.p.m.mail-news

Also, I'm not sure if there should be a prf for this or if this should be the
default behaviour. Whichever seems appropriate should be implemented.

Comment 1

[Stewart Gordon]

Indeed, it would be a nice feature.  But one thing needs to be considered.  At
least as an option, it should not automatically download headers in the 'group
you are actually in at the time.

Otherwise, it would break some people's way of Usenet, including mine, which is
to look through the threads, read some and hold K to ignore the rest.  If new
headers are going to spontaneously come in halfway through the process, which
may include followups on my watched threads, then they will be lost.

Comment 2

[(not reading, please use [e-mail] instead)]

sorry for the spam.  making bugzilla reflect reality as I'm not working on these bugs.  filter on FOOBARCHEESE to remove these in bulk.

Comment 3

[Serge Gautherie (:sgautherie)]

Filter on "Nobody_NScomTLD_20080620"

Comment 4

[Joshua Cranmer [:jcranmer]]

Bug 311774 has essentially fixed this bug.