On Sat, Mar 7, 2015, at 11:21 PM, Rudy Gevaert wrote: > > Quoting David Carter <dpc22@xxxxxxxxx>, Fri, 06 Mar 2015: > > > On 2015-03-05 23:47, Bron Gondwana wrote: > >> On Thu, Mar 5, 2015, at 08:34 PM, Rudy Gevaert wrote: > >>> > >>> Quoting Frank Richter <frank.richter@xxxxxxxxxxxxxxxxxx>, Thu, 05 > >>> Mar 2015: > >>> > >>> > Last night ecactly this happened on our mail server the 1st time. > >>> > One partition was filled up ... The user was noticing "some > >>> > duplicate messages", but not thousands. I'll check up if a virus > >>> > scanner is involved in our case. > > > >> This isn't a Cyrus issue or even something that Cyrus can fix I > >> don't think :( > > > > One thing which would help is a limit on the amount of expunged data > > which can be held in a single mailbox before an expire automatically > > kicks in. > > As far as I know there isn't a way to actually see this from cyrus. > For know I have a script that goes over every mailbox and does a a du > and cyrus quota lookup. If they are to much different (e.g. 200MB > difference) I force an expunge. > > This also catches mailboxes that haven't been expired like it should be. > > An other way to catch clients that are misbehaving is to count nr of > entries for user_deny for that user in the log file. The client that > is misbehaving is always at the head of the list. We have a plan to keep the count in the cyrus.index header and make it available via an annotation(metadata). https://bugzilla.cyrusimap.org/show_bug.cgi?id=3562 Bron. -- Bron Gondwana brong@xxxxxxxxxxx ---- Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ To Unsubscribe: https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus
