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

New feature: Deny list #42

Closed
MHP47 opened this issue Feb 21, 2021 · 2 comments
Closed

New feature: Deny list #42

MHP47 opened this issue Feb 21, 2021 · 2 comments
Assignees
Labels
enhancement New feature or request

Comments

@MHP47
Copy link

MHP47 commented Feb 21, 2021

My Problem

Great project, love having the catch-all option for emails, works perfect.

Thinking about a deny list of some sort, so I can sign up dodgy_website@domain.com and then after using it and not needing it again, add that specific email to a deny list, so when the lambda executes for incoming mail, checks the address against the deny, and drops it instead of formatting into the S3 buckey

Solution

Seems like a simple DynamoDB table lookup would suffice, but I haven't thought too much into latency lookups, or costs of looking up each time

@MHP47 MHP47 added the enhancement New feature or request label Feb 21, 2021
@davidgatti
Copy link
Member

Thank you for the suggestion, but the project was designed to not care what you receive, since it is not going to your inbox, it is stored in S3, so if you don't care about the emails, don't go to that folder.

As you mentioned, it is a catch all.

@cariaso
Copy link

cariaso commented Feb 21, 2021

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Development

No branches or pull requests

3 participants