Export: match a message the target holds under its own key #87

Merged
jcoffey-dev merged 2 commits from fix/export-parse-rematch into main 2026-11-17 15:50:32 +00:00
2 Commits
Author SHA1 Message Date
jcoffey-dev 28e9ae1d58 Merge remote-tracking branch 'origin/main' into fix/export-parse-rematch
ci / test (pull_request) Skipped
github/ci (branch) GitHub Actions
ci / github (pull_request) Successful in 5m32s
ci / announce (pull_request) Skipped
# Conflicts:
#	CHANGELOG.md
2026-11-17 08:43:06 -07:00
jcoffey-dev 34981475f2 Export: match a message the target holds under its own key
ci / test (pull_request) Skipped
github/ci (branch) GitHub Actions
ci / github (pull_request) Successful in 3m37s
ci / announce (pull_request) Skipped
A message with two Message-ID headers is keyed by both in the archive,
while a JMAP server's messageId reflects one, so export never paired it
and imported it again on every run (shown live on inbuxa 27.1-rc.4).

While target emails are left unpaired, a batch about to be imported is
parsed by the target first (Email/parse) and each message it already
holds under that key is matched, with its keywords and folders synced
like any other match. A target that refuses Email/parse is not asked
again; any other failure leaves that batch unchecked, imported as before.
The parsed key also settles an import that ended without a clear answer.

Upstream fixed the same case in v1.0.17 (#86); written here on our own
code and tests.
2026-11-16 23:52:18 -07:00