Cron.sh as root

Hi,

This is my first contribution (and first day in use ) to otrs.
Thanks for it!

I wasn't able to get otrs running with apache-2.0.53 and mod_perl-1.99.17, i 
have now apache-1.3.33 and mod_perl-1.27-r4 on 
Gentoo Linux with preloaded perl libs.

I have written a little patch witch allows me to run ~otrs/bin/Cron.sh as 
root.

cmd: ~otrs/bin/Cron.sh (start|stop|restart) <otrs_user> <otrs_home>

With friendly regards,

Jochum Rene

P.s.: sry, for my poor english

_______________________________________________
OTRS mailing list: dev - Webpage: http://otrs.org/
Archive: http://lists.otrs.org/pipermail/dev
To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/dev

Change of contact

Anyone that needs to reach me regarding any of our submissions to the 
OTRS project can now reach me at jason.dixon <at> amti.com.  My email 
address at NASA (jason <at> nccs.nasa.gov) should no longer be used.

Thanks,

--
Jason Dixon
Technical Lead, Open Source Tools
AMTI, Inc.

_______________________________________________
OTRS mailing list: dev - Webpage: http://otrs.org/
Archive: http://lists.otrs.org/pipermail/dev
To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/dev

Re: [announce] OTRS 2.0 beta1 (Klong Jark Beach) Released

On 2-05-2005 at 10:19, Stefan Rother wrote:

 >The OTRS Team is pleased to announce the first beta release of the
 >Trouble-Ticket-System OTRS 2.0.0 beta1.

Thank you very much for this release, it's very interesting. However:

1) I see that my recent patch was not merged in 2.0.0 although it's very 
   very simple and it was ready for merging in 1.3:

   http://bugs.otrs.org/show_bug.cgi?id=664

2) Robert Mathews' patch is still pending although it's very quick (just 
   remove wrap=hard). Note that I have been testing his patch for 
   months.

   http://bugs.otrs.org/show_bug.cgi?id=526

3) I have another tiny feature request I've been testing locally for a 
   year: accesskey attributes in HTML. This is useful for avoiding mouse 
   or tabkey to click on links and buttons. If the OTRS team agree on 
   this, I can provide a full patch against 2.0.0 beta1.

- Alessandro Ranellucci
_______________________________________________
OTRS mailing list: dev - Webpage: http://otrs.org/
Archive: http://lists.otrs.org/pipermail/dev
To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/dev

Re: Re: [announce] OTRS 2.0 beta1 (Klong Jark Beach) Released

Hi Alessandro,

Alessandro Ranellucci wrote:
>  >The OTRS Team is pleased to announce the first beta release of the
>  >Trouble-Ticket-System OTRS 2.0.0 beta1.
> 
> Thank you very much for this release, it's very interesting. However:

Thanks! Also thanks for your help!

> 1) I see that my recent patch was not merged in 2.0.0 although it's very 
>    very simple and it was ready for merging in 1.3:
> 
>    http://bugs.otrs.org/show_bug.cgi?id=664

I added the part with date, Cc, ... With the "wrap" see below.

> 2) Robert Mathews' patch is still pending although it's very quick (just 
>    remove wrap=hard). Note that I have been testing his patch for 
>    months.
> 
>    http://bugs.otrs.org/show_bug.cgi?id=526

I'll start a new email to this "wrap" on the list. I'd have some questions.

> 3) I have another tiny feature request I've been testing locally for a 
>    year: accesskey attributes in HTML. This is useful for avoiding mouse 
>    or tabkey to click on links and buttons. If the OTRS team agree on 
>    this, I can provide a full patch against 2.0.0 beta1.

text area wrap - Problem / Feedback

Hi,

