Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
Cc: ding@gnus.org
Subject: Re: Expiring spam groups
Date: Thu, 14 Dec 2006 19:18:18 +0000	[thread overview]
Message-ID: <g69zm9qffr9.fsf@lifelogs.com> (raw)
In-Reply-To: <el9uvr$7mu$1@sea.gmane.org> (vedm's message of "Thu\, 07 Dec 2006 15\:53\:15 -0500")

On  7 Dec 2006, mlist@rogers.com wrote:

> I have a problem with spam group expiration. My mail is split by
> procmail and all spam goes into a "spam" group. I have this group in the
> spam-junk-mailgroups. 
>
> When I go into the "spam" group I see that the newly arrived spam
> messages are marked as spam (the '$' mark). When I exit the group and
> then enter it again I see that those same messages are marked as expired
> (E), so I expect that they would disappear in several days - but instead
> the messages that were marked as "E" after some time are shown with the
> mark "O", and they never disappear..
>
> What am I doing wrong? (I do not have any group or topic parameters).

Hi,

spam.el will just mark the articles as expired when you exit the
group.  So the rest of the work is done by Gnus, which has built-in
intelligence regarding article expiry.  You need to look in the manual
for that info, it's not too complicated.

Another possibility is that right now, the spam/ham-process-destination
can be one of these:

- nil ("leave spam in the group, expired")
- 'respool ("send back to the split method"--this is for ham)
- one or more groups (copy to N-1 groups, move to the last one)

I could add a 'delete option, which would just delete whatever
articles match, if 'respool or group names are not specified.  So you
wouldn't use it for ham-process-destination probably, but it could
make sense for spam-process-destination.  Let me know if you need
that, rather than using the normal Gnus expiry process.

Ted

p.s. I use the word "expiry" because Gnus uses it a lot.  I don't know
if "expiration" is more appropriate, but just keep it in mind if you
do an M-x apropos :)



  reply	other threads:[~2006-12-14 19:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-07 20:53 vedm
2006-12-14 19:18 ` Ted Zlatanov [this message]
2006-12-23 16:00   ` vedm
2006-12-27 15:46     ` Ted Zlatanov
2006-12-27 16:40       ` Dimitre Liotev
2006-12-27 19:25         ` 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=g69zm9qffr9.fsf@lifelogs.com \
    --to=tzz@lifelogs.com \
    --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).