> Also, I'd like to propose these for sa-update inclusion. Finally, I > should add. Any opinion about this?
+1, go for it. They are of course already in the 3.3.0 updates. BUt for 3.2.x, things are a little trickier.... they're built from a separate SVN url: https://svn.apache.org/repos/asf/spamassassin/rules/branches/3.2 . So you add the rules there, then copy the contents of that dir to the "rules" dir of a 3.2.x checkout and make sure it passes --lint with that version before checking them in. Then you need to log in to the Solaris Zone (see http://wiki.apache.org/spamassassin/SpamAssassinAsfZone ), in order to publish a rule update from there. see http://wiki.apache.org/spamassassin/ManualRuleUpdates . I'll send you account details for that machine offlist. (the hostname is "spamassassin.zones.apache.org" btw.) > (Side note: Any ham hits so far > turned out to be more likely a dirty corpus, than a real, rare FP. Yay.) on this issue: it's customary to ask the people to check their corpus; if you cut and paste the lines from the "[logs]" link on the per-user mass-check results page, and mail those to dev@, the submitters can use masses/mboxget to turn those mass-check logs back into the scanned message, and tell if it's a real FP or not -- and more importantly, delete the misfiled messages from their corpus. --j.
