message filter does not set label

Bug #252503 reported by grouch
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Evolution
Expired
Medium
evolution (Ubuntu)
Invalid
Low
Ubuntu Desktop Bugs

Bug Description

Binary package hint: evolution

I'm using Evolution 2.22.3.1 on Ubuntu 8.04

I have several pop3 accounts and set up message filters to, among other things, automatically set labels on incoming messages. It doesn't work. Other filter action are taken (set status, move to folder, play sound etc.) but the message label remains unset.

See also thus thread on ubuntuforums:
http://ubuntuforums.org/showthread.php?t=785437

Looks like someone else has the same problem with IMAP.

grouch (grouch)
description: updated
grouch (grouch)
description: updated
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for your bug report. The issue seems similar to http://bugzilla.gnome.org/show_bug.cgi?id=537904

Changed in evolution:
assignee: nobody → desktop-bugs
importance: Undecided → Low
status: New → Triaged
Revision history for this message
Sebastien Bacher (seb128) wrote :

do you set the label before or after moving?

Revision history for this message
grouch (grouch) wrote :

I was setting label after moving when I had this problem. I have now
changed the order of the filter actions such that the label is set
before moving. Now everything seems to work fine.

Thank you so much for asking me this question!

Revision history for this message
Sebastien Bacher (seb128) wrote :

I've let a comment on the upstream bug to tell them that the behaviour was confusing for users

Changed in evolution:
status: Unknown → New
Revision history for this message
NoOp (glgxg) wrote :

This same problem occurs even without moving messages. I have a filter set up for a gmane newsgroup:
gmane.comp.openoffice.questions
With a filter set to filter on a 'Delivered-To' header which contains 'moderator'. The action is to:

Assign Color: Red
Set Status: Important

When I fetch new messages for the newsgroup I see messages that match the filter criteria. However, the filters are not applied unless I first select the individual message, and then use Message|Apply Filters or Ctrl-Y. Only then does the filter work.

I have even tried selecting all of the message headers, the bottom status will show 'Filtering selected messages', but the filter is not applied - and is only applied if I select an individual message as above.

Evolution 2.22.3.1
Hardy 8.04 2.6.24-23-generic #1 SMP Thu Feb 5 15:00:25 UTC 2009 i686 GNU/Linux
Fully updated.

Revision history for this message
Martin Mai (mrkanister-deactivatedaccount-deactivatedaccount) wrote :

Upstream bug has been marked as duplicate of bug https://bugzilla.gnome.org/show_bug.cgi?id=573120

Changed in evolution:
status: New → Unknown
Changed in evolution:
status: Unknown → New
Changed in evolution:
status: New → Invalid
Revision history for this message
Omer Akram (om26er) wrote :

is this still an issue?

Changed in evolution (Ubuntu):
status: Triaged → Incomplete
Revision history for this message
NoOp (glgxg) wrote : Re: [Bug 252503] Re: message filter does not set label

On 06/09/2010 10:36 AM, Omer Akram wrote:
> is this still an issue?
>
> ** Changed in: evolution (Ubuntu)
> Status: Triaged => Incomplete
>

I'll need to restore the Evolution settings/filter to test as I stopped
using Evolution sometime back.

Revision history for this message
NoOp (glgxg) wrote :

On 06/09/2010 04:16 PM, NoOp wrote:
> On 06/09/2010 10:36 AM, Omer Akram wrote:
>> is this still an issue?
>>
>> ** Changed in: evolution (Ubuntu)
>> Status: Triaged => Incomplete
>>
>
> I'll need to restore the Evolution settings/filter to test as I stopped
> using Evolution sometime back.
>

Still not working on Evolution 2.28.3 - lucid 2.6.32-22-generic.
Move filters work, label not applied at all now.

If I right-click on the message subject and select 'Label' I can see
that the proper label is checked/ticked (in this case 'Important - red'
but the color is not applied unless I apply to the individual msg per my
comment #5.

Revision history for this message
Omer Akram (om26er) wrote :

Can you please provide a few precise steps so that I could try to reproduce this bug with evolution 2.30 and if its there I could try to re-open the upstream bug. Thanks

Changed in evolution:
importance: Unknown → Medium
status: Invalid → Expired
Revision history for this message
Jörg Frings-Fürst (jff-de) wrote :

bug from 2008 - version not longer supported
change status to invalid

Changed in evolution (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.