[ale] Automated removal message

[Christopher Fowler]

Its needs to know how to combine the results of this:

fetchmail -> procmail -> spamassisin -> procmail -> filters -> perl

Too many levels of crap to go through. 
The problem was the automation script did not keep track of
where it was sending repsonses to one email to ale at ale.org
could generate ~ number of responses.  Luckily I was monitoring
the execution and saw what was happening.  One solution would
be to keep a log file of where the responses were going and
then not send responses back to that same adress then reset the
number after 24 hours.



On Sun, May 04, 2003 at 05:13:57PM -0400, Christopher Ness wrote:
> On Sunday 04 May 2003 04:55 pm, Christopher Fowler wrote:
> > Guys/Gals,
> >
> > Ignore the 13 automated removal message responses.  We had a small
> > issue in out scripts that do automatic responses to mailing lists for
> > employees no longer here.  The problem was that the reponse was being
> > sent back to the filter which generated another response.  I caught that
> > mess and just did away with that part.
> >
> > Chris
> 
> You need one of those ENS-8 things. It says it will "locate and resolve issues 
> before they become problems."
> -- 
> Chris Ness
> mailto:cness at earthlink.net               All jobs are equally easy to
> http://home.earthlink.net/~cness           the person not doing the work.
> 			   			    Holt's Law
> 
> 
> _______________________________________________
> Ale mailing list
> Ale at ale.org
> http://www.ale.org/mailman/listinfo/ale
_______________________________________________
Ale mailing list
Ale at ale.org
http://www.ale.org/mailman/listinfo/ale