From: Jake Colman <colman@ppllc.com>
Subject: bug copying ham from spam folder
Date: Thu, 30 Oct 2003 18:59:49 -0500 [thread overview]
Message-ID: <76y8v2z37u.fsf@newjersey.ppllc.com> (raw)
Step by step, little by little...
I've figured out that ham in a spam group, or spam in a ham, cannot be sent
directly for training but must first be copied to an appropriate ham or spam
group where its exit processor will train it. Great!
I marked my ham message in my spam group and exited. I got the following
error: "nnnil does not support article copying".
I use nnnil as my gnus-select-method, as recommended for situations where
there is no news server and just email. nnimap is my
gnus-secondary-select-methods. I guess that I actually configure things
correctly and wanted to copy the message from my nnimap-based spam group to
my nnimap-based ham group but triggered this error instead.
BTW, gnus does support moving message between nnimap folders since I do it
all the time.
Here is the backtrace:
Signaling: (error "nnnil does not support article copying")
signal(error ("nnnil does not support article copying"))
cerror("%s does not support article copying" nnnil)
apply(cerror "%s does not support article copying" nnnil)
error("%s does not support article copying" nnnil)
gnus-summary-move-article(nil "INBOX/Misc")
spam-ham-copy-or-move-routine(nil ("INBOX/Misc"))
spam-ham-move-routine("INBOX/Misc")
spam-summary-prepare-exit()
run-hooks(spam-summary-prepare-exit)
apply(run-hooks spam-summary-prepare-exit)
gnus-run-hooks(gnus-summary-prepare-exit-hook)
gnus-summary-exit()
gnus-summary-catchup-and-exit(nil)
call-interactively(gnus-summary-catchup-and-exit)
--
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-10-30 23:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-30 23:59 Jake Colman [this message]
[not found] ` <m3n0bjrkv1.fsf@biostaff03.nuigalway.ie>
2003-10-31 14:23 ` Jake Colman
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=76y8v2z37u.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).