Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!bu.edu!wang!fitz From: fitz@wang.com (Tom Fitzgerald) Newsgroups: comp.mail.misc Subject: Re: BITFTP grief! Message-ID: Date: 25 May 91 02:07:36 GMT References: <1705@aupair.cs.athabascau.ca> <34032@ucsd.Edu> <8942@gollum.twg.com> Distribution: na Organization: Wang Labs, Lowell MA, USA Lines: 27 I'm running an MBAS here (flame away, I'm distributing stuff that too many people have no other way to get, and I've got load-limiters in place to keep the total volume reasonable). peter@ficc.ferranti.com (Peter da Silva) writes: > Here's another idea... how about having mail-based archive servers putting > a line that says "Class: Junk". Then if you have an expensive link you > dump junk mail going through it on the floor. You mean "Precedence:"? My pride won't let me put in "Precedence: Junk", but I'm perfectly willing to put in "Precedence: Bulk". On the other hand, if I find out that mail is being dropped as a result with no message to either me or the requester, I'll take it out again. If anyone (even a daemon) writes to me saying the load from the MBAS is too high, I'll choke it back or find another route. That's doable, once I know which system to route around. If mail mysteriously disappears somewhere, I'll force it through by disguising all the keywords that might give away the fact that it's an archive server. Actually, "Precedence: Bulk" is a pretty good thought. --- Tom Fitzgerald Wang Labs fitz@wang.com 1-508-967-5278 Lowell MA, USA ...!uunet!wang!fitz