Hello to all, Having the same Problem dealing with Windows 8.1 and it belongs to all IMAP-Servers but Exchange from Mirosoft. The first thing we recognized that patching windows 8.1 was the worst thing to do. After patching we could no longer establish a stable connection to any IMAP Server if, and this is important, i spart of a windows domain!!! Is this is a bug in wondows 8.1 or outloook 2013!? We could not battle around in a production environment and from Mirosoft there was nothing they could do. So this ist he workoround: Set up a local user on the machine and set up outlook IMAP connection. This will work fine. Then log in as the domain user and do a link to the local users profile like this, ex: Runas /savecred /user:MYPC\yourlocalusername “C:\Program Files\Microsoft Office\Office15\OUTLOOK.EXE"
Good Luck Daniel EDV Daniel Müller Leitung EDV Tropenklinik Paul-Lechler-Krankenhaus Paul-Lechler-Str. 24 72076 Tübingen Tel.: 07071/206-463, Fax: 07071/206-499 eMail: muel...@tropenklinik.de Internet: www.tropenklinik.de -----Ursprüngliche Nachricht----- Von: Sam Varshavchik [mailto:mr...@courier-mta.com] Gesendet: Montag, 18. Mai 2015 03:42 An: Courier Users Betreff: Re: [courier-users] Recent Windows 8.1 update problem Mark Constable writes: > I've got a screenshot of the error so I'll manually type it in here... > > Task 'Syncronizing subscribed folders for user@domain' reported error > (0x800CCC0E): 'Outlook cannot synchronize subscribed folders for > user@domain. Error: Cannot connect to the server. If you continue to > receive this message, contact your server administrator or ISP. > > I think I am seeing way too many of these but it's hard to nail down > which user belongs to which IP when a lot of them are dynamic... > > May 18 10:37:12 s1 courieresmtpd: > error,relay=::ffff:xx.xx.xx.xx,msg="502 ESMTP command error",cmd: > DATA > > There is not a lot in the logs to go by. courier-mta 0.73, imap 4.15 The SMTP error message would not have anything to do with the client's failure to talk IMAP. That's a dead end. Unless, for some reason, the client makes an smtp connection, for some reason. It's true that there's not a lot to go by. In fact, without the actual error being shown – the actual error message, instead of meaningless dribble like "error 0x800CCC0E" – the only party here who could possibly know the answer is Microsoft. The only way this can be investigated further, is have a controlled environment with IMAGDEBUGFILE turned on, to capture what the client is sending, and what the response is. ------------------------------------------------------------------------------ One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y _______________________________________________ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
