Jos

My interpretation is different. UIDVALIDITY should also show these changes between sessions. As long as the UIDVALIDITY and UID are the same the message should be exactly the same, only the flags may change. The point of this is that messages can be cached. If DavMail keeps a running set of UIDs and only hands them out to new or changed messages, then it is fine to not change UIDVALIDITY. That would mean that either Exchange tracks this correctly or that DavMail keeps a state for each account.

Double space in UID FETCH response.

UIDVALIDITY is always 1

Thank you. I've applied the patch and pushed it. Cheers, Jos On Saturday 14 May 2016...

simple.xsl

xsl:message and xsl:namespace-alias are missing for xslt2