RT 4.2.13 backed by PostgreSQL, though I feel like we've been
experiencing the following for many versions.
I've been suspect for quite some time, but thought maybe I was losing my
mind instead. I've confirmed finally that I am not losing my mind re: RT
in this specific case. We are definitely see
To my knowledge, yes, mail is routed through use of the subject line. When you
create a queue, you give it a tag that is used in email subjects, and that is
combined with the ticket ID to form the basis for how RT knows which
queue/ticket a given message goes to. However, you can customize the r
Thank you for your detailed response Jeff.
Thinking out of the box, a Random Number is not necessary if we can mask
it from email responses. In my specific case, I do not want non-staff
to access RT. Only support agents.
Is some sort of ID number absolutely necessary in the subject field a
On Oct 25, 2016, at 2:17 PM, Alex Hall
mailto:ah...@autodist.com>> wrote:
Hello list,
Every so often, and seemingly randomly, I see this error in /var/log/messages
just as the FCGI server stops working:
Oct 25 13:43:07 RTServer RT: [8137] Argument "username" isn't numeric in
numeric ne (!=) at
OH! I should mention that code stanza below is taken from the rt-4.4.1.tar.gz
since I don't have 4.4.1 installed.
On Oct 25, 2016, at 2:29 PM, Landon Stewart
mailto:lstew...@internap.com>> wrote:
I think it has something to do with the reminders if that helps. The following
if() statement is
Hello list,
Every so often, and seemingly randomly, I see this error in
/var/log/messages just as the FCGI server stops working:
Oct 25 13:43:07 RTServer RT: [8137] Argument "username" isn't numeric in
numeric ne (!=) at /opt/rt4/sbin/../lib/RT/Interface/Web.pm line 3027.
It shows up three times,
I'm just taking a shot in the dark, not knowing the code base well, but
what about this. You keep the actual number, but add things before and
after it. For instance:
1207b6988c77
where the ID is 988. Your filter is a letter followed by a number, then
your ID, then a letter. You can add random numb
Hi Alex,
On Tue, Oct 25, 2016 at 1:55 PM, Alex Hall wrote:
>
> I know, in theory, how to make such a change now. What I'm wondering is how
> hard it might be. If anyone has ever done this before, can you give an idea
> of what is involved? The UI is one part, but what behind-the-scenes changes
>
All,
People at work are wanting me to modify RT so that the one-time CC options
on ticket replies are instead full CCs. That is, anyone added there is
CC-ed on the full ticket rather than on just the transaction being made. No
one wants to use the 'people' tab, and one-time CC-ing isn't something
a
Reza writes:
>The use case for random IDs is quite simple. Ascending / serial number
>of IDs compromises confidentiality. End users would be able to guess
>how busy I could be with the amount of tickets answered. Its something
>I don't want to disclose. Almost ALL ticketing systems I have
>
> Sorry for not seeing this sooner, but I'll leave this for people wondering
> about the same in the future.
>
> We have sucessfully deleted single attachments from a ticket using
> rt-shredder. Issue the command like this;
>
> rt-shredder --plugin 'Objects=Attachment,'
>
This is what I expect
Greetings Jeff:
Thank you for your reply.
The use case for random IDs is quite simple. Ascending / serial number
of IDs compromises confidentiality. End users would be able to guess
how busy I could be with the amount of tickets answered. Its something
I don't want to disclose. Almost A
?Hello,
Sorry for not seeing this sooner, but I'll leave this for people wondering
about the same in the future.
We have sucessfully deleted single attachments from a ticket using rt-shredder.
Issue the command like this;
rt-shredder --plugin 'Objects=Attachment,?'
We use RT 4.2.8.
Med ve
Reza writes:
>The last 24-48 hrs has been an amazing learning experience. I feel
>as-if I can do Kung Fu now :)
>
> From my recent agenda of:
>
> 1. Create Random Ticket numbers.
> 2. Suppress "RT System Itself - Outgoing email recorded"
> 3. Customization of Auto ticket reply.
> 4. Assigning tic
Maik Nergert writes:
>is there a simple way to proof, that a message and the attachment was
>delivered to the recipient?
>It would be much better if the recipient has to confirm, that the
>message arrived and he has read it.
SMTP, by definition cannot do this. It cannot even guarantee delivery.
--- Begin Message ---
Hello!
I would like to ask if I can rename the word "Owner" in RT.
I modified the file en.po and indeed the word changed.
However, it changed BOTH for the TICKET Owner and the ASSET Owner.
I cannot find a way to change ONLY the ASSET Owner, although I specified it as
followi
--- Begin Message ---
Hello everybody,
I need your help on the following, please.
I would like to allow sorting of the Asset List in the SelfService.
I create a copy (Customization with local dir) of the relevant file
/opt/rt4/share/html/User/Elements/AssetList
in the local dir: /opt/rt4/local/h
Hi,
we have migrated to another server with newer Debian and this issue
suddenly dissapeared. So I wanted just let you know. Thanks to Jeffrey
Pilant for interest and morale support :)
Petr
On 1.6.2016 11:04, Petr Hanousek wrote:
> Dear all,
> we have here some users who have such a habit to keep
Hi @all,
is there a simple way to proof, that a message and the attachment was
delivered to the recipient?
It would be much better if the recipient has to confirm, that the
message arrived and he has read it.
best
Maik
smime.p7s
Description: S/MIME Cryptographic Signature
-
RT 4.4
19 matches
Mail list logo