+ Next, install new binaries, config files and libraries by running:
+
+ make upgrade
+
+ This will also prompt you to upgrade your database by running:
+
+ make upgrade-database
+
+ You should back up your database before running this command.
+ When you run it, you will be prompted for your previous version of
+ RT (such as 3.6.4) so that the appropriate set of database
+ upgrades can be applied.
+
+ Finally, clear the Mason cache dir:
+
+ rm -fr /opt/rt4/var/mason_data/obj
+
+ You may then start your web server again.
+
+ 7) Configure the web server, as described in docs/web_deployment.pod,
+ and the email gateway, as described below.
+
+ NOTE: The default credentials for RT are:
+ User: root
+ Pass: password
+ Not changing the root password from the default is a SECURITY risk!
+
+ Once you've set up the web interface, consider setting up automatic
+ logout for inactive sessions. For more information about how to do
+ that, run:
+
+ perldoc /path/to/rt/sbin/rt-clean-sessions
+
+ 8) Set up users, groups, queues, scrips and access control.
+
+ Until you do this, RT will not be able to send or receive email, nor
+ will it be more than marginally functional. This is not an optional
+ step.
+
+ 9) Set up automated recurring tasks (cronjobs):
+
+ To generate email digest messages, you must arrange for the provided
+ utility to be run once daily, and once weekly. You may also want to
+ arrange for the rt-email-dashboards utility to be run hourly. For
+ example, if your task scheduler is cron, you can configure it as
+ follows:
+
+ crontab -e # as the RT administrator (probably root)
+ # insert the following lines:
+ 0 0 * * * /opt/rt4/sbin/rt-email-digest -m daily
+ 0 0 * * 0 /opt/rt4/sbin/rt-email-digest -m weekly
+ 0 * * * * /opt/rt4/sbin/rt-email-dashboards
+
+10) Configure the RT email gateway. To let email flow to your RT
+ server, you need to add a few lines of configuration to your mail
+ server's "aliases" file. These lines "pipe" incoming email messages
+ from your mail server to RT.
+
+ Add the following lines to /etc/aliases (or your local equivalent)
+ on your mail server:
+
+ rt: "|/opt/rt4/bin/rt-mailgate --queue general --action correspond --url http://rt.example.com/"
+ rt-comment: "|/opt/rt4/bin/rt-mailgate --queue general --action comment --url http://rt.example.com/"
+
+ You'll need to add similar lines for each queue you want to be able to
+ send email to. To find out more about how to configure RT's email
+ gateway, type:
+
+ perldoc /opt/rt4/bin/rt-mailgate
+
+ If your webserver uses SSL, rt-mailgate will require several new
+ Perl libraries. RT can detect and install these for you automatically
+ if you include --enable-ssl-mailgate when running configure and then
+ run make fixdeps as described in step 4. It is safe to rerun configure
+ and make fixdeps after you have installed RT, you should be sure to include
+ all the arguments you used in step 2 plus --enable-ssl-mailgate.