Re: [rt-users] RT Not Sending Autoreply E-Mails On Ticket Creation Via E-Mail
Am 24.09.2015 um 23:42 schrieb Tim Gustafson: > I think the problem is that NotifyActor is set to 0; when I changed it > to 1, the e-mail originator got their autoreply. But it seems to me > that an autoreply should go out, even if NotifyActor is set to 0. Did > something change around that option recently? This is the difference between the Notify* actions, which respects the NotifyActor setting, and the "Autoreply To Requestors" action, which sends always an auto reply regarding of the NotifyActor setting. The screen shot of your scrips shows, that you only user the Notify* actions and don't have a script which uses the "Autoreply To Requestors" action. The "On Create Autoreply To Requestors" scrip [1], which is created on RT installation, is missing. Chris [1] https://github.com/bestpractical/rt/blob/stable/etc/initialdata#L759-L762
Re: [rt-users] RT Not Sending Autoreply E-Mails On Ticket Creation Via E-Mail
> Set the log level to debug, and compare the output of creating a ticket in > the UI and via email. Heres the config I use: Here's what I see: Committing scrip #5 on txn #28447 of ticket #1938 (/usr/local/lib/perl5/site_perl/RT/Scrips.pm:290) Calling SetRecipientDigests for transaction RT::Transaction=HASH(0x81294e168), id 28447 (/usr/local/lib/perl5/site_perl/RT/Action/SendEmail.pm:624) Working on mailfield To; recipients are (/usr/local/lib/perl5/site_perl/RT/Action/SendEmail.pm:640) So that last line is the one that's odd; the "recipients are" part seems to suggest that there should be a recipient listed there, but it's not. Here's the same section for a ticket created via the web: Committing scrip #5 on txn #28453 of ticket #1939 (/usr/local/lib/perl5/site_perl/RT/Scrips.pm:290) Calling SetRecipientDigests for transaction RT::Transaction=HASH(0x813452d68), id 28453 (/usr/local/lib/perl5/site_perl/RT/Action/SendEmail.pm:624) Working on mailfield To; recipients are t...@ucsc.edu (/usr/local/lib/perl5/site_perl/RT/Action/SendEmail.pm:640) I think the problem is that NotifyActor is set to 0; when I changed it to 1, the e-mail originator got their autoreply. But it seems to me that an autoreply should go out, even if NotifyActor is set to 0. Did something change around that option recently? -- Tim Gustafson Technical Lead, Baskin School of Engineering t...@ucsc.edu 831-459-5354 Baskin Engineering, Room 313A
Re: [rt-users] RT Not Sending Autoreply E-Mails On Ticket Creation Via E-Mail
On 9/23/15 2:01 PM, Tim Gustafson wrote: I have an RT 4.2.11 instance that is not sending autoreply messages when tickets are created via e-mail. If you create a ticket on behalf of a user through the web form, an autoreply is sent. It's only when a ticket is created via e-mail that an autoreply is not sent. The Sendmail log file shows no attempt to send an autoreply, and no outbound e-mail is recorded in the ticket's transaction history. Hi Tim, Set the log level to debug, and compare the output of creating a ticket in the UI and via email. Heres the config I use: Set($LogToFile, 'debug'); Set($LogDir, '/opt/rt4/var/log'); Set($LogToFileNamed, 'rt.log'); Regards,
[rt-users] Adding HTML comment with a scrip
Hello, I am trying to add a comment as a scrip with some html tags. For example: $self->TicketObj->Comment(Content=> "Hello", Type=>'text/html'); The "Type" parameter does not seem to do anything though. Is it not possible to add comments as HTML using a scrip? Thanks.
Re: [rt-users] Internal server error Can't locate RT/Ex.pm solved
On 09/23/2015 06:11 PM, Jonathan Murray wrote: Folks, I'm running: RT 4.2.9 CentOS 6.7 httpd-2.2.15-47.el6.centos.x86_64 when I go to the rt URL: Internal Server Error The server encountered an internal error or misconfiguration and was unable to complete your request. Please contact the server administrator, root@localhost and inform them of the time the error occurred, and anything you might have done that may have caused the error. More information about this error may be available in the server error log. Apache/2.2.15 (CentOS) Server at rtdev.whoi.edu Port 443 I checked /opt/rt4/var/log and discovered that I needed something called [1920] [Wed Sep 23 20:33:11 2015] [critical]: Can't locate RT/Authen/ExternalAuth.pm in @INC (@INC contains: /opt/rt4/sbin/../local/lib /opt/rt4/sbin/../lib /usr/local/lib64/perl5 /usr/local/share/perl5 /usr/lib64/perl5/vendor_perl /usr/share/perl5/vendor_perl /usr/lib64/perl5 /usr/share/perl5 .) at /opt/rt4/sbin/../lib/RT.pm line 729. (/opt/rt4/sbin/../lib/RT.pm:388) so I got that via cpan> install RT::Authen::ExternalAuth seemed to work OK. Restarted the web server, Then I got this: [3160] [Wed Sep 23 21:39:04 2015] [critical]: Can't locate RT/Extension/ActivityReports.pm in @INC (@INC contains: /opt/rt4/sbin/../local/lib /opt/rt4/local/plugins/RT-Authen-ExternalAuth/lib /opt/rt4/sbin/../lib /usr/local/lib64/perl5 /usr/local/share/perl5 /usr/lib64/perl5/vendor_perl /usr/share/perl5/vendor_perl /usr/lib64/perl5 /usr/share/perl5 .) at /opt/rt4/sbin/../lib/RT.pm line 729, line 755. (/opt/rt4/sbin/../lib/RT.pm:388) I was able to get that install in /opt/rt4/local/plugins/RT-Extension-ActivityReports/lib/RT/Extension/ActivityReports.pm Now I'm looking for something called Ex.pm [3414] [Wed Sep 23 21:55:08 2015] [critical]: Can't locate RT/Ex.pm in @INC (@INC contains: /opt/rt4/sbin/../local/lib /opt/rt4/local/plugins/RT-Authen-ExternalAuth/lib /opt/rt4/local/plugins/RT-Extension-ActivityReports/lib /opt/rt4/sbin/../lib /usr/local/lib64/perl5 /usr/local/share/perl5 /usr/lib64/perl5/vendor_perl /usr/share/perl5/vendor_perl /usr/lib64/perl5 /usr/share/perl5 .) at /opt/rt4/sbin/../lib/RT.pm line 729, line 755. (/opt/rt4/sbin/../lib/RT.pm:388) Can someone direct me to a place where I can download that? I can't seem to find that specific module anywhere. Also, if I can get that installed, is there a way to make sure that I can get all the dependencies associated with it? Or is the normal mode to just keep chasing each one individually. Happy to do that, or (most)anything to get this running. Sorry, absolute beginner here. Thank you, Jonathan This was a typo in /opt/rt4/etc/RT_SiteConfig.pm carriage return truncated the plugins line. Set( @Plugins, qw(RT::Authen::ExternalAuth RT::Extension::ActivityReports RT::Extension::CommandByMail) );
Re: [rt-users] Output contents of Custom field via command line
You could write your own script. It's not that bad.
Or perhaps try a dashboard, though those would email about the contents.
On Sep 23, 2015 11:58 PM, "Yourevilness" wrote:
> Hello, RT 4.2.11 on Centos 6
>
> I'm trying to generate a list of all unresolved tickets via command line
> and
> output the contents of a custom field value to a log file. I have another
> system checking this log file to verify the contents.
>
> Without going too far into the requirements. Is there any way to do this?
>
> I've tried RT-Crontool (Via Mysql), RT CLI queries etc. I can find the
> tickets ID but cannot extract the correct information I am after.
>
>
> CLI - /opt/rt4/bin/rt list -i "status != 'resolved' AND (Queue =
> 'Operations')"
> #This gives me a list of the tickets.
> /opt/rt4/bin/rt show -t ticket 265550 -f 'CF.{A Number}'
> #This gives me the contents of the custom field called "A number"
>
> I cannot seem to combine them into one command.
>
> Likewise with rt-crontool... I can gather the necessary ticket ID's but
> cannot get any further information.
>
> I am aware of the REST interface and its ability to do what I am after, but
> I've not had much luck with it creating issues with the Mysql process.
>
>
>
> --
> View this message in context:
> http://requesttracker.8502.n7.nabble.com/Output-contents-of-Custom-field-via-command-line-tp60701.html
> Sent from the Request Tracker - User mailing list archive at Nabble.com.
>
Re: [rt-users] Migration from MySQL to PostreSQL - corrupt characters (german umlaut)
I have the same problem. I want to migrate my RT 4.2.12 mysql-database to postgres. Did you find an solution for this problem? I noticed that the problem with the german umlauts is not in all fields. In my history for example the german umlauts displayed correctly but in the ticket subject they didn't. On Wed, Sep 23, 2015 at 5:34 PM, Frank Wissink wrote: > Did find any solution for this problem? I have the same problem. > > > > Am 21.09.2015 um 16:22 schrieb Maik Nergert : > > >> I'm now testing to serialize mysql and import to mysql again. > > > > This is working, so it's a problem with Pg > > >