I want to discuss the text area wrap for mac, linux and win users
(http://bugs.otrs.org/show_bug.cgi?id=526).

We implemented this patch for OTRS 2.0 beta1. But we forgot to remove 
the "wrap" from the .dtl files. :-/

We will change this and it would be fine if this could be tested in OTRS 
2.0 beta2. Feedback on this list is really welcome.

Thanks!

   Martin

--
((otrs.de)) :: OTRS GmbH :: Norsk-Data-Str. 1 :: 61352 Bad Homburg
         http://www.otrs.de/ :: Manage your communication!

_______________________________________________
OTRS mailing list: dev - Webpage: http://otrs.org/
Archive: http://lists.otrs.org/pipermail/dev
To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/dev

Re: Mail Header problems (spam filter)

Hi Ritme,

Ritme Informatique wrote:
> we are using popfile as a spam proxy for otrs, it is performing very
> well (over 99.5 % of precision), but some spam mail do not get
> filtered by the postmaster filter.
> Popfile works by adding a header called "X-Text-Classification", so I
> filter on this in my postmaster.
> 
> The problems is on some mails containing additionnal space in Subject,
> Otrs doesn't recognize the rest of the headers as Headers.
> 
> Here is an example:
> 
> Return-Path: <cvujhsuonyqse <at> wondstops.com>
> Received: from Dickson (194.98.113.80) by globald.com with SMTP
> (Eudora Internet Mail Server X 3.2.6); Tue, 5 Apr 2005 02:03:12 +0200
> Return-Path: eiuliq <at> wondstops.com
> From: "Sherry" <cvujhsuonyqse <at> wondstops.com>
> Reply-To: "Sherry" <cvujhsuonyqse <at> wondstops.com>
> Date: Mon, 4 Apr 2005 17:04:38 -0700
> To: MAILhidden <at> ritme.com
> Subject: Budget tight? Get  up to 1500 USD by tomorrow
> 
> Message-ID : <746847.5684276 <at> wondstops.com>  Content-Type:
> text/plain;charset="iso-8859-1
> Message-ID: <1099463104-184944895 <at> globald.com>
> X-Text-Classification: spam
> 
> In fact the part starting with the Message ID is dumped in the email

Re: Re: [announce] OTRS 2.0 beta1 (Klong Jark Beach) Released

On 3-05-2005 at 8:12, Martin Edenhofer wrote:

 >> 3) I have another tiny feature request I've been testing locally
 >> for a year: accesskey attributes in HTML. This is useful for
 >> avoiding mouse or tabkey to click on links and buttons. If the OTRS
 >> team agree on this, I can provide a full patch against 2.0.0 beta1.
 >
 >I remember. :) I like this feature. The problem because this feature
 >is on in cvs is, because how to use it in a multi language frontend?

I would choose standard and cross-language keys, as in normal
applications ("P" for print, "O" for open etc.). I don't think we must
display the key in the name, as they could just be listed separately in
a help page.

What do you think about this?

As always - thank you for the prompt reply :)

  - Alessandro Ranellucci

_______________________________________________
OTRS mailing list: dev - Webpage: http://otrs.org/
Archive: http://lists.otrs.org/pipermail/dev
To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/dev

"hexcheck" number generator

Attached

--

-- 
Now using M2, Opera's e-mail client: http://www.opera.com/m2/

_______________________________________________
OTRS mailing list: dev - Webpage: http://otrs.org/
Archive: http://lists.otrs.org/pipermail/dev
To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/dev

Hexcheck number generator

[What happens when you click "send" instead of "attach"? :)]

So, now it _is_ attached: this is a
  ~otrs/Kernel/System/Ticket/Number/ generator for a shorter
hexa numbering with kind of checksum. Our customers complained
about the DateCheck's length, so this is shorter. The
output ticket numbers are like: Ticket# 70141D0.

In /etc/otrs/Kernel/Config.pm:
     $Self->{'Ticket::NumberGenerator'} =  
'Kernel::System::Ticket::Number::HexCheck';
     $Self->{'Ticket::NumberGenerator::HexCheck::MinCounterSize'} = 5;

Enjoy!

--

-- 
Now using M2, Opera's e-mail client: http://www.opera.com/m2/

_______________________________________________
OTRS mailing list: dev - Webpage: http://otrs.org/
Archive: http://lists.otrs.org/pipermail/dev
To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/dev

2.0beta observations

[btw last mail's hexcheck was for 2.0beta in this form, but could be  
"backported"
by changing Ticket::Whatevers to TicketWhatevers in the code]

I installed 2.0beta1, some observations.

- postgres upgrade script _still_ contains mysql in the comment as example  
)

Apart from that, upgrade worked almost seamless. Some Config.pm variables
were changed (like my very first comment showed: TicketNumberGenerator  
became
Ticket::NumberGenerator and like that), I figured this out pretty painfully
for my own module mentioned up there.

Linking and merging actually work, which is great, but not really what I'd
expect, comments below:

- I would expect closing a parent would close all its descendants (children
and grandchildren etc), or at least have the possibility to do so.

- Parents should be able to see all notes/entries of children together
(probably using a "show all children" link), and navigate through them.
I imagine every line would contain the source of the line, a clickable
ticket number, if user want to attach new note to there. Or even a [note  
here]
link? (I hope I was able to tell what I mean :))

- Merge should have similiar UI to linking: a chooser. I hate to memorise
ticket numbers.