🚀 go-pugleaf

>>>>> On 20 Oct 91 03:54:43 GMT, kyle@uunet.UU.NET (Kyle Jones) said:

Kyle> Dan_Jacobson@ATT.COM writes:
 > I noticed if person A sends me an email without a trailing newline,
 > the next sender's mail will get glued to the bottom of A's message,
 > and possibly overlooked by me the next morning when read them with VM
 > 5.31.  I want to make "\nFrom" be the delimiter for me, not just
 > "\n\nFrom"... [By the way, if somebody send me a mail with "\nFrom" in
 > it, it gets put into my $MAIL box as "\n>From" by the system here.]
 > Is there a variable us "\nFrom" folks can set to just affect the $MAIL
 > --> INBOX parsing phase?

Kyle> You might be able to do something in vm-build-message-list, but I
Kyle> offer no guarantees as I haven't thought through the
Kyle> ramifications.  Try removing one of the newlines from
Kyle> separator-string.

\begin{pretty-please}
Perhaps this can maybe be tracked down from all the spots that it is
used and put into a tidy defvar in VM5.32.
\end{pretty-please}

Kyle> Also get your mail delivery agent fixed.  The behavior you
Kyle> describe is a bug.  The job it has to do is simple enough that
Kyle> one could write the thing from scratch in fairly short order, if
Kyle> need be.  Its code is certainly a lot less complicated than that
Kyle> of VM.

I just got off the phone with top mail experts and they say there's no
RFC for mailbox format, and that "\nFrom " is the fundamental trustable
separator most often.  Yes, on particular [OK, vanilla SunOS] systems,
I am able to do
$ echo -n blabla | mail me
$ echo -n blabla | mail me
and still depend on "\n\nFrom " as separator, but it's not universal...

[note that I'm now campaigning for
"\nFrom " etc.
not just
"\nFrom"]