Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
Subject: Re: How many people mark spam in gmane groups?
Date: Sat, 05 Apr 2003 08:20:16 -0500	[thread overview]
Message-ID: <m33ckx3wtr.fsf@heechee.beld.net> (raw)
In-Reply-To: <v91y0kx2jn.fsf@marauder.physik.uni-ulm.de> (Reiner Steib's message of "Wed, 02 Apr 2003 18:54:52 +0200")

On Wed, 02 Apr 2003, 4.uce.03.r.s@nurfuerspam.de wrote:
> On Wed, Apr 02 2003, Ted Stern wrote:
> 
>> At the moment, this entails me exposing the X-Report-Spam header
>> using "C-u g" in the summary buffer, then using browse-url-at-point
>> to send the link to my browser.
>> Is there some way to automate this a bit more?  
> 
> Sure, it's Gnus. :-)
> 
[ code omitted ]
> 
>> It would be nice if there were a single keystroke (say "$ R") to
>> report spam.
> 
> I didn't use the above code very often, so I'm not sure if it works
> reliable.
> 
> Should we add something like this to Gnus?  Opinions?

Although spam.el might be too heavyweight for something like this, a
spam/ham summary exit processor ("reporter"?) that can use the
X-Report-Spam header would work.  Then the spam-marked messages could
be batch-processed as described above, then copied (not moved!) if
spam-process-destination is set for the newsgroup.

This would require some changes to spam.el, since it has been used
only with mail groups, so it's not a trivial addition.

Ted




  parent reply	other threads:[~2003-04-05 13:20 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-02 15:59 Ted Stern
2003-04-02 16:54 ` Reiner Steib
2003-04-02 20:58   ` Jon Ericson
2003-04-05 13:20   ` Ted Zlatanov [this message]
2003-04-05 23:16     ` Reiner Steib
2003-04-07 20:49       ` Ted Zlatanov
2003-04-12 15:50         ` Andreas Fuchs
2003-04-12 20:58           ` Lars Magne Ingebrigtsen
2003-04-13 10:56             ` Andreas Fuchs
2003-04-13 13:31               ` Lars Magne Ingebrigtsen
2003-04-14 19:33               ` Ted Zlatanov
2003-04-14 21:03                 ` Andreas Fuchs
2003-04-14 21:05                 ` Reiner Steib
2003-04-14 23:32                   ` Ted Zlatanov
2003-04-15 14:24                     ` Reiner Steib
2003-04-15  5:34                   ` Steinar Bang
2003-04-15 14:23                     ` Reiner Steib
2003-04-15 19:33                     ` Ted Zlatanov
2003-04-15 21:42                       ` Andreas Fuchs
2003-04-15 22:31                         ` Lars Magne Ingebrigtsen
2003-04-16  6:02                           ` Andreas Fuchs
2003-04-16 16:33         ` Ted Zlatanov
2003-04-26  1:40           ` Jon Ericson
2003-04-29 17:19             ` Ted Zlatanov
2003-04-29 17:48               ` Jon Ericson
2003-04-29 18:04                 ` Ted Zlatanov
2003-04-29 19:48                   ` Jon Ericson
2003-04-30 18:28                     ` Ted Zlatanov
2003-04-30 21:37                       ` Jon Ericson
2003-05-01 17:34                         ` Ted Zlatanov
2003-04-26  2:49           ` Jon Ericson
2003-04-27  3:41             ` Lars Magne Ingebrigtsen
2003-04-28 18:36               ` Jon Ericson
2003-04-29 17:12                 ` Ted Zlatanov
2003-04-30 18:37                   ` Jon Ericson
2003-04-02 19:32 ` Raja R Harinath
2003-04-13  1:31   ` Daniel Néri

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=m33ckx3wtr.fsf@heechee.beld.net \
    --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).