Gnus development mailing list
 help / color / mirror / Atom feed
From: "Jochen Küpper" <jochen-+It19tn3Rl9sbm7dSapR3bNAH6kLmebB@public.gmane.org>
Subject: Re: Gnus SPAM support, and email based reporting.
Date: Thu, 22 Apr 2004 18:23:16 +0200	[thread overview]
Message-ID: <ovy8oooubv.fsf@mp09.rz-berlin.mpg.de> (raw)
In-Reply-To: <87fzawgyxq.fsf-1rLz5CwDoL8@public.gmane.org> (Steinar Bang's message of "Thu, 22 Apr 2004 11:10:57 +0200")

On Thu, 22 Apr 2004 11:10:57 +0200 Steinar Bang wrote:

>>>>>> Ted Zlatanov <tzz-mIZUurteI1BWk0Htik3J/w@public.gmane.org>:

>> We can add something like Jochen Kupper's code to spam-report.el if
>> everyone is OK with it.

Should probably be written a little nicer...

Steinar> Note that there are two different ways of reporting the spam: 
Steinar> - as resends 
Steinar> - MIME attachments

Agreed.

Steinar> Jochen's code seems to support the MIME attachment approach.  

Yep, that's what we need here.

Steinar> There's also some use of digests in there that I don't quite
Steinar> understand? 

Me neither;) The way I use it is that I process mark all
ill-classified articles and then send them with a single command
(jk/spam-report, bound to "$").

Steinar> Doesn't the digesting in Gnus strip headers from the digested
Steinar> messages?

I have the following (should probably be set temporarily inside the
function then).
,----[ C-h v gnus-uu-digest-headers RET ]
| gnus-uu-digest-headers's value is nil
| 
| Documentation:
| *List of regexps to match headers included in digested messages.
| The headers will be included in the sequence they are matched.  If nil
| include all headers.
| 
| You can customize this variable.
| 
| Defined in `gnus-uu'.
`----

Steinar> In any case, I would like it to be possible to set the reporting
Steinar> method (ie. resend or MIME attachment), as well as the reporting
Steinar> address, in the Group parameters

Seems totally reasonable... 


I'd like to also move the messages to certain Groups when reported,
maybe I get to do that sometime soon.

Greetings,
Jochen
-- 
Einigkeit und Recht und Freiheit                http://www.Jochen-Kuepper.de
    Liberté, Égalité, Fraternité                GnuPG key: CC1B0B4D
        (Part 3 you find in my messages before fall 2003.)




  parent reply	other threads:[~2004-04-22 16:23 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-17 12:40 Daniel Pittman
2004-04-17 15:20 ` Derrell.Lipman
2004-04-21 15:44   ` Ted Zlatanov
2004-04-22  9:10     ` Steinar Bang
     [not found]       ` <87fzawgyxq.fsf-1rLz5CwDoL8@public.gmane.org>
2004-04-22 16:23         ` Jochen Küpper [this message]
2004-04-22 20:11           ` Ted Zlatanov
     [not found]             ` <4n1xmfept2.fsf-mIZUurteI1BWk0Htik3J/w@public.gmane.org>
2004-04-22 21:32               ` Jochen Küpper
2004-04-23 16:15                 ` Ted Zlatanov
2004-04-22 18:35       ` Ted Zlatanov
2004-04-23  5:34         ` Steinar Bang
2004-04-23  7:45           ` Daniel Pittman
2004-04-23 16:17           ` Ted Zlatanov
2004-05-15 13:27     ` Daniel Pittman
2004-05-18 20:08       ` Ted Zlatanov
2004-05-24 11:09         ` Daniel Pittman
2004-05-24 11:39           ` Kai Grossjohann
2004-05-24 14:07             ` Daniel Pittman
2004-05-24 14:12               ` Kai Grossjohann
2004-05-26 19:00                 ` Michael Schierl
2004-05-24 13:44           ` Ted Zlatanov
2004-05-24 14:18             ` Daniel Pittman
2004-05-24 17:40               ` Ted Zlatanov
2004-05-24 18:07                 ` Daniel Pittman
2004-05-24 18:50                   ` Ted Zlatanov
2004-05-24 18:52             ` spam.el processor code refactored (was: Gnus SPAM support, and email based reporting.) Ted Zlatanov
     [not found] ` <87isfy7p6a.fsf-kiwxAyAbAnkGAYDEi5AF0l6hYfS7NtTn@public.gmane.org>
2004-04-18 22:05   ` Gnus SPAM support, and email based reporting Jochen Küpper

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=ovy8oooubv.fsf@mp09.rz-berlin.mpg.de \
    --to=jochen-+it19tn3rl9sbm7dsapr3bnah6klmebb@public.gmane.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).