Outlook assistant fails with autodiscovered account | MDaemon Technologies, Ltd.
  1. Forum
  2. MDaemon
  3. Outlook assistant fails with autodiscovered account

Outlook assistant fails with autodiscovered account

  • S

    Hi forum,

    fist, the autodiscover entries are all well created and the're working. see article https://help.mdaemon.com/mdaemon/de/autodiscovery--server.html)

    But both kind's of Outook assistands fail.
    - The "new" assistant (which pop's up when create a new account)
    - And the "old" assistant (from control panel > E-Mail)

    Problem is, the assistant can connect and find the settings, but it seems he stuck on authentication.


    The Autodiscover url's are all working

    Im not sure, but i think, the problem is related to authentication. If i browse to the "https://server/mddp site i get an login page. If i use valid credentials (they are working in webmail for example) i cant get beyond this. 
    If in the assitant, after the error page (screenshot at the top) he also asks for credentials but cant get forward.

     

    What i want is an solution like it worked with Exchange or 365. Open Outlook, add credentials, finnished. No old school entering tons of values like in connector or something. 

    Does anybody know, why the assistant may is failing?

    0 likes
  • A

    What do MDaemon's AutoDiscover and MDDP logs show is happening?

    --
    Arron Caruth

    0 likes
  • S

    Hi Arron, there is no mddp*.log and no activesync*.log in the log directory of mdaemon. 
    But there is an airsync-[date].log 

    In that log, at the time i enter the credentials. Nothing to this account is logged.

    0 likes
  • A

    Please repeat the steps you did previously by going to https://autodiscover.domain.com/autodiscover/autodiscover.xml and then to https://mail.domain.com/mddp, where domain.com is your domain.  You should be prompted for credentials, enter a username and password that are valid on the MDaemon server.  Then go to the MDaemon\logs directory and check for an AutoDiscover*.log and a MDDP*.log file.  

    If there is still no activity, check the MDaemon\Data\mddp.ini file, what is the LogLevel set to in the [Logs] section?  What is the LogName?

     

    --
    Arron Caruth

    0 likes
  • S

    @Arron The situation changed. But i am not sure why because i did'nt made changes.
    Actually, the logs are there and getting filled (with correct ip address my computer actually is behind on).
    If i connect via Outlook, sadly Outlook (2019/2022) creates a IMAP account automatically, not an active sync account. 

    Mddp-[date].log:
    The log is only filled, when i open with browser. Not when i try to connect with Outlook. The content is:

    241105 104815611 I [3BA08DB8] 0x41330080 Connection: IP:84.115.238.181 SRV:mail.domain.com RM:GET SSL:On UA:Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:132.0) Gecko/20100101 Firefox/132.0 QS: LNG:(null) CT= CL=0 TID:0x00003028 
    241105 104815611 W [3BA08DB8] 0x81440060 HTTP Status: 401
    241105 104815612 D [3BA08DB8] 0x4144002F Connection Terminating
    241105 104825308 I [3BA08DBB] 0x41330080 Connection: IP:84.115.238.181 SRV:mail.domain.com RM:GET SSL:On UA:Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:132.0) Gecko/20100101 Firefox/132.0 QS: LNG:(null) CT= CL=0 TID:0x0001BA50 
    241105 104825554 I [3BA08DBB] 0x41330008 Authenticated: User1@domain.com
    241105 104825558 D [3BA08DBB] 0x4144002F Connection Terminating

    Autodiscover-[date].log (when connecting via Outlook):
    241105 104238557 I [3B9FD026] 0x41330080 Connection: IP:84.115.238.181 SRV:autodiscover.domain.com RM:GET SSL:Off UA:Microsoft Office/16.0 (Windows NT 10.0; MAPICPL 16.0.18129; Pro) QS: LNG:(null) CT=text/xml CL=0 TID:0x0001AA30 
    241105 104238558 D [3B9FD026] 0x41380102 Connection Terminating

    Autodiscover-[date].log (when connecting via Chrome browser):
    241105 111442813 I [3B9FD02B] 0x41330080 Connection: IP:84.115.238.181 SRV:autodiscover.domain.com RM:GET SSL:On UA:Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:132.0) Gecko/20100101 Firefox/132.0 QS: LNG:(null) CT= CL=0 TID:0x0001A858 
    241105 111442814 D [3B9FD02B] 0x41380102 Connection Terminating

    0 likes
  • A

    It sounds like the autodiscovery server is working now, is that correct?

    According to the information available on Google the AutoDiscover process that outlook uses is different for ActiveSync.  If you want an ActiveSync account to be created you must specifically tell Outlook that you want an ActiveSync account.  

     

    --
    Arron Caruth

    0 likes
Please login to reply this topic!