Hi all,
after fiddeling around some days as an rt-newbie I would now ask for
some help to increase my learning curve.
I (currently) have mainly two questions:
-
mail setup
According to the docs (Draft, April 13, 2003; perldoc rt-mailgate):
“Note that you don’t have to run your RT server on your mail server,
as the mail gateway will happily relay to a different machine.”
If I install rt on server A and the mail gateway for our LAN is
server B, does this mean that I also have to install the program
rt-mailgate (and the needed perl modules to make it happy) on
mailserver B? Does it work standalone without the rt installation on
B?
-
localizing templates
What is the most appropriate method to localize the templates? When I
create a new ticket in my nicely localized rt-webinterface, I get the
autoreply template in english.
As we have a multilingual environment in our research institute I
don’t simply want to change this template via the web interface
(Configure->Global->Templates) into another language. Every user
should get his localized template according to his configured
language.
Or did I get some configuration details completely wrong?
Thanks in advance
Helmut
Helmut Lichtenberg heli@tzv.fal.de Tel. +49 (0)5034/871-128
Institut f�r Tierzucht 31535 Neustadt Germany
Helmut Lichtenberg wrote:
Hi all,
after fiddeling around some days as an rt-newbie I would now ask for
some help to increase my learning curve.
I (currently) have mainly two questions:
-
mail setup
According to the docs (Draft, April 13, 2003; perldoc rt-mailgate):
“Note that you don’t have to run your RT server on your mail server,
as the mail gateway will happily relay to a different machine.”
If I install rt on server A and the mail gateway for our LAN is
server B, does this mean that I also have to install the program
rt-mailgate (and the needed perl modules to make it happy) on
mailserver B? Does it work standalone without the rt installation on
B?
You have to move rt-mailgate script to server B. Server B must have perl
with Getopt::Long and LWP::UserAgent modules.
Also server B should have ability of connect to Server A via HTTP.
- localizing templates
What is the most appropriate method to localize the templates? When I
create a new ticket in my nicely localized rt-webinterface, I get the
autoreply template in english.
As we have a multilingual environment in our research institute I
don’t simply want to change this template via the web interface
(Configure->Global->Templates) into another language. Every user
should get his localized template according to his configured
language.
For me it’s dark topic right now. 3.0.{9,10} has work on it, but still
as I think it’s not finished to be full featured, yet.
after fiddeling around some days as an rt-newbie I would now ask for
some help to increase my learning curve.
I (currently) have mainly two questions:
- mail setup
According to the docs (Draft, April 13, 2003; perldoc rt-mailgate):
“Note that you don’t have to run your RT server on your mail server,
as the mail gateway will happily relay to a different machine.”
If I install rt on server A and the mail gateway for our LAN is
server B, does this mean that I also have to install the program
rt-mailgate (and the needed perl modules to make it happy) on
mailserver B? Does it work standalone without the rt installation on
B?
You have to move rt-mailgate script to server B. Server B must have perl
with Getopt::Long and LWP::UserAgent modules.
Also server B should have ability of connect to Server A via HTTP.
Thanks, this brought me some steps forward. But now another problem
occurs. When I send mail to some of the aliases on the mail server, I
get the following error in the logs:
Mar 19 08:22:11 dcs postfix/local[15079]: DD93523426D: to=service@tzv.local,
relay=local, delay=3, status=deferred (temporary failure. Command output:
Connecting to http://service.tzv.local//REST/1.0/NoAuth/mail-gateway at
/usr/local/sbin/rt-mailgate line 444, <> chunk 1.
An Error Occurred ================= 401 Authorization Required
This is /usr/local/sbin/rt-mailgate exiting because of an undefined server
error at /usr/local/sbin/rt-mailgate line 492, <> chunk 1. )
And on the rt server side I get a log entry:
10.1.0.1 - - [19/Mar/2004:08:22:11 +0100] “POST //REST/1.0/NoAuth/mail-gateway HTTP/1.1” 401 483 “-” “libwww-perl/5.64”
I found a thread about exactly this problem on rt-users (May 2003). It
ended with this hint from Jesse:>On Fri, May 09, 2003 at 09:37:51AM -0500, Christian Gilmore wrote:
On the second suggestion, allowing the gateway to pass
unauthenticated, how does that fit with the documentation in the
rt-mailgate POD? I am confused where/why/how the mailgate should
authenticate to the web interface? It is a new concept for RT3, and
I’m just not quite getting it yet.
It doesn’t and shouldn’t. there’s code in the mail gateway client to
support it. but it’s not needed. What is needed is to have whatever http
auth system you use pass through requests for the NoAuth path the
mailgate client calls. Just tell apache not to require auth for that
path.
Can somebody tell me, how this should look like (in httpd.conf I guess)?
We also use external authentication via LDAP.
TIA
Helmut
Helmut Lichtenberg heli@tzv.fal.de Tel. +49 (0)5034/871-128
Institut f�r Tierzucht 31535 Neustadt Germany
It doesn’t and shouldn’t. there’s code in the mail gateway client to
support it. but it’s not needed. What is needed is to have whatever http
auth system you use pass through requests for the NoAuth path the
mailgate client calls. Just tell apache not to require auth for that
path.
Can somebody tell me, how this should look like (in httpd.conf I guess)?
We also use external authentication via LDAP.
ok, I found it in a later post on rt-users:
<LocationMatch “/NoAuth”>
Satisfy Any
Allow from all
Would be nice, if this could be included into the docs. This would
reduce lots of redundant questions (and answers) on the mailing list.
Is wiki the appropriate place for this?
Helmut
Helmut Lichtenberg heli@tzv.fal.de Tel. +49 (0)5034/871-128
Institut f�r Tierzucht 31535 Neustadt Germany
- localizing templates
What is the most appropriate method to localize the templates? When I
create a new ticket in my nicely localized rt-webinterface, I get the
autoreply template in english.
As we have a multilingual environment in our research institute I
don’t simply want to change this template via the web interface
(Configure->Global->Templates) into another language. Every user
should get his localized template according to his configured
language.
For me it’s dark topic right now. 3.0.{9,10} has work on it, but still
as I think it’s not finished to be full featured, yet.
I’m using rt-3.0.10pre2. Despite of ‘not finished yet’, is there
already anything usable?
Another localization topic:
How are the names of queues (RT) and classes (RTFM) localizeable? Or
does it make no sense as the contents of tickets and articles are fixed
to one (common) language in a multilingual environment anyway?
Helmut
Helmut Lichtenberg heli@tzv.fal.de Tel. +49 (0)5034/871-128
Institut f�r Tierzucht 31535 Neustadt Germany
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1On Mar 19, 2004, at 4:47 AM, Helmut Lichtenberg wrote:
On Fri, Mar 19, 2004 at 08:49:17AM +0100, Helmut Lichtenberg wrote:
It doesn’t and shouldn’t. there’s code in the mail gateway client to
support it. but it’s not needed. What is needed is to have whatever
http
auth system you use pass through requests for the NoAuth path the
mailgate client calls. Just tell apache not to require auth for that
path.
Can somebody tell me, how this should look like (in httpd.conf I
guess)?
We also use external authentication via LDAP.
ok, I found it in a later post on rt-users:
<LocationMatch “/NoAuth”>
Satisfy Any
Allow from all
Would be nice, if this could be included into the docs. This would
reduce lots of redundant questions (and answers) on the mailing list.
Is wiki the appropriate place for this?
Indeed it is. Thanks!
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (Darwin)
iD8DBQFAWxQZQaM/s3DrrJARAqw/AKDJmX+Ds3On9ebWBtsYR36nXqTIjgCeK7LZ
8n9KyBHhL1AONff7/F7zBng=
=coI9
-----END PGP SIGNATURE-----
Another localization topic:
How are the names of queues (RT) and classes (RTFM) localizeable? Or
does it make no sense as the contents of tickets and articles are fixed
to one (common) language in a multilingual environment anyway?
We’ve set up RT for multiple languages, one queue per language. Custom
fields are used to sort the tickets in each queue.
For each language we’ve set up a corresponding RTFM class for
stock/templated answers. We have tens and in some cases hundreds per
language. I’ve built a pop-up window enable searching or browsing stock
answers. It is heavily customized (e.g. custom fields, message formats,
etc.) to our environment though, and uses a lot of Javascript - not sure if
it would be applicable to the core RT code base.
Ed