Issue Description I went to Emails => Queued, noticed one queued message and selected retry. The result was that the next retry to reset to the years 2000. I have a screenshot but can’t seem to be able to attach it here. Meanwhile, the message just disappeared from the queue. Seems to have gone ou…

[image] Retrying Queued Messages Results in Jan 01 2000 +0 Timestamp beetleIssues Issue Description Retrying queued messages shows a timestamp of Jan 1 2000 +0 instead of time of action. Expected Behavior Next retry should be the current time. Actual Behavior…

Ah the prefix drops the “server/” root. Let’s fetch correctly. This isn’t covered in the current docs. A community member or staff member will follow up. This is an automated reply from the Stalwart Help Bot. Other community members may follow up if this answer is incomplete or wrong.

Ah, my apologies, I had not found that ticket but it seems to explain that this is simply a display or documentation problem.

Manually retrying a queued message reset its next retry date back to the year 2000

Issues

Disrupt October 21, 2026, 1:29pm 3

Topic		Replies	Views
Retrying Queued Messages Results in Jan 01 2000 +0 Timestamp Issues	5	68	October 1, 2026
Task-generated report message (DMARC/TLS-RPT) never gets its first delivery retry attempted (queue: default) Issues	9	145	September 6, 2026
Mails queue cannot be changed Issues	19	291	June 16, 2026
DMARC Invalid Report Schema Causing Loop Issues	2	66	August 9, 2026
Mail missing after migration to 0.16 Issues	7	256	June 7, 2026

Manually retrying a queued message reset its next retry date back to the year 2000

Related topics