On Wed, 11 Aug 2004, Nathan Ollerenshaw wrote:
> The reason I ask is that we have an app that can't read some of the
> files. Turns out, they're reading it incorrectly. They are assuming
> that there will be a XXXXC entry after the XXXXS entry, but this might
> not be the case. Nowhere in the spec for Maildir++ does it say that any
> of the entries are mandatory.
When Exim creates a maildirsize file, it will always write both an S and
a C entry on the first line.
>
> [root@??? root]# cat
> /data/mail/85/59/flyflyfly.net/me@???/Maildir/maildirsize
>
> 0 0
> -686 -1
> 2864 1
> -2864 -1
> 6997 1
> 618 1
> 1378 1
> 1628 1
> 1637 1
>
> Note that blank line at the beginning. Thats kinda odd, but not sure if
> its exim doing that or not?
The Exim code does not appear to be capable of doing that. It either
writes a new file containing
xxxS, xxxC
n m
or it adds one line to the file, containing "n 1".
--
Philip Hazel University of Cambridge Computing Service,
ph10@??? Cambridge, England. Phone: +44 1223 334714.
Get the Exim 4 book: http://www.uit.co.uk/exim-book
