Hi,
What I had noticed is that although the mail was read and removed from the POP3 account, the database was down and therefore no tickets were created and those messages were lost.
mmh, if it really behaves this way, I think it's worth opening a bug to otrs's bugzilla...
Wouldn't it be a better idea for this script to check whether the SQL server is up before trying to pick up mail?
Or work in a transactional way: issue the POP3 'dele' command to a message only once this message has been successfully stored into the database. One message after the other. This way any unsaved message will stay in the pop3 server until it's in the database...
Eric
_______________________________________________ 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/
