J
Jsezze

  • 6 hours ago
  • Joined Aug 17, 2023
  • 5 best answers
  • muhammadriyas

    The only reasons a reply wouldn't be sent to the user via email are:

    You mail provider could also be very well rate-limiting or throttling outbound messages. Some hosts/providers have certain daily limits, etc. When in doubt reach out to your mail provider.

    There are just too many unknowns here. You would need to investigate and debug deeper to see where exactly this is failing.

    Cheers.

  • Thanks to all of you. I solved the problem by simply doing a PHP upgarde and removing and resetting all permissions. I don't think it had anything to do with PHP, but a clean permissions distribution might help. Anyway, if anyone get the same case in the future need to clean all permissions and set them clear again. Please check if the php.ini setup is as following as well:

    Check as well if the web server still does not have write access to the temp directory. Simply upload a PHP file to the web server and display the (temp_dir)

    Then write the following code in the file:

    _<?php
    echo 'upload_tmp_dir = ' . ini_get('upload_tmp_dir') . "\n";_

    The temp directory used path should then be displayed as following:

    This is a default directory. If you want you can as well set your own folder.

  • Jsezze

    Thank you! I was able to solve the problem. It was a combination of a configuration issue and our mailserver setup.

    vitweb Problem solved! After digging into the database I realised that the tickets DO get created. But they get the wrong department ID and don't show up in the frontend because of that. There is a second department configured that we no longer use (at least at the moment) so noone could see them.

    I checked the config for the mail addresses, the correct department was selected. The issue was laying within the mail address. Our mail addresses always get an alias address with another domain (or maybe the addresses we use are actually the aliases, I don't know). The configured address was the one with the other domain so osTicket always placed the incoming mails in the first department it could find because the mail address did not match.

    Maybe it would be helpful to add a second field to the configuration where we can add alias addresses that the system also checks?

  • Jsezze

    You’d have to check all possible logs on the server, browser, etc. to see what it’s complaining about.

    Cheers.

  • VomS

    Have new Tickets go to a specific Department that only has the Supervisor in it. Then the once the supervisor approves they can transfer the Ticket to another Department with the other Agents in it.

    Cheers.

  • Thanks kevin yeah thats exactly it just wanted to share, not for sale or anything of the sort. If i decide to make a package out of it even for free i will do it on github or my own site. Appreciate the heads up on rules and the understanding. I compared some stuff i had written in 2009 to the current version, wow its like a whole rewrite so many improvements, that is so awesome.. 🙂

    @Jsezze none of that is done yet, i was just sharing for now, if i make it a full fledge theme package i will do it in another venue, but so much to be done yet regardless. 🙂

    • Jsezze

      It’s not required but it’s good to fill that out to ensure best functionality.

      Cheers.

    • Jsezze If you enable the autologin you can do that, and I'm pretty sure that link only works once.
      I don't use it, and don't recommend it.

      In what I said you use the email address as the username and the ticket number acts as a password.
      It's not particularly secure, but not insecure either as you need two pieces of information to log in.

    • You can configure your webserver however you want to configure your webserver.
      Kevin is right that this is not related to osTicket but to your apache2 configuration.
      You probably have the default website still running.

    • Jsezze

      This is not an osTicket issue; this is a webserver configuration issue. You need to look at guides online on how to block direct access via IP in the webserver rules, add webserver rules to redirect to the hostname, or add webserver rules to show a specific error code/page when accessing via IP.

      Edit:
      I would recommend adding an HTTP -> HTTPS redirect rule so all connections to any point on the server is forced to HTTPS (secure connection).

      Cheers.