From owner-freebsd-questions@FreeBSD.ORG Thu May 1 00:31:04 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 4230EEF6 for ; Thu, 1 May 2014 00:31:04 +0000 (UTC) Received: from mail-oa0-x234.google.com (mail-oa0-x234.google.com [IPv6:2607:f8b0:4003:c02::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0868B196C for ; Thu, 1 May 2014 00:31:03 +0000 (UTC) Received: by mail-oa0-f52.google.com with SMTP id l6so2887395oag.39 for ; Wed, 30 Apr 2014 17:31:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=references:mime-version:in-reply-to:content-type :content-transfer-encoding:message-id:cc:from:subject:date:to; bh=gMjkDLY8uFE+j2KAa6zT+IOnn0m8lwkHo4kUGxMZzGE=; b=eIROH9M4uoCZYhhi2xaHGh8L7wzfYII5HIXnX6YhFJ20mPbjEulM2IqARWbP5cnV4u 2+AVlYvgiFRf5FeRE36rH6Gm0/XraIw0ny6Mo0k1tMgg2MPn4EvF2qaKJt+1Z0GFzGfd RJV91liOAoGAippamlxpj4aOz1l8U8vFRwpJJWmqElBLJhikFhkinOGmY7pTZRySVNZs gNNoP5P8vgbCvBjHDsNsEwoD6JqV5hg09f2P/74xWDJV6gO7HlOy4suv8hsoM+4ptLl1 rY9EqQr5CSwKokXTmg2olvtLsCL/mldm8cuvk0FjS+vSRTfaBb+T0E9EtEY4wtiFgi7Y 8Jxw== X-Received: by 10.182.126.137 with SMTP id my9mr4765634obb.61.1398904263272; Wed, 30 Apr 2014 17:31:03 -0700 (PDT) Received: from [192.168.1.64] (pool-71-170-112-253.dllstx.fios.verizon.net. [71.170.112.253]) by mx.google.com with ESMTPSA id pt8sm51261036obb.5.2014.04.30.17.31.02 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 30 Apr 2014 17:31:02 -0700 (PDT) References: <20140430195924.GA1011@taco-shack.cow> <20140430211105.GA961@taco-shack.cow> Mime-Version: 1.0 (1.0) In-Reply-To: <20140430211105.GA961@taco-shack.cow> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Message-Id: X-Mailer: iPad Mail (11D201) From: Matthew Pherigo Subject: Re: Respecting Privacy: How To Prevent Spam Date: Wed, 30 Apr 2014 19:31:03 -0500 To: Mike Sanders Cc: "freebsd-questions@freebsd.org" 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: Thu, 01 May 2014 00:31:04 -0000 Hey Mike, First of all, it should be noted that the prevalence of spam on this mailing= list is not because the configuration of this list is insecure, but because= using email in mailing lists has always been an easy way to harvest email a= ddresses, and spammers have only now caught on. The first option for somebody to be secure in a mailing list would be to use= an email account only used for public mailing lists. But, let's be fair, no= body is going to do that. The second option is to do as you suggest and anonymize the list addresses w= ith only one mailing list address. Not considering the fact that this makes f= iguring out who the message is from much harder, this also causes a problem w= hen time comes to have a conversation OFF of the list. If two posters want t= o speak to each other off of the main mailing list, they have a problem: the= y have to exchange email addresses OVER the mailing list. This leaves you wi= th two options: either exchange email addresses in public (defeating the poi= nt of anonymization), or use email messages back-and-forth to execute a piec= e of key-exchange cryptography to exchange email addresses without making th= em public. If you ever find yourself doing that last part, you know you're p= robably doing something wrong. I think the problem is less about "is this mailing list secure" and more abo= ut "is email suited for this kind of use", to which I would say "no, not rea= lly, but the community here is totally worth using email for the wrong purpo= se." When you get the spam messages, flag them as spam with whatever email p= rovider you use. Since they're not being sent through the list and are inste= ad coming from their own domains, flagging them as spam will cause your emai= l provider's junk filter to pick up on those messages in the future and not a= llow any more of them to pass through. --Matt > On Apr 30, 2014, at 4:11 PM, Mike Sanders wro= te: >=20 > Mike Sanders wrote: >=20 >> >>=20 >> Under section 'Spam-specific posting filters': >>=20 >> Value: Hide the sender of a message, replacing it with the list address >> (Removes From, Sender and Reply-To fields) >>=20 >> Description: This tells Mailman to rewrite the header so that traffic >> appears to be coming from the list itself instead of the original poster.= >> Provides some added privacy for posters, but may be annoying to some list= >> members as mailbox headers show only the list name instead of the >> actual poster. >=20 > Okay enough... >=20 > Because I spoke out about this, spammers are attacking my inbox > with malformed email, attachments, etc. Don't know if these messages > are turning up on the list, but someone is replying to my list messages > with email such as: >=20 > 'Would you like to meet? I'll let you lick my twat' >=20 > If this list ever becomes secure look me up, I'd love to learn from you gu= ys. >=20 > I'm out. >=20 > --=20 > Mike Sanders > www: http://freebsd.hypermart.net > gpg: 0xD94D4C13 > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.or= g"