Gnus development mailing list
 help / color / mirror / Atom feed
From: David Z Maze <dmaze@MIT.EDU>
Cc: ding@gnus.org
Subject: Re: spam.el not moving ham message from spam group
Date: Fri, 24 Jan 2003 14:31:56 -0500	[thread overview]
Message-ID: <y68n0lq1h03.fsf@multics.mit.edu> (raw)
In-Reply-To: <4nadhq1mzq.fsf@lockgroove.bwh.harvard.edu> (Ted Zlatanov's message of "Fri, 24 Jan 2003 12:22:33 -0500")

Ted Zlatanov <tzz@lifelogs.com> writes:
> With total-expire, read messages are always assigned the expired mark,
> right?

No, you're thinking of auto-expire.  total-expire means that expiry
treats any article with a read mark (not just 'E') as expirable.
FWIW, I haven't had any issues using spam.el and total expiry together.

-- 
David Maze             dmaze@mit.edu          http://www.mit.edu/~dmaze/
"Theoretical politics is interesting.  Politicking should be illegal."
	-- Abra Mitchell




  reply	other threads:[~2003-01-24 19:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-24 13:36 Niklas Morberg
2003-01-24 17:22 ` Ted Zlatanov
2003-01-24 19:31   ` David Z Maze [this message]
2003-01-27  8:35   ` Niklas Morberg
2003-01-27 19:11     ` Torsten Hilbrich
2003-01-27 19:37       ` Ted Zlatanov

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=y68n0lq1h03.fsf@multics.mit.edu \
    --to=dmaze@mit.edu \
    --cc=ding@gnus.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 NNTP newsgroup(s).