Hi there, I'm running OTRS v2.0.4p01-4 under Debian Etch which has been upgraded from Sarge with OTRS v1.x on it.
I manually upgraded the PostgreSQL database schema because this wasn't done during the automatic upgrade, and all seems to work fine, excepted the notifications. If I create a ticket by sending an email to [EMAIL PROTECTED], the ticket is created and put in the correct queue. So it seems that procmail is correctly launched and PostMaster.pl correctly parses the message. If I login as a fake customer user and create a ticket it is created correctly and viewable when I login as a normal user. If when logged as a normal user I answer a ticket by email, the message is sent correctly to the customer user. BUT normal users are never notified that a new ticket has been created, which renders OTRS in fact unusable. If while logged in as the admin I send an admin notification, it is correctly sent to normal users though. I've checked my mail server logs and nothing gets sent. If when logged as an admin I view the system log, I've got : "OTRS-PM-10 Sent agent 'NewTicket' notification to '[EMAIL PROTECTED]'." So it appears that OTRS "believes" that it has sent the notification but in fact wasn't able to do this. I use Exim as the outgoing SMTP server, and nothing appears in mainlog, rejectlog or paniclog, so OTRS fails somewhere before the notification gets sent. Any idea of what I should do to manually send a fake notification to diagnose the problem further ? Thanks in advance for any help bye Jerome Alet _______________________________________________ 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 Support oder Consulting für Ihr OTRS System? => http://www.otrs.de/
