https://issues.apache.org/SpamAssassin/show_bug.cgi?id=7043
[email protected] changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #2 from [email protected] --- I had a look at the 'glue' I'm using, which is vm-spamassassin http://vm-spamassassin.cvs.sourceforge.net Apparently the code there bluntly filters all incoming mail through spamassassin and takes whatever the output as "marked mail": -- emacs lips sniplet from vm-spamassassin.el, slightly older version ---- (message "Assassinating new mails... ") (call-process-region (point) (point-max) (or shell-file-name "sh") t t nil shell-command-switch (concat vm-spamassassin-formail-program " " vm-spamassassin-formail-program-options " " vm-spamassassin-program " " vm-spamassassin-program-options)) (message "Assassinating new mails... done") --- In bash speak (and resolving all the symbols) this roughly translates to cat input-mail-NN.txt | formail -s spamassassin > output-mail-NN.txt I agree that it is rather disappointing of vm-spamassassin to have no sort of error handling here, so the glue is indeed to blame. Nevertheless IMHO spamassassin should always echo the input (if any), i.e., yield config: no rules were found! Do you need to run 'sa-update'? at /usr/bin/spamassassin line 407. `cat input-mail-NN.txt` The data would then be at least present. It does not help the user much if you can just tell him that her glue is broken. -- You are receiving this mail because: You are the assignee for the bug.
