FreeBSD Port: courier-imap-2.2.1,1
ian at mahuron.org
Mon Feb 2 14:42:43 PST 2004
I have not contacted the developers. I am not sure this has anything to do
with MySQL integration. On a hunch, I downgraded after reading the
The CPU utilization issue was also present on my installation. While
trying to query a folder with more than 10 messages in it, utilization for
that daemon would reach 99% utilization until I shot it down with SIGTERM.
By downgrading, I was able to kill two birds with one stone. Both issues
which occurred under 2.2.1 are absent in 2.1.1.
You will notice that the aforementioned thread references issues in 2.1.0
and a downgrade to 2.0. Do you recall what was changed between 2.1.0 and
2.1.1? 2.1.1 seems quite stable.
I have not tried 2.1.2 or 2.2.0.
--On Monday, February 02, 2004 23:10 +0100 Oliver Lehmann
<oliver at FreeBSD.org> wrote:
> Hi Ian,
> Ian Mahuron wrote:
>> First let me thank you for maintaining these fine Courier-IMAP ports!
>> I'm not sure if this is the correct way to address this, but I ran
>> into some serious trouble with the 2.2.1,1 port over the weekend.
>> System is FreeBSD 4.9. I had complied with both MySQL and SSL
>> support. I experienced various server connection closures (server
>> initiates close w/ FIN) in both SSL and non-SSL modes. Upon reverting
>> to 2.1.1,1, I restarted all processes using very same configuration
>> files, and everything works perfectly.
>> I found ML posts on google from others with the very same problem.
>> They reverted to an older version as well.
> Hm... I'm sorry to say, that I have no experience with
> courier-imap+mysql. What is the official statement from the developers?
> Are those problems fixed in CVS (so we may provide a patch for the
> port), or are they suggest to downgrade? How does it perform on 2.2.0,
> or 2.1.2 (just in case we really have to downgrade)?
> Oliver Lehmann
More information about the freebsd-ports