From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/65316 Path: news.gmane.org!not-for-mail From: Stainless Steel Rat Newsgroups: gmane.emacs.devel,gmane.emacs.gnus.general Subject: Re: Is this patch of gnus/pop3.el reasonable? Date: Sun, 30 Sep 2007 20:06:00 -0400 Message-ID: <518B3F73-E280-4A15-AC96-909316E59A5D@peorth.gweep.net> References: <85ir5r2302.fsf@lola.goethe.zz> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 (Apple Message framework v752.3) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Content-Transfer-Encoding: 7bit X-Trace: sea.gmane.org 1191222654 23940 80.91.229.12 (1 Oct 2007 07:10:54 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Mon, 1 Oct 2007 07:10:54 +0000 (UTC) Cc: ding@gnus.org, emacs-devel@gnu.org To: David Kastrup Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Oct 01 09:10:49 2007 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1IcFQX-00068N-Ji for ged-emacs-devel@m.gmane.org; Mon, 01 Oct 2007 09:10:49 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1IcFQT-0002p7-Gu for ged-emacs-devel@m.gmane.org; Mon, 01 Oct 2007 03:10:45 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Ic8nw-0000li-0Z for emacs-devel@gnu.org; Sun, 30 Sep 2007 20:06:32 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Ic8nu-0000jE-HX for emacs-devel@gnu.org; Sun, 30 Sep 2007 20:06:31 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Ic8nu-0000jB-FK for emacs-devel@gnu.org; Sun, 30 Sep 2007 20:06:30 -0400 Original-Received: from vms042pub.verizon.net ([206.46.252.42]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Ic8np-0007R5-Db; Sun, 30 Sep 2007 20:06:25 -0400 Original-Received: from [192.168.1.205] ([71.124.222.175]) by vms042.mailsrvcs.net (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPA id <0JP7006ZXHM1CS69@vms042.mailsrvcs.net>; Sun, 30 Sep 2007 19:06:02 -0500 (CDT) In-reply-to: <85ir5r2302.fsf@lola.goethe.zz> X-Mailer: Apple Mail (2.752.3) X-Detected-Kernel: Solaris 9.1 X-Mailman-Approved-At: Mon, 01 Oct 2007 03:10:42 -0400 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:80084 gmane.emacs.gnus.general:65316 Archived-At: 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/