summaryrefslogtreecommitdiff
path: root/libexec/spamd
diff options
context:
space:
mode:
authorJason McIntyre <jmc@cvs.openbsd.org>2007-03-07 08:26:53 +0000
committerJason McIntyre <jmc@cvs.openbsd.org>2007-03-07 08:26:53 +0000
commit5d32268cb8ffb54b8e5daf0aab6f76530e9ea52d (patch)
tree0470d2f4ca526603deb387df660c2ef0d27011d3 /libexec/spamd
parentdb54134a035a25176142dc6bf91ab40e426487b5 (diff)
new sentence, new line
kill whitespace at eol
Diffstat (limited to 'libexec/spamd')
-rw-r--r--libexec/spamd/spamd.818
1 files changed, 12 insertions, 6 deletions
diff --git a/libexec/spamd/spamd.8 b/libexec/spamd/spamd.8
index 0ea7cd539c3..00815f9c1ea 100644
--- a/libexec/spamd/spamd.8
+++ b/libexec/spamd/spamd.8
@@ -1,4 +1,4 @@
-.\" $OpenBSD: spamd.8,v 1.93 2007/03/06 23:38:36 beck Exp $
+.\" $OpenBSD: spamd.8,v 1.94 2007/03/07 08:26:52 jmc Exp $
.\"
.\" Copyright (c) 2002 Theo de Raadt. All rights reserved.
.\"
@@ -155,7 +155,10 @@ listens on all local addresses.
.It Fl M Ar address
Specify a local address which is listed as a low priority
MX record, used to identify and trap hosts that connect to MX
-hosts out of order. See GREYTRAPPING below for details.
+hosts out of order.
+See
+.Sx GREYTRAPPING
+below for details.
.It Fl n Ar name
The SMTP version banner that is reported upon initial connection.
.It Fl p Ar port
@@ -393,14 +396,17 @@ or
.Em bigbutts@bofh.ucs.ualberta.ca
would cause the sending host to be trapped.
.Pp
-A low priority MX ip address may be specified with the -M option.
+A low priority MX IP address may be specified with the
+.Fl M
+option.
When
.Nm
has such an address specified, no host may enter new greylist
tuples when connecting to this address, only existing entries
-may be updated. Any host attempting to make new deliveries to
+may be updated.
+Any host attempting to make new deliveries to
the low priority MX for which a tuple has not previously
-been seen will be trapped.
+been seen will be trapped.
.Pp
Note that is is important to ensure that a host running
.Nm
@@ -414,7 +420,7 @@ For example, on a host which is an existing MX record for a domain of
value 10, A second IP address with MX of value 99 (a higher number, and
therfore lower priority) would ensure that any RFC conformant client
would attempt delivery to the IP address with the MX value of 10
-first, and should not attempt to deliver to the address with MV value 99.
+first, and should not attempt to deliver to the address with MV value 99.
.Sh BLACKLISTING
The normal way that spam has been dealt with in the past is to either
accept and drop, or outright block.