Hi all,
At present, unless I’m completely off the mark here, RT sends emails
out to all users, with the exception of the user who initiated the
email. If there any way to make sure that when an email is sent, it
is sent to all watchers, requesters, etc. regardless of whether it
is them that initiated the email?
If not, I’m gonna have to start hacking code (something I want to
avoid, if possible)
thanks,
Greg
You have to hack code for that at this point.On Wed, Oct 17, 2001 at 01:27:36PM +1000, Greg Boug wrote:
Hi all,
At present, unless I’m completely off the mark here, RT sends emails
out to all users, with the exception of the user who initiated the
email. If there any way to make sure that when an email is sent, it
is sent to all watchers, requesters, etc. regardless of whether it
is them that initiated the email?If not, I’m gonna have to start hacking code (something I want to
avoid, if possible)thanks,
Greg
rt-users mailing list
rt-users@lists.fsck.com
http://lists.fsck.com/mailman/listinfo/rt-users
http://www.bestpractical.com/products/rt – Trouble Ticketing. Free.
Hi all,
At present, unless I’m completely off the mark here, RT sends emails
out to all users, with the exception of the user who initiated the
email. If there any way to make sure that when an email is sent, it
is sent to all watchers, requesters, etc. regardless of whether it
is them that initiated the email?If not, I’m gonna have to start hacking code (something I want to
avoid, if possible)
What you can do (which is fun) is to create an e-mail alias on the server
that contains the e-mail addresses of all the watchers you want, and just
set that e-mail address as the only watcher.
Obviously, this only works well with smaller-sized numbers of
watchers. We’ve got it set up that way for our abuse queue, and it works
just well with eight people.
What you can do (which is fun) is to create an e-mail alias on the server
that contains the e-mail addresses of all the watchers you want, and just
set that e-mail address as the only watcher.Obviously, this only works well with smaller-sized numbers of
watchers. We’ve got it set up that way for our abuse queue, and it works
just well with eight people.
I’d love to see a script, if anyone has one, to rotate, for example,
an on-call email address to point to different email addresses
on different days. Our staff members carry pagers that have email
addresses, and it would be really handy to have a single email
address point to different people at different times.
srl
Shane Landrum (srl AT boston DOT com) Software Engineer, boston.com
Working with a clean install of 3.6.3 on FC 7, running into a problem
with outgoing email. Using the default config of sendmail pipe.
Scrip 6, which is the default send email to requester, is failing with
error: no recipients found. This was with email coming from a internal
account that also has an account in RT. Looking at the full headers
showed no To: field, so I can see why the SendEmail package is failing
to find a recipient. The user that send does show as having a valid
email in their user profile.
Testing with unknown (to RT), local account on the linux server: a
response did go out and full headers looked normal in the ticket.
Any idea why the outgoing mail might be failing to correctly generate
a recipient?
Steve
A little more info. Did some additional testing and a second account
that was known to RT but wasn’t “privileged” received a response
correctly.
Is there any differences how the system would respond to a request
generated by a “privileged” user?
SteveOn Jan 8, 2008, at 2:54 PM, Steve Cochran wrote:
Working with a clean install of 3.6.3 on FC 7, running into a
problem with outgoing email. Using the default config of sendmail
pipe.Scrip 6, which is the default send email to requester, is failing
with error: no recipients found. This was with email coming from a
internal account that also has an account in RT. Looking at the full
headers showed no To: field, so I can see why the SendEmail package
is failing to find a recipient. The user that send does show as
having a valid email in their user profile.Testing with unknown (to RT), local account on the linux server: a
response did go out and full headers looked normal in the ticket.Any idea why the outgoing mail might be failing to correctly
generate a recipient?Steve
SAVE THOUSANDS OF DOLLARS ON RT SUPPORT:
If you sign up for a new RT support contract before December 31,
we’ll take
up to 20 percent off the price. This sale won’t last long, so get in
touch today. Email us at sales@bestpractical.com or call us at +1
617 812 0745.Community help: http://wiki.bestpractical.com
Commercial support: sales@bestpractical.comDiscover RT’s hidden secrets with RT Essentials from O’Reilly
Media.Buy a copy at http://rtbook.bestpractical.com
Think we solved it. If you respond to a ticket that you generated the
request for, it doesn’t send you mail. Is that correct?
SteveOn Jan 8, 2008, at 4:20 PM, Steve Cochran wrote:
A little more info. Did some additional testing and a second account
that was known to RT but wasn’t “privileged” received a response
correctly.Is there any differences how the system would respond to a request
generated by a “privileged” user?Steve
On Jan 8, 2008, at 2:54 PM, Steve Cochran wrote:
Working with a clean install of 3.6.3 on FC 7, running into a
problem with outgoing email. Using the default config of sendmail
pipe.Scrip 6, which is the default send email to requester, is failing
with error: no recipients found. This was with email coming from a
internal account that also has an account in RT. Looking at the
full headers showed no To: field, so I can see why the SendEmail
package is failing to find a recipient. The user that send does
show as having a valid email in their user profile.Testing with unknown (to RT), local account on the linux server: a
response did go out and full headers looked normal in the ticket.Any idea why the outgoing mail might be failing to correctly
generate a recipient?Steve
SAVE THOUSANDS OF DOLLARS ON RT SUPPORT:
If you sign up for a new RT support contract before December 31,
we’ll take
up to 20 percent off the price. This sale won’t last long, so get
in touch today. Email us at sales@bestpractical.com or call us at
+1 617 812 0745.Community help: http://wiki.bestpractical.com
Commercial support: sales@bestpractical.comDiscover RT’s hidden secrets with RT Essentials from O’Reilly
Media.Buy a copy at http://rtbook.bestpractical.com
SAVE THOUSANDS OF DOLLARS ON RT SUPPORT:
If you sign up for a new RT support contract before December 31,
we’ll take
up to 20 percent off the price. This sale won’t last long, so get in
touch today. Email us at sales@bestpractical.com or call us at +1
617 812 0745.Community help: http://wiki.bestpractical.com
Commercial support: sales@bestpractical.comDiscover RT’s hidden secrets with RT Essentials from O’Reilly
Media.Buy a copy at http://rtbook.bestpractical.com
Look into NotifyActor. I bet if you set it to 1, in RT_SiteConfig.pm, it’ll
do what you want.On Jan 8, 2008 3:26 PM, Steve Cochran stephen.cochran@kingarthurflour.com wrote:
Think we solved it. If you respond to a ticket that you generated the
request for, it doesn’t send you mail. Is that correct?Steve
On Jan 8, 2008, at 4:20 PM, Steve Cochran wrote:
A little more info. Did some additional testing and a second account
that was known to RT but wasn’t “privileged” received a response
correctly.Is there any differences how the system would respond to a request
generated by a “privileged” user?Steve
On Jan 8, 2008, at 2:54 PM, Steve Cochran wrote:
Working with a clean install of 3.6.3 on FC 7, running into a
problem with outgoing email. Using the default config of sendmail
pipe.Scrip 6, which is the default send email to requester, is failing
with error: no recipients found. This was with email coming from a
internal account that also has an account in RT. Looking at the
full headers showed no To: field, so I can see why the SendEmail
package is failing to find a recipient. The user that send does
show as having a valid email in their user profile.Testing with unknown (to RT), local account on the linux server: a
response did go out and full headers looked normal in the ticket.Any idea why the outgoing mail might be failing to correctly
generate a recipient?Steve
SAVE THOUSANDS OF DOLLARS ON RT SUPPORT:
If you sign up for a new RT support contract before December 31,
we’ll take
up to 20 percent off the price. This sale won’t last long, so get
in touch today. Email us at sales@bestpractical.com or call us at
+1 617 812 0745.Community help: http://wiki.bestpractical.com
Commercial support: sales@bestpractical.comDiscover RT’s hidden secrets with RT Essentials from O’Reilly
Media.Buy a copy at http://rtbook.bestpractical.com
SAVE THOUSANDS OF DOLLARS ON RT SUPPORT:
If you sign up for a new RT support contract before December 31,
we’ll take
up to 20 percent off the price. This sale won’t last long, so get in
touch today. Email us at sales@bestpractical.com or call us at +1
617 812 0745.Community help: http://wiki.bestpractical.com
Commercial support: sales@bestpractical.comDiscover RT’s hidden secrets with RT Essentials from O’Reilly
Media.Buy a copy at http://rtbook.bestpractical.com
SAVE THOUSANDS OF DOLLARS ON RT SUPPORT:
If you sign up for a new RT support contract before December 31, we’ll
take
up to 20 percent off the price. This sale won’t last long, so get in touch
today.
Email us at sales@bestpractical.com or call us at +1 617 812 0745.Community help: http://wiki.bestpractical.com
Commercial support: sales@bestpractical.comDiscover RT’s hidden secrets with RT Essentials from O’Reilly Media.
Buy a copy at http://rtbook.bestpractical.com