-
-
Notifications
You must be signed in to change notification settings - Fork 140
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WIP: Added Rspamd installation #493
base: master
Are you sure you want to change the base?
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #493 +/- ##
==========================================
- Coverage 54.40% 53.86% -0.54%
==========================================
Files 10 10
Lines 761 789 +28
==========================================
+ Hits 414 425 +11
- Misses 347 364 +17 ☔ View full report in Codecov by Sentry. |
Hi @Spitfireap! I'm seeing that your contributions are also included in the latest We are soon doing the switch from v1 to the v2 series, and have not the best experiences with SpamAssassin, why rspamd comes to mind. Seeing your contributions encourages me to test it out. Would it be possible to add some documentation, e.g. to the readme, about how to set up rspamd (instead of SpamAssassin + amavis?), and maybe some notes to the I'm interested in checking out your branch here during our upgrade, to give feedback and find quirks, but I would need some instructions on how to work myself there. Thanks in advance for any pointers! |
Hi, thanks for your interest. The branch nor modoboa-rspamd is not ready yet for production use eventhough we use it with @tonioo and it does the work (minus some adjustments needed). We have not developed any migration tool but a backup and restore on a fresh server As for the documentation, it is not automatically deployed for now but it is nonetheless avaliable here (not quite detailed for now though). |
I will follow the these developments closely. We have no ETA yet for when we will do (1) the switch to the v2 series and (2) to |
I'm very interested in testing this branch, esp. due to support for ARC signing in rspamd. Unfortunately we only have a production instance available and a supported upgrade path is a sufficient condition for this integration to work. From my current knowledge, these upgrade instructions should include information about installing and setting up rspamd, as well as removing and uninstalling SpamAssassin and OpenDKIM. Ideally this is taken care of by the installer. – At this stage of maturity of this PR, does it seem feasible that we set up a testing instance and work towards documenting this upgrade path? |
@almereyda I've added it with my latest commit on the installer by reusing the DKIM keys. I'm not sure if it's ok or not... |
I can come back here during winter. |
Let me see to testing this PR on a separate testing environment during the next month. |
Enabled the installation of automated Rspamd installation through the installer.