Blobs saved but not showing after import

Issues
1

Issue Description

After importing mail to user account using imapsync and/or Thunderbird for imap-to-imap, on some user accounts the entire mails are imported, show the headers in Thunderbird or Nextcloud Mail but the body is not showing. So I assume the blob is not linked properly.
This happens on some accounts, others work, set up practically identical (different user names). New, incoming mail is displayed properly.

Expected Behavior

Show the e-Mail including body and attachments (blob).

Actual Behavior

No error, just the mail not being displayed. On the respective accounts it shows i.e. 3GB data (all mails obviously accounted for), the blob directory grows accordingly, but the mail shows only and exclusively the header (I assume from the postgres-data) but not the mail (I assume the blob data). Blob resides in filesystem.

Reproduction Steps

Used imapsync to move mails from old postfix/dovecot to stalwart.
Upon error, deleted all mails, restarted stalwart. Then used Thunderbird, connecting to old server and stalwart, mark the mails in old server, “move to” selecting stalwart. Same result, only the headers show. Other users work fine.

Two issues. As I deleted all mails and re-“imported” them using another tool with the same result, I guess there is something wrong with either user account or database. Unfortunately I do not really understand where what is filed and how to make sure if I deleted mails that they are properly flushed. Or to repair the links. Unfortunately, both import and repair have been removed from stalwart-cli AFAIK?

How can I either repair or safely delete an account and all links and blobs associated to it, to recreate it from scratch? As I cannot change the mail address, it’s established. I can only make a clean sweep (if I know how) and recreate it from scratch, hoping that fixes any malfunctioning stalwart-internals.

Strong recommendation: If stalwart does not deliver a blob, there must be some log and “screaming” in the system. This happened all quietly, nothing in log, no error, nothing that made me aware until the user called, rather upset, which I can understand.
Second strong recommendation: If stored in file system, it would be good to have a field in postgres to see where the blob resides?

Note. stalwart was installed from installer as per Linux / MacOS | Stalwart

Relevant Log Output

