On Sun, 29 Oct 2006, henckens wrote:
Well, one possibility is if you built the software in 64-bit mode. If
you did, try rebuilding it in 32-bit mode. The IMAP software is
currently untested in 64-bit mode, and I've heard reports of some
issues when it is built in 64-bit mode.
ouch, I have to install the 32-bit libraries first then, I was hoping that I
never needed them.
Definitely try a build in 32-bit mode. There is nothing in UW IMAP that
would benefit from a 64-bit build; all IMAP protocol values are 32-bit.
More is not necessarily better in this case; you'll just get a bigger (and
generally slower) binary.
UW IMAP was designed not to be dependent upon processor word size; it
builds and runs fine on 16-bit and 36-bit(!) processors as well as 32-bit.
However, the C language made extensions for 64-bit (e.g., the "long long"
type) that it doesn't know about. Also, some casts between 64 and 32
involving pointers don't work as expected. The upshot is that in the
64-bit world, applications actually need to know the word size.
Large file (>2GB) support is independent of 64-bit mode; 64-bit mode is
neither sufficient nor necessary for large files. Any 64-bit development
will be for large files first (although I hear some beleaguered sysadmins
screaming "NO!!!"...).
But here is also some LMTP involved to amavisd-new and back.
That shouldn't affect things normally.
-- Mark --
http://panda.com/mrc
Democracy is two wolves and a sheep deciding what to eat for lunch.
Liberty is a well-armed sheep contesting the vote.
_______________________________________________
Imap-uw mailing list
[email protected]
https://mailman1.u.washington.edu/mailman/listinfo/imap-uw
