Last modified: 2009-06-04 17:06:11 UTC
The junk queue is continuing to build up (currently holding 198,382 messages).
I'm told this also means the spam filters aren't getting trained as that's done at the same time as the deleting. Shouldn't it be possible to train the filter as messages come in even they're not being deleted?
If storage is not a problem and the growing queue doesn't make OTRS slower, I don't think there's a need to delete them (unless there's some training silliness). False positives do happen, and in case of queries mentioning previous messages or other uncertainty about reception[1], it's useful to be able to see if any have been junked. [1] http://lists.wikimedia.org/pipermail/foundation-l/2007-November/034529.html
(In reply to comment #2) > If storage is not a problem and the growing queue doesn't make OTRS slower, I > don't think there's a need to delete them (unless there's some training > silliness). False positives do happen, and in case of queries mentioning > previous messages or other uncertainty about reception[1], it's useful to be > able to see if any have been junked. > > [1] http://lists.wikimedia.org/pipermail/foundation-l/2007-November/034529.html > We don't need all junk tickets forever. There is just no reason to store it. People regularly look in the junk queue to make sure nothing is there that shouldn't be however, when there are hundreds of thousands of messages there (currently there are 280,135 messages), people will not even bother to look. So really, it is more helpful to keep it reduced in size and continue to check regularly for misplaced tickets, as we were doing before.
Still growing and currently at 408,676. I mention it again because it seems to have negative effects on the speed of the system. Over the last month or so, all page loads on OTRS are taking longer. As the number of junk tickets goes up, the load time goes up as well. Is this a coincidence or not? If not, I'll open a separate bug. If the amount of messages in the junk queue is playing a role, I'd hope that we can get to this soon.
The DELETE option has been re-enabled while the Junk queue is getting purged. Cary is in the process of purging the queue itself. Hopefully this will improve the situation.
