F
fnasti

  • Nov 29, 2022
  • Joined Sep 5, 2022
  • 0 best answers
  • In Two Factor Authentication v1.17RC3 Problem

    Hello Kevin, do you have some more suggestions or check/tests to do trying to solve the issue above?
    Thank you again

    • In Two Factor Authentication v1.17RC3 Problem

      Thank you Kevin ...
      I checked out the changes you pointed at ... and they already were in our installation.
      I've also downloaded again the 2FA plugin, uninstalled and reinstalled it, but it still reports the same version (0.3) ... so I guess we've already had the last version.
      Nonetheless, it seems the situation has not changed.
      In the User Profile page I still can select and configure only the Email verification option.

      Thanks for your help
      Cheers

    • In Two Factor Authentication v1.17RC3 Problem

      I follow this thread because i noticed 2FA plugin is not working in 1.17.RC4 (i didn't test this feature in RC3)
      The plugin seems to correctly install in the Manage - Plugins panel, though then nothing changes in the Default 2FA menu in the User profile: only the Email option appears and not the Authenticator option ...

      Tried to uninstall and reinstall the plugin but nothing changes.

      Using Apache2 + php8.0

      Thanks

      • In Reject Action filter: API Error (403) Ticket denied and mail not deleted

        As an added information:

        The following is the cron log when the API error (403) appears in the System Logs Dashboard

        (403) Ticket denied
        PHP Fatal error: Uncaught Error: Call to undefined method osTicket\Mail\Fetcher::getHost() in /var/www/html/include/class.mailfetch.php:105

        So we've tried to comment out the above line and then the cron log only reports
        (403) Ticket denied

        and the following message appears in the System Logs Dashboard
        Mail Fetcher Excessive errors processing emails for 1/2. Please manually check the inbox.

        I guess the point is:
        why this Mail Fetcher Error occurs only when the Reject filter is applied?

        Thank you

        • In Reject Action filter: API Error (403) Ticket denied and mail not deleted

          Yes, when a ticket by email is rejected by a Filter the relative email is not deleted from the mailbox and some warnings/errors appears

          As I said other tickets, even with others filters active (to set Department based on email address for example), are working as expected and the emails are deleted from the mailbox.

          • In Reject Action filter: API Error (403) Ticket denied and mail not deleted

            We noticed a wrong behaviour on Reject Action filtered tickets both in RC3 and in RC4 (not tested previous RC versions).

            We have Apache2 + php 8.0
            We have setup accounts, remote mailbox and fetching configuration and everything is working fine (email fetched, tickets created, email deleted as per configuration)

            We have setup a filter as follow
            Filter Name -> Undelivered Reject
            Execution Order -> 1
            Stop processing further on match
            Filter status -> Active
            Target channel -> Email

            Filter Rules
            Ticket/Issue Summary Contains "Undelivered Mail Returned to Sender"
            Filter Actions
            Reject Ticket

            We sent an email with "Undelivered Mail Returned to Sender" as subject to the above email account already configured and tested.

            The Filter works as expected as the ticket is not created and the System Logs dashboard reports the following message:
            Ticket denied Ticket rejected (....@....) by filter "Undelivered Reject"
            So far so good ...

            Issues are:

            • one more message appears in the System Logs (and also in the cron error logs sent to local mail user www-data)
              API Error (403) Ticket denied
            • the email in the mailbox results as "seen" but is not deleted
            • following cron executions (every 5 minutes as per our configuration) then continue to process the same email showing the same messages until the email is deleted from mailbox "by hand"

            We reproduced the same configuration and steps on a 1.15.8 installation and the behaviour is as expected (only first warning message in System Logs dashboard, email correctly deleted from mailbox, ...)
            Here we have apache2 + php 7.4
            Hope to have been clear ... and somehow useful to improve the excellent work the community is doing here.

            Thanks