mirror of
https://github.com/anonaddy/anonaddy.git
synced 2026-04-25 22:25:55 +03:00
[GH-ISSUE #593] [Enhancement] Allow blocking senders. #995
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#995
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 @RokeJulianLockhart on GitHub (Feb 9, 2024).
Original GitHub issue: https://github.com/anonaddy/anonaddy/issues/593
I don't want to disable an alias every time spam reaches one, especially because most spam I receive is from the same few addresses (yet can't be unsubscribed from; it's mostly phishing). Consequently, please allow me to block senders per alias, recipient, and account-wide (the 3rd being the most important for me immediately).
@Cascabel-dev commented on GitHub (Feb 14, 2024):
You should just be able to block the sender from the email, no? When you receive the forwarded mail, it will be youralias+sender=sender.com@yourname.anonaddy.com. So if you block that, you would just be blocking that specific sender, not the alias itself. It would still be great to have a place to do it in the Addy dashboard, but you shouldn't have to deactivate the whole alias. If I am missing something, then please let me know!
@RokeJulianLockhart commented on GitHub (Feb 16, 2024):
@Cascabel-dev, the example you provide would only block the sender from a specific alias. I need it at least account-wide to lessen currently common spearfishing attempts.
Additionally, most e-mail providers I've used (GMail, Outlook, and potentially Proton) appear to check whether a domain is in a whitelist and if not, block the entire domain, when it automatically detects spam from an address.
@willbrowningme commented on GitHub (Feb 16, 2024):
The solution I have in mind for this would only be able to block sends based on the SMTP FROM address (return path) and not the
From:header. So it might not be as effective for services using variable envelope return path (VERP).@RokeJulianLockhart commented on GitHub (Feb 16, 2024):
For those reading, https://stackoverflow.com/a/7874260/9731176 is an easy-to-understand explanation of VERP.
@RokeJulianLockhart commented on GitHub (Jul 5, 2024):
@willbrowningme, I've had to put a few senders' messages in spam recently, because specific addresses routinely find new aliases and send mail to them - I can't constantly disable and replace my aliases just for a few specific spammers. However, I really don't want to be inadvertently telling my e-mail provider that the
addy.iodomain is spam, but without a way to block these senders at this level, I don't see much of an alternative except to utilize my provider's spam filtration feature. Luckily it's Proton, so hopefully the effect isn't as bad as if I were using MSFT, etc.@willbrowningme commented on GitHub (Jul 6, 2024):
@RokeJulianLockhart Please do not mark any messages forwarded to you by addy.io as spam as it achieves nothing but to harm addy.io's sending reputation.
You can currently use your rules to block emails based on the sender, you could block an entire sender's domain.
You can also forward me the messages and I can look into blocking the spammers completely from the mail servers.
I still do plan to add a global blacklist but as mentioned above this would only work for the SMTP FROM address (envelope sender) and not the
From:header.@RokeJulianLockhart commented on GitHub (Jul 6, 2024):
@willbrowningme, I didn't realize that I could use rules for that. I'll try that. Where is that feature documented, though? I don't see it in
bc626e80bfc3e21a8f9ae39fce987a33ad795e2a/README.md#faq. Can you confirm that the undermentioned is correct to blockgracexiaomonv@qftechtalent.combeing forwarded throughk6x2vl0p@rokejulianlockhart.addy.io?Most importantly, I don't see a way to select the value of
X-Anonaddy-Original-Sender. I'm guessing that "Sender e-mail" meansReply-To...?@RokeJulianLockhart commented on GitHub (Dec 1, 2024):
@willbrowningme, there's a severe limitation to this method:
...am I expected to make a new blocking rule every 10 blocks?
@RokeJulianLockhart commented on GitHub (Sep 1, 2025):
I was rather foolish. Presumably, I'm able to add multiple conditions per rule,
OR'd:That's significantly more convenient. With
issues/765, this issue shall be improved.@obadz commented on GitHub (Dec 23, 2025):
I'd suggest injecting an
List-Unsubscribeheader which the server would intercept to add the sender of that email to a special rule called "Block Senders" which which just blocks a list of senders. This would block them across all aliases but I think that's the desirable outcome.@willbrowningme commented on GitHub (Feb 23, 2026):
This is now possible with the new blocklist feature.
You can also change the "List-Unsubscribe Behaviour" in your account settings to:
Always use one-click block sender emailorAlways use one-click block sender domain.@RokeJulianLockhart commented on GitHub (Feb 23, 2026):
@willbrowningme, thanks. However, I've begun to like your Rules-based approach, because I can decide the exact RegEx, and what I want to do to the received mail. Regardless, I'd require
issues/819to be completed, to transfer them, if I were to want to.