Deather
the title says "SMTP Server not sending emails after changing internet provider" that means the IP address might have changed and maybe a firewall or something blocking it or you may need to add IP to relay.

      Daedalus01

      Not sure, if I were you I'd contact Gmail and raise hell. There should be no reason for that. As you can see below I still have the option to disable/enable 2FA as well as add/remove App Passwords.

      Maybe you need to login as the account administrator, go to the admin console, and allow App Passwords for specific accounts?

      Cheers.

        Daedalus01 Well Leave it to Google. Maybe its because I had 2FA enabled before the push. I disabled 2FA, re-enabled it still using my Yubikey and now app passwords are back. Didn't think to try that until now since other people were saying they still had app passwords. I figured Google just made it a hard decision.

          ramrajone Hi, we have checked the Google workspace admin console aswell the firewall and the IP addresses and ports are all allowed. We just ran a test using the smtp on a Xerox scanner with the App password generated before and it sent the email of the scan pefectly. But when we try and use the same configuration on OsTicket it just does not work at all. Also, we tried using smtp-relay.gmail.com, and that worked flawlesly on the scanner, but yet again with no success on OsTicket

              Deather Host not found usually means DNS issues. By shared host I think ( but not certain) that he is asking if you are using a shared hosting platform for this.

                Deather

                I’m asking if you use a shared hosting platform or if this is is a sever you host in house. If you use shared host they typically have SMTP restrictions. If this is the case you’d need to reach out to your hosting provider to have them lift the restrictions.

                Since that domain can’t be found (it’s a completely valid domain from Google) it appears you are having network/DNS issues on your server. You need to resolve your network/dns issues and you should be good.

                Cheers.

                  ramrajone

                  I don't know how in the world smtp.gmail.com is working for IMAP for you. I've never seen that before. Typically it's imap.gmail.com.

                  Cheers.

                      KevinTheJedi
                      that's how I have always been using it and never had any issues
                      I think it's because Gmail uses the same server for IMAP and SMTP and I am setting IMAP Port 993.
                      Name: smtp.gmail.com
                      Addresses: 2607:f8b0:4004:c06::6c
                      172.253.63.108

                      Name: imap.gmail.com
                      Addresses: 2607:f8b0:4004:c17::6c
                      2607:f8b0:4004:c17::6d
                      142.251.163.108
                      142.251.163.109

                          ramrajone

                          That's very weird of them then lol Why don't they have just mail.gmail.com or something generic if it's like that? 🤣

                          Cheers.

                            ramrajone Not sure how you are seeing that they are using the same server for smtp. and imap. Those are completely different IPv6 and IPv4 addresses and I get different ones than you. My guess would be is that both sets of ports are open on each server and then the backend routes it correctly. I agree with @KevinTheJedi though, they could just have a mail.gmail.com and be done.

                              5 days later

                              Hello everyone, after a while we managed to solve our issue. Our main issue was the HELO. No matter what host we picked, it always said HELO error. So I found a workaround and now the system is working flawlessly.
                              What I did is, got inside the OSticket folder, got into the Include folder and then into the Pear folder. Then went inside the Mail folfer. There I found a file called SMTP.php. I edit the file, to be more specific, the line 134

                              That is what the file said by default. I changed the string from localhost to “computername.domainname.com” (The FQDN) and now it just works.
                              Thank everyone for your help! Hope this helps someone else too!

                              2 years later

                              It seems like the issue may be related to your SMTP configuration after switching providers. Double-check the SMTP server settings in OSticket, including authentication, port, and encryption methods. If you recently changed your ISP, ensure they are not blocking the SMTP ports or IP. Try reaching out to DigitalAka or Mailgun for further troubleshooting.

                                Write a Reply...