Bug 152160

Summary:	Mail filter does not mark messages as 'read'
Product:	[Fedora] Fedora	Reporter:	Sean Carolan <sean>
Component:	evolution	Assignee:	Matthew Barnes <mbarnes>
Status:	CLOSED INSUFFICIENT_DATA	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	3	CC:	ivazqueznet, mcepl, mcepl
Target Milestone:	---
Target Release:	---
Hardware:	i386
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2007-10-02 16:51:49 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Sean Carolan 2005-03-25 14:35:18 UTC

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.6) Gecko/20050323 Firefox/1.0.2 Fedora/1.0.2-1.3.1

Description of problem:
I have a mail filter with two actions.  The first is set to catch all email from a particular mailing list and move it into a folder.  The second action is supposed to mark these emails as 'read', but they are still showing as 'unread'.

Version-Release number of selected component (if applicable):
evolution-2.0.4-2

How reproducible:
Always

Steps to Reproduce:
1.  Create a filter based on mailing list
2.  Add action to mark email as 'read'
3.  Wait for email to arrive  

Actual Results:  Mail not marked as 'read'

Expected Results:  Mail should be marked as read

Additional info:

Comment 1 Ignacio Vazquez-Abrams 2005-04-30 21:03:11 UTC

Does it work if you reverse the actions, i.e., mark it read first, then move it?

Comment 3 Matthew Barnes 2007-01-01 12:45:02 UTC

Is this problem still present in Fedora Core 6?

Comment 4 Matěj Cepl 2007-08-31 15:21:50 UTC

The distribution against which this bug was reported is no longer supported,
could you please reproduce this with the updated version of the currently
supported distribution (Fedora Core 6, or Fedora 7, or Rawhide)? If this issue
turns out to still be reproducible, please let us know in this bug report.  If
after a month's time we have not heard back from you, we will have to close this
bug as INSUFFICIENT_DATA.

Setting status to NEEDINFO, and awaiting information from the reporter.

Thanks in advance.

Comment 5 Matthew Barnes 2007-10-02 16:51:49 UTC

Closing as INSUFFICIENT_DATA.