Skip to content

chore: purelymail accepts a never-issued token - #771

Merged
tobixen merged 2 commits into
masterfrom
chore/purelymail-invalid-token-hint
Oct 14, 2026
Merged

tobixen merged 2 commits into
masterfrom
chore/purelymail-invalid-token-hint

Conversation

@tobixen

@tobixen tobixen commented Oct 14, 2026

Copy link
Copy Markdown
Member

Follow-up to #770: purelymail's first complete compatibility run - possible once the caldav-server-tester stops sleeping before every search (its branch fix/purelymail-delay-only-filtered, PR to follow) - asked for one more hint. The second commit clarifies a comment, from the review.

  • chore: purelymail accepts a never-issued token
  • docs: name the Calendar.search wrap it relies on (purelymails search-cache logic)

🤖 Generated with Claude Code

The sync-token.invalid-token probe came after the purelymail profile,
whose compatibility run did not finish before.  With the server tester
no longer sleeping before every search it does: purelymail answers a
token it never issued with a report and no error, like Stalwart.

Prompt: Yes to both [add the purelymail sync-token.invalid-token hint that its first complete compatibility run asked for, and review-and-push the tester fix]

Assisted-By: Claude Opus 5.5 <noreply@anthropic.com>
Reviewed-by: Tobias Brox <tobias@redpill-linpro.com>
The comment in get_object_by_uid() said a search-cache delay patches
Calendar.search; the caldav-server-tester now wraps CalDAVSearcher
instead, so it names the wrap that still does it, in
tests/test_caldav.py.

Prompt: [fix issues found during the review process]

Assisted-By: Claude Opus 5.5 <noreply@anthropic.com>
Reviewed-by: Tobias Brox <tobias@redpill-linpro.com>
@tobixen
tobixen merged commit 5dfa039 into master Oct 14, 2026
17 checks passed
@tobixen
tobixen deleted the chore/purelymail-invalid-token-hint branch October 14, 2026 16:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant