I've so far preferred SA-Exim to the exiscan spam condition because the latter is somewhat limited as to what you can do to with the messages you decide to let through (you only have $spam_score(_int), $spam_bar and $spam_report to play with).
There is an idea to add a new method to spamd that just returns the headers that SpamAssassin would have added (see http://issues.apache.org/SpamAssassin/show_bug.cgi?id=4469). I don't know what might become of that idea but if it becomes reality I think the new method would be the best one to use (because you could easily achieve the same result whether messages are passed through Exim calling SA or through spamassassin directly). Let's say that you in some future version could do warn add_header = $spam_headers There is one issue though, and that is that if SA-rewritten headers are to be included, then either you can't use rewrite_header in SA or you'd need a complicated construct in the system filter to remove all headers found in $spam_headers before the new headers could be added. It could therefore conceivably be very handy to have a filter command that would *replace* headers in one action. It can probably be useful in other situations as well. What do you think? -- Magnus Holmgren -- ## List details at http://www.exim.org/mailman/listinfo/exim-dev Exim details at http://www.exim.org/ ##
