Oh man I’m sure this is a RTFM/PEBCAK error…
When I reply to a mail-submitted ticket in RT the reply-to address is
"www-data@rt.foo.com" instead of "support@rt.foo.com".
And yes I know www-data is the apache user in the httpd.conf … Still doesn’t
make sense why RT is using that vs. the address I specified for the queue.
Anyone?
( you’know, a name would be nice. )
Oh man I’m sure this is a RTFM/PEBCAK error…
When I reply to a mail-submitted ticket in RT the reply-to address is
“www-data@rt.foo.com” instead of “support@rt.foo.com”.And yes I know www-data is the apache user in the httpd.conf … Still doesn’t
make sense why RT is using that vs. the address I specified for the queue.
MTA (sendmail most likely) problem. See ‘Trusted User’ in MTA
configuration, and add ‘www-data’ to it if required.
Bruce Campbell RIPE
Systems/Network Engineer NCC
www.ripe.net - PGP562C8B1B Operations
Thanks for the reply Bruce, though I think I may have confused the issue.
Here is my desired setup:
Someone mails RT for assistance
RT takes the mail and drops it in the correct queue
An RT user replies to the request for assistance.
The reply is mailed back to the person that requested assistance.
The person who requested assitance can simply reply to the message and it
gets added to the current ticket or goes back into the queue.
It’s the last step that won’t work because they are replying to mail that is
from “www-data@rt.foo.com”.
PS: I’m not allowed to tie my organization into anything so that’s why it’s
all anonymous.On January 30, 2002 04:39 pm, you wrote:
On Wed, 30 Jan 2002, RT2 Troubles wrote:
( you’know, a name would be nice. )
Oh man I’m sure this is a RTFM/PEBCAK error…
When I reply to a mail-submitted ticket in RT the reply-to address is
“www-data@rt.foo.com” instead of “support@rt.foo.com”.And yes I know www-data is the apache user in the httpd.conf … Still
doesn’t make sense why RT is using that vs. the address I specified for
the queue.MTA (sendmail most likely) problem. See ‘Trusted User’ in MTA
configuration, and add ‘www-data’ to it if required.
Pardon my creative rearranging of replies for readability:On Wed, 2002-01-30 at 17:04, RT2 Troubles wrote:
On January 30, 2002 04:39 pm, Bruce Campbell wrote:
MTA (sendmail most likely) problem. See ‘Trusted User’ in MTA
configuration, and add ‘www-data’ to it if required.[…] It’s the last step that won’t work because they are replying to
mail that is from “www-data@rt.foo.com”.
Right. Bruce was pointing out that it’s a problem with your Mail
Transport Agent (MTA) not trusting the apache user (www-data) and
therefore not allowing the apache user to send mail with headers
claiming to be some other user (support@rt.foo.com).
He was suggesting that you check out how to add the apache user to your
MTA’s trusted users, which would solve your problem.
Cheers!
–j
Jim Meyer, Geek At Large purp@wildbrain.com
Pardon my creative rearranging of replies for readability:
nearly 2am my time mind 
MTA (sendmail most likely) problem. See ‘Trusted User’ in MTA
configuration, and add ‘www-data’ to it if required.[…] It’s the last step that won’t work because they are replying to
mail that is from “www-data@rt.foo.com”.Right. Bruce was pointing out that it’s a problem with your Mail
Transport Agent (MTA) not trusting the apache user (www-data) and
therefore not allowing the apache user to send mail with headers
claiming to be some other user (support@rt.foo.com).He was suggesting that you check out how to add the apache user to your
MTA’s trusted users, which would solve your problem.
This does have some problems in the long term, in that any process
running as www-data (ie, from your web server) can send mail masquarading
as any address. ( I’m not that good with long explanations when I’m
excessively tired ).
With the latest spate of spam mail spewing forth from web → email scrips,
having your web server with this ability isn’t something you want to
operate an exposed web server with.
Its better, imo, to run the RT web server as a seperate user, as this
contains any problems.
Bruce Campbell RIPE
Systems/Network Engineer NCC
www.ripe.net - PGP562C8B1B Operations