by SysKoll » Fri Jan 16, 2004 4:34 pm
The eaten message log was the subject of a very delicate trade off. It's a demanding feature (both in terms of storage and CPU). The current implementation is a baseline. Were we to extend the eaten message logs, SG would need several hundreds of MB immediately, not to mention a potentially pegged CPU. Both are a no-no for a free service.
So there is little hope here, unless Josh gets free extra storage from his hosting provider.
-- SysKoll