Skip Navigational Links
LISTSERV email list manager
LISTSERV - COMMUNITY.EMAILOGY.COM
LISTSERV Menu
Log In
Log In
LISTSERV 17.5 Help - LSTOWN-L Archives
LISTSERV Archives
LISTSERV Archives
Search Archives
Search Archives
Register
Register
Log In
Log In

LSTOWN-L Archives

LISTSERV List Owners' Forum

LSTOWN-L

Menu
LISTSERV Archives LISTSERV Archives
LSTOWN-L Home LSTOWN-L Home

Log In Log In
Register Register

Subscribe or Unsubscribe Subscribe or Unsubscribe

Search Archives Search Archives
Options: Use Forum View

Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
Re: Sending HTML content thru LISTSERV
From:
"Good, Donald" <[log in to unmask]>
Reply To:
LISTSERV list owners' forum <[log in to unmask]>
Date:
Fri, 28 Mar 2003 16:15:32 -0600
Content-Type:
text/plain
Parts/Attachments:
text/plain (35 lines)
You are missing 2 things:

First, the MIME headers need to be a part of the email message headers.  The
email message headers are separated from the email message body by a blank
line.  If you copy and paste your MIME and HTML into the body of your
message, then it will be after that blank line and all of it will be
considered part of the body and treated as plain text.  In general, most
email clients do not give you direct access to header information to control
MIME headers.

Second, in the example you gave, there are some missing MIME parts,
specifically, boundary= in the Content-Type: header, the blank line above
<html> separating headers from body, and the boundary marker.  These are
automatically generated by the mail client when a MIME/HTML message is
composed if the mail client can compose a message in HTML format.  Below is
one example among many possibilities.

Date:
From:
Subject:
To:
MIME-Version: 1.0
Content-Type: text/html; charset=us-ascii; boundary="boundarymarkerstring"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

<html>
<head>
...
</html>
--boundarymarkerstring--

So the non-technical answer is to have the mail client format the message as
an HTML message if it has that option.

ATOM RSS1 RSS2

COMMUNITY.EMAILOGY.COM CataList Email List Search Powered by LISTSERV