18 lines
1,008 B
Text
18 lines
1,008 B
Text
|
spamdyke monitors incoming traffic, acting as a middleman between
|
||
|
|
qmail and the remote server. It catches the sender and recipient
|
||
|
|
addresses as they go by and logs them to syslog. If it sees something
|
||
|
|
it doesn't like (e.g. a blacklisted sender), it cuts the connection,
|
||
|
|
closes qmail and fakes the rest of the SMTP transaction with the
|
||
|
|
remote server. qmail thinks the remote server disconnected normally.
|
||
|
|
The remote server thinks qmail is rejecting the message. It's the
|
||
|
|
best of both worlds.
|
||
|
|
|
||
|
|
spamdyke can optionally reject the connection if the remote server's
|
||
|
|
reverse DNS entry does not exist, does not resolve, contains its
|
||
|
|
IP address and either contains a prohibited keyword (like "dynamic")
|
||
|
|
or ends in a country code; if the IP address, reverse DNS entry,
|
||
|
|
or envelope sender is listed in a blacklist; or if data is sent
|
||
|
|
before the SMTP greeting banner is displayed. spamdyke can also
|
||
|
|
limit recipients per connection, greylist for some or all domains,
|
||
|
|
and close connections that go idle or take too long.
|