Skip to content
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

[feat] Support failing faster for unroutable address #289

Open
2 tasks done
xim opened this issue Feb 7, 2024 · 1 comment
Open
2 tasks done

[feat] Support failing faster for unroutable address #289

xim opened this issue Feb 7, 2024 · 1 comment

Comments

@xim
Copy link

xim commented Feb 7, 2024

Describe the feature

Currently, if an email is sent to an unroutable address, the email is deferred (421).

I get that this can be helpful when first configuring a domain, but in a stable setting I'd prefer these to fail with 550 Unrouteable address

Adding a configuration option for this, e.g. adding a config or by allowing aliases to be explicitly set to reject incoming email (so I can add a wildcard reject alias)

Checklist

  • I have searched through GitHub issues for similar issues.
  • I have completely read through the README and documentation.
@xim xim added the enhancement label Feb 7, 2024
@titanism
Copy link
Contributor

titanism commented Feb 7, 2024

@xim thank you for the request! we'll look at adding this – right now we're trying to ship calendars/contacts/newsletter support

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants