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?
Many thanks,
Steve.
Stephen Ison
Unix Support
University of Cambridge Computing Service si202@cam.ac.uk
(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.)
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?