[rt-users] rt-mailgate and web authentication.

[Roedel, Mark]

We got around this by including a valid username and password in the URL
that gets passed to rt-mailgate in the aliases file.  Our aliases look
like

rt: "|/usr/local/rt3/bin/rt-mailgate --queue General --action correspond
--url http://username:password@rt.server.hostname/"

(that's all on one line, of course).  (And the rt-mailgate software does
seem to correctly pull sender information from the incoming message to
correctly attribute replies to the correct user.)


--
Mark Roedel
Web Programmer / Analyst
LeTourneau University


-----Original Message-----
From: rt-users-bounces at lists.bestpractical.com
[mailto:rt-users-bounces at lists.bestpractical.com] On Behalf Of Steve
Ison
Sent: Thursday, October 21, 2004 10:21 AM
To: rt-users at lists.bestpractical.com
Subject: [rt-users] rt-mailgate and web authentication.

Dear All,
I have RT 3.2.2 running on Suse 9.1 pro/apache2-2.0.49-27.16 using 
exim as the MTA, I'm also using external web authentication.

My problem is that when a user replies to the automatically generated RT
message to update their request apache doesn't know who the rt-mailgate
is 
($REMOTE_USER is not set) and blocks access, They get a bounced mail 
message with a 404 page not found error.

Is there some way of allowing rt-mailgate to access apache without 
disabling the web authentication?