From: Ted Zlatanov <tzz@lifelogs.com>
Subject: Re: Gnus SPAM support, and email based reporting.
Date: Fri, 23 Apr 2004 12:17:45 -0400 [thread overview]
Message-ID: <4n7jw6r7me.fsf@lifelogs.com> (raw)
In-Reply-To: <87zn93xnoq.fsf@dod.no> (Steinar Bang's message of "Fri, 23 Apr 2004 07:34:13 +0200")
On Fri, 23 Apr 2004, sb@dod.no wrote:
>>>>>> Ted Zlatanov <tzz@lifelogs.com>:
>
>> On Thu, 22 Apr 2004, sb@dod.no wrote:
>
>>> Note that there are two different ways of reporting the spam:
>>> - as resends
>>> - MIME attachments
>
>> We'll just add a digest and attachment version of the reporter:
>
>> (defun spam-report-resend-attachment (&rest articles)
>> ...)
>> (defun spam-report-resend-digest (&rest articles)
>> ...)
>
> That would make it three different ways. By "resend" I meant what
> happens when you do `S D r'. It's what I need for one of my
> addresses.
The idea is that the spam exit processor will do it automatically
when you exit the group, so you don't need S D r or anything like
that - just to mark spam articles.
> The difference between resend attachment and resend digest is that
> with the latter, the message/rfc822 parts are wrapped inside a
> multipart/digest, and the first part should be skipped when
> unpacking. I don't know how significant this difference would be
> for the unpacking filter...?
Let's list the possibilities and we'll see if they should all be
separate spam exit processors or we can generalize to 2 or 3
processors and do the rest with group/topic parameters.
Ted
next prev parent reply other threads:[~2004-04-23 16:17 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
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 [this message]
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=4n7jw6r7me.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).