From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Kevin Gallagher" Newsgroups: gmane.emacs.devel Subject: Re: Why can I not receive mail from this list Date: Sun, 26 Feb 2006 13:05:02 -0600 Message-ID: <000d01c63b07$8c84ef90$0200a8c0@janus> References: <87bqwvy1k4.fsf-monnier+emacs@gnu.org> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; format=flowed; charset=iso-8859-1; reply-type=original Content-Transfer-Encoding: 7bit X-Trace: sea.gmane.org 1141014294 24716 80.91.229.2 (27 Feb 2006 04:24:54 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Mon, 27 Feb 2006 04:24:54 +0000 (UTC) Cc: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Feb 27 05:24:50 2006 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1FDZwF-0005q6-ET for ged-emacs-devel@m.gmane.org; Mon, 27 Feb 2006 05:24:48 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1FDZwI-0004tv-G2 for ged-emacs-devel@m.gmane.org; Sun, 26 Feb 2006 23:24:51 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1FDRCt-000388-8P for emacs-devel@gnu.org; Sun, 26 Feb 2006 14:05:23 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1FDRCi-00033w-K0 for emacs-devel@gnu.org; Sun, 26 Feb 2006 14:05:13 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1FDRCb-00031G-P0 for emacs-devel@gnu.org; Sun, 26 Feb 2006 14:05:07 -0500 Original-Received: from [206.46.252.46] (helo=vms046pub.verizon.net) by monty-python.gnu.org with esmtp (Exim 4.52) id 1FDRD8-0003rR-H1 for emacs-devel@gnu.org; Sun, 26 Feb 2006 14:05:38 -0500 Original-Received: from janus ([71.96.139.120]) by vms046.mailsrvcs.net (Sun Java System Messaging Server 6.2-4.02 (built Sep 9 2005)) with ESMTPA id <0IVB00FM96C93873@vms046.mailsrvcs.net> for emacs-devel@gnu.org; Sun, 26 Feb 2006 13:04:57 -0600 (CST) Original-To: "Stefan Monnier" , "Herbert Euler" X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2670 X-Mailer: Microsoft Outlook Express 6.00.2900.2670 X-Priority: 3 X-MSMail-priority: Normal X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:51005 Archived-At: From: "Stefan Monnier" : > The FSF mailer seems to regularly be mistakenly added to some blacklist > (spamcop IIRC). This happened again a few days ago. > I wish they had a whitelist as well. I'm sure this is happening because some criminals regularly use mailing lists to send out fraudulent mail and the FSF lists are no exception. Since signing on to several Emacs mailing lists, I periodically receive fraudulent notices about various problems with accounts I supposedly have with Ebay, PayPal, and quite a few banks. Each claims that there is a problem with my account and I should click on a link to deal with it. The bogus links in these messages typically redirect the unsuspecting person to a web page where the criminals try to steal personal information, account numbers, and passwords. It's not a daily occurrence, but it happens often enough to be a real problem for unmoderated mailing lists and unsuspecting readers of those lists, nevertheless. Each time I have received one of these suspect mail messages, I always examine the full mail header. Since signing up for the Emacs mailing lists, every one of these fraudulent notices sent to me has come by way of one of the Emacs mailing lists. All it takes is for one unsuspecting person to get burned and to report it. Then, seeing that a number of these are being sent through FSF lists, the site admin takes an easy path and blocks all mail from those lists and reports his findings to one or more of the blacklist sites. To prevent this from happening in the future, the administrator of the FSF lists may have no alternative but to take some defensive measures and put into place a filter that blocks the distribution of known fraudulent messages.