Great Circle Associates Majordomo-Workers
(November 1996)
 

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

Subject: Re: Return Loops
From: Jason L Tibbitts III <tibbs @ hpc . uh . edu>
Date: 10 Nov 1996 10:27:02 -0600
To: majordomo-workers @ greatcircle . com
In-reply-to: Brock Rozen's message of Sun, 10 Nov 1996 04:09:46 -0500 (EST)
References: <Pine.OSF.3.95.961110040648.7148E-100000@webdreams.com>

>>>>> "BR" == Brock Rozen <brozen@webdreams.com> writes:

BR> On Sat, 9 Nov 1996, Jason L Tibbitts III wrote:
>> The only real solution I can see is to either slurp the mail into a
>> string, or copy it into a file, then process that.  In other words, a
>> proper solution will take more than just a small patch.  I'm still
>> working on this, though.

BR> Wouldn't it also require saving state on a grand scale? (whole
BR> messages)

How do you figure this?  The message doesn't survive past a single
majordomo run.  You just copy it somewhere so you can scan it.  Just like
resend does.  It was an idle comment on why it isn't easy to graft a regexp
filter onto majordomo like resend has.

BR> But saving whole messages for just 24 hours can take up considerable
BR> space.

I have yet to see a message that proposed saving whole messages.

 - J<


References:
Indexed By Date Previous: Re: Return Loops
From: Evan Champion <evanc@synapse.net>
Next: ANNOUNCE: patches for Majordomo 1.94 available
From: Chael Hall <nowhere@chaos.taylored.com>
Indexed By Thread Previous: Re: Return Loops
From: Evan Champion <evanc@synapse.net>
Next: Question about V1.93, majordomo and config_parse.pl's direct call to shlock rtn.
From: zielonko@ucx.lkg.dec.com (Karol Zielonko 508-486-5632)

Google
 
Search Internet Search www.greatcircle.com