 | Start a set with this search |
 | Include this search in one of my sets |
 | Exclude this search from one of my sets |
 | Permalink to these results Paste this link in email or IM: |
 | Atom feed for tracking future search results Paste this URL into your reader: |
23 messages in net.sourceforge.lists.courier-usersRe: [courier-users] Deactivate tarpit...| From | Sent On | Attachments |
|---|---|---|
| niclas | Nov 10, 2007 6:41 am | |
| Sam Varshavchik | Nov 10, 2007 7:11 am | |
| Bernd Wurst | Nov 10, 2007 7:15 am | |
| Bernd Wurst | Nov 10, 2007 7:29 am | |
| Alessandro Vesely | Nov 10, 2007 9:00 am | |
| Bernd Wurst | Nov 10, 2007 9:09 am | |
| niclas | Nov 10, 2007 6:12 pm | |
| Alessandro Vesely | Nov 11, 2007 3:05 am | |
| niclas | Nov 11, 2007 3:38 am | |
| Bernd Wurst | Nov 11, 2007 4:01 am | |
| niclas | Nov 11, 2007 5:19 am | |
| Bernd Wurst | Nov 11, 2007 6:32 am | |
| Alessandro Vesely | Nov 11, 2007 10:54 pm | |
| niclas | Nov 12, 2007 3:49 am | |
| Gordon Messmer | Nov 12, 2007 10:50 am | |
| Dirk Kulmsee | Nov 13, 2007 10:13 am | |
| Sam Varshavchik | Nov 13, 2007 4:00 pm | |
| Dirk Kulmsee | Nov 13, 2007 4:28 pm | |
| Sam Varshavchik | Nov 13, 2007 4:42 pm | |
| Dirk Kulmsee | Nov 13, 2007 5:03 pm | |
| Sam Varshavchik | Nov 13, 2007 6:15 pm | |
| Dirk Kulmsee | Nov 13, 2007 7:08 pm | |
| Sam Varshavchik | Nov 13, 2007 7:17 pm |
| Permalink for this message Paste this link in email or IM: |
| Permalink for this thread Paste this link in email or IM: |
| Atom feed for this thread Paste this URL into your reader: |
| Subject: | Re: [courier-users] Deactivate tarpitting? | Actions... |
|---|---|---|
| From: | Dirk Kulmsee (kulm...@netgroup.de) | |
| Date: | Nov 13, 2007 5:03:14 pm | |
| List: | net.sourceforge.lists.courier-users | |
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.
Tarpitting would be the reason only if you see actual errors in the maillog. Only errors are the triggers for any tarpitting.
I find no reason why you would reject mail from your proxy, provided that your proxy only accepts mail for recipient addresses that actually exist, and its various settings are not any less liberal than Courier's; such as that it does not accept any mail that's larger than the maximum size of an email message that Courier is willing to accept.
Yes Sam! That is exactly the point which hurts. Being a proxy ASSP "tunnels" the connection from the sending mail server to my receiving Courier. Courier does the ESMTP dialog.
The bright side: if I set up all MXs as ASSP filters then all MXs will check with the mailbox server if the recipient exists and spammers' strategy to pour in junk on the 2nd MX which often has no knowledge of the existing mailboxes is rendered useless without me having to set up LDAP or the like.
The dark side: while checking for existing recipients the spam filtering machine _will_ produce errors on bad mail. Will it get punished?
Thanks for your help Dirk Kulmsee