mirror of
https://github.com/anonaddy/anonaddy.git
synced 2026-04-25 14:15:53 +03:00
[GH-ISSUE #684] Rules to whitelist addresses from spam detection #1048
Labels
No labels
bug
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/anonaddy#1048
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @stites on GitHub (Sep 24, 2024).
Original GitHub issue: https://github.com/anonaddy/anonaddy/issues/684
Is it possible to bypass spam filtering for certain addresses? Maybe with the "Rules" feature in addy.io that I just noticed? I subscribe to a plaintext digest which triggers addy.io's spam detector and preppends an html tag with the warning:
The spam detector is doing the right thing, but the prepended tag messes up the plaintext rendering of the message (so I have to inspect the message source to see the correct formatting).
I'm just using addy.io, so I'm not sure if this feature is already in the source. Maybe I missed something in the documentation around defining rule-sets. Any pointers would be appreciated, thank you!
@willbrowningme commented on GitHub (Nov 27, 2024):
I could add a setting to change that behaviour to prepend
**SPAM**to the subject line instead of adding the warning to the email body.@OlliesGudh commented on GitHub (Apr 24, 2025):
Maybe [Feature Request] to include option in the spam warning header itself or dashboard to whitelist given domain? Alert is fine, it's just kinda annoying when receiving several e-mails from a trusted sender.