mirror of
https://github.com/axllent/mailpit.git
synced 2026-04-26 00:35:51 +03:00
[GH-ISSUE #333] Relay recipient blocklist #221
Labels
No labels
awaiting feedback
bug
docker
documentation
enhancement
github_actions
invalid
pull-request
question
stale
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/mailpit#221
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 @zmweske on GitHub (Jul 11, 2024).
Original GitHub issue: https://github.com/axllent/mailpit/issues/333
First off, I love this application and thank you for creating and maintaining it.
Would you consider creating a blocklist as well? I think that one simple reason for this would be to block all emails sent to admin@admin.lan for some services so they don't spam a downstream SMTP provider (and prevent spam filtering).
Similar to the allowlist defined by
--smtp-relay-matching, the blocklist would (in the same but opposite way- list below copied from https://github.com/axllent/mailpit/issues/108#issuecomment-1535317838):Haven't had time to set up a dev environment yet, but based on #108, it should be very similar with just the inverse logic and an extra branch for the config flag?
Thanks again for your work with this project!
@axllent commented on GitHub (Jul 12, 2024):
Thank you for opening a new issue @zmweske. I will look into this in the near future and see what I can do.
@axllent commented on GitHub (Jul 14, 2024):
@zmweske I have added this feature in v1.19.1 and is documented here.
Please let me know if this works as you expected?
@axllent commented on GitHub (Jul 21, 2024):
I'm closing this issue as it was released a week ago. Please feel free to re-open if there are issues.
@zmweske commented on GitHub (Jul 23, 2024):
Had been busy but finally got around to testing it out- works like a charm- thanks so much!
@axllent commented on GitHub (Jul 24, 2024):
Great, thanks for the feedback!