From owner-freebsd-questions@freebsd.org Thu Nov 16 23:11:27 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3F3A4DECE36 for ; Thu, 16 Nov 2017 23:11:27 +0000 (UTC) (envelope-from luzar722@gmail.com) Received: from mail-io0-x235.google.com (mail-io0-x235.google.com [IPv6:2607:f8b0:4001:c06::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 023606FFC8 for ; Thu, 16 Nov 2017 23:11:27 +0000 (UTC) (envelope-from luzar722@gmail.com) Received: by mail-io0-x235.google.com with SMTP id w127so6954262iow.11 for ; Thu, 16 Nov 2017 15:11:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-transfer-encoding; bh=14kQpb10AYAZ3LVuJL2PeMtGm4Exw9scq/lC4v+DjWU=; b=StNaSDK1/TH3JI+09muQx6LSJ0xA+Ju1PG0GcOku0zrzGy/jhONkrNdZUuJ1n3j5MX MUa36GbZ0/8oMcc92NJLEaI1eSh7oIzCVJ6mAS1DDX9IhgXRLfwhFEZxI19C3Mu6kMx/ xR7ABgDaCnpDMyXVZmxKYpi3eOn08qoxoo0E+oeofSYhNx08cwYL1bxdA6LzPLvC+9Jr CrUhT/iQQyBiePAYqB5qBHXCHqWfur/7FG+2Ta1FHzvXXMMsWdENlypCYpyRliM8afKQ qH6gjLZ1elYiMZ7swKDX6/uitXZ1D1LibYvFs4kyixGFSYWuPsM74KVPQtM5vU/UEuRP kHFg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-transfer-encoding; bh=14kQpb10AYAZ3LVuJL2PeMtGm4Exw9scq/lC4v+DjWU=; b=sUuEXoOW8bosGX7GIxc1Ni9OgSXlYCAons6TVpcdW9Sf2jqMElb4V1VXYlsNUW1Sk5 yxu23wvZwEJv13Cy+wKMhZ2AIhOw3JOIPkcZ/VMxOVMf44dBkUVncuso7ipXgRuB/UnA A4Kb8Lidt/fXc+QhPaQlO2eC1cWfRnjDs6B1734/Rcd7s/Zp+D0aQ5CKWMo+jJUtr3tG eYDD4CD5caHfn7rT3v7eNMXcBB3/NKZYUG720YPAYybVVcwqTw0fI0TVx6FlCfA0ByC1 125CYq8Z/UZHasMuhNkCisohZSgCPfQ8NbQ3aiIFaEXhtiyNIjn9eBytfjnNsyhV1ARR us+w== X-Gm-Message-State: AJaThX4tztb/lbmFQyYiBCBE9D2/pcyD3puhJsiKoMJpWuP80KGpZMm8 vYVigYVrl5YUVTgOBljgRbrtpg== X-Google-Smtp-Source: AGs4zMYzuilpXEos45XI/RoDpG/Q5xhntF2V33CHxgpYpr7obh+y61NZ/rlzuBch25u13ncSNp5vAQ== X-Received: by 10.107.180.77 with SMTP id d74mr626453iof.118.1510873886389; Thu, 16 Nov 2017 15:11:26 -0800 (PST) Received: from [10.0.10.7] (cpe-65-25-50-122.neo.res.rr.com. [65.25.50.122]) by smtp.googlemail.com with ESMTPSA id g195sm1484560itc.14.2017.11.16.15.11.25 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Thu, 16 Nov 2017 15:11:25 -0800 (PST) Message-ID: <5A0E1B1D.60406@gmail.com> Date: Thu, 16 Nov 2017 18:11:25 -0500 From: Ernie Luzar User-Agent: Thunderbird 2.0.0.24 (Windows/20100228) MIME-Version: 1.0 To: Polytropon CC: "freebsd-questions@freebsd.org" Subject: Re: fetchmail References: <5A0C4C88.70105@gmail.com> <20171115152344.d08dfe4f.freebsd@edvax.de> <5A0C5727.7080105@gmail.com> <20171115164017.0af64123.freebsd@edvax.de> In-Reply-To: <20171115164017.0af64123.freebsd@edvax.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Nov 2017 23:11:27 -0000 Polytropon wrote: > On Wed, 15 Nov 2017 10:03:03 -0500, Ernie Luzar wrote: >> Polytropon wrote: >>> On Wed, 15 Nov 2017 09:17:44 -0500, Ernie Luzar wrote: >>>> Is there a more modern port that does the same thing as fetchmail? >>> What is "un-modern" about fetchmail? >>> >>> >> >> It's been around for a very long time and I have been using it all most >> all that time. But lately been getting socket errors and other error >> messages. > > One suggestion is to use an IP instead of a hostname for the > server to fetch messages from: > > http://www.fvue.nl/wiki/Fetchmail:_socket_error_while_fetching_from_mail.example.com > > I don't think this is an ideal workaround (as IPs might change). > Also the suggestions here (from the fetchmail web page) could > help: > > http://www.catb.org/esr/fetchmail/fetchmail-FAQ.html#R6 > That faq #6 talks about people who are using the PPP protocol which is not me. The bottom of that faq says to use ip address instead of fqdn. > And another suggestion is to check if your configuration file > has the "ssl" keyword added, for example with a configuration line > in ~/.fetchmailrc (for user-local use) like this: > > poll pop.example.com proto POP3 user pass fetchall flush ssl > > If you don't add "ssl", but the server does not support non-SSL > connections, such socket errors might occur. See "man fetchmail" > for option details. > I have ssl and port 995 options. Changed the remote server fqdn to its ip address and still got the same socket error. This is an informational only message that pops out a few times in 24 hour period. Just one of those background noise issues that I am going to ignore. I shortened the timeout from 30 seconds to 3 seconds. Lets wait and see if that has any effect. Thanks for your input.