I've been testing out the latest maildrop version (1.63.20040608) with the
new 64-bit safe maildir quota code, and it appears at least on my 32-bit
system to have an overrun when calculating the total size of a mailbox.
The OS/architecture in question is FreeBSD-4.9/x86.
The calculation works fine up to the point where the mailbox needs to be
tallied for over quota or summarization (i.e. adding up the individual
message entries in maildirsize), but produces very large integers for the
summary calculation. I've verified that the released 1.6.3 doesn't have
this issue and I didn't check if Courier-IMAP 3.0.5 does or not, but I
assume it would based on the release notes and the sharing of code between
the two.
For example, with a quota of 1000S (its small for testing), 1.6.3 produces
the following:
1000S
900 2
But, for 1.6.3.20040608, it produces:
1000S
42949673860 2
This is on the same mail spool, using the same messages already in the
spool and attempting to deliver a new message that will force the mailbox
over quota. The only thing thats different between the deliveries is the
maildrop binary used.
Options used when configuring maildrop:
./configure \
--enable-maildrop-uid=mailuser \
--enable-maildrop-gid=mailuser
--enable-smallmsg=32768 \
--enable-global-timeout=120 \
--enable-maildirquota \
--with-trashquota \
--enable-userdb
Has anyone else seen this problem?
Thanks,
-Doug
-------------------------------------------------------
This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference
Learn from the experts at JavaOne(SM), Sun's Worldwide Java Developer
Conference, June 28 - July 1 at the Moscone Center in San Francisco, CA
REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority Code NWMGYKND
_______________________________________________
courier-users mailing list
[EMAIL PROTECTED]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
