From: Ted Zlatanov <tzz@lifelogs.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Spliting in Gnus
Date: Mon, 15 Sep 2008 09:01:07 -0500 [thread overview]
Message-ID: <86prn5qzj0.fsf@lifelogs.com> (raw)
In-Reply-To: mailman.19263.1221470614.18990.help-gnu-emacs@gnu.org
On Mon, 15 Sep 2008 17:23:10 +0800 Magicloud Magiclouds <magicloud.magiclouds@gmail.com> wrote:
MM> I am trying to use Gnus. While I was trying the function of
MM> "spliting", I got problem.
MM> It did not report any error, just move my mail into "bogus" folder,
MM> and kept doing this no matter how I modified the configuration.
MM> Why?
By the way, there is a Gnus-specific newsgroup (gnu.emacs.gnus).
The "bogus" group catches miscellaneous configuration errors for
technical reasons. Cut out rules until you find the broken one, or
start with a known good configuration and add rules, or post your
configuration here and maybe someone will spot the problem.
Ted
next parent reply other threads:[~2008-09-15 14:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.19263.1221470614.18990.help-gnu-emacs@gnu.org>
2008-09-15 14:01 ` Ted Zlatanov [this message]
2008-09-15 9:23 Spliting in Gnus Magicloud Magiclouds
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86prn5qzj0.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=help-gnu-emacs@gnu.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).