GNOME Bugzilla – Bug 579315
Identify filter names in filtering errors
Last modified: 2012-12-10 13:51:49 UTC
evolution-2.24.5-1.fc10.x86_64 evolution-data-server-2.24.5-5.fc10.x86_64 Exact same summary as bug 447977, because that's what happens. It's probably not a duplicate of bug 444503 because I don't use Exchange. Possible reproducer: 1) Set up a local delivery account 2) Set up an IMAP account, don't apply filter to the new messages in inbox 3) Set up a filter that moves a mail from the IMAP account to a local folder 4) Applying the filter works 5) Delete (I don't think disable actually reproduces the problem) the local delivery account 6) Try to apply the filter setup in 3 " Error while Filtering Selected Messages. No provider available for protocol 'email' " 7) Go to Edit->Message filters, and edit the filter created in 3), there's no target folder selected
http://www.go-evolution.org/FAQ#Why_do_I_get_the_message_.22No_provider_available_for_protocol_email..22.3F - does it help ?
It certainly would, as mentioned in 7), but I don't understand why the filter would get associated with the local delivery account when it's not the one providing the storage for local mails. What's mentioned in the FAQ is a work-around, not a fix.
hadess: Is this still an issue, or can this be closed as OBSOLETE? Asking as I haven't seen any new bug reports about that error for a while now...
Unless positive steps have been taken to fix the problem, I'm certain the problem is still there. The reproducer steps in comment 0 should help.
Also see bug 525932 about the error message itself.
This is still reproducible, with the given steps, but the message is better descriptive, due to fix from bug #525932. Bastien, are you fine with this kind of solution?
The message is sub-par for me: > One reason can be that folder location set in one or more filters is invalid. I'm pretty sure that the computer could check that, and even tell me which folder is invalid. > Please check your filters in Edit->Message Filters. Does it link straigth to the filter that's broken?
Created attachment 231143 [details] [review] eds patch for evolution-data-server; (In reply to comment #7) > The message is sub-par for me: > > One reason can be that folder location set in one or more filters is invalid. > I'm pretty sure that the computer could check that, and even tell me which > folder is invalid. The current error message looks like this (it's with this patch included, see below): Error while Filtering Selected Messages. Failed to filter selected messages. One reason can be that folder location set in one or more filters is invalid. Please check your filters in Edit->Message Filters. Original error was: Execution of filter 'XX broken rule XX' failed: Invalid folder URI 'folder://1355145511.7145.14%40host/INBOX' > > Please check your filters in Edit->Message Filters. > > Does it link straigth to the filter that's broken? It unfortunately doesn't, and even I agree with your proposal of "Edit Filter" button, then it cannot be done currently, due to design limitations. The thing is that even if I pass a rule name to the caller, then it cannot process it into an "Edit Filter" button, because it doesn't have access to this part of evolution. There is some ongoing effort to move certain parts of mailer into evolution-data-server, thus processes will be able to access mail through DBus. This filtering part is also going to be part of this code movement, thus the only outcome of the filter operation is a GError structure. I'd rather avoid "encoding" filter name into a GError message, especially because the error will be received by any application. Of course, sadly, the information about Edit->Message Filters may not be accurate there as well, but as long as we are currently the only user of it, then I guess it's fine. Maybe the API/design will change during the movement too, thus the whole this will be possible, though probably not. Finally, this patch prefixes original error with a filter name, which is the most I can do right now.
Created attachment 231144 [details] [review] evo patch for evolution; Hrm, I overlooked the outgoing filters, where the same error can happen, thus I added the descriptive message there as well.
Created commit 807d32c in eds master (3.7.3+) Created commit c5eb6af in evo master (3.7.3+)