Could you break it up so several people could do it, maybe once a week
or only so much bandwidth or a few of the functions.  i would like to
help
with things like this, but like you i have more things to do than time.
On Wed, 18 Sep 1996 19:42:47 -0800 jory bell <jory@MIT.EDU> writes:
>i have a list administration problem which may mean the list in its
>present
>form will have to cease.
>
>as i have mentioned in the past, every error generated by the piclist
>(bounces, delays, full mailboxes, etc) needs to be forwarded
>somewhere.
>
>currently, this mail is forwarded to an account on my local network
>(at my
>home... though i am still affiliated with mit, i am currently living
>in
>california and thus no longer have the advantage of mit's 100 mbit
>network
>to deal with these little problems ;).
>
>unfortunately, there are a lot of errors on a thusand member list, and
>the
>error traffic is a serious burden to my personal mail host (running on
>an 8
>year old mac se/30).
>
>so, i need to do something about thisstate of affairs. the options as
>i see
>them
>
>1. someone can give me an ipx or indy which can handle the traffic :)
>
>2. someone can volunteer to accept the error traffic (the recipient is
>settable).
>
>3. i can shut the list down
>
>obviously #3 is the least desirable.
>
>while i certainly wouldn't mind #1, #2 seems the most likely. if
>someone is
>getting the error messages, they can either also have priveleges to
>delete
>subscribers, etc and take care of this, or they can just dev/nul it
>and i
>can periodically add myself to the errors-to field and go through the
>week's problem accounts by getting a sampling of the errors.
>
>i haven't quantified the error traffic, but i am less concerned with
>the
>bandwidth than with the torture of my mail host.
>
>i am also open to other suggestions.
>
>sincerely,
>jory bell
>piclist administrator
>