From owner-freebsd-questions@FreeBSD.ORG Fri Aug 1 04:26:02 2008 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5E27D106566C for ; Fri, 1 Aug 2008 04:26:02 +0000 (UTC) (envelope-from af300wsm@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.229]) by mx1.freebsd.org (Postfix) with ESMTP id 2C2FB8FC18 for ; Fri, 1 Aug 2008 04:26:02 +0000 (UTC) (envelope-from af300wsm@gmail.com) Received: by rv-out-0506.google.com with SMTP id b25so1201094rvf.43 for ; Thu, 31 Jul 2008 21:26:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:to:subject:date :user-agent:cc:references:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:message-id; bh=9Ocy1hQYZwoxXZ/wm9sIRPaJZRAlnGbFz60dRkxT2y8=; b=DB4tX6h9KO3LpY8aPkzqZoxnMXiDyuL9M7iyc4un3sfLXOqg4O+NLVMdnnpYullvJL J1+LYsV//rEGwqKRlHWUIUDrZ/Tf04FOEr9wnIuyOE9DQM6JYXIm3coWeWC4CisH1IBv S7NdXgD0ufucZIqttJPcbssVfx+d5Oi1gfZQk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:subject:date:user-agent:cc:references:in-reply-to :mime-version:content-type:content-transfer-encoding :content-disposition:message-id; b=c9vgP535yeojeRbiUBlMpYVallZf+oktJn85oD+StN18/aMIob5FnptS+Jo6pfa3o/ iQqlPYlbDonTMYS0f0fz7q3ioMaLoiEuX+xzZdwfiQtFfFOyEM5SdLUm764Ebz5uRXPx d4kI7+bzyq/P30g+yTTpJiAS6jRbXo07jAtSo= Received: by 10.141.210.13 with SMTP id m13mr5713304rvq.25.1217564761770; Thu, 31 Jul 2008 21:26:01 -0700 (PDT) Received: from sniper ( [71.221.191.175]) by mx.google.com with ESMTPS id k2sm916942rvb.4.2008.07.31.21.26.00 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 31 Jul 2008 21:26:01 -0700 (PDT) From: Andrew Falanga To: "Barry Byrne" Date: Thu, 31 Jul 2008 22:25:56 -0600 User-Agent: KMail/1.9.6 References: <200807301835.17740.af300wsm@gmail.com> <000801c8f2f0$3a49ff60$72010c0a@wbt.wbtsystems.com> In-Reply-To: <000801c8f2f0$3a49ff60$72010c0a@wbt.wbtsystems.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200807312225.57211.af300wsm@gmail.com> Cc: 'FreeBSD Questions' Subject: Re: Having some problems with a FreeBSD mail server (SMTP) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Aug 2008 04:26:02 -0000 On Thursday 31 July 2008 03:31:36 Barry Byrne wrote: > > Andrew: > > I've seen a similar problem from time to time with Outlook 2003 clients. > For seemingly no reason whatsoever, they give a timeout sending mail. > Googling the error code throws up many with the same error and no solution > that I've found. Telneting to port 25 or even running the Outlook test mail > account feature still work, while Outlook comlains it can't send. > > The workaround is to quit Outlook and start again. By quitting Outlook, the > user must choose 'exit' from the 'file' menu. Simply closing the close box > still leaves Outlook in memory and the problem remains. The problem seems > to happen perhaps once or twice a month for some users. > > Regards, > > Barry To everyone who responded, Thanks for the great suggestions. A couple of you replied that they've seen issues with this and resolved them by closing down Outlook, by the "File --> Exit" method rather than the "X" in the upper right. I'm really beginning to suspect this because the pastor I was working with told me that our senior pastor explained to him that he could send from a particular coffee shop in town when he couldn't from church. Though I can't personally see a down side to having an office in a Starbucks (I don't know the name of the actual shop they were in), I think that the Outlook client get's some bad stuff in the cache that is flushed out when they shutdown their computers to go make the journey. The pastor I was dealing with said he went there and all of this mail sent without a hitch. The other possibility is that the ISP is blocking some particular port. We did just change ISP's within the last 2 weeks and according to this pastor, these sending problems originated at that time. We'll see. Andy