May 18 07:12:15 mindship-syl stalwart[1039163]: IMAP connection started
May 18 07:12:15 mindship-syl stalwart[1039163]: Raw IMAP input received
May 18 07:12:15 mindship-syl stalwart[1039163]: Cache hit
May 18 07:12:15 mindship-syl stalwart[1039163]: Cache hit
May 18 07:12:15 mindship-syl stalwart[1039163]: Cache hit
May 18 07:12:15 mindship-syl stalwart[1039163]: Cache hit
May 18 07:12:15 mindship-syl stalwart[1039163]: Authentication successful
May 18 07:12:15 mindship-syl stalwart[1039163]: Data store iteration operation
May 18 07:12:15 mindship-syl stalwart[1039163]: Cache hit
May 18 07:12:15 mindship-syl stalwart[1039163]: Raw IMAP output sent
May 18 07:12:15 mindship-syl stalwart[1039163]: Raw IMAP input received
May 18 07:12:15 mindship-syl stalwart[1039163]: IMAP ENABLE command
May 18 07:12:15 mindship-syl stalwart[1039163]: Raw IMAP output sent
May 18 07:12:15 mindship-syl stalwart[1039163]: Raw IMAP input received
May 18 07:12:15 mindship-syl stalwart[1039163]: IMAP ID command
May 18 07:12:15 mindship-syl stalwart[1039163]: Raw IMAP output sent
May 18 07:12:15 mindship-syl stalwart[1039163]: Raw IMAP input received
May 18 07:12:15 mindship-syl stalwart[1039163]: IMAP ID command
May 18 07:12:15 mindship-syl stalwart[1039163]: Raw IMAP output sent
May 18 07:12:15 mindship-syl stalwart[1039163]: Raw IMAP input received
May 18 07:12:15 mindship-syl stalwart[1039163]: Cache hit
May 18 07:12:15 mindship-syl stalwart[1039163]: Data store iteration operation
May 18 07:12:15 mindship-syl stalwart[1039163]: Cache hit
May 18 07:12:15 mindship-syl stalwart[1039163]: IMAP STATUS command
May 18 07:12:15 mindship-syl stalwart[1039163]: Raw IMAP output sent
May 18 07:12:15 mindship-syl stalwart[1039163]: Raw IMAP input received
May 18 07:12:15 mindship-syl stalwart[1039163]: IMAP ID command
May 18 07:12:15 mindship-syl stalwart[1039163]: Raw IMAP output sent
May 18 07:12:15 mindship-syl stalwart[1039163]: Raw IMAP input received
May 18 07:12:15 mindship-syl stalwart[1039163]: IMAP ID command
May 18 07:12:15 mindship-syl stalwart[1039163]: Raw IMAP output sent
May 18 07:12:15 mindship-syl stalwart[1039163]: Raw IMAP input received
May 18 07:12:15 mindship-syl stalwart[1039163]: Cache hit
May 18 07:12:15 mindship-syl stalwart[1039163]: Data store iteration operation
May 18 07:12:15 mindship-syl stalwart[1039163]: Cache hit
May 18 07:12:15 mindship-syl stalwart[1039163]: Data store iteration operation
May 18 07:12:15 mindship-syl stalwart[1039163]: Cache hit
May 18 07:12:15 mindship-syl stalwart[1039163]: Data store iteration operation
May 18 07:12:15 mindship-syl stalwart[1039163]: Cache hit
May 18 07:12:15 mindship-syl stalwart[1039163]: Data store iteration operation
May 18 07:12:15 mindship-syl stalwart[1039163]: Data store iteration operation
May 18 07:12:15 mindship-syl stalwart[1039163]: Data store iteration operation
May 18 07:12:15 mindship-syl stalwart[1039163]: Cache hit
May 18 07:12:15 mindship-syl stalwart[1039163]: Raw IMAP output sent
May 18 07:12:15 mindship-syl stalwart[1039163]: IMAP FETCH command
May 18 07:12:15 mindship-syl stalwart[1039163]: IMAP SELECT command
May 18 07:12:15 mindship-syl stalwart[1039163]: Raw IMAP output sent
May 18 07:12:15 mindship-syl stalwart[1039163]: Raw IMAP input received
May 18 07:12:15 mindship-syl stalwart[1039163]: IMAP ID command
May 18 07:12:15 mindship-syl stalwart[1039163]: Raw IMAP output sent
May 18 07:12:15 mindship-syl stalwart[1039163]: Raw IMAP input received
May 18 07:12:15 mindship-syl stalwart[1039163]: IMAP ID command
May 18 07:12:15 mindship-syl stalwart[1039163]: Raw IMAP output sent
May 18 07:12:16 mindship-syl stalwart[1039163]: Raw IMAP input received
May 18 07:12:16 mindship-syl stalwart[1039163]: IMAP ID command
May 18 07:12:16 mindship-syl stalwart[1039163]: Raw IMAP output sent
May 18 07:12:16 mindship-syl stalwart[1039163]: Raw IMAP input received
May 18 07:12:16 mindship-syl stalwart[1039163]: IMAP ID command
May 18 07:12:16 mindship-syl stalwart[1039163]: Raw IMAP output sent
May 18 07:12:16 mindship-syl stalwart[1039163]: Raw IMAP input received
May 18 07:12:16 mindship-syl stalwart[1039163]: IMAP ID command
May 18 07:12:16 mindship-syl stalwart[1039163]: Raw IMAP output sent
May 18 07:12:16 mindship-syl stalwart[1039163]: Raw IMAP input received
May 18 07:12:16 mindship-syl stalwart[1039163]: Data store iteration operation
May 18 07:12:16 mindship-syl stalwart[1039163]: Cache hit
May 18 07:12:16 mindship-syl stalwart[1039163]: Data store iteration operation
May 18 07:12:16 mindship-syl stalwart[1039163]: Cache hit
May 18 07:12:16 mindship-syl stalwart[1039163]: Raw IMAP output sent
May 18 07:12:16 mindship-syl stalwart[1039163]: IMAP FETCH command
May 18 07:12:16 mindship-syl stalwart[1039163]: Raw IMAP output sent
May 18 07:12:16 mindship-syl stalwart[1039163]: Raw IMAP input received
May 18 07:12:16 mindship-syl stalwart[1039163]: IMAP ID command
May 18 07:12:16 mindship-syl stalwart[1039163]: Raw IMAP output sent
May 18 07:12:16 mindship-syl stalwart[1039163]: Raw IMAP input received
May 18 07:12:16 mindship-syl stalwart[1039163]: IMAP ID command
May 18 07:12:16 mindship-syl stalwart[1039163]: Raw IMAP output sent
May 18 07:12:16 mindship-syl stalwart[1039163]: Raw IMAP input received
May 18 07:12:16 mindship-syl stalwart[1039163]: IMAP ID command
May 18 07:12:16 mindship-syl stalwart[1039163]: Raw IMAP output sent
May 18 07:12:16 mindship-syl stalwart[1039163]: Raw IMAP input received
May 18 07:12:16 mindship-syl stalwart[1039163]: Cache hit
May 18 07:12:16 mindship-syl stalwart[1039163]: Data store iteration operation
May 18 07:12:16 mindship-syl stalwart[1039163]: Cache hit
May 18 07:12:16 mindship-syl stalwart[1039163]: Data store iteration operation
May 18 07:12:16 mindship-syl stalwart[1039163]: Cache hit
May 18 07:12:16 mindship-syl stalwart[1039163]: Data store iteration operation
May 18 07:12:16 mindship-syl stalwart[1039163]: Cache hit
May 18 07:12:16 mindship-syl stalwart[1039163]: Data store iteration operation
May 18 07:12:16 mindship-syl stalwart[1039163]: Data store iteration operation
May 18 07:12:16 mindship-syl stalwart[1039163]: Data store iteration operation
May 18 07:12:16 mindship-syl stalwart[1039163]: Cache hit
May 18 07:12:16 mindship-syl stalwart[1039163]: Raw IMAP output sent
May 18 07:12:16 mindship-syl stalwart[1039163]: IMAP FETCH command
May 18 07:12:16 mindship-syl stalwart[1039163]: IMAP SELECT command
May 18 07:12:16 mindship-syl stalwart[1039163]: Raw IMAP output sent
May 18 07:12:16 mindship-syl stalwart[1039163]: Raw IMAP input received
May 18 07:12:16 mindship-syl stalwart[1039163]: IMAP ID command
May 18 07:12:16 mindship-syl stalwart[1039163]: Raw IMAP output sent
May 18 07:12:16 mindship-syl stalwart[1039163]: Raw IMAP input received
May 18 07:12:16 mindship-syl stalwart[1039163]: IMAP ID command
May 18 07:12:16 mindship-syl stalwart[1039163]: Raw IMAP output sent
May 18 07:12:16 mindship-syl stalwart[1039163]: Raw IMAP input received
May 18 07:12:16 mindship-syl stalwart[1039163]: IMAP ID command
May 18 07:12:16 mindship-syl stalwart[1039163]: Raw IMAP output sent
May 18 07:12:16 mindship-syl stalwart[1039163]: Raw IMAP input received
May 18 07:12:16 mindship-syl stalwart[1039163]: IMAP ID command
May 18 07:12:16 mindship-syl stalwart[1039163]: Raw IMAP output sent
May 18 07:12:16 mindship-syl stalwart[1039163]: Raw IMAP input received
May 18 07:12:16 mindship-syl stalwart[1039163]: IMAP ID command
May 18 07:12:16 mindship-syl stalwart[1039163]: Raw IMAP output sent
May 18 07:12:16 mindship-syl stalwart[1039163]: Raw IMAP input received
May 18 07:12:16 mindship-syl stalwart[1039163]: IMAP ID command
May 18 07:12:16 mindship-syl stalwart[1039163]: Raw IMAP output sent
May 18 07:12:16 mindship-syl stalwart[1039163]: Raw IMAP input received
May 18 07:12:16 mindship-syl stalwart[1039163]: IMAP ID command
May 18 07:12:16 mindship-syl stalwart[1039163]: Raw IMAP output sent
May 18 07:12:16 mindship-syl stalwart[1039163]: Raw IMAP input received
May 18 07:12:16 mindship-syl stalwart[1039163]: Data store iteration operation
May 18 07:12:16 mindship-syl stalwart[1039163]: Cache hit
May 18 07:12:16 mindship-syl stalwart[1039163]: IMAP SEARCH command
May 18 07:12:16 mindship-syl stalwart[1039163]: Raw IMAP output sent
May 18 07:12:16 mindship-syl stalwart[1039163]: Raw IMAP input received
May 18 07:12:16 mindship-syl stalwart[1039163]: IMAP LOGOUT command
May 18 07:12:16 mindship-syl stalwart[1039163]: Raw IMAP output sent
May 18 07:12:16 mindship-syl stalwart[1039163]: IMAP connection ended

