Path: utzoo!censor!geac!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!tut.cis.ohio-state.edu!mstar!mstar.morningstar.com!bob From: bob@MorningStar.Com (Bob Sutterfield) Newsgroups: comp.mail.misc Subject: Re: CompuServe backlog; mail servers Message-ID: Date: 17 Dec 90 14:48:11 GMT References: Sender: usenet@MorningStar.COM (USENET Administrator) Reply-To: bob@MorningStar.Com (Bob Sutterfield) Organization: Morning Star Technologies Lines: 32 In-Reply-To: karl_kleinpaste@cis.ohio-state.edu's message of 13 Dec 90 00:40:10 GMT In article karl_kleinpaste@cis.ohio-state.edu writes: Mail-based archive servers are a disease which should be stamped out wherever they are found. ... MBASes: Just Say No, because You Don't Know Anything About The Links Between Hither And Yon. Amen. Say it with feeling, brother! A whole slew of CompuServe users appears to have discovered the wonders of bitftp@pucc.princeton.edu in the last week or so, not to mention not a few other similar addresses. ... We are considering, for the sake of gateway sanity, aggressively blowing away anything that clearly comes from or is going to an archive server. This will require some administrative nonsense that I don't like, because I _really_ don't like peeking in other people's mail. That's the lesser evil because But we have to get control of the machines again. is a system and gateway maintainer's first responsibility. You might consider implementing a filter to replace the message bodies of the irresponsible abusers' traffic with a brief explanation of why they can't take advantage of your service any more. That way at least they won't be able to plead ignorance, complain about broken servers, or bleat about censorship. Such a filter can probably be expressed as a Perl one-liner, hidden away in a Sendmail ruleset somewhere. It's all just line noise :-)