Thanks for your kind reply.
Then no need to worry about as the closed tickets may get delete. There are several options, in that I found a option to generate the tickets in the pdf format. We need to do it for each ticket which consume more time. So is there any way by which weekly/monthly once I can generate all closed tickets in one pdf file. If yes, it would be very helpful to store the ticket details in another machine also.
I saw the url, but users are getting mails when they sign up for for time. and It is sending mails to the users when they request for forgotten password which means I think sendmail option is enabled by default. I need auto response to the users about their new and closed tickets.
Do we have authority to customize the otrs product as our own? I mean, do we have authority to change name, logo etc.
Originally Posted by Mitchal
I have got OTRS up and running on Centos as well and have been running it for about 6 months now. I can't see any reason for OTRS deleting any historical data unless otherwise specified. In terms of where your new customers and agents have been stored.... i'm not really good at running queries on a DB and someone chime in if they have a good idea of what query to run but maybe you could setup another install of otrs on centos in a virtual machine and point it to 1 database at a time to see what info is present and what is missing. I couldn't imagine the data being stored across multiple db's though.
I trust you have consulted the documentation for the sendmail function in otrs http://doc.otrs.org/2.0/en/html/c1216.html
Also what are your logs saying? they can be found in admin>system log. are the replies being generated and attached to the ticket record but just not being sent out?