From: Ted Zlatanov <tzz@lifelogs.com>
Cc: ding@gnus.org
Subject: Re: "url ping" spam reporting with wget
Date: Tue, 09 Sep 2003 14:16:45 -0400 [thread overview]
Message-ID: <4noext3jzm.fsf@lockgroove.bwh.harvard.edu> (raw)
In-Reply-To: <vw3k78i31cl.fsf@informatik.uni-tuebingen.de> (Eric Knauel's message of "Tue, 09 Sep 2003 08:47:06 +0200")
On Tue, 09 Sep 2003, knauel@informatik.uni-tuebingen.de wrote:
> here is a little patch for spam-report.el that provides a function
> `spam-report-url-ping-wget' that calls wget to report a spam message
> to gmane. I found that convenient because the orginal
> `spam-report-url-ping' (now `spam-report-url-ping-plain') didn't
> obey the http proxy settings.
I like the patch, but wouldn't it make sense, as Reiner said, to use
a mm-url.el function as the alternative, instead of crafting our own
replacements for it?
Ted
next prev parent reply other threads:[~2003-09-09 18:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-09 6:47 Eric Knauel
2003-09-09 16:51 ` Reiner Steib
2003-09-09 18:13 ` Ted Zlatanov
2003-09-09 18:19 ` Ted Zlatanov
2003-09-09 19:50 ` Reiner Steib
2003-09-09 18:16 ` Ted Zlatanov [this message]
2003-09-10 6:52 ` Eric Knauel
2003-09-10 10: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=4noext3jzm.fsf@lockgroove.bwh.harvard.edu \
--to=tzz@lifelogs.com \
--cc=ding@gnus.org \
/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).