| Age | Commit message (Collapse) | Author |
|---|
|
structures aligned to 16 byte boundaries for maximum portability
(somewhat similar to CMSG's). Old spamd's and new spamd's can still
communicate with this change. It would be nice if someone tested spamd
on 64-bit unaligned architectures (with and without this change)
ok beck
|
|
hold the header with length field.
ok deraadt@ beck@
|
|
|
|
|
|
From Diego Giagio (dgiagio at gmail)
with input from tedu@
|
|
noticed and patch from Piotr Sikora <piotr@sikora.nu>
|
|
|
|
traps.
- Change count to size_t to avoid a size_t -> int conversion.
- Since configure_spamd always returns 0, change to void.
- Since configure_spamd now returns void, remove unreachable logging
statement.
OK ckuethe and deraadt, initial diff from fgsch@ and OKed by beck.
|
|
- 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
|
|
|
|
ok millert@
|
|
sized array, so memory corruption occurs when writing the field.
problem encountered by Jeremy C. Reed. ok reyk@
|
|
|
|
whitespace at eol
|
|
to remember how to commit to do that.
|
|
|
|
|
|
|
|
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@
|
|
|
|
ok reyk@
|
|
by checking for them being in the db first.
ok millert@
|
|
closes user/5408 from sthen
ok reyk
|
|
mx for the first minute, to avoid problems if hosts legitimately try it
after we are down.
suggested by millert@
|
|
and this hides the evidence. Avoids a potential race when
using -M traps where a retry comes in between deletion and
whitelisting.
ok millert@
|
|
|
|
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
|
|
|
|
than a hardcoded value.
ok reyk@, deraadt@ with knfisms and saner variable names
|
|
ok jmc@, reyk@
|
|
|
|
create one? and so on...
help from jmc@
|
|
we save the entry.
ok reyk@
|
|
|
|
commit with the U of A value, which may not be safe on all GENERICs with
an unmodified kern.maxfiles
|
|
|
|
|
|
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@
|
