From xemacs-m  Mon May  5 15:34:22 1997
Received: from amber.vis-av.com (amber.vis-av.com [206.119.44.2])
	by xemacs.org (8.8.5/8.8.5) with ESMTP id PAA10623
	for <xemacs-beta@xemacs.org>; Mon, 5 May 1997 15:34:17 -0500 (CDT)
Received: (from derrell@localhost)
          by amber.vis-av.com (8.8.5/8.8.4)
	  id QAA26390; Mon, 5 May 1997 16:34:17 -0400 (EDT)
Date: Mon, 5 May 1997 16:34:17 -0400 (EDT)
Message-Id: <199705052034.QAA26390@amber.vis-av.com>
From: Derrell Lipman <derrell@vis-av.com>
To: xemacs-beta@xemacs.org
Subject: Where did the extra recipient come from in mail to xemacs-beta???
X-Mailer: VM 6.30 under 20.2 XEmacs Lucid (beta4)
Reply-To: derrell@vis-av.com
Mime-Version: 1.0 (generated by tm-edit 7.106)
Content-Type: multipart/mixed;
 boundary="Multipart_Mon_May__5_16:30:25_1997-1"
Content-Transfer-Encoding: 7bit

--Multipart_Mon_May__5_16:30:25_1997-1
Content-Type: text/plain; charset=US-ASCII

I tried to send this to xemacs-beta-owner and to majordomo-owner but
neither of those exist.  Who is the list owner? ...


I just received this message that I had sent this morning, but the
headers have been changed and someone who I've never heard of is
indicated in the recipient list.  Who is Percy Veals, and how did he
invade my message?

Derrell


--Multipart_Mon_May__5_16:30:25_1997-1
Content-Type: message/rfc822

Message-Id: <199705051952.PAA26338@amber.vis-av.com>
X-Attachments: "ORIGINAL.HEADER" (type: text)
MIME-version: 1.0
Content-type: multipart/mixed; boundary="YJtn3n2ZruCs62sakjjDmYqolgzLJWvN"
Subject: 20.2-b4 Build success
From: derrell@vis-av.com
Sender: xemacs-beta-request@xemacs.org
To: "Percy Veals" <veals@nortel.ca>, xemacs-beta@xemacs.org
Date: 05 May 1997 15:16 EDT

>
> This is a MIME Encoded message.  If you are reading this text,
> then your mail reader does not support the MIME (Multipurpose
> Internet Mail Extensions) standard.  To take  full advantage of
> the features of this message, you need to upgrade  your mailer to
> a MIME V1.0 compliant package.  Some parts of this  message may
> be in human readable form.
>
> MIME Decoding Utilities
> -----------------------
> To make use of this encoded message, you can decode it using
> a MIME Decoding utility.  The following are some freely available
> MIME decoding utilities:
>
>   UNIX Users
>   -----------
>    Metamail : ftp://ftp.bellcore.com/pub/nsb/mm2.7.tar.Z
>               This is the Metamail source code distribution.
>    Mpack    : ftp://ftp.andrew.cmu.edu/pub/mpack/mpack-1.5-src.tar.Z
>               Source code for all platforms.
>   MACINTOSH Users
>   ---------------
>    Mpack    : ftp://ftp.andrew.cmu.edu/pub/mpack/mpack-1.5-mac.hqx
>               Contains the Macintosh binaries
>   PC Users
>   ---------
>    Metamail : ftp://ftp.bellcore.com/pub/nsb/mm2.7.dos.zip
>               This is the MS-DOS binaries
>
>    Mpack    : ftp://ftp.andrew.cmu.edu/pub/mpack/mpack15d.zip
>               This contains the MS-DOS binaries
> MIME-Aware Mail User Agents
> ---------------------------
> Note that the following Mail User Agents support MIME and hence if
> one of these are used the message will be automatically decoded 
> be in a readable state:
>       Elm Version 2.4 (UNIX)
>           ftp://ftp.uu.net/networking/mail/elm
>       Eudora 1.4.4   (Macintosh, MS-Windows)
>           ftp://ftp.qualcomm.com/quest/eudora/windows/1.4/eudor144.exe
>           ftp://ftp.qualcomm.com/quest/eudora/mac/1.4/eudora144.hqx
>       Pegasus mail    (MS-DOS, MS-Windows, Macintosh)
>           ftp://risc.ua.edu/pub/network/pegasus/*
>       Pine  (UNIX)
>           ftp://ftp.cac.washington.edu/pine/pine.tar.Z
>


--YJtn3n2ZruCs62sakjjDmYqolgzLJWvN
Content-type: text/plain; charset="us-ascii"


Configured for `i386-unknown-freebsd2.1.5'.

  Where should the build process find the source code?    /usr/src/local/xemacs-20.2-b4
  What installation prefix should install use?		  /usr/local
  What operating system and machine description files should XEmacs use?
        `s/freebsd.h' and `m/intel386.h'
  What compiler should XEmacs be built with?              gcc  -g -O 
  Should XEmacs use the GNU version of malloc?            yes
  Should XEmacs use the relocating allocator for buffers? yes
  What window system should XEmacs use?                   x11
  Where do we find X Windows header files?                /usr/X11R6/include
  Where do we find X Windows libraries?                   /usr/X11R6/lib
  Compiling in support for XAUTH.
  Compiling in support for XPM.
  Compiling in support for X-Face headers.
  Compiling in support for GIF image conversion.
  Compiling in support for JPEG image conversion.
  Compiling in support for PNG image conversion.
  Compiling in support for Berkeley DB.
  Compiling in support for DBM.
  Compiling in support for ncurses.
  Using the Lucid menubar.
  Using the Lucid scrollbar.
  Using the Athena dialog boxes.

                              
--YJtn3n2ZruCs62sakjjDmYqolgzLJWvN
Content-type: text/plain; charset="us-ascii"


Received: from bcarsbf5.localhost (actually bcarsbf5.ott.bnr.ca) by bcarsfbb.ott.bnr.ca; Mon, 5 May 1997 09:26:04 -0400
Received: from xemacs.org (actually xemacs.cs.uiuc.edu) by bcarsbf5.localhost;
          Mon, 5 May 1997 09:25:33 -0400
Received: (from xemacs-m@localhost) by xemacs.org (8.8.5/8.8.5) id IAA26191;
          Mon, 5 May 1997 08:25:00 -0500 (CDT)
Resent-Date: Mon, 5 May 1997 08:25:00 -0500 (CDT)
Date: Mon, 5 May 1997 09:24:28 -0400 (EDT)
Message-Id: <199705051324.JAA25532@amber.vis-av.com>
From: Derrell Lipman <derrell@vis-av.com>
To: XEmacs Beta List <xemacs-beta@xemacs.org>
Subject: 20.2-b4 Build success
X-Mailer: VM 6.30 under 20.2 XEmacs Lucid (beta4)
Reply-To: derrell@vis-av.com
Mime-Version: 1.0 (generated by tm-edit 7.106)
Content-Type: text/plain; charset=US-ASCII
Resent-Message-ID: <"H-m1j.0.CP6.h-TRp"@xemacs>
Resent-From: xemacs-beta@xemacs.org
X-Mailing-List: <xemacs-beta@xemacs.org> archive/latest/7983
X-Loop: xemacs-beta@xemacs.org
Precedence: list
Resent-Sender: xemacs-beta-request@xemacs.org

--YJtn3n2ZruCs62sakjjDmYqolgzLJWvN--

--Multipart_Mon_May__5_16:30:25_1997-1--

