Received: from localhost (daemon@localhost) by CS.UTK.EDU with SMTP (cf v2.9s-UTK) id UAA22780; Thu, 31 Oct 1996 20:43:08 -0500 Received: by CS.UTK.EDU (bulk_mailer v1.7); Thu, 31 Oct 1996 20:41:22 -0500 Received: by CS.UTK.EDU (cf v2.9s-UTK) id UAA22238; Thu, 31 Oct 1996 20:41:20 -0500 Received: from lacroix.wildbear.on.ca (lacroix.wildbear.on.ca [199.246.132.198]) by CS.UTK.EDU with ESMTP (cf v2.9s-UTK) id UAA22232; Thu, 31 Oct 1996 20:41:16 -0500 Received: by lacroix.wildbear.on.ca from localhost (router,SLmailNT V3.0 (alpha 1)); Thu, 31 Oct 1996 20:36:30 -0500 Received: by lacroix.wildbear.on.ca from tester.wildbear.on.ca (199.246.132.199::mail daemon,SLmailNT V3.0 (alpha 1)); Thu, 31 Oct 1996 20:36:29 -0500 X-Sender: "Jack De Winter" X-Mailer: Windows Eudora Version 2.1.1 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: drums@cs.utk.edu From: "Jack De Winter" Subject: about authentication trails in messages for RFC822bis Date: Thu, 31 Oct 1996 20:36:30 -0500 Message-Id: <19961031203630.069355ac.in@lacroix.wildbear.on.ca> Content-Transfer-Encoding: 7bit was talking to the gent responsible for the SASL and SMTP-AUTH drafts, and we were talking about a good way to trace an authenticated message. Are there currently any headers set aside for adding additional trace information? I ask this as I was told that the received line is pretty much solid, non extensible, and another header line would be better. regards, Jack ------------------------------------------------- Jack De Winter - Wildbear Consulting, Inc. (519) 576-3873 http://www.wildbear.on.ca/ Author of SLMail(95/NT) (http://www.seattlelab.com/) and other great products.