Hi,

I am having a problem with how maildrop creates the maildirsize file. It seems to add extra spaces before the size and between the size and count fields. This is causing a problem with a proprietary webmail product by Mintersoft, that regards this file as corrupted and removes it, which results in it reporting that users have 0 usage and 0 quota.

Using qmail+ldap, maildirsize would look like this: [root@craniac Maildir]# cat maildirsize 15728640S,4000C 175298 22 2241 1 1715 1

which webmail would deal with nicely, and report that I have 6% of 15MB used. However when I started using maildrop for my MDA, it makes the maildirsize file look like this:

[root@craniac Maildir]# cat maildirsize 15728640S,4000C 175298 22 2241 1 1715 1

which causes webmail to freak out. I tried looking at the C code to find out where the extra spaces were being inserted, but I am not familiar enough with C to find it. The maildir++ spec, from the courier page states:

"The quota definition is a list, separate by commas. Each member of the list consists of an integer followed by a letter, specifying the nature of the quota. Currently defined quota types are 'S' - total size of all messages, and 'C' - the maximum count of messages in the maildir. For example, 10000000S,1000C specifies a quota of 10,000,000 bytes or 1,000 messages, whichever comes first.

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 messages."

So the spec specifies that there should be a single space bewteen the two values. There are more. It doesn't say anything about leading spaces, but I can't see a reason to put them in there. Anyone have any ideas or opinions on this?