Stalwart Version

v0.16.x

Installation Method

Binary (Linux)

Database Backend

PostgreSQL

Blob Storage

Filesystem

Search Engine

Internal

Directory Backend

Internal

Additional Context

Rocky Linux 10.1, I searched for assistance and ideas before raising the issue. If duplicate I apologize and appreciate a link. Else I hope for information how to resolve this quickly. Server is a commercial Hetzner with 80GB + 1TB storage box used for the blob storage.

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

2

Based on my research, here is what the documentation covers for your situation:

The symptoms – headers visible but body blank – point to blob references in the database that don’t resolve to actual blob content on the filesystem. This can happen when a prior partial delete leaves orphaned or stale references. The two key tools available through the task system are:

1. Clean up the affected account completely

The DestroyAccount task permanently deletes an account and all data associated with it (mailbox records in PostgreSQL and blob references). You can create it via the WebUI (Management › Tasks) or via stalwart-cli:

stalwart-cli create task/DestroyAccount \
  --field 'accountName=<username>' \
  --field 'accountDomainId=<domain-id>'

After that, recreate the account from scratch and re-import. Because blobs are content-addressed (BLAKE3 hash), any blobs already physically on disk for those messages will be correctly re-linked when new IMAP APPEND operations write them.

2. Per-account maintenance after re-import

