Skip to content

MailFerry v2.0.2 — IMAP Migration & Sync

Choose a tag to compare

View all tags
@ajsap ajsap released this 19 Jul 00:19
v2.0.2
49c208a

Superseded release

This version contains known issues that have been resolved in v2.0.3. Users should upgrade to the latest stable release. This release is retained for historical and reproducibility purposes.

Upgrade: MailFerry v2.0.3 — latest stable release

MailFerry v2.0.2 — Patch Release

High-Performance Native IMAP Migration Engine.

Fixes the "stair-step" terminal output defect at its actual root cause
— reproduced on real macOS arm64 with v2.0.0/v2.0.1, and this fix
verified on that same real environment before release.

Fixed

  • Stair-step output: MailFerry writes ordinary "\n" line output
    and relies on the terminal’s output post-processing (OPOST/ONLCR)
    for carriage returns. A terminal left in a raw-ish state by a
    previously crashed full-screen program renders every subsequent run
    as a stair-step from the very first banner line — and v2.0.1’s
    capture/restore preserved that inherited state instead of healing
    it. MailFerry now repairs the stty sane newline flag subset before
    its first byte of output (only when actually broken, with a one-line
    notice), and every capture thereafter snapshots the sane state — no
    exit path can hand a broken terminal back to the shell. Already-sane
    terminals are untouched; pipes/non-TTY output are never modified;
    TUI, headless and SSH/tmux/screen behaviour is unchanged.

Added

  • mailferry term-diag — supported terminal self-test (no servers, no
    credentials, no data).
  • MAILFERRY_TERM_DIAG=FILE — per-stage termios flag logging for field
    diagnosis (flags only — never mailbox data).
  • PTY-level regression tests asserting that every rendered line begins
    at column 1 on clean and pre-broken terminals, and that a broken
    terminal ends healed.

No engine, protocol, state or data-handling changes: migration
behaviour is identical to v2.0.0/v2.0.1. Existing mailferry.db and
mailferry.toml are fully compatible.

macOS note: binaries remain unsigned/not notarised — Gatekeeper asks
for a one-time "Open Anyway" approval
(guide).

Verify downloads: shasum -a 256 -c SHA256SUMS
Issues: https://github.com/ajsap/mailferry/issues
Author: Andy Saputra andy@saputra.org · Licence: GNU AGPL v3.0

Assets 9
Loading