Hi Madars,

I wrote that guide, but I'm afraid I never tested it with Outlook.
So far I've tested the webmail, K9 (Android), and Thunderbird (Linux).
Could it be that Outlook is trying to force a type of authentication that SOGo doesn't like?
What server type did you use in your Outlook Account settings?

I have just tried on a Windows work laptop, and in Outlook 2016, I used the following settings (manually configured):

IMAP
On the Advanced settings, Incoming port 143, TLS encryption
Outgoing port 25, TLS encryption.
If "My outgoing server (SMTP) required authentication" is selected, even with "Use same settings as my incoming mail server", this doesn't work for some reason, even though it should require a login, and I have configured a login on Thunderbird (Linux) and it works fine.

With these settings, I was able to log in, view previously received messages, I can see the test message that Outlook sends when testing the account, and I can send mail from Outlook to another domain.

Judging by the fact that you say that you're only seeing errors in Apache logs, doesn't this mean that it's trying RPCHTTP or whatever it's called that Outlook uses for newer versions of Exchange to allow HTTP/HTTPS access to mail?
I can't say I've ever tried that or know if it is even capable of working...

NOTE: I need to add a bit to the Wiki about securing Postfix - if you're not careful you will end up being a spam relay... as I found out recently :(

Chris


On 26/09/16 10:00, Madars Vitolins ([email protected]) wrote:
Hi Folks,

I have done run successfully example.com domain with external IMAP/STMP
server. Now I move to production by changing the domain name by using
http://wiki.sogo.nu/ZEGReconfiguration documentation.

All process went well, SOGo web is working fine, but outlook keeps
saying that server is in offline (Outlook cannot logon). Only logs I can
find from Outlook anywhere mode is from Apache:

-------------
[Mon Sep 26 04:56:10.246795 2016] [wsgi:error] [pid 2773] RPCProxy started
[Mon Sep 26 04:56:10.247144 2016] [wsgi:error] [pid 2773]
INFO:openchange.web.auth.NTLMAuthHandler:client did not pass auth cookie
[Mon Sep 26 04:56:10.253964 2016] [wsgi:error] [pid 2773]
INFO:openchange.web.auth.NTLMAuthHandler:acquiring lock
/var/cache/ntlmauthhandler/ntlm-127.0.0.1.lock (2773)
[Mon Sep 26 04:56:10.275789 2016] [wsgi:error] [pid 3176]
INFO:openchange.web.auth.NTLMAuthHandler:NTLMAuthHandler daemon spawned
with pid 3176
--
[email protected]
https://inverse.ca/sogo/lists

Reply via email to