mox/imapserver
Mechiel Lukkien 142b2498bf
fix two parsing bugs in imapserver
these could cause the parser to reject correct commands.

the first bug is about the allowed chars for an "atom", we were accepting too
many. this probably isn't easily triggered in practice.

the second bug is about how numbers (digits) are parsed. when gathering digits
to parse as number, we didn't consider only the directly upcoming digits that
make up the number, but continued looking for digits later on in the command.
then we tried to parse a string that was too long as a number, which would fail
because of additional characters. this could have been triggered with commands
containing two numbers. this is possible with e.g. "tag search or larger 123
smaller 123", the "or" takes two search keys again, each with a number. not too
common, but can happen.

found while writing tests for upcoming condstore/qresync implementation.
2023-06-28 19:41:58 +02:00
..
2023-02-11 23:00:12 +01:00
2023-01-30 14:27:06 +01:00
2023-01-30 14:27:06 +01:00
2023-01-30 14:27:06 +01:00
2023-01-30 14:27:06 +01:00
2023-01-30 14:27:06 +01:00
2023-01-30 14:27:06 +01:00
2023-01-30 14:27:06 +01:00
2023-01-30 14:27:06 +01:00
2023-06-28 19:41:58 +02:00
2023-01-30 14:27:06 +01:00
2023-01-30 14:27:06 +01:00
2023-01-30 14:27:06 +01:00
2023-01-30 14:27:06 +01:00
2023-01-30 14:27:06 +01:00
2023-01-30 14:27:06 +01:00
2023-01-30 14:27:06 +01:00
2023-01-30 14:27:06 +01:00
2023-01-30 14:27:06 +01:00
2023-01-30 14:27:06 +01:00
2023-01-30 14:27:06 +01:00