The AccountMaintenance task supports recalculateImapUid and recalculateQuota operations, which can fix IMAP UID inconsistencies after bulk imports:

stalwart-cli create task/AccountMaintenance \
  --field 'accountId=<account-id>' \
  --field 'maintenanceType=recalculateImapUid'

3. Purge orphaned blobs store-wide

To clean up any orphaned blobs left over from deleted messages:

stalwart-cli create task/StoreMaintenance \
  --field 'maintenanceType=purgeBlob'

On the “no logging” concern: the log output you shared is at debug level and shows only IMAP protocol events. If you increase the log level to trace or enable store.unexpected-error event logging, failed blob fetches should surface. That said, whether a missing-blob retrieval failure is logged as an error today is something a human can better confirm.

On the “field in postgres for blob location”: Stalwart’s blob store is intentionally abstracted – all blobs are addressed by content hash (BLAKE3), not by path. The filesystem path is deterministically derived from that hash; there is no separate pointer column in the database.

Relevant docs:

This is an automated reply from the Stalwart Help Bot. Other community members may follow up if this answer is incomplete or wrong. If you found it useful, mention @helpbot in any reply to ask follow-up questions and the bot will respond again.

3

[root@mindship-syl juergen]# /usr/local/bin/stalwart-cli create task/DestroyAccount --field ‘accountName=susanne’ --field ‘accountDomainId=herdomain.eu’
error: no URL provided (use --url or STALWART_URL)
[root@mindship-syl juergen]#

Wow. Simply. Wow.
Tried also username with the domain. Wondered why it did not work to create in the WebUI, seems something is off here.

Interesting that I find in Management Tasks a lot of “Index” failures.
“Failed to index documents”. Showing 1-25 of 1508 failed tasks
Now I checked Mails that transferred to stalwart without error and trying to access them through Nextcloud the messages bodies do not load! “Loading messages …” under a rotating circle.
Looked through some other “Failed Tasks”, finding
“Record not found in database (store.not-found): details = Blob not found” for the account having trouble.

I am sorry, I am new to stalwart, but it is quite frustrating that there is little to no structure that allows me my local debugging. Like “which message” is involved. Asked for adding in postgres a field at least to the blob-folder, to learn it’s encoded. Doesn’t help me to debug either. That ain’t “security by obscurity” but making it a black box for a normal admin. I did not ever had such trouble debugging Postfix, I am considering a switch back. Not as I dislike stalwart, but if it a. does swallow blobs without screaming error at the admin, it is not a save message store but a black hole, not just a black box. And if I get advise that creates errors, your AI RAG needs more updating to 0.16.x - I guess the response is a <=0.15 answer?

I also asked for advise on import, as the page Google refers to is outdated (Error 404), only to learn from own research that the “import” in stalwart-cli got discontinued. But imap-to-imap fails, so how can I move safe to stalwart?
And how can I safely delete the corrupted account username@domain?

ANY help truly appreciated, as I’d like to keep stalwart, but need to make sure it’s a reliable tool. As is, it keeps me busy for too many days as it is already and I have trouble debugging the issue?

4

Here are clear answers to each of your problems:

Fix 1: The stalwart-cli requires --url and credentials on every call. The error you got is simply because the CLI doesn’t know where your server is. You must always include the server address and admin credentials:

