Hej alla!
Detta är Microsofts svar:
Efter många och noggranna undersökningar har Microsoft lokaliserat felet till din e-postleverantör.
"Felet" är en konfiguration i serverns mjukvara som alltså inte uppdagades innan November uppdateringen från Windows Update.
Microsoft kommer att kontakta e-postleverantörer med dessa servrar, men det underlättar och påskyndar en lösning om ni kontaktar dem personligen.
Kontakta dem med följande information så de kan konfigurera sina servrar och ditt konto för att problemet ska lösas (ISP=Internet Service Provider, i detta fall e-postleverantör):
Microsoft has investigated this issue and it appears your ISP needs to update their email server software to ensure RFC compliance. Please share the specifics below with your ISP so they can investigate and
address the issue. Microsoft is developing a fix for an upcoming update to special case this RFC compliance issue but it is preferred to address this with the ISP to ensure the best functionality.
After installing the Outlook 2013 November Public Update
http://support.microsoft.com/kb/2837618/en-us no new IMAP email items are downloaded after the initial sync.
The Outlook IMAP log shows the following TX/RX pair with an error:
IMAP: 09:08:37 [tx] vos2 UID SEARCH UID 302220:4294967295 SINCE 31-Dec-2013
IMAP: 09:08:37 [rx] vos2 BAD invalid SEARCH command syntax, invalid search criteria syntax
Looking at the description of a UID command
http://tools.ietf.org/html/rfc3501#section-6.4.8, the RFC states:
“[…], the UID command takes a SEARCH command with SEARCH command arguments. The interpretation of the arguments is the same as with SEARCH”
Therefore, any syntax that works with plain “SEARCH” commands should also work with “UID SEARCH” commands. Also, looking at the Formal Syntax of the UID and SEARCH commands at
http://tools.ietf.org/html/rfc3501#section-9, it appears that Outlook is sending a valid command to the server and
the server is rejecting it.
Reviewing the Outlook logs we can see Outlook is sending a command similar to the following:
UID SEARCH UID ######:########## SINCE 31-Dec-2013
But the server is not accepting/processing the command and returning:
BAD invalid SEARCH command syntax, invalid search criteria syntax