Dear friends, I am using CanIt-FREE to fighting spam on RT. It is great! www.roaringpenguin.com
Regards, Eder Miranda -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: quarta-feira, 19 de julho de 2006 23:04 To: rt-users@lists.bestpractical.com Subject: RT-Users Digest, Vol 28, Issue 58 Send RT-Users mailing list submissions to rt-users@lists.bestpractical.com To subscribe or unsubscribe via the World Wide Web, visit http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users or, via email, send a message with subject or body 'help' to [EMAIL PROTECTED] You can reach the person managing the list at [EMAIL PROTECTED] When replying, please edit your Subject line so it is more specific than "Re: Contents of RT-Users digest..." Today's Topics: 1. Re: CommandByMail problems in RT 3.6? (Camron W. Fox) 2. Re: Custom Fields / Transaction Custom Fields inScrips [FIX!] (jesse vincent) 3. Re: Spam on the Wiki (Benji Wakely) 4. Re: Spam on the Wiki (Gilmar Santos Jr) 5. Re: Spam on the Wiki (Jesse Vincent) 6. LDAP working, now the next step (Jay Vlavianos) 7. Re: Spam on the Wiki (Gilmar Santos Jr) 8. Ticket not appearing (Mathew Snyder) 9. RE: LDAP working, now the next step (Joachim Thuau) ---------------------------------------------------------------------- Message: 1 Date: Wed, 19 Jul 2006 13:26:18 -1000 From: "Camron W. Fox" <[EMAIL PROTECTED]> Subject: Re: [rt-users] CommandByMail problems in RT 3.6? To: rt-users@lists.bestpractical.com Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Camron W. Fox wrote: > Alle, > > As anyone had problems installing the patch for CommandByMail > extension in RT V3.6? I've installed the extension and its prereqs, > but when I try to install the patch: > > patch -p0 > /home/cwfox/RT3/RT-Extension-CommandByMail-0.02/patch/command_by_email > -0.1-RT-3.4.5.patch > > OK, nevermind...oxygen narcosis from traveling to the Summit...BUT, Now I send this input to the generic queue: <MAIL CONTENT> Queue: "FAI Internal" Subject: "TEST Command Subject Change" Status: open Owner: cwfox Requestor: [EMAIL PROTECTED] CF.{Urgency}: Normal CF.{Area}: DNS Gentlemen, This is a test of the commandByMail extension for RT. Best Regards, Camron </MAIL CONTENT> and a ticket was created in the generic queue with all the input above as the content. Here are the errors: [Wed Jul 19 23:11:38 2006] [debug]: Converting 'ISO-8859-1' to 'utf-8' for text/plain - TEST CommandByMail (/usr/local/rt3/lib/RT/I18N.pm:226) [Wed Jul 19 23:11:38 2006] [debug]: RT::Ticket=HASH(0xa60f68c) No queue given for ticket creation. (/usr/local/rt3/lib/RT/Ticket_Overlay.pm:396) [Wed Jul 19 23:11:38 2006] [error]: Couldn't create ticket from message with commands, fallback to standard mailgate. Error: Could not create ticket. Queue not set (/usr/local/rt3/local/lib/RT/Interface/Email/Filter/TakeAction.pm:447) [Wed Jul 19 23:11:38 2006] [warning]: Couldn't create ticket from message with commands, fallback to standard mailgate. Error: Could not create ticket. Queue not set (/usr/local/rt3/local/lib/RT/Interface/Email/Filter/TakeAction.pm:583) [Wed Jul 19 23:11:38 2006] [crit]: Couldn't create ticket from message with commands, fallback to standard mailgate. Error: Could not create ticket. Queue not set (/usr/local/rt3/lib/RT/Interface/Email.pm:242) ------------------------------ Message: 2 Date: Wed, 19 Jul 2006 16:24:48 -0700 From: "jesse vincent" <[EMAIL PROTECTED]> Subject: Re: [rt-users] Custom Fields / Transaction Custom Fields inScrips [FIX!] To: [EMAIL PROTECTED] Cc: rt-users@lists.bestpractical.com Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; charset=iso-8859-1 Unfortunately, the patch violates abstraction barriers all over the place. Io never found a way to do it cleanly ------- Original message ------- From: Mike Coakley <[EMAIL PROTECTED]> Sent: 19.7.'06, 16:33 > For anyone following this thread (doubtful as it is old) I've got everything > working. After looking through the code I noticed that the patch that Jesse > had released for 3.4 that I had tried to apply did not apply fro some reason > although I didn't remember getting any errors. So I re-applied the patch to > my 3.6 and everything is working as I expected it in the past. > > So, I concur with Jesse... His patch does fix the issue :-D > > Now my only question would be why isn't this patch in the core yet as of > 3.6? > > Thanks, > > -- > Mike Coakley > Managed Business > http://www.managedbusiness.com > http://my.managedbusiness.com > Voice - 973-252-0770 x2100 > Fax - 973-252-1797 > > > > > > From: Mike Coakley <[EMAIL PROTECTED]> > > Date: Fri, 07 Jul 2006 15:30:03 -0400 > > To: "rt-users@lists.bestpractical.com" <rt-users@lists.bestpractical.com> > > Conversation: [rt-users] Custom Fields / Transaction Custom Fields in Scrips > > Subject: Re: [rt-users] Custom Fields / Transaction Custom Fields in Scrips > > > > Hello all... > > > > In further attempts to get this working I've done the following: > > > > 1. I upgraded to RT 3.6.0. Upgrade went smooth but this still does not work. > > > > 2. In further research I found an article in the archives that stated that > > this was a known issue back in the 3.4 timeframe basically stating the the > > Transaction Custom Fields don't get populated until after the scrips are > > run. There was a patch file available through the archives but this patch > > file also did not fix my issue. > > > > So, I'm wondering if anyone has any further help or places I can look. > > > > Thanks, > > > > -- > > Mike Coakley > > Managed Business > > http://www.managedbusiness.com > > http://my.managedbusiness.com > > Voice - 973-252-0770 x2100 > > Fax - 973-252-1797 > > > > > > > > > >> From: Mike Coakley <[EMAIL PROTECTED]> > >> Date: Wed, 05 Jul 2006 16:02:42 -0400 > >> To: <rt-users@lists.bestpractical.com> > >> Conversation: Custom Fields / Transaction Custom Fields in Scrips > >> Subject: [rt-users] Custom Fields / Transaction Custom Fields in Scrips > >> > >> I'm trying to write a custom condition that will trigger every time a > >> transaction custom field is updated that will update other custom fields. > >> The idea is to keep track of time in a better way. > >> > >> So I have 2 custom fields: Billable Time and Non-Billable Time. These are > >> attached to a ticket. I can easily manually update these fields. I also have > >> two Transaction based custom fields: TRANS Billable Time and TRANS > >> Non-Billable Time. I want to have a condition that fires when the "TRANS*" > >> fields get updated. Then when the condition is fired the action will be to > >> update the Billable Time and Non-Billable Time field appropriately. > >> > >> I've been doing some debugging within the Scrip condition and it appears the > >> condition gets tested twice during a "comment" (haven't worked on reply > >> yet). BUT I don't see the transaction custom field values so my condition > >> fails. So I'm either not retrieving the transaction custom field values > >> improperly (I get no value) or I'm not seeing the right condition. > >> > >> Anyone have any ideas? > >> > >> Thanks, > >> > >> -- > >> Mike Coakley > >> Managed Business > >> http://www.managedbusiness.com > >> http://my.managedbusiness.com > >> Voice - 973-252-0770 x2100 > >> Fax - 973-252-1797 > >> > >> > >> > >> _______________________________________________ > >> http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users > >> > >> Community help: http://wiki.bestpractical.com > >> Commercial support: [EMAIL PROTECTED] > >> > >> > >> Discover RT's hidden secrets with RT Essentials from O'Reilly Media. > >> Buy a copy at http://rtbook.bestpractical.com > >> > >> > >> We're hiring! Come hack Perl for Best Practical: > >> http://bestpractical.com/about/jobs.html > > > > _______________________________________________ > > http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users > > > > Community help: http://wiki.bestpractical.com > > Commercial support: [EMAIL PROTECTED] > > > > > > Discover RT's hidden secrets with RT Essentials from O'Reilly Media. > > Buy a copy at http://rtbook.bestpractical.com > > > > > > We're hiring! Come hack Perl for Best Practical: > > http://bestpractical.com/about/jobs.html > > _______________________________________________ > http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users > > Community help: http://wiki.bestpractical.com > Commercial support: [EMAIL PROTECTED] > > > Discover RT's hidden secrets with RT Essentials from O'Reilly Media. > Buy a copy at http://rtbook.bestpractical.com > > > We're hiring! Come hack Perl for Best Practical: http://bestpractical.com/about/jobs.html > ------------------------------ Message: 3 Date: Thu, 20 Jul 2006 10:15:13 +1000 From: "Benji Wakely" <[EMAIL PROTECTED]> Subject: Re: [rt-users] Spam on the Wiki To: rt-users@lists.bestpractical.com Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; charset=UTF-8; format=flowed > It has been mentioned before but is there a way to get rid of the spam > on the Wiki? Don't know how it'll fly, but: Semi-public login, posted to the mailing lists regularly? Word-verification/captcha? --Benji Wakely 0409 588 566 ------------------------------ Message: 4 Date: Wed, 19 Jul 2006 21:29:10 -0300 From: Gilmar Santos Jr <[EMAIL PROTECTED]> Subject: Re: [rt-users] Spam on the Wiki Cc: rt-users@lists.bestpractical.com Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; charset=UTF-8 Benji Wakely escreveu: >> It has been mentioned before but is there a way to get rid of the spam >> on the Wiki? > > Don't know how it'll fly, but: > Semi-public login, posted to the mailing lists regularly? > Word-verification/captcha? I take care of a few wiki sites and this problem was relatively solved by requiring login to edit. In the register process the user writes a comment about why she/he wants to register and a confirm mail is sent to the supplied address. The registration is complete when this mail is replyed or the code sent is inputed in a particular web form. A notice is generated and sent to the administrator, that can remove the account if it's the case. This way we are fairly safe from robots, and incidents with bad users are very rare... Btw, I use TWiki (http://twiki.org/), a very robust, flexible and extensible wiki. -- Gilmar Santos Jr ------------------------------ Message: 5 Date: Wed, 19 Jul 2006 20:29:54 -0400 From: Jesse Vincent <[EMAIL PROTECTED]> Subject: Re: [rt-users] Spam on the Wiki To: Benji Wakely <[EMAIL PROTECTED]> Cc: rt-users@lists.bestpractical.com Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; charset=us-ascii On Thu, Jul 20, 2006 at 10:15:13AM +1000, Benji Wakely wrote: > >It has been mentioned before but is there a way to get rid of the spam > >on the Wiki? > > Don't know how it'll fly, but: > Semi-public login, posted to the mailing lists regularly? Our spammers use google. I think we'll need to go to a full-email-verified login. Wifty is almost, but not quite ready for that. The "other" option is Mediawiki, but my personal distaste for PHP makes that a bit of a non-starter. > Word-verification/captcha? Tried it. The spammers are humans. > --Benji Wakely > 0409 588 566 > _______________________________________________ > http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users > > Community help: http://wiki.bestpractical.com > Commercial support: [EMAIL PROTECTED] > > > Discover RT's hidden secrets with RT Essentials from O'Reilly Media. > Buy a copy at http://rtbook.bestpractical.com > > > We're hiring! Come hack Perl for Best Practical: > http://bestpractical.com/about/jobs.html > -- ------------------------------ Message: 6 Date: Wed, 19 Jul 2006 17:52:44 -0700 From: "Jay Vlavianos" <[EMAIL PROTECTED]> Subject: [rt-users] LDAP working, now the next step To: <rt-users@lists.bestpractical.com> Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; charset="us-ascii" Hurrah! I got LDAP working with Active Directory using the Mosemann implementation found on the wiki. It took some tweaking and some trial and error, but I finally got it working with a Windows 2003 AD server (which is different than 2000). If anyone is having problems getting that far, I think I can be a resource for you. NOW I have a problem. I want people to be able to create tickets without having an account, but then be able to log into the system and have those tickets associated with their account (by email). I am currently using the "Auto Create on email, then set password via Auto Respond" method, which I will need to turn off. Ideally I can have a replacement for that process that uses LDAP. Does anyone have any ideas about how I might accomplish the above? Thanks! -Jay ------------------------------ Message: 7 Date: Wed, 19 Jul 2006 22:11:38 -0300 From: Gilmar Santos Jr <[EMAIL PROTECTED]> Subject: Re: [rt-users] Spam on the Wiki Cc: rt-users@lists.bestpractical.com Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; charset=ISO-8859-1 Jesse Vincent escreveu: > Our spammers use google. > > I think we'll need to go to a full-email-verified login. Wifty is > almost, but not quite ready for that. The "other" option is Mediawiki, > but my personal distaste for PHP makes that a bit of a non-starter. > <marketing-joke> TWiki is in Perl. :-) http://twiki.org/ </marketing-joke> -- Gilmar Santos Jr ------------------------------ Message: 8 Date: Wed, 19 Jul 2006 21:59:38 -0400 From: Mathew Snyder <[EMAIL PROTECTED]> Subject: [rt-users] Ticket not appearing To: rt-users@lists.bestpractical.com Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; charset=ISO-8859-1 A user has pointed out a problem. He was doing a search for resolved tickets that he owns falling under a specific custom field value. The ticket exists in the database and has the status of 'resolved'. However, entering the ticket number in the search box results in nothing. Also, doing a search specifically for that ticket on the Tickets page results in nothing again. Is there an issue with v3.6.0 that might prevent some tickets from being displayed or is this just, as my user called it, an RT anomaly? Or, could something in the ticket get changed within the database which prevents it from showing up in the UI? Mathew Snyder ------------------------------ Message: 9 Date: Wed, 19 Jul 2006 19:05:07 -0700 From: Joachim Thuau <[EMAIL PROTECTED]> Subject: RE: [rt-users] LDAP working, now the next step To: rt-users@lists.bestpractical.com Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; charset="iso-8859-1" I just went through the step to setup the auth from the wiki, using LDAP. following all the steps (and now that my exchange and AD are sync'ed throught the exchange connector), gave me the ability to logon with my AD password, and have users registered the same way. If a user send an email, their account is created automatically, and populated with the right details from AD. If a user logon using a browser, the same thing happens. As long as exchange and AD have "sync'ed" data (the connector wasn't configured properly in our case, but since it's there, everything is working beautifully.) my understanding is that with the LDAP plugin/extension setup, the authentication happens over LDAP against AD, and the user details (including emails and stuff) is pulled from AD as well. so when a user sends an email, an account for that user is created with their AD login (minus the domain). the password being checked is the one is AD. So if you look at the auth extension for the ldap in the wiki. i believe the pages that i looked at are the one linked from there: http://wiki.bestpractical.com/index.cgi?LDAP not the one you referenced. RT3.6, apache 1.3, perl 5.8.8. Thanks to Jim Meyer. It works for me(TM). Jok -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Jay Vlavianos Sent: Wednesday, July 19, 2006 5:53 PM To: rt-users@lists.bestpractical.com Subject: [rt-users] LDAP working, now the next step Hurrah! I got LDAP working with Active Directory using the Mosemann implementation found on the wiki. It took some tweaking and some trial and error, but I finally got it working with a Windows 2003 AD server (which is different than 2000). If anyone is having problems getting that far, I think I can be a resource for you. NOW I have a problem. I want people to be able to create tickets without having an account, but then be able to log into the system and have those tickets associated with their account (by email). I am currently using the "Auto Create on email, then set password via Auto Respond" method, which I will need to turn off. Ideally I can have a replacement for that process that uses LDAP. Does anyone have any ideas about how I might accomplish the above? Thanks! -Jay _______________________________________________ http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users Community help: http://wiki.bestpractical.com Commercial support: [EMAIL PROTECTED] Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy a copy at http://rtbook.bestpractical.com We're hiring! Come hack Perl for Best Practical: http://bestpractical.com/about/jobs.html ------------------------------ _______________________________________________ RT-Users mailing list RT-Users@lists.bestpractical.com http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users End of RT-Users Digest, Vol 28, Issue 58 **************************************** _______________________________________________ http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users Community help: http://wiki.bestpractical.com Commercial support: [EMAIL PROTECTED] Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy a copy at http://rtbook.bestpractical.com We're hiring! Come hack Perl for Best Practical: http://bestpractical.com/about/jobs.html