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

Tracking issue for VRFY support #7

Open
novedevo opened this issue Jun 19, 2021 · 2 comments
Open

Tracking issue for VRFY support #7

novedevo opened this issue Jun 19, 2021 · 2 comments
Labels
enhancement New feature or request

Comments

@novedevo
Copy link
Member

this one's a little trickier than some other commands. RFC declares that we can't just check syntax, we need to make sure that we actually have a user at that mailbox, so to support VRFY we already need to maintain a user database. In the initial versions, this could be a .txt file, or a Vec<String>, but if we want this to be a functional server we'll need something a little heavier.

Similar issues apply to EXPN, but if we just don't create any mailing lists we can trivially return for that one.

@novedevo novedevo added the enhancement New feature or request label Jun 19, 2021
@novedevo
Copy link
Member Author

if we do end up supporting EXPN, we need to add it to our EHLO response

@novedevo
Copy link
Member Author

we also should put a config option to disable VRFY and EXPN for security reasons, returning 252

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

No branches or pull requests

1 participant