Articles already read are newly marked as unread
Categories
(SeaMonkey :: MailNews: Message Display, defect)
Tracking
(Not tracked)
People
(Reporter: bitwise, Unassigned)
Details
User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:-1.0) Gecko/20100101 Firefox/-1.0
Steps to reproduce:
Read articles in subscribed group.
AND/OR
Marked whole group as "read".
Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:68) Gecko/20100101 Firefox/68
Actual results:
Article is marked as "read".
After a few hours (following repeated requests to the server for new articles) the same article (and a number of others) are remarked as "unread" (like any new ones).
Can keep doing this repeatedly.
(Typical small group: a few hundred articles conserved a month, 10-20 new articles per day.) I deleted the relevant .msf file to get a fresh start: no difference.
The file's authorisations are ok.
Expected results:
Nothing should have changed.
|
||
Updated•3 years ago
|
|
||
Comment 1•3 years ago
|
||
I can't remember to have seen that effect with installation of unofficial (by wg9s) De SeaMonkey 2.53.14 beta 1 pre Mozilla/5.0 (NT 6.1; Win64; x64; rv:68.0) Gecko/20100101 Firefox/68.0 Build 20220801210005 (Same with normal user Profile and newly created User Profile Default Classic Theme) on German WIN10 64bit or versions before. But will keep my eyes open.
@reporter:
Can you tell a way how to reproduce your problem reliably?
|
Reporter | |
Comment 2•3 years ago
|
||
@Rainer
I don' t know if it's reliable for other people: but I found another way to do it:
Looking at my group list I see ONE single new unread message.
I click on the group and immediately 48 previously read messages are marked as unread.
Note: I have 2.53.13 release
|
|
||
Comment 3•3 years ago
|
||
Never saw this lately. Just tried again and can't reproduce. Check add-ons. Might also be server related.
|
|
Reporter | |
Comment 4•3 years ago
|
||
The server doesn't know anything: it just supplies articles to the client as requested.
Only the client knows what it has already received and what has been read.
If the server sends every message that is has stored, it is up to the client to sort out the new ones and only display those which match the criteria chosen by the user (date...), and only mark as unread those which haven't been ( MID's registered and marked).
I have always had the same add-ons (none have anything to do with nntp) but this problem is new since upgrading from 2.49
And it is 100% reproducible - every day. I can only tell what is really new by sorting by date and ignoring all threads - unuseable.
Is this newsgroup a public one and if so, which one and on which newsgroup server?
For testing purposes, does this happen on a new profile?
|
|
||
Comment 6•3 years ago
|
||
Tried all day but unable to reproduce with news.individual.de and several newsgroups.
As IanN stated please try in a new test profile or name the server if public.
|
||
Comment 7•3 years ago
|
||
Do you have any message filter that could be doing this?
Along with testing in a new profile, can you check if it happens in the current profile if you configure a different news server and subscribe to a group there? For example, if you're not using news.aioe.org or news.eternal-september.org, you could try with one of these. (While eternal-september requires login to access most groups, you should be able to access eternal-september.* groups without logging in).
When this behaviour happens, do you get any new message(s) in SeaMonkey's error console? (Tools->Web Development->Error Console in the Mail&News window)
|
|
Reporter | |
Comment 8•3 years ago
|
||
The problem continues - this morning 6 unread mesages became 79 as soon as I selected the group.
In the blank profile 3 messages unread became 15.
(In reply to Nuno Silva from comment #7)
Thanks for your suggestions.
Do you have any message filter that could be doing this?
I have many message filters based on the sender's identity (killfile).
There is no difference in their operation with the pseudo-unread messages and it is not messages previously filtered that appear and become unread.
Along with testing in a new profile, can you check if it happens in the current profile if you configure a different news server and subscribe to a group there? For example, if you're not using news.aioe.org or news.eternal-september.org, you could try with one of these. (While eternal-september requires login to access most groups, you should be able to access eternal-september.* groups without logging in).
I will try this when I have time (I am just starting work).
The newsgroup mainly concerned is fr.bio.medecine and the server news-3.proxad.net (both public - but server requiring inscription).
When this behaviour happens, do you get any new message(s) in SeaMonkey's error console?
There are literally hundreds of warnings - but that is normal with many sites these days: many young programmers are careless and don't verify their code. Dozens of warnings were generated by "bugzilla.mozilla.org" and three errors. When I read your question I went and looked then cleared; just now (the time to write this) there are already dozens more, and six errors.
No errors from my news server. Considering the rate of new warnings and errors I can't say which (if any) could be related to the problem (there are no filters other than errors/warnings). I am only connected to Bugzilla and the flow of warnings is constant and rapid.
|
||
Updated•7 months ago
|
Description
•