Re: [rt-users] RT Ubuntu A;pache Issue
Sorry, typo errors. really sorry. Dear RT Friends, I have a clean Ubuntu and I installed RT according to RT website instruction. Says the url to access my rt is http://192.168.1.1/rt/ I found that I can't access to apache default "it's works" page on http://192.168.1.1 and also I put a folder with a index.html file in /var/www/abc I can't browse the page at http://192.168.1.1/abc/index.html it's all resource not found error. Notice that I can access to my webmin at https://192.168.1.1:1 Will someone so kind to tell me what's wrong? Thank you very much. From: adamtang...@hotmail.com To: rt-users@lists.bestpractical.com Date: Fri, 28 Jan 2011 15:22:40 +0800 Subject: [rt-users] RT Ubuntu A;pache Issue Dear RT Friends, I have a clean Ubuntu and I installed RT according to RT website instruction. Says the url to access my rt is http://192.168.1.1/rt/ I found that I can access to apache default "it's works" page on http://192.168.1.1 and also I put a folder with a index.html file in /var/www/abc I can't browse the page at http://192.168.1.1/abc/index.html it's all resource not found error. Notice that I can access to my webmin at https://192.168.1.1:1 Will someone so kind to tell me what's wrong? Thank you very much.
[rt-users] RT Ubuntu A;pache Issue
Dear RT Friends, I have a clean Ubuntu and I installed RT according to RT website instruction. Says the url to access my rt is http://192.168.1.1/rt/ I found that I can access to apache default "it's works" page on http://192.168.1.1 and also I put a folder with a index.html file in /var/www/abc I can't browse the page at http://192.168.1.1/abc/index.html it's all resource not found error. Notice that I can access to my webmin at https://192.168.1.1:1 Will someone so kind to tell me what's wrong? Thank you very much.
Re: [rt-users] Passing date variables as dates from the CLI
On 27 Jan 2011 22:36, Chris Herrmann wrote: > Actually, the problem is more with variables fullstop... > > faredge@sirius:~$ rtqueryqueue=myrtqueue;export rtqueryqueue > faredge@sirius:~$ rt > rt> list "queue = '$rtqueryqueue'" > Query:queue = '$rtqueryqueue' > No matches found > rt> > > If I run this by typing the queue name into the cli, it works OK. > > So... then I guess the question becomes how do I correctly pass environment > variables into the RT CLI so that they're substituted correctly? You don't. bin/rt doesn't do variable substitution. If you need to use environment variables then you need to do it without dropping into bin/rt's shell. Thomas
[rt-users] Passing date variables as dates from the CLI
Ok, some more things. I think it's an RT bug not a bash problem... actually I think there are two (possibly separate) bugs. Actually I'm not editing the email after having done some more testing, and there is only one problem... but I'll leave the (brief) journey in to show how I got there. 1. If you create any arbitrary variable that contains a date string (in any format... -MM-DD, DD-MM- etc etc) and try to use this with a "<" operator it will return no results, regardless of how you create the variable. For example, I was previously trying to build a date string (which produces a correctly formatted date string for the variable) but this didn't work. So I tried typing enddate=2011-02-01 and this does not work either. If I replace the variable in the rt cli query with the literal values then it works correctly. Have also tried exporting the variables - it appears to make no difference. I also tried other variable names startdate / randomdate / thisnamecannotbereserved etc. 2. If you are using a date variable with the > operator you get a different result - it returns a whole set of data rather than restricting by the date in question. Actually, the problem is more with variables fullstop... faredge@sirius:~$ rtqueryqueue=myrtqueue;export rtqueryqueue faredge@sirius:~$ rt rt> list "queue = '$rtqueryqueue'" Query:queue = '$rtqueryqueue' No matches found rt> If I run this by typing the queue name into the cli, it works OK. So... then I guess the question becomes how do I correctly pass environment variables into the RT CLI so that they're substituted correctly? Regards, Chris Herrmann Far Edge Technology p. 02 84251400 m. 0403 393309 http://www.faredge.com.au
[rt-users] Looking for RT extension to batch create tickets.
Anyone know of an extension that will create one ticket for each requestor in a uploaded list, all with the same correspondence? Thanks. -Todd
[rt-users] Route tickets to queues based on TO email address
I would like to be able to route tickets to different queues based on the "to" address in the headers of the incoming emails. Right now I have one mailbox (ithelp@company) with several aliases (qa@company and po@company). I would like to route incoming messages to different queues based the "to" address. I want to avoid setting up multiple mailboxes because we will have about a dozen of these aliases and don't want to spend the extra money to support the additional mailboxes. Currently fetchmail is handling the incoming mail with this config: poll mail.xx.net protocol imap username "ithelp" password "xxx" mda "/usr/bin/rt-mailgate --queue general --action correspond --url http://localhost/rt/"; no keep I've done some research into this and have seen multiple possibilities on how to handle this issue, but frankly I don't have a lot of experience dealing with email backends, especially on Linux. My options seem to be: 1) Use fetchmail to direct the messages to some sort of intermediary MDA that parses the header and forwards to rt-mailgate passing the correct queue variable 2) Re-write rt-mailgate to direct to correct queues (after staring at the code for a while I'm still not sure how to even start) 3) Have a script on my "general" queue that moves messages to the correct queue, similar to this http://requesttracker.wikia.com/wiki/EmailRouting (but there doesn't seem to be a variable I can use here to pull the "to" address) Does anyone have any experience dealing with this? I don't need a step by step tutorial, but a better idea of how to handle this would be much appreciated! Thanks, Stephen De Vight Health Solutions Network
Re: [rt-users] cannot display requestor or requestors attributes in rt CLI when specifying fields
On Thu, Jan 27, 2011 at 01:19:05PM +1100, Chris Herrmann wrote: > Dominic: Yes, agree but I need a way of making this work right now, so for > the moment I'll update our internal documentation around deploying upgrades > for RT and a note to check this functionality. We have several other systems > that depend upon RT (like billing for example) so we don't tend to upgrade RT > very often, only when we're looking for some significant new functionality. Fair enough :) > What's the protocol for me to post this up as a suggestion for this fix to > become incorporated back into the main 3.8 code base so that future releases > will include it? (assuming that this isn't going to break some other piece of > critical functionality!). I would write an email to rt-b...@bestpractical.com including a reference to this thread. Cheers, Dominic. -- Dominic Hargreaves, Systems Development and Support Team Computing Services, University of Oxford signature.asc Description: Digital signature
