Hi,
I am getting this message in my email, day in and day out:
Subject: Cron root@otrsserver /opt/otrs/bin/PostMasterMailbox.pl /dev/null
ERROR: OTRS-PMAccount-10 Perl: 5.8.8 OS: linux Time: Wed Feb 8 13:52:02 2012
Message: Bad filter
Traceback (12123):
Module:
Do you have any '*' symbols in any of your postmaster filters? I
remember for a while this gave me some grief aswell, from what I
remember I had tried to do a filter like EMAILADDRESS:*@domain.com -
this had to be corrected to EMAILADDRESS:.*@domain.com (extra .
infront of the *)
Steve
On 8
Just did the migration using the backup.pl script, so far so good and
everything looks great!
Anything else missing to be done? :)
Thank you all!
Thanks
//M
On Tue, Feb 7, 2012 at 8:47 AM, Michiel Beijen michiel.bei...@gmail.comwrote:
Hi Rob,
On Sun, Feb 5, 2012 at 02:09, Robinson
Ok, I reply to myself:
OTRS 3.1 admin manual is available:
http://doc.otrs.org/3.1/en/html/auth-backends.html#agent-auth-backends; now it
need a new line in Config.pm: $Self-{'AuthModule::UseSyncBackend'} =
'AuthSyncBackend';
Juan Clavero Almirón
Gestiò d’Identitats, Firma i Custòdia
Oficina
On 2012-02-08 04:09, Muhammad El-Sergani wrote:
Just did the migration using the backup.pl http://backup.pl script, so
far so good and everything looks great!
Anything else missing to be done? :)
Hard to tell as you only mention that you used one tool...
Hi All,
We are getting this error message:
ERROR: No Ticket::StateAfterPending found for 'Monitor - Auto Close' in
Kernel/Config.pm!
I found something that seemed to say I needed the following in our
Kernel/Config.pm file
so I added it but we are still getting the above mentioned error
Hi Michiel and others,
Without having yet migrated to 3.1, I have at least done some sleuthing
on a system that is born with 3.0 and upgraded to 3.1, and I have a
stong feeling that YAML is the issue...
On my original 2.4 system, the previous administrator have installed
YAML through CPAN in
Sorry for top posting, but I think I found it:
I do have translated states, so I had to adjust my config:
For the second error (closed successful)
Core::Ticket::StateAfterPending:
I had changed the Key, but forgot to change the Content.
However, I still haven't found for the first one, which
Hello,
You could get that info using an SQL query: the ticket table has a field
called customer_user_id which has the login of the customer (or his email
in case he is not a registered customer) and you can join it with the
customer_user table where the first_name and last_name of all your
Hallo Zusammen,
dies kann man sehr einfach umsetzen: zuerst entfernen wir die
Auswahlmöglichkeit für eine Queue aus dem NewTicketView und anschließend
definieren immer eine Default Queue z.B. Eingang.
Es landen nun alle neuen Tickets in der Eingang Queue und die Agents können
diese in andere
10 matches
Mail list logo
