Hi Wesley,
Thank you for your info.
It gives me a clearer idea how it works.
The multiple front-ends with the imap aggregator would give a huge
advantage for expanding when more resources are needed, so this is an
option i would like to use.
The only issue i can think of is backups of the
Bron Gondwana wrote:
On Mon, Feb 08, 2010 at 11:29:22AM -0500, Ken Murchison wrote:
Bron Gondwana wrote:
On Mon, Feb 08, 2010 at 07:53:21AM +0100, Garry wrote:
Hi,
after wondering for a while why occasionally my sieve script rules
wouldn't work, I just found the reason (I guess) - Sieve
I've been noticing idle pop3d processes on our Cyrus front end server
for some time. These should be transient. One that was several days
old had an established TCP connection to a wireless client that had
disappeared. Presumably the client never closed the connection.
Setting TCP keepalive on
On Fri, 2010-02-05 at 09:54 +, Simon Fraser wrote:
On Thu, 2010-02-04 at 16:27 -0500, Brian Awood wrote:
We've seen somewhat similar behavior with the Apple Mail client in the
past.
My guess is it's IDLE related. If your using Apple Mail that came with
10.5,
it's IDLE
On Fri, Feb 12, 2010 at 10:18:02AM -0500, Ken Murchison wrote:
Bron Gondwana wrote:
On Mon, Feb 08, 2010 at 11:29:22AM -0500, Ken Murchison wrote:
Bron Gondwana wrote:
On Mon, Feb 08, 2010 at 07:53:21AM +0100, Garry wrote:
Hi,
after wondering for a while why occasionally my sieve script
On Fri, Feb 12, 2010 at 09:45:02AM -0600, Gary Mills wrote:
I've been noticing idle pop3d processes on our Cyrus front end server
for some time. These should be transient. One that was several days
old had an established TCP connection to a wireless client that had
disappeared. Presumably
Shouldn't these client connections already be handled by the poptimeout
timeout options? unless you have it set to zero...
We have had problems within the murder (old code had several spots where
murder front - back communications could deadlock)..
On Sat, 13 Feb 2010, Bron Gondwana wrote:
On Fri, Feb 12, 2010 at 03:59:31PM -0600, Paul M Fleming wrote:
Shouldn't these client connections already be handled by the poptimeout
timeout options? unless you have it set to zero...
They don't seem to be. We're using the default timeout setting.
It seems to have no effect on front end
