I've had multiple "problems" with the rr.com domain, including one
recently. They are not a real problem any more but I still notice when
they screw up, which is fairly often. They're running a buggy Micros**t
Exchange server so their users frequently cause loops when they try to
set the vacation notice facility.
You're going to have to put some loop protection "in the loop". :-)
Seriously, though, you do need to do this. One of the things I do is
log message-ids of messages and for every incoming message I look to see
if I've seen the message recently. How recently is debatable. I used
to use 2 months but now I use 4 months.
I do other things but this is the one that catches almost all the
duplicate messages. I set those aside for manual review, which is
really just so I can figure out who is dumb enough to loop messages and
unsubscribe them *with prejudice*.
There's nothing "magic" about how I do this. Outgoing messages run
through a script before alias expansion that logs the message-id.
Incoming messages run through a script, before the outgoing script, that
grabs the message-id and looks in the log file for it.
If possible you might also just setup your SMTP server to deny incoming
email from the rr.com domain. That at least will help the short-term.
Jim
On Sun, 11 Mar 2001, Mitchell Leben wrote:
Date: Sun, 11 Mar 2001 12:21:21 -0600 (CST)
From: Mitchell Leben <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: List owner needs help dealing with mail loop
Hello list managers,
I have a problem which I cannot lick by myself, thought I'd toss it to the
list.
Since 3-5-01 I have a mail loop on three of my mailing lists. Subscribers
are receiving three and four copies of each message, and the problem
continues. The common element is the *.rr.com mail servers. Below is the
header information from one of the duplicates.
The best I can tell, something odd is going on here: (see full headers at
the end of this message)
Received: from mail pickup service by Mail.austin.rr.com with Microsoft
SMTPSVC;
Fri, 9 Mar 2001 01:38:44 -0600
Received: from sm4.texas.rr.com ([24.93.35.211]) by Mail.austin.rr.com
with Microsoft SMTPSVC(5.5.1877.537.53);
Mon, 5 Mar 2001 21:46:18 -0600
The mail is going back and forth between mail.austin.rr.com and
sm4.texas.rr.com, after being held from March 5 till March 9?
I have asked for help from postmaster and root at various rr.com
subdomains, so far no response.
People are rapidly unsubscribing, and my mail server is grinding away on
an ever increasing load.
Any ideas are welcome, this is the worst problem I have ever had like
this. Usually I can find the offending address fairly quickly. I tried
unsubscribing several *.rr.com addresses, but the problem does not seem
specific to any one address.
Thanks.
--
-Mitch
---------- Forwarded message ----------
Return-Path: <[EMAIL PROTECTED]>
Received: from localhost (mail@localhost)
by spock.leben.com (8.9.3/8.9.3) with SMTP id PAA21909;
Sat, 10 Mar 2001 15:46:22 -0600
Received: by spock.leben.com (bulk_mailer v1.13); Sat,
10 Mar 2001 15:46:03 -0600
Received: (from majordomo@localhost)
by spock.leben.com (8.9.3/8.9.3) id PAA21653
for digicam-list; Sat, 10 Mar 2001 15:45:52 -0600
Received: from Mail.austin.rr.com (sm2.texas.rr.com [24.93.35.55])
by spock.leben.com (8.9.3/8.9.3) with ESMTP id PAA21566
for <[EMAIL PROTECTED]>; Sat, 10 Mar 2001 15:45:43 -0600
Received: from mail pickup service by Mail.austin.rr.com with Microsoft
SMTPSVC;
Sat, 10 Mar 2001 15:05:47 -0600
Received: from mail pickup service by sm11.texas.rr.com with Microsoft
SMTPSVC;
Sat, 10 Mar 2001 05:23:43 -0600
Received: from sm4.texas.rr.com ([24.93.35.211]) by Mail.austin.rr.com
with Microsoft SMTPSVC(5.5.1877.537.53);
Fri, 9 Mar 2001 10:17:14 -0600
Received: from spock.leben.com (209-44-133-26.pdq.net [209.44.133.26])
by sm4.texas.rr.com (8.10.1/8.10.1) with ESMTP id f29GHEs28746
for <[EMAIL PROTECTED]>; Fri, 9 Mar 2001 10:17:14 -0600
Received: from localhost (mail@localhost)
by spock.leben.com (8.9.3/8.9.3) with SMTP id HAA14094;
Fri, 9 Mar 2001 07:08:46 -0600
Received: by spock.leben.com (bulk_mailer v1.13); Fri,
9 Mar 2001 07:08:18 -0600
Received: (from majordomo@localhost)
by spock.leben.com (8.9.3/8.9.3) id HAA13911
for digicam-list; Fri, 9 Mar 2001 07:08:15 -0600
Received: from Mail.austin.rr.com ([24.93.35.226])
by spock.leben.com (8.9.3/8.9.3) with ESMTP id HAA13849
for <[EMAIL PROTECTED]>; Fri, 9 Mar 2001 07:08:07 -0600
Received: from mail pickup service by Mail.austin.rr.com with Microsoft
SMTPSVC;
Fri, 9 Mar 2001 01:38:44 -0600
Received: from sm4.texas.rr.com ([24.93.35.211]) by Mail.austin.rr.com
with Microsoft SMTPSVC(5.5.1877.537.53);
Mon, 5 Mar 2001 21:46:18 -0600
Received: from spock.leben.com (209-44-133-26.pdq.net [209.44.133.26])
by sm4.texas.rr.com (8.10.1/8.10.1) with ESMTP id f263kHA18607
for <[EMAIL PROTECTED]>; Mon, 5 Mar 2001 21:46:17 -0600
Received: from localhost (mail@localhost)
by spock.leben.com (8.9.3/8.9.3) with SMTP id UAA28165;
Mon, 5 Mar 2001 20:55:19 -0600
Received: by spock.leben.com (bulk_mailer v1.13); Mon,
5 Mar 2001 20:55:15 -0600
Received: (from majordomo@localhost)
by spock.leben.com (8.9.3/8.9.3) id UAA28148
for digicam-list; Mon, 5 Mar 2001 20:55:15 -0600
Received: from mta8 (mta8.srv.hcvlny.cv.net [167.206.5.23])
by spock.leben.com (8.9.3/8.9.3) with ESMTP id UAA28144
for <[EMAIL PROTECTED]>; Mon, 5 Mar 2001 20:55:10 -0600
Received: from pii350 (ool-18bcb82f.dyn.optonline.net [24.188.184.47])
by mta8.srv.hcvlny.cv.net
(iPlanet Messaging Server 5.0 Patch 2 (built Dec 14 2000))
with SMTP id <[EMAIL PROTECTED]> for [EMAIL PROTECTED];
Mon, 05 Mar 2001 21:15:24 -0500 (EST)
Date: Mon, 05 Mar 2001 21:16:45 -0500
From: Jim Reilly <[EMAIL PROTECTED]>
Subject: RE: Waterproof camera suggestions
In-reply-to: <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Message-id: <000901c0a5e3$7deb3660$2fb8bc18@pii350>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7BIT
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
Sender: [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
