jaymzh
valid addresses supplied to "-n" treated as invalid, and invalid addresses treated as valid
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.
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@
