Being a happy new user of spamd and friends (thank you Bob!),
I have a few nitpicking questions as I go through the manpages.
(1)
spamd whitelists a given host by _adding_ it as a whitelist entry;
the original GREY entry is left there. Why is is kept around, now
that the host is WHITE anyway? Is it because it is just easier to
let it expire than to explicitly delete it? Or is it because
greytrapping only applies to greylisted connections, and we want
to know about even WHITE hosts sending to spamtrap?
(2)
The spamd(8) manpage says "Use crontab(1) to uncomment the entry
in root's crontab", which I did, but experienced spamd-setup failures
(see the yesterday's post). I was later advised here that having
spamd-setup run at precisely '0 * * * *' might clash with all
the others doing the same at that exact time. I moved the spamd-setup
to a few minutes later and that solved the problem. Would a note
to that effect be an appripriate addition to the spamd(8)
(or spamd-setup(8)) manpage?
(3)
If I understand the GREYTRAPPING section right, a host can get
spamtrapped even if it is WHITE: if the original GREY entry is still
present and he sends to a spamtrap address within greyexp. The
pf.conf example of spamd(8) makes all connections from <spamd-white>
go to the real mailserver. That means a connection from a WHITE host
goes to the real mailserver even if the host is simultaneously TRAPPED.
Is that correct? Is that intended? It is a political decision of
course: do I allow obvious spam from WHITE hosts?
(4)
You can't "receive a failure":
Index: spamd.8
===================================================================
RCS file: /home/cvsync/openbsd/src/libexec/spamd/spamd.8,v
retrieving revision 1.118
diff -u -p -r1.118 spamd.8
--- spamd.8 19 Mar 2011 23:29:45 -0000 1.118
+++ spamd.8 30 May 2012 08:26:15 -0000
@@ -236,7 +236,7 @@ below.
.El
.Pp
When run in default mode,
-connections receive the pleasantly innocuous temporary failure of:
+connections receive the pleasantly innocuous temporary failure message of:
.Bd -literal -offset 4n
451 Temporary failure, please try again later.
.Ed
Thanks again for the great tool!
Jan
