Hi, I have the same problem, I run testing + some bits from unstable on this machine.
$ env LC_ALL=C fetchmail -v -v -v --nodetach --nosyslog -b 2 Old UID list from mail.riseup.net: <empty> Scratch list of UIDs: <empty> fetchmail: removing stale lockfile fetchmail: 6.4.0.beta4 querying mail.riseup.net (protocol POP3) at Wed Feb 6 11:42:01 2019: poll started Trying to connect to 198.252.153.22/110...connected. fetchmail: POP3< +OK howdy, ready. fetchmail: POP3> CAPA fetchmail: POP3< +OK fetchmail: POP3< CAPA fetchmail: POP3< TOP fetchmail: POP3< UIDL fetchmail: POP3< RESP-CODES fetchmail: POP3< PIPELINING fetchmail: POP3< AUTH-RESP-CODE fetchmail: POP3< STLS fetchmail: POP3< SASL fetchmail: POP3< . fetchmail: POP3> STLS fetchmail: POP3< +OK Begin TLS negotiation now. fetchmail: Certificate chain, from root to peer, starting at depth 2: fetchmail: Issuer Organization: COMODO CA Limited fetchmail: Issuer CommonName: COMODO RSA Certification Authority fetchmail: Subject CommonName: COMODO RSA Certification Authority fetchmail: Certificate at depth 1: fetchmail: Issuer Organization: COMODO CA Limited fetchmail: Issuer CommonName: COMODO RSA Certification Authority fetchmail: Subject CommonName: COMODO RSA Domain Validation Secure Server CA fetchmail: Server certificate: fetchmail: Issuer Organization: COMODO CA Limited fetchmail: Issuer CommonName: COMODO RSA Domain Validation Secure Server CA fetchmail: Subject CommonName: *.riseup.net fetchmail: Subject Alternative Name: *.riseup.net fetchmail: Subject Alternative Name: riseup.net fetchmail: mail.riseup.net key fingerprint: A6:13:14:09:4D:61:97:D9:D0:A1:E1:C7:2D:F4:4E:6E fetchmail: SSL/TLS: using protocol TLSv1.2, cipher ECDHE-RSA-AES128-GCM-SHA256, 128/128 secret/processed bits fetchmail: POP3> CAPA fetchmail: POP3< +OK fetchmail: POP3< CAPA fetchmail: POP3< TOP fetchmail: POP3< UIDL fetchmail: POP3< RESP-CODES fetchmail: POP3< PIPELINING fetchmail: POP3< AUTH-RESP-CODE fetchmail: POP3< USER fetchmail: POP3< SASL PLAIN LOGIN fetchmail: POP3< . fetchmail: mail.riseup.net: upgrade to TLS succeeded. fetchmail: POP3> USER dogsleg fetchmail: POP3< +OK fetchmail: POP3> PASS * fetchmail: POP3< +OK Logged in. fetchmail: selecting or re-polling default folder fetchmail: POP3> STAT fetchmail: POP3< +OK 29 272396 29 messages for dogsleg at mail.riseup.net (272396 octets). fetchmail: POP3> LIST 1 fetchmail: POP3< +OK 1 6319 fetchmail: POP3> RETR 1 fetchmail: POP3< +OK 6319 octets reading message dogs...@mail.riseup.net:1 of 29 (6319 octets) About to rewrite Return-Path: <bounce-debian-devel=dogsleg=debian....@lists.debian.org>... ...rewritten version is Return-Path: <bounce-debian-devel=dogsleg=debian....@lists.debian.org>. About to rewrite From: Paul Wise <p...@debian.org>... ...rewritten version is From: Paul Wise <p...@debian.org>. About to rewrite To: debian-de...@lists.debian.org... ...rewritten version is To: debian-de...@lists.debian.org. About to rewrite Resent-From: debian-de...@lists.debian.org... ...rewritten version is Resent-From: debian-de...@lists.debian.org. About to rewrite Resent-Sender: debian-devel-requ...@lists.debian.org... ...rewritten version is Resent-Sender: debian-devel-requ...@lists.debian.org. Trying to connect to ::1/25...connection failed. fetchmail: connection to localhost:smtp [::1/25] failed: Connection refused. Trying to connect to 127.0.0.1/25...connected. fetchmail: SMTP< 220 urfu-thinkpad ESMTP Exim 4.92-RC5 Wed, 06 Feb 2019 11:42:05 +0500 fetchmail: SMTP> EHLO mail.riseup.net fetchmail: SMTP< 250-urfu-thinkpad Hello mail.riseup.net [127.0.0.1] fetchmail: SMTP< 250-SIZE 52428800 fetchmail: SMTP< 250-8BITMIME fetchmail: SMTP< 250-PIPELINING fetchmail: SMTP< 250-CHUNKING fetchmail: SMTP< 250-PRDR fetchmail: SMTP< 250 HELP fetchmail: forwarding to localhost fetchmail: SMTP> MAIL FROM:<bounce-debian-devel=dogsleg=debian....@lists.debian.org> BODY=8BITMIME SIZE=6319 fetchmail: SMTP< 250 OK fetchmail: SMTP> RCPT TO:<dogsleg@localhost> fetchmail: SMTP< 250 Accepted fetchmail: SMTP> DATA fetchmail: SMTP< 354 Enter message, ending with "." on a line by itself #************************** fetchmail: SMTP>. (EOM) fetchmail: SMTP< 250 OK id=1grGuL-0002s8-Oa flushed fetchmail: POP3> DELE 1 fetchmail: POP3< +OK Marked to be deleted. Segmentation fault I've tried to downgrade to fetchmail 6.4.0~beta4-1 (from snapshot.debian.org), tried to upgrade to glibc 2.28-6, tried to reboot with another version of Linux kernel, and the problem is still there. Since the problem is a recent one, I've tried to investigate, which packages were upgraded on my machine recently: $ which-pkg-broke fetchmail perl-base Tue Feb 5 11:20:26 2019 libdb5.3:amd64 Wed Feb 6 11:02:03 2019 libc6:amd64 Wed Feb 6 11:20:43 2019 fetchmail Wed Feb 6 11:41:49 2019 Changes in libc6 reflect my attempts to upgrade to glibc 2.28-6 and changes in fetchmail reflect my attempts to downgrade (which I mentioned before). With regards, Lev Lamberov
