From: Paul Haldane (Paul.Haldane@newcastle.ac.uk)
Date: Tue Jun 15 1999 - 04:21:06 CDT
On Mon, 14 Jun 1999, Otis Gospodnetic wrote:
> I've noticed this weird behaviour when I use the latest HM.
I'm not sure I'd call it wierd :-> Hypermail is complaining because the
messages in the archive don't have message-ids. See previous discussion
on this list for why hypermail prefers to use the real msgids.
> When a message sent to a mailing list returns to sender (majordomo-owner
> eventually) the message also contains all the HM messages (example below).
> This never used to happen before (HM 2.0b3) until I switched to the latest
> HM.
>
> Is this a bug?
Nope - it's a feature (at least the detection of missing/duplicate msgids
is).
> It's not preventing things from functioning properly, it's just that
> majordomo-owner's mailbox gets filled with multiple 200K messages in my
> case...
It would be trivial for hypermail not to let the user know when it was
taking actions like this (replacing duplicate msgids, adding new msgids to
messages with no msgid). I would make this optional as there may be those
who do want to archive all messages (even apparent duplicates/invalid
messages) but do want to be told when such a message appears.
> Is there anything I can do to prevent this from happening?
You've got the source - you can comment out the printf statements that
produce the messages. Or you could run hypermail from within a script and
use grep to discard the error messages you don't want to see.
Paul
> message 0: Message-ID missing, using 929376531.0000@hypermail.dummy instead.
> message 2: Message-ID missing, using 929376531.0001@hypermail.dummy instead.
> message 3: Message-ID missing, using 929376531.0002@hypermail.dummy instead.
...