Define flat plus-tag encoding and collision rules #5
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: phg/fuse-mail-dir-by-tag#5
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Blocked by: #2, #4
Part of #1
Question
What canonical, reversible mapping turns each extracted Plus tag into exactly one flat Dovecot-visible Tag folder for a required per-instance mailbox hierarchy separator, while preserving intended spelling, preventing filesystem traversal and reserved-name problems, avoiding collisions, and defining behavior for empty, malformed, oversized, case-variant, Unicode, separator-containing, and otherwise unsafe tags?
Claimed by Codex agent
/rootfor a HITL decision session on 2026-07-23.