Joshua E Warchol writes: > Here is an example of one maildirsize file: > > 209715200S > 23801 1 > -23760 -1 > > > My MTA isn't writting the proper message count, so there is probably more > than just one message in the box before that message was deleted. > > But the problem is with the 3rd line. The maildir++ spec says that the > removal value must be at the start of the line (where did that whitespace > come from?) and that it is seperated from the message count by one space
It doesn't say that, although it does say something slightly different, which I'll have to fix. All remaining lines all contain two integers separated by a single space. The first integer is interpreted as a byte count. The second integer is interpreted as a file count. A Maildir++ writer can add up all byte counts and file counts from maildirsize and enforce a quota based either on number of messages or the total size of all the > (more spaces or a tab here?). Has anyone seen this before. When it happens > I've seen courier report the wrong value to a GETQUOTA command. It shouldn't. Maildirquota code was revised in courier-imap 1.5.1, hence the change in format, but the new code should still be able to read any legacy leftover cruft. -- Sam ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Two, two, TWO treats in one. http://thinkgeek.com/sf _______________________________________________ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
