From xemacs-m  Fri Sep 26 13:11:40 1997
Received: from firewall1.Lehman.COM (firewall.Lehman.COM [192.147.65.66])
	by xemacs.org (8.8.5/8.8.5) with ESMTP id NAA26361
	for <xemacs-beta@xemacs.org>; Fri, 26 Sep 1997 13:11:39 -0500 (CDT)
Received: from relay.messaging-svcs2.lehman.com by firewall1.Lehman.COM (8.8.6/8.6.12) id OAA21900; Fri, 26 Sep 1997 14:11:40 -0400 (EDT)
Received: from cfdevx1.lehman.com by relay.messaging-svcs2.lehman.com (8.8.5/8.8.5) id OAA27069; Fri, 26 Sep 1997 14:11:02 -0400 (EDT)
Received: from localhost by cfdevx1.lehman.com (4.1/Lehman Bros. V1.6)
	id AA26537; Fri, 26 Sep 97 14:10:43 EDT
Message-Id: <9709261810.AA26537@cfdevx1.lehman.com>
Reply-To: Rick Campbell <rickc@lehman.com>
X-Face: #<@""pDMxa>Mr$Wp[^l7e1RwB6]&7pRp,f=|)6y5?t45X$y(xx.x^?k~;-d>s:SL86Qt82U
 'M!RC3LrDvD/LjiYdGO!:\/\qx?YabgGC9%xw5%0-W05LRvyu9vB9TYk%5PN|C*0WgrXD-L0'g3j;h
X-Windows: The joke that kills.
Organization: Lehman Brothers Inc.
From: Rick Campbell <rickc@lehman.com>
To: Hrvoje Niksic <hniksic@srce.hr>
Cc: XEmacs Developers <xemacs-beta@xemacs.org>
Subject: Re: Bronx on SunOS: success, but broken MIME and adjusted puresize 
In-Reply-To: Your message of "26 Sep 1997 19:35:34 +0200."
             <kig67rom109.fsf@jagor.srce.hr> 
Mime-Version: 1.0 (generated by tm-edit 7.106)
Content-Type: multipart/signed; protocol="application/pgp-signature";
 boundary="pgp-sign-Multipart_Fri_Sep_26_14:10:24_1997-1"; micalg=pgp-md5
Content-Transfer-Encoding: 7bit
Date: Fri, 26 Sep 1997 14:10:30 -0400
Sender: rickc@lehman.com

--pgp-sign-Multipart_Fri_Sep_26_14:10:24_1997-1
Content-Type: text/plain; charset=US-ASCII

That maybe, however, it truly is a receiver issue -- there is no waay
to even ensure that your intended recipient will receive your reply
unless you include their address.  If you assume that they will
receive the message through the list, you will usually be correct, but
noy always.  If you intend a Reply All, you should reply to all.

There are tools around, notably procmail, that will filter out
duplicate message ids and this is where the reponsibility properly
lies for people annoyed by multiple copies.  The procmail recipe is
simply:

  :0 Wh: msgid.lock
  | $FORMAIL -D 8192 msgid.cache

The Mail-Copies-To hack is not part of any standards that I'm aware
of.

			Rick

--pgp-sign-Multipart_Fri_Sep_26_14:10:24_1997-1
Content-Type: application/pgp-signature
Content-Transfer-Encoding: 7bit

-----BEGIN PGP MESSAGE-----
Version: 2.6.2
Comment: Processed by Mailcrypt 3.4, an Emacs/PGP interface

iQCVAwUBNCv6kVtTztlqB385AQG09QP+MMa//Q0tIqU+4RtmnHyp5lhqm/PZm+E5
NNMn2BcGXXQPHqZvniDdo0CdCu4RNTKs8qOkW7LRyFrDUdFOzkEM4fsjUl4bo9Kp
U44mzxT6XsvBI1DQXsgkMVOGWJ8JwVFmKpAS3cf+m92CCUZN/Y9D5IPxD+82LECK
t4L5oio9fPk=
=0E3/
-----END PGP MESSAGE-----

--pgp-sign-Multipart_Fri_Sep_26_14:10:24_1997-1--

