[Eisfair] Neues Problem bei fetchmail?

[Dirk Alberti]

Hallo zusammen,

neuerdings (bemerkt erst heute) holt mein fetchmail keine bzw. fast 
keine Emails mehr ab. Sporadisch kamen die letzten Tage wohl noch welche 
durch.

fetchmail.log zeigt mir dieses:

fetchmail: Try adding the --service option (see also FAQ item R12).
fetchmail: POP3 connection to securepop.t-online.de failed: No such file 
or directory
fetchmail: Query status=2 (SOCKET)
fetchmail: getaddrinfo("pop.gmx.net","pop3s") error: Servname not 
supported for ai_socktype
fetchmail: Try adding the --service option (see also FAQ item R12).
fetchmail: POP3 connection to pop.gmx.net failed: No such file or directory
fetchmail: Query status=2 (SOCKET)
fetchmail: getaddrinfo("securepop.t-online.de","pop3s") error: Servname 
not supported for ai_socktype
fetchmail: Try adding the --service option (see also FAQ item R12).
fetchmail: POP3 connection to securepop.t-online.de failed: No such file 
or directory
fetchmail: Query status=2 (SOCKET)
fetchmail: sleeping at Sat, 22 Apr 2023 12:11:04 (CEST) for 750 seconds
fetchmail: awakened at Sat, 22 Apr 2023 12:23:34 (CEST)
fetchmail: getaddrinfo("pop.gmx.net","pop3s") error: Servname not 
supported for ai_socktype
fetchmail: Try adding the --service option (see also FAQ item R12).
fetchmail: POP3 connection to pop.gmx.net failed: No such file or directory
fetchmail: Query status=2 (SOCKET)
fetchmail: getaddrinfo("mx.freenet.de","pop3s") error: Servname not 
supported for ai_socktype
fetchmail: Try adding the --service option (see also FAQ item R12).
fetchmail: POP3 connection to mx.freenet.de failed: No such file or 
directory
fetchmail: Query status=2 (SOCKET)
fetchmail: getaddrinfo("pop3.web.de","pop3s") error: Servname not 
supported for ai_socktyp

usw.


Nach einem Aufruf des Setups und abspeichern desselben erhalte ich im 
Fetchmail.log anstatt o.g. Zeilen nun sowas hier, für alle zum Abruf 
eingestellten Konten:


fetchmail: starting fetchmail-loader script
fetchmail: awakened at Sat, 22 Apr 2023 17:59:14 (CEST)
fetchmail: 16 messages for *****@gmx.de at pop.gmx.net (875474 octets).
fetchmail: reading message *****@gmx.de at pop.gmx.net:1 of 16 (13684 
octets) (log message incomplete)
fetchmail: SMTP error: 451 Temporary local problem - please try later
fetchmail:  not flushed
fetchmail: reading message *****@gmx.de at pop.gmx.net:2 of 16 (130699 
octets) (log message incomplete)
fetchmail: SMTP error: 451 Temporary local problem - please try later
fetchmail:  not flushed
fetchmail: reading message *****@gmx.de at pop.gmx.net:3 of 16 (68015 
octets) (log message incomplete)
fetchmail: SMTP error: 451 Temporary local problem - please try later
fetchmail:  not flushed
fetchmail: reading message *****@gmx.de at pop.gmx.net:4 of 16 (75320 
octets) (log message incomplete)
fetchmail: SMTP error: 451 Temporary local problem - please try later
fetchmail:  not flushed
fetchmail: reading message *****@gmx.de at pop.gmx.net:5 of 16 (13995 
octets) (log message incomplete)
fetchmail: SMTP error: 451 Temporary local problem - please try later
fetchmail:  not flushed
fetchmail: reading message *****@gmx.de at pop.gmx.net:6 of 16 (16459 
octets) (log message incomplete)
fetchmail: SMTP error: 451 Temporary local problem - please try later
fetchmail:  not flushed

usw.


Ich habe keine Ahnung, ob das etwas mit den haufenweisen Updates zu tun 
hat, die derzeit hier laufen. Mein E1 ist nach Stand von vor 5min 
jedenfalls auf dem aktuellen Stand.


Grüße, Dirk