Gnus development mailing list
 help / color / mirror / Atom feed
From: Steinar Bang <sb@dod.no>
Subject: Re: Reporting spamming/protecting against spamming on USENET
Date: Sun, 06 Mar 2005 18:09:28 +0100	[thread overview]
Message-ID: <87acpgzoon.fsf@dod.no> (raw)
In-Reply-To: <87r7l5rybp.fsf@dod.no>

>>>>> Steinar Bang <sb@dod.no>:

>>>>> "Ted Zlatanov" <tzz@lifelogs.com>:
>> On Tue, 14 Dec 2004, sb@dod.no wrote:
>>> The manual has this from your sample file:
>>> ;; all NNTP groups
>>> ;; autodetect spam with the blacklist and ham with the BBDB
[snip!]
>>> But I don't understand how this releates to USENET or the NNTP
>>> backend...?

>> It works in any Gnus group, and acts only on unseen articles when
>> you enter the group.  It's intended for read-only backends where
>> you don't have splitting, but nothing prevents its use in any other
>> backends.

> What I meant to say was that I didn't understand what exactly it was
> in the example, that said that these settings applied to NNTP groups.

> Or are these settings that are supposed to be added to a group's
> parameters? 

They are.

I missed this bit from the example:
     ;; my parameters, set with `G p'

It would be nice if these parameters could be set on the server.
Either from the server buffer, or from the .gnus.el file.




  reply	other threads:[~2005-03-06 17:09 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-14 21:40 Steinar Bang
2004-12-14 22:26 ` Ted Zlatanov
2004-12-31  9:37   ` Steinar Bang
2005-01-01 14:58   ` Steinar Bang
2005-03-06 17:09     ` Steinar Bang [this message]
2005-03-06 17:58       ` Reiner Steib
2005-04-10 19:16       ` Can't mark spam in NNTP group (Was: Reporting spamming/protecting against spamming on USENET) Steinar Bang
2005-04-11  7:33         ` Can't mark spam in NNTP group Steinar Bang
2005-04-12 17:06           ` Ted Zlatanov
2005-04-17 19:39             ` Steinar Bang

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=87acpgzoon.fsf@dod.no \
    --to=sb@dod.no \
    /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).