GNOME Bugzilla – Bug 601526
Message filters that 'Run Program' don't
Last modified: 2012-02-06 13:41:22 UTC
I've got a filter set up so that whenever an email with a specific subject line is received, a specific program should be run and the mail should be moved to a folder. This worked well in the 2.26.x series. I am now running 2.28.1 and, while the mail gets moved to the folder, the program no longer gets run. I've tried running the program from the command line, and it runs fine.
Check the order - app has to run before mail gets moved.
It is listed first. It also doesn't work if the program is the only thing listed to be done. I've now replicated this problem in another machine (one is Ubuntu Karmic, one is Gentoo).
It seems like the bug is intermittent. It happens most of the time, but sometimes the program does run.
alito: If you have time, could you please check again whether this issue still happens in Evolution 3.2.2 or 3.0.3 and update this report by adding a comment and changing the "Version" field and provide information about your distribution? Maybe you could find out if either your script sometimes fails, or if it is Evolution that fails to call the script, by setting to keys in GNOME's "gconf" registry. The relevant gconf keys are: /apps/evolution/mail/filters/log = true /apps/evolution/mail/filters/logfile = "/path/to/your/logfile" Unfortunately there is no interface in Evolution to access this functionality directly. You have to edit the Gconf database, preferably by using one of the specialized configuration editors such as "gconf-editor". Make sure to change "/path/to/your/logfile" to a real path (like your user's home directory), it is just an example path. Unfortunately the log is written buffered and only written to the file when, for example, Evolution ends. Monitoring the file with something like "tail -f /path/to/your/logfile" will NOT show any output. The other option would be to provide your script, but keep in mind that this bugtracker is totally public.
Hi, Sorry, I defected from evolution a couple of years ago now. The problem wasn't the script though, since the details of the script weren't important (eg I remember substituting the contents of the script with a single 'touch ~/amarkerfile.txt' line and that wouldn't work either). Thanks for taking a look though.
Hmm, I see. That makes it hard to reproduce, so closing as INCOMPLETE for the time being, but thanks for the quick answer and sorry that this report was not handled in time when you reported it.