Timo Sirainen wrote:
Note the UID FETCH 119071:* command. Outlook thinks the latest UID it has seen is 1190710, so it tries to fetch new messages with that command. It doesn't really even want to fetch 11703 here, but because "*" matches the latest existing message (by IMAP spec), the last message is returned sort-of unintentionally.
I think your Outlook has just broken its internal cache. Try recreating the account or clearing the cache if you can figure out how.
Maybe that high UIDs did exist at some point and then UIDVALIDITY changed, but Outlook didn't understand that?
Thanks Timo, I will try that and see what the result is today. Obviously Outlook has missed something at some point; perhaps it would be possible for Dovecot to notice the OOB UID and try to send Outlook correcting advice? It might save someone else the mystery!
cheers, Karl