Refuse an empty JMAP id instead of reading it as id 0 #145
Assignees
jcoffey-dev (John Coffey)
Clear assignees
jcoffey-dev (John Coffey)
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: inbuxa/inbuxa-server#145
Reference in new issue
Block a user
An Email/set with mailboxIds {"": true} was accepted and filed the
message in the Inbox. Id::from_str returned 0 for an empty string, and
document 0 is each collection's first: the Inbox for mail. RFC 8620
§1.2 ids are 1 to 255 characters, so "" is refused now, and every
caller already treats a refused id as invalid or not found.
Over-long ids still parse as they did; upstream's test accepts them on
purpose. Found while probing group mailboxes on a scratch server
(specs/multi-account.md, G3).
types tests, jmap_tests and imap_tests pass (RocksDB).
An Email/set with mailboxIds {"": true} was accepted and filed the message in the Inbox. Id::from_str returned 0 for an empty string, and document 0 is each collection's first: the Inbox for mail. RFC 8620 §1.2 ids are 1 to 255 characters, so "" is refused now, and every caller already treats a refused id as invalid or not found. Over-long ids still parse as they did; upstream's test accepts them on purpose. Found while probing group mailboxes on a scratch server (specs/multi-account.md, G3). types tests, jmap_tests and imap_tests pass (RocksDB).