I am probably in the minority here, but I like keeping track of the stdout and stderr of all my running applications, in order to spot if there's anything unusual going on. Some weeks ago I added a few filtering rules, and one of the first rules was to perform no further processing if the mail comes from somebody in my mailing list. The filtering rules work correctly, but now claws-mail is always printing out: (claws-mail:*): Claws-Mail-WARNING **: No further processing after rule stop Why such a warning? The code is working as intended, I don't need to be reminded of that... each time I check for new email. The offending line is in src/filtering.c:742. You can get this warning anyway if you are debugging the filtering session, so why not remove that from non-debugging sessions?
I agree that a warning is out-of-place for something that works as expected. If anything, g_message() or g_debug() would be more suitable.
Maybe it is just me who has misunderstand something:-) But what is the reason for writing to stderr that something performed as expected when not running in debug mode?
Changes related to this bug have been committed. Please check latest CVS and update the bug accordingly. You can also get the patch from: http://www.colino.net/claws-mail/ 2011-10-23 [holger] 3.7.10cvs43 * src/filtering.c Don't issue a warning for designed behaviour of the stop rule. Fixes bug #2520, 'Please remove verbose "No further processing after rule %s" message.'