Add spamassassin start and enable at boot. #228
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
There appears to be an issue when using Debian 11 where spamassassin won't register to start at boot, and even in a post-install rebooted state, will not be running. Perhaps I am incorrect, but I think this is a useful addition that makes sure this is all set up to operate as you intended. I am not much of a systemd guy, but I think this is the correct way to do this. It appears to work on a server I used this script on. Please reject if superfluous or unnecessary. Thanks for your work automating the "really fun" part of all this!
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In Debian 11, the spamassassin process does not appear to start after boot, so I included the debian/ubuntu generic command to (hopefully) ensure this is done. Perhaps I missed something, but I don't think this was explicitly handled otherwise.
I only make this alteration because the issue occurred on my own use of the script. I figure I may not be the only one. I am no fan of, or expert in, systemd, so this may be incorrect in approach or use.