-
Notifications
You must be signed in to change notification settings - Fork 0
GH-111 - more and better spam filtering inside the AS Email Service #137
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
Open
scanner
wants to merge
20
commits into
feature/GH-111-add-an-option-to-block-incoming-email-that-is-considered-spam
Choose a base branch
from
main
base: feature/GH-111-add-an-option-to-block-incoming-email-that-is-considered-spam
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
GH-111 - more and better spam filtering inside the AS Email Service #137
scanner
wants to merge
20
commits into
feature/GH-111-add-an-option-to-block-incoming-email-that-is-considered-spam
from
main
Conversation
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
* updating requirements * Only log from `mail` at error or higher * Update to python3.12
… in the external pw file (#118) * GH-117 - add support for maintaing an external pwfile by email account This is still lacking the test for the code we added. * GH-117 - testing the reading and writing of external pwfile * GH-117 - update email account update task to use relative paths for mail dirs Need to write test for the two tasks. * GH-117 - test delete/add/update tasks for email accounts in external pw file
* GH-116 - I was using the wrong python redis client. * GH-116 - create default folders. Also better fix for GH-123 - catch EmailAccount.DoesNotExist. With the proper redis client we can retry tasks that fail. Since we create 9accounts at once, retry up to 10 times. Also make sure that we can lock the pwfile so that there is only one reader or writer at a time.
…-1 encoded messages, do the binary conversion ourselves. (#127)
…. Update requirements. Add more files that can be filtered on. (#154)
* Updating requirements * updating requirements * Use fakeredis for the index test as compressor relies on being able to use the cache Also move running tests out of the docker container. * Retry failed email. This will keep retrying forever, based on the assumption that the failure was transient, and if it is not, an admin will manually deal with the messages.
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.
Postmark gives us spam assassin.. which used to be pretty weak-sauce.. and after watching it in action is still pretty weak sauce for the kinds of spam we get.
While we will still be delivering all email's including spam to local delivery, we want the option of blocking it when sending it via forwarding.
Eventually we might also get a daily report of blocked messages on the incoming stream from postmark and present users with a "here is the spam that was filtered" system.