Hi ALL,

I would like to upload more than 500 customer data in to postgres db of OTRS. I was tried with copy and pg_upload that have not been successful.

Any help?


SMPM

On Mon, Jun 11, 2012 at 5:30 PM, <otrs-request@otrs.org> wrote:
Send otrs mailing list submissions to
       otrs@otrs.org

To subscribe or unsubscribe via the World Wide Web, visit
       http://lists.otrs.org/cgi-bin/listinfo/otrs
or, via email, send a message with subject or body 'help' to
       otrs-request@otrs.org

You can reach the person managing the list at
       otrs-owner@otrs.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of otrs digest..."


Today's Topics:

  1.  Error fetchting mails with IMAPTLS (Johannes Homuth)
  2.  change ticketing numbering (Neil Simpson)
  3. Re:  change ticketing numbering (Steven Carr)


----------------------------------------------------------------------

Message: 1
Date: Mon, 11 Jun 2012 10:47:26 +0200
From: Johannes Homuth <johannes.homuth@sourcepark.de>
Subject: [otrs] Error fetchting mails with IMAPTLS
To: otrs@otrs.org
Message-ID: <4FD5B09E.4080603@sourcepark.de>
Content-Type: text/plain; charset="iso-8859-15"; Format="flowed"

Hi List,

I setup my OTRS System last week (Version 3.1.6) and everything works
fine. But I get stuck on an "Error" which is displayed in the
SystemProtocol. It always says that he can't process mail the Array
would be empty. I mean, there is no mail every time the cron job will
check, but that isn't an error I guess?!? Does anyone have the same
problem and/or know how to fix that?


   Aktuelle Eintr?ge im Systemprotokoll

Zeit    Priorit?t       Einrichtung     Nachricht
Mon Jun 11 10:22:02 2012        notice  OTRS-otrs.PostMasterMailbox.pl-10
IMAPTLS: Fetched 1 email(s) from xxxx/xx.xx.xx.xx
Mon Jun 11 10:22:02 2012        error   OTRS-otrs.PostMasterMailbox.pl-10
IMAPTLS: Can't process mail, email no ARRAY(0x3322e88) is empty!


--
-------------------------------------------------------
SOURCEPARK GmbH
B.Sc. Johannes Homuth
Hohenzollerndamm 150
14199 Berlin

Tel.    : +49 (0) 30 / 39 80 68 30
Fax     : +49 (0) 30 / 39 80 68 39
e-mail  : johannes.homuth@sourcepark.de
www     : www.sourcepark.de
------------------------------------------------------
SOURCEPARK GmbH
Sitz der Gesellschaft: Berlin / Amtsgericht Charlottenburg
HRB 80254
Gesch?ftsf?hrung: Matthias Barmeier, Harald D?rr
------------------------------------------------------

Wichtiger Hinweis: Die vorgenannten Angaben werden jeder E-Mail automatisch hinzugef?gt
und lassen keine R?ckschl?sse auf den Rechtscharakter der E-Mail zu.

Diese Email kann vertrauliche und/oder rechtlich gesch?tzte Informationen
enthalten. Wenn sie nicht der richtige Adressat sind oder diese E-Mail irr-
t?mlich erhalten haben, informieren Sie bitte sofort diesen Absender und ver-
nichten Sie diese E-Mail. Das unerlaubte Kopieren sowie die unbefugte
Weitergabe dieser E-Mail ist nicht gestattet.



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.otrs.org/pipermail/otrs/attachments/20120611/13599123/attachment-0001.html>

------------------------------

Message: 2
Date: Mon, 11 Jun 2012 10:51:39 +0200
From: Neil Simpson <nadsys@gmail.com>
Subject: [otrs] change ticketing numbering
To: "User questions and discussions about OTRS." <otrs@otrs.org>
Message-ID:
       <CAD-pqJZuxNEHv4U-ngM5P=hB1YtkXB5X0t=r5FNkHK6ZJo4How@mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"

We have two ticket systems running currently and in certain cases they send
mail to each other. The problem we have is that tickets are being merged
together that shouldn't be due to the numbering in the subject. For example
first otrs system had a ticket 1, then second otrs system sends a ticket to
it also with ticket 1 number, now there merged but two totally different
issues.

Can we change the ticket numbering to make one system unique. so instead of
Ticket#2012060110000065, maybe Ticket#2012060110000065a. then both systems
could not get tickets confused with one another.

thanks

Neil
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.otrs.org/pipermail/otrs/attachments/20120611/4b0068b8/attachment-0001.html>

------------------------------

Message: 3
Date: Mon, 11 Jun 2012 10:12:02 +0100
From: Steven Carr <sjcarr@gmail.com>
Subject: Re: [otrs] change ticketing numbering
To: "User questions and discussions about OTRS." <otrs@otrs.org>
Message-ID:
       <CALMep04ArNes6U=yT8wBDqYU+HA+ZspLbRsk-iFFaxMRwkzPoQ@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

You system IDs are the same (looks like they are both set to the default:
10), change the ID in Framework -> Core -> SystemID so that both systems
are unique.

Steve



On 11 June 2012 09:51, Neil Simpson <nadsys@gmail.com> wrote:

> We have two ticket systems running currently and in certain cases they
> send mail to each other. The problem we have is that tickets are being
> merged together that shouldn't be due to the numbering in the subject. For
> example first otrs system had a ticket 1, then second otrs system sends a
> ticket to it also with ticket 1 number, now there merged but two totally
> different issues.
>
> Can we change the ticket numbering to make one system unique. so instead
> of Ticket#2012060110000065, maybe Ticket#2012060110000065a. then both
> systems could not get tickets confused with one another.
>
> thanks
>
> Neil
>
>
>
> ---------------------------------------------------------------------
> OTRS mailing list: otrs - Webpage: http://otrs.org/
> Archive: http://lists.otrs.org/pipermail/otrs
> To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.otrs.org/pipermail/otrs/attachments/20120611/e504d66f/attachment-0001.html>

------------------------------

---------------------------------------------------------------------
OTRS mailing list: otrs - Webpage: http://otrs.org/
Archive: http://lists.otrs.org/pipermail/otrs
To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs

End of otrs Digest, Vol 45, Issue 15
************************************