> Formatting emails is a wash, anyway, since many people use variable-width
> fonts.
>
> In order to send HTML emails, you have to send a MIME header. And you have
> to package the content according to MIME. It's somewhat convoluted. It's
> the same concept as sending attachments. It's well-covered in books (even
> mine) and on the Web, so you should be able to figure out how to do it.
>
> As with many things, HTML emails usually work fine on Windows and not as
> well on Macs, Linux or whatever. As far as I know, there's no way to send
> someone a message that auto-detects whether their client can handle HTML
> emails.
Almost all reasonably new mail clients (i.e., clients that understand
MIME) handle HTML just fine, as long as you format the MIME correctly.
I haven't done HTML messages, but I've formatted attachments and I'm
guessing it looks something like:
<these are the headers>
MIME-Version: 1.0
Content-type: multipart/alternative; boundary=boundary12345
--boundary12345
Content-type: text/plain
<put text form of message here>
--boundary12345
Content-type: text/html
<put html here>
--boundary12345--
<email ends here>
("boundary12345" just has to be something that isn't present in the
bodies of the parts)
People who have non-HTML mailers will see the text, people with HTML
mailers will see the HTML version. It will be about as portable as
your HTML is (i.e., if you use <FONT SIZE="1"> some people won't be
able to read it).
I might have the multipart/alternative thing wrong... I've only done
attachments, so you'll have to test it to make sure (though please
tell me if I'm wrong, for my own education).
--
Ian Bicking
4869 N. Talman Ave., Chicago, IL 60625
(773) 275-7241
[EMAIL PROTECTED] http://www.colorstudy.com/ianb
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Site: http://www.working-dogs.com/freetrade/
Problems?: [EMAIL PROTECTED]
