>> The address "drblade@dux.isec.pt" is subscribing to lists for the
>> explicit purpose of forwardinFrom list-managers-owner Thu Dec 5 07:33:40 1996
Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id HAA29667 for list-managers-outgoing; Thu, 5 Dec 1996 07:01:43 -0800 (PST)
Received: from aamc.org (wpo.aamc.org [143.220.26.49]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id HAA29650 for <list-managers@GreatCircle.COM>; Thu, 5 Dec 1996 07:01:34 -0800 (PST)
Received: from AAMC-Message_Server by aamc.org
with Novell_GroupWise; Thu, 05 Dec 1996 09:51:53 -0500
Message-Id: <s2a69b39.026@aamc.org>
X-Mailer: Novell GroupWise 4.1
Date: Thu, 05 Dec 1996 10:02:50 -0500
From: David Rodbard <DRODBARD@aamc.org>
To: list-managers@GreatCircle.COM
Subject: How to prevent mail-loops with majordomo?
Sender: list-managers-owner@GreatCircle.COM
Precedence: bulk
I would very much appreciate advice re: how to protect against mail-loops when
using majordomo in the "reply to list" mode? (A number of our list owners and
subscribers prefer the "Reply to List" option to the "Reply to Sender Only"
option).
Is there a way to automatically detect and abort a mail-loop in the absence of
list-owner or operator intervention (e.g. at night and on weekends)?
Thanks.
|
|
