From owner-freebsd-pf@FreeBSD.ORG Mon Feb 5 16:39:23 2007 Return-Path: X-Original-To: freebsd-pf@freebsd.org Delivered-To: freebsd-pf@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0424416A401 for ; Mon, 5 Feb 2007 16:39:22 +0000 (UTC) (envelope-from msgs_for_me@mail.ru) Received: from f22.mail.ru (f22.mail.ru [194.67.57.55]) by mx1.freebsd.org (Postfix) with ESMTP id B8A2E13C491 for ; Mon, 5 Feb 2007 16:39:21 +0000 (UTC) (envelope-from msgs_for_me@mail.ru) Received: from mail by f22.mail.ru with local id 1HE6sC-000Ht1-00 for freebsd-pf@freebsd.org; Mon, 05 Feb 2007 19:39:20 +0300 Received: from [82.114.107.25] by win.mail.ru with HTTP; Mon, 05 Feb 2007 19:39:20 +0300 From: Vladimir Kapustin To: freebsd-pf@freebsd.org Mime-Version: 1.0 X-Mailer: mPOP Web-Mail 2.19 X-Originating-IP: [82.114.107.25] Date: Mon, 05 Feb 2007 19:39:20 +0300 Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 8bit Message-Id: Subject: Re: Re: SPAMD stop passing mail from WHITE-list X-BeenThere: freebsd-pf@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Vladimir Kapustin List-Id: "Technical discussion and general questions about packet filter \(pf\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Feb 2007 16:39:23 -0000 > > I have spamd configured like in > > http://home.nuug.no/~peter/pf/en/spamd.html > > with greylisting enabled > > > > and i meet some problems with it: > > Well, you have my attention. I am would be very interested in getting > to know about any inaccuracies in that document, and certainly any > that trip people up. > > > 1. My 2 FreeBSD routers stopped to pass mail from WHITE-list. First > > one - when spamd grows to 500 Megabytes. Second - 350 Meg. > > At the point where things stop working, what content does the > whitelist table have? ie, anything recognizable or (incredibly) zero > size? One possibility - a far fetched one, admittedly - is that > hosts in your whitelist got themselves greytrapped (if you did set > that up). Nothing unusual, but that the mail stops forwarding from the whitelist. i.e. the sender resends the mail, gets in WHITE-list in spamd, but the mail does not actually pass the router. Many users started to complain and I forgot to look into pfctl -t spamd-white -T show but actually I have no BLACK list, and I still don't have a good idea how to use TRAPs automatically...I try to put some adresses in TRAP-list manually, but I can catch only myself in test purposes. > > > When I do: > > cat /dev/null > /var/db/spamd > > all starts to work again > > This sounds like somehow your initally whitelisted hosts got > themselves blacklisted, or the whitelist is somehow bypassed. > As I wrote above they could not get into BLACK-list because i don't have any. And it could not bypass anyhow, because I have such redirect rules: pfctl -sn rdr pass inet proto tcp from to any port = smtp -> 127.0.0.1 port 8025 rdr pass inet proto tcp from ! to any port = smtp -> 127.0.0.1 port 8025 .... > > 2. If i have some malware on my PC and use mail-client program. If I > > send the same message some times I automatically get into WHITE-list > > and my malware can spam as much as it must? > > If your malware manages to behave RFC-correctly, that is, resend after > what the greylisting host considers a reasonable interval, it will > manage to send whatever it's trying to send. No...not malware...suppose that a user doesn't know about malware and uses Outlook to send his mail. He'll get into THE WHITE-list and spamd can't stop HIS malware? tusen takk at du har blitt interessert i problemet mitt