[rt-users] Mailgate issue

[Winn Johnston]

Apr 17 16:46:08 rt postfix/local[16592]: 2B1CE97EC3:
to=<[EMAIL PROTECTED]>, relay=local, delay=0,
status=deferred (temporary failure. Command output: An
Error Occurred =  403 Forbidden 

Error msg.

Can someone please help me. Not sure why apache would
be issuing a 403 error


Thanks

-winn


  

Be a better friend, newshound, and 
know-it-all with Yahoo! Mobile.  Try it now.  
http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ
___
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

[rt-users] RT mail problem - chameleon

[Judy Illeman Gaukel]

Hi,
  I posted earlier about my solaris RT 3.6.3 perl 5.8.8 problem.   I 
decided to rename /bin/perl and force RT to use /opt/csw/bin/perl, (even 
though this is stated in the RT config files!) - and now have a 
different kind of error.   I have since learned how to
cpan -i Scalar::Util which was up to date, anyway (and it IS using 
/opt/csw/perl)...   but now the error log shows:

Apr 17 19:42:01 localhost RT: Scrip Prepare 7 died. - Require of 
RT::Action:: failed.\nCan't loca
te RT/Action/.pm in @INC (@INC contains: /opt/csw/rt3/local/lib 
/opt/csw/rt3/lib /opt/csw/lib/per
l5/site_perl/5.8.8/sun4-solaris-thread-multi /opt/csw/lib/perl/5.8.8 
/opt/csw/share/perl/5.8.8 /o
pt/csw/lib/perl/site_perl /opt/csw/share/perl/site_perl 
/opt/csw/lib/perl/csw /opt/csw/share/perl
/csw . /opt/csw/apache/ /opt/csw/apache/lib/perl) at (eval 1349) line 
3.\n\nStack:\n  [(eval 1349
):3]\n  [/opt/csw/rt3/lib/RT/Scrip_Overlay.pm:471]\n  
[/opt/csw/rt3/lib/RT/Scrips_Overlay.pm:237]
\n  [/opt/csw/rt3/lib/RT/Transaction_Overlay.pm:171]\n  
[/opt/csw/rt3/lib/RT/Record.pm:1444]\n  [
/opt/csw/rt3/lib/RT/Ticket_Overlay.pm:2441]\n  
[/opt/csw/rt3/lib/RT/Ticket_Overlay.pm:2355]\n  [/
opt/csw/rt3/share/html/Ticket/Elements/PreviewScrips:82]\n  
[/opt/csw/rt3/share/html/Ticket/Updat
e.html:137]\n  [/opt/csw/rt3/share/html/autohandler:292]\n\n\nStack:\n  
[/opt/csw/rt3/lib/RT/Scri
pAction_Overlay.pm:175]\n  [/opt/csw/rt3/lib/RT/Scrip_Overlay.pm:471]\n  
[/opt/
Apr 17 19:42:01 localhost RT: Scrip Prepare 6 died. - Undefined 
subroutine &Scalar::Util::weaken
called at /opt/csw/rt3/lib/RT/Action/Generic.pm line 107.\n\nStack:\n  
[/opt/csw/rt3/lib/RT/Actio
n/Generic.pm:107]\n  [/opt/csw/rt3/lib/RT/Action/Generic.pm:79]\n  
[/opt/csw/rt3/lib/RT/ScripActi
on_Overlay.pm:177]\n  [/opt/csw/rt3/lib/RT/Scrip_Overlay.pm:471]\n  
[/opt/csw/rt3/lib/RT/Scrips_O
verlay.pm:237]\n  [/opt/csw/rt3/lib/RT/Transaction_Overlay.pm:171]\n  
[/opt/csw/rt3/lib/RT/Record
.pm:1444]\n  [/opt/csw/rt3/lib/RT/Ticket_Overlay.pm:2441]\n  
[/opt/csw/rt3/lib/RT/Ticket_Overlay.
pm:2355]\n  
[/opt/csw/rt3/share/html/Ticket/Elements/PreviewScrips:82]\n  
[/opt/csw/rt3/share/htm
l/Ticket/Update.html:137]\n  [/opt/csw/rt3/share/html/autohandler:292] 
(/opt/csw/rt3/lib/RT/Scrip
_Overlay.pm:479)\n
Apr 17 19:42:01 localhost RT: Scrip Prepare 1 died. - Require of 
RT::Action:: failed.\nCan't loca
te RT/Action/.pm in @INC (@INC contains: /opt/csw/rt3/local/lib 
/opt/csw/rt3/lib /opt/csw/lib/per
l5/site_perl/5.8.8/sun4-solaris-thread-multi /opt/csw/lib/perl/5.8.8 
/opt/csw/share/perl/5.8.8 /o
pt/csw/lib/perl/site_perl /opt/csw/share/perl/site_perl 
/opt/csw/lib/perl/csw /opt/csw/share/perl
/csw . /opt/csw/apache/ /opt/csw/apache/lib/perl) at (eval 1360) line 
3.\n\nStack:\n  [(eval 1360
):3]\n  [/opt/csw/rt3/lib/RT/Scrip_Overlay.pm:471]\n  
[/opt/csw/rt3/lib/RT/Scrips_Overlay.pm:237]
\n  [/opt/csw/rt3/lib/RT/Transaction_Overlay.pm:171]\n  
[/opt/csw/rt3/lib/RT/Record.pm:1444]\n  [
/opt/csw/rt3/lib/RT/Ticket_Overlay.pm:2441]\n  
[/opt/csw/rt3/lib/RT/Ticket_Overlay.pm:2355]\n  [/
opt/csw/rt3/share/html/Ticket/Elements/PreviewScrips:82]\n  
[/opt/csw/rt3/share/html/Ticket/Updat
e.html:137]\n  [/opt/csw/rt3/share/html/autohandler:292]\n\n\nStack:\n  
[/opt/csw/rt3/lib/RT/Scri
pAction_Overlay.pm:175]\n  [/opt/csw/rt3/lib/RT/Scrip_Overlay.pm:471]\n  
[/opt/
Apr 17 19:42:16 localhost RT: Scrip Prepare 7 died. - Require of 
RT::Action::rt-3.6.3-561-1208461
336-1233 failed.\nsyntax error at (eval 1300) line 1, near "require 
RT::Action::rt-"\n\n\nStack:\
n  [/opt/csw/rt3/lib/RT/ScripAction_Overlay.pm:175]\n  
[/opt/csw/rt3/lib/RT/Scrip_Overlay.pm:471]
\n  [/opt/csw/rt3/lib/RT/Scrips_Overlay.pm:237]\n  
[/opt/csw/rt3/lib/RT/Transaction_Overlay.pm:17
1]\n  [/opt/csw/rt3/lib/RT/Record.pm:1444]\n  
[/opt/csw/rt3/lib/RT/Ticket_Overlay.pm:2441]\n  [/o
pt/csw/rt3/lib/RT/Ticket_Overlay.pm:2355]\n  
[/opt/csw/rt3/lib/RT/Interface/Web.pm:570]\n  [/opt/
csw/rt3/share/html/Ticket/Display.html:142]\n  
[/opt/csw/rt3/share/html/Ticket/Update.html:216]\n
  [/opt/csw/rt3/share/html/autohandler:292] 
(/opt/csw/rt3/lib/RT/Scrip_Overlay.pm:479)\n
Apr 17 19:42:16 localhost RT: Scrip Prepare 6 died. - Undefined 
subroutine &Scalar::Util::weaken
called at /opt/csw/rt3/lib/RT/Action/Generic.pm line 107.\n\nStack:\n  
[/opt/csw/rt3/lib/RT/Actio
n/Generic.pm:107]\n  [/opt/csw/rt3/lib/RT/Action/Generic.pm:79]\n  
[/opt/csw/rt3/lib/RT/ScripActi
on_Overlay.pm:177]\n  [/opt/csw/rt3/lib/RT/Scrip_Overlay.pm:471]\n  
[/opt/csw/rt3/lib/RT/Scrips_O
verlay.pm:237]\n  [/opt/csw/rt3/lib/RT/Transaction_Overlay.pm:171]\n  
[/opt/csw/rt3/lib/RT/Record
.pm:1444]\n  [/opt/csw/rt3/lib/RT/Ticket_Overlay.pm:2441]\n  
[/opt/csw/rt3/lib/RT/Ticket_Overlay.
pm:2355]\n  [/opt/csw/rt3/lib/RT/Interface/Web.pm:570]\n  
[/opt/csw/rt3/share/html/Ticket/Display
.html:142]\n  [/opt/csw/rt3/share/html/Ticket/Update.html:216]\n  
[/opt/csw/rt3/share/html/autoha
ndler:292] (/opt/csw/rt3/lib/RT/Scrip_Overlay.pm:479)\n
Apr 17 19:42:16 localhost 

[rt-users] Attachments not included in tickets?

[Juan Mas]

When new tickets are being created with an image attachment, the
attachments are not in the ticket.  I see the attachment referenced
under Attachments in the display but I cant actually see them.  Anyone
have any ideas?  I am using 3.6.6 on Gentoo.

-- 
-Juan
___
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] Requestor or Owner

[Ryan Moxley]

 
The owner would typically be the person in charge of rectifying the issue
within the ticket.  The requestor is the originator of the issue.  You can
add or change roles using the "People" link in the ticket display. 

Ryan Moxley
IT Department
EnvisionWare, Inc.

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of John BORIS
Sent: Thursday, April 17, 2008 1:55 PM
To: rt-users@lists.bestpractical.com
Subject: [rt-users] Requestor or Owner

This may be a simple question but is the Requestor (person who submits the
ticket) the same as the owner?  I usually enter tickets when Users contact
me or I am starting a project and want to track it in RT. But now I want the
user who contacted me to be the person who would have emailed the request
into RT or even filled out a form for the request. 
So do I make that person the owner of the ticket or a watcher?

John J. Boris, Sr.
JEN-A-SyS Administrator
Archdiocese of Philadelphia
"Remember! That light at the end of the tunnel Just might be the headlight
of an oncoming train!"
___
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] Requestor or Owner

[John BORIS]

Thanks.
After I sent the email I started looking around and saw where I can add
the person's to the ticket as the requestor. I couldn't find this as a
field to enter when I first looked at the ticket.

John J. Boris, Sr.
JEN-A-SyS Administrator
Archdiocese of Philadelphia
"Remember! That light at the end of the tunnel
Just might be the headlight of an oncoming train!"

>>> "Ruslan Zakirov" <[EMAIL PROTECTED]> 4/17/2008 2:21 PM >>>
Watchers - people around ticket, who is in any way interested in the
ticket.
Requestor - people who is interested in the ticket to be resolved.
Owner - one and only one person at a time who works hard to resolve the
ticket.
Cc, AdminCc - people as well interested in the ticket, but these group
are flexible and can be used in many ways, depends on workflow.

On Thu, Apr 17, 2008 at 10:00 PM,  <[EMAIL PROTECTED]> wrote:
> It's really up to you how you want to handle how people are
associated to a
>  ticket.  With that said, typically the person 'opening' the ticket
or
>  making the request is the requestor.
>
>  The owner of the ticket is the person that is working the ticket or
that
>  the ticket is assigned to.  You can very easily modify the requestor
(or
>  populate the field when the ticket is created) field by changing the
email
>  address to who should be the requestor, ie, the person who should
have
>  opened the ticket in the first place.
>
>
>  James Moseley
>
>
>
>
>
>  "John  BORIS"
>  <[EMAIL PROTECTED] 
>  rg> 
  To
>  Sent by: 

>  rt-users-bounces@   
  cc
>  lists.bestpractic
>  al.com   
Subject
>[rt-users] Requestor or Owner
>
>  04/17/2008 12:54
>  PM
>
>
>
>
>
>
>
>
>
>  This may be a simple question but is the Requestor (person who
submits
>  the ticket) the same as the owner?  I usually enter tickets when
Users
>  contact me or I am starting a project and want to track it in RT.
But
>  now I want the user who contacted me to be the person who would
have
>  emailed the request into RT or even filled out a form for the
request.
>  So do I make that person the owner of the ticket or a watcher?
>
>  John J. Boris, Sr.
>  JEN-A-SyS Administrator
>  Archdiocese of Philadelphia
>  "Remember! That light at the end of the tunnel
>  Just might be the headlight of an oncoming train!"
>  ___
>  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 
>



-- 
Best regards, Ruslan.
___
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] Requestor or Owner

