Re: [rt-users] Having RT ignore internal email not associated with a ticket
On Mon, Apr 11, 2011 at 02:52:33PM -0400, Paul Fincher wrote: >Hi all, > > > >We are getting ready to bring RT live and are passing the final > hurdles. One issue that I >am working through is the following. We are adding RT to already existing > mail aliases which >our support engineers currently monitor for incoming customer requests. > The problem is they >also sometimes use these aliases for internal communication unrelated to a > specific ticket. >I was hoping to have RT ignore these internal emails not related to a > ticket. From what I've >seen in past posts I may be out of luck but just thought I'd see if > someone had any ideas. How do you intend to differentiate between "not related to a ticket" and "intended to create a new ticket" since emails sent to rt-mailgate without a subject tag create new tickets in the given queue (assuming permissions are configured to allow it). You'll need to filter before rt-mailgate gets the email -kevin pgplNLXJSzlen.pgp Description: PGP signature
Re: [rt-users] Forcing a custom field to be a mandatory date
On Mon, Apr 11, 2011 at 11:12:13AM -0700, Kenneth Crocker wrote: >2) If on 3.8.8+, you can make the CF a "SelectDate" field and get the use > of Calendar. The SelectDate field that you are referencing is a third party patch with known problems and we cannot advise that you use it. We have reimplemented this feature properly for RT4 -kevin >However, there is no "built-in" way to make the field mandatory unless you > add some of your >own code. This has been discussed in past threads. We choose to keep the > basic code and work >around the problem by writing a scrip to use another CF and re-set the > Status field (to >"stalled" when they "resolve" without setting the date field) and then > send email >notifications to alert the ticket owners that they need to put in the date > field). This is a >bit simple, but keeps us from messing with code. However, there are some > other options >discussed that modify the RT code and allow the CF to be treated as a > "TRULY" mandatory field. >Check out the threads. I believe there is even a link to some of that code. > >Hope this helps. > >Kenn >LBNL > >On Mon, Apr 11, 2011 at 6:30 AM, Vance Walsh > <[1]vance_wa...@concordacademy.org> wrote: > > What would be the proper string to make a Custom field Mandatory and > contain a date field? > --- > Vance Walsh > Network and Systems Administrator > Concord Academy - Concord, Mass. > pgpVPKrkyJHGb.pgp Description: PGP signature
Re: [rt-users] Having RT ignore internal email not associated with a ticket
--- On Mon, 4/11/11, Paul Fincher wrote: From: Paul Fincher Subject: [rt-users] Having RT ignore internal email not associated with a ticket To: rt-users@lists.bestpractical.com Date: Monday, April 11, 2011, 11:52 AM Hi all, We are getting ready to bring RT live and are passing the final hurdles. One issue that I am working through is the following. We are adding RT to already existing mail aliases which our support engineers currently monitor for incoming customer requests. The problem is they also sometimes use these aliases for internal communication unrelated to a specific ticket. I was hoping to have RT ignore these internal emails not related to a ticket. From what I've seen in past posts I may be out of luck but just thought I'd see if someone had any ideas. Thanks in advace,Paul - Paul Fincher Senior Engineering Support Engineer When the original email is sent to create a ticket, it looks like any other email. Subsequent tickets would contain a special subject unique to RT. But that original email would always get into RT, and RT would not be able to determine if that email was intended for RT or not.However, you could write a perl interceptor which sits between RT and sendmail/postfix (ie: directly in the /etc/aliases file) which looks for a certain string of characters. If the email does not contain this string, it passes it into RT; if the email does contain this string, it drops it. So, if the email contained something like: RT-IGNORE, then the perl script could ignore that message without piping it into RT.You would just need to make sure people include that RT-IGNORE in the body or the subject if RT is to ignore it.Maybe RT already has something in place to do this? Not sure..
[rt-users] Having RT ignore internal email not associated with a ticket
Hi all, We are getting ready to bring RT live and are passing the final hurdles. One issue that I am working through is the following. We are adding RT to already existing mail aliases which our support engineers currently monitor for incoming customer requests. The problem is they also sometimes use these aliases for internal communication unrelated to a specific ticket. I was hoping to have RT ignore these internal emails not related to a ticket. >From what I've seen in past posts I may be out of luck but just thought I'd see if someone had any ideas. Thanks in advace, Paul - Paul Fincher Senior Engineering Support Engineer Green Hills Software - http://www.ghs.com http://www.ghs.com/> 34125 US Hwy 19 North Suite 100 Palm Harbor, FL 34684 (727) 781-4909 - This e-mail may contain Green Hills Software Proprietary and Confidential information, and is intended only for the named recipient(s) above. If you have received this message in error, or are not a named recipient(s), you are hereby notified that any dissemination, distribution or copying of this e-mail is strictly prohibited. If you have received this message in error, please immediately notify the sender by return e-mail and delete this e-mail message from your computer. Thank you.
Re: [rt-users] Finding tickets based on changed field
Vance, I don't think you can do that with standard RT-SQL. I would imagine you could do it directly from the DB via SQL by looking at the "LastUpdated" date field of the OBJECTCUSTOMFIELDVALUES table. Kenn LBNL On Mon, Apr 11, 2011 at 6:32 AM, Vance Walsh wrote: > Is there a method to find all tickets which have had a custom field > edited/changed in the last 30 days? > > --- > > Vance Walsh > Network and Systems Administrator > Concord Academy - Concord, Mass. > >
Re: [rt-users] Forcing a custom field to be a mandatory date
Vance, Well, there are a few vastly different ways to do this: 1) If on rt 3.6.x, you can use any of these formatting sequences: # for format control of "mm/dd/" (?#Date mm/dd/)^(((0)?[1-9]|1[0-2])\/((0)?[1-9]|[12][0-9]|3[01])\/([12][0-9])?[0-9][0-9])?$ # for format control of "/mm/dd hh:mi:ss" (?#Date /mm/dd hh:mi:ss)^(([1-2][0-9][0-9][0-9])\/(0[1-9]|1[0-2])\/(0[1-9]|[1-2][0-9]|3[0-1]) (0[1-9]|1[0-2]):(0[1-9]|1[0-2]):(0[1-9]|1[0-2]))?$ # for format control of "/mm/dd" (?#Date /mm/dd)^(([1-2][0-9][0-9][0-9])\/(0[1-9]|1[0-2])\/(0[1-9]|[1-2][0-9]|3[0-1]))?$ 2) If on 3.8.8+, you can make the CF a "SelectDate" field and get the use of Calendar. However, there is no "built-in" way to make the field mandatory unless you add some of your own code. This has been discussed in past threads. We choose to keep the basic code and work around the problem by writing a scrip to use another CF and re-set the Status field (to "stalled" when they "resolve" without setting the date field) and then send email notifications to alert the ticket owners that they need to put in the date field). This is a bit simple, but keeps us from messing with code. However, there are some other options discussed that modify the RT code and allow the CF to be treated as a "TRULY" mandatory field. Check out the threads. I believe there is even a link to some of that code. Hope this helps. Kenn LBNL On Mon, Apr 11, 2011 at 6:30 AM, Vance Walsh wrote: > What would be the proper string to make a Custom field Mandatory and > contain a date field? > > --- > > Vance Walsh > Network and Systems Administrator > Concord Academy - Concord, Mass. > >
Re: [rt-users] RT::Authen::ExternalAuth, Possible Configuration Issue?
Original Message From: rt-users-boun...@lists.bestpractical.com [mailto:rt-users-boun...@lists.bestpractical.com] On Behalf Of Thomas Sibley Sent: Monday, April 11, 2011 11:06 AM To: rt-users@lists.bestpractical.com Subject: Re: [rt-users] RT::Authen::ExternalAuth,Possible Configuration Issue? > On 04/11/2011 12:43 PM, Eli Guzman wrote: >> On the pastebin you may also notice that there is a message when >> httpd services are initializing stating that "RT's GnuPG libraries >> couldn't successfully read your configured GnuPG home directory" >> and thereupon Disables PGP support for RT. Could this have something >> to do with the RT::Authen::ExternalAuth error? > > Nope, this is completely unrelated to ExternalAuth. > >> If there is anything else I can try please let me know. > > Please send the output of: ls -lR > /opt/rt3/local/plugins/RT-Authen-ExternalAuth/html/Callbacks/ > > Thomas Hey Thomas, Here it is: http://pastebin.com/raw.php?i=U3a8gde4 I think I see where you are going, maybe the permissions under the: _/autohandler, _/Elements/Header directories could be incorrect? Thanks, Eli
Re: [rt-users] RT::Authen::ExternalAuth, Possible Configuration Issue?
On 04/11/2011 12:43 PM, Eli Guzman wrote: > On the pastebin you may also notice that there is a message when httpd > services are initializing > stating that "RT's GnuPG libraries couldn't successfully read your > configured GnuPG home directory" > and thereupon Disables PGP support for RT. Could this have something to > do with the > RT::Authen::ExternalAuth error? Nope, this is completely unrelated to ExternalAuth. > If there is anything else I can try please let me know. Please send the output of: ls -lR /opt/rt3/local/plugins/RT-Authen-ExternalAuth/html/Callbacks/ Thomas
Re: [rt-users] RT::Authen::ExternalAuth, Possible Configuration Issue?
Original Message From: rt-users-boun...@lists.bestpractical.com [mailto:rt-users-boun...@lists.bestpractical.com] On Behalf Of Kevin Falcone Sent: Monday, April 11, 2011 8:00 AM To: rt-users@lists.bestpractical.com Subject: Re: [rt-users] RT::Authen::ExternalAuth, Possible Configuration Issue? >> [Fri Apr 8 23:34:13 2011] [debug]: Attempting to use external auth >> service: My_LDAP >> (/opt/rt3/local/plugins/RT-Authen-ExternalAuth/lib/RT/Authen/ExternalA >> ut h.pm:64) >> [Fri Apr 8 23:34:13 2011] [debug]: SSO Failed and no user to test >> with. Nexting > > This implies that the username you typed into the login box isn't > getting to the plugin. > > You did clear the mason cache when you updated the module, right? > > -kevin Hey Kevin, No I did not clear the cache at that time, so I made sure to do so now: [root@xx ~]# rm -fr /opt/rt3/var/mason_data/obj [root@xx ~]# rm -rf /opt/rt3/var/mason_data/* And then restarted httpd services, this goes ok, and once again I get the same message: http://pastebin.com/raw.php?i=kme8CUdk All of the "ExternalAuth" messages listed on the pastebin came up as I opened the browser, with our designated test domain user named "jjdoe". On the pastebin you may also notice that there is a message when httpd services are initializing stating that "RT's GnuPG libraries couldn't successfully read your configured GnuPG home directory" and thereupon Disables PGP support for RT. Could this have something to do with the RT::Authen::ExternalAuth error? [Mon Apr 11 16:30:02 2011] [debug]: RT's GnuPG libraries couldn't successfully read your configured GnuPG home directory (/opt/rt3/var/data/gpg). PGP support has been disabled /opt/rt3/bin/../lib/RT/Config.pm:449) If there is anything else I can try please let me know. Thanks, Eli
Re: [rt-users] Problem delivering email messages to RT queues
After finally finding some time for looking into /var/log/maillog and some googling, I found out, not surprisingly, that I had modified the system after all and messed the configuration myself. The reason in this case was that I had configured Apache to use https instead of http. And I didn't remember that also rt-mailgate uses http/https to communicate with RT. Thus I had to modify all URL:s in /etc/aliases to reflect the change and run newaliases at command prompt. I also restarted postfix, as I'm not sure if the change comes into effect without it. Rgds, Tapio Tirkkola CSolutor Oy Lähettäjä: Tapio Tirkkola Lähetetty: 7. huhtikuuta 2011 12:13 Vastaanottaja: 'rt-users@lists.bestpractical.com' Aihe: Problem delivering email messages to RT queues Hi I'm confused as I noticed that email messaged destined to create or update tickets in RT seem to do nothing anymore. I've had this configuration work properly before but suddenly it doesn't work anymore. And - yes, as so often - I don't know that anything would have been changed in the system. I use postfix on my RT host. So far I have verified, that email is still successfully delivered to my local mailbox on the RT host, both from my work mail (internally) and from my private mail (from public internet). Thus it seems that there is no general mail delivery problem to accounts in my RT email domain. However, messages to email addresses in the same email domain that match my RT queues don't seem to receive anything. At least messages don't appear in RT as new or updated tickets. And I don't get any responses like "Undeliverable..." like I do in case I try to send to a completely non-existing email address in the same domain. To me it looks like there's something funny in how RT receives the messages. Can anyone give hints how to troubleshoot this kind of a problem? E.g. is there a way to check postfix logs or something whether the messages have been received and maybe find out what happened to them? Or is there a way in RT to troubleshoot incoming email messages? Regards, Tapio Tirkkola tapio.tirkk...@csolutor.fi
Re: [rt-users] Asset Tracker 2.0 Rest API
Dustin, I'll have to review the REST interface. No updates were made to it in the 2.0 release. My guess would be that it is currently lacking. The best place to discuss Asset Tracker is on the at-users mailing list: http://groups.google.com/group/at-users -Todd On Mon, Apr 11, 2011 at 10:14 AM, Dustin Berube wrote: > My apologizes if this is the wrong list to ask this question. Does the new > version of Asset Tracker have a REST API or does it utilize the REST > interface naively in RT? I need to integrate the data from Asset Tracker > with a third party application and the REST interface would be the easiest. > > I'm currently running RT 3.8.9 and AT 2.0.0b1. > > Thanks, > Dustin >
[rt-users] Asset Tracker 2.0 Rest API
My apologizes if this is the wrong list to ask this question. Does the new version of Asset Tracker have a REST API or does it utilize the REST interface naively in RT? I need to integrate the data from Asset Tracker with a third party application and the REST interface would be the easiest. I'm currently running RT 3.8.9 and AT 2.0.0b1. Thanks, Dustin
Re: [rt-users] Rest API search by email?
On 04/10/2011 10:12 AM, elekistvan wrote: > I think I found it out, I sent a ticket with my problem: > http://issues.bestpractical.com/Ticket/Display.html?id=17076 Next time you create a ticket, please set your email address as the requestor so we can contact you about it. I've replied there. Thomas
Re: [rt-users] RT::Authen::ExternalAuth, Possible Configuration Issue?
> [Fri Apr 8 23:34:13 2011] [debug]: Attempting to use external auth > service: > My_LDAP > (/opt/rt3/local/plugins/RT-Authen-ExternalAuth/lib/RT/Authen/ExternalAut > h.pm:64) > [Fri Apr 8 23:34:13 2011] [debug]: SSO Failed and no user to test with. > Nexting This implies that the username you typed into the login box isn't getting to the plugin. You did clear the mason cache when you updated the module, right? -kevin pgpJKgg6zOEHb.pgp Description: PGP signature
[rt-users] Finding tickets based on changed field
Is there a method to find all tickets which have had a custom field edited/changed in the last 30 days? --- Vance Walsh Network and Systems Administrator Concord Academy - Concord, Mass.
[rt-users] Forcing a custom field to be a mandatory date
What would be the proper string to make a Custom field Mandatory and contain a date field? --- Vance Walsh Network and Systems Administrator Concord Academy - Concord, Mass.
Re: [rt-users] RT-Authen-ExternalAuth-0.08 which packages i need for Authentification ?
You don't say your RT version, or what fails, it is possible you need .08_01 if you're running RT 3.8.9 Hello Kevin Sorry i forgot i currently useig the Version 3.8.9 So i had followed your advice and now the RT-Authen-ExternalAuth-0.08_01 is still running. At first it looks better than before, now i get response from the rt.log.. but there still some problems ... here is the relevant piece of information from my log file: Reloading RT::User to work around a bug in RT-3.8.0 and RT-3.8.1 (/opt/rt3/local/plugins/RT-Authen-ExternalAuth/html/Elements/DoAuth:14) [Mon Apr 11 12:13:55 2011] [debug]: Attempting to use external auth service: My_LDAP (/opt/rt3/local/plugins/RT-Authen-ExternalAuth/lib/RT/Authen/ExternalAuth.pm:64) [Mon Apr 11 12:13:55 2011] [debug]: SSO Failed and no user to test with. Nexting (/opt/rt3/local/plugins/RT-Authen-ExternalAuth/lib/RT/Authen/ExternalAuth.pm:92) [Mon Apr 11 12:13:55 2011] [debug]: Attempting to use external auth service: My_MySQL (/opt/rt3/local/plugins/RT-Authen-ExternalAuth/lib/RT/Authen/ExternalAuth.pm:64) [Mon Apr 11 12:13:55 2011] [debug]: SSO Failed and no user to test with. Nexting (/opt/rt3/local/plugins/RT-Authen-ExternalAuth/lib/RT/Authen/ExternalAuth.pm:92) [Mon Apr 11 12:13:55 2011] [debug]: Attempting to use external auth service: My_SSO_Cookie (/opt/rt3/local/plugins/RT-Authen-ExternalAuth/lib/RT/Authen/ExternalAuth.pm:64) [Mon Apr 11 12:13:55 2011] [debug]: SSO Failed and no user to test with. Nexting (/opt/rt3/local/plugins/RT-Authen-ExternalAuth/lib/RT/Authen/ExternalAuth.pm:92) [Mon Apr 11 12:13:55 2011] [debug]: Autohandler called ExternalAuth. Response: (0, No User) (/opt/rt3/local/plugins/RT-Authen-ExternalAuth/html/Elements/DoAuth:26) [Mon Apr 11 12:14:06 2011] [debug]: Attempting to use external auth service: My_LDAP (/opt/rt3/local/plugins/RT-Authen-ExternalAuth/lib/RT/Authen/ExternalAuth.pm:64) [Mon Apr 11 12:14:06 2011] [debug]: Calling UserExists with $username (RT-USER) and $service (My_LDAP) (/opt/rt3/local/plugins/RT-Authen-ExternalAuth/lib/RT/Authen/ExternalAuth.pm:105) [Mon Apr 11 12:14:06 2011] [debug]: Invalid service type for UserExists: My_LDAP (/opt/rt3/local/plugins/RT-Authen-ExternalAuth/lib/RT/Authen/ExternalAuth.pm:361) [Mon Apr 11 12:14:06 2011] [debug]: Attempting to use external auth service: My_MySQL (/opt/rt3/local/plugins/RT-Authen-ExternalAuth/lib/RT/Authen/ExternalAuth.pm:64) [Mon Apr 11 12:14:06 2011] [debug]: Calling UserExists with $username (RT-USER) and $service (My_MySQL) (/opt/rt3/local/plugins/RT-Authen-ExternalAuth/lib/RT/Authen/ExternalAuth.pm:105) [Mon Apr 11 12:14:06 2011] [debug]: Invalid service type for UserExists: My_MySQL (/opt/rt3/local/plugins/RT-Authen-ExternalAuth/lib/RT/Authen/ExternalAuth.pm:361) [Mon Apr 11 12:14:06 2011] [debug]: Attempting to use external auth service: My_SSO_Cookie (/opt/rt3/local/plugins/RT-Authen-ExternalAuth/lib/RT/Authen/ExternalAuth.pm:64) [Mon Apr 11 12:14:06 2011] [debug]: Calling UserExists with $username (RT-USER) and $service (My_SSO_Cookie) (/opt/rt3/local/plugins/RT-Authen-ExternalAuth/lib/RT/Authen/ExternalAuth.pm:105) [Mon Apr 11 12:14:06 2011] [debug]: Invalid service type for UserExists: My_SSO_Cookie (/opt/rt3/local/plugins/RT-Authen-ExternalAuth/lib/RT/Authen/ExternalAuth.pm:361) [Mon Apr 11 12:14:06 2011] [debug]: Autohandler called ExternalAuth. Response: (0, No User) (/opt/rt3/local/plugins/RT-Authen-ExternalAuth/html/Elements/DoAuth:26) [Mon Apr 11 12:14:06 2011] [error]: FAILED LOGIN for RT-USER from 192.168.112.1 (/opt/rt3/bin/../lib/RT/Interface/Web.pm:424) Thanks in advance best regrads john s. -- View this message in context: http://old.nabble.com/RT-Authen-ExternalAuth-0.08-which-packages-i-need-for-Authentification---tp31342791p31369863.html Sent from the Request Tracker - User mailing list archive at Nabble.com.