Adds import fastmail — a Fastmail source for migrate. The 27.1 roadmap flagged this as "JMAP — easy + good marketing," and that's exactly what it is.## What it isimport fastmail is import jmap with Fastmail's server and sign-in filled in:- Server preset to https://api.fastmail.com/jmap/session — where every Fastmail account reaches JMAP, custom domains included — overridable with --url.- Auth is bearer-token only (Fastmail's JMAP takes nothing else): --token, $INBUXA_MIGRATE_API_KEY, or a prompt.- It reuses the entire JMAP import pipeline, so the estimate (counts-only, as for any JMAP), the delta re-sync, and the archive format all come with it for free. No new import machinery.What crosses over is whatever that account's session advertises — mail always (Fastmail is the reference JMAP mail server), calendars and contacts where Fastmail offers them over JMAP, and the capability-gated import simply skips what isn't advertised.## The "easy" part: primary-account defaultThe generic import jmap requires naming the account (--account-id/--account-name), which a one-mailbox Fastmail user shouldn't have to do. So a new AccountSelector::Primary resolves the account the session marks primary for mail (primaryAccounts, RFC 8620 — Fastmail sends it), falling back to the sole account, and only asking which when there are several and none is primary. With no --account-*, import fastmail just works.That's the one change touching shared code (session.rs gains the optional primaryAccounts field; account.rs the new variant). It's additive and import jmap's own required behavior is unchanged.## Validation- cargo fmt clean, cargo clippy --all-targets -D warnings clean, full cargo test --locked green.- New tests: fastmail defaults to Fastmail's URL + bearer + primary account; --url override; --auth-basic rejected (bearer-only); and three for AccountSelector::Primary (uses primaryAccounts, falls back to the sole account, errors on ambiguity).- import fastmail --help renders; import --help lists it next to jmap.README "Sources" entry, a docs/usage.md section, and a CHANGELOG [Unreleased] note.Remaining migrate [post] sources (POP3, Zimbra/Zoho) and the reconciliation report are separate items, not in this PR.
Adds `import fastmail` — a Fastmail source for migrate. The 27.1 roadmap flagged this as "JMAP — easy + good marketing," and that's exactly what it is.## What it is`import fastmail` is `import jmap` with Fastmail's server and sign-in filled in:- **Server** preset to `https://api.fastmail.com/jmap/session` — where every Fastmail account reaches JMAP, custom domains included — overridable with `--url`.- **Auth** is bearer-token only (Fastmail's JMAP takes nothing else): `--token`, `$INBUXA_MIGRATE_API_KEY`, or a prompt.- **It reuses the entire JMAP import pipeline**, so the estimate (counts-only, as for any JMAP), the delta re-sync, and the archive format all come with it for free. No new import machinery.What crosses over is whatever that account's session advertises — **mail always** (Fastmail is the reference JMAP mail server), calendars and contacts where Fastmail offers them over JMAP, and the capability-gated import simply skips what isn't advertised.## The "easy" part: primary-account defaultThe generic `import jmap` requires naming the account (`--account-id`/`--account-name`), which a one-mailbox Fastmail user shouldn't have to do. So a new `AccountSelector::Primary` resolves the account the session marks primary for mail (`primaryAccounts`, RFC 8620 — Fastmail sends it), falling back to the sole account, and only asking which when there are several and none is primary. With no `--account-*`, `import fastmail` just works.That's the one change touching shared code (`session.rs` gains the optional `primaryAccounts` field; `account.rs` the new variant). It's additive and `import jmap`'s own required behavior is unchanged.## Validation- `cargo fmt` clean, `cargo clippy --all-targets -D warnings` clean, full `cargo test --locked` green.- New tests: fastmail defaults to Fastmail's URL + bearer + primary account; `--url` override; `--auth-basic` rejected (bearer-only); and three for `AccountSelector::Primary` (uses `primaryAccounts`, falls back to the sole account, errors on ambiguity).- `import fastmail --help` renders; `import --help` lists it next to `jmap`.README "Sources" entry, a `docs/usage.md` section, and a CHANGELOG `[Unreleased]` note.Remaining migrate [post] sources (POP3, Zimbra/Zoho) and the reconciliation report are separate items, not in this PR.
import fastmail imports from a Fastmail account over JMAP. It is import
jmap with Fastmail's server (https://api.fastmail.com/jmap/session, where
every Fastmail account reaches JMAP, custom domains included) and
bearer-token sign-in already filled in, so it needs only an API token.
What it brings across is whatever that account's session advertises:
mail always, calendars and contacts where Fastmail offers them. The same
import pipeline, so the estimate, the delta re-sync and the archive
format all come with it.
With no --account given it imports the account the session marks primary
for mail, which a personal account has exactly one of; a new
AccountSelector::Primary resolves that from the session's primaryAccounts
(RFC 8620), falling back to the sole account and asking which only when
there are several and none is primary. That spares the common case from
naming its own account.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Adds
import fastmail— a Fastmail source for migrate. The 27.1 roadmap flagged this as "JMAP — easy + good marketing," and that's exactly what it is.## What it isimport fastmailisimport jmapwith Fastmail's server and sign-in filled in:- Server preset tohttps://api.fastmail.com/jmap/session— where every Fastmail account reaches JMAP, custom domains included — overridable with--url.- Auth is bearer-token only (Fastmail's JMAP takes nothing else):--token,$INBUXA_MIGRATE_API_KEY, or a prompt.- It reuses the entire JMAP import pipeline, so the estimate (counts-only, as for any JMAP), the delta re-sync, and the archive format all come with it for free. No new import machinery.What crosses over is whatever that account's session advertises — mail always (Fastmail is the reference JMAP mail server), calendars and contacts where Fastmail offers them over JMAP, and the capability-gated import simply skips what isn't advertised.## The "easy" part: primary-account defaultThe genericimport jmaprequires naming the account (--account-id/--account-name), which a one-mailbox Fastmail user shouldn't have to do. So a newAccountSelector::Primaryresolves the account the session marks primary for mail (primaryAccounts, RFC 8620 — Fastmail sends it), falling back to the sole account, and only asking which when there are several and none is primary. With no--account-*,import fastmailjust works.That's the one change touching shared code (session.rsgains the optionalprimaryAccountsfield;account.rsthe new variant). It's additive andimport jmap's own required behavior is unchanged.## Validation-cargo fmtclean,cargo clippy --all-targets -D warningsclean, fullcargo test --lockedgreen.- New tests: fastmail defaults to Fastmail's URL + bearer + primary account;--urloverride;--auth-basicrejected (bearer-only); and three forAccountSelector::Primary(usesprimaryAccounts, falls back to the sole account, errors on ambiguity).-import fastmail --helprenders;import --helplists it next tojmap.README "Sources" entry, adocs/usage.mdsection, and a CHANGELOG[Unreleased]note.Remaining migrate [post] sources (POP3, Zimbra/Zoho) and the reconciliation report are separate items, not in this PR.