🚀 go-pugleaf

	  EXACTLY what  you describe seems  to be occuring!  But  my messages
have been like  that for YEARS.  Is  it possible that I did  something when I
first got on this (Sun/Gnu/Bash) system  (years ago) to make this happen?  If
so, what? Where do I start looking?

          If it is not something I have done, is it possible that because the
"standard" mail prorgam is now something  much simpler and the old program is
now called "mailx" and is referred to  as the "BSD mailer".. that all this is
happening.

	I have appended a typical header to the end of this message.

	(Actually most folks here use Pine  or Elm, but I wanted to learn the
	most  standrad Unix  program first,  then I  got stuck  with  all the
	.mailrc  stuff  that saves  stuff  in  folders  automatically and  my
	addressbook)

From ph10@cus.cam.ac.uk, on 17 May 2000 08:37:14 GMT we perused:

*+-In article <slrn8i394q.i5p.vjp2@amanda.dorsai.org>, vjp2@dorsai.org (Vasos
     Panagiotopoulos +1-917-287-8087 Bioengineer-Financier) writes:
*+-|> For half a decade my ISP has been using the 1988 Sun MAIL program.
*+-|> Now They upgraded to a 1995 release which means I am using Mailx.
*+-|> But the following problem also appears in several other mail programs.
*+-|> 
*+-|> I can't view any subject headers because something sticks a blank line into
*+-|> my messages after the first header (this is a peculiar header in that it has
*+-|> no colons [:] and includes both From and Date)
*+-
*+-Then it is not a header line in the sense of RFC 822. Some software that
*+-is handling your mail is broken if it is putting in lines starting with
*+-"From ". These lines usually look like this:
*+-
*+-From xxxx@yyyy Tue May 16 09:40:51 2000
*+-
*+-They are used
*+-
*+-(a) In messages being transported by UUCP (see RFC 976).
*+-(b) To separate messages that are stored in Berkeley format mailboxes.
*+-
*+-They should *not* appear in messages that are being transmitted using 
*+-SMTP over the Internet. Many MTAs, on receiving a broken message that
*+-starts with such a line, assume that it is the first data line of the 
*+-message, and insert a blank line (and a few default header lines) to 
*+-make the message conform to RFC 822.
*+-

Here is my typical mail header:

                   (what has changed with the new install is that the
                    fourth [blank] line gets inserted - it seems to do this
                    to messages that have been in the mailbox [actually,
                    a folder] before the new software was installed as well)

From eeurope-changes-request@medusa.blackops.org  Mon May 15 09:17:24 2000
Status: RO
Content-Length: 111209

>From 65535  Mon May 15 09:17:24 2000
Return-Path: eeurope-changes-request@medusa.blackops.org
Received: from medusa.blackops.org (root@medusa.blackops.org
        [205.158.26.242]) by tam.dorsai.org (8.8.4/8.6.12) with ESMTP id 
        JAA20192 for <vjp2@dorsai.org>; 
        Mon, 15 May 2000 09:17:20 -0500 (EST) %*%
Received: (from daemon@localhost)
	by medusa.blackops.org (8.11.0.Beta1/8.9.1) id e4FCYMK30775
	for list12200-376328-d; Mon, 15 May 2000 05:34:22 -0700 (PDT)
Date: Mon, 15 May 2000 05:34:22 -0700 (PDT)
From: eeurope-changes-request@humintel.com
Message-Id: <200005151234.e4FCYMK30775@medusa.blackops.org>
To: Multiple recipients of the eeurope-changes-digest list 
    <eeurope-changes-digest@humintel.com> %*%
Precedence: list
Errors-To: eeurope-changes-errors@humintel.com
Reply-To: eeurope-changes-request@humintel.com
X-List-Software: listmanager v2.104, Copyright (c) 1994-2000, M. S. Kucherawy
X-Loop-Detect: humintel.com:eeurope-changes
Subject: [EECD:1840] eeurope-changes digest (00/05/15 4150)

(lines ending in %*% were reformatted so the newsreader would let me post..
they originally wrapped around)