In <news:[email protected]>, Daniel <[email protected]> wrote:
> In my SM 2.0.2, when looking at this group (and, I guess, other > groups as well), the header area of messages has a line called > "References" which lets you click on the reference number to go back > one, two, or several levels at once. > > In some of the threads here, the number of levels can get large, e.g. > the thread called "Goodbye Seamonkey" gets close to thirty levels in > some branches. > > However the reference number does not increase beyond 21, i.e. the > 22nd msg has refs 1 to 21, the 23rd msg has refs 1 to 21, the 24th > has...... > > Is there some setting that limits the reference string to 1 to 21?? > Can it be changed to allow 2 to 22, 3 to 23, 43 to 63, etc to be > displayed?? When the References header becomes large enough, some clients start removing some of the message-ids from it, but what you describe should never happen. The 23rd message in a branch should at least have the mid of the OP and the mid of its parent (the 22nd message). Some of the mids in between may be dropped. Why ever drop any mids? A line of a message sent via NNTP can't be more than 1000 characters (998 plus the CR/LF). To stay within that limit, clients that put the entire References header on one line have to throw away some mids once there are too many of them. If some have been dropped, there's no way to get to them from the current message -- you'd have to go back up the thread to a post that still has them in its References header. There is a better solution, header "folding", which allows a header to span multiple lines. Until TB/SM implement that, they're going to have to keep throwing away mids when References gets too big. Example of folding: <http://al.howardknight.net/msgid.cgi?ID=126603122100> SM/TB actually have a bug that prevents them from handling folded headers correctly -- when they unfold the headers, they leave a lot of whitespace that shouldn't be there. Example: <http://al.howardknight.net/msgid.cgi?ID=126603147200>. (At least one other client's author has had to update his code to deal with those bad headers SM/TB sends.) -- »Q« /"\ ASCII Ribbon Campaign \ / against html e-mail X <http://asciiribbon.org/> / \ _______________________________________________ support-seamonkey mailing list [email protected] https://lists.mozilla.org/listinfo/support-seamonkey
