Ken
Just last week I got it working by doing what Sebastien said
(ldaps://) and following the instructions in
http://lists.otrs.org/pipermail/dev/2004-March/000418.html
but I wasn't able to add the modules via CPAN, I just used Yast to add
the perl SSL modules (which I noted had the IO::Socket::SS
t is something like new the next
default state would be 'open' . But what I am seeing is that even
when the state is new, the next default is closed...
(I hope that made sense...)
On 6/30/05, Christian Schoepplein <[EMAIL PROTECTED]> wrote:
> Hi Kevin,
>
> On Wed, Jun 29, 20
Hi all!
When a customer logs in to the UI and zooms into an existing ticket,
they have the option of attaching a webrequest to the ticket.
Unfortunately, the next state of the ticket defaults to
Closed-Resolved. This has caused a couple of customers to
accidentally close their tickets then wonder
Hi All,
My system seems to be eating M$ Word attachments (.doc)
Other types of attachments come in fine.
Below is from my procmail log when a mail with a .doc is received.
Any ideas on what to check would be greatly appreciated!
procmail: Executing "/opt/otrs/bin/PostMaster.pl"
DBD::mysql::db
Actually, anybody can send an email into the system, but you gain
loads of functionality if you setup the customeruser information...
If you have AD (I'm assuming the same is true for OpenLDAP), its
relatively easy to set up the Agent, CustomerAuthentication and
CustomerUser to get their infomatio
ck, then check again before posting...
Thanks!
On 5/26/05, Kevin Kasner <[EMAIL PROTECTED]> wrote:
> Hi All,
> Love OTRS so far (and my CIO is going to love it more!)...Have it
> running on SuSe 9.3 w/ MySQL and Apache2.
>
> I have LDAP/AD working perfeclty (as far as
Hi All,
Love OTRS so far (and my CIO is going to love it more!)...Have it
running on SuSe 9.3 w/ MySQL and Apache2.
I have LDAP/AD working perfeclty (as far as I can tell ) for the
Agents and for the Customer Backend, but I'm running into trouble
getting it to work for the Customer Authentication.
I just got otrs working on my Suse 9.2 system & ran into the same
problem. I found the answer in the otrs FAQ (after much digging):
Title: SUSE Linux: Invalid command 'Perlrequire'...
Category: webserver
State: public (all)
Language: en
Keywords: apache mod_perl perl suse
Attachment: