>Dwayne,
>
>Let me point out a few gotchas that hopefully the tutorial will cover.
>
>1) Outlook XP and the latesxt versions of Outlook Express block by default any _javascript_ or Active X Controls. That means if you send out any videos, Flash or a snippy _javascript_ most folks can't see it.
>
>
>2) The latest beta of Outlook blocks HTML email having formating or images from an external source. HTML email requires external images for displaying the images properly as the email is forwared from one person to the next. Marketers use this feature to embed web bugs allowing one to track the number of people who have opened the email message.
>
>3) You must use an opt-in list to send out the email. In some US States and contries, you can be legally liable for emails not sent to an opt in list. Even worse, you can also be placed on a Black Hole list if you're using an external server acting as a relay.
>
>4) You need to configrue your mail server to ensure outsiders can not relay off of the server you're using to send CFMAIL. CFMAIL does require an open relay to send out email-- on the other hand if you use NAT to make sure only non-routeable IP addresses are relayed by CFMAIL and specifically specify the non-routeable IP address of the Cold Fusion in the mail server, then you can protect yourself from spammers and not get yourself on a black hole list for having an open relay.
>
>
>>From a business point of view this has the following reprocussions.
>
>A) Your subject line must clear, consise and meaningful to the opener
>B) You should use plain text without forwarding unless the email generated is from an Intranet (where one can control the user experiance while using the firewall and black hole lists to control spam)
>C) If your trying this for an external audiance, you need to purcahse or generate an opt in list, have a privacy policy in place and have a real secure set-up from a hosting point of view.
>
>
>On the other hand why send out a message people can not read because they are protecting themselves from spam, viruses-- and protect yourself from potential legal and network configuration issues. IMHO, HTML email should only be used in an Intranet setting where one can control the message and the client.
>
>I know that this is a hot button issue among the CF talkers out there -- this has been discussed at length on this forum. However, I have seen the reprocussions of a poor network configuration and HTML email.
>
>Jeremy
>
>P.S. I've included how to set up the HTML email below as an FYI
>
>
>
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
