From: Jake Colman <colman@ppllc.com>
Subject: Problem Moving Ham from Spam
Date: Mon, 03 Nov 2003 09:56:52 -0500 [thread overview]
Message-ID: <76brrtwle3.fsf@newjersey.ppllc.com> (raw)
I thought I had this all worked out but it didn't quite work out right.
My spam group has the following group parameters set:
((uidvalidity . "71437")
(timestamp 16294 26744)
(auto-expire . t)
(registry-ignore . t)
(spam-contents gnus-group-spam-classification-spam)
(spam-process
(gnus-group-spam-exit-processor-bogofilter gnus-group-ham-exit-processor-bogofilter))
(ham-process-destination . "nnimap+hamilton:INBOX/Misc")
(expiry-wait . 2))
I also set the global variable
spam-mark-ham-unread-before-move-from-spam-group to true.
I entered the group and tickeed ("!") those messages that were really ham. I
did a 'c' on the group and watched it all chug away expecting to have my ham
moved to the INBOX/Misc folder marked unread. Instead, the ticked messages
remained as ticked messages in my spam folder and did not get moved.
Two questions:
1) What did I do wrong? Do I need to specify the ham-marks group parameter
for this to work? I didn't think so since the tick mark shold be
comnsidered a ham mark by default, no?
2) How do I fix this now? I want the ticked messages to be trained as ham
and moved. Do I just move them manually to my ham group and let them get
trained by the ham group's exit processor?
--
Jake Colman
Principia Partners LLC Phone: (201) 209-2467
Harborside Financial Center Fax: (201) 946-0320
902 Plaza Two E-mail: colman@ppllc.com
Jersey City, NJ 07311 www.principiapartners.com
next reply other threads:[~2003-11-03 14:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-03 14:56 Jake Colman [this message]
2003-11-03 16:13 ` Jody Klymak
2003-11-03 16:58 ` Michael Shields
2003-11-03 19:01 ` 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=76brrtwle3.fsf@newjersey.ppllc.com \
--to=colman@ppllc.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).