From owner-freebsd-questions@FreeBSD.ORG Mon Nov 3 19:39:31 2014 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 04859B18 for ; Mon, 3 Nov 2014 19:39:31 +0000 (UTC) Received: from fly.hiwaay.net (fly.hiwaay.net [216.180.54.1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C3CCDEEF for ; Mon, 3 Nov 2014 19:39:30 +0000 (UTC) Received: from kabini1.local (rbn1-216-180-19-112.adsl.hiwaay.net [216.180.19.112]) (authenticated bits=0) by fly.hiwaay.net (8.13.8/8.13.8/fly) with ESMTP id sA3JdSE7025870 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO) for ; Mon, 3 Nov 2014 13:39:29 -0600 Message-ID: <5457DB67.4010002@hiwaay.net> Date: Mon, 03 Nov 2014 13:45:43 -0600 From: "William A. Mahaffey III" User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 CC: freebsd-questions@freebsd.org Subject: Re: Postal Notification References: <20141103140638.60B9617470E@scprod53.upprovider.it> <5457A6D1.5050209@gmail.com> <5457AA1D.5070602@hiwaay.net> <20141103182021.5748167b.freebsd@edvax.de> In-Reply-To: <20141103182021.5748167b.freebsd@edvax.de> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Nov 2014 19:39:31 -0000 On 11/03/14 11:20, Polytropon wrote: > On Mon, 03 Nov 2014 10:15:25 -0600, William A. Mahaffey III wrote: >> On 11/03/14 10:01, jd1008 wrote: >> >> >> I 2nd this motion. The #1 source of SPAM which makes it to my home PC >> (this FBSD 9.3p3 box) is crap going to this list, which I have >> whitelisted :-/ .... > This mailing list is public. It also is not being moderated. > However, you can easily filter spam on client side, for example, > if the messages contain HTML garbage, or certain keywords are > met. Filtering for certain X-Mailer strings is also possible. > If you don't want to do this in your MUA, you can use your > MTA to do this at an earlier stage (either by deleting the > offending messages, or simply denying to receive them). > > In my opinion, this is not even worth the time, as there > is only _few_ spam on this list (compared to others!) which > only requires a single DEL keypress to be deleted. In most > cases, the subject is fully sufficient to determine if this > action is required. This opinion illustrates that I'm a lazy > person who doesn't receive thousands of messages per day to > be bothered automating anything. ;-) > > > My ISP allows (Linux RHEL 5.n) shell access to their servers, & I have a 2100+ line procmail file doing *mucho* detailed keyword/header filtering. Filtering HTML would lose anyone I buy something from on Ebay or stuff from my brokers. My ISP has some pretty aggressive/effective filtering as well. I only get 2-3 SPAMs/month, but unfortunately almost *all* are from crap that leaks through on this list. Could the list white-list anyone who subscribes, then eliminate any SPAMmers once they rear their ugly heads ? I don't know what the solution is, & I think the list is fabulously managed overall, but these SPAMs are irritating .... -- William A. Mahaffey III ---------------------------------------------------------------------- "The M1 Garand is without doubt the finest implement of war ever devised by man." -- Gen. George S. Patton Jr.