atom feed9 messages in net.sourceforge.lists.courier-imapRe: [Courier-imap] max value for mail...
FromSent OnAttachments
Felipe NeuwaldJan 30, 2008 11:08 am 
Sam VarshavchikJan 30, 2008 4:31 pm 
Felipe NeuwaldJan 31, 2008 3:01 am 
Sam VarshavchikJan 31, 2008 4:08 am 
Felipe NeuwaldJan 31, 2008 4:10 am 
Jose CelestinoJan 31, 2008 6:50 am 
Francis GaliegueJan 31, 2008 6:59 am 
Jose CelestinoJan 31, 2008 7:06 am 
Francis GaliegueJan 31, 2008 7:25 am 
Subject:Re: [Courier-imap] max value for maildirsize
From:Francis Galiegue (fg@one2team.net)
Date:Jan 31, 2008 7:25:06 am
List:net.sourceforge.lists.courier-imap

Le jeudi 31 janvier 2008, Jose Celestino a écrit :

Words by Francis Galiegue [Thu, Jan 31, 2008 at 03:59:36PM +0100]:

Le jeudi 31 janvier 2008, Jose Celestino a écrit :

Words by Sam Varshavchik [Thu, Jan 31, 2008 at 07:08:11AM -0500]:

Felipe Neuwald writes:

Does anybody knows how can I fix this?

Upgrade to a 64 bit platform.

On some platforms, it is possible to enable 64 bit file size support by using some custom flags when compiling code, usually by defining _FILE_OFFSET_BITS=64 or _LARGE_FILES=1. If that's the case, you will need to reconfigure and recompile everything, with those custom flags.

I'm running a 32bit platform. That's the only way?

Yes, until someone changes certain fundamental laws of physics in this universe, which limits signed 32 bit values to a maximum value of 2147483647.

Of course that you could use a long long. You know that, right?

Provided that the target compiler supports it. AFAIK, Courier IMAP doesn't require gcc.

And being long long supported on C99 and assured to be 64 bits is of no value, of course.

Not all compilers support C99. In fact, gcc doesn't even support the whole standard.

And, well, the problem is with MySQL to start with - which also happens not to require gcc anyway.