Bug 1488

Summary: Filter action mark_as_read failing with move to sub-folder
Product: Claws Mail (Maemo) Reporter: Walt Bilofsky <bilofsky>
Component: GeneralAssignee: users
Status: RESOLVED WORKSFORME    
Severity: normal    
Priority: P3    
Version: 3.2.0   
Hardware: Nokia n810   
OS: Linux   

Description Walt Bilofsky 2008-01-24 15:22:12 UTC 
The filter action

mark_as_read move "#mh/Mail/Walt's Email/Junk"

moves applicable messages to the indicated folder but does not mark them read.

A similar action without the move does mark as read.
Comment 1 Colin Leroy 2008-01-24 16:19:35 UTC 
It works correctly for me. Can you double-check your preceding rules to make sure it's not another one that moves the mail? 

If that doesn't help, enable filtering log in preferences and look at it...
Comment 2 Brian Morrison 2008-01-24 16:58:14 UTC 
Which way round are the commands?

Mark as read before moving should work, I'm not sure about the moving first. A previous mail client I used long ago terminated all rules after a move, so doing it first would result in the mark as read never being actioned.
Comment 3 Holger Berndt 2008-01-24 17:00:08 UTC 
(In reply to comment #2)
> Mark as read before moving should work, I'm not sure about the moving first. A
> previous mail client I used long ago terminated all rules after a move, so
> doing it first would result in the mark as read never being actioned.

Claws Mail does the same, so it should work the way the reporter posted it.
Comment 4 Walt Bilofsky 2008-01-24 18:02:50 UTC 
I edited my other filtering rule (which also had mark_as_read) and turned on the filtering log, and now they both work fine.  The most logical explanation is that I confused the two rules, and the one that was failing had mark_as_read after the move.  

(Personally I don't believe that, because I'm pretty sure both rules failed to mark_as_read, but I can't duplicate that any more.  I restored an earlier backup, but that failed to restore either the old filters or the old mailbox contents.)

Bottom line:  Since I can no longer duplicate this, I withdraw the report.

But it seems to me that if mark_as_read doesn't work after a move, either it should, or the filter construction code should always put it first.  I will submit that as a separate bug.