Vince Vielhaber <vev@michvhf.com> writes:
> Looks like someone's mailer reinjected this one.
Yes, along with five others that were also about two weeks old.
I recall having noticed several other such incidents in the recent
past, all bearing headers that indicate the retransmitted messages
originally went from the mail list to one <Z.Nijmeyers@cable.a2000.nl>.
Start of reinjection of this one (note date):
Received: from hardy-1.a2000.nl ([127.0.0.1]) by hardy-1.a2000.nl (Netscape Messaging Server 3.6) with SMTP id
AAA5185; Mon, 26 Jul 1999 13:34:05 +0200
Immediately prior Received: lines:
Received: from smtp1.a2000.nl ([192.168.17.19]) by hardy-1.a2000.nl (Netscape Messaging Server 3.6) with ESMTP
idAAT19D0 for <Z.Nijmeyers@cable.a2000.nl>; Fri, 9 Jul 1999 06:48:41 +0200
Received: from hub.org ([209.167.229.1])by smtp1.a2000.nl with esmtp (Exim 2.02 #4)id 112SYe-0002lN-00for
Z.Nijmeyers@cable.a2000.nl;Fri, 9 Jul 1999 06:46:44 +0200
Received: from hub.org (hub.org [209.167.229.1])by hub.org (8.9.3/8.9.3) with ESMTP id AAA39425;Fri, 9 Jul 1999
00:40:25-0400 (EDT)(envelope-from owner-pgsql-hackers@hub.org)
This morning I sent a polite note to postmaster@cable.a2000.nl, warning
them that they've got a problem with mail looping. It promptly bounced
back with
postmaster@cable.a2000.nl: SMTP error from remote mailer after RCPT TO: <postmaster@cable.a2000.nl>: host
hardy-1.a2000.nl[192.168.17.13]: 550 Invalid recipient <postmaster@cable.a2000.nl>
(Sending to postmaster@a2000.nl instead probably won't help, since it
MX's to the same machines.)
I conclude that a2000.nl is run by a bunch of idiots who can't read
RFCs, let alone operate a mail server competently. I expect that
we will continue to get blessed with regurgitated messages until Marc
pulls any a2000.nl addresses from the mailing lists :-(
regards, tom lane