Hello once more. Steffen Nurpmeso wrote in <20181217173029.gnodt%[email protected]>: |Dr. Werner Fink wrote in <[email protected]>: ||On Thu, Dec 13, 2018 at 06:06:24PM +0100, Steffen Nurpmeso wrote: ||> Werner Fink wrote in <[email protected]>: | ... ||>|Also I'd like to ask how to enable the RFC4155 as default as I can ||>|not break mbox out there. This was the first what I've seen on my ... ||> Well, i hope we do not break MBOXes! ||> The default parser uses the laxe POSIX standard rules for MBOX ||> parsing (Vol. 3, Shell and Utilities, mailx), and these specify ||> (in OUTPUT FILES) "line beginning with From space" ... "one or ||> more header lines" ... "empty line" ... "zero or more body lines, ||> followed by empty line". || ||What I see is || || There are new messages in the error message ring (denoted by ERROR) || The `errors' command manages this message ring || ERROR# ? || ||for several mailboxes which contain mail body including a "From " at ||at the beginning of the line. AFAICS nnon of the do use a mail address ||nor a date after this initial "From " but a normal sentence :) ..
So i rethought a bit and touched that once again. In the future, when we see just any message with a "bad From_ line", we will automatically apply MBOXO quoting for "bad From_ line", whether *mbox-rfc4155* is set or not, when we do write out messages in that box anew. In conjunction with the improved MBOX parser this should fulfill your wishes. For even better message boundary detection when opening a MBOX users still have to set *mbox-rfc4155* --- i have seen too many MBOX files which do not comply to RFC 4155 to enable this strict mode by default! You could set that in the global s-nail / mail / xy.rc, however. An even stricter default could be achieved by adding "ok_bset(mbox_rfc4155);" to the end of a_main_setup_vars(). Ciao, --steffen | |Der Kragenbaer, The moon bear, |der holt sich munter he cheerfully and one by one |einen nach dem anderen runter wa.ks himself off |(By Robert Gernhardt)
