https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6566
--- Comment #6 from Mark Martinec <[email protected]> 2011-05-05 17:07:19 UTC --- > > Only the code modification from the attached patch has been applied > > to trunk, not the change to a reporting template - so there is no > > user-perceived change, retaining compatibility. > > It seems strange to me to consider changing the default wording to be a > compatibility problem. The wording is wrong. It's fine by me to commit the change of a report template to 3.3.2, I just didn't want to do it straight away without approval. One thing to consider: if a change to 'report' in 10_default_prefs.cf gets propagated through sa-update to older versions, the report will not be expanded correctly. I guess this can be handled by 'if version' and both variants provided. Btw, the changed report text as suggested by the attached patch yields either the (for ham): Spam detection software, running on the system "xxx.xxx.xxx", has NOT identified this incoming email as spam. The original message has been attached to this so you can view it or label similar future email. If you have any questions, see the administrator of that system for details. or for spam: Spam detection software, running on the system "xxx.xxx.xxx", has identified this incoming email as possible spam. The original message has been attached to this so you can view it or label similar future email. If you have any questions, see the administrator of that system for details. -- Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
