stalwartlabs/stalwart · error

Server::ThreadError

Error message

Server::ThreadError

What it means

An internal trc::Error with EventType::Server(ServerEvent::ThreadError) raised in `send_imip` (crates/services/src/task_manager/imip.rs) when the spawned async task/job fails — the `.await` on the task join returns Err and is mapped to this event. It signals the iMIP (email-based scheduling) send worker could not complete, not a message-level failure.

Source

Thrown at crates/services/src/task_manager/imip.rs:301

                        QueueId = queue_id,
                    );
                } else {
                    trc::event!(
                        Calendar(trc::CalendarEvent::ItipMessageError),
                        From = from,
                        To = to,
                        AccountId = account_id,
                        DocumentId = document_id,
                        Reason = format!(
                            "Server rejected DATA: {}",
                            std::str::from_utf8(&response).unwrap().trim()
                        ),
                    );
                }
            })
            .await
            .map_err(|_| {
                trc::Error::new(trc::EventType::Server(trc::ServerEvent::ThreadError))
                    .caused_by(trc::location!())
            })?;
        }
    }

    Ok(TaskResult::Success(vec![]))
}

pub struct Details {
    pub subject: String,
    pub body: String,
}

#[allow(clippy::too_many_arguments)]
pub async fn build_itip_template(
    server: &Server,
    account_info: &AccountInfo,
    account_id: u32,

View on GitHub (pinned to e962003857)

Solutions

1. Look up the server logs for the ThreadError entry and the `caused_by` location to find the underlying task failure.
2. Re-run/queue the affected iMIP messages — the scheduling messages were not confirmed delivered.
3. Fix the panic or resource issue inside the spawned delivery task (e.g. mail server connectivity, worker pool sizing).

// at the task_manager call site
match send_imip(&mut core, &account_id, &messages).await {
    Err(err) if err.is_server_thread_error() => {
        tracing::error!(?err, "iMIP send task failed; requeueing messages");
        requeue(messages);
    }
    other => other?,
}

When it happens

Trigger: `send_imip` spawns a task (e.g. via a task queue/join handle) to deliver iMIP messages; the awaited result errors (task panicked, was cancelled, or the worker failed), and `map_err` converts it into Server::ThreadError with `trc::location!()` context.

Common situations: Mail delivery worker crashes under load; runtime shutdown/cancellation kills the spawned task mid-send; a panic inside the per-message delivery closure; thread pool exhaustion.

Understand the failure class

Background: "This is a bug, please report it": internal invariant violations, unreachable panics, and SNH errors explained — this error's family across 47 libraries.

Related errors

• Sieve test failed: {}

AI-assisted analysis of stalwartlabs/stalwart@e962003857 (2026-09-06). Data as JSON: /api/errors/44cead294505a75f. Report an issue: GitHub.