I'm new at OSTicket.

Using the latest OSTicket version just implemented yesterday.
Using office365 account with smtp enabled.

When I go to the admin panel -> emails -> add new email and then proceed to change the SMTP settings to:
Status - Enabled
hostname - smtp.office365.com
port - 587
authentication - basic (legacy)

I click on the config button and when I enter my office365 user and password it gives me an error message saying "PROTOCOL REQUIRED"

it works perfectly fine when testing the smtp with a python script

ricardogomez

Disable SMTP and save the hostname/port number first. Then configure the authentication information, save the popup, enable SMTP, and Save Changes.

Cheers.

    ricardogomez

    It’s unable to connect to the given mail server (hostname and port) via TLS. You need to contact your systems administrator or contact you mail provider for further assistance.

    Cheers.

      KevinTheJedi

      Actually this is working when using an osticket install on a local vm

      but when using this install from a digital ocean droplet it doesnt work

      ive also tested using smtp with a python script and everything on that side seems to be working :C

        ricardogomez

        Then you’d need to contact the maker of the digital ocean droplet. As long as the server meets the prerequisites it should be working.

        Cheers.

          ricardogomez

          Are you using a custom self-signed certificate or something? Do you have openssl installed and on the latest version? Do you have a firewall blocking the connection? Is the port open on the server? So many questions.

          Cheers.

          6 months later

          Bumping. :-)

          I'm having the exact same issue.

          Just setup osTicket. v1.17.3 (ca95150)

          I'm using a self-hosted mailcow. Version: 2023-05a with LetsEncrypt certificates that are not expired.

          In fact I just got done configuring and setting up the default "support@" email address in osTicket and confirmed it could login to mailcow just fine:

          Both SMTP and IMAP worked just fine.

          Now I'm in the process of setting up a separate email address.

          And when I go to configure the Outgoing SMTP parameters, using the same hostname, port, and authentication just I just got done configuring for support@ I receive the same "Host, Port, and Protocol Required" as OP received when they opened this thread initially.

          Except, I am the systems administrator :-) and I'm not using a self-signed certificate anywhere. There's no firewall that's blocking IMAP or SMTPS connections and I confirmed that everything was working just fine for the initial support@ configuration, it's only when I've just now gone in to configure a secondary email address where I've run into a problem. :-)

          Would appreciate any thoughts or ideas anyone would have to resolve this.

          Thanks!

            gellenburg

            Save it disabled with no authentication set, set auth back to basic, configure auth info, and try again.

            Cheers.

            Write a Reply...