Repository navigation
Conversation
tobixen
force-pushed
the
test/stalwart-v1
branch
from
November 12, 2026 23:17
1d4bf60 to
c592bd3
Compare
Stalwart v1.0 needs a migration from v0.16, and v1.1 behaves differently: several v0.16 bugs are fixed, a comp-type-less prop-filter search now finds nothing (the stricter reading of RFC 4791), and "@" and "%40" in a path name one resource. Like zimbra, the profile is split into stalwart_0_16 and stalwart_1_1; the old name resolves to stalwart_0_16 with a warning. v1.1 updates its text-search index asynchronously, so stalwart_1_1 asks for a short search-cache delay. The docker setup follows v1's renamed minPasswordStrength, and turns off the MTA inbound throttles: v1.1 delivers local iTIP through them, so after 25 invitations to one user they stall. Prompt: A new version of stalwart is out. Please check if anything needs to be changed in the setup script. Please run the caldav server tester and see if htnts (sic) needs to be changed Followup-Prompt: Perhaps we should do with stalwart like we've done with bedework and zimbra - keep the old version hints but rename it Followup-Prompt: search.text.comp-type-optional failing is not really a regression, a strictly RFC-compliant server should not support it. (...) Assisted-By: Claude Opus 5.5 <noreply@anthropic.com> Reviewed-by: Tobias Brox <tobias@redpill-linpro.com>
tobixen
force-pushed
the
test/stalwart-v1
branch
from
November 12, 2026 23:19
c592bd3 to
f73168b
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Commit message:
Stalwart v1.0 needs a migration from v0.16, and v1.1 behaves
differently: several v0.16 bugs are fixed, a comp-type-less prop-filter
search now finds nothing (the stricter reading of RFC 4791), and "@" and
"%40" in a path name one resource. Like zimbra, the profile is split
into stalwart_0_16 and stalwart_1_1; the old name resolves to
stalwart_0_16 with a warning.
v1.1 updates its text-search index asynchronously, so stalwart_1_1
asks for a short search-cache delay.
The docker setup follows v1's renamed minPasswordStrength, and
turns off the MTA inbound throttles: v1.1 delivers local iTIP
through them, so after 25 invitations to one user they stall.
Prompt: A new version of stalwart is out. Please check if anything needs to be changed in the setup script. Please run the caldav server tester and see if htnts (sic) needs to be changed
Followup-Prompt: Perhaps we should do with stalwart like we've done with bedework and zimbra - keep the old version hints but rename it
Followup-Prompt: search.text.comp-type-optional failing is not really a regression, a strictly RFC-compliant server should not support it. (...)
Assisted-By: Claude Opus 5.5 noreply@anthropic.com
Reviewed-by: Tobias Brox tobias@redpill-linpro.com