Gnus development mailing list
 help / color / mirror / Atom feed
From: "Erik Østlyngen" <eriko@ifbt.ntnu.no>
Subject: Re: pop3-movemail trouble
Date: 18 Jun 1999 15:11:20 +0200	[thread overview]
Message-ID: <uemj9mz5z.fsf@ifbt.ntnu.no> (raw)
In-Reply-To: Stainless Steel Rat's message of "17 Jun 1999 16:46:01 -0400"

Stainless Steel Rat <ratinox@peorth.gweep.net> writes:
> * "Erik Østlyngen" <eriko@ifbt.ntnu.no>  on Thu, 17 Jun 1999
> | 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.
> 
> That is a good idea.  Or find out what POP server is being used (it is not
> particularly obvious from this end), so I can take a look at the code and
> see what it is doing.

I solved the problem.  In pop3.el, I changed the function
pop3-send-command:

(defun pop3-send-command (process command)
    (set-buffer (process-buffer process))
    (goto-char (point-max))
    (setq pop3-read-point (point))
    (goto-char (point-max))
    (process-send-string process command)
    (process-send-string process "\r\n")
    )

to:

(defun pop3-send-command (process command)
    (set-buffer (process-buffer process))
    (goto-char (point-max))
    (setq pop3-read-point (point))
    (goto-char (point-max))
    (process-send-string process (concat command "\r\n"))
    )

I don't know _why_ this works better. If it is any help, the pop
server answers "-ERR Command line too long" on very long commands,
e.g. "USER aaaaaaaaaaaaa...(1700 chars)"

-Erik Østlyngen



  reply	other threads:[~1999-06-18 13:11 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
1999-06-17 20:46         ` Stainless Steel Rat
1999-06-18 13:11           ` Erik Østlyngen [this message]
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=uemj9mz5z.fsf@ifbt.ntnu.no \
    --to=eriko@ifbt.ntnu.no \
    /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).