Does spam.el only use group parameters now?

Does spam.el only use group parameters now?

[Michael Shields]

It looks like spam.el, since the big customization change last week,
uses only group parameters to determine whether a message should be
processed on exit or not.  This is not convenient for me, since I have
dozens of mail groups; I want to invoke bogofilter whenever I exit
a mail group, but I don't want to set dozens of group parameters.

Is there a way around this?  This clumsily hacks around it:

    (defun spam-group-processor-bogofilter-p (group)
      (not (gnus-news-group-p group)))

but that's obviously not the right way to solve the problem.
-- 
Shields.

Re: Does spam.el only use group parameters now?

[Ted Zlatanov]

On Tue, 07 Jan 2003, shields@msrl.com wrote:
> It looks like spam.el, since the big customization change last week,
> uses only group parameters to determine whether a message should be
> processed on exit or not.  This is not convenient for me, since I
> have dozens of mail groups; I want to invoke bogofilter whenever I
> exit a mail group, but I don't want to set dozens of group
> parameters.
> 
> Is there a way around this?  This clumsily hacks around it:
> 
>     (defun spam-group-processor-bogofilter-p (group)
>       (not (gnus-news-group-p group)))
> 
> but that's obviously not the right way to solve the problem.

Correct, and the manual in CVS has been updated correspondingly.

The spam-process group parameter has a corresponding
gnus-spam-process-newsgroups variable you can customize; just put a
"nnml.*" regex in that variable to get global behavior for nnml
groups, or whatever's appropriate for you.

Also, if you use topics, you can customize the topic parameters, that
should work also if all your mail groups are under one topic.

spam-use-XYZ only relates to spam-split now, summary exit spam/ham
processing is always done with the spam-process group parameter.  This
is because the gnus-spam-process-newsgroups variable was, in my
opinion, sufficient and I didn't want to provide two ways of doing the
same thing.

If you think we should have a global variable corresponding to the old
spam-use-XYZ variable for summary exit processing, let me know.

Ted

Re: Does spam.el only use group parameters now?

[Michael Shields]

> The spam-process group parameter has a corresponding
> gnus-spam-process-newsgroups variable you can customize; just put a
> "nnml.*" regex in that variable to get global behavior for nnml
> groups, or whatever's appropriate for you.

After:

  (setq gnus-spam-process-newsgroups '("^nnimap:"))

I get

  Wrong type argument: listp, "^nnimap:"

  # bind (standard-output stack-trace-on-signal debug-on-signal stack-trace-on-error debug-on-error alist elem value name)
  gnus-parameter-spam-process("INBOX.politech")
  # bind (processor group)
  spam-group-processor-p("INBOX.politech" gnus-group-spam-exit-processor-bogofilter)
  # bind (group)
  spam-group-processor-bogofilter-p("INBOX.politech")
  spam-summary-prepare-exit()
  run-hooks(spam-summary-prepare-exit)
  apply(run-hooks spam-summary-prepare-exit)
  # (unwind-protect ...)
  # bind (buf funcs)
  gnus-run-hooks(gnus-summary-prepare-exit-hook)
  # bind (buf group-point mode gnus-group-is-exiting-p quit-config group temporary)
  #<compiled-function (&optional temporary) "...(388)" [gname gnus-article-buffer group quit-config buf buffer gnus-set-global-variables gnus-buffer-live-p mm-destroy-parts nil gnus-kill-save-kill-buffer gnus-async-halt-prefetch gnus-group-quit-config t gnus-score-adaptive gnus-score-save gnus-run-hooks gnus-summary-prepare-exit-hook get-buffer buffer-name kill-buffer gnus-cache-possibly-remove-articles gnus-cache-save-buffers gnus-async-prefetch-remove-group gnus-dup-enter-articles gnus-tree-close gnus-cache-write-active nnmail-purge-split-history string-match "^[^:]+:" 0 gnus-exit-group-hook gnus-summary-update-info gnus-close-group gnus-group-jump-to-group gnus-summary-exit-hook gnus-group-group-name gnus-group-next-unread-group 1 gnus-deaden-summary gnus-summary-clear-local-variables bury-buffer pop-to-buffer gnus-configure-windows force gnus-handle-ephemeral-exit gnus-summary-mode gnus-newsgroup-name mode group-point gnus-group-buffer gnus-article-mime-handles gnus-single-article-buffer gnus-original-article-buffer gnus-article-current gnus-use-cache gnus-newsgroup-variables gnus-summary-local-variables gnus-article-mime-handle-alist gnus-group-is-exiting-p major-mode gnus-newsgroup-adaptive gnus-use-scoring gnus-suppress-duplicates gnus-use-trees temporary gnus-kill-summary-on-exit gnus-select-method gnus-current-select-method] 5 ("/home/shields/share/xemacs/site-packages/lisp/gnus/gnus-sum.elc" . 177840) nil>()
  call-interactively(gnus-summary-exit)
  # (condition-case ... . error)
  # (catch top-level ...)
-- 
Shields.

Re: Does spam.el only use group parameters now?

[Ted Zlatanov]

On Tue, 07 Jan 2003, shields@msrl.com wrote:
>> The spam-process group parameter has a corresponding
>> gnus-spam-process-newsgroups variable you can customize; just put a
>> "nnml.*" regex in that variable to get global behavior for nnml
>> groups, or whatever's appropriate for you.
> 
> After:
> 
>   (setq gnus-spam-process-newsgroups '("^nnimap:"))
> 
> I get
> 
>   Wrong type argument: listp, "^nnimap:"

Sorry, I should have been more explicit.  Use customize-variable, it's
easier than trying to set it manually.  The variable is an alist of
regexes and their related spam or ham processors.

Ted