Duncan posted on Tue, 23 Sep 2025 07:17:20 -0000 (UTC) as excerpted: > So pan has had a longstanding bug or "undocumented feature" related to > fetching headers in the context of crossposted messages. I've not > reported the bug as I've never felt I had a good enough grasp on the > problem to report it properly[. ...]
> The only thing I can figure out that could plausibly trigger this > behavior is if the originally-tracked group is busier and thus has > higher xref (I think that's the header) numbers, and pan is somehow > treating the high- water numbers in the busier group as applying to the > less-busy/lower- number group as well. If that's the case, pan would > always see the higher high-water-mark of the busier group and thus > always think there were no new headers to download in the less busy > group, because it's using the higher high-water-marks for the busier > group instead of the lower ones for the group I'm attempting to view. Hmm... The more I think about it, the more I suspect that's _exactly_ the problem I'm seeing: with crossposts to both groups, pan's using the busier group's higher high-water-mark for the less busy group too, and refusing to get headers for the lower high-water-mark group because it thinks it has already seen everything. I'm surely about to crash ATM, and I make no claims to actually write code anyway, but sometimes if I can find it I can then reason out its behavior and even occasionally hack-patch a constant here or there, so I'll try to take a look anyway, within the week... -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman _______________________________________________ Pan-users mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/pan-users