stalwart-cli --url https://mail.yourdomain.com \
  --user admin --password 'yourpassword' \
  create task/DestroyAccount \
  --field 'accountName=susanne' \
  --field 'accountDomainId=herdomain.eu'

Or set environment variables so you don’t have to repeat them every time:

export STALWART_URL=https://mail.yourdomain.com
export STALWART_USER=admin
export STALWART_PASSWORD='yourpassword'

stalwart-cli create task/DestroyAccount \
  --field 'accountName=susanne' \
  --field 'accountDomainId=herdomain.eu'

If your TLS certificate is self-signed or internal, add --insecure / -k. These connection flags go in the same environment variable form shown above. See the CLI docs.

Fix 2: “Failed to index documents” / “Blob not found” – these 1,508 failures are the root cause. The blobs were written to the filesystem during IMAP import, but the indexing tasks that link them into the search/retrieval layer failed and exhausted their retry budget. This is why headers show but bodies don’t – the metadata record exists in PostgreSQL but the blob reference was never fully committed. This is a real bug/data integrity issue that a human staff member should confirm.

Recommended immediate steps:

  1. Destroy the corrupted account using the CLI command above (with --url added).
  2. Recreate the account fresh in the WebUI.
  3. Run a blob store purge to clean up orphaned blobs from the failed import:
    stalwart-cli create task/StoreMaintenance \
  --field 'maintenanceType=purgeBlob'
  4. Re-import mail – but see the note on failed indexing below. The 1,508 failed index tasks suggest something in the indexing pipeline may be unhealthy. Check Management › Tasks › Failed for the specific error details on those tasks to see if there is a pattern (same account? same time window?).

On the WebUI task creation: The Tasks section in Management should allow creating tasks directly. If you’re seeing that fail too, it would help a human to know the exact error shown in the UI.

On IMAP import reliability: The stalwart-cli import subcommand was removed. IMAP-to-IMAP via tools like imapsync is the supported path, but the 1,508 indexing failures suggest something went wrong server-side during ingestion – this warrants a human look, as it may indicate a resource exhaustion (disk, memory, DB connection pool) issue during the bulk import rather than a Stalwart bug per se.

Docs used:

This is an automated reply from the Stalwart Help Bot. Other community members may follow up if this answer is incomplete or wrong. If you found it useful, mention @helpbot in any reply to ask follow-up questions and the bot will respond again.

5

The log lines you posted are event types without parameters, which doesn’t tell us whether the body bytes are missing in the blob store, whether the message metadata points at a hash that isn’t there, or whether the client is asking for a body part the server is declining. A few specific things would help.

Reproduce against one affected account with debug-level (or trace-level) tracing for the IMAP and Store event groups; capture the events for one full FETCH cycle and share the BlobRead, BlobNotFound and MetadataFetch lines with their parameters. You can also run a raw BODY[] FETCH against one affected message with openssl s_client (or curl --url 'imaps://...') to see whether the server returns an empty body or only headers.

Did the affected accounts have mail in 0.15 that survived the upgrade, or are they fresh accounts in a fresh 0.16 install? And is your BlobStore configured for filesystem, S3, or “Default” (data store)?

6

[root@mindship-syl juergen]# /usr/local/bin/stalwart-cli --url https://mx.barthel.eu --user admin --password ‘[secret]’ create task/DestroyAccount --field ‘accountName=susanne’ --field ‘accountDomainId=barthel.eu’
error: invalidPatch
Failed to parse Id from string
Properties: accountDomainId
error: create failed
[root@mindship-syl juergen]#
How can I clean all account information. Restarting stalwart didn’t do the trick. I also tried deleting the user, restarting - recreating, the mailbox is empty. As soon as I copy the mails, the ones that backed up from stalwart before deletion propagate properly, the ones that came with an empty body (blob error) come again with the same problem.

7

