From: Sebastian Luque <spluque@gmail.com>
Subject: some messages ending up in 'bogus' group
Date: Fri, 08 Jul 2005 14:50:48 -0500 [thread overview]
Message-ID: <87wto1m607.fsf@gmail.com> (raw)
Dear List,
I recently found that a mail message sent to me ended up in the 'bogus'
group, much to my horror (because I was not subscribed to that one...until
now). I reanalyzed my ~/.gnus, but couldn't find anything that could cause
this, but reading the manual it seemed that this might have something to
do with it:
(require 'spam)
(setq spam-split-group "Spam"
spam-use-bogofilter t
nnmail-split-methods 'nnmail-split-fancy
nnmail-split-fancy
'(| (any ".*video4linux.*\\|.*Sympa\\|.*helixcommunity.*\\|.*aircanada.com.*\\|.*ostg.*" "Various")
("to" ".*ecolog-l.*" "Ecolog-L")
("to" ".*marmam.*" "Marmam")
("to" ".*mammal-l.*" "Mammal-L")
(: spam-split)
"mail.misc"))
(spam-initialize)
I added this not a long time ago, after learning to use spam, and I didn't
encounter this problem before that. The relevant info contains:
,-----[ (info "(gnus)Splitting Mail") <lines: 31 - 40> ]
| 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".) If no rule matched, the
| mail will end up in the `bogus' group. When new groups are created by
| splitting mail, you may want to run `gnus-group-find-new-groups' to see
| the new groups. This also applies to the `bogus' group.
`-----
so I guess I followed those instructions above, but perhaps someone can
correct me. Thanks in advance.
--
Sebastian P. Luque
next reply other threads:[~2005-07-08 19:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-08 19:50 Sebastian Luque [this message]
2005-07-09 12:36 ` Johan Bockgård
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=87wto1m607.fsf@gmail.com \
--to=spluque@gmail.com \
/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).