From: Niklas Morberg <niklas.morberg@axis.com>
Subject: Re: Bug when using the agent and spam.el
Date: Wed, 12 Feb 2003 09:11:33 +0100 [thread overview]
Message-ID: <u4r79x6iy.fsf@axis.com> (raw)
In-Reply-To: <4nd6lyr8yc.fsf@lockgroove.bwh.harvard.edu> (Ted Zlatanov's message of "Tue, 11 Feb 2003 13:03:23 -0500")
Ted Zlatanov <tzz@lifelogs.com> writes:
> I don't use the agent, so I can't really duplicate your situation.
It's really easy to set-up (see e.g. Kevins message
<uadh2hecc.fsf@xpediantsolutions.com> in the nnimap usage
model thread), but I don't think you need to bother. Your
latest change with the process-mark stuff seems to have
fixed this as well.
> Are you sure your spam-process-destination is set for that
> group? What does (gnus-parameter-spam-process-destination
> gnus-newsgroup-name) return when you are in that group?
Just for the record, this was properly set up. (g-p-s-p-d
g-n-n) returned "spam".
Anyway, things seem to be running a lot more smoothly now,
thanks a lot for looking at this.
Niklas
prev parent reply other threads:[~2003-02-12 8:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-11 11:07 Niklas Morberg
2003-02-11 18:03 ` Ted Zlatanov
2003-02-12 8:11 ` Niklas Morberg [this message]
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=u4r79x6iy.fsf@axis.com \
--to=niklas.morberg@axis.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).