remove nasty verbiage

1 files changed, 6 insertions, 35 deletions

diff --git a/libexec/spamd/spamd.8 b/libexec/spamd/spamd.8
index 294755c69f9..6b8c426af4d 100644
--- a/libexec/spamd/spamd.8
+++ b/libexec/spamd/spamd.8
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: spamd.8,v 1.3 2002/12/23 01:34:36 deraadt Exp $
+.\"	$OpenBSD: spamd.8,v 1.4 2002/12/25 10:14:20 deraadt Exp $
 .\"
 .\" Copyright (c) 2002 Theo de Raadt.  All rights reserved.
 .\"
@@ -74,41 +74,12 @@ The SMTP version banner that is reported upon initial connection.
 .Nm
 is designed to be very efficient so that it does not slow down the
 receiving machine.  SPAM is never accepted, but always rejected with
-either a 450 or 550 error message.
-.Pp
-There are currently two methods that are being used to
-fight spam.
-.Bl -enum -offset indent
-.It
-Block (or slowly block) This works well, the spammers are blocked, and cannot
-access your host's services.  Unfortunately this does little to combat the
-problem of spam in general, allowing the spammer to continue to spam others.
-.It
-Accept & drop via a
-.Xr sendmail 8
-addon.  This works well for many sites also.  All the mail that is recieved
-by your host is processed by a set of rules, and the spam is either deleted
-or flagged for further action.  Unfortunately this method can consume a
-considerable amount of your systems resources.
-.El
-.Pp
-What
-.Nm
-does, is defer the spammers connections.  It does this in a manner
-designed to use as few local resources as possible, while consuming as much
-of the spammers resources as possible.
-.Nm
-replies to the spammers mail with error codes which cause will cause mail
-to be stored in remote mail queues, taking up disk
-space, and to be resent multiple times, using network resources.
-.Pp
-.Nm
-does not follow the policy of playing nice with your neighbor.  Clients
-which reach
+either a 450 or 550 error message.  The normal way that SPAM has been
+dealt with in the way is to either acccept and drop, or outright block.
+When configured to use 450 responses,
 .Nm
-have already been flagged as being spammers.  The only way to combat spam is
-to remove the sender's ability to deliver it.  In this case, that means force
-the delivery of spam to have a very high overhead for the remote relay.
+takes neither of these actions: it rejects the mail back to the senders'
+queue.
 .Pp
 .Nm
 is best started from