Alan,
I think there is a incompatibility here. According to Adobe documents
(I'm not saying this what needs to happen, but just pointing out), the
"type" attribute of <cfmail> is:
----------
MIME type of the message. Can be a valid MIME media type or one of the
following:
* text: specifies text/plain type.
* plain: specifies text/plain type.
* html: specifies text/html type.
For a list of all registered MIME media types, see
www.iana.org/assignments/media-types/.
----------
So it can be a "shortcut" or a full and complete MIME type. The
behavior of the "type" attribute of <cfmail> differs from the behavior
of the "type" attribute of <cfmailparam> and <cfmailpart> (both of which
support the shortcuts or fully qualified MIME types).
Derrick is referring the EmailLogger bundled with Mach-II. We used the
full MIME type of "text/html" instead of the "html" shortcut which is a
shortcut for "text/html". I think that cfmail should support the
"shortcuts" (current behavior) or fall back to the passed MIME value if
the developer chooses something else. One example is using <cfmail> to
send mail with the MIME of "multipart/digest" and using <cfmailpart>.
This is the format used to send digest style emails. For example, the
Apache Tomcat list sends digests in this format. The current behavior
of Open BD restricts the usage of the tag. Here's a link the usage of
multipart/digest from the RFC specs:
http://tools.ietf.org/html/rfc2046#section-5.1.5
I think the "type" attribute of <cfmail> should be corrected to match
the behavior of <cfmailpart> and <cfmailparam>'s "type" attribute.. I
don't think it would be hard to check if the value of "type" is of a
supported shortcut in which the correct MIME type is used or if no
shortcut matches -- then the value supplied by the developer is passed
on. I'll be happy to log a ticket if this is deemed a worthy change.
Best,
.Peter
Alan Williamson (aw1) said the following on 10/18/2009 11:51 AM:
> I believe the only values that CFMAIL support in the "type" field is
> "HTML" or "TEXT". Therefore, anything that is not those will default to
> simply text.
>
> This is different from constructing your CFMAIL using
> CFMAILPART/CFMAILPARAM child tags.
>
> So, to go back to your original observation, this is what i would expect
> to see.
>
>
>> I just stumbled upon something interesting in openBD when using <cfmail>
>> with a type of "html" and "text/html".
>>
>
> >
>
--~--~---------~--~----~------------~-------~--~----~
Open BlueDragon Public Mailing List
http://groups.google.com/group/openbd?hl=en
official site @ http://www.openbluedragon.org/
!! save a network - trim replies before posting !!
-~----------~----~----~----~------~----~------~--~---
