Alex Strickland wrote:
Daniel wrote:
I think this could be this bug here:
https://bugzilla.mozilla.org/show_bug.cgi?id=540288
Dom
Spot on, Dominique, I've just added myself to the bug.
I looked for a bug report before I originally posted, but couldn't find
it :( Good catch, and thank you dominique.
Do you think maybe it is really three bugs?
1. The reproducible behaviour the original bug reporter showed.
2. The not so reproducible behaviour when the connectivity is just so
bad that NNTP doesn't work, but SM/TB does not tell the user.
3. The failure to repopulate when the cache is empty after something (1.
or 2.) has gone wrong?
Regards
Alex
Strikes me, something tricks SM/TB into thinking it has received the
message, but in fact it has received a blank message, so it's not a
connectivity thing (2) and if it (SM/TB) believes it has received a
valid message, why should it try to repopulate (3)??
Your number 1's the problem.
IMHO, of course.
Daniel
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
