Re: Ham messages not being moved anymore

[Ted Zlatanov <tzz@lifelogs.com>]

On Wed, 30 Apr 2003, niklas.morberg@axis.com wrote:
> The first thing that got me was that messages are no longer
> marked as read just by viewing them. This is good and just
> something that I needed to learn.

I'm not sure what you mean, messages should get the read-mark when
they are viewed.  This is exactly what should happen, so they are
considered ham and moved out of the spam group.

> The second thing was that I had configured the parameter 
> 
>  (ham-marks
>   (gnus-read-mark))
> 
> for my spam group. When removing this configuration, read
> messages (explicitly marked as read by pressing `d' in the
> summary buffer) were moved properly.
> 
> With this configuration, read messages are not moved. Am I
> using the ham-marks parameter in the wrong way?

Not wrong, just not what you want.  The default ham marks:

   :variable-default '((".*" ((gnus-del-mark 
			       gnus-read-mark
			       gnus-killed-mark 
			       gnus-kill-file-mark
			       gnus-low-score-mark))))

should cover everyone (though I'm not sure about the kill-file and
low-score marks, I think they're better as ham marks than spam marks).

The mark definitions in gnus-sum.el say:

(defcustom gnus-del-mark ?r
  "*Mark used for del'd articles."
  :group 'gnus-summary-marks
  :type 'character)

(defcustom gnus-read-mark ?R
  "*Mark used for read articles."
  :group 'gnus-summary-marks
  :type 'character)

What you call "explicitly marking messages read" is considered a
delete operation internally in Gnus, thus the del-mark.  I think the
word "delete" was avoided in user interactions so users don't get the
impression they are expiring the article or removing it through the
backend (B Del).

Thanks
Ted