-
How do you setup RT to automatically parse incoming email, and convert
it automatically to a ticket? I couldn’t find the documentation or the
link in regards to this functionality.
-
The pages or interface for RT is supposely easy to configure. I was
wondering if it is easy it to convert the queue page back into the RT
1.0 format. The current 2.0 format does not contain the priority column
or the convenient sort arrows, which I found very useful.
So I actually tried to install RT 1.07 instead, but I had problems with
the install. I suspect it has to do with only mod_perl compiled into
Apache, and that I may need mod_cgi or some other module. Overall, I
decided to go back to RT 2.0 since I essentially need something up and
runnning fairly soon.
Again, any help or suggestions would be welcomed. Thanks!
Gary
|+ How do you setup RT to automatically parse incoming email, and convert
|+ it automatically to a ticket? I couldn’t find the documentation or the
|+ link in regards to this functionality.
Did you read the README file included with the RT distribution? From the README:
SETTING UP THE MAIL GATEWAY
An alias for the initial queue will need to be made in either your
global mail aliases file (if you are using NIS) or locally on your
machine.
Add the following lines to /etc/aliases (or your local equivalent) :
rt: “|/path/to/rt2/bin/rt-mailgate --queue general --action correspond”
rt-comment: “|/path/to/rt2/bin/rt-mailgate --queue general --action comment”
| |
----/ |
|
<correspond or comment depending on whether |
the mail should be resent to the requestor>—/
Then, say you have a queue called ‘service’ and you create an email address for
this queue (service@yourdomain.com). You would just do:
service: “|/path/to/rt2/bin/rt-mailgate --queue service --action correspond”
and when any email is sent to service@yourdomain.com; a ticket will either be
generated, or an existing ticket will contain the contents.