Your message dated Fri, 15 Feb 2019 23:23:39 +0100
with message-id <[email protected]>
and subject line Re: Bug#922164: fetchmail: With buster :fetchmail: Erreur de
login ou d'identification inconnue pour [email protected]
has caused the Debian Bug report #922164,
regarding fetchmail: With buster :fetchmail: Erreur de login ou
d'identification inconnue pour [email protected]
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
922164: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922164
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: fetchmail
Version: 6.3.26-3
Severity: normal
Dear Maintainer,
I use buster (testing) and after last upgrade I get :
fetchmail: pop.free.fr: passage au TLS raté.
fetchmail: Erreur de login ou d'identification inconnue pour [email protected]
fetchmail: erreur socket durant la réception de [email protected]
fetchmail: État de la requête=2 (SOCKET)
fetchmail: pop.free.fr: passage au TLS raté.
fetchmail: Erreur de login ou d'identification inconnue pour [email protected]
fetchmail: erreur socket durant la réception de [email protected]
fetchmail: État de la requête=2 (SOCKET)
fetchmail: pop.free.fr: passage au TLS raté.
fetchmail: Erreur de login ou d'identification inconnue pour [email protected]
fetchmail: erreur socket durant la réception de [email protected]
fetchmail: État de la requête=2 (SOCKET)
This is with fetchmail 6.4.0
I just installed fetchmail 6.3.26-3 (stretch) and now it works fine.
Gerard
-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.19.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8),
LANGUAGE=fr_FR.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages fetchmail depends on:
ii adduser 3.118
ii debianutils 4.8.6.1
ii libc6 2.28-6
ii libcomerr2 1.44.5-1
ii libgssapi-krb5-2 1.17-1
ii libk5crypto3 1.17-1
ii libkrb5-3 1.17-1
ii libssl1.1 1.1.1a-1
ii lsb-base 10.2018112800
Versions of packages fetchmail recommends:
ii ca-certificates 20190110
Versions of packages fetchmail suggests:
pn fetchmailconf <none>
ii postfix [mail-transport-agent] 3.3.2-1+b1
pn resolvconf <none>
-- no debconf information
--- End Message ---
--- Begin Message ---
Control: tags -1 wontfix -moreinfo
Guys,
this isn't a bug, and you're not using fetchmail properly.
Here's the thing:
pop.free.fr does not support STLS (STARTTLS),
fetchmail 6.4.0 fails, fetchmail 6.3.26 continues without TLS instead, so
using an unencrypted channel, but pop.free.fr does support SSL-wrapper mode.
Hence, the solution is to tell fetchmail (whichever version) to talk
directly to the SSL-wrapped port 995, for instance, by adding "ssl" to the
rcfile,
or --ssl --sslcertck to the command line.
Happy fetching,
Matthias
--- End Message ---
