I wonder if there is a way to deactivate the teergrube in Courier
without recompiling?
Nope.
Maybe there is even a way to exclude (whitelist) single IPs from
tarpitting?
Stripping a mail server of its defenses against hostile peers, instead
of fixing whatever problem causes the peer to shovel crap in the
server's direction, is a rather foolish and a naive decision.
Hi Sam,
I _definitely_ agree with you. Courier has been serving us well for years
now, teergrube included. The reason why I want to know is, that I want to
use a spam filter in front of courier on a separate machine. This would be
ASSP (assp.sourceforge.net) which works as a proxy. Now if
mailserver.somewhere.com wants to send me an email Courier logs like this:
Nov 14 01:01:16 jupiter courierd: newmsg,id=007174C6.473A3AC6.00007A1F: dns;
lists-outbound.sourceforge.net (sirius.netgroup.de [::ffff:195.138.34.209])
[...]
Nov 14 01:01:20 jupiter courierd: completed,id=007174C6.473A3AC6.00007A1F
If all incoming connections, good or bad, carry the IP of my spam filter
then I am afraid of tarpitting my own machine. There are strange delays and
I would like to check if tarpitting is the reason.