🚀 go-pugleaf

Questions:

    1.  Is this a known RMAIL bug?
    2.  Is there a fix to this bug?

Suggested workaround:

    I think the right thing to do is to move the (looking-at "BABYL OPTIONS")
    expression out of the WHILE loop in RMAIL-CONVERT-TO-BABYL-FORMAT, but I
    don't have sufficient information about the BABYL format, its history, and
    its extent of usage to know that such a change won't break something else.

Information:

    When I read my mail this morning, rmail complainted that it couldn't find
    "^J_" (or something like that), leaving me with a partially BABYL'ized
    RMAIL buffer and ~200 unread messages in my queue.

    A big thank you to whoever staged mail delivery to the .newmail file!
    
    After a couple of passes at RMAIL'ing the .newmail file, I realized that I
    was losing because someone had sent a BABYL file header in the body of
    their message; specifically, the header of the troublesome message was:
    
	From gnulists@ai.mit.edu Wed Aug 14 18:31:49 1991
	Date: Sun, 11 Aug 91 18:10:19 EST
	From: nelson@mohlsun.physics.upenn.edu (Phil Nelson)
	Sender: gnulists@ai.mit.edu
	Posted-Date: Sun, 11 Aug 91 18:10:19 EST
	Message-Id: <9108112310.AA00100@mohlsun.physics.upenn.edu>
	To: bug-gnu-emacs@prep.ai.mit.edu
	Subject: retransmitting incomplete message of 8/8
    
    I am using an rmail.el that: 1) came from emacs-18.57.tar.Z on
    PREP.AI.MIT.EDU and 2) was patched with apollo-emacs.tar.Z on
    LABREA.STANFORD.EDU (Leonard Zubkoff's (LNZ) modifications for the Apollo
    environment).  LNZ's rmail.el patch does not involve the
    RMAIL-CONVERT-TO-BABYL-FORMAT function.