From: Ted Zlatanov <tzz@lifelogs.com>
Subject: Re: How do you make spam automatically move to spam group on exit?
Date: Mon, 10 Mar 2003 10:41:40 -0500 [thread overview]
Message-ID: <4nllznteiz.fsf@lockgroove.bwh.harvard.edu> (raw)
In-Reply-To: <vuobs0l5a3y.fsf@csa.bu.edu> (Emerick Rogul's message of "Sun, 09 Mar 2003 01:26:25 -0500")
On Sun, 09 Mar 2003, emerick@cs.bu.edu wrote:
> Ted Zlatanov writes:
>
>> Look at your ham marks - only those articles marked as ham (Unread
>> messages do not count!) will be processed as ham.
>
> My ham group is an auto-expirable group. It seems that it gets the
> 'E' mark before it's sent to the ham processor; when I exit the
> group, none of my ham is processed by the ham processor. If I
> explicitly mark the ham with 'd' before exiting the group, it's
> correctly processed as ham. Is that really the correct behavior?
The intent is to have messages that you read marked "R" (read-mark),
and that's a ham mark. With auto-expiry that doesn't work, of
course.
> I'd expect any new non-spam mail in a ham group to be processed by
> the ham processor on group exit (regardless of whether or not the
> message was auto-expired).
I suppose it could be added as a feature,
spam-treat-non-spam-as-ham-in-ham-group or something like that. Is
Jorge's solution of using total-expire inadequate?
Thanks
Ted
next prev parent reply other threads:[~2003-03-10 15:41 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
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 [this message]
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=4nllznteiz.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).