From: Reiner Steib <reinersteib+gmane@imap.cc>
Subject: Re: spam.el/spam-report.el: Gmane spam reporting broken in No Gnus
Date: Tue, 20 Sep 2005 20:19:38 +0200 [thread overview]
Message-ID: <v9br2n61qd.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <4nek7jk83j.fsf@lifelogs.com>
On Tue, Sep 20 2005, Ted Zlatanov wrote:
> On Thu, 08 Sep 2005, reinersteib+gmane@imap.cc wrote:
[...]
> Can you try to use (spam spam-use-gmane) instead of
> gnus-group-spam-exit-processor-report-gmane?
Then it works:
--8<---------------cut here---------------start------------->8---
(setq
gnus-verbose 10
spam-report-gmane-use-article-number nil
spam-report-url-ping-function 'spam-report-url-to-file
gnus-parameters '(("^gmane\\."
(spam-process
((spam spam-use-gmane))))))
(spam-initialize)
--8<---------------cut here---------------end--------------->8---
>> I found out, that the Gmane entry has been removed from
>> `spam-list-of-processors' ("The OBSOLETE `spam-list-of-processors'
>> list."), but re-adding it didn't help:
[...]
> If you can test as I showed above, that would help me determine if the
> bug is in the Gmane reporting or just the backwards compatibility.
It seems it's in the backwards compatibility. With this patch [1],
`spam-report-url-to-file' still is not called using this settings:
--8<---------------cut here---------------start------------->8---
(setq
spam-report-gmane-use-article-number nil
spam-report-url-ping-function 'spam-report-url-to-file
gnus-parameters '(("^gmane\\."
(spam-process
(gnus-group-spam-exit-processor-report-gmane)))))
(spam-initialize)
--8<---------------cut here---------------end--------------->8---
I'm a little confused about the obsolescence: In [v5-10]/lisp/spam.el
`spam-list-of-processors' does not seem to be obsolete (CMIIW,
please). But in the manual, there is:
,----[ [v5-10]/texi/gnus.texi ]
| @emph{WARNING}
|
| Instead of the obsolete
| @code{gnus-group-spam-exit-processor-report-gmane}, it is recommended
| that you use @code{'(spam spam-use-gmane)}. Everything will work the
| same way, we promise.
`----
While at it: In the v5-10 branch, there's the following comment:
,----[ [v5-10]/lisp/spam.el ]
| ;; note that spam-use-gmane is not a legitimate check
| (spam-use-gmane nil
| spam-report-gmane-register-routine
| ;; does Gmane support unregistration?
| nil
| nil)
`----
Gmane supports unregistration: You can reverse the report
http://spam.gmane.org/gmane.foo.bar:1234 with
http://unspam.gmane.org/gmane.foo.bar:1234
Bye, Reiner.
[1]
,----[ <f1> v spam-list-of-processors RET ]
| spam-list-of-processors is a variable defined in `spam'.
| Its value is shown below.
|
| [...]
|
| Value:
| ((gnus-group-spam-exit-processor-report-gmane spam spam-use-gmane)
| (gnus-group-spam-exit-processor-bogofilter spam spam-use-bogofilter)
| [...]
| (gnus-group-ham-exit-processor-spamoracle ham spam-use-spamoracle))
`----
--
,,,
(o o)
---ooO-(_)-Ooo--- | PGP key available | http://rsteib.home.pages.de/
next prev parent reply other threads:[~2005-09-20 18:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-08 15:07 Reiner Steib
2005-09-20 16:38 ` Ted Zlatanov
2005-09-20 18:19 ` Reiner Steib [this message]
2005-09-21 14:45 ` Ted Zlatanov
2005-09-21 16:51 ` Reiner Steib
2005-09-22 12:20 ` Reiner Steib
2005-10-04 18:18 ` 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=v9br2n61qd.fsf@marauder.physik.uni-ulm.de \
--to=reinersteib+gmane@imap.cc \
--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).