Dear Jesse, Thank you for your quick response.
You wrote: > > This is but one of many fairly important bugfixes. Rather than further > customizing your RT 3.4 instance, I'd strongly consider putting that > effort toward coming up to 3.8. > We have some reasons to postpone upgrading to 3.8-latest. Can you advice something in our current situations? We made a workaround - set "UNLINK => 0" and cleanup procedure is running by cron. It seems it's workable. -- Agnislav Onufrijchuk PortaOne, Inc., RT Developer Tel: +1-866-SIP VOIP (+1 866 747 8647) ext. 7670 Meet us at Internet Telephony East February 2-4, 2009 - Booth 826 Miami Beach Convention Center _______________________________________________ http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users Community help: http://wiki.bestpractical.com Commercial support: [EMAIL PROTECTED] Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy a copy at http://rtbook.bestpractical.com
