From: asjo@koldfront.dk (Adam Sjøgren)
Subject: Re: spam.el reporting and moving ham out of spam groups.
Date: Mon, 07 Jun 2004 20:15:52 +0200 [thread overview]
Message-ID: <87brjv2q07.fsf@koldfront.dk> (raw)
In-Reply-To: <4nn03fpa10.fsf@lifelogs.com>
On 7 Jun 2004 13:12:27 -0400, Ted wrote:
>> On 26 May 2004 12:16:07 -0400, Ted wrote:
>>>> But shouldn't spam-process-ham-in-nonham-groups do this? If it
>>>> doesn't, there's a bug in my code.
>>> I just tested with latest cvs; yes it does work.
>> Uh, it gets processed, but not respooled.
>> Maybe I need to set "spam-move-ham-in-nonham-groups" to t?
> There is no such parameter now.
I know.
> The logic for moving ham out of spam groups is:
[...]
Yes - that is what the (third part of the) patch we are discussing
(<news:874qq4bjr2.fsf@koldfront.dk>) changes.
> The belief is that ham is already in the right place outside of spam
> groups - why should you respool it? It only makes sense to process
> ham outside of spam groups.
That I want to change this, is an artefact stemming from the fact that
I do not want spam in my spam-group automatically marked expirable.
Thus I keep my spam-group not classified as spam, but non-classified.
> Anyhow, I guess this logic can be changed, but I don't think it
> makes sense.
If you mark something as ham in a non-classified group, it makes sense
to process it, but not to move/respool it?
Okay, I see the point - to me both choices make sense (so "my version"
doesn't make _more_ sense than yours :-))
> If you feel strongly about this, and/or anyone else wants to
> comment, feel free. I just don't want to make spam.el too esoteric.
Don't make is more esoteric on my account. I can easily keep patching.
The root of my configurations mess is that articles in groups
classified as spam automatically get marked expirable (which I don't
want), so if it's easier to make that configurable, that could perhaps
be a compromise. It would solve the whole problem for me.
Again, if you think that is making spam.el too cluttered, don't change
it for just one person :-)
Best regards,
--
"Who ees thees Kählveen?" Adam Sjøgren
asjo@koldfront.dk
next prev parent reply other threads:[~2004-06-07 18:15 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-25 13:17 Daniel Pittman
2004-05-25 14:14 ` Kai Grossjohann
2004-05-26 4:41 ` Daniel Pittman
2004-05-26 16:17 ` Ted Zlatanov
2004-05-25 15:37 ` Adam Sjøgren
2004-05-26 4:46 ` Daniel Pittman
2004-05-26 8:38 ` Adam Sjøgren
2004-05-26 16:16 ` Ted Zlatanov
2004-05-26 20:29 ` Adam Sjøgren
2004-05-28 19:52 ` Adam Sjøgren
2004-06-07 17:12 ` Ted Zlatanov
2004-06-07 18:15 ` Adam Sjøgren [this message]
2004-06-08 14:24 ` Ted Zlatanov
2004-05-26 16:14 ` Ted Zlatanov
2004-05-26 20:23 ` Miles Bader
2004-05-27 6:15 ` Daniel Pittman
2004-05-27 14:35 ` 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=87brjv2q07.fsf@koldfront.dk \
--to=asjo@koldfront.dk \
/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).