[Ruslan Zakirov]

Watchers - people around ticket, who is in any way interested in the ticket.
Requestor - people who is interested in the ticket to be resolved.
Owner - one and only one person at a time who works hard to resolve the ticket.
Cc, AdminCc - people as well interested in the ticket, but these group
are flexible and can be used in many ways, depends on workflow.

On Thu, Apr 17, 2008 at 10:00 PM,  <[EMAIL PROTECTED]> wrote:
> It's really up to you how you want to handle how people are associated to a
>  ticket.  With that said, typically the person 'opening' the ticket or
>  making the request is the requestor.
>
>  The owner of the ticket is the person that is working the ticket or that
>  the ticket is assigned to.  You can very easily modify the requestor (or
>  populate the field when the ticket is created) field by changing the email
>  address to who should be the requestor, ie, the person who should have
>  opened the ticket in the first place.
>
>
>  James Moseley
>
>
>
>
>
>  "John  BORIS"
>  <[EMAIL PROTECTED]
>  rg>To
>  Sent by:  
>  rt-users-bounces@  cc
>  lists.bestpractic
>  al.comSubject
>[rt-users] Requestor or Owner
>
>  04/17/2008 12:54
>  PM
>
>
>
>
>
>
>
>
>
>  This may be a simple question but is the Requestor (person who submits
>  the ticket) the same as the owner?  I usually enter tickets when Users
>  contact me or I am starting a project and want to track it in RT. But
>  now I want the user who contacted me to be the person who would have
>  emailed the request into RT or even filled out a form for the request.
>  So do I make that person the owner of the ticket or a watcher?
>
>  John J. Boris, Sr.
>  JEN-A-SyS Administrator
>  Archdiocese of Philadelphia
>  "Remember! That light at the end of the tunnel
>  Just might be the headlight of an oncoming train!"
>  ___
>  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
>



