Re: [rt-users] RT 4

2007-05-01 Thread Benjamin Robson
Thanks for asking Jesse,

My number 1 desire would be: Ability to group Unprivileged Users.

That is, allow Unpriv users to be grouped per Company or even a sub-set 
Company-Department, such that all correspondence on tickets can be viewed 
by members of the same Company or Company-Department.  When RT is 
currently used to service external customers, it requires a bodge to 
insert other unpriv users of the same company as a Cc.  RT needs a way to 
group Unpriv users to form Company or Company-Department sets and that 
users can then opt-in or opt-out of receiving all tickets associated with 
their company or company-department.

Hope that makes sense.

BenR

-- 









Jesse Vincent [EMAIL PROTECTED] 
Sent by: [EMAIL PROTECTED]
02/05/2007 03:54 AM

To
RT Users rt-users@lists.bestpractical.com
cc

Subject
[rt-users] RT 4






If, for the sake of argument, Best Practical were to rewrite RT, what 
would you want to see in the new product?

Think big.

Jesse
___
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


PGP.sig
Description: Binary data
___
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

Re: [rt-users] Adding Delete Button

2007-04-30 Thread Benjamin Robson
Bill,

Have you tried the old bogus-mx record trick?

That is, alter the MX records for the mail server handling inbound mail 
such that the first few MX entries (with the lower, but getting higher, 
record numbers) are bogus (point to nothing) and the valid MX entry isn't 
till later in the list and has the highest record number.  In the 
good-ol-days spambots wouldn't go past the first (or first few) MX entries 
if they were invalid, where legitimate mail servers would.  Even these 
days, bots will only go so far because they don't want to waste time doing 
too many attempts as they work their way through a target's list of MX 
entries trying to find one that works.

Anyway, just another idea to consider.  But I do think your in the region 
of rapidly diminishing returns.

BenR





William (Bill) Triest [EMAIL PROTECTED] 
Sent by: [EMAIL PROTECTED]
01/05/2007 03:47 AM

To
Kenneth Marshall [EMAIL PROTECTED], rt-users@lists.bestpractical.com
cc

Subject
Re: [rt-users] Adding Delete Button






Kenneth,

Thanks, we've already been working with spamassassin.  Other departments 
have what should be the exact same configuration and complain when 9 
spam a weekend get through.  When we have less then 9 in a night, we're 
happy.  Spam filtering is over 90% effective, but with our spam level 
that's just not sufficient.  Our best guess as to the root problem is 
the server can not handle the load.  Obviously fixing the root problem 
(in-effective spam filtering) would be ideal, and its something we are 
VERY actively working on. In the mean time my boss has charged me with 
adding back the delete button, thus my question.

Thanks,
Bill

Kenneth Marshall wrote:
 Bill,

 We found that putting RT behind DSPAM or another Baysian based filter
 was the best solution for us. The support staff monitor the quarantine
 and train the misses. It is accurate enough that only a very few ever
 make it to the RT system.

 Ken

 On Mon, Apr 30, 2007 at 12:16:28PM -0400, William (Bill) Triest wrote:
 
 Basically a lot of spam gets through our spam filtering and ends up in 
 rt.  We hacked an older version of rt to have a delete button to the 
 right of the take button under RT at a glance so we could easily delete 

 spam.  I've been trying to find the right way to do add it back to 
our 
 current version (3.6.3).

 If you go to Customize N newest unowned tickets, you can add new 
 Columns.  For the link option you have Display or Take.  I think I just 

 need to add a delete option, and then add a Column (similar to the 
 loc(Take) that's currently in there).  Is this correct?  If so, for the 

 life of me I can't find what I need to edit it, and would appreciate 
 some one pointing me in the right direction.

 --Bill Triest
 Systems Specialist
 Department of Chemistry
 The Ohio State University
 ___
 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

 

___
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

___
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

Re: [rt-users] 3.6 to 3.6.1 server migration

2006-08-18 Thread Benjamin Robson

Todd,

Can I ask the same question about 3.5.5
- 3.6.0 (and hence 3.6.1)?

I have an RT 3.5.5 deployment that started
out as a test but unfortunately management got wind and liked what they
saw way to much, now I am pondering upgrading to the legitimate stable
release.

Thanks.

BenR

--





Todd Chapman [EMAIL PROTECTED]

Sent by: [EMAIL PROTECTED]
18/08/2006 11:48 PM




To
Helmuth Ramirez [EMAIL PROTECTED]


cc
rt-users@lists.bestpractical.com


Subject
Re: [rt-users] 3.6 to 3.6.1 server migration








On Fri, Aug 18, 2006 at 08:58:03AM -0400, Helmuth
Ramirez wrote:
 Hi All,
  I am planning our RT move from our pilot hardware to our production
 hardware (fresh box just for RT :). I found a great article
in the wiki
 for the server migration
 (http://wiki.bestpractical.com/index.cgi?MigrateToNewServer ). 
 
 My question is about 3.6 and 3.6.1 though.
 
 I believe I read there were some changes made to the database in 3.6.1,
 is this change something I can change to my current 3.6 db and just
put
 it over on my new machine running 3.6.1? Or is it a change I'll
need to
 upgrade to as suggested in the article?
 

No database changes between 3.6.0 and 3.6.1.

-Todd
___
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

___
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