From: Andreas Fuchs <asf@void.at>
Subject: Re: How do you make spam automatically move to spam group on exit?
Date: Sun, 9 Mar 2003 11:33:44 +0000 (UTC) [thread overview]
Message-ID: <87heac22pu.fsf@eris.void.at> (raw)
In-Reply-To: <m3adg5zsli.fsf@heechee.beld.net>
On 2003-03-08, Ted Zlatanov <tzz@lifelogs.com> wrote:
> I added the spam-mark-ham-unread-before-move-from-spam-group variable,
> enjoy.
Great, thank you!
--
Andreas Fuchs, <asf@acm.org>, asf@jabber.at, antifuchs
irc.freenode.net's #emacs - online emacs advice from IRC addicts
next prev parent reply other threads:[~2003-03-09 11:33 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-07 20:34 Emerick Rogul
2003-03-07 20:56 ` Ted Zlatanov
2003-03-07 21:35 ` Emerick Rogul
2003-03-08 6:07 ` Ted Zlatanov
2003-03-08 13:21 ` Andreas Fuchs
2003-03-08 15:13 ` Ted Zlatanov
2003-03-08 17:10 ` Andreas Fuchs
2003-03-08 17:16 ` Ted Zlatanov
2003-03-09 11:33 ` Andreas Fuchs [this message]
2003-03-09 6:26 ` Emerick Rogul
2003-03-09 10:59 ` Jorge Godoy
2003-03-09 17:24 ` Emerick Rogul
2003-03-10 15:53 ` Ted Zlatanov
2003-03-10 16:31 ` Emerick Rogul
2003-03-10 17:15 ` Ted Zlatanov
2003-03-10 18:23 ` Ted Zlatanov
2003-03-10 15:41 ` Ted Zlatanov
2003-03-10 16:20 ` Emerick Rogul
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=87heac22pu.fsf@eris.void.at \
--to=asf@void.at \
/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).