-- 
Best regards, Ruslan.
___
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] Requestor or Owner

[jmoseley]

It's really up to you how you want to handle how people are associated to a
ticket.  With that said, typically the person 'opening' the ticket or
making the request is the requestor.

The owner of the ticket is the person that is working the ticket or that
the ticket is assigned to.  You can very easily modify the requestor (or
populate the field when the ticket is created) field by changing the email
address to who should be the requestor, ie, the person who should have
opened the ticket in the first place.


James Moseley




   
 "John  BORIS" 
 <[EMAIL PROTECTED] 
 rg>To 
 Sent by:
 rt-users-bounces@  cc 
 lists.bestpractic 
 al.comSubject 
   [rt-users] Requestor or Owner   
   
 04/17/2008 12:54  
 PM
   
   
   




This may be a simple question but is the Requestor (person who submits
the ticket) the same as the owner?  I usually enter tickets when Users
contact me or I am starting a project and want to track it in RT. But
now I want the user who contacted me to be the person who would have
emailed the request into RT or even filled out a form for the request.
So do I make that person the owner of the ticket or a watcher?

John J. Boris, Sr.
JEN-A-SyS Administrator
Archdiocese of Philadelphia
"Remember! That light at the end of the tunnel
Just might be the headlight of an oncoming train!"
___
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] Requestor or Owner

