From owner-freebsd-questions@freebsd.org Wed Nov 15 15:40:28 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 D04FADE0408 for ; Wed, 15 Nov 2017 15:40:28 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mailrelay10.qsc.de (mailrelay10.qsc.de [212.99.163.152]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.antispameurope.com", Issuer "TeleSec ServerPass Class 2 CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 5BB3C6F8D1 for ; Wed, 15 Nov 2017 15:40:27 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mx01.qsc.de ([213.148.129.14]) by mailrelay10.qsc.de; Wed, 15 Nov 2017 16:40:19 +0100 Received: from r56.edvax.de (port-92-195-23-159.dynamic.qsc.de [92.195.23.159]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx01.qsc.de (Postfix) with ESMTPS id 750643CBF9; Wed, 15 Nov 2017 16:40:18 +0100 (CET) Received: from r56.edvax.de (localhost [127.0.0.1]) by r56.edvax.de (8.14.5/8.14.5) with SMTP id vAFFeHd4008198; Wed, 15 Nov 2017 16:40:17 +0100 (CET) (envelope-from freebsd@edvax.de) Date: Wed, 15 Nov 2017 16:40:17 +0100 From: Polytropon To: Ernie Luzar Cc: "freebsd-questions@freebsd.org" Subject: Re: fetchmail Message-Id: <20171115164017.0af64123.freebsd@edvax.de> In-Reply-To: <5A0C5727.7080105@gmail.com> References: <5A0C4C88.70105@gmail.com> <20171115152344.d08dfe4f.freebsd@edvax.de> <5A0C5727.7080105@gmail.com> Reply-To: Polytropon Organization: EDVAX X-Mailer: Sylpheed 3.1.1 (GTK+ 2.24.5; i386-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-cloud-security-sender: freebsd@edvax.de X-cloud-security-recipient: freebsd-questions@freebsd.org X-cloud-security-Virusscan: CLEAN X-cloud-security-disclaimer: This E-Mail was scanned by E-Mailservice on mailrelay10.qsc.de with D3D66683A8F X-cloud-security-connect: mx01.qsc.de[213.148.129.14], TLS=1, IP=213.148.129.14 X-cloud-security: scantime:.1874 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: Wed, 15 Nov 2017 15:40:28 -0000 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 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. > To lazy to spend the time right now to trace down the problem with the > remote email provider. It is possible that the problem (maybe just an SSL upgrade) is at the end of the provider, and you need to change your local configuration in order to adapt to that change. > Though it would be quicker to try something different and if got same > problem then will know problem is with other end for sure. Okay, so you're searching for an _alternative_ program for the same purpose, primarily for diagnostics and repair. ;-) In this case, getmail is probably a good thing to try. From its feature summary: - Retrieve mail from an unlimited number of POP3/IMAP4 mailboxes and servers. - Support for POP3-over-SSL and IMAP-over-SSL, as well as SDPS WARNING: even with SSL, "no certificate or key validation is done." so that getmail does not detect or protect from man-in-the-middle attacks. - Support for multidrop or domain mailboxes. - Safe and reliable delivery to qmail-style Maildirs, as well as program (pipe) delivery for use with arbitrary external MDAs. Includes an MDA for mbox files that supports mboxrd format and fcntl-type flock locking. - Does not destroy information by rewriting mail headers. - Does not cause mail loops by doing SMTP injection, and therefore does not require that you run an MTA (like qmail or sendmail) on your host. - Can remember which mail it has already retrieved, and can be set to only download new messages. - Written in Python, and therefore easy to extend or customize. - Simple to install, configure, and use. Source of list here: https://www.freshports.org/mail/getmail/ Documentation: http://pyropus.ca/software/getmail/ If this also shows you comparable errors, re-check the SSL thing. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...