From: Norbert Koch <n.koch@delta-ii.de>
Subject: Re: pop server access?
Date: 22 Oct 1998 07:21:19 +0200 [thread overview]
Message-ID: <voems16uk0.fsf@apollonius.delta-ii.de> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of "20 Oct 1998 19:57:35 +0200"
Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> Norbert Koch <n.koch@delta-ii.de> writes:
>
> > have you made any changes regarding the pop server access? I can't get
> > onto the server after the installation of 0.35.
>
> This patch was applied to make things work under Emacs 20.3:
>
[...]
Hmm, the problem still exists after an update to 0.36. C-g comes up
with
Signaling: (quit)
accept-process-output(#<network connection "POP" (110 . "mail.delta-ii.de") state:run> 3)
pop3-read-response(#<network connection "POP" (110 . "mail.delta-ii.de") state:run> t)
pop3-open-server("mail.delta-ii.de" 110)
pop3-movemail("/zeus_home/norbert/mail/.gnus-crash-box")
nnmail-pop3-movemail("po:nok_mail" "/zeus_home/norbert/mail/.gnus-crash-box")
byte-code("..." [nnmail-movemail-program inbox tofile 0 result] 3)
nnmail-move-inbox("po:nok_mail")
nnmail-get-new-mail(nnml nnml-save-nov "/home/norbert/mail/" nil)
nnml-request-scan(nil "nk")
gnus-request-scan(nil (nnml "nk"))
gnus-read-active-file(nil nil)
gnus-setup-news(nil nil nil)
byte-code("..." [dont-connect did-connect gnus-group-quit gnus-run-hooks gnus-startup-hook gnus-make-newsrc-file gnus-startup-file gnus-current-startup-file gnus-slave gnus-use-dribble-file gnus-dribble-read-file gnus-use-grouplens bbb-login add-hook gnus-summary-mode-hook gnus-grouplens-mode gnus-setup-news nil level gnus-setup-news-hook gnus-start-draft-setup gnus-group-list-groups gnus-group-first-unread-group gnus-configure-windows group gnus-group-set-mode-line gnus-started-hook] 4)
gnus-1(nil nil nil)
gnus(nil)
call-interactively(gnus)
At this point the system seems to hang (well, I don't know for how
long, I'm sort of impatient :-).
Any leads? Tia, norbert.
--
Dr Norbert Koch, DELTA Industrie Informatik GmbH, Fellbach, Germany
A rattlesnake that doesn't bite teaches you nothing!
next prev parent reply other threads:[~1998-10-22 5:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-10-20 10:53 Norbert Koch
1998-10-20 17:57 ` Lars Magne Ingebrigtsen
1998-10-22 5:21 ` Norbert Koch [this message]
[not found] ` <x7yaq8gpp8.fsf@peorth.gweep.net>
1998-10-23 4:39 ` Norbert Koch
[not found] ` <x7emry3jcc.fsf@peorth.gweep.net>
1998-10-25 11:54 ` Norbert Koch
[not found] ` <x7zpak5fgp.fsf@peorth.gweep.net>
1998-10-26 6:02 ` Norbert Koch
[not found] ` <x7btmyyk3x.fsf@peorth.gweep.net>
1998-10-27 13:18 ` Norbert Koch
1998-11-04 7:47 ` Shenghuo ZHU
[not found] ` <x7u30fpi7v.fsf@peorth.gweep.net>
1998-11-04 18:00 ` Jan Vroonhof
[not found] ` <x790ia3thq.fsf@peorth.gweep.net>
1998-10-22 7:14 ` Urban Engberg
1998-10-22 7:22 ` Urban Engberg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=voems16uk0.fsf@apollonius.delta-ii.de \
--to=n.koch@delta-ii.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).