Digest message count incorrect in 2.0.6

Bug #265819 reported by Bryce Harrington
2
Affects Status Importance Assigned to Milestone
GNU Mailman
Invalid
Medium
Unassigned

Bug Description

In digests, the # of messages reported does not match
the actual number of messages contained in the digest.

Take, for example, this digest :
Cgl_proof_subgroup digest, Vol 1 #130 - 14 msgs
which has :
Today's Topics:

   1. RE: Re: CGL-WG PoC-sg : Feature Sets & Ho
       t Device Identity ([Cgl_proof_subgroup] Proposed
FS list) (Randy.Dunlap)
   2. RE: Re: CGL-WG PoC-sg : Feature Sets & Ho
       t Device Identity ([Cgl_proof_subgroup] Proposed
FS list) (Perez-Gonzalez,
Inaky)
   3. RE: Re: CGL-WG PoC-sg : Feature Sets & Ho
       t Device Identity ([Cgl_proof_subgroup] Proposed
FS list) (Mika Kukkonen)
   4. Re: 2.4 v. 2.5 (was RE: [Cgl_proof_subgroup] Re:
CGL-WG PoC-sg :
       Feature Sets & Ho t Device Identity
([Cgl_proof_subgroup] Proposed FS
       list)) (Mika Kukkonen)
   5. Re: 2.4 v. 2.5 (was RE: [Cgl_proof_subgroup] Re:
CGL-WG PoC-sg :
       Feature Sets & Ho t Device Identity
([Cgl_proof_subgroup] Proposed FS
       list)) (Randy.Dunlap)
   6. RE: Re: CGL-WG PoC-sg : Feature Sets & Ho
       t Device Identity ([Cgl_proof_subgroup] Proposed
FS list) (Randy.Dunlap)

6 messages, not the 14 claimed by the subject.
In general, all the lists seem to double-count some
messages. If the digest only
contains one or two messages, the subject seems to be
correct, but it is less and
less accurate as the message count increases.

Perhaps it is counting messages with wrapped subject
lines as 2+ messages?

This has also been reported elsewhere:

http://mail.python.org/pipermail/mailman-users/2001-February/009697.html

[http://sourceforge.net/tracker/index.php?func=detail&aid=656042&group_id=103&atid=100103]

Bryce Harrington (bryce)
Changed in mailman:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.