GNOME Bugzilla – Bug 343657
'create rule from message' created Outgoing filter, not Incoming filter
Last modified: 2012-08-06 19:15:25 UTC
I saw a message in my Inbox which I would rather have filtered into a different folder. I right-clicked the message in the folder listing, selected "Create Rule From Message" => "Filter On Sender" and specified the folder I wanted the mail to be filed in. I then tried running the filters using control-y, but the mail didn't move. I opened up the "Edit" => "Message Filters" dialog, and didn't see the filter I had just created. Further exploration revealed that the filter was in the "Outgoing" section, rather than the expected "Incoming" section. I was making a filter based on "Sender" after all. Filtering outgoing mail based on sender is likely to be a less common requirement than incoming mail, since all my outgoing mail is sent by the same person (ie. me). I think the root cause of this is that I file my sent mails in Inbox along with received mails, so I can see conversations as threads, and file both sent and received messages with a single drag. To reproduce, set the 'sent messages folder' to be Inbox: Edit => Preferences => <account> => Edit => Defaults => Sent Messages Folder => Inbox Then try creating a filter from a message in Inbox. It gets set to be an outgoing filter. I would suggest that incoming filtering is more common that outgoing filtering, and so if the sent messages folder is 'inbox' then default new filters to be incoming ones, and give the user a choice at creation time.
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of bug 415371 ***
(In reply to comment #1) > Thanks for the bug report. This particular bug has already been reported into > our bug tracking system, but please feel free to report any further bugs you > find. > > *** This bug has been marked as a duplicate of bug 415371 *** What do you mean, "has already been reported"? I reported this over 6 years ago. You wait 6 years then tell me it's a duplicate of a 5 year old bug?
Surely you can tell the comment is just boilerplate text. It's irrelevant who reported it first.