[Gene LeDuc]

Hi John,

The Owner is usually the person who is taking responsibility for the ticket.

Gene

At 10:54 AM 4/17/2008, John  BORIS wrote:
>This may be a simple question but is the Requestor (person who submits
>the ticket) the same as the owner?  I usually enter tickets when Users
>contact me or I am starting a project and want to track it in RT. But
>now I want the user who contacted me to be the person who would have
>emailed the request into RT or even filled out a form for the request.
>So do I make that person the owner of the ticket or a watcher?


-- 
Gene LeDuc, GSEC
Security Analyst
San Diego 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

[rt-users] Requestor or Owner

[John BORIS]

This may be a simple question but is the Requestor (person who submits
the ticket) the same as the owner?  I usually enter tickets when Users
contact me or I am starting a project and want to track it in RT. But
now I want the user who contacted me to be the person who would have
emailed the request into RT or even filled out a form for the request. 
So do I make that person the owner of the ticket or a watcher?

John J. Boris, Sr.
JEN-A-SyS Administrator
Archdiocese of Philadelphia
"Remember! That light at the end of the tunnel
Just might be the headlight of an oncoming train!"
___
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

[rt-users] error upgrading from 3.4.5 to 3.6.4 (via etc/upgrade/3.5.1 script)

[Trenton Taylor]

I'm trying to upgrade my RT system from 3.4.5 to 3.6.4 via:

 

# command:

/opt/rt3.6/sbin/rt-setup-database --action schema \ --datadir
etc/upgrade/3.5.1 --dba root --prompt-for-dba-password

 

But I am getting this error:

 

#:

Creating database schema.

Problem with statement:

 

 

CREATE TABLE Attachments (

  id INTEGER NOT NULL  AUTO_INCREMENT,

  TransactionId integer NOT NULL  ,

  Parent integer NOT NULL DEFAULT 0  ,

  MessageId varchar(160) NULL  ,

  Subject varchar(255) NULL  ,

  Filename varchar(255) NULL  ,

  ContentType varchar(80) NULL  ,

  ContentEncoding varchar(80) NULL  ,

  Content LONGTEXT NULL  ,

  Headers LONGTEXT NULL  ,

  Creator integer NOT NULL DEFAULT 0  ,

  Created DATETIME NULL  ,

  PRIMARY KEY (id)

) TYPE=InnoDB

Table 'Attachments' already exists at /opt/rt3.6/sbin/rt-setup-database
line 220,  line 464.

 

 

Thanks in advance -

Trent 

 



Important: The information contained in this e-mail message is confidential and 
is intended only for the named addressee(s). If the reader of this e-mail 
message is not an intended recipient (or the individual responsible for the 
delivery of this e-mail message to an intended recipient), please be advised 
that any re-use, dissemination, distribution or copying of this e-mail message 
is prohibited. If you have received this e-mail message in error, please reply 
to the sender that you have received the message in error and then delete it. 
Thank you. 
___
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

[rt-users] (no subject)

[Trenton Taylor]

subscribe



Important: The information contained in this e-mail message is confidential and 
is intended only for the named addressee(s). If the reader of this e-mail 
message is not an intended recipient (or the individual responsible for the 
delivery of this e-mail message to an intended recipient), please be advised 
that any re-use, dissemination, distribution or copying of this e-mail message 
is prohibited. If you have received this e-mail message in error, please reply 
to the sender that you have received the message in error and then delete it. 
Thank you. 
___
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] RT as a intranet portal? Or other suggestions?

[Martin Wheldon]

Non at all I'm afraid, it is however extremely easy to use and easily
extensible.

I use it for all my systems documentation, FAQ's etc

Regards

Martin


