Yum install rt tracker

To enable external access to RT, open web server port on firewall. Hence, execute the command below to open port 80 on firewall. If using a custom port, be sure to open the port on firewall and specify the port using rt-server script above. Access RT from browser to proceed with configuration. Click Next to create RT database and database user. Ensure you provide credentials for administrative user.

Click Next to customize your RT with the most basic configurations needed to get it up and running. Once the database is initialized, click Finish installation to complete the setup. Note that RT is still running on standalone mode. Logging in RT is controlled from SiteConfig configuration file. However, we are going to configure RT logging to a file in this guide. At the end of configuration files, insert the following lines making appropriate changes as per your environment setup. Use root as the username and password configured while setting up RT.

This is an unofficial installation guide. It may be outdated or apply only to very specific configurations and versions. This is a setup for a RT mail dispatcher using sendmail and procmail. It is based on the assumption that you use one domain for all your RT queues, e. You can always change it to be a RT queue as well. You'll have rt installed in no time Note: Depending upon which Perl modules you had installed in the past, you may have to update before installing via yum.

If a whole lot of dependency errors display when you run yum install, then type the following:. Run the following command. This will take some time. If you have gotten this far, well done! You will need the database password you set earlier for this. You need to give RT the ability to process email and generate support tickets. Read on:. Add the exchange mailbox username and password that you obtained for RT use.

Save this file and set the following permissions:. Now you need to create some procmail rules for RT. But you want to make sure there are filters in place to aviod ticket duplication and to prevent unauthorised users mailing in and creating tickets.

Once you have created your rules you need to ensure the RT mailgate is called after the rules have been processed. At the bottom of. Now, to get fetchmail to start fetching, you must add a crojob to do so for the RT user not root :. Fetchmail should now be fetching mail, filtering with procmail, then passing to the RT mailgate.

You might, for example, have messages to support go into the service queue, and abuse go into the ops queue. You can have more than one set of aliases point to the same queue, if, for example, you wanted mail to both abuse and security both go to the ops queue.

The queue name may have spaces. These sendmail's will only execute programs as alias targets which have been blessed by placing them in a special directory. You'll choose from "--action correspond" and "--action comment" depending on whether the mail should be resent to the requestor. If you want the requestor to see it, choose correspond; if you want to keep it from the requestor, choose comment. If you're using sendmail be sure to install the sendmail-cf package to facilitate the changes that follow.

You may find your installation defaults to not accepting external mail. If this is the case, to accept mail from other sources you need to remove the loopback restriction directive from the sendmail configuation. To do this, modify the following in sendmail. Stop and start your mail server, so it picks up your configuration changes. Change the password.

The default root password for the web interface is password, as installed.