From: Reiner Steib <4.uce.03.r.s@nurfuerspam.de>
Subject: Re: mail-splitting issue
Date: Tue, 13 Apr 2004 00:09:55 +0200 [thread overview]
Message-ID: <v9fzb8kfv0.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <8jfad1hjjd2.fsf@kamel.stud.ntnu.no>
On Mon, Apr 12 2004, Lars Tobias Borsting wrote:
> About improving the manual; perhaps make the text about the general rule
> stand out more, so that everyone must see it, even those who just skim the
> text for some quick documentation. Like me... ;-) An especially point
> out that if the general rule isn't present, the mail will vanish. Maybe
> I should give Lars Magne a hint about this.
According to your headers, you are using a very old version of Gnus
(5.6.45). I'd suggest to upgrade to Gnus 5.10.6. And I think that
the manual in 5.10.6 is quite clear about this, WDYT?
,----[ (info "(gnus)Splitting Mail") ]
| 6.3.3 Splitting Mail
|
| The `nnmail-split-methods' variable says how the incoming mail is to be
| split into groups.
|
| (setq nnmail-split-methods
| '(("mail.junk" "^From:.*Lars Ingebrigtsen")
| ("mail.crazy" "^Subject:.*die\\|^Organization:.*flabby")
| ("mail.other" "")))
|
| This variable is a list of lists, where the first element of each of
| these lists is the name of the mail group (they do not have to be called
| something beginning with `mail', by the way), and the second element is
| a regular expression used on the header of each mail to determine if it
| belongs in this mail group. The first string may contain `\\1' forms,
| like the ones used by `replace-match' to insert sub-expressions from
| the matched text. For instance:
|
| ("list.\\1" "From:.* \\(.*\\)-list@majordomo.com")
|
| The second element can also be a function. In that case, it will be
| called narrowed to the headers with the first element of the rule as the
| argument. It should return a non-`nil' value if it thinks that the
| mail belongs in that group.
|
| The last of these groups should always be a general one, and the
| regular expression should _always_ be `*' so that it matches any mails
| that haven't been matched by any of the other regexps. (These rules are
| processed from the beginning of the alist toward the end. The first
| rule to make a match will "win", unless you have crossposting enabled.
| In that case, all matching rules will "win".)
`----
> Another approach is that the mail-spliting function could be modified
> check if there is such a general rule and if not, ask whether general
> mail should go up in to thin air.
This has already be done in Gnus 5.10.6, AFAICS:
,----
| 2003-10-17 Lars Magne Ingebrigtsen <larsi@gnus.org>
| [...]
| * nnmail.el (nnmail-article-group): Default to "bogus".
`----
Bye, Reiner.
--
,,,
(o o)
---ooO-(_)-Ooo--- PGP key available via WWW http://rsteib.home.pages.de/
prev parent reply other threads:[~2004-04-12 22:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-12 14:11 Lars Tobias Borsting
[not found] ` <874qrp457j.fsf@exal.austin.rr.com>
2004-04-12 15:11 ` Jochen Küpper
2004-04-12 15:52 ` Al Arduengo
[not found] ` <8jfad1hjjd2.fsf@kamel.stud.ntnu.no>
2004-04-12 22:09 ` Reiner Steib [this message]
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=v9fzb8kfv0.fsf@marauder.physik.uni-ulm.de \
--to=4.uce.03.r.s@nurfuerspam.de \
--cc=reiner.steib@gmx.de \
/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).