On 4/16/08, Nelson Pereira <[EMAIL PROTECTED]> wrote:
>
>  Does it have any scripts that work with RT at all?
>
>
>
> Regards,
>
>
>
> Nelson Pereira
>  --
>
> *From:* [EMAIL PROTECTED] [mailto:
> [EMAIL PROTECTED] *On Behalf Of *Martin Wheldon
> *Sent:* Wednesday, April 16, 2008 11:12 AM
> *To:* rt-users@lists.bestpractical.com
> *Subject:* Re: [rt-users] RT as a intranet portal? Or other suggestions?
>
>
>
> I personaly use pmwiki and have been very happy with it.
>
>
>
> Martin
>
>
>
> On 4/16/08, *Nelson Pereira* <[EMAIL PROTECTED]> wrote:
>
> Hi all,
>
>
>
> Is there an extension that will make RT look like an intranet portal?
>
> To be able to put in articles, upload docs, and such?
>
>
>
> Or do you guys have any suggestions as a good Intranet Portal I could
> install on the same box as RT (RHEL5) ?
>
>
>
>
>
> *Nelson Pereira*
> Senior Network Administrator
>
> Protus IP Solutions Inc.
> [EMAIL PROTECTED]
> phone: 613.733. ext.528
> MyFax: 613.822.5083
> www.myfax.com
>
> Refer your friends and colleagues to MyFax!
> Click here for more information.
>
> [image: www.MyFax.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] MySQL Connect errorr

[Ruslan Zakirov]

the server != RT, but == mysql server! If you're going to use "older
password hashing algorithm" then you should read mysql docs to
understand consequences.

On Thu, Apr 17, 2008 at 5:22 PM, LDB <[EMAIL PROTECTED]> wrote:
> Does the following apply to RT ...
>
> Tell the server to use the older password hashing algorithm
>
>  ?
>
>  Thanks,
>
>
>  LDB
>
>  On Apr 17, 2008, at 9:17 AM, Ruslan Zakirov wrote:
>
>
> > This problem is related to mysql and has nothing to do with RT. It's
> > very well documented on mysql site.
> >
> > On Thu, Apr 17, 2008 at 5:02 PM, LDB <[EMAIL PROTECTED]> wrote:
> >
> > > I am receiving the following error when I connect my apache instance
> > > of RT:
> > >
> > > [Thu Apr 17 08:57:46 2008] [error] [client 192.168.10.66] Connect
> > > Failed Client does not support authentication protocol requested by
> > > server; consider upgrading MySQL client\n at /opt/rt3/lib/RT.pm line
> > > 220\n
> > >
> > > My MySQL version is 5.0.26 on SuSE 9 SP4 using the latest version of
> > > RT. My /etc/apache2/vhosts.d/rt.conf is ..
> > >
> > > 
> > >   ServerName rt.example.org
> > >   DocumentRoot /opt/rt3/share/html
> > >   ServerAdmin [EMAIL PROTECTED]
> > >   LogLevel debug
> > >   ErrorLog /var/log/apache2/rt_error_log
> > >   TransferLog /var/log/apache2/rt_access_log
> > >
> > >   AddDefaultCharset UTF-8
> > >
> > >   # this line applies to Apache2+mod_perl2 only
> > >   # Below line might be incorrect, I had to use:
> > >   # PerlModule Apache2::compat
> > >   # mod_perl 2.0.1 from FC4 Linux
> > >   #PerlModule Apache2 Apache::compat
> > >
> > >   SetHandler perl-script
> > >   PerlHandler RT::Mason
> > >
> > >   Alias /rt "/opt/rt3/share/html"
> > >   PerlModule Apache::DBI
> > >   PerlRequire /opt/rt3/bin/webmux.pl
> > >
> > >   
> > > AllowOverride All
> > > Options ExecCGI FollowSymLinks
> > > 
> > >Order allow,deny
> > > Allow from all
> > > 
> > >   
> > >
> > >   
> > > RewriteEngine On
> > > RedirectMatch permanent (.*)/$ $1/index.html
> > >   
> > > 
> > >
> > >
> > >
> > > Any ideas??
> > > ___
> > > 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
> > >
> > >
> >
> >
> >
> > --
> > Best regards, Ruslan.
> >
>
>



-- 
Best regards, Ruslan.
___
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

[rt-users] rt-mailgate stopped working please help

[Matthew Simpson]

Hi all,

I'm using Centos 4.5 and use the RT yum repo to install RT 3. Over the 
last week I have noticed this error in the mailog for sendmail:


sendmail[7784]: m3H2xC0A007792: to=|"/etc/smrsh/rt-mailgate --queue 
care-shifts --action correspond --url http://care.domain.com/";, 
ctladdr=<[EMAIL PROTECTED]> (8/0), delay=04:13:07, 
xdelay=00:00:00, mailer=prog, pri=483216, dsn=4.0.0, stat=Deferred: prog 
mailer (/usr/sbin/smrsh) exited with EX_TEMPFAIL


Delivery Fail:

   - Transcript of session follows -
RT server error.

The RT server which handled your email did not behave as expected. It
said:

Can't locate object method "tmp_recycling" via package "MIME::Parser" at 
/usr/lib/rt/RT/EmailParser.pm line 616.

Stack:
  [/usr/lib/rt/RT/EmailParser.pm:616]
  [/usr/lib/rt/RT/EmailParser.pm:225]
  [/usr/lib/rt/RT/EmailParser.pm:177]
  [/usr/lib/rt/RT/EmailParser.pm:137]
  [/usr/lib/rt/RT/Interface/Email.pm:523]
  [/var/rt/html/REST/1.0/NoAuth/mail-gateway:58]

|"/etc/smrsh/rt-mailgate --queue care-shifts --action correspond --url 
http://care.domain.com/";... Deferred: 421 4.4.2 sv2-2.per.domain.com 
Error: timeout exceeded
Warning: message still undelivered after 4 hours
Will keep trying until message is 5 days old


What has happened? Please help?



Matt




___
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] MySQL Connect errorr

