Index: [Article Count Order] [Thread]

Date:  Fri, 13 Apr 2007 14:55:49 -0400
From:  "Darrell D. Mobley" <dmobley (at mark) uhostme.net>
Subject:  [coba-e:09561] Re: Dovecot/POP3 Flood
To:  <coba-e (at mark) bluequartz.org>
Message-Id:  <002201c77dfd$5a279590$0e76c0b0$@net>
In-Reply-To:  <200704131740.l3DHe1oY022280 (at mark) srv1.nickelnetworks.com>
References:  <000e01c77b7c$16426680$42c73380$ (at mark) net> <200704131740.l3DHe1oY022280 (at mark) srv1.nickelnetworks.com>
X-Mail-Count: 09561

I think it is imperative for us to find the cause of Dovecot's problems and
resolve them.  Email is a mission critical component for most webhosting
accounts, probably more so than the actual serving of web pages.  If we
allow this deficiency to cripple the BQ platform, it's going to kill the
project.  No one will want to migrate to or install a web hosting platform
that will hobble the email aspect of your operations.

 

From: Paul Aviles [mailto:paul.aviles (at mark) nickelnetworks.com] 
Sent: Friday, April 13, 2007 1:40 PM
To: coba-e (at mark) bluequartz.org
Subject: [coba-e:09559] Re: Dovecot/POP3 Flood

 

I think this is the issue that will never die.. I am seeing the same
behavior on servers with the latest releases also...

 

Regards,

 

Paul Aviles

Nickel Networks

 

 

  _____  

From: Darrell D. Mobley [mailto:dmobley (at mark) uhostme.net] 
Sent: Tuesday, April 10, 2007 10:25 AM
To: coba-e (at mark) bluequartz.org
Subject: [coba-e:09510] Re: Dovecot/POP3 Flood

For all of its problems, at least the old system worked.  Can't say that
much for dovecot.


	

9561_2.html (attatchment)(tag is disabled)