From: Ted Zlatanov <tzz@lifelogs.com>
Subject: Re: Marking as spam -- spam-stat
Date: Fri, 31 Oct 2003 12:01:22 -0500 [thread overview]
Message-ID: <4nad7h8hp9.fsf@lockgroove.bwh.harvard.edu> (raw)
In-Reply-To: <u8yn2ikxt.fsf@adobe.com> (Danny Siu's message of "Thu, 30 Oct 2003 11:29:02 -0800")
On Thu, 30 Oct 2003, dsiu@adobe.com wrote:
> It can be done. If you see a spam in your ham group, just do a
> "M-d" (gnus-summary-mark-as-spam) in the summary buffer. The spam
> would then be moved to the spam group and spam-stat would be update
> when you exit the group.
>
> The same can be done with ham in spam group, except that there is no
> key binding for moving ham back in spam group back to inbox. You
> just need to do a "B m" and spam-stat would be updated when you exit
> the group.
I think Peter may like the spam-process-ham-in-nonham-groups and
spam-process-ham-in-spam-groups settings (I prefer the latter, and
plan to make it t by default). They make ham-process-destination in
a spam group work as expected.
Ted
prev parent reply other threads:[~2003-10-31 17:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-29 21:31 Peter Lee
2003-10-30 10:20 ` Ian Dobbie
2003-10-30 19:29 ` Danny Siu
2003-10-31 16:20 ` Peter Lee
2003-10-31 17:01 ` Ted Zlatanov [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=4nad7h8hp9.fsf@lockgroove.bwh.harvard.edu \
--to=tzz@lifelogs.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).