home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!cs.utexas.edu!swrinde!elroy.jpl.nasa.gov!decwrl!decwrl!infopiz!mccall!ipmdf-newsgate!list
- From: mitchell%uthscsa.bitnet@ymir.claremont.edu (Scott J. Mitchell)
- Newsgroups: vmsnet.mail.pmdf
- Subject: RE: two minor points
- Message-ID: <01GNHMFBC00Y8Y4WOB@YMIR.CLAREMONT.EDU>
- Date: 12 Aug 92 16:26:00 GMT
- Organization: The Internet
- Lines: 20
- Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
- Resent-Date: 12 Aug 1992 11:26 -0500 (CDT)
- Resent-From: epmdf@YMIR.CLAREMONT.EDU
- Errors-To: epmdf@YMIR.CLAREMONT.EDU
- Resent-Message-ID: <01GNHMFJJLWI94E14W@YMIR.CLAREMONT.EDU>
- X-Vms-To: IN%"ipmdf@YMIR.CLAREMONT.EDU"
- Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
- Content-Transfer-Encoding: 7BIT
- Original_To: BITNET%"ipmdf@ymir"
-
- >> Is this information "boundary..." important to the person, who really only
- >> needs to know that he spelled the nodename wrong?
- >> Can we suppress it?
-
- > This information is boundary information separating different pieces of the
- > message. The message, if you examine the headers, is a multipart message
- > which had two pieces: bad address list and returned content of the original
- > message. You cannot remove this information. When we finish up our user
- > agent, users using it will not see these boundary markers and whatnot (althoug
- h
- > they will still be there).
-
- I hate to sound retrograde, but there are probably some sites that would
- prefer non-multipart notices. Many people here won't have MIME-speaking
- UAs in the near future. Novice users looking at these things sometimes
- despair before noticing that they contain readable information!
-
- Scott Mitchell
- University of Texas Health Science Center
- mitchell@uthscsa.edu
-