Error 0x8004011c after Testing send/receive success in Outlook 2013

Hi there

We were having the same issue and read this post and felt your frustration.

We noticed that we got the error only on profiles that were logged in to the domain.  When we set up a local computer account the IMAP configured fine.  As we needed this for a domain user we investigated further.   A rather long winded way around it but this is what worked for us:

Design flaw causing Microsoft outlook 2013 to not connect to imap accounts whilst joined on domain,

Here is the workaround.

Create a local profile with the same username and password, open outlook and set up the imap account as per usual.

When finished, and it is working, close outlook, log out of the profile, and log in on the domain profile.

For the next part I will be using "bob" as the local username, and "MYPC" as the local computer name.

Right click on the desktop, create new shortcut.

Pop-up window will appear, location of the item.

Type in the following,

Runas /savecred /user:MYPC\bob “C:\Program Files\Microsoft Office\Office15\OUTLOOK.EXE"

** you must make sure of the path of the OUTLOOK.EXE file **

Click Next

Type a name for this shortcut: I would type in My Mail, and remove the original outlook icon from desktop, start menu, start screen etc.

Click Finish

Right click on shortcut, properties, change icon, and browse to outlook exe

Choose it, and choose outlook icon.

Click ok, to close the properties box.

Double click on icon, it will prompt for password of local account, you will only need to input it once.

Outlook will now open with the profile that was created in the local account to loop around IMAP domain level issues.

PS: If it does not ask for a password, and cmd window just pops up and closes, right click the icon, and edit the location string, remove the /savecred part, this will unfortunately cause the user to enter his password every time he opens outlook, which is less of a headache than not having mail on domain level.

Hope this helps someone and full recognition to Jean Korster for resolving this issue for us and not myself!