Configure Incoming mail using https 443 activesync style connection

[Jero Dungog]

I am currently configuring a Mail server for a client and I keep on getting:

My configuration are as follows:
I had tried the other steps and recommendations from other threads with no luck.
Some recommendations say that something needs to be configured from the host's end to allow the connection.
However, I do not have access to the host server.

I tried logging in to the account via an email client and I had successfully logged in.

Any further comments or suggestions is highly appreciated!

PS. Server logs only shows:

[Craig Castle-Mead · Accepted solution]

Hi @Jero Dungog 

Jira mail handlers do not support activesync / MAPI - only pop and imap

you can find more detail on this previous post  - https://community.atlassian.com/t5/Jira-questions/JIRA-mail-server-with-Exchange/qaq-p/90235

CCM

[Jero Dungog]

I had contacted the email server admin and asked for him to provide a way for me to connect via POP and IMAP.

I will update here again once his changes are done and I had tested it.
Though it might take a day sine we are in different time-zones.

Thank you @Craig Castle-Mead  for bringing this up.

[Brant Schroeder]

The error shown from the server logs usually means that the authentication credentials supplied for the SMTP server are not correct or have expired.  Did you happen to use different credentials at first?  

Here is a help article - https://confluence.atlassian.com/jirakb/sending-a-test-email-fails-due-to-javax-mail-authenticationfailedexception-151519286.html

Also are you sure that the port is 443?  Usually it is 995 for secure pop.

[Jero Dungog]

@Brant Schroeder no I had not used any other credentials prior.
That is also something which I am curious about but that is the port number that the email server admin gave me.

I had already contacted the email server admin and I will be requesting him to enable pop/imap based on the recommendation of @Craig Castle-Mead .

I will update here again if that solved the issue.

Thank you for your response, it is much appreciated

[Jero Dungog]

For others who might stumble upon this thread:
Was finally able to resolve this issue in the mail handlers by contacting the mail server admin.

Work around done:
Created a sub-domain for our intended emails and enabled SECURED_IMAP/SECURED_POP in that specific sub-domain.

Connected via the sub-domain configured.

So in conclusion, 
This was not in any way a JIRA issue but instead an issue on the Mail Server.


Thank you to: @Craig Castle-Mead & @Brant Schroeder for helping me out on this one.