indreias requested a separate thread. (Note: I’m having problems with formatting of the forum here when I quote someone, if I add text after the /quote tag, it jumbles everything together, so I’m having to rearrange everything to get it to show up correctly.)
I have to agree with Norlig (quote bottom of page) as when I use TLS, I can’t get my phone to connect. I’ve confirmed that I have access from the outside using simple telnet as well as the “openssl s_client -showcerts -connect <domain.com>:<port#> -servername <domain.com>”
I’m still learning to read my Axigen logs, but I think I’m making connection with IMAPS, although it does say “LOGINDISABLED” in it.
IMAP Log
2020-01-20 08:37:54 -0700 16 Server IMAP:00000000: << SSL: client hello, remote 52.125.129.44:42746, version TLS 1.3 (0304)
2020-01-20 08:37:54 -0700 16 Server IMAP:00000000: << SSL: client hello, remote 52.125.129.44:42746, 43 cipher suites:
2020-01-20 08:37:54 -0700 16 Server IMAP:00000000: << SSL: client hello, remote 52.125.129.44:42746, sni extension for <domain.com>
2020-01-20 08:37:54 -0700 16 Server IMAP:00000000: >> SSL: server hello, remote 52.125.129.44:42746, version TLS 1.2 (0303)
2020-01-20 08:37:54 -0700 16 Server IMAP:00000000: >> SSL: server hello, remote 52.125.129.44:42746, cipher suite c02f
2020-01-20 08:37:54 -0700 16 Server IMAP:00000000: >> SSL: server write cert, remote 52.125.129.44:42746, version TLS 1.2 (0303)
2020-01-20 08:37:54 -0700 16 Server IMAP:00000000: >> SSL: server write cert, remote 52.125.129.44:42746, certificate 1: serial 03B20A70177357804011B1815CCB62E353CA
2020-01-20 08:37:54 -0700 16 Server IMAP:00000000: >> SSL: server write cert, remote 52.125.129.44:42746, certificate 2: serial 0A0141420000015385736A0B85ECA708
2020-01-20 08:37:54 -0700 08 Server IMAP:000018EB: [10.0.0.100:993] connection accepted from [52.125.129.44:42746]
2020-01-20 08:37:54 -0700 16 Server IMAP:000018EB: >> * OK AXIGEN IMAP4rev1 service is ready
2020-01-20 08:37:55 -0700 16 Server IMAP:000018EB: << BAX0 CAPABILITY
2020-01-20 08:37:55 -0700 16 Server IMAP:000018EB: >> * CAPABILITY IMAP4rev1 CHILDREN IDLE LITERAL+ MULTIAPPEND SPECIAL-USE NAMESPACE UIDPLUS QUOTA XLIST ID LOGINDISABLED AUTH=CRAM-MD5 AUTH=DIGEST-MD5 AUTH=GSSAPI ACL RIGHTS=texkbn
2020-01-20 08:37:55 -0700 16 Server IMAP:000018EB: >> BAX0 OK CAPABILITY completed [0 msec]
2020-01-20 08:37:55 -0700 16 Server IMAP:000018EB: << BAX1 ID (“name” “Outlook-iOS-Android” “version” “2.0”)
2020-01-20 08:37:55 -0700 16 Server IMAP:000018EB: >> * ID (“name” “Axigen” “version” “10.3.0 (Windows/x64)”)
2020-01-20 08:37:55 -0700 16 Server IMAP:000018EB: >> BAX1 OK ID completed [0 msec]
2020-01-20 08:37:55 -0700 16 Server IMAP:000018EB: >> * BYE AXIGEN IMAP4rev1 service terminating connection
2020-01-20 08:37:55 -0700 08 Server IMAP:000018EB: Closing connection from [52.125.129.44:42746]
When I look at my SMTP Receiving Log, I can see people trying to log into my server over port 25, but no attempts from me on port 465.
Maybe with multiple people having the same problem, we can figure this out together.
My wife told me today that she can’t send e-mails, and I’ve confirmed it. I can send e-mail via Webmail, but she cannot. As far as I can tell, both accounts are configured the same, but obviously something is different. She can send e-mails internally to me, but not external.
When she sends, she I see a relay messages in the SMTP Send Log
Wife Sending EXTERNAL e-mail
2020-01-21 10:41:17 -0700 08 Server SMTP-OUT:00000019: Relay mail 2F5FB4: connecting to 104.215.95.187:25
2020-01-21 10:41:38 -0700 08 Server SMTP-OUT:00000019: Relay mail 2F5FB4: unable to connect to 104.215.95.187:25: The semaphore timeout period has expired.
2020-01-21 10:41:38 -0700 08 Server SMTP-OUT:00000019: Use 52.164.206.56 to relay mail 2F5FB4 for domain hotmal.com
2020-01-21 10:41:38 -0700 08 Server SMTP-OUT:0000001A: Relay mail 2F5FB4: connecting to 52.164.206.56:25
2020-01-21 10:41:59 -0700 08 Server SMTP-OUT:0000001A: Relay mail 2F5FB4: unable to connect to 52.164.206.56:25: The semaphore timeout period has expired.
2020-01-21 10:41:59 -0700 08 Server SMTP-OUT:0000001A: Relay mail 2F5FB4: no more relays for hotmal.com
2020-01-21 10:41:59 -0700 04 Server SMTP-OUT:0000001A: Delivery attempt completed for mail 2F5FB4; 1 recipients remaining; reschedule for delivery
2020-01-21 10:41:59 -0700 08 Server SMTP-OUT:0000001A: Set mail state to SEND FAILURE
2020-01-21 10:47:04 -0700 08 Server SMTP-OUT:0000001B: Relay mail 2F5FB4: connecting to 104.215.95.187:25
2020-01-21 10:47:25 -0700 08 Server SMTP-OUT:0000001B: Relay mail 2F5FB4: unable to connect to 104.215.95.187:25: The semaphore timeout period has expired.
2020-01-21 10:47:25 -0700 08 Server SMTP-OUT:0000001B: Use 52.164.206.56 to relay mail 2F5FB4 for domain hotmal.com
2020-01-21 10:47:25 -0700 08 Server SMTP-OUT:0000001C: Relay mail 2F5FB4: connecting to 52.164.206.56:25
2020-01-21 10:47:46 -0700 08 Server SMTP-OUT:0000001C: Relay mail 2F5FB4: unable to connect to 52.164.206.56:25: The semaphore timeout period has expired.
2020-01-21 10:47:46 -0700 08 Server SMTP-OUT:0000001C: Relay mail 2F5FB4: no more relays for hotmal.com
2020-01-21 10:47:46 -0700 04 Server SMTP-OUT:0000001C: Delivery attempt completed for mail 2F5FB4; 1 recipients remaining; reschedule for delivery
2020-01-21 10:47:46 -0700 08 Server SMTP-OUT:0000001C: Set mail state to SEND FAILURE
But when I use Webmail to send to the exact same receiving e-mail address, it immediately goes through:
Me Sending EXTERNAL e-mail
2020-01-21 10:52:39 -0700 08 Server SMTP-OUT:0000001E: Relay mail 25BF3B: connected to 104.47.41.33:25
2020-01-21 10:52:40 -0700 16 Server SMTP-OUT:0000001E: << 220 DM3NAM03FT052.mail.protection.outlook.com Microsoft ESMTP MAIL Service ready at Tue, 21 Jan 2020 17:52:27 +0000
2020-01-21 10:52:40 -0700 16 Server SMTP-OUT:0000001E: >> EHLO Server
2020-01-21 10:52:40 -0700 16 Server SMTP-OUT:0000001E: << 250-DM3NAM03FT052.mail.protection.outlook.com Hello [999.999.999.999]
2020-01-21 10:52:40 -0700 16 Server SMTP-OUT:0000001E: << 250-SIZE 49283072
2020-01-21 10:52:40 -0700 16 Server SMTP-OUT:0000001E: << 250-PIPELINING
2020-01-21 10:52:40 -0700 16 Server SMTP-OUT:0000001E: << 250-DSN
2020-01-21 10:52:40 -0700 16 Server SMTP-OUT:0000001E: << 250-ENHANCEDSTATUSCODES
2020-01-21 10:52:40 -0700 16 Server SMTP-OUT:0000001E: << 250-STARTTLS
2020-01-21 10:52:40 -0700 16 Server SMTP-OUT:0000001E: << 250-8BITMIME
2020-01-21 10:52:40 -0700 16 Server SMTP-OUT:0000001E: << 250-BINARYMIME
2020-01-21 10:52:40 -0700 16 Server SMTP-OUT:0000001E: << 250-CHUNKING
2020-01-21 10:52:40 -0700 16 Server SMTP-OUT:0000001E: << 250 SMTPUTF8
2020-01-21 10:52:40 -0700 16 Server SMTP-OUT:0000001E: >> STARTTLS
2020-01-21 10:52:40 -0700 16 Server SMTP-OUT:0000001E: << 220 2.0.0 SMTP server ready
2020-01-21 10:52:40 -0700 16 Server SMTP-OUT:0000001E: >> SSL: client hello, remote 104.47.41.33:25, version TLS 1.3 (0304)
2020-01-21 10:52:40 -0700 16 Server SMTP-OUT:0000001E: >> SSL: client hello, remote 104.47.41.33:25, session id 34e91757c33095cbf621d7d930cc3709a77c3bc3b997438276b519caabdc7bba
2020-01-21 10:52:40 -0700 16 Server SMTP-OUT:0000001E: >> SSL: client hello, remote 104.47.41.33:25, 31 cipher suites:
2020-01-21 10:52:40 -0700 16 Server SMTP-OUT:0000001E: << SSL: server hello, remote 104.47.41.33:25, version TLS 1.3 (0304)
2020-01-21 10:52:40 -0700 16 Server SMTP-OUT:0000001E: << SSL: server hello, remote 104.47.41.33:25, session id 93150000950bc65bc141ee7f0981e843936f2869380e931843a30703ab5f481c
2020-01-21 10:52:40 -0700 16 Server SMTP-OUT:0000001E: << SSL: server hello, remote 104.47.41.33:25, cipher suite c030
2020-01-21 10:52:40 -0700 16 Server SMTP-OUT:0000001E: >> EHLO Server
2020-01-21 10:52:40 -0700 16 Server SMTP-OUT:0000001E: << 250-DM3NAM03FT052.mail.protection.outlook.com Hello [999.999.999.999]
2020-01-21 10:52:40 -0700 16 Server SMTP-OUT:0000001E: << 250-SIZE 49283072
2020-01-21 10:52:40 -0700 16 Server SMTP-OUT:0000001E: << 250-PIPELINING
2020-01-21 10:52:40 -0700 16 Server SMTP-OUT:0000001E: << 250-DSN
2020-01-21 10:52:40 -0700 16 Server SMTP-OUT:0000001E: << 250-ENHANCEDSTATUSCODES
2020-01-21 10:52:40 -0700 16 Server SMTP-OUT:0000001E: << 250-8BITMIME
2020-01-21 10:52:40 -0700 16 Server SMTP-OUT:0000001E: << 250-BINARYMIME
2020-01-21 10:52:40 -0700 16 Server SMTP-OUT:0000001E: << 250-CHUNKING
2020-01-21 10:52:40 -0700 16 Server SMTP-OUT:0000001E: << 250 SMTPUTF8
2020-01-21 10:52:40 -0700 08 Server SMTP-OUT:0000001E: Start sending mail 25BF3B
2020-01-21 10:52:40 -0700 16 Server SMTP-OUT:0000001E: >> MAIL FROM:me@domain.com SIZE=1484
2020-01-21 10:52:40 -0700 16 Server SMTP-OUT:0000001E: >> RCPT TO:nytestaccount@hotmail.com
2020-01-21 10:52:40 -0700 16 Server SMTP-OUT:0000001E: >> NOOP
2020-01-21 10:52:40 -0700 16 Server SMTP-OUT:0000001E: << 250 2.1.0 Sender OK
2020-01-21 10:52:40 -0700 16 Server SMTP-OUT:0000001E: << 250 2.1.5 Recipient OK
2020-01-21 10:52:40 -0700 16 Server SMTP-OUT:0000001E: << 250 2.0.0 OK
2020-01-21 10:52:40 -0700 16 Server SMTP-OUT:0000001E: >> BDAT 1484 LAST
2020-01-21 10:52:40 -0700 16 Server SMTP-OUT:0000001E: >> Send last chunk of size 1484
2020-01-21 10:52:40 -0700 08 Server SMTP-OUT:0000001E: Release mail 25BF3B
2020-01-21 10:52:40 -0700 16 Server SMTP-OUT:0000001E: << 250 2.6.0 1579629159869189179@domain.com [InternalId=55117315370507, Hostname=DM3NAM03HT007.eop-NAM03.prod.protection.outlook.com] 8558 bytes in 0.317, 26.334 KB/sec Queued mail for delivery -> 250 2.1.5
2020-01-21 10:52:40 -0700 08 Server SMTP-OUT:0000001E: Data sent for mail 25BF3B; server response: 2.6.0 1579629159869189179@domain.com [InternalId=55117315370507, Hostname=DM3NAM03HT007.eop-NAM03.prod.protection.outlook.com] 8558 bytes in 0.317, 26.334 KB/sec Queued mail for delivery -> 250 2.1.5
2020-01-21 10:52:40 -0700 08 Server SMTP-OUT:0000001E: Set recipient nytestaccount@hotmail.com state to SENT
2020-01-21 10:52:40 -0700 08 Server SMTP-OUT:0000001E: Delivery attempt completed for mail 25BF3B; schedule for cleanup
2020-01-21 10:52:40 -0700 08 Server SMTP-OUT:0000001E: Set mail state to SENT
2020-01-21 10:52:40 -0700 16 Server SMTP-OUT:0000001E: >> QUIT
2020-01-21 10:52:40 -0700 16 Server SMTP-OUT:0000001E: << 221 2.0.0 Service closing transmission channel
2020-01-21 10:52:40 -0700 08 Server SMTP-OUT:0000001E: Disconnected from 104.47.41.33
Yesterday, I was playing with a 3rd account and noticed that it couldn’t send either, but I thought it was just because I didn’t have something configured correctly in Outlook. Now that I’m using the Webmail, I can see the same behavior (as my wife’s account.)
Ugghh… I can’t believe I did that. Thank for pointing that out. She said that she couldn’t e-mail brother that’s in her contact list and I just tried to do a simple test. I just checked the logs for her original e-mail and it gives a “<< 550 Access denied - Invalid HELO name (See RFC5321 4.1.1.1)” We’ve sent to them many times before using my previous server and I’ve never seen that before. The one thing that I noticed that that is obviously different is when I telnet to my new server, it responds with a “220 Server Axigen ESMTP ready” rather than my server & domain name. It may mean nothing, but it was something that I saw.
Of course, I still can’t connect my Android device up. It keeps giving me an error.
I’m really at a loss as to why I can’t get my Android clients connecting to my Axigen server for IMAPS/SMTPS. As I was looking at my logs, I found the following:
IMAP Log
2020-01-29 20:20:31 -0700 16 Server IMAP:00000000: << SSL: client hello, remote 52.125.129.35:59608, version TLS 1.3 (0304)
2020-01-29 20:20:31 -0700 16 Server IMAP:00000000: << SSL: client hello, remote 52.125.129.35:59608, 43 cipher suites:
2020-01-29 20:20:31 -0700 16 Server IMAP:00000000: << SSL: client hello, remote 52.125.129.35:59608, sni extension for <domain.com>
2020-01-29 20:20:31 -0700 16 Server IMAP:00000000: >> SSL: server hello, remote 52.125.129.35:59608, version TLS 1.2 (0303)
2020-01-29 20:20:31 -0700 16 Server IMAP:00000000: >> SSL: server hello, remote 52.125.129.35:59608, cipher suite c02f
2020-01-29 20:20:31 -0700 16 Server IMAP:00000000: >> SSL: server write cert, remote 52.125.129.35:59608, version TLS 1.2 (0303)
2020-01-29 20:20:31 -0700 16 Server IMAP:00000000: >> SSL: server write cert, remote 52.125.129.35:59608, certificate 1: serial
2020-01-29 20:20:31 -0700 16 Server IMAP:00000000: >> SSL: server write cert, remote 52.125.129.35:59608, certificate 2: serial
2020-01-29 20:20:31 -0700 08 Server IMAP:00003700: [10.0.0.100:993] connection accepted from [52.125.129.35:59608]
2020-01-29 20:20:31 -0700 16 Server IMAP:00003700: >> * OK AXIGEN IMAP4rev1 service is ready
2020-01-29 20:20:31 -0700 16 Server IMAP:00003700: << IUR0 CAPABILITY
2020-01-29 20:20:31 -0700 16 Server IMAP:00003700: >> * CAPABILITY IMAP4rev1 CHILDREN IDLE LITERAL+ MULTIAPPEND SPECIAL-USE NAMESPACE UIDPLUS QUOTA XLIST ID LOGINDISABLED AUTH=CRAM-MD5 AUTH=DIGEST-MD5 AUTH=GSSAPI ACL RIGHTS=texkbn
2020-01-29 20:20:31 -0700 16 Server IMAP:00003700: >> IUR0 OK CAPABILITY completed [0 msec]
2020-01-29 20:20:31 -0700 16 Server IMAP:00003700: << IUR1 ID (“name” “Outlook-iOS-Android” “version” “2.0”)
2020-01-29 20:20:31 -0700 16 Server IMAP:00003700: >> * ID (“name” “Axigen” “version” “10.3.0 (Windows/x64)”)
2020-01-29 20:20:31 -0700 16 Server IMAP:00003700: >> IUR1 OK ID completed [0 msec]
2020-01-29 20:20:31 -0700 16 Server IMAP:00003700: >> * BYE AXIGEN IMAP4rev1 service terminating connection
2020-01-29 20:20:31 -0700 08 Server IMAP:00003700: Closing connection from [52.125.129.35:59608]
Now, when I looked at the Everything Log, I noticed the following:
2020-01-29 20:20:42 -0700 02 Server SERVER:00000000: SSL_connect error (A request to send or receive data was disallowed because the socket had already been shut down in that direction with a previous shutdown call.)
And I’ve repeated trying to connect my phone to Axigen via 993/465 and I see the same stuff in the logs each time.
Does anyone have any suggestions for troubleshooting steps that I can look at? I’m sure that others have this working, so I’m hoping it’s just a simple configuration setting that I’m missing.
I still haven’t been able to figure out the problem with this. Is there anyone here that can help troubleshoot. I’m sure that it’s something small that I’m missing.
Regarding the “The semaphore timeout period has expired.” error please know that it reffers to a timeout, which is typical when the connection was blocked by a firewall. Could you confirm that from the Axigen server you are able to access using telnet 52.164.206.56 on port 25 and the connections are not blocked by a firewall?
Regarding the mobile onnection problems, please also provide us a screenshot with the mail settings configured in your Android mail client.
Thanks for the response. Yea, networking is the first thing that I thought of, but so far haven’t seen anything. As you can see below, I’m forwarding 993 & 465.
I’ve also tried the Android e-mail app and get the same results.
And yes, I have always been able to get through port 25. The server sends and receives e-mail fine. I actually replaced a different server that worked fine for several yeas, but I always used ActiveSync rather than IMAP.
I also tested (from the outside) telneting to port 25, 465 & 993 without a problem. Port 25 comes back with the normal response and the other other two show the normal blank connection screen, but it is connecting.
I can connect via DAV and WebMail (port 443 obviously) without a problem as well as using the Outlook Connector locally.
Please let us know if you are able to connect without specifying the SSL port in the hostname textbox (for example without using “:993”)
If you select in your mail client to use a secure connection, I am certain that you could also select the port or that will usethe default SSL port for that protocol (in IMAP case 993)
So, I was able to add my Axigen account to my mobile phone, having only SMTP Receiving listener with port 465, and IMAP port 993 active.
And only when my I had turned WIFI off on my phone. (i.e using 4G)
Trying to add it while on WIFI, I would get wrong username or password error in the Outlook application, but the IMAP log would register authentication authorized.
With WIFI off, autodiscovery worked as well, did not have to manually enter any domains or ports.
However, having port 25 disabled would stop me from receiving any emails (tested sending from Outlook.com)
Nothing was logged in SMTP Receiving.
I then enabled port 25 and the Email came in after a service restart.
Turning WIFI on again and I still get emails on my phone.
obviously my SMTP Receiving SSL port is not working?
I dont know if my phone is using SSL ports, but I think so?
Per your suggestion, I also tried without the port numbers and also got the same error.
I also wanted to show a screenshot when I use the gmail client:
It seems like my server doesn’t like authenticating my mobile client. I know I’m typing in the correct credentials (user@domain.com and password) as I can open a browser on the same client and copy/paste the same information and login successfully.
So I looked at my IMAP log again and it shows:
IMAP Log
2020-03-20 18:42:39 -0600 16 Server IMAP:00000000: << SSL: client hello, remote 64.44.80.148:60308, version TLS 1.3 (0304)
2020-03-20 18:42:39 -0600 16 Server IMAP:00000000: << SSL: client hello, remote 64.44.80.148:60308, 15 cipher suites: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
2020-03-20 18:42:39 -0600 16 Server IMAP:00000000: << SSL: client hello, remote 64.44.80.148:60308, sni extension for domain.com
2020-03-20 18:42:39 -0600 16 Server IMAP:00000000: >> SSL: server hello, remote 64.44.80.148:60308, version TLS 1.2 (0303)
2020-03-20 18:42:39 -0600 16 Server IMAP:00000000: >> SSL: server hello, remote 64.44.80.148:60308, cipher suite c02f
2020-03-20 18:42:39 -0600 16 Server IMAP:00000000: >> SSL: server write cert, remote 64.44.80.148:60308, version TLS 1.2 (0303)
2020-03-20 18:42:39 -0600 16 Server IMAP:00000000: >> SSL: server write cert, remote 64.44.80.148:60308, certificate 1: serial xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
2020-03-20 18:42:39 -0600 16 Server IMAP:00000000: >> SSL: server write cert, remote 64.44.80.148:60308, certificate 2: serial xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
2020-03-20 18:42:39 -0600 08 Server IMAP:00004D8D: [10.0.0.100:993] connection accepted from [64.44.80.148:60308]
2020-03-20 18:42:39 -0600 16 Server IMAP:00004D8D: >> * OK AXIGEN IMAP4rev1 service is ready
2020-03-20 18:42:39 -0600 16 Server IMAP:00004D8D: << 1 CAPABILITY
2020-03-20 18:42:39 -0600 16 Server IMAP:00004D8D: >> * CAPABILITY IMAP4rev1 CHILDREN IDLE LITERAL+ MULTIAPPEND SPECIAL-USE NAMESPACE UIDPLUS QUOTA XLIST ID LOGINDISABLED AUTH=CRAM-MD5 AUTH=DIGEST-MD5 AUTH=GSSAPI ACL RIGHTS=texkbn
2020-03-20 18:42:39 -0600 16 Server IMAP:00004D8D: >> 1 OK CAPABILITY completed [0 msec]
2020-03-20 18:42:39 -0600 16 Server IMAP:00004D8D: << 2 ID (“name” “com.google.android.gm” “os” “android” “os-version” “9; PPR1.180610.011” “vendor” “samsung” “x-android-device-model” “SM-A705MN” “x-android-mobile-net-operator” “T-Mobile” “AGUID” “T/WGmeHRwY+NsxGdXi4N1a2MjHc=”)
2020-03-20 18:42:39 -0600 16 Server IMAP:00004D8D: >> * ID (“name” “Axigen” “version” “10.3.1.5 (Windows/x64)”)
2020-03-20 18:42:39 -0600 16 Server IMAP:00004D8D: >> 2 OK ID completed [0 msec]
2020-03-20 18:42:39 -0600 16 Server IMAP:00004D8D: << 3 LOGIN user@domain.com
2020-03-20 18:42:39 -0600 16 Server IMAP:00004D8D: >> 3 NO LOGIN failed [0 msec]
2020-03-20 18:42:58 -0600 16 Server IMAP:00004D8D: >> * BYE AXIGEN IMAP4rev1 service terminating connection
2020-03-20 18:42:58 -0600 08 Server IMAP:00004D8D: Closing connection from [64.44.80.148:60308]
I did see in the log a mention "LOGINDISABLED’ and a “NO LOGIN failed”, but as we can see below, I’ve enabled it for this user. In the SMTP Receive Log, I also saw “Authentication error for user ‘user@domain.com’: Invalid password.”
I’ve got to be missing some simple setting somewhere. And I am coming in from the outside (WIFI is turned off. I’ve even tried this when running errands around town.) What else can I look at?
Yes, when I check the of the “unsecured” options, I can set the mobile device perfectly. Of course, I definitely don’t want any unsecured connections. What would be the next step?
Please know that the “unsecured” authentication type does not mean that anyone can brake it.
For example an 1024 encryption is unsecure comparing to a 2048 encryption.
The mail clients (in your case the mobile mail client) can use specific authentication methods and not all authentication methods and therefore the enxt step is to uncheck the “unsecure” authentication types one by one and save configuration for each to see wich is the one needed for the mobile client.
This way you will have only one “unsecure” authentication type enabled so you can also use the mobile client to authenticate.
Do note that you are also using SECURE connection (SSL / TLS connection) to connect to the server even from your mobile client.
Thanks for the information @MaXiM. I did go ahead and set it up with:
From my view, it’s almost like using Basic Auth vs. Modern Auth/OAUTH. My question now is, since I’m using the latest version of Android and mail clients (both Google & Microsoft,) do they not support the secured authentication methods?
By googleing for the supported authentication methods for mobile devices you will notice that most of the mobile mail apps including Gmail Android app do not support modern authentication.
Mostly only have PLAIN, LOGIN and XOAUTH2.
We currently do not support XOAUTH2 and our recommendation is to post it as feature request on our product community page.
