On Thu, 2003-04-03 at 05:55, Mark Keasling wrote: > > The way my server does it is that it accepts UIDs even for messages that > > client hasn't been notified yet, but '*' in messagesets still refers to > > the last notified message. > > This behavior will cause more harm than good.
In what way? It affects only broken clients. > It would be better to send the EXISTS and RECENT updates just before > sending the FETCH response. Except we're only trying to work around OE bug. And like I said, sending EXISTS and RECENT before the FETCH triggers another OE bug. > A server should never generate bad > protocol as a work around for a client problem. If client clearly asks for it by violating protocol itself, why not? Maybe I should make this workaround configurable anyway.
