I've read every word of this 19 page thread. I've read through the wiki page
. I've taken a Lot of notes in preparation for what turns out to be a rather trivial initial switch. I've been eager to try out Rspamd, but I don't think I'm ready. For all of its faults, SpamAssassin is already built-in and an integral part of this Zimbra environment. For my very modest usuage, self-hosting for about 6 domains, no responsibility to clients, I don't feel compelled to quest for the rewards that might be possible with Rspamd, when it seems SA might be fine for now. The observations and conclusions by everyone here weighed significantly in my decision.
My greatest inspiration has really been due to my respect for @phoenix. I trust whatever Bill says, and have since my very first post here
and his response, just over a year ago. I've learned a Lot since then and am very thankful for every bit of information that I've been able to find here. I also appreciate that Vsevolod Stakhov, @vstakhov is author of Rspamd, has contributed to this thread.
But for me, Rspamd needs to remain on the horizon. I'll move forward with SA for some number of months and then I might come back if I feel the "brand spankin new v2.0" might scratch an itch or two.
For now, I'm posting some "errata" notes about Bill's wiki page on Rspamd, which I hope are accurate and helpful.
- There is a duplicate section at top, starting with "Configuring Rspamd on the Zimbra Server" down to after the "yum install rspamd redis" command.
- Under "Modify the ZCS…" it shows '[/code]', indicating mismatched markdown.
- The listing under 'zmprov gs' is missing zimbraMtaNonSmtpdMilters.
- By text "the following 'one', run the following (singular) command…" ... There are two commands.
- There is a note "If you want extended headers…" But the value is already set in the previous code block, so the reference is redundant.
- "The only modification you should need to make after each upgrade are the ones to the zmconfigd.cf file and..." … There was no previous mention of zmconfigd.cf.
- Minor grammar/typo : "and also given it" … should be " and have also given it".
- The example for non_smtp_milters shows null but the instruction says to change it. (There is a value)
- "this file needs changing as mentioned in the initial installation settings: " ... There was no previous mention of main.cf.
- The wiki doesn't mention zimbraServiceEnabled.
- The forum page1 has a lot more detail on logging.inc. I'm not sure if that was new material or code that should be added. It's subject to changes in Zimbra releases so too much reproduction of core code is probably not desirable.
- From page 1 of forum thread: "in addition you'll also need to modify the nightly scheduled cron job that trains the anti-spam system." There's no info about this. It's discussed later in the thread.
- Perhaps most of the install/configuration can be implemented in the wiki as a script, as contributed by @siavash.
- As I went through the wiki I was wondering why the installation couldn't be repeated through each Zimbra update. For example, the wiki documents the removal of four lines from /opt/zimbra/conf/zmconfigd.cf after an update. Why don't we need to remove those as part of the installation? If the installation includes "remove these four lines if they exist", then the intallation and become almost the exact same process, which can be scripted and simply re-run whenevever desired. That includes the creation of zmtrainsa and it's copying/overwrite of the default Zimbra code after each update.