[BUG?]: Spam issue

[BUG?]: Spam issue

[Xavier Maillard]

Hello,

When using `gnus-parameters' this way:

,----
|            '((".*"
|               (total-expire . t)
| ;;              (expiry-wait . immediate)
| ;;              (expiry-target . delete)
|               (display . default)
|               (spam-contents gnus-group-spam-classification-ham)
|               (spam-process ((ham spam-use-bogofilter))))
`----

and setting my classification with:

,----
| (setq gnus-spam-newsgroup-contents
|       '(("INBOX.mail.spam" gnus-group-spam-classification-spam)))
`----

makes my Gnus still thinks that my spam group is not:

,----
| ELISP> (gnus-parameter-spam-contents "INBOX.mail.spam")
| (gnus-group-spam-classification-ham)
| 
| ELISP> 
`----

Is this the expected behavior ?

Regards.
-- 
GNUSFR.ORG                       http://gnusfr.org/
EMACSFR.ORG                      http://emacsfr.org/
Xavier Maillard                  Tel: +33 6 68 04 64 37

Re: [BUG?]: Spam issue

[Ted Zlatanov]

On Sat, 12 Feb 2005, zedek@gnu-rox.org wrote:

> When using `gnus-parameters' this way:
> 
> ,----
>|            '((".*"
>|               (total-expire . t)
>| ;;              (expiry-wait . immediate)
>| ;;              (expiry-target . delete)
>|               (display . default)
>|               (spam-contents gnus-group-spam-classification-ham)
>|               (spam-process ((ham spam-use-bogofilter))))
> `----
> 
> and setting my classification with:
> 
> ,----
>| (setq gnus-spam-newsgroup-contents
>|       '(("INBOX.mail.spam" gnus-group-spam-classification-spam)))
> `----
> 
> makes my Gnus still thinks that my spam group is not:
> 
> ,----
>| ELISP> (gnus-parameter-spam-contents "INBOX.mail.spam")
>| (gnus-group-spam-classification-ham)
>| 
>| ELISP> 
> `----
> 
> Is this the expected behavior ?

I don't think the behavior is explicitly defined.  There are multiple
ways to specify a setting in Gnus and you just found out the hard way
why it's a bad idea to do that :)

Ted

Re: [BUG?]: Spam issue

[Ted Zlatanov]

On 14 Feb 2005, tzz@lifelogs.com wrote:

> I don't think the behavior is explicitly defined.  There are
> multiple ways to specify a setting in Gnus and you just found out
> the hard way why it's a bad idea to do that :)

I should clarify here, I didn't mean it's a bad idea for you, the
user, to specify a setting in multiple ways.  It's bad that the
developers gave you a way to do it.  There are three ways to specify
group settings in Gnus that I know of:

1) gnus-parameters
2) group/topic parameters
3) global variables, e.g. gnus-spam-newsgroup-contents

plus there may be others.  I think Something Should Be Done (tm).

Either move everyone to gnus-parameters and group/topic parameters, or
provide a way to synchronize gnus-parameters with the global
variables.  At least, there should be a warning if you customize
overlapping things.

Ted