> I manage about 30 mail servers, all using greylisting for years (not
> OpenBSD spamd, but a version running in the MTA). But as I greylist at
> RCPT TO, I only noticed the problem it when clamav did go down and the
> server was producing a 4xx error at DATA when it should have scanned the
> mail.
I have definately seen issues here with other implemntations,
because the 4XX code given, the XX's matter... Have you seen
this with OpenBSD spamd? (As opposed to something else..)
>
> Also, as an idea, I found it quite useful to whitelist only with a
> triplet (from, to, IP), and not just the IP. Why? Because some people
> are behind a firewall which allows them to go out with the same IP as
> their mail server (yes, IPs are expensive in Europe), so windows
> spamware is going out with the same IP than their mailserver and so
> bypasses the filter.
I find this exceedingly unhelpful. as it makes the database
huge and does unnecessarily delay mail. Generally either a service
is reasonably well run, or it isn't. This also prevents the ease of
spamlogd pre-whitelisting stuff going out.
It sounds like you're speaking on this topic without
any actual experience with OpenBSD spamd, but rather something
like postfix or the sendmail-milter implementation.
-Bob