[LDB]

Sure enough that was it ... :)

It uses the old client protocol ..

Thanks,

LDB

On Apr 17, 2008, at 9:17 AM, Ruslan Zakirov wrote:
> This problem is related to mysql and has nothing to do with RT. It's
> very well documented on mysql site.
>
> On Thu, Apr 17, 2008 at 5:02 PM, LDB <[EMAIL PROTECTED]> wrote:
>> I am receiving the following error when I connect my apache instance
>> of RT:
>>
>> [Thu Apr 17 08:57:46 2008] [error] [client 192.168.10.66] Connect
>> Failed Client does not support authentication protocol requested by
>> server; consider upgrading MySQL client\n at /opt/rt3/lib/RT.pm line
>> 220\n
>>
>> My MySQL version is 5.0.26 on SuSE 9 SP4 using the latest version of
>> RT. My /etc/apache2/vhosts.d/rt.conf is ..
>>
>> 
>>ServerName rt.example.org
>>DocumentRoot /opt/rt3/share/html
>>ServerAdmin [EMAIL PROTECTED]
>>LogLevel debug
>>ErrorLog /var/log/apache2/rt_error_log
>>TransferLog /var/log/apache2/rt_access_log
>>
>>AddDefaultCharset UTF-8
>>
>># this line applies to Apache2+mod_perl2 only
>># Below line might be incorrect, I had to use:
>># PerlModule Apache2::compat
>># mod_perl 2.0.1 from FC4 Linux
>>#PerlModule Apache2 Apache::compat
>>
>>SetHandler perl-script
>>PerlHandler RT::Mason
>>
>>Alias /rt "/opt/rt3/share/html"
>>PerlModule Apache::DBI
>>PerlRequire /opt/rt3/bin/webmux.pl
>>
>>
>>  AllowOverride All
>>  Options ExecCGI FollowSymLinks
>>  
>> Order allow,deny
>>  Allow from all
>>  
>>
>>
>>
>>  RewriteEngine On
>>  RedirectMatch permanent (.*)/$ $1/index.html
>>
>> 
>>
>>
>>
>> Any ideas??
>> ___
>> 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
>>
>
>
>
> -- 
> Best regards, Ruslan.

___
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] MySQL Connect errorr

[LDB]

Does the following apply to RT ...

Tell the server to use the older password hashing algorithm

?

Thanks,

LDB

On Apr 17, 2008, at 9:17 AM, Ruslan Zakirov wrote:
> This problem is related to mysql and has nothing to do with RT. It's
> very well documented on mysql site.
>
> On Thu, Apr 17, 2008 at 5:02 PM, LDB <[EMAIL PROTECTED]> wrote:
>> I am receiving the following error when I connect my apache instance
>> of RT:
>>
>> [Thu Apr 17 08:57:46 2008] [error] [client 192.168.10.66] Connect
>> Failed Client does not support authentication protocol requested by
>> server; consider upgrading MySQL client\n at /opt/rt3/lib/RT.pm line
>> 220\n
>>
>> My MySQL version is 5.0.26 on SuSE 9 SP4 using the latest version of
>> RT. My /etc/apache2/vhosts.d/rt.conf is ..
>>
>> 
>>ServerName rt.example.org
>>DocumentRoot /opt/rt3/share/html
>>ServerAdmin [EMAIL PROTECTED]
>>LogLevel debug
>>ErrorLog /var/log/apache2/rt_error_log
>>TransferLog /var/log/apache2/rt_access_log
>>
>>AddDefaultCharset UTF-8
>>
>># this line applies to Apache2+mod_perl2 only
>># Below line might be incorrect, I had to use:
>># PerlModule Apache2::compat
>># mod_perl 2.0.1 from FC4 Linux
>>#PerlModule Apache2 Apache::compat
>>
>>SetHandler perl-script
>>PerlHandler RT::Mason
>>
>>Alias /rt "/opt/rt3/share/html"
>>PerlModule Apache::DBI
>>PerlRequire /opt/rt3/bin/webmux.pl
>>
>>
>>  AllowOverride All
>>  Options ExecCGI FollowSymLinks
>>  
>> Order allow,deny
>>  Allow from all
>>  
>>
>>
>>
>>  RewriteEngine On
>>  RedirectMatch permanent (.*)/$ $1/index.html
>>
>> 
>>
>>
>>
>> Any ideas??
>> ___
>> 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
>>
>
>
>
> -- 
> Best regards, Ruslan.

___
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] MySQL Connect errorr

[LDB]

Yes, I have looked through the documentation there and none of it  
seemingly
applies. I will search again though ..

LDB

