clarification for the MX stuff; requested by Stephan A. Rickauer

ok beck

1 files changed, 4 insertions, 4 deletions

diff --git a/libexec/spamd/spamd.8 b/libexec/spamd/spamd.8
index 24c5e197ad1..f38e5c90bd5 100644
--- a/libexec/spamd/spamd.8
+++ b/libexec/spamd/spamd.8
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: spamd.8,v 1.111 2008/09/20 20:38:23 jmc Exp $
+.\"	$OpenBSD: spamd.8,v 1.112 2009/02/17 22:07:11 jmc Exp $
 .\"
 .\" Copyright (c) 2002 Theo de Raadt.  All rights reserved.
 .\"
@@ -22,7 +22,7 @@
 .\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
 .\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 .\"
-.Dd $Mdocdate: September 20 2008 $
+.Dd $Mdocdate: February 17 2009 $
 .Dt SPAMD 8
 .Os
 .Sh NAME
@@ -438,8 +438,8 @@ been seen will be trapped.
 Note that it is important to ensure that a host running
 .Nm
 with the low priority MX address active must see all the greylist
-changes for a higher priority MX host for the same domains, either by
-being synchronised with it, or by receiving the connections itself to
+changes for a higher priority MX host for the same domains.
+This is best done by the host itself receiving the connections to
 the higher priority MX on another IP address (which may be an IP alias).
 This will ensure that hosts are not trapped erroneously if the higher
 priority MX is unavailable.