Timo Sirainen wrote:
This doesn't happen with dovecot-stable. I'm wondering whether it might be a different issue, after all. If it's only giving spurious but correct responses, then I guess a real client/user wouldn't notice.
I don't think it's a problem, but unexpected things usually tell that there's a bug :)
This was caused by "keyword resets" being written to transaction log file using sequence numbers, but later being treated as UIDs. So the bug could have erased some keywords, or just give these extra FLAGS-replies for those messages..
I'm glad to say the flag change losses appear to be fixed in 1.0-stable. I've now got most of the IT department using Dovecot (those that don't use Ex****ge anyway, if you'll pardon my bad language!). Nobody's complained yet ;)
Best Wishes, Chris
-- --+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+- Christopher Wakelin, c.d.wakelin@reading.ac.uk IT Services Centre, The University of Reading, Tel: +44 (0)118 378 8439 Whiteknights, Reading, RG6 2AF, UK Fax: +44 (0)118 975 3094