GNOME Bugzilla – Bug 211587
Filters/Inbox doesn't work in evolution > 0.13
Last modified: 2002-04-11 05:39:29 UTC
Package: Evolution Priority: Normal Version: evolution-0.14.99-snap.ximian.200109300808 Synopsis: Filters/Inbox doesn't work in evolution > 0.13 Bugzilla-Product: Evolution Bugzilla-Component: Mailer Description: When I doing an upgrade from 0.13 to 0.14 the filters I'd setup for incomming email stopped working. And all email stayed in . (or #.) which is the local Maildir folder that email is delivered into. In 0.13 email was automatically moved from this folder into Inbox (or another folder depending on the filters). Selecting the messages in #. and then doing apply filters also doesn't move the message. However vfolders do appear to work (although you can't seem to delete a vfolder). Automatic collection of email also doesn't seem to work all the time (although I have seen it work). The filters file I'm using is available at http://sophia.and.org/ximian-bug-filters.xml Unknown reporter: james@and.org, changed to bugbuddy-import@ximian.com.
james: still seeing this problem in 0.16.99?
I don't think so, here is what I see with 0.16.99+cvs.2001.10.18.15.19. Auto. collect of email still doesn't work (doesn't even do it once on startup). This is with a ~/Maildir/ qmail style mailbox. As for filters, sort of. If I select "." and click send/recieve _nothing_ happens. But if I then click on Inbox (after having done above) then as soon as I select Inbox all email will be processed as though it's gone into "." and selected and had filters applied to it. Also worth noting is that if I select Inbox, click send/recieve then nothing happens. I have to then click on "." and then click off it again (Ie. click Inbox) and on the selection change from "." to Inbox incomming mail will be processed. I'm also confused about intended behaviour, in 0.13 all email not matched by a filter ended up in Inbox, from then to now it all ends up in "." are you supposed to have a match all filter which moves stuff out of "." ? HTH.
I'm not sure what you mean. Where exactly is your mail delivered? Is it delivered directly to the maildir tree, or somewhere else? Where is 'Inbox'? Is that a sufolder of the maildir tree? The way the maildir is supposed tow ork is you just dont have to move it around, you just use it 'where it lives'. I've setup '.' as the 'incoming inbox' as used by the 'filter new messages in the inbox inbox'. If you want to have it so messages dont work from inside the maildir area (and there's no reason to do this, or not to do this, its upto you), then you can setup a default rule at the bottom of all your other rules to move the messages to your other inbox, as you correctly supposed. Does that help?
> Where exactly is your mail delivered? It is delivered into ~/Maildir/ this is then mapped to "." by evolution with the config. of having one mail source of type maildir with the ~/Maildir/ dir. as the directory. > Where is 'Inbox'? Inbox was created by evolution in 0.13, it's on disk location is ~/evolution/local/Inbox all other mail folders are located under ~/evolution/local/Inbox/subfolders/. > The way the maildir is supposed tow ork is you just dont have to > move > it around, you just use it 'where it lives'. I've setup '.' as the > 'incoming inbox' as used by the 'filter new messages in the inbox > inbox'. > > If you want to have it so messages dont work from inside the maildir > area (and there's no reason to do this, or not to do this, its upto > you), then you can setup a default rule at the bottom of all your > other rules to move the messages to your other inbox, as you > correctly supposed. Ok. So it's supposed to keep unfiltered email in ".". Fair enough. How does this work with multiple mail sources, do they all have their seperate "." folders now ? Having it be in Inbox, instead of ".", was nicer visually IMO. But I can happily setup a rule to move them over to Inbox (just fix the other stuff :).
One more point is that if you do a manual apply filters, then when the messages move from "." to Inbox they are no longer present in ".". However on automatic filters on incomming mail they are "deleted" in the "." folder (have strike through but you have to expunge for them to be gone). Also there is no obvious way to make a catch all filter (I ended up doing a any of and two mutually exclusive rules). Also it'd be nice for a way to say this rule must stay on the bottom when I create new rules (as atm. new rules will go under the catch all rule and hence never be run).
Maildir ISNT a mail source. its a mail storage. e.g. like imap. Most people that use imap dont download all their imap mail to a local fodler ot read it. POP does this because pop is a very simple and not very flexible protocol. Catch all could be somethign like 'subject contains ''' (i.e. an empty string). Manually applying filters just does a sync automatically, i dont think we're doing to do things like a sync + expunge on any automatic process for various reasons. You could also do hide deleted messages, etc. Yeah i know '.' is ugly, but its better it works, making it 'Inbox' was a lot of messy work I didn't want to have to do. Anyway, can this be considered fixed? You should be able to do everything you used to do, it just works differently than you had it before. I would still btw recommend using '.' as your inbox, maildir has some nice properties and if your mta already uses it, its nice for your mua to use it too.
> Maildir ISNT a mail source. its a mail storage. e.g. like imap. Well I've never used it that way, and the "mail account" settings in evolution imply otherwise, but I can see the argument. > Catch all could be somethign like 'subject contains ''' (i.e. an > empty string). Well I wasn't sure if that would match everything or nothing, I did... <rule grouping="any" source="incoming"> <title>Rest to Inbox</title> <partset> <part name="source"> <value name="srcmatch-type" type="option" value="is"/> <value name="source" type="uri"> <uri>maildir:/home/lynn/Maildir/;filter</uri> </value> </part> <part name="source"> <value name="srcmatch-type" type="option" value="is-not"/> <value name="source" type="uri"> <uri>maildir:/home/lynn/Maildir/;filter</uri> </value> </part> </partset> <actionset> <part name="move-to-folder"> <value name="folder" type="folder"> <folder name="Inbox" uri="file:///home/lynn/evolution/local/Inbox"/> </value> </part> </actionset> </rule> ...which seemed to work, but I now appear to be getting the mail in _both_ the catch all folder and a specific folder for anything matching a previous rule *sigh*. > Manually applying filters just does a sync automatically, i dont > think we're doing to do things like a sync + expunge on any > automatic process for various reasons. Hmmm, that's kinda annoying. Is this just a hard problem (Ie. locking complexity) or is it a trade off for some reason ? Could you have an folder option to say expunge on startup/shutdown ? I'm mainly worried that either the folder will become very large and slow down retrieving mail or that my wife will get annoying doing an expunge every now and again and beat me :). > Yeah i know '.' is ugly, but its better it works, making it > 'Inbox' was a lot of messy work I didn't want to have to do. Ok, I don't mind it going there first. Just so long as it's easy to get it out again. > Anyway, can this be considered fixed? You should be able to do > everything you used to do, it just works differently than you had it > before. No, things that still don't work. 1. Automatic fetch of email doesn't work at all AFAICS. 2. Manual fetch only works if after doing it you select and then deselect the "." folder. I want to have Inbox selected and to just press send/recieve and it do everything (and it should do it automatically too, if that option is on -- see 1.). 3. Catch all filter seems to also match email already matched by a previous filter, presumably this needs to be an option in the filter setup. > I would still btw recommend using '.' as your inbox, maildir has > some nice properties and if your mta already uses it, its nice for > your mua to use it too. I've converted all the evoltion email folders to Maildir _type_, I just don't want the mail in an out of the way folder called ".". Having new mail be in a different place than your "misc" folder also has some nice properties too.
Ok slight addition to the above. If you exit from evolution and get new mail and then run evolution, evolution will notice that it is there without you having to do anything. HOWEVER it won't apply filters to it, you have to do that manually (or run evolution all the time and do the above dance).
The latter case is expected. Its an IMAP limitation.
So this would be the special version of IMAP that's spelt everywhere as "Maildir" in my bug reports, and even the amazing title of "local Maildir folder" in the first part of the bug report. So again, this is still the same in 1.0.x. With a _LOCAL_ Maildir as the delivery point, if you have filters then mail doesn't get sent where it should unless you switch to the "." folder and back again. And the mail is still in the Maildir folder and so that needs to be expunged. This is exactly as I said on my "2001-10-22 17:22" comment.
this is the way it's supposed to work.