From: Stainless Steel Rat <ratinox@peorth.gweep.net>
Subject: Re: pop3-movemail trouble
Date: 16 Jun 1999 12:06:26 -0400 [thread overview]
Message-ID: <m3909k870d.fsf@peorth.gweep.net> (raw)
In-Reply-To: "Erik Østlyngen"'s message of "16 Jun 1999 09:26:32 +0200"
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
* "Erik Østlyngen" <eriko@ifbt.ntnu.no> on Wed, 16 Jun 1999
| +OK POP3 dj.stud.ntnu.no proxy server v1.0 ready.
| -ERR Command line too long.
| -ERR Null command.
That... is strange. 'Command line too long' is not a valid error in any
event as POP requires that excess gubbage be ignored. I cannot recreate
the error manually, which makes it difficult to track down what is causing
the problem. pGnus sends nothing to the POP server; that traffic is
handled entirely by pop3.el. It sends nothing other than what you are
typing. It is a very simple, very literal, brute-force library.
| It looks like pguns (I'm using version 0.88) sends an invalid command
| to the server after connecting. Is there an easy way to insert trace
| sentences into the pop3 code?
As I just said, I failed miserably at making that work. That is not to say
it is impossible, just that I could not make it work.
| (setq nnmail-spool-file '(
This variable's name has changed to mail-sources. What does 'C-h v' tell
you about mail-sources or nnmail-spool-file?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v0.9.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE3Z8uCgl+vIlSVSNkRAlwoAKDuaPo7CxDwW4WEUVbilF9gqkvKhwCggz6V
0UfI8QPKJomEUbwGrAbuy9w=
=BXy7
-----END PGP SIGNATURE-----
--
Rat <ratinox@peorth.gweep.net> \ Do not use Happy Fun Ball on concrete.
Minion of Nathan - Nathan says Hi! \
PGP Key: at a key server near you! \
next prev parent reply other threads:[~1999-06-16 16:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-06-15 12:56 Erik Østlyngen
1999-06-15 18:23 ` Stainless Steel Rat
1999-06-16 7:26 ` Erik Østlyngen
1999-06-16 16:06 ` Stainless Steel Rat [this message]
1999-06-17 9:10 ` Erik Østlyngen
1999-06-17 20:46 ` Stainless Steel Rat
1999-06-18 13:11 ` Erik Østlyngen
1999-06-18 16:52 ` Stainless Steel Rat
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=m3909k870d.fsf@peorth.gweep.net \
--to=ratinox@peorth.gweep.net \
/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).