docs: SpamAssassin ENV docs refactor#3756
Merged
polarathene merged 12 commits intomasterfrom Jan 8, 2024
Merged
Conversation
ENV name logged was incomplete.
polarathene
added
area/scripts
kind/improvement
polarathene
changed the title
SPAMASSASSIN_SPAM_TO_INBOX=1 ENV correctlySPAMASSASSIN_SPAM_TO_INBOX=1 ENV correctly
georglauterbach
previously approved these changes
Jan 7, 2024
casperklein
previously approved these changes
Jan 7, 2024
polarathene
dismissed stale reviews from casperklein and georglauterbach
via
5595edb
casperklein
reviewed
Jan 8, 2024
| - **2.0** => add spam info headers if at, or above that level | ||
| - **2.0** => add 'spam info' headers at, or above this level | ||
|
|
||
| Mail is not yet considered spam, but for purposes like diagnositcs it can be useful to identify mail with a spam score from a lower bound than `SA_TAG2`. |
Member
There was a problem hiding this comment.
Suggested change
| Mail is not yet considered spam, but for purposes like diagnositcs it can be useful to identify mail with a spam score from a lower bound than `SA_TAG2`. | |
| Mail is not yet considered spam, but for purposes like diagnostics it can be useful to identify mail with a spam score from a lower bound than `SA_TAG2`. |
polarathene
commented
Jan 8, 2024
Co-authored-by: Casper <[email protected]>
Member
Author
|
At this point, the content is probably sufficient to migrate into it's own dedicated docs page (and pull in related FAQ items) 😝 Maybe if I find the time to reorganize the docs better I'll get around to that. Thanks for the review catching those typos 🙏 Happy with this now, enabling auto-merge 🚀 |
Contributor
|
Documentation preview for this PR is ready! 🎉 Built with commit: 5dafd4b |
polarathene
changed the title
SPAMASSASSIN_SPAM_TO_INBOX=1 ENV correctly
polarathene
changed the title
casperklein
approved these changes
Jan 8, 2024
This was referenced Jan 9, 2024
Merged
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Description
SPAM_TO_INBOX=1).SA_KILL, linked references to other related ENV.SA_KILLexisting admonition about quarantine andONE_DIRwas introduced in Aug 2019. Revised.'warning'log level missed in review, this has been corrected to'warn'.Fixes: #2491
References:
SPAMASSASSIN_SPAM_TO_INBOXdefault changed from0to1in DMSv10.5.0(Mar 2022)SA_KILLdefault changed in DMSv12.0.0(April 2023), from6.31(same asSA_TAG2) to10.0(thus not all mail marked as spam has a quarantine copy).SPAMASSASSIN_SPAM_TO_INBOX=1andSA_KILL.SPAMASSASSIN_SPAM_TO_INBOX=1was bugged at the time, by not modifying$final_spam_destinyfrom theD_BOUNCEvalue we used to default to. Resolved with Feature: Spam to Junk folder #1485SPAMASSASSIN_SPAM_TO_INBOXENV was introduced in March 2020.Type of change
Checklist:
CHANGELOG.md