You can no longer build multipart/alternative messages manually. You have to use CFMAILPART instead. At the very least, this means you have to go rewrite all your multipart/alternative CFMAIL tags. If you're doing other things (like inlining images), then you're dead in the water; no way to do it on CFMX 6.1.
Not huge problems, but nasty enough, and made worse by MM's stance that this is the first time you've EVER been able to send multipart/alternative email with CF, and therefore code that has been working for years can break with no issue, or even a warning (docs, errata, code analyzer, release notes). It was pure "check out how cool we are" marketing BS, in my opinion, and it certainly made my life difficult. Cheers, barneyb > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Phil Cruz > Sent: Friday, May 07, 2004 2:34 PM > To: [EMAIL PROTECTED] > Subject: CFMAIL (was RE: [CFCDev] CFINCLUDE forces var scope > into arguments?) > > At 02:31 PM 5/7/2004, Barney Boisvert wrote: > > > In MX 6.1, I can see your point. However, in MX 6.0, > > > functions were not > > > transaction-aware, so you had to cfinclude your queries to > > > achieve the same > > > effect. > > > >A very valid point, though aside from CFMAIL getting totally > hosed, I can't > >think of a reason to still be running 6.0. > > What are the problems with CFMAIL in 6.1? > > Phil ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [EMAIL PROTECTED] with the words 'unsubscribe cfcdev' in the message of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by Mindtool, Corporation (www.mindtool.com). An archive of the CFCDev list is available at www.mail-archive.com/[EMAIL PROTECTED]
