From owner-freebsd-questions@freebsd.org Sat Jul 25 11:42:45 2015 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C41939AAEA0 for ; Sat, 25 Jul 2015 11:42:45 +0000 (UTC) (envelope-from quartz@sneakertech.com) Received: from douhisi.pair.com (douhisi.pair.com [209.68.5.179]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A60FA1941 for ; Sat, 25 Jul 2015 11:42:45 +0000 (UTC) (envelope-from quartz@sneakertech.com) Received: from [10.2.2.1] (pool-173-48-121-235.bstnma.fios.verizon.net [173.48.121.235]) by douhisi.pair.com (Postfix) with ESMTPSA id 05F6E3F759; Sat, 25 Jul 2015 07:42:43 -0400 (EDT) Message-ID: <55B37633.6000209@sneakertech.com> Date: Sat, 25 Jul 2015 07:42:43 -0400 From: Quartz User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2 MIME-Version: 1.0 To: CK CC: freebsd-questions@freebsd.org Subject: Re: SPAM from freebsd-questions References: <0MaJPk-1ZclO93RGK-00JoYf@mail.gmx.com> In-Reply-To: <0MaJPk-1ZclO93RGK-00JoYf@mail.gmx.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Jul 2015 11:42:45 -0000 > I just posted about data loss, and got 3 spam emails from China > instantly. This has been going on for ages and people complain about it regularly with no result (you're like the 3rd person this month). >How is China finding out email addresses > of everyone that posts to freebsd-questions, They're subscribed just like anyone else is, they just reply to whatever is in the 'from' field. >and can the SPAM be > stopped? Technically the list maintainer(s) should really unsubscribe them, but that doesn't seem to be happening. Just set up a kill filter in your client.