From owner-freebsd-stable@FreeBSD.ORG Tue Dec 19 23:01:58 2006 Return-Path: X-Original-To: freebsd-stable@FreeBSD.ORG Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D513216A407 for ; Tue, 19 Dec 2006 23:01:58 +0000 (UTC) (envelope-from jdow@earthlink.net) Received: from elasmtp-banded.atl.sa.earthlink.net (elasmtp-banded.atl.sa.earthlink.net [209.86.89.70]) by mx1.FreeBSD.org (Postfix) with ESMTP id 694DD43C9F for ; Tue, 19 Dec 2006 23:01:58 +0000 (GMT) (envelope-from jdow@earthlink.net) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=Db4rXkGt6QvJ867bRAVTlSalPfuJL/NzkrqYgmzM71XQZ7eELxJAIMnsugi4qS+b; h=Received:Message-ID:From:To:References:Subject:Date:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Priority:X-MSMail-Priority:X-Mailer:X-MIMEOLE:X-ELNK-Trace:X-Originating-IP; Received: from [208.127.11.96] (helo=wednesday) by elasmtp-banded.atl.sa.earthlink.net with asmtp (Exim 4.34) id 1GwnZ1-0007Gg-39 for freebsd-stable@FreeBSD.ORG; Tue, 19 Dec 2006 17:35:59 -0500 Message-ID: <00b801c723be$106ce980$0225a8c0@wednesday> From: "jdow" To: References: <200612191227.kBJCRRLJ054427@lurza.secnetix.de> <4587D1B6.6060500@andric.com><200612191146.45521.joao@matik.com.br> <45882572.7040707@vindaloo.com> Date: Tue, 19 Dec 2006 14:36:02 -0800 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.3028 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3028 X-ELNK-Trace: bb89ecdb26a8f9f24d2b10475b5711208d9b96685dbac63882dd452740aeab22f3955f778df1f3fd350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c X-Originating-IP: 208.127.11.96 Cc: Subject: Re: OpenBSD's spamd. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Dec 2006 23:01:58 -0000 From: "Christopher Hilton" > JoaoBR wrote: >> >> why the spam daemon should introduce an artificial delay >> (tarpit) if this can be done already before like Oliver >> said, it would only eat up and slow down threads between >> both daemons (smtp + spamd) and overall spamd doesn't even >> talk directly to the remote smtp >> > > Spamd does talk to the remote smtp. It does this until it determines > that the remote smtp is RFC compliant in the area of retrying mail. On > the first delivery attempt it sets up a time window for the delivery > tuple: (server, sender, recipient). If it receives another delivery > attempt within this time window it modifies a PF table which allows > further delivery attempts to bypass spamd and talk directly to your > actual smtp daemon. Without this entry remote smtp daemons talk to your > spamd. Features aside I see a huge problem with something called spamd. That is the same name as the daemon mode for SpamAssassin. It's not good to have duplicated names that way. It makes life difficult when you want to run both tools on the same system. {o.o}