Great Circle Associates Majordomo-Workers
(October 1998)
 

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

Subject: Re: Quiet in here
From: Oliver Xymoron <oxymoron @ waste . org>
Date: Fri, 16 Oct 1998 22:06:35 -0500 (CDT)
To: Jason L Tibbitts III <tibbs @ hpc . uh . edu>
Cc: majordomo-workers @ GreatCircle . COM
In-reply-to: <ufapvbr7vig.fsf@sina.hpc.uh.edu>

On 16 Oct 1998, Jason L Tibbitts III wrote:

> >>>>> "OX" == Oliver Xymoron <oxymoron@waste.org> writes:
> 
> OX> Not true in general - imagine a subject marker "foo" - shall we remove
> OX> that from all subject lines?
> 
> Duh, now I see what you mean.  Yes, that is a problem, but it's mostly
> solved by making the prefix odd enough.  How often does "[Prefix]:" appear
> on a regular message when it's not really the prefix?  (And even if it did
> appear, I probably wouldn't mind having it stripped anyway.)
> 
> OX> Hmmm... bouncing is one solution, but the solution of modifying the
> OX> headers is probably preferable sometimes.
> 
> If I send a message somewhere and it does somewhere else (or at least, to
> some places and not others) and I'm not informed about it, I'm going to get
> pissed.  But that's just me; I generally try to make sure I know where I'm
> sending messages.  Lots of people don't.

The message goes where you sent it. But recipients on lists that
remove other lists from the headers only see it addressed to a single
list. 
 
> OX> The problem arises when user-b only on list-2 replies without editing
> OX> the header, and leaves the list-1 owner to decide whether to approve
> OX> it, if the list bounces non-member submissions.
> 
> Were I such a list owner, I would simply send to the bit bucket (using an
> access rule, of course) any crossposted message to my closed list.

And that's what I tend to do. But there's also the case where there is a
large intersection of readership on list-1 and list-2 and crossposted
threads tend to live a long time.

> However, I can see the utility for something like this and I'd be
> interested to know what you come up with.
> 
> One first approximation to this is to add To: and CC: to skip_headers
> (which is now a per-list config variable instead of a hardcoded string in
> resend) and add To: list-name to message_headers.  Of course, this removes
> legitimate CC's, perhaps to people who aren't members.  It does have some
> utility, however.

I'm going to work on a MJ1.9x patch then (cuz it will be a while before 
I can put 2.0 into production and I could use this feature on a few
dozen lists right now) that breaks up To: and Cc: lines and removes
offending entries. 

--
 "Love the dolphins," she advised him. "Write by W.A.S.T.E.." 




Follow-Ups:
References:
Indexed By Date Previous: Re: Quiet in here
From: Jason L Tibbitts III <tibbs@hpc.uh.edu>
Next: Re: Virtual Server Install Prob.
From: Jason L Tibbitts III <tibbs@hpc.uh.edu>
Indexed By Thread Previous: Re: Quiet in here
From: Jason L Tibbitts III <tibbs@hpc.uh.edu>
Next: Re: Quiet in here
From: Jason L Tibbitts III <tibbs@hpc.uh.edu>

Google
 
Search Internet Search www.greatcircle.com