X-Spam-Check-By: sourceware.org Date: Sun, 16 Jul 2006 10:47:14 -0500 From: "David E. Bath" To: cygwin@cygwin.com Subject: Re: fetchmail 6.3.1-1 problem Message-ID: <20060716154714.GA1012@newsguy.com> References: <20060617161937.GA1348@newsguy.com> <20060716010236.GD1120@tishler.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060716010236.GD1120@tishler.net> User-Agent: Mutt/1.4.2.1i Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com On Sat, Jul 15, 2006 at 09:02:36PM -0400, Jason Tishler wrote: > > David, > > On Sat, Jun 17, 2006 at 11:19:37AM -0500, David E. Bath wrote: > > I recently updated fetchmail 6.3.1-1 from 6.2.5-2. I now get an error > > when it connects to one of my mail servers. Using "fetchamil -v" I > > noticed a difference in the output that indicates the likely problem. > > > > 6.3.1-1 give this message when the connection fails: > > > > fetchmail: 6.3.1 querying mail.********.*** (protocol POP3) at Fri Jun 16 15:05:3 > > 1 2006: poll started > > fetchmail: getaddrinfo("mail.********.***","pop3s") error: nodename nor servname > > provided, or not known > > fetchmail: POP3 connection to mail.********.*** failed: Operation not permitted > > I was able to workaround the above by adding the following line to > /etc/services: > > pop3s 995/tcp #POP3 SSL > > Jason This looked very promising, but alas, no dice. David Bath -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/