On Apr 17, 2008, at 9:17 AM, Ruslan Zakirov wrote:
> This problem is related to mysql and has nothing to do with RT. It's
> very well documented on mysql site.
>
> On Thu, Apr 17, 2008 at 5:02 PM, LDB <[EMAIL PROTECTED]> wrote:
>> I am receiving the following error when I connect my apache instance
>> of RT:
>>
>> [Thu Apr 17 08:57:46 2008] [error] [client 192.168.10.66] Connect
>> Failed Client does not support authentication protocol requested by
>> server; consider upgrading MySQL client\n at /opt/rt3/lib/RT.pm line
>> 220\n
>>
>> My MySQL version is 5.0.26 on SuSE 9 SP4 using the latest version of
>> RT. My /etc/apache2/vhosts.d/rt.conf is ..
>>
>> 
>>ServerName rt.example.org
>>DocumentRoot /opt/rt3/share/html
>>ServerAdmin [EMAIL PROTECTED]
>>LogLevel debug
>>ErrorLog /var/log/apache2/rt_error_log
>>TransferLog /var/log/apache2/rt_access_log
>>
>>AddDefaultCharset UTF-8
>>
>># this line applies to Apache2+mod_perl2 only
>># Below line might be incorrect, I had to use:
>># PerlModule Apache2::compat
>># mod_perl 2.0.1 from FC4 Linux
>>#PerlModule Apache2 Apache::compat
>>
>>SetHandler perl-script
>>PerlHandler RT::Mason
>>
>>Alias /rt "/opt/rt3/share/html"
>>PerlModule Apache::DBI
>>PerlRequire /opt/rt3/bin/webmux.pl
>>
>>
>>  AllowOverride All
>>  Options ExecCGI FollowSymLinks
>>  
>> Order allow,deny
>>  Allow from all
>>  
>>
>>
>>
>>  RewriteEngine On
>>  RedirectMatch permanent (.*)/$ $1/index.html
>>
>> 
>>
>>
>>
>> Any ideas??
>> ___
>> 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
>>
>
>
>
> -- 
> Best regards, Ruslan.

___
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] MySQL Connect errorr

[Ruslan Zakirov]

This problem is related to mysql and has nothing to do with RT. It's
very well documented on mysql site.

On Thu, Apr 17, 2008 at 5:02 PM, LDB <[EMAIL PROTECTED]> wrote:
> I am receiving the following error when I connect my apache instance
>  of RT:
>
>  [Thu Apr 17 08:57:46 2008] [error] [client 192.168.10.66] Connect
>  Failed Client does not support authentication protocol requested by
>  server; consider upgrading MySQL client\n at /opt/rt3/lib/RT.pm line
>  220\n
>
>  My MySQL version is 5.0.26 on SuSE 9 SP4 using the latest version of
>  RT. My /etc/apache2/vhosts.d/rt.conf is ..
>
>  
> ServerName rt.example.org
> DocumentRoot /opt/rt3/share/html
> ServerAdmin [EMAIL PROTECTED]
> LogLevel debug
> ErrorLog /var/log/apache2/rt_error_log
> TransferLog /var/log/apache2/rt_access_log
>
> AddDefaultCharset UTF-8
>
> # this line applies to Apache2+mod_perl2 only
> # Below line might be incorrect, I had to use:
> # PerlModule Apache2::compat
> # mod_perl 2.0.1 from FC4 Linux
> #PerlModule Apache2 Apache::compat
>
> SetHandler perl-script
> PerlHandler RT::Mason
>
> Alias /rt "/opt/rt3/share/html"
> PerlModule Apache::DBI
> PerlRequire /opt/rt3/bin/webmux.pl
>
> 
>   AllowOverride All
>   Options ExecCGI FollowSymLinks
>   
>  Order allow,deny
>   Allow from all
>   
> 
>
> 
>   RewriteEngine On
>   RedirectMatch permanent (.*)/$ $1/index.html
> 
>  
>
>
>
>  Any ideas??
>  ___
>  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
>



-- 
Best regards, Ruslan.
___
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

[rt-users] MySQL Connect errorr

[LDB]

I am receiving the following error when I connect my apache instance  
of RT:

[Thu Apr 17 08:57:46 2008] [error] [client 192.168.10.66] Connect  
Failed Client does not support authentication protocol requested by  
server; consider upgrading MySQL client\n at /opt/rt3/lib/RT.pm line  
220\n

My MySQL version is 5.0.26 on SuSE 9 SP4 using the latest version of  
RT. My /etc/apache2/vhosts.d/rt.conf is ..


ServerName rt.example.org
DocumentRoot /opt/rt3/share/html
ServerAdmin [EMAIL PROTECTED]
LogLevel debug
ErrorLog /var/log/apache2/rt_error_log
TransferLog /var/log/apache2/rt_access_log

AddDefaultCharset UTF-8

# this line applies to Apache2+mod_perl2 only
# Below line might be incorrect, I had to use:
# PerlModule Apache2::compat
# mod_perl 2.0.1 from FC4 Linux
#PerlModule Apache2 Apache::compat

SetHandler perl-script
PerlHandler RT::Mason

