Hello I have done the upgrade procedure to move from 4.2.12 to 4.4 version.
Cleaned cache, started my webserver, enable SLA on all queues and then run
the etc/upgrade/upgrade-sla scritp. I have noticed that the Due of all
tickets is set to ('not set'). How can I avoid this?
Status: rejected
SLA:
Hello,
Is it possible to group tickets in Search/Result.html by Owner?
What I wanna do is:
+--+
+ Tickets with owner: owner1
+
Glad to hear that. Waiting for the fix.
--
View this message in context:
http://requesttracker.8502.n7.nabble.com/REST-mail-gateway-using-100-cpu-tp56255p56375.html
Sent from the Request Tracker - User mailing list archive at Nabble.com.
Sorry for my lack of knowledge. Still I think that RT, to be more precise,
Email::Address:List module should reject this kind of header and not stuck
in infinity regex loop.
What I was able to get from mail sender, he was using Microsoft Outlook Web
App.
--
View this message in context:
I don't think so.
First point, correct me if I'm wrong - An 'encoded-word' MUST NOT appear in
any portion of an 'addr-spec' :
It says, that you can't have the following syntax: Name Surname
name@=?UTF-8?B?abc=?=
See http://tools.ietf.org/html/rfc2047#page-11, the examples section, where
the
Falcone-2 wrote
On Wed, Jan 15, 2014 at 12:26:28PM -0800, andriuss wrote:
From:
=?UTF-8?B?ICJUb21hcyBNYXLEjWl1bGlvbmlzIiA8VG9tYXMuTWFyY2l1bGlvbmlzQGJp?=
=?UTF-8?B?dGVzcGFydG5lcmlzLmx0Pg==?=
This line, in the mail was the problem, RT somehow hang when parsing this
in
I18N.pm. Any solution
From:
=?UTF-8?B?ICJUb21hcyBNYXLEjWl1bGlvbmlzIiA8VG9tYXMuTWFyY2l1bGlvbmlzQGJp?=
=?UTF-8?B?dGVzcGFydG5lcmlzLmx0Pg==?=
This line, in the mail was the problem, RT somehow hang when parsing this in
I18N.pm. Any solution for this?
--
View this message in context:
RT 4.2.2
Apache2::CmdParms2.04/usr/lib/perl5/Apache2/CmdParms.pm
Apache2::Const 2.04/usr/lib/perl5/Apache2/Const.pm
Apache2::Directive 2.04/usr/lib/perl5/Apache2/Directive.pm
Apache2::Log 2.04/usr/lib/perl5/Apache2/Log.pm
Hello,
I got this process im my apache
POST //REST/1.0/NoAuth/mail-gateway HTTP/1.1
It hangs there until I kill it manualy, because it takes 100% of server cpu.
Is the any way to fix it, cause I don't understand the reason why it behaves
so.
--
View this message in context:
