On Mon, 15 Nov 1993  16:18:00 EDT "John F. Chandler" <[log in to unmask]>
said:
 
>This  sounds bizarre.  Maybe Marty  wasn't looking  for this  particular
>problem, but he *did* mention noticing  that the first three messages of
>the aberrant index were (would have been) dated from the preceding month
>and had apparently been delayed en route to LISTSERV. Surely, this is an
>interesting coincidence and worth considering as a possible symptom of a
>*third* way of getting mismatched message numbers.
 
But neither the database code nor the  index code care about the month in
the  'Date:' field  of  the  messages. The  database  driver indexes  the
messages in their order of appearance  in the individual log files, which
are sorted by CMS filetype, ie in  their order of arrival. A message sent
in October but arriving in November  is written to the November log file.
The same  code paths  are selected  whether the message  was sent  in the
previous or current  month. The index code uses the  temporary file where
information is recorded as messages arrive.
 
  Eric