Date: 26 Jul 2001 15:43:27 -0400
From: stanislav shalunov <shalunov(_at_)internet2(_dot_)edu>
Message-ID: <87itgf5vds(_dot_)fsf(_at_)cain(_dot_)internet2(_dot_)edu>
| 3
<3652(_dot_)996076219(_at_)brandenburg(_dot_)cs(_dot_)mu(_dot_)OZ(_dot_)AU>
| 3
<2986(_dot_)996071361(_at_)brandenburg(_dot_)cs(_dot_)mu(_dot_)OZ(_dot_)AU>
That's me. That is, that's my laptop. It runs sendmail 8.11.0
with default timeouts - but being a laptop, there's no guarantee
at all that it will be hanging around for an hour for a message to
get delivered. (And yes, it delivers directly to the MX target,
I don't go through local relays whenever I can avoid it).
But ...
Those messages went nowhere near ietf.org they were sent to the ipngwg
list (ipng(_at_)sunroof(_dot_)eng(_dot_)sun(_dot_)com).
What's more the messages left brandenburg only once. I have the logs..
Those duplicates were caused by a system receiving mail from the ipng list
and returning it to the list again.
If you looked at them, that was obvious from the headers. Even more than
that, the 2nd of those actually contained this same answer to this same
question, part of it was a reply to someone who asked why the duplicates
were happening.
I suspect that all the messages you saw with 3 copies were from the same
problem (I have no idea if it is still happening, I filter duplicates,
and don't bother to count them) - the "3" is because that's how long it
took for the Received header loop protection to eventually drop the message.
Could we please stop bickering about mail agent behaviour, and let us all
go back to collecting all the stuff that this virus has been kind enough to
send our way (so far I have DES keys, project proposals, and quite a bit
of noise - wedding pictures, prayers, ...). It is amazing what having
a few very well publicised email addresses will attract from those poor
unfortunates running trashware from microtrash.
kre