Received: from localhost (daemon@localhost) by CS.UTK.EDU with SMTP (cf v2.9s-UTK) id SAA06848; Wed, 27 Nov 1996 18:53:11 -0500 Received: by CS.UTK.EDU (bulk_mailer v1.7); Wed, 27 Nov 1996 18:52:42 -0500 Received: by CS.UTK.EDU (cf v2.9s-UTK) id SAA06788; Wed, 27 Nov 1996 18:52:40 -0500 Received: from koobera.math.uic.edu (qmailr@koobera.math.uic.edu [128.248.178.247]) by CS.UTK.EDU with SMTP (cf v2.9s-UTK) id SAA06782; Wed, 27 Nov 1996 18:52:37 -0500 Received: (qmail 19377 invoked by uid 666); 27 Nov 1996 23:58:06 -0000 Date: 27 Nov 1996 23:58:06 -0000 Message-ID: <19961127235806.19376.qmail@koobera.math.uic.edu> From: "D. J. Bernstein" To: drums@cs.utk.edu Subject: Re: draft-ietf-drums-msg-fmt-00.txt > The question was whether it was unreasonable to say whether they SHOULD. > Would your concern be solved if it were "should" instead of "SHOULD"? No. There are some applications where Resent seems to make sense, and many applications where it definitely doesn't. We can't make a blanket statement about ``any message which is reintroduced into the transport system after being received out of the transport system.'' > do you think that "1*(ALPHA / SPACE)" > would be a good way of putting this in the obsolete syntax? I haven't had time to study the issue. A quick search shows that ``MET DST'' appears in many mail messages generated in 1996; so obviously MUA implementors will have to be told _something_. This needs discussion. ---Dan Sick of sendmail? Don't get mad; get qmail. http://pobox.com/~djb/qmail.html