I have trace set in journalctl.
I guess the only thing I see is
May 19 20:40:21 mindship-syl stalwart[1118288]: Record not found in database
But I cannot upload the log file (too big).
I created a different account to use alias later, but same issue:
May 19 20:55:21 mindship-syl stalwart[1118288]: Raw IMAP input received
May 19 20:55:21 mindship-syl stalwart[1118288]: Raw IMAP input received
May 19 20:55:21 mindship-syl stalwart[1118288]: Raw IMAP input received
May 19 20:55:21 mindship-syl stalwart[1118288]: Raw IMAP input received
May 19 20:55:21 mindship-syl stalwart[1118288]: Raw IMAP input received
May 19 20:55:21 mindship-syl stalwart[1118288]: Raw IMAP input received
May 19 20:55:21 mindship-syl stalwart[1118288]: Raw IMAP input received
May 19 20:55:21 mindship-syl stalwart[1118288]: Raw IMAP input received
May 19 20:55:21 mindship-syl stalwart[1118288]: Cache hit
May 19 20:55:21 mindship-syl stalwart[1118288]: Data store iteration operation
May 19 20:55:21 mindship-syl stalwart[1118288]: Cache hit
May 19 20:55:21 mindship-syl stalwart[1118288]: Cache hit
May 19 20:55:21 mindship-syl stalwart[1118288]: Cache hit
May 19 20:55:21 mindship-syl stalwart[1118288]: Cache hit
May 19 20:55:21 mindship-syl stalwart[1118288]: Data store iteration operation
May 19 20:55:21 mindship-syl stalwart[1118288]: Write batch operation
May 19 20:55:21 mindship-syl stalwart[1118288]: Write batch operation
May 19 20:55:21 mindship-syl stalwart[1118288]: Write batch operation
May 19 20:55:21 mindship-syl stalwart[1118288]: Message appended via IMAP
May 19 20:55:21 mindship-syl stalwart[1118288]: IMAP APPEND command
May 19 20:55:21 mindship-syl stalwart[1118288]: Raw IMAP output sent
May 19 20:55:21 mindship-syl stalwart[1118288]: Data store iteration operation
May 19 20:55:21 mindship-syl stalwart[1118288]: Task acquired from queue
May 19 20:55:21 mindship-syl stalwart[1118288]: Write batch operation
May 19 20:55:21 mindship-syl stalwart[1118288]: Data store iteration operation
May 19 20:55:21 mindship-syl stalwart[1118288]: Write batch operation
May 19 20:55:21 mindship-syl stalwart[1118288]: Write batch operation
May 19 20:55:21 mindship-syl stalwart[1118288]: Write batch operation
May 19 20:55:21 mindship-syl stalwart[1118288]: Data store iteration operation
May 19 20:55:21 mindship-syl stalwart[1118288]: Blob read operation
May 19 20:55:21 mindship-syl stalwart[1118288]: Record not found in database
May 19 20:55:21 mindship-syl stalwart[1118288]: Task will be retried
May 19 20:55:21 mindship-syl stalwart[1118288]: Write batch operation
May 19 20:55:21 mindship-syl stalwart[1118288]: Write batch operation
May 19 20:55:21 mindship-syl stalwart[1118288]: Data store iteration operation
May 19 20:55:21 mindship-syl stalwart[1118288]: IMAP connection started
May 19 20:55:21 mindship-syl stalwart[1118288]: Raw IMAP input received
May 19 20:55:21 mindship-syl stalwart[1118288]: Raw IMAP output sent
May 19 20:55:21 mindship-syl stalwart[1118288]: Raw IMAP input received
May 19 20:55:21 mindship-syl stalwart[1118288]: Cache hit
May 19 20:55:21 mindship-syl stalwart[1118288]: Cache hit
May 19 20:55:21 mindship-syl stalwart[1118288]: Cache hit
May 19 20:55:21 mindship-syl stalwart[1118288]: Cache hit
May 19 20:55:21 mindship-syl stalwart[1118288]: Authentication successful
May 19 20:55:21 mindship-syl stalwart[1118288]: Data store iteration operation
May 19 20:55:21 mindship-syl stalwart[1118288]: Cache update
May 19 20:55:21 mindship-syl stalwart[1118288]: Raw IMAP output sent
May 19 20:55:21 mindship-syl stalwart[1118288]: Raw IMAP input received
May 19 20:55:21 mindship-syl stalwart[1118288]: IMAP ID command
May 19 20:55:21 mindship-syl stalwart[1118288]: Raw IMAP output sent
May 19 20:55:21 mindship-syl stalwart[1118288]: Raw IMAP input received
May 19 20:55:21 mindship-syl stalwart[1118288]: IMAP ENABLE command
May 19 20:55:21 mindship-syl stalwart[1118288]: Raw IMAP output sent
May 19 20:55:21 mindship-syl stalwart[1118288]: Raw IMAP input received
May 19 20:55:21 mindship-syl stalwart[1118288]: Cache hit
May 19 20:55:21 mindship-syl stalwart[1118288]: Data store iteration operation
May 19 20:55:21 mindship-syl stalwart[1118288]: Cache hit
May 19 20:55:21 mindship-syl stalwart[1118288]: Data store iteration operation
May 19 20:55:21 mindship-syl stalwart[1118288]: Cache hit
May 19 20:55:21 mindship-syl stalwart[1118288]: IMAP SELECT command
May 19 20:55:21 mindship-syl stalwart[1118288]: Raw IMAP output sent
May 19 20:55:21 mindship-syl stalwart[1118288]: Raw IMAP input received
May 19 20:55:21 mindship-syl stalwart[1118288]: Cache hit
May 19 20:55:21 mindship-syl stalwart[1118288]: Data store iteration operation
May 19 20:55:21 mindship-syl stalwart[1118288]: Cache hit
May 19 20:55:21 mindship-syl stalwart[1118288]: Cache hit
May 19 20:55:21 mindship-syl stalwart[1118288]: IMAP GETQUOTA command
May 19 20:55:21 mindship-syl stalwart[1118288]: Raw IMAP output sent
May 19 20:55:21 mindship-syl stalwart[1118288]: Raw IMAP input received
May 19 20:55:21 mindship-syl stalwart[1118288]: Data store iteration operation
May 19 20:55:21 mindship-syl stalwart[1118288]: Cache hit
May 19 20:55:21 mindship-syl stalwart[1118288]: Data store iteration operation
May 19 20:55:21 mindship-syl stalwart[1118288]: Cache hit
May 19 20:55:21 mindship-syl stalwart[1118288]: Raw IMAP output sent
May 19 20:55:21 mindship-syl stalwart[1118288]: IMAP FETCH command
May 19 20:55:21 mindship-syl stalwart[1118288]: Raw IMAP output sent
May 19 20:55:22 mindship-syl stalwart[1118288]: Raw IMAP input received
May 19 20:55:22 mindship-syl stalwart[1118288]: Data store iteration operation
May 19 20:55:22 mindship-syl stalwart[1118288]: Cache hit
May 19 20:55:22 mindship-syl stalwart[1118288]: Data store iteration operation
May 19 20:55:22 mindship-syl stalwart[1118288]: Cache hit
May 19 20:55:22 mindship-syl stalwart[1118288]: Raw IMAP output sent
May 19 20:55:22 mindship-syl stalwart[1118288]: IMAP FETCH command
May 19 20:55:22 mindship-syl stalwart[1118288]: Raw IMAP output sent
May 19 20:55:22 mindship-syl stalwart[1118288]: Raw IMAP input received
May 19 20:55:22 mindship-syl stalwart[1118288]: Data store iteration operation
May 19 20:55:22 mindship-syl stalwart[1118288]: Cache hit
May 19 20:55:22 mindship-syl stalwart[1118288]: Data store iteration operation
May 19 20:55:22 mindship-syl stalwart[1118288]: Cache hit
May 19 20:55:22 mindship-syl stalwart[1118288]: Blob read operation
May 19 20:55:22 mindship-syl stalwart[1118288]: Record not found in database
May 19 20:55:22 mindship-syl stalwart[1118288]: IMAP FETCH command
May 19 20:55:22 mindship-syl stalwart[1118288]: Raw IMAP output sent
May 19 20:55:22 mindship-syl stalwart[1118288]: Raw IMAP input received
May 19 20:55:22 mindship-syl stalwart[1118288]: Data store iteration operation
May 19 20:55:22 mindship-syl stalwart[1118288]: Cache hit
May 19 20:55:22 mindship-syl stalwart[1118288]: IMAP NOOP command
May 19 20:55:22 mindship-syl stalwart[1118288]: Raw IMAP output sent
May 19 20:55:22 mindship-syl stalwart[1118288]: Task scheduled for future execution
May 19 20:55:22 mindship-syl stalwart[1118288]: Metrics collected
May 19 20:55:24 mindship-syl stalwart[1118288]: Raw IMAP input received
May 19 20:55:24 mindship-syl stalwart[1118288]: Raw IMAP output sent
May 19 20:55:24 mindship-syl stalwart[1118288]: IMAP IDLE start
May 19 20:55:33 mindship-syl stalwart[1118288]: IMAP IDLE stop
May 19 20:55:33 mindship-syl stalwart[1118288]: Raw IMAP output sent
May 19 20:55:33 mindship-syl stalwart[1118288]: Raw IMAP input received
May 19 20:55:33 mindship-syl stalwart[1118288]: Raw IMAP input received
May 19 20:55:33 mindship-syl stalwart[1118288]: Data store iteration operation
May 19 20:55:33 mindship-syl stalwart[1118288]: Cache hit
May 19 20:55:33 mindship-syl stalwart[1118288]: IMAP NOOP command
May 19 20:55:33 mindship-syl stalwart[1118288]: Raw IMAP output sent
May 19 20:55:33 mindship-syl stalwart[1118288]: Raw IMAP input received
May 19 20:55:33 mindship-syl stalwart[1118288]: Cache hit
May 19 20:55:33 mindship-syl stalwart[1118288]: Data store iteration operation
May 19 20:55:33 mindship-syl stalwart[1118288]: Cache hit
May 19 20:55:33 mindship-syl stalwart[1118288]: Cache hit
May 19 20:55:33 mindship-syl stalwart[1118288]: IMAP GETQUOTA command
May 19 20:55:33 mindship-syl stalwart[1118288]: Raw IMAP output sent
May 19 20:55:33 mindship-syl stalwart[1118288]: Raw IMAP input received
May 19 20:55:33 mindship-syl stalwart[1118288]: Data store iteration operation
May 19 20:55:33 mindship-syl stalwart[1118288]: Cache hit
May 19 20:55:33 mindship-syl stalwart[1118288]: Data store iteration operation
May 19 20:55:33 mindship-syl stalwart[1118288]: Cache hit
May 19 20:55:33 mindship-syl stalwart[1118288]: Raw IMAP output sent
May 19 20:55:33 mindship-syl stalwart[1118288]: IMAP FETCH command
May 19 20:55:33 mindship-syl stalwart[1118288]: Raw IMAP output sent
May 19 20:55:34 mindship-syl stalwart[1118288]: Raw IMAP input received
May 19 20:55:34 mindship-syl stalwart[1118288]: Data store iteration operation
May 19 20:55:34 mindship-syl stalwart[1118288]: Cache hit
May 19 20:55:34 mindship-syl stalwart[1118288]: Data store iteration operation
May 19 20:55:34 mindship-syl stalwart[1118288]: Cache hit
May 19 20:55:34 mindship-syl stalwart[1118288]: Blob read operation
May 19 20:55:34 mindship-syl stalwart[1118288]: Record not found in database
May 19 20:55:34 mindship-syl stalwart[1118288]: IMAP FETCH command
May 19 20:55:34 mindship-syl stalwart[1118288]: Raw IMAP output sent
May 19 20:55:34 mindship-syl stalwart[1118288]: IMAP IDLE stop
May 19 20:55:34 mindship-syl stalwart[1118288]: Raw IMAP output sent
May 19 20:55:34 mindship-syl stalwart[1118288]: Raw IMAP input received
May 19 20:55:34 mindship-syl stalwart[1118288]: Raw IMAP output sent
May 19 20:55:34 mindship-syl stalwart[1118288]: IMAP IDLE start
May 19 20:55:35 mindship-syl stalwart[1118288]: Raw IMAP input received
May 19 20:55:35 mindship-syl stalwart[1118288]: Data store iteration operation
May 19 20:55:35 mindship-syl stalwart[1118288]: Cache hit
May 19 20:55:35 mindship-syl stalwart[1118288]: Data store iteration operation
May 19 20:55:35 mindship-syl stalwart[1118288]: Cache hit
May 19 20:55:35 mindship-syl stalwart[1118288]: Blob read operation
May 19 20:55:35 mindship-syl stalwart[1118288]: Record not found in database
May 19 20:55:35 mindship-syl stalwart[1118288]: IMAP FETCH command
May 19 20:55:35 mindship-syl stalwart[1118288]: Raw IMAP output sent
May 19 20:55:37 mindship-syl stalwart[1118288]: Raw IMAP input received
May 19 20:55:37 mindship-syl stalwart[1118288]: Raw IMAP output sent
May 19 20:55:37 mindship-syl stalwart[1118288]: IMAP IDLE start
[root@mindship-syl juergen]#

10

SOLVED. For the case. For anyone having the same problem.
Used Thunderbird. Copy the messages to “Local Folder”, then copy to stalwart. Do not move, it seems to work differently. So yes, I had and have to replicate tons of folders and copy/copy/delete/delete them “manually” one by one, but at least that way stalwart does get the blob properly allocated. And no, I have no idea why that problem exists. But with no help here, the workaround is better than nothing.