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

valid addresses supplied to "-n" treated as invalid, and invalid addresses treated as valid #127

Open
ghost opened this issue Mar 5, 2019 · 1 comment

Comments

@ghost
Copy link

ghost commented Mar 5, 2019

case 1: valid email rejected

This command should work:

pius -n bob@localhost -H 127.0.0.1 -P 587...

but it results in pius: error: Option -n: Value bob@localhost does not appear like a well formed email address

case 2: possibly invalid email accepted

My knee-jerk next attempt was pius -n [email protected] -H 127.0.0.1 -P 587..., but that address is refused by the mail server. However it was submitted by pius, so pius regarded it as a valid address. It's unclear to me if it is valid. This thread suggests some tools regard it as valid, so maybe pius is doing the right thing in case 2.

@jaymzh
Copy link
Owner

jaymzh commented Jul 1, 2019

bob@localhost is... arguably an invalid mail address for this purpose. If that's a UID in a key, I cannot send encrypted email to it, nor can I send validate it and sign that UID.

It is true that you could have an email at a TLD, theoretically, but I'm not aware of anywhere that's done, so I'm not sure that it's a problem in the real world.

As to name@, yeah that's bogus, and we should fix that. Not pressing, but a valid bug.

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

No branches or pull requests

1 participant