Am 22.03.21 um 14:57 schrieb Stefan Wiens:
Ich habe nochmal von vorne angefangen. (require 'cl) ist in die
~/.gnus.el eingetragen.
Nun ist es so, zwischen
news.individual.de und Gnus werkelt leafnode.
root@wolfgang-bauer:/etc/news/leafnode# leafnode
200 Leafnode NNTP Daemon, version 1.11.11 running at
wolfgang-bauer.at
(my fqdn:
wolfgang-bauer.at)
oot@wolfgang-bauer:/etc/news/leafnode# fetchnews -v
leafnode 1.11.11: verbosity level is 1, debugmode is 0
try_lock(timeout=5), fqdn="
wolfgang-bauer.at"
Groupinfo file /var/spool/news/leaf.node/groupinfo not present or too
small, forcing active fetch.
news: connecting to port nntp...
warning: news: connection to 185.51.8.103 failed: Connection refused
| wo kommt diese IP Adresse her ^^^^^^^^^^^
news: address list exhausted without establishing connection.
news: connection failed.
WARNING: some servers have not been queried!
wrote active file with 0 lines
Started process to update overview data in the background.
Network activity has finished.
Das ist wohl auch der Grund warum Gnus beim Bestellen einer Gruppe sagt,
Debugger entered--Lisp error: (error "Couldn’t activate group de.test:
411 No such group ")
signal(error ("Couldn’t activate group de.test: 411 No such group "))
error("Couldn't activate group %s: %s" "de.test" "411 No such group ")
gnus-select-newsgroup("de.test" nil nil)
gnus-summary-read-group-1("de.test" nil nil nil nil nil)
gnus-summary-read-group("de.test" nil nil nil nil nil nil)
gnus-group-read-group(nil nil nil)
gnus-topic-read-group(nil)
funcall-interactively(gnus-topic-read-group nil)
call-interactively(gnus-topic-read-group nil nil)
command-execute(gnus-topic-read-group)
Freundliche Grüße
Wolfgang