Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Josh Huber <huber@alum.wpi.edu>
Subject: Re: fancy splitting and procmail
Date: Wed, 03 Jul 2002 16:30:53 -0400	[thread overview]
Message-ID: <87pty4366a.fsf@alum.wpi.edu> (raw)
In-Reply-To: <87d6u4va4c.fsf@Pulsar.resI.insa-lyon.fr>

Boris DAIX <Boris.Daix@insa-lyon.fr> writes:

> (setq nnmail-split-fancy 
> 	'(| 
> 	    (any "debian-\\b\\(\\w+\\)@lists.debian.org" "debian-\\1")
> 	    (any "ding@gnus.org" "gnus.list")
> 	    (any "jackit-devel@sourceforge.net" "JACK.list")
> 	    mail.misc
> 	 )
> )
> (setq nnmail-split-method 'nnmail-split-fancy)
> (setq nnmail-resplit-incoming t)
> ------------------------------------------------------
>
> I don't understand why this doesn't work... "any" means To, From, Cc ?
> I don't even trust the rules anymore...

What doesn't work?  I've had problems in the past matching some text
with fancy split rules that were caused by gnus using
re-search-backward to scan the message.

For debian lists, I suggest matching on something like the
Resent-Sender header.  For example, here is the nnmail-split-fancy
entry I use for my debian lists:

	("Resent-Sender"
	 "debian-\\(\\w+\\)\\(-request\\)?@lists\\.debian\\.org"
	 "mail.lists.debian.\\1")

Hope that helps.

-- 
Josh Huber


  reply	other threads:[~2002-07-03 20:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87y9ctxh3l.fsf@Pulsar.resI.insa-lyon.fr>
     [not found] ` <afuvmh$n6s$1@wsc10.lrz-muenchen.de>
2002-07-03 16:58   ` Boris DAIX
     [not found]     ` <afvb1r$2bj$1@wsc10.lrz-muenchen.de>
     [not found]       ` <87bs9olniq.fsf@Pulsar.resI.insa-lyon.fr>
2002-07-04 14:57         ` Kai Großjohann
2002-07-03 20:18   ` Boris DAIX
2002-07-03 20:30     ` Josh Huber [this message]
2002-07-03 20:49     ` Jack Twilley

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87pty4366a.fsf@alum.wpi.edu \
    --to=huber@alum.wpi.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).