Alias /rt "/opt/rt3/share/html"
PerlModule Apache::DBI
PerlRequire /opt/rt3/bin/webmux.pl


  AllowOverride All
  Options ExecCGI FollowSymLinks
  
 Order allow,deny
  Allow from all
  



  RewriteEngine On
  RedirectMatch permanent (.*)/$ $1/index.html





Any ideas??
___
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

[rt-users] rt-mailgate stopped workng please help

[Matthew Simpson]

Hi all,

I'm using Centos 4.5 and use the RT yum repo to install RT 3. Over the 
last week I have noticed this error in the mailog for sendmail:


sendmail[7784]: m3H2xC0A007792: to=|"/etc/smrsh/rt-mailgate --queue 
care-shifts --action correspond --url http://care.domain.com/";, 
ctladdr=<[EMAIL PROTECTED]> (8/0), delay=04:13:07, 
xdelay=00:00:00, mailer=prog, pri=483216, dsn=4.0.0, stat=Deferred: prog 
mailer (/usr/sbin/smrsh) exited with EX_TEMPFAIL


Delivery Fail:

   - Transcript of session follows -
RT server error.

The RT server which handled your email did not behave as expected. It
said:

Can't locate object method "tmp_recycling" via package "MIME::Parser" at 
/usr/lib/rt/RT/EmailParser.pm line 616.

Stack:
  [/usr/lib/rt/RT/EmailParser.pm:616]
  [/usr/lib/rt/RT/EmailParser.pm:225]
  [/usr/lib/rt/RT/EmailParser.pm:177]
  [/usr/lib/rt/RT/EmailParser.pm:137]
  [/usr/lib/rt/RT/Interface/Email.pm:523]
  [/var/rt/html/REST/1.0/NoAuth/mail-gateway:58]

|"/etc/smrsh/rt-mailgate --queue care-shifts --action correspond --url 
http://care.mattysimpson.com/";... Deferred: 421 4.4.2 sv2-2.per.domain.com 
Error: timeout exceeded
Warning: message still undelivered after 4 hours
Will keep trying until message is 5 days old


What has happened? Please help?



Matt


___
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] I've asked the beginner perl group but no one responded

[Stefan Hornburg]

Sven Sternberger wrote:
> Hello!
> 
> just my 2c, Request Tracker is really a nice piece of
> Software which helps our organisation a lot
> 
> BUT
> 
> the distribution is a mess, the only thing an average
> sysadmin wants to do is to install via the package
> manager on his RT server, and to run from time to time
> an update with his package manager.
> I don't want to install via cpan perl modules which may be
> in conflict with versions from perl packages of the operating
> system. 

It shouldn't be hard to run a custom Perl just for RT.

Regards
Racke


-- 
LinuXia Systems => http://www.linuxia.de/
Expert Interchange Consulting and System Administration
ICDEVGROUP => http://www.icdevgroup.org/
Interchange Development Team

___
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] I've asked the beginner perl group but no one responded

[Sven Sternberger]

Hello!

just my 2c, Request Tracker is really a nice piece of
Software which helps our organisation a lot

BUT

the distribution is a mess, the only thing an average
sysadmin wants to do is to install via the package
manager on his RT server, and to run from time to time
an update with his package manager.
I don't want to install via cpan perl modules which may be
in conflict with versions from perl packages of the operating
system. 
For this convenience I'm sure there would be also some
customer willing to pay a subscription fee.

till this happy days I will tar,make,cpan 

regards!

sven

On Mi, 2008-04-16 at 20:30 +0400, Ruslan Zakirov wrote:
> Except that it's 3.6.x where x < 6 (I think it's still 3.6.1) and when
> users of this package come to list they have less chances to get
> feedback and fixes.


___
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] I've asked the beginner perl group but no one responded

[Stefan Hornburg]

Ruslan Zakirov wrote:
> On Wed, Apr 16, 2008 at 7:14 PM, Toby Darling <[EMAIL PROTECTED]> wrote:
>>
>>  Stefan Hornburg wrote, On 16/04/2008 15:26:
>>
>>> Vivek Khera wrote:
>>  >> On Apr 16, 2008, at 9:57 AM, Mike Peachey wrote:
>>  >>> I disagree. Distribution packaging systems cause a LOT of RT
>>  >>> problems. Manual installation or platform-independent packaging is a
>>  >>> much better way of managing RT and using CPAN to perform perl
>>  >>> installations is by far the best automatable method.
>>  >> Must be crappy packages.  The freebsd packages work wonderfully across
>>  >> upgrades.
>>  >
>>  > I also have good experiences with packaged RT. In my case the Debian
>>  > packages were easy to install and that saved a lot of work.
>>
>>  Agreed, RT on debian's easy. Thank you Niko.
> Except that it's 3.6.x where x < 6 (I think it's still 3.6.1) and when
> users of this package come to list they have less chances to get
> feedback and fixes.

Right, but I think it is still easier to backport it from testing
than installing from scratch.

Regards
Racke



-- 
LinuXia Systems => http://www.linuxia.de/
Expert Interchange Consulting and System Administration
ICDEVGROUP => http://www.icdevgroup.org/
Interchange Development Team


___
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