GNOME Bugzilla – Bug 354797
Cannot add program switches/parameters for "Pipe to" or "Run" filter
Last modified: 2021-05-19 12:13:24 UTC
Please describe the problem: While trying to add spam filtering rules using "Pipe to Program" or "Run Program", the file search dialog box allows a program to be selected but does not offer the ability to append any additional switches to be used with the selected program. Steps to reproduce: Attempt to create any message filter rule that uses the "Pipe to Program" or "Run Program" and append any additional switches to the selected program cannot be done via the evolution gui. The only way to add switches to be used with the selected program is to manually edit the ~/.evolution/mail/filters.xml file and add them to the xml code. Actual results: After selecting the program to be piped to or run, no additional editing to the dialog box can be made, nor does evolution display the path/program name. Expected results: After selecting the program, a dialog window should be displayed with the path and name of the program selected, with the ability to click on the dialog box and manually type in additional information such as program switches. Does this happen every time? Yes Other information: The only way to add switches to be used with a selected program is to manually edit the ~/.evolution/mail/filters.xml file and add them into the xml code.
...which command do you want to run? :-)
Created attachment 72550 [details] Snapshot of Filter Edit Rule window Note the highlighted dialog tabs cannot be seen properly.
I'm trying to implement spam filters using bogofilter and spamassassin in a howto that I found here http://ubuntuforums.org/showthread.php?t=99603 Unfortunately it's not possible to add the -u and -s options to the filters using bogofilter and -e to the filter using spamassassin.
Moving it to mailer.
Since your parameters are all constant, Write a simple script that will get some arguments and call the individual bogofilter and spamassasin scripts with required arguments. And set this script to be executed in the filter. This should solve your problem.
WONTFIX as per last comment.
REOPENing. Confiming. This is a regression. This used to be an option, and a lot of tipps and howtos use it.
A few points, as just discussed on IRC: 1.- A user migrating from 2.6 to 2.8 will be confused after he/she finds out that in place of the text entry where there previously was a custom command with arguments he/she had entered there is now a "browse" button instead, *with no indication whatsoever of which command is being called and how*. As a developer said on the #evolution channel, the backend has not changed, only the UI, so there can be no data loss. But not many people will know that they can check ~/.evolution/mail/filters.xml to see if anything has changed, as this is not documented anywhere AFAIK. The average user will most probably have created a filter using the "Pipe to Program" option following a howto or tip on the net, as guenther pointed out. He will now see that: a) he can no longer follow that HOWTO, or b) having followed a howto before 2.8 he will see that the command line he entered is not there anymore and probably think that this is no longer working. See http://ubuntuforums.org/showpost.php?p=1818640&postcount=9 for just such a random example. 2.- The UI is being simplified to make it easier for users, yet now users have to *write a script* for a functionality which in 2.6 could be achieved by simply typing on a text entry from the UI. IMO the average user should not have to deal with scripts.
Ubuntu bug about that: https://launchpad.net/products/evolution/+bug/70554
*** Bug 395270 has been marked as a duplicate of this bug. ***
Still valid in 3.2
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org. As part of that, we are mass-closing older open tickets in bugzilla.gnome.org which have not seen updates for a longer time (resources are unfortunately quite limited so not every ticket can get handled). If you can still reproduce the situation described in this ticket in a recent and supported software version, then please follow https://wiki.gnome.org/Community/GettingInTouch/BugReportingGuidelines and create a new bug report ticket at https://gitlab.gnome.org/GNOME/evolution/-/issues/ Thank you for your understanding and your help.