From: Reiner Steib <4.uce.03.r.s@nurfuerspam.de>
Cc: Ding List <ding@gnus.org>
Subject: Re: How to report spam with Gnus
Date: Sat, 17 Apr 2004 17:57:46 +0200 [thread overview]
Message-ID: <v9n05avbph.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <l1zn9bogsv.fsf@budvar.future-i.net> (Ed Avis's message of "Fri, 16 Apr 2004 20:37:20 +0100")
[ This is not relevant to Gmane anymore. Let's shift the discussion
to gmane.emacs.gnus.general aka <ding@gnus.org>.
(-> Mail-Followup-To: Ding List <ding@gnus.org> ]
On Fri, Apr 16 2004, Ed Avis wrote:
> Reiner Steib <4.uce.03.r.s@nurfuerspam.de> writes:
>
>>>I can't find any documentation on how to use Gnus to report an
>>>article as spam.
>>
>>See (info "(gnus)Gmane Spam Reporting")
>
> Yes, that is the page I looked at, but I didn't understand it. (I can
> customize-variable gnus-spam-process-newsgroups but I didn't know what
> to set it to.)
Hm, could suggest an improvement to the current wording?
,----[ (info "(gnus)Gmane Spam Reporting") ]
| -- Variable: gnus-group-spam-exit-processor-report-gmane
| Add this symbol to a group's `spam-process' parameter by
| customizing the group parameters or the
| `gnus-spam-process-newsgroups' variable. When this symbol is
| added to a group's `spam-process' parameter, the spam-marked
| articles groups will be reported to the Gmane administrators via a
| HTTP request.
`----
> Thanks, I have set that using M-x customize-variable gnus-parameters,
> so now my ~/.xemacs/custom.el has something like
>
> (custom-set-variables
> '(gnus-parameters '(("^gmane\\."
> (spam-process
> (gnus-group-spam-exit-processor-report-gmane))))
> )
Looks fine.
> I will try it out soon.
If you set `gnus-verbose' to some high value, say 8, you will see
what's going on looking at the " *Message-Log*" (XEmacs) buffer.
Bye, Reiner.
--
,,,
(o o)
---ooO-(_)-Ooo--- PGP key available via WWW http://rsteib.home.pages.de/
parent reply other threads:[~2004-04-17 15:57 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <l1zn9bogsv.fsf@budvar.future-i.net>]
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=v9n05avbph.fsf@marauder.physik.uni-ulm.de \
--to=4.uce.03.r.s@nurfuerspam.de \
--cc=ding@gnus.org \
--cc=reiner.steib@gmx.de \
/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).