| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
- this document talks about "default mode", not "greylisting mode"
- kill trailing whitespace
|
|
longer used in greylisting mode.
ok ckuethe@
|
|
from Saint Aardvark the Carpeted, documentation/5535;
|
|
|
|
|
|
also, this section is blacklist-only, so tweak .Sh
|
|
|
|
whitespace at eol
|
|
1) Implement the NOOP command, which now seems necessary for certain
windows mail wrappers and sender verification schemes. Tested by me
and sidcarter@symonds.net, who noticed the problem on his site.
ok millert@
2) Change the behaviour of the maxblack parameter, instead of hanging
up immediately on new blacklisted connections when the maxblack parameter
is reached, we instead make spamd not stutter at them, so the connection
is instead completed quickly. This seems to handle peaks and spikes
much better than the old way of doing this.
ok deraadt@, with some man page changes by jmc@
|
|
closes user/5408 from sthen
ok reyk
|
|
explicitly mentioning IP aliases, which is typically how you would
implement MX trapping using a single host.
OK beck@, trusted by deraadt@
|
|
|
|
|
|
kill whitespace at eol
|
|
address than the primary one. spamd will trap hosts that contact this
address first without first contacting the primary.
- get it in, deraadt@
|
|
|
|
- move some relevant bits of SYNCHRONISATION into -Yy descriptions
- tweaks for SYNCHRONISATION
ok reyk beck
|
|
|
|
ok jmc@, reyk@
|
|
|
|
create one? and so on...
help from jmc@
|
|
|
|
This adds an HMAC protected synchronization protocol for use by spamd and
spamlogd.
- spamd can receive updates from other hosts for GREY, WHITE, and TRAPPED db
entries, and will update the local /var/db/spamd accordingly.
- spamd can send updates when it makes changes to the GREY or TRAPPED
entries in the db to other hosts running spamd. (Note it does not send
WHITE entries because the other spamd will see the GREY changes and have
complete information to make appropritate decisions)
- spamlogd can send updates for WHITE db entries that it performs on the local
db to other hosts running spamd, which will then apply them on remote hosts.
note that while this diff provides synchronization for changes made to the
spamd db by the daemons, it does *not* provide for sychonizing changes
to the spamd db made manually with the spamdb command.
Synchronization protocol and most of the work by reyk@,
with a bunch of the spamd, and spamlogd stuff by me.
testing mostly at the U of A, running happily there under big load.
ok reyk@ jmc@
|
|
|
|
|
|
|
|
.Dq for services
.Aq for tables
|
|
|
|
- no need for <> for tables
- use escapes for <> where needed
|
|
|
|
diff from Okan Demirmen, tweaked by myself and beck
ok beck
|
|
has for a little while now - it got changed so people don't get
hooped by certain stupid sender verification schemes.
|
|
|
|
|
|
1) config files move to /etc/mail
2) -g option goes away in spamd-setup and spamd - greylisting is now the default
3) option change to spamd, -b addr becomes -l addr.
4) -b option in spamd-setup and spamd to turn on old blacklisting mode.
Man page shortly to be flensed to make this easier to explain
ok deraadt@ millert@
|
|
- remove misleading sentence
ok millert
|
|
|
|
We just do no-rdr for things in <spamd-white> and rdr the rest to spamdb.
OK beck@
|
|
|
|
by okan@demirmen.com
|
|
1) remove requirement for <> around spamtrap addresses
2) add support for /etc/spamd/alloweddomains to specify
suffixes for which any destinations that don't match
get trapped
various knf's by theo, feedback from jmc, millert, deraadt
|
|
|
|
from jared rr spiegel (pr #5292), tweaked somewhat;
|
|
|
|
ok deraadt@
|
|
|
|
|
|
SMTP banner
ok beck@
|
