On Tue, 23 Oct 2001 20:32:06 EDT, Nelly Yusupova <[log in to unmask]>  said:
> We have not done anything on the server for weeks now.  That's why there is
> no explanation for this behavior.

Al is correct in his statement that this is usually indicative of a
spool area being restored from backup tapes.  However, I can think
of another failure mode (which I've seen before):

User sets up a brain-dead forwarding/filtering scheme that reposts
stuff back to the list it came from.  Happens all the time, but usually
gets caught by Listserv's CRC checker in the loop detector, where it
is returned with a nice "This appears to have been posted before".

Sometimes the forwarding is brain-dead enough to leave the original
To:/From: intact (which is loads of fun when it re-injects the mail
with a From: the list owner who posted it, not From: the idiot causing
the mail loop).

And sometimes, the idiot user goes on vacation for a month and doesn't
check his mail - so when he finally DOES check, the mail gets bounced
back, and by the time it gets there, the CRC cookies have all gone
quite stale, so the item gets re-posted.

If you can dig up a *complete* copy of one of the repeated posts,
complete with the Received: lines, we could probably tell in greater
detail what happend.

                                Valdis Kletnieks
                                Operating Systems Analyst
                                Virginia Tech