Re: [Dovecot] uid fetch/store always use the last uid when range is invalid

2010-03-11 Thread Timo Sirainen
On 11.3.2010, at 12.07, Jean-Baptiste Vignaud wrote: >>> l uid store 100:* +flags (\Seen \Deleted) >>> * 281 FETCH (UID 362 FLAGS (\Deleted \Seen)) >>> l OK Store completed. >> >> and exactly as required by RFC 3501. > > Thanks; i'll tell him :) > > It seems he has seen another server that

Re: [Dovecot] uid fetch/store always use the last uid when range is invalid

2010-03-11 Thread Jean-Baptiste Vignaud
On Thu, Mar 11, 2010 at 10:54 AM, Timo Sirainen wrote: >> one colleague found a strange behavior, that can be annoying : > .. >> and more annoying: >> >> l uid store 100:* +flags (\Seen \Deleted) >> * 281 FETCH (UID 362 FLAGS (\Deleted \Seen)) >> l OK Store completed. > > and exactly as requi

Re: [Dovecot] uid fetch/store always use the last uid when range is invalid

2010-03-11 Thread Timo Sirainen
On 11.3.2010, at 11.27, Jean-Baptiste Vignaud wrote: > one colleague found a strange behavior, that can be annoying : .. > and more annoying: > > l uid store 100:* +flags (\Seen \Deleted) > * 281 FETCH (UID 362 FLAGS (\Deleted \Seen)) > l OK Store completed. and exactly as required by RFC 35

[Dovecot] uid fetch/store always use the last uid when range is invalid

2010-03-11 Thread Jean-Baptiste Vignaud
hello all; one colleague found a strange behavior, that can be annoying : -bash-3.1$ telnet 0 143 Trying 0.0.0.0... Connected to 0 (0.0.0.0). Escape character is '^]'. * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE AUTH=PLAIN AUTH=CRAM-MD5] Dovecot ready. l login login pass