Issue Description
Migrating a single-node 0.16.27 Podman deployment (RocksDB, 3 accounts, ~70 emails, 140 contacts) to 1.0.1 with stalwartlabs/stalwart-migrate. The final run fails verification on contact cards in every available version of the tool.
The 1.0.4 changelog lists a matching fix (“Verify no longer reports contact cards whose vCard 3.0 N or ADR has extra trailing components as mismatched”), but 1.0.4 was never released: the tag v1.0.4 exists, yet the Release workflow on 2026-10-29 failed in every Build job (CI Clippy exited with code 101). Docker Hub and GHCR only have up to 1.0.3.
So a 0.16 → 1.0 migration with contacts cannot be finalised right now without --allow-errors. We rolled back to 0.16.27 (the source store is untouched) and are waiting.
Could you:
- publish 1.0.4 (images), and
- confirm that the fix also covers vCard 4.0 cards (ours are 4.0, the changelog says 3.0) and the ADR case where the extra components hold data? For ADR it should be a real difference, not a false positive.
Expected Behavior
run --final verifies the migrated contact cards as equal (they only differ in empty trailing N components) and marks the migration done.
Actual Behavior
run --final fails verification with 140 mismatches, all “contactCard … differs in the target: vcard” in one account, and the final run is not marked done. Same result with stalwart-migrate 1.0.0 and 1.0.3, on a fresh state directory and a fresh target store.
The stored cards are vCard 4.0: all 140 have an N with 7 components (components 6–7 empty); 4 also have an ADR with 18 components, with data beyond component 7.
Reproduction Steps
- Stalwart 0.16.27 (Podman, RocksDB) with an address book of vCard 4.0 contacts whose N has 7 components.
- stalwart-migrate:1.0.3 prepare --non-interactive (all recommended answers), then run: 0 errors.
- Stop 0.16, then: run --final --yes --source /etc/stalwart/config.json --target /etc/stalwart-v1/config.json --state /var/lib/stalwart-migrate --target-path-map /var/lib/stalwart=/var/lib/stalwart-v1
- Verification fails with the contactCard mismatches.
Relevant Log Output
run 1: ok ({"accounts_failed":0,"accounts_full":3,"emails_written":69,"errors":0,"objects_written":250,"registry_written":2832})
verify: 3 accounts checked, 140 mismatches, 140 not explained by earlier reports (failed)
finalize completed but verification failed: the final run is not marked done. Fix the reported mismatches (stalwart-migrate report --severity verify) and run --final again.
$ stalwart-migrate report --severity verify
run severity category account object id message
3 verify mismatch 3 contactCard 9 differs in the target: vcard
3 verify mismatch 3 contactCard 8 differs in the target: vcard
... (140 rows, all contactCard / vcard, account 3)
Stalwart Version
v1.x
Installation Method
Docker
Database Backend
RocksDB
Blob Storage
RocksDB
Search Engine
Internal
Directory Backend
Internal
Additional Context
Tool images tried: stalwartlabs/stalwart-migrate 1.0.0 and 1.0.3 (1.0.3 = latest); target server image stalwartlabs/stalwart:v1.0.1. Podman with Quadlet, Caddy as reverse proxy (http_forwarded answered as xForwardedFor, 1 hop). The data set is small (about 9 MB), so we can re-run the migration quickly once 1.0.4 is available.
I have reviewed the documentation and FAQ and confirm that my issue is NOT addressed there.
on
I have searched this support forum (open and closed topics) and confirm this is not a duplicate.
on
I understand that topics in this category are triaged by a bot first but a human reply will follow up. If I’d prefer a human-only reply, I’ll add the no-ai tag to my topic.
on