This helps me quite some.
https://alexander.beard.se/spub/6dd1a43187c19431d087c91e403b756b/index.html
No man page (yet) but the code should should
reveal the secrets of most options and switches.
Simple start:
# spamwhite -nv
Two cron jobs:
"spamwhite" every few minutes (it's cheap).
"spamwhite -a" once per day or so to pick up changes. Not as cheap.
/Alexander
On 03/28/13 17:52, Sarah Caswell wrote:
> Hi all,
>
> I had a question about greylisting (with spamd) in production.
>
> I've successfully run spamd on firewalls (as a frontend to either barracuda
> or SpamAssassin) and have really liked the reduction in SPAM volume.
>
> Unfortunately my employer's wife does not like the delays that this
> introduces into our mail delivery, since she uses email for quick turn-around
> communication.
>
> The main problem occurs with senders like Gmail, yahoo, hotmail, etc. ...i.e.
> all the senders that have large farms of smtp servers from which they can
> retry delivery after initial greylisting delay.
>
> I know this means I'm not doing proper whitelisting of those major sender
> domains, but I'm at a loss on how to best construct and maintain such a
> whitelist.
>
> Are there any up-to-date lists that already track the MTAs of these large
> mail providers?
>
> Or will this mostly be a DIY effort on my part?
>
> Any thoughts/insights/experiences would be greatly appreciated.
>
> :-)
>
> Sarah
