Date: Mon, 10 Jun 1996 15:08:08 -0400 (EDT) From: Brian Clapper <bmc@telebase.com> To: DARREND@novell.com (Darren Davis) Cc: hackers@freebsd.org Subject: Re: Ahhhhhhhhhh! Message-ID: <199606101908.PAA06231@telebase.com.> In-Reply-To: <108976225@toto.iv>
next in thread | previous in thread | raw e-mail | index | archive | help
>>>>> "Darren" == Darren Davis <DARREND@novell.com> writes: Darren> What are the thoughts on breaking this stuff out of mail lists and Darren> into news groups? (At least there I can use kill files to Darren> eliminate the noise.) Or, must I suffer this fate? Any Darren> suggestions on how to manage this much email? Jordan, how do you Darren> deal with all this traffic? My solution is to digest the stuff here through Majordomo, since the `freebsd.org' mailing lists aren't "digested" at the source. Throw majordomo up on a Unix box, create a local digest for each list in question, and subscribe that digest to the FreeBSD list. Then, subscribe yourself to your local digest. You're in control of Majordomo, so you can control how often the queued messages are compiled into a digest and shipped out. Set the threshold higher for really busy lists. Run a cron-driven shell script each night to ensure that the digests get built at least once a day. This approach has worked very well for us for more than a year. We use local mailing lists for a lot of Internet lists, partly to minimize traffic to our mailer (i.e., every one who's interested can subscribe to the local mailing list "exploder", rather than the real list), and partly to permit us to make digests out of lists that aren't digested. Or the FreeBSD guys can make digest versions of all the existing lists. Whatever. ---- Brian Clapper .............................................. bmc@telebase.com http://www.netaxs.com/~bmc/ ............. PGP public key available on request The attacker must vanquish; the defender need only survive.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199606101908.PAA06231>