>>been happening for many years now.
> Macromedia/CF needs to address this issue if they haven't already.
Don't lose any sleep over this. I have clients that have been using
CF to mail for years with zero problems due to CF mail headers. There
was a time a LONG time ago when CF headers were an issue, but the A/S
industry has progressed in sophistication well past this
oversimplification.
Its far more important to have your mail server set up properly (CF is
not a mail server) so that other A/S systems don't see an open relay,
get a proper reverse dns etc. etc. Also you need mail that does have
a prop or two via cfmailparam.
I use this format below for html email. the mime type shouldn't be
used on CF 6+, and I'm pretty sure the reply-to is bad as RFC's go
(but putting it in has never hurt that I can tell). You need a
message ID. Imail will put it in for you if you don't and others
might as well. Putting it in expressly is the safest answer.
--
--Matt Robertson--
MSB Designs, Inc.
mysecretbase.com
<cfset variables.ContentValue="text/html; charset=UTF-8">
<cfmail
to="#my.Email#"
from="#your.Email#"
subject="Woo Hoo"
server="#my.EmailServer#"
type="HTML">
<cfmailparam name="Reply-To" VALUE="#my.Email#">
<cfmailparam name="Message-ID" VALUE="<#CreateUUID()[EMAIL PROTECTED]>">
<cfmailparam name="Content-Type" VALUE="#variables.ContentValue#">
<cfmailparam name="Mime-Version" VALUE="1.0">
<link href="" rel="stylesheet" type="text/css">
#MESSAGE.GOESHERE#
</cfmail>
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]
