| Age | Commit message (Collapse) | Author |
|---|
|
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
|
|
the connecting hosts in the tuple key when greylisting. catches
a few more bogus hosts and will let us trap based on HELO later.
Changes spamdb(8) output to include the new field.
ok deraadt@, jmc@
|
|
walk with mutiple conditions in the loop.
ok deraadt@
|
|
|
|
|
|
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
|
|
and the rebalancing really slags big databases. Make spamd use DB_HASH
instead, and convert if the old type is noticed on startup.
Testing by me, djm, ian, others
ok deraadt@, millert@, djm@
|
|
|
|
command not after the RCPT command, as this helps people out when
they are faced with retarded sender verification schemes - tested
out by a number of people on tech@, and running at u of a for a
while. Supposedly this makes verizon sender verification happy.
Suggested as a stable candidate by people on tech@, I'm ok with
that.
|
|
|
|
from jared rr spiegel (pr #5292), tweaked somewhat;
|
|
|
|
|
|
ok deraadt@
|
|
|
|
|
|
SMTP banner
ok beck@
|
|
the per-connection copy of the connecting address was being pointed
to the on-stack copy. Spotted (and fix suggested) by Michael Durket
in pr 5046
ok deraadt@
|
|
ok jmc@
|
|
|
|
|
|
|
|
ok krw@ deraadt@
diff from ray lai;
|
|
always skipping the last address. ok beck@
|
|
|
|
closing the connection while we're trying to write to it
|
|
|
|
- note that greylisting does stutter slightly
- make clear role of spamdb and spamd.conf
- few minor tweaks
ok beck@
|
|
operations. ok millert@ ages ago.
|
|
|
|
full speed. By default do this for 10 seconds. Many spammers disconnect by
then. Adds -S option to select the amount of time greylisted connections
will be stuttered at.
feedback from jmc@, deraadt@, ok deraadt@
|
|
ok millert@
|
|
a list of spamtrap destination addresses in the spamd database. When
a spamtrap address gets an attempted greylist delivery, blacklist the
offending host for a day. Does not affect hosts already whitelisted.
ok deraadt@, jmc@, dhartmei@ to get it in so it can be whacked on
|
|
|
|
signal handler could be interrupted by another instance
of itself because it was used for multiple signals and
only one signal was blocked.
ok beck@ henning@
|
|
- Implement RSET in spamd - some virus scanning products (notably symantec's
viruswall) spew a RSET into the smtp stream before every attempted delivery.
(noticed by reitenba@fh-brandenburg.de and some others). This ensures
such things can successfully talk to a spamd greylister.
ok millert@ henning@
|
|
MTA's with a quadratic retry schedule have a retry after 26 minutes, and
then again after an hour, so this probably makes a lot more sense than the
old 30 minute default.
ok henning@
|
|
people on misc, and some observations by Evan harris on the greylisting
mailing list that a number of clustered mailers like aol behave better
(and retry from the same IP) when they see a 451, but do not when
they see a 450 (traditionally used for mailbox lock failure)
450 was the original for spamd, as the default for the tarpit is to
encourage quick retries to punish blacklisted smtp servers more. This
got carried over to the greylisting implementation, and isnt' really
optimal for that case.
ok millert@, henning@, todd@
|
|
ok henning@
|
|
|
|
|
|
with an expire time in the past. From beck@, OK deraadt@
|
|
|
|
|
|
|
