Re: CID url type
MARKJOSEPH@delphi.com Fri, 13 October 1995 21:05 UTC
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa18406; 13 Oct 95 17:05 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa18402; 13 Oct 95 17:05 EDT
Received: from list.cren.net by CNRI.Reston.VA.US id aa02308; 13 Oct 95 17:05 EDT
Received: from localhost (localhost [127.0.0.1]) by list.cren.net (8.6.12/8.6.12) with SMTP id QAA27905; Fri, 13 Oct 1995 16:25:37 -0400
Received: from dimacs.rutgers.edu (root@dimacs.rutgers.edu [128.6.75.16]) by list.cren.net (8.6.12/8.6.12) with ESMTP id QAA27865 for <ietf-822@list.cren.net>; Fri, 13 Oct 1995 16:25:25 -0400
Received: from bos1f.delphi.com (SYSTEM@bos1f.delphi.com [192.80.63.6]) by dimacs.rutgers.edu (8.6.12+bestmx+oldruq+newsunq+grosshack/8.6.12) with ESMTP id QAA01256 for <ietf-822@dimacs.rutgers.edu>; Fri, 13 Oct 1995 16:25:25 -0400
Received: from delphi.com by delphi.com (PMDF V5.0-5 #10880) id <01HWEBY7RFV4924450@delphi.com> for ietf-822@dimacs.rutgers.edu; Fri, 13 Oct 1995 16:25:21 -0400 (EDT)
Message-Id: <01HWEBY7RPIA924450@delphi.com>
Date: Fri, 13 Oct 1995 16:25:21 -0400
X-Orig-Sender: owner-ietf-822@list.cren.net
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: MARKJOSEPH@delphi.com
To: ietf-822@dimacs.rutgers.edu
Subject: Re: CID url type
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET="US-ASCII"
Content-transfer-encoding: 7bit
X-VMS-To: INTERNET"ietf-822@dimacs.rutgers.edu"
X-Listprocessor-Version: 7.2 -- ListProcessor by CREN
There seems to be two cases when creating an HTML bodypart in a MIME message. Case 1: the user is composing the HTML directly in a WYSWYG mail client editor. In this case all relative URLs could easly be expanded by the mail client to the full URL. Case 2: the user drags and drops an existing HTML page off of the Web or from somewhere else. In this case the user wants the page to go "as is". For the mail client to "fix up" the HTML page it runs the risk of breaking something. Better to leave the HTML page alone and on the receiving side set the base URL in the browser just before the HTML page is displayed. draft-ietf-mimesgml-related-03.txt I think it should be "cid:222222" instead of "cid:<2222222>". In RFC1630 the "mid:222222" is defined to be without the "<>". Unfortunately its not very clear in RFC1630 about "cid:", but it should be consistent. Regards, Mark Joseph The Wollongong Group, Inc.
- Re: CID url type MARKJOSEPH
- Re: CID url type Ed Levinson
- Re[2]: CID url type Ron Croonenberg
- Re: Re[2]: CID url type Valdis.Kletnieks
- Re: CID url type MARKJOSEPH
- Re: Re[2]: CID url type Rens Troost
- Re: Re[2]: CID url type Ed Levinson
- Related-03 example [was Re: CID url type] Ed Levinson