On Sat, Jul 13, 2019 at 08:07:31PM +0200, Guillaume Brogi wrote: > Hello again, > > > > > > i reported the bug to them, so doing nothing might also get you > > > > > somewhere. :D > > > > They are usually quite reactive, though I think it's a small team. > > > > > > > ok, let's hope the report actually went through (i used their weird > > > contact form, which didn't give much of a delivery confirmation ...) > > Ack. If there's no news by next week I'll try contacting them > > I imagine you didn't get a reply then. > yeah, silence.
> I'll try sending them an email too. > What should I be telling them? > AFAIU, their server responds to `5 UID FETCH *:*` but should instead > respond to `5 UID FETCH *`, right? > not quite. it responds in both cases, but both times incorrectly. > Alternative commands could be `10 FETCH * (UID)` or `11 UID SEARCH *` > but both return nothing. > Anything else I should mention? > it boils down to the interpretation of uncommon message ranges, and it appears to be unrelated to whether the range is about UIDs or not (otherwise the alternative commands would work). basically, * results in no messages and *:* results in all messages, while both should result in exactly one message: the last one in the box. > Do you have a link to the spec mentioning the old and new command? > it boils down to the BNF for seq-number in RFC3501. section 6.4.8 may be helpful for understanding. > Do you want me to Cc you when I send the email? > yep _______________________________________________ isync-devel mailing list isync-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/isync-devel
