I noticed this while working on Bug 1563891. Also, if you initially enter a valid address like ```gds@localhost``` and then edit it back to invalid ```gds```, the Send button remains enabled. I think it should become disabled. It does for 68. But with 78, if you still try to send to the bad address ```gds```, you get the alert: "gds <> is not a valid e-mail address because it is not of the form user@host. You must correct it before sending the e-mail." So the send the bad address is still inhibited. > Reverse case: I'm surprised that localpart@server (without domain) gets enabled for sending. Are there still local server scenarios where that can succeed to send? Seems like gds@localhost might be a possible valid example of this. (I assume that by "with domain" you mean localpart@server.net ?)
Bug 1664733 Comment 2 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
I noticed this while working on Bug 1563891. Also, if you initially enter a valid address like ```gds@localhost``` and then edit it back to invalid ```gds```, the Send button remains enabled. I think it should become disabled. It does for 68. But with 78, if you still try to send to the bad address ```gds```, you get the alert: "gds <> is not a valid e-mail address because it is not of the form user@host. You must correct it before sending the e-mail." So sending to the bad address is still inhibited. > Reverse case: I'm surprised that localpart@server (without domain) gets enabled for sending. Are there still local server scenarios where that can succeed to send? Seems like gds@localhost might be a possible valid example of this. (I assume that by "with domain" you mean localpart@server.net ?)