I've been working with spamassassin recently using spamd in a
mail delivery system to allow per-user preferences which don't
seem to be handled when running under amavisd, and to provide
more fine grained spam checking. In doing this I found that
spamd didn't allow connections from remote machines, even if the
interface was changed from 127.0.0.1. The attached patch to the
rc.spamassassin file adds a couple of variables to the %config
section to allow these in the @l_prefix@/etc/rc.conf file, and
changes the %start section to use these variables.
The variables control, (a) who is allowed to connect to the
server, and (b) whether to use network tests. I think that the
default settings shouldn't change the current behaviour of
spamassassin (but might include 10. and whatever the other local
IP range is that I never remember :-).
Bill
--
INTERNET: [EMAIL PROTECTED] Bill Campbell; Celestial Software LLC
UUCP: camco!bill PO Box 820; 6641 E. Mercer Way
FAX: (206) 232-9186 Mercer Island, WA 98040-0820; (206) 236-1676
URL: http://www.celestial.com/
With Congress, every time they make a joke it's a law; and every time
they make a law it's a joke.
-- Will Rogers
--- rc.spamassassin.orig Tue Jun 28 09:29:44 2005
+++ rc.spamassassin Tue Jun 28 10:23:01 2005
@@ -12,6 +12,12 @@
spamassassin_log_numfiles="10"
spamassassin_log_minsize="1M"
spamassassin_log_complevel="9"
+ # These options control various startup options, and are
+ # included here to allow changes in the @l_prefix@/etc/rc.conf file.
+ # Allow local private networks and local host to connect
+ spamassassin_allowed_ips='-A 192.168. -A 127.'
+ # Use only local tests
+ spamassassin_local_only='--local'
%common
spamassassin_pidfile="@l_prefix@/var/spamassassin/spamassassin.pid"
@@ -36,7 +42,8 @@
--pidfile="${spamassassin_pidfile}" \
--listen-ip="${spamassassin_iface}" \
--port="${spamassassin_port}" \
- --local
+ $spamassassin_allowed_ips \
+ $spamassassin_local_only
%stop -p 400 -u @l_susr@
rcService spamassassin enable yes || exit 0
