Received: from localhost (maia-4.hub.org [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 5975A9FC1B2 for ; Thu, 8 Mar 2007 20:46:36 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-new, port 10024) with ESMTP id 37433-02 for ; Thu, 8 Mar 2007 20:46:31 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from linuxworld.com.au (unknown [203.34.46.50]) by postgresql.org (Postfix) with ESMTP id A74839FC17B for ; Thu, 8 Mar 2007 20:46:30 -0400 (AST) Received: from linuxworld.com.au (IDENT:swm@localhost.localdomain [127.0.0.1]) by linuxworld.com.au (8.13.2/8.13.2) with ESMTP id l290kSfi032651; Fri, 9 Mar 2007 11:46:28 +1100 Received: from localhost (swm@localhost) by linuxworld.com.au (8.13.2/8.13.2/Submit) with ESMTP id l290kS4v032648; Fri, 9 Mar 2007 11:46:28 +1100 X-Authentication-Warning: linuxworld.com.au: swm owned process doing -bs Date: Fri, 9 Mar 2007 11:46:28 +1100 (EST) From: Gavin Sherry X-X-Sender: swm@linuxworld.com.au To: lissette cc: pgsql-performance@postgresql.org Subject: Re: help In-Reply-To: <1173180973.063890.208190@30g2000cwc.googlegroups.com> Message-ID: References: <1173180973.063890.208190@30g2000cwc.googlegroups.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200703/185 X-Sequence-Number: 23590 On Tue, 6 Mar 2007, lissette wrote: > 2007-02-02 16:41:03 [Thread-6 ] message(s) in mail box> > 2007-02-02 16:41:13 [Thread-39 ] an ebxml message from mail box> > 2007-02-02 16:41:13 [Thread-39 ] > > 2007-02-02 16:41:14 [Thread-39 ] outgoing message: 20070202-164113-85...@192.168.2.105> > 2007-02-02 16:41:25 [Thread-6 ] collecting message from mail box> > hk.hku.cecid.piazza.commons.net.ConnectionException: Unable to > connect > to incoming mail server > by javax.mail.AuthenticationFailedException: [LOGIN-DELAY] > minimum > time between mail checks violation > at > hk.hku.cecid.piazza.commons.net.MailReceiver.connect(MailReceiver.java: > 66) Did you actually read the error message? This seems unrelated to PostgreSQL and definately not related to PostgreSQL performance. Gavin