From owner-freebsd-questions@FreeBSD.ORG Wed Apr 30 11:45:51 2014 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 94A8A5EB for ; Wed, 30 Apr 2014 11:45:51 +0000 (UTC) Received: from mailout16.yourhostingaccount.com (mailout16.yourhostingaccount.com [65.254.253.131]) by mx1.freebsd.org (Postfix) with ESMTP id 5A24B153F for ; Wed, 30 Apr 2014 11:45:51 +0000 (UTC) Received: from mailscan08.yourhostingaccount.com ([10.1.15.8] helo=mailscan08.yourhostingaccount.com) by mailout16.yourhostingaccount.com with esmtp (Exim) id 1WfSeT-0006x1-7V for freebsd-questions@freebsd.org; Wed, 30 Apr 2014 07:26:13 -0400 Received: from impout02.yourhostingaccount.com ([10.1.55.2] helo=impout02.yourhostingaccount.com) by mailscan08.yourhostingaccount.com with esmtp (Exim) id 1WfSeR-00024N-MX for freebsd-questions@freebsd.org; Wed, 30 Apr 2014 07:26:11 -0400 Received: from walauthsmtp13.yourhostingaccount.com ([10.1.18.13]) by impout02.yourhostingaccount.com with NO UCE id wBSC1n0070GvC8i01BSCJk; Wed, 30 Apr 2014 07:26:12 -0400 X-Authority-Analysis: v=2.0 cv=XZQLPfF5 c=1 sm=1 a=MlIERbc/LeOD9IsFJ/vXKg==:17 a=EUXf4MBdpf0A:10 a=BTUk5m_ZKwEA:10 a=hq8RW5-nFdsA:10 a=oKNMHU8azEoA:10 a=kj9zAlcOel0A:10 a=YsjP1prSAAAA:8 a=mh5cOPX7AAAA:8 a=rmQgN8h9AAAA:8 a=CjxXgO3LAAAA:8 a=QGkg5yLt1sOHgBZPIuAA:9 a=CjuIK1q_8ugA:10 a=G1cppYHRSN6zanrJ:21 a=V2--ETElgmsiv_Gv:21 a=98qOcNyB16KL63Z3hZrGug==:117 X-EN-OrigOutIP: 10.1.18.13 X-EN-IMPSID: wBSC1n0070GvC8i01BSCJk Received: from adsl-64-218-114-145.dsl.amrltx.swbell.net ([64.218.114.145]:57117 helo=localhost) by walauthsmtp13.yourhostingaccount.com with esmtpa (Exim) id 1WfSeS-0004tV-HD for freebsd-questions@freebsd.org; Wed, 30 Apr 2014 07:26:12 -0400 Date: Wed, 30 Apr 2014 06:26:04 -0500 From: Mike Sanders To: "freebsd-questions@freebsd.org" Subject: Re: Spam to list participants (from openhosting.com & softcom.com) Message-ID: <20140430112604.GA1033@taco-shack.cow> References: <73354.1398734218@server1.tristatelogic.com> <535F1667.1050406@soliddataservices.com> <20140429114019.0eb3ce48@X220.alogt.com> <20140429124618.06d708ba@gumby.homeunix.com> <20140429204204.2e561935@X220.alogt.com> <20140429140123.GA910@taco-shack.cow> <08BA00AD-BBFF-42CA-8BDE-730814E64A8B@kallab.com> <20140430101958.GB931@taco-shack.cow> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-PGP-KEY: http://freebsd.hypermart.net/gpg-key.txt User-Agent: Mutt/1.5.22 (2013-10-16) X-EN-UserInfo: 86ba54ea1171c58e9a877a5108176e6f:931c98230c6409dcc37fa7e93b490c27 X-EN-AuthUser: mike@freebsd.hypermart.net Sender: Mike Sanders X-EN-OrigIP: 64.218.114.145 X-EN-OrigHost: adsl-64-218-114-145.dsl.amrltx.swbell.net X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Apr 2014 11:45:51 -0000 Olivier Nicole wrote: > Spam is *not* sent to the list, so abuse button or anything will not > help at all. > > The spamers harvest the addresses from some web archive of the list > (or because they subscribed to the list themselves) but they do not > use the list to send smap. > > FreeBSD list *cannot* help on the matter. No sir, not true. If an email address were mangled or otherwise truncated this would not be an issue... Now obviously anyone that's already infiltrated the list, we couldn't stop, however *future* spammers can be stopped, witness an example: The sender's email address is not exposed... Once the email is sent to the list, the sender is then validated against the list, the email is then sent all list users, with the original *senders address obfuscated*. ie we should only see/respond to the FreeBSD address, not the users address as so often happens here. In other other words, *the FreeBSD list should mangle the posters address in the message header before broadcasting to other list members*. Wouldn't a simple script achieve that result? It all starts on the list-end by exposing user's email address & it can be stopped, provided we worked to make it happen... -- Mike Sanders www: http://freebsd.hypermart.net gpg: 0xD94D4C13