From: Norbert Koch <n.koch@delta-ii.de>
Subject: Re: pop server access?
Date: 26 Oct 1998 07:02:55 +0100 [thread overview]
Message-ID: <vod87foo6o.fsf@apollonius.delta-ii.de> (raw)
In-Reply-To: Stainless Steel Rat's message of "25 Oct 1998 19:33:58 -500"
Stainless Steel Rat <ratinox@peorth.gweep.net> writes:
> "viteno" == Norbert Koch <n.koch@delta-ii.de> writes:
> Though you might want to update your qpopper to 2.52 RSN.
>
> You might also wish to try the pop3.el that is with pgnus 0.39. If that
> does not work, then there is a problem much deeper in FSF Emacs.
I've now updated to qpopper-2.52 and pgnus-0.40 and still run into the
same troubles.
The one thing that strikes me is that I'm the only one who has this
problem. Therefore, I guess, the real culprit must lie somewhere else
in the system configuration, although I can't remember of any other
things I could have changed in the meantime.
Oh what the hell, I postpone the issue for a couple of days. Maybe,
(the) something slips back into my mind :-)
Cheers, norbert.
--
Cursed, cursed creator! Why did I live? Why, in that instant, did I
not extinguish the spark of existance that you had so wantonly
bestowed?
next prev parent reply other threads:[~1998-10-26 6:02 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
[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 [this message]
[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=vod87foo6o.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).