On Tue, Sep 20, 2016 at 4:26 PM, Thierry Thelliez
wrote:
> Hello,
>
> Under RT 4.2, is it possible to not automatically create a user from the CC
> field?
It is possible to create a user - that has an email address as a
"name". RT uses the field "name" to mean username.
I just tested it on my 4.
Hello all,
I finally have RT sending out emails on the company's server, so we're
ready to move forward with testing things and making changes. To that end,
I'm wondering how everyone manages testing changes without affecting the
primary instance, then moving those changes into production?
My firs
On Wed, Sep 21, 2016 at 12:50:51PM -0400, Alex Hall wrote:
> Hello all,
> I finally have RT sending out emails on the company's server, so we're
> ready to move forward with testing things and making changes. To that end,
> I'm wondering how everyone manages testing changes without affecting the
>
Do you run from source? If not, how did you direct RT to use alternative
paths during the install rather than using all the same ones and thus
failing to install or overriding existing files?
Were I to attempt a source install again, could I safely do so alongside
the current 4.2.8 instance on the
On Wed, Sep 21, 2016 at 02:12:00PM -0400, Alex Hall wrote:
> Do you run from source? If not, how did you direct RT to use alternative
> paths during the install rather than using all the same ones and thus
> failing to install or overriding existing files?
>
> Were I to attempt a source install ag
Hi
I am using RT4.4.1.
I got some complains from some of my users because most of the times when
users reply to tickets, normally by email, RT get the following message in the
ticket body.
“ Message body is not shown because it is too large.”
I intend to avoid users to click in download (un
Set($MaxInlineBody, 9);
https://docs.bestpractical.com/rt/4.4.1/RT_Config.html
-m
On Wed, Sep 21, 2016 at 1:23 PM, yugi wrote:
> Hi
>
> I am using RT4.4.1.
> I got some complains from some of my users because most of the times when
> users reply to tickets, normally by email, RT get the fo
On Wed, Sep 21, 2016 at 11:50 AM, Alex Hall wrote:
> Hello all,
> I finally have RT sending out emails on the company's server, so we're ready
> to move forward with testing things and making changes. To that end, I'm
> wondering how everyone manages testing changes without affecting the primary
>
Hi all,
I'm planning to add a "type" field globally. Initially, this will be a list
containing "discussion", "problem", and, maybe, "critical issue". What I'm
wondering, though, is whether the selection of a value from this list can
do anything? That is, could selecting "discussion" force the prior
Hi Alex,
On Wed, Sep 21, 2016 at 3:55 PM, Alex Hall wrote:
> Hi all,
> I'm planning to add a "type" field globally. Initially, this will be a list
> containing "discussion", "problem", and, maybe, "critical issue". What I'm
> wondering, though, is whether the selection of a value from this list c
I am trying to avoid creating a user in the first place. From what I have
been able to trace in the RT code, a first class user is created from the
CC field.
But that's a bit confusing in our case. We are using our own external
authentication system and when CCs are automatically created, our sy
11 matches
Mail list logo