Great Circle Associates Majordomo-Workers
(October 2000)
 

Indexed By Date: [Previous] [Next] Indexed By Thread: [Previous] [Next]

Subject: Re: X Loop trapping
From: Joseph Brennan <brennan @ columbia . edu>
Date: Mon, 23 Oct 2000 10:20:22 -0400
To: SRE <eckert @ climber . org>, list-managers @ GreatCircle . COM, majordomo-workers @ GreatCircle . COM, mj2-dev @ csf . colorado . edu
Cc: @columbia.edu
In-reply-to: <4.3.1.0.20001022053531.00b9d7b0@pop.climber.org>
Reply-to: Postmaster <postmaster @ columbia . edu>



--On Sunday, October 22, 2000 05:43 -0700 SRE <eckert@climber.org> 
wrote:

> At 08:40 PM 10/17/00, A. Subscriber wrote:
>  >I have no control over this...is there any way for me to work
>  around this >and get a response from the list server?
>
> I can disable Mj2's loop trapping stuff, but that opens up other
> problems and so far no one else I'm aware of is adding X*Loop.
> I add X*Loop headers to outgoing messages, and trap them in posts,
> to keep loops from hitting the list subscribers.


I don't have Majordomo 2 yet, but the only reliable way to do this is
to put your own system's name into the X-Loop: header, to make it
unique. Relying on something as generic as "X-Loop-Detect: 1" is asking
for trouble.  If it had "X-Loop: Majordomo-myhostname.mydomain 1" then
you'd have better reason to question another host putting your host's
name and domain into their mail.

FYI, Procmail recommends putting X-Loop headers into automatic replies.

Joseph Brennan                           postmaster@columbia.edu
Academic Technologies Group, Academic Information Systems (AcIS)




References:
Indexed By Date Previous: RE: Some thoughts on qmail..
From: James Berry <james@adastra.co.uk>
Next: Re: Mj2: Re: X Loop trapping
From: SRE <eckert@climber.org>
Indexed By Thread Previous: Re: X Loop trapping
From: David Miller <justdave@a2central.com>
Next: Re: Mj2: Re: X Loop trapping
From: SRE <eckert@climber.org>

Google
 
Search Internet Search www.greatcircle.com