MarcinZ Delete the email and re-add it and reconfigure it.

bhushan timeout is indicative of deeper issues. You need to check your logs for any related errors. You can also try deleting the email and reading it. Also, you need to be running v1.17.2 and the latest build of the OAuth2 plugin.

Cheers.

        MarcinZ

        URL Rewriting isn’t enabled or configured properly. You need to research older discussions on this on how to get it working with NGINX. A community member posted their working config in an older thread. I don’t remember which discussion it was so you’ll have to do some searching.

        Cheers.

            Is there any update on the "cannot select INBOX, is this a valid transport?". My installation also stopt fetching mails on the 27-december. I have tried a couple of things (removed and added the email adresses in osTicket an removed and added the registration in the microsoft tenant), but nothing seems to have any effect. I can send email with the Microsoft 365 account, but i cant read the emails from the microsof365 accounts.

            I can't disable ipv6 on the server because there a more sites on the same server witch need ipv6. For now i have a little workaround to forward the mails to a external mailbox witch a can read with IMAP.

            Hi Kevin,
            I reset the my web server, and now it is going to authenticate and redirect to login Microsoft after fillup the Microsoft plugin config, I am authenticated with the Azure admin, it time out when redirecting the URL on my server.

              KevinTheJedi
              Thanks Kevin for your help! It did help. I have finished mail configuration. For those who struggle with NGINX rewrite config, you need to add auth in api rewrite rule. Details here
              https://github.com/osTicket/osTicket/issues/6293#issuecomment-1315838614

              But still I can't fetch email's from O365. Diagnostic is able to sent, but emails on INBOX are not processed. Any hint where to start to look? No error in OSTicket log (in debug mode). IPv6 disabled.
              OK. I fixed the problem. In my case bumpy update of our Ubuntu deleted crontab. So task cron.php was not scheduled.

              THX,
              -Marcin

                az68 Honestly - no idea as to why it would suddenly stop supporting IPv6 - perhaps this is something the osTicket devs can look into with Microsoft. From a quick search it seems that IPv6 and Exchange have never gotten on well.. but why it would stop working suddenly over Christmas is strange as my configuration with osTicket worked perfectly prior but it does show a suddent stop at 00:01 on the 27th December 2022.. which is why this issue isn't well documented on here yet.

                What are you hosting on? I may be able to help you disable it. For osTicket and it's various plugins etc. I would recommend wither a VPS or using their hosted model as I have used web-hosting services for it before and had constant issues.. AWS Lightsail is a very cheap way of doing it yourself.

                  I sort of "fixed" it for now by adding outlook.office365.com with a ipv4 adress in the /etc/hosts of the server.

                  Now my osticket installation is retrieving the mails again.

                  I dont know how long this wil work (dont know how static the dns-records are at microsoft)

                  2 months later

                  Hi all,
                  I also get the cannot select INBOX, is this a valid transport? error. I've tried disabling my ipv6 but doesn't seem to do it for me. Are there any new fixes?
                  I use Ubuntu,
                  Osticket v17.1
                  Thanks in advance

                    Joep87

                    Sounds like you authorized using the wrong account. Also, you definitely need to upgrade to v1.17.3 and install the latest build of the OAuth2 plugin. Once you do this Delete the current token, visit osTicket in an incognito/private window, login as an admin, go to the email authentication config popup, submit the email config popup, when it brings you to MS authenticate as the email you are configuring in osTicket, consent if it asks, and then you should be good. Otherwise you'd need to make sure IMAP is enabled for the email address in Exchange.

                    If you do all of that and still run into issues it's likely an issue with the app registration or OAuth2 config. If this is the case you'll need to follow the documentation in thorough detail:

                    Cheers.

                      I found a solution! I used pop3 instead of imap and it worked!

                      Write a Reply...