Hi,
Firstly many thanks to all who helped me get RT up and running. After
spending the day playing with it I am very impressed, and it should do
nicely for what I need.
One small niggle I’ve spotted is that if I go in as root and reassign an
issue to another person that person doesn’t get notified by email.
I have made some changes to the scrips but I don’t think I have removed
this.
OnCreate AutoreplyToRequestors with template Autoreply
OnCreate NotifyAdminCcs with template Transaction
OnCorrespond NotifyOwner with template AdminCorrespondence
OnComment NotifyRequestorsAndCcs with template Correspondence
OnComment NotifyOtherRecipientsAsComment with template Correspondence
OnCorrespond NotifyOtherRecipients with template Correspondence
OnStatus NotifyRequestors with template StatusChange
OnCorrespond NotifyRequestorsAndCcs with template Correspondence
OnResolve NotifyRequestorsAndCcs with template Resolved
OnComment NotifyOwner with template AdminComment
One possible clue is this from the maillog:
Jul 16 18:00:14 etg-dev sendmail[11327]: NOQUEUE: etg-dev.cam.pace.co.uk
[136.170.131.70] (may be forged) did not issue MAIL/EXPN/VRFY/ETRN during
connection to MTA
Any thoughts?
Neil.
That shouldn’t work by default. You’d need the “OnOwnerChange” scrip
from RT-Addons for that feature.
O- ~ARK
One small niggle I’ve spotted is that if I go in as root and reassign an
issue to another person that person doesn’t get notified by email.
You wish to have the following Scrips on your queue:
OnOwnerChange NotifyOwnerAsComment with template Give
OnOwnerChange NotifyOldOwner with template Steal
The extra ScripCondition and ScripAction can be transferred from:
http://www.fsck.com/pub/rt/contrib/2.0/OwnerChange/
http://www.fsck.com/pub/rt/contrib/2.0/NotifyOldOwner/
Bruce Campbell RIPE
Systems/Network Engineer NCC
www.ripe.net - PGP562C8B1B Operations/Security
One small niggle I’ve spotted is that if I go in as root
and reassign an
issue to another person that person doesn’t get notified by email.
You wish to have the following Scrips on your queue:
OnOwnerChange NotifyOwnerAsComment with template Give
OnOwnerChange NotifyOldOwner with template Steal
The extra ScripCondition and ScripAction can be transferred from:
http://www.fsck.com/pub/rt/contrib/2.0/OwnerChange/
http://www.fsck.com/pub/rt/contrib/2.0/NotifyOldOwner/
Thanks. I’ve installed them, and my rules now look like this, but no mail
is being sent.
OnOwnerChange NotifyOldOwner with template Steal
OnOwnerChange NotifyOwner with template Give
OnOwnerChange NotifyRequestors with template Steal
There is nothing in the sendmail logs. RT isn’t logging anything. I have
lots of zero byte files in my log dir.
Neil.
Hello!
Before you install the scrips you should check in the
source code if the path settings are correct
- to the perl interp.
- to the modules
The second isssue with the log file is probably a problem
with the right management. Look which user or group your
web server is running and allow the web server user/group
to write files in the directory.
okay hope this help
bye!Am Mit, 2002-07-17 um 11.04 schrieb Neil Bingham:
One small niggle I’ve spotted is that if I go in as root
and reassign an
issue to another person that person doesn’t get notified by email.
You wish to have the following Scrips on your queue:
OnOwnerChange NotifyOwnerAsComment with template Give
OnOwnerChange NotifyOldOwner with template Steal
The extra ScripCondition and ScripAction can be transferred from:
http://www.fsck.com/pub/rt/contrib/2.0/OwnerChange/
http://www.fsck.com/pub/rt/contrib/2.0/NotifyOldOwner/
Thanks. I’ve installed them, and my rules now look like this, but no mail
is being sent.
OnOwnerChange NotifyOldOwner with template Steal
OnOwnerChange NotifyOwner with template Give
OnOwnerChange NotifyRequestors with template Steal
There is nothing in the sendmail logs. RT isn’t logging anything. I have
lots of zero byte files in my log dir.
Neil.
rt-users mailing list
rt-users@lists.fsck.com
http://lists.fsck.com/mailman/listinfo/rt-users
Have you read the FAQ? The RT FAQ Manager lives at http://fsck.com/rtfm
Sven Sternberger Tel.: +49 (0) 40 8998 4397
Desy Email: sven.sternberger@desy.de
Notkestr. 85
D-22607 Hamburg
Sven Sternberger wrote:
The second isssue with the log file is probably a problem
with the right management. Look which user or group your
web server is running and allow the web server user/group
to write files in the directory.
Nope, lots of empty logfiles is normal operation. 
If scrips are failing, try increasing the logging level.
Look in config.pm for $LogToScreen and $LogToFile.
Sven Sternberger wrote:
The second isssue with the log file is probably a problem
with the right management. Look which user or group your
web server is running and allow the web server user/group
to write files in the directory.
Nope, lots of empty logfiles is normal operation.
If scrips are failing, try increasing the logging level.
Look in config.pm for $LogToScreen and $LogToFile.
Thanks. I figured out the problem with the scips not running.
I’ll look into the logging
Neil.