• [deleted]

  • Post #1

When I'm setting something up to use my on prem Exchange server for email I've always used https://mail.domain.com for the hostname. When I use that with osTicket I'm getting an error:

Failed to connect to https://mail.domain.com:25 [SMTP: Failed to connect socket: Unable to find the socket transport "https" - did you forget to enable it when you configured PHP? (code: -1, response: )]

extension=php_openssl.dll is not commented out in my php.ini file. I've tried entering mail.domain.com, tcp://mail.domain.com, and ssl://mail.domain.com. All give me a different error.

I can login to my owa at https://mail.domain.com just fine. Is there a setting within PHP that I'm missing to allow this?

      • [deleted]

      • Post #3

      KevinTheJedi I tried that before and it was throwing a "no supported authentication methods" error. Just tried it again and set it to no authentication required and it's working now. I appreciate ya!! have a great weekend!!

          [deleted]

          Well that’s no good. You have to use authentication unless you’re using relaying. What are you using as the port number?

          Cheers.

              as way of an explanation
              https://mail.domain.com is not a hostname, it is a web URL.
              hostnames do not include a protocol at the beginning.
              Technically mail is the host name, and domain.com is the domain name.
              The two together form a FQDN (Fully Qualified Domain Name).
              You would use mail.domain.com for mail settings.

              • [deleted]

              • Post #7

              KevinTheJedi Sorry about the lack of response on my part. I didn't get a notification that you had replied. I'm using port 25.

                  [deleted]

                  Okay yea you can’t do authentication on that port as that’s relay. I would suggest using SMTP + Authentication via port 587 (TLS) or 465 (SSL) unless you prefer relaying.

                  Cheers.

                      • [deleted]

                      • Post #9

                      KevinTheJedi Gotcha. I assumed I needed to use port 25. I just double checked to make sure I'm not open relayed and I'm not. Had me a bit worried there! lol I appreciate ya kind sir!!

                        Write a Reply...