Repository navigation
v0.3.2 — safety guards, reply fixes
Security
- Behavior change: an account whose IMAP or SMTP has
tls = falseandstarttls = falseto a non-loopback host is now rejected when the config loads, and byimap-wizard config validate. The login would cross the network in clear text. To fix a config that stops loading, settls = trueorstarttls = trueon the named[accounts.imap]/[accounts.smtp]section.localhost,127.0.0.0/8and::1stay allowed. Adapted from Mailoo by Bitfloo. - A refused login still shows the server's own reason (for example "application-specific password required"), with any secret it quotes scrubbed.
- Error text from IMAP and SMTP connects, sends, connection tests, the watcher and the OAuth2 token endpoint now has the account's password, OAuth2 tokens and client secret replaced with
[redacted]before it is returned or logged. Adapted from Mailoo by Bitfloo.
Added
NOTICEfile with fork and attribution details; code adapted from Mailoo by Bitfloo (LGPL-3.0-or-later) is credited there and in file headers.- A baseline test locks the registered tools, prompts and resources (names and schemas) in full and read-only mode, so accidental public API changes fail CI. Approach from Mailoo by Bitfloo.
Fixed
- Replies and forwards no longer stack prefixes:
RE:,re:,AW:,SV:,FW:andWG:are recognised in any case (upstream #102). - Sent copies and drafts are normalised to CRLF before IMAP APPEND, so strict servers accept them (upstream #116).
Docs
- The upstream section now shows upstream's own status for each issue as of v0.6.0, instead of implying all are still unfixed there.
Install: npx -y imap-wizard