Why cfmailpart not including text/plain?

[Guest]

I've given up on being able to parse the text/html base64 encoded messages with my Thunderbird email client.  There seems to be a long standing bug since 2009 that prevents me from parsing the email with my filters to sort them.

Anway, as a workaround till that gets fixed I was trying to simply put text in the email so that the key elements can be parsed for sorting with the filters.  I can't figure out why this example below strips out the text/plain portion.  Please forgive the formatting.

<cfmail to="me@domain.edu" from="webmaster@domain.edu" subject="domain- Error Page">

                                     <cfmailpart type="text/plain">

                                        #CGI.LOCAL_ADDR#<br/>

                                        #error.Browser#<br/>

                                        #error.Diagnostics#<br/>

                                        #error.Message#<br/>

                                        #error.QueryString#<br/>

                                        #error.RemoteAddress#<br/>

                                        #error.Type#<br/>

                                    </cfmailpart>

                                    <cfmailpart type="text/html">

                                        <cfdump var="#error#" metainfo="no" abort="false">

                                    </cfmailpart>

</cfmail>

At this time the text/html is the only thing that is visible.  None of the text/plain comes through.

[Adam Cameron.]

How are you determining this?

If you're just eyeballing the screen in a mail client, you will only see one of them: whichever the client best supports (HTML, failing over to TEXT if the client doesn't support HTML).

I might be stating the blinding obvious to you here, but you're not clear about what you mean by "visible"..?

--

Adam

[Guest]

I think I'm suffering from Gross Conceptual Error on this one.  I don't think I fully understood what to expect from use of cfmailpart.

I was trying to receive messages with two different types to workaround the Thunderbird base64 issue.  I'll revisit this later and see if there is another option.