Gnus development mailing list
 help / color / mirror / Atom feed
From: Stainless Steel Rat <ratinox@peorth.gweep.net>
To: David Kastrup <dak@gnu.org>
Cc: ding@gnus.org, emacs-devel@gnu.org
Subject: Re: Is this patch of gnus/pop3.el reasonable?
Date: Sun, 30 Sep 2007 20:06:00 -0400	[thread overview]
Message-ID: <518B3F73-E280-4A15-AC96-909316E59A5D@peorth.gweep.net> (raw)
In-Reply-To: <85ir5r2302.fsf@lola.goethe.zz>

On Sep 30, 2007, at 6:38 PM, David Kastrup wrote:
> Now the question is whether this is a bad idea to check into upstream.
> I can't see that it will affect operation where the server is correct,
> and it might avoid hangs where it isn't.
>
> What do you think?

I think it breaks spec.  POP3 responses are terminated with CRLF (\r 
\n).  That's not an option.  My dim recollection of the POP3 specs  
are that lone CRs or LFs are not prohibited in responses so searching  
for something other than the in-spec terminator could be bad.

Does such a buggy, standards-breaking POP3 server exist?  If so then  
I think that the correct way to address it is to make the terminator  
a variable that can be changed on a per-user basis rather than making  
a global static change that could adversely affect everyone else in  
the world using in-spec POP servers.  Otherwise leave it alone.  It  
does what the POP3 RFCs say it should.
-- 
\m/  (--)  \m/

  parent reply	other threads:[~2007-10-01  0:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-30 22:38 David Kastrup
2007-09-30 23:01 ` Leo
2007-10-01  0:06 ` Stainless Steel Rat [this message]
2007-10-01  6:32 ` Zhang Wei
2007-10-01 18:16   ` Stainless Steel Rat
2007-10-01 17:40 ` Richard Stallman

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=518B3F73-E280-4A15-AC96-909316E59A5D@peorth.gweep.net \
    --to=ratinox@peorth.gweep.net \
    --cc=dak@gnu.org \
    --cc=ding@gnus.org \
    --cc=emacs-devel@gnu.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).