I’ve been able to do an upgrade, keeping our old database. The web
interface is up and running, but I’m still hung up on the mailgate…
How do the mail aliases work with different queues? On our old server,
mail was sent to different queues by addressing the message to
rt-queue@myrthost. Now, only rt@myrthost works. Here’s my mailgate
symlink in
/etc/smrsh:
rt-mailgate -> /usr/local/rt/bin/rt-mailgate
Mail still comes into the system this way, and I can assign each
incoming message to a queue, but no matter what queue I assign it to, or
even if I don’t assign it to a queue at all, responses to the requestor
are not sent through. I can’t find anything in maillog or messages
reporting any problem with sending mail, either… Clues?
Read RT’s readme. it describes what you need to put in your /etc/aliases.On Fri, Jan 12, 2001 at 05:51:25PM -0500, Neil Curri wrote:
Hello,
I’ve been able to do an upgrade, keeping our old database. The web
interface is up and running, but I’m still hung up on the mailgate…
How do the mail aliases work with different queues? On our old server,
mail was sent to different queues by addressing the message to
rt-queue@myrthost. Now, only rt@myrthost works. Here’s my mailgate
symlink in
/etc/smrsh:
rt-mailgate → /usr/local/rt/bin/rt-mailgate
Mail still comes into the system this way, and I can assign each
incoming message to a queue, but no matter what queue I assign it to, or
even if I don’t assign it to a queue at all, responses to the requestor
are not sent through. I can’t find anything in maillog or messages
reporting any problem with sending mail, either… Clues?
You’ll need an alias like the following for action requests:
rt-action: |"/path/to/rt/bin/rt-mailgate general action"
What is an “action”… is there a list of choices?
Thanks,
-Neil
Jesse wrote:
Read RT’s readme. it describes what you need to put in your /etc/aliases.
On Fri, Jan 12, 2001 at 05:51:25PM -0500, Neil Curri wrote:
Hello,
I’ve been able to do an upgrade, keeping our old database. The web
interface is up and running, but I’m still hung up on the mailgate…
How do the mail aliases work with different queues? On our old server,
mail was sent to different queues by addressing the message to
rt-queue@myrthost. Now, only rt@myrthost works. Here’s my mailgate
symlink in
/etc/smrsh:
rt-mailgate → /usr/local/rt/bin/rt-mailgate
Mail still comes into the system this way, and I can assign each
incoming message to a queue, but no matter what queue I assign it to, or
even if I don’t assign it to a queue at all, responses to the requestor
are not sent through. I can’t find anything in maillog or messages
reporting any problem with sending mail, either… Clues?
You’ll need an alias like the following for action requests:
rt-action: |"/path/to/rt/bin/rt-mailgate general action"
What is an “action”… is there a list of choices?
“action” can be replaced by either “comment” or “correspond” in /etc/aliases.
An ‘action’ queue ignores any plain text in the incoming message (I
think you get an error). The subject line of the message must
reference an actual, existing case in the database. This is only
useful for using the “email command interface” of RT (the %RT
commands).
A ‘comment’ queue treats the plain text in the incoming message as a
comment, as if you had entered a new comment in the web interface. As
with ‘action’ arguments, the subject must reference an existing
case on which you are commenting.
A ‘correspond’ queue treats the plain text in the incoming message as
a reply (i.e., sends a message to the requestor as well as queue
members). If the subject line of the message does not reference an
case in the database, then a new case is created – if allowed by the
queue – using the information in the email (requestor is read from
the “From:” line, etc.).
I’m trying to get a handle on RT to use for my employer’s IT support.
According to ‘perldoc /opt/rt3/bin/rt-mailgate’:
‘… you will need first of all to create an RT user for the mail
gateway and assign it a password; this helps to ensure that mail coming
into the web server did originate from the gateway.’
I’m not at all clear on what this represents. Is it a single user
within RT that recieves all email directed at the system like help@rt.example.com? Am I missing something fundamental here?
I’m trying to get a handle on RT to use for my employer’s IT support.
According to ‘perldoc /opt/rt3/bin/rt-mailgate’:
‘… you will need first of all to create an RT user for the mail
gateway and assign it a password; this helps to ensure that mail coming
into the web server did originate from the gateway.’
I’m not at all clear on what this represents. Is it a single user
within RT that recieves all email directed at the system like help@rt.example.com? Am I missing something fundamental here?
I created a user ‘help’ on my test system ( http://rt.paulororke.net )
and have the following in /etc/aliases:
help: "|/opt/rt3/bin/rt-mailgate --queue general --action
correspond --url http://rt.paulororke.net/"
rt-comment: "|/opt/rt3/bin/rt-mailgate --queue general --action
comment --url http://rt.paulororke.net/"
the pipe seems valid in that rt-mailgate is where it says it is, the
queue exists within RT and the URL resolves. When I send mail (from
gmail) to help@rt.paulororke.net, POSTFIX replies (bounced mail):
Final-Recipient: rfc822; help@rt.paulororke.net
<mailto:help@rt.paulororke.net>
Action: failed
Status: 5.0.0
Diagnostic-Code: X-Postfix; mail for rt.paulororke.net
<http://rt.paulororke.net> loops back to myself
/var/log/maillog says:
Jul 19 10:54:21 paulororke postfix/smtp[15720]: 86778123757:
to=<help@rt.paulororke.net>, relay=none, delay=1, status=bounced
(mail for rt.paulororke.net loops back to myself)
Any suggestions on how to solve this?
Labonte, Phil wrote:
Yes basically that is it…
If you look at /etc/aliases that is where you assign which user you
designate as the one the receives the emails (rt by default).
I’m trying to get a handle on RT to use for my employer’s IT support.
According to ‘perldoc /opt/rt3/bin/rt-mailgate’:
‘… you will need first of all to create an RT user for the mail
gateway and assign it a password; this helps to ensure that mail coming
into the web server did originate from the gateway.’
I’m not at all clear on what this represents. Is it a single user
within RT that recieves all email directed at the system like help@rt.example.com? Am I missing something fundamental here?