From: "Erik Østlyngen" <eriko@ifbt.ntnu.no>
Cc: "(ding)" <ding@gnus.org>
Subject: Re: pop3-movemail trouble
Date: 17 Jun 1999 11:10:50 +0200 [thread overview]
Message-ID: <uvhcnw5t1.fsf@ifbt.ntnu.no> (raw)
In-Reply-To: Stainless Steel Rat's message of "16 Jun 1999 12:06:26 -0400"
Stainless Steel Rat <ratinox@peorth.gweep.net> writes:
> * "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.
I'm sorry. I thought pop3.el was part of pGnus.
> | (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?
mail-sources is nil
nnmail-spool-file is:
((pop :user "erikoest"
:server "pop.stud.ntnu.no"
:password "SecretWord" ))
I tried to change my .emacs to use mail-sources instead of
nnmail-spool-file.
nnmail-spool-file is now ((file))
mail-sources is:
((pop :user "erikoest"
:server "pop.stud.ntnu.no"
:password "SecretWord" ))
But the response is the same. I still get the "Command line too long"
error. I think I will see if the system administrator here knows what
this error message means.
-Erik Østlyngen
next prev parent reply other threads:[~1999-06-17 9:10 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
1999-06-17 9:10 ` Erik Østlyngen [this message]
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=uvhcnw5t1.fsf@ifbt.ntnu.no \
--to=eriko@ifbt.ntnu.no \
--cc=ding@gnus.org \
/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).