RE: [iMS] Content-Type

[Marc Lichtenfeld]

Thanks Howie. If figured those were my options, but just wanted to make sure. I installed 2.9.6 with a different name, and that does the trick.     -----Original Message----- From: Howie Hamlin [mailto:[EMAIL PROTECTED] Sent: Friday, January 09, 2004 2:56 PM To: inFusion Support List Subject: Re: [iMS] Content-Type The CFX creates the file with specific, standard formatting.  You can see the logic in the CFX source code (I'll reproduce this below).  If you need different formatting then you would need to either recompile the CFX tag or use the older version (I think 2.9.6 may do what you want).  You can install the older version on the same server as the newer version as long as you register it as a different CFX name in the CF administrator.   HTH,   Howie   ---- CFX formatting criteria -----   // MIME encoded messages have 3 general envelopes: // // 1 - text only (multipart/alternative) // 2 - text plus embedded content (multipart/related) // 3 - text with attachments (multipart/mixed) // // we need to construct the envelopes to contain the proper content as follows: // //   +----- multipart/mixed -----------------------+ //   |                                             | //   |  +----- multipart/related ---------------+  | //   |  |                                       |  | //   |  |  +----- multipart/alternative -----+  |  | //   |  |  |                                 |  |  | //   |  |  |  +---------------------------+  |  |  | //   |  |  |  |                           |  |  |  | //   |  |  |  |        plain text         |  |  |  | //   |  |  |  |                           |  |  |  | //   |  |  |  +---------------------------+  |  |  | //   |  |  |  |                           |  |  |  | //   |  |  |  |        HTML text          |  |  |  | //   |  |  |  |                           |  |  |  | //   |  |  |  +---------------------------+  |  |  | //   |  |  |                                 |  |  | //   |  |  +----- multipart/alternative -----+  |  | //   |  |                                       |  | //   |  |  +---------------------------------+  |  | //   |  |  |                                 |  |  | //   |  |  |    embedded content for HTML    |  |  | //   |  |  |                                 |  |  | //   |  |  |       images, sounds, etc.      |  |  | //   |  |  |                                 |  |  | //   |  |  +---------------------------------+  |  | //   |  |                                       |  | //   |  +----- multipart/related ---------------+  | //   |                                             | //   |  +---------------------------------------+  | //   |  |                                       |  | //   |  |           attachment 1                |  | //   |  |                                       |  | //   |  +---------------------------------------+  | //   |  +---------------------------------------+  | //   |  |                                       |  | //   |  |           attachment 2                |  | //   |  |                                       |  | //   |  +---------------------------------------+  | //   |                    .                        | //   |                    .                        | //   |                    .                        | //   |  +---------------------------------------+  | //   |  |                                       |  | //   |  |           attachment N                |  | //   |  |                                       |  | //   |  +---------------------------------------+  | //   |                                             | //   +----- multipart/mixed -----------------------+ // // //  So, we need to build the envelope properly.  If there is only text //  then we only need the multipart/alternative envelope and the main //  content type is multipart/alternative.  If the html portion of the //  email has embedded content then we need to have multipart/related //  as the main content type and have a sub envelope of multipart/alternative. //  If the email also has attachments then the main content type becomes //  multipart/mixed. // ----- Original Message ----- From: Marc Lichtenfeld To: inFusion Support List Sent: Friday, January 09, 2004 11:51 AM Subject: [iMS] Content-Type Hi Howie,   I am using the CFX_IMSMAIL tag to send e-mail to a service that only accepts plain text e-mail. I am sending a plain text e-mail with an attachment. It looks like the 2 boundaries may be throwing off the recipients e-mail parser. Is there any way to have the current CFX_IMSMAIL tag only use a single boundary like older CFX_IMSMAIL tags did for plain text with attachments?   If not, I can try using an older version of the CFX tag for sending to the service.   Thanks for the help, Marc ------------------------------------------------------ Marc Lichtenfeld Senior Programmer www.bigdough.com This list server is Powered by iMS "The Swiss Army Knife of Mail Servers" This list is provided as a free service. Although we will try to address issues in a timely manner, support via this list is not guaranteed. If you require expedited support then a support contract is required. Support may be purchased from http://www.coolfusion.com/commerce. Details regarding support options may be reviewed at: http://www.coolfusion.com/SupportOptions.cfm. To leave this list please complete the form at http://www.coolfusion.com/Support/ Need an iMS Developer license? Sign up for a free license here: http://www.coolfusion.com/Developers/ List archives: http://www.mail-archive.com/infusion-email%40eoscape.com/ Note: You are subscribed as [EMAIL PROTECTED]