From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Kai Grossjohann Newsgroups: gmane.emacs.devel Subject: Re: RMAIL against Texinfo Date: Sun, 01 Feb 2004 22:51:31 +0100 Sender: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Message-ID: <87isiq5uzg.fsf@emptyhost.emptydomain.de> References: <2914-Sun01Feb2004191602+0200-eliz@elta.co.il> NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1075672546 16172 80.91.224.253 (1 Feb 2004 21:55:46 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Sun, 1 Feb 2004 21:55:46 +0000 (UTC) Original-X-From: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Sun Feb 01 22:55:41 2004 Return-path: Original-Received: from quimby.gnus.org ([80.91.224.244]) by deer.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 1AnPZ6-0006Qj-00 for ; Sun, 01 Feb 2004 22:55:40 +0100 Original-Received: from monty-python.gnu.org ([199.232.76.173]) by quimby.gnus.org with esmtp (Exim 3.35 #1 (Debian)) id 1AnPZ6-0003c8-00 for ; Sun, 01 Feb 2004 22:55:40 +0100 Original-Received: from localhost ([127.0.0.1] helo=monty-python.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.24) id 1AnPW7-0008MT-CF for emacs-devel@quimby.gnus.org; Sun, 01 Feb 2004 16:52:35 -0500 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.24) id 1AnPVa-0008LL-FA for emacs-devel@gnu.org; Sun, 01 Feb 2004 16:52:02 -0500 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.24) id 1AnPV2-000816-Vf for emacs-devel@gnu.org; Sun, 01 Feb 2004 16:52:01 -0500 Original-Received: from [80.91.224.249] (helo=main.gmane.org) by monty-python.gnu.org with esmtp (Exim 4.24) id 1AnPV2-00080v-F7 for emacs-devel@gnu.org; Sun, 01 Feb 2004 16:51:28 -0500 Original-Received: from list by main.gmane.org with local (Exim 3.35 #1 (Debian)) id 1AnPV1-0002Sb-00 for ; Sun, 01 Feb 2004 22:51:27 +0100 Original-Received: from 213-203-244-156.kunde.vdserver.de ([213.203.244.156]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun Feb 1 21:51:27 2004 Original-Received: from kai by 213-203-244-156.kunde.vdserver.de with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun Feb 1 21:51:27 2004 X-Injected-Via-Gmane: http://gmane.org/ Original-To: emacs-devel@gnu.org Original-Lines: 40 Original-X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: 213-203-244-156.kunde.vdserver.de User-Agent: Gnus/5.110002 (No Gnus v0.2) Emacs/21.2 (gnu/linux) Cancel-Lock: sha1:X3DIVDx0qEem+D4uAGNgJSagF7I= X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.2 Precedence: list List-Id: Emacs development discussions. List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Xref: main.gmane.org gmane.emacs.devel:19625 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:19625 "Eli Zaretskii" writes: > That seems like a simple bug to me: the intent was to remove the > "info-*" mailing lists, which are essentially read-only (you are sent > information, but are not supposed to reply), so the regexp should > have been anchored at the beginning of a word, like this: > > "\\\\|\\" > > (I think my username and email addresses should get the same anchors, > to avoid filtering out someone whose username happens to be "noteliz", > for example.) This will still remove frumple-info and tex-info from the list of addresses. Also, there is experience with nnmail-fancy-split in Gnus, which automatically surrounds regexes with \\< and \\>. Users are supposed to say ".*foo.*" if they want to undo the effect of \\<...\\>. But after some years it turned out that this didn't always work, and now there is additional code in the function supporting nnmail-split-fancy which checks for the regex starting with ".*"... I forgot what exactly was the problem, though. I'm afraid that with a similar change for rmail-dont-reply-to-names, you might fall into similar traps. And it doesn't even cover all cases. A "real" solution might have to parse email addresses such that the rules can be formulated in an unambiguous way. Maybe it's useful to also talk with the Gnus folks, since the same problem happens there (though in a different context). Kai PS: nnmail-fancy-split allows you to express which incoming emails should go into which group (or mail file, or folder, or ... well, I hope you understand what I mean). So it does something very different, but it also matches regexes against email addresses.