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.