tnolan

I would recommend moving the mail out of the folder and test some new mail. Do you see anything in your system logs? Can you run cron manually to see if it spits out any errors?

Cheers.

    Kevin,

    Thank you for the quick reply.
    So, I've removed the emails. Ran the cron manually and no dice, rebooted server as well for the heck of it.
    Additionally and interestingly, it's not loading any new errors in the log.

    I've also actually removed the banlist entry and put the original php files back into place.
    Additionally with no luck on the emails. I'm thoroughly confused now as to why emails will not pull through.
    There's got to be something stuck in somewhere, but I can't seem to locate it.

      tnolan

      Check if the email is able to authenticate successfully by clicking Save Changes under Admin Panel > Emails > Emails > click the email in question. Also, check to make sure email fetching is enabled at the email level (in an email's Remote Mailbox tab) as well as the system level (Admin Panel > Emails > Settings > Email Fetching).

      Cheers.

        Kevin,

        Good call on the Save Changes under the account. It claimed that the token had expired, so it made me refresh the login and confirm 2FA. All set and emails are now working.
        Thank you so much. Cannot express how helpful that was!

        Further into the API 403 error, is the banlist the root cause of the OP topic?
        Or is it related to bad email/ui accounts? I'm just interested in the error and further diagnosing. Thank you again.

          tnolan

          Banlist or a Ticket Filter. When any mail is rejected by either method it causes an issue with the rest of the emails in that batch. You can apply the linked pull request as well as the one below and it should resolve the rejected mail causing subsequent mail to not be fetched issue.

          Cheers.

            a month later

            I think that today we hit the same problem here.
            Investigation in progress.
            We will back with results soon.

            19 days later

            Hello KevinTheJedi ,

            I have applied your patch and it is working fine.
            But it cause another problem. In Admin Dashboard, we can not see logs anymore.

            I have checked the logs and it gives the following error:

            AH01071: Got error 'PHP message: PHP Fatal error: Declaration of ContentAjaxAPI::log($id) must be compatible with ApiController::log($title, $msg, $level = LOG_WARN) in /var/www/vhosts/XXX/xxx.xxx.com/V1.17.2/include/ajax.content.php on line 22', referer: https://xxx.xxx.com/V1.17.2/scp/logs.php

            How can I fix that?
            I have attached the screenshot of the issue as well.

                Hi KevinTheJedi ,

                I have applied the changes from this Commit "https://github.com/osTicket/osTicket/pull/6381".
                It fixed one issue but caused others.

                e.g. Logs are not working properly.

                Now I saw the API is also not working.

                So I added the change you committed on the 6399 and it works fine.

                I want to know is there any other Issue I should be aware of?

                Thanks

                    upervaiz

                    There will always be some sort of bug which is why we make new releases 😉

                    We are releasing today (hopefully) so the majority of bugs will be addressed. Stay tuned!

                    Cheers.

                      Write a Reply...