From: vedm <mlist@rogers.com>
Cc: tzz@lifelogs.com
Subject: Re: Expiring spam groups
Date: Sat, 23 Dec 2006 11:00:37 -0500 [thread overview]
Message-ID: <emjjr6$i0v$1@sea.gmane.org> (raw)
In-Reply-To: <g69zm9qffr9.fsf@lifelogs.com>
Ted Zlatanov <tzz@lifelogs.com> writes:
> 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 :)
I still do not understand why the expiry mark "E" disappears from the
articles in my spam group.
I set up my spam group so:
(add-to-list 'spam-junk-mailgroups "nnimap+localhost:spam")
When I get mail, procmail splits it and puts the spam in a "spam" mbox
file which is one of my IMAP folders. (I use the crm114 spam filter and
the dovecot IMAP server)
Now when I go into the spam group in Gnus (that is the "spam" IMAP
folder), all new spam is marked as spam ("$"). When I exit the group and
then open it again after a short time, I see that the same articles
which were marked as spam are now marked as expired ("E"). But when some
more time passes, and I open the spam group a few more times, I see that
the "E" mark has disappeared from the older spam articles - so my spam
group keeps growing.
The Gnus documentation says that expired articles are deleted after some
time - but in my spam group expired articles become "unexpired" again,
and so far I haven't found out why this happens.
--
vedm
next prev parent reply other threads:[~2006-12-23 16:00 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
2006-12-23 16:00 ` vedm [this message]
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='emjjr6$i0v$1@sea.gmane.org' \
--to=mlist@rogers.com \
--cc=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).