An account in mailspring can not be set up when the SMTP server refuses to send to ‘email@example.com’. This behavior is strange. We have a server that is limited in which domains it relays to, ‘invalid.com’ is not one of them of course. There should at the very least be an override button in the interface to skip such a verification but in my opinion it would be better not to use this verification at all.
The description above should give enough of an indication on how to reproduce this.
Frankly, I wouldn’t expect an email client to send to ‘firstname.lastname@example.org’ to verify its configuration. But if you absolutely must, then you should at least give an option to proceed in any case when verification fails.
- OS and Version: Debian Testing and Ubuntu 20.04
- Installation Method: DEB , snap
- Mailspring Version: 1.9.1
Is there a workaround that would allow me to use mailspring until this is fixed?