Thank you for your reply. Now I'm scratching my head, because other
than admins and "privileged users", no one has "View Queue" permissions
in my platform and I'm not getting any error as you described.
Hoping someone can shed some light here per this anomaly.
I recommend https://discordapp.com
Information Technology | Informationstechnik
Stuttgarter Str. 3
Phone: +49 351 205768-167
Fax: +49 351 205768-999
Greetings new and recent adopters to RT!
I recently joined the community and though I have RT running in a
production environment, I have it running in the most basic of
The best way I learn is through interaction of other newbies and
Unfortunately I do not
Update: I remembered that I installed JSGantt and Calendar via aptitude
and the other plugins via Makefile.PL, make, make install. So I now
decided to deinstall everything and reinstall all plugins by one method
via Makefile.PL, make, make install.
My "double directory structure" is now no more
I'm still pretty new to RT, so would like to join such a session. Thanks.
Sent from my iPhone
> On Nov 22, 2016, at 08:25, Reza wrote:
> Greetings new and recent adopters to RT!
> I recently joined the community and though I have RT running in a production
there are no "secrets" in our customization I disabled the check which prevents
send an email to a queue adress (we process income mails with procmail and
send emails which were adressed to an other queue to the staff member of this
We just went live with RT 4.4.1 and it seems that LDAP authentication is
It has now died 2 days in a row, at approximately the same time.
The RT log is showing the following error:
2819] [Mon Nov 21 21:10:28 2016] [critical]:
RT::Authen::ExternalAuth::LDAP::_GetBoundLdapObj Can't bind:
I think you may have misinterpreted my screenshot. "Everyone",
"Privileged", "Unprivileged", "Owner", etc are all "highlighted" just to
show that there are selected permissions under that group. The bold one
is "Everyone", which is the current selection and what permissions are
On Tue, Nov 22, 2016 at 04:13:46PM -0500, Mike Johnson wrote:
> We just went live with RT 4.4.1 and it seems that LDAP authentication is
> It has now died 2 days in a row, at approximately the same time.
> The RT log is showing the following error:
> 2819] [Mon Nov 21 21:10:28
Update: I now replaced 1.01 with 0.07 (since this one is slightly
diferent in configuration). Still getting
 [Tue Nov 22 15:28:51 2016] [error]: could not find component for path
Den 2016-11-22 kl. 14:43, skrev Sinapius, Vinzenz:
> I recommend https://discordapp.com
Is there video at discordapp.com?
RT 4.4 and RTIR training sessions, and a new workshop day!
* Los Angeles - January 9-11 2017
I guess we will decide about the app later on.
Focus of this thread is to see who is interested to participate in group
study. There are hundreds of apps and possibilities we can address
later on. Simplest is telephone conference and I'm assuming most of us
are in North America. Long
I now made research from bottom to top and found out that all files
under /usr/local/share/request-tracker4/plugins were root:staff and 0775
- except RTx-Calendar, which was 0444. I chmoded to 0775 and heureka!
Calendar is displayed. What a...
What still does not work: The inline
I now upgraded again to 1.01, and the inline images are displayed. No
more error messages in the logfile.
One thing though:
The documentation of Calendar says
Edit your /opt/rt4/etc/RT_SiteConfig.pm
If you are using RT
I faced a similar challenge when I first started to use RT. As
commented by our friend, the "view queue" has nothing to do with the
issue you faced.
The issue is, "/... attempted to create a ticket via email in the queue
Incident Reports; you might need to grant 'Everyone' the
Mail list logo