From: "Ted Zlatanov" <tzz@lifelogs.com>
Subject: Re: spam-report.el pinging too fast?
Date: 25 May 2004 14:50:27 -0400 [thread overview]
Message-ID: <4naczw8hos.fsf@lifelogs.com> (raw)
In-Reply-To: <m3ekp9h1ui.fsf@quimbies.gnus.org> (Lars Magne Ingebrigtsen's message of "Tue, 25 May 2004 00:55:33 +0200")
On Tue, 25 May 2004, larsi@gnus.org wrote:
> Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
>
>> So there's two solutions to this: Either spam-report.el could wait
>> for a response (and serialize the reports), or I could write a new
>> "programmatic" spam.php that queues the reports and does the real
>> handling of them later.
>
> I've now done the latter. :-)
>
> The new URL is
>
> http://gmane.org/ping-spam.php?group=some.group&article=1234&command=spam
>
> (or unspam).
>
> spam.gmane.org checks User-Agent, and if it contains
> "spam-report.el", it'll just queue the report.
So this code in spam-report.el will have to change:
(if spam-report-gmane-use-article-number
(spam-report-url-ping
"spam.gmane.org"
(format "/%s:%d"
(gnus-group-real-name gnus-newsgroup-name)
article))
or does it still work? When I connected directly it seemed to be OK,
but I wasn't sure if you're rewriting properly or it's going to
/dev/null.
Hmmm, maybe I should also have a ham Gmane reporter! I didn't know
you could "unspam." Does it work with the
http://unspam.gmane.org/GROUP:ARTICLE format as you would expect? I
tested and it looked OK, but same question as above...
Thanks
Ted
prev parent reply other threads:[~2004-05-25 18:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-24 22:40 Lars Magne Ingebrigtsen
2004-05-24 22:55 ` Lars Magne Ingebrigtsen
2004-05-25 11:23 ` Reiner Steib
2004-05-25 18:50 ` Ted Zlatanov [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=4naczw8hos.fsf@lifelogs.com \
--to=tzz@lifelogs.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).