Sealwax 1.0.5

• No more waiting on an address that doesn't answer: a mail server's name often leads to several addresses, usually an IPv6 one first. When the network dropped everything sent to that first address, as a broken IPv6 route does, Sealwax waited on it until its time to connect ran out and said the server didn't answer in time, without trying the others. Sealwax now starts on the next address after a quarter of a second while the first goes on trying, and uses whichever answers first, for incoming and outgoing mail alike.
• Large messages open even when the server describes them oddly: Sealwax downloads a message over 10 MB without its attachments, which needs the server's description of how the message is put together. When Sealwax couldn't read that description, the message didn't open, and neither did the other large messages asked for with it. Now such a message is downloaded whole instead, after a moment's reconnect, and the others open as usual.
• Sending turned off says so: when a Microsoft 365 admin turns off SMTP AUTH, the way mail apps send, after you added the account, Sealwax used to keep trying to send without telling you why nothing went. Now the account says "sending off" and a banner says "Sending is turned off" for it and that your organization's admin can turn it on. Your messages wait in the outbox and go once it is on again (issue #21's follow-up).
• A clear word for a Microsoft account to add again: since 1.0.3, Sealwax gives a Microsoft sign-in only to Microsoft's servers. A Microsoft account added earlier with another server saved for it then showed as offline, or quietly didn't send. Now it says "needs adding again", and a banner says to remove the account and add it again.
• For people who build Sealwax themselves: a development build (cargo run) now keeps its own folders, sealwax-devel beside the installed Sealwax's sealwax, so it never opens your real mail or accounts (INSTALL.md).

---

Install, update or uninstall: see INSTALL.md, in plain words.