At 6/3/2003 09:46 PM -0400, Howie Hamlin wrote:
>I announced several times that iMS 2.4f requires cfx version 3.3.

Sorry... I guess it didn't "sink in" or something.

>  The cfx is downward compatible with older versions of iMS, BTW.  If you are sending 
> mail with 1 control file and 1 mail file then the version doesn't matter.  If you 
> are sending mail with more than one control file associated with a single mail file 
> then the 3.3 version is mandatory because there are now counter files that are 
> needed in these situations and these are only in the latest cfx.

OK you're saying the spec for putting mail into the iMS queue has changed.  This I 
imagine can have some fairly far-reaching consequences for anyone's custom solutions 
out there.  I know it does here, somewhat, so we're probably stuck at a lower version 
for now.  Is the new spec documented anywhere?  Also, do you plan on updating the COM 
object to support the new spec?

Thanks,
-Max




>Regards,
>
>Howie
>
>----- Original Message ----- 
>From: "Max Paperno" <[EMAIL PROTECTED]>
>To: "inFusion Support List" <[EMAIL PROTECTED]>
>Sent: Tuesday, June 03, 2003 9:37 PM
>Subject: [iMS] cfx/ims versions (was Mail files missing)
>
>
>> Howie,
>> 
>> Is cfx_imsmail 3.3 required for iMS POST 2.4.6?  Older CFX's will cause problems?  
>> mail-archive.com is down so I can't look up if I missed/forgot something about that 
>> from you on the list  :-)  If yes, then my next question will be: why?
>> 
>> Thanks,
>> -Max
>> 

==^=======================================================
     This list server is Powered by iMS
   "The Swiss Army Knife of Mail Servers"
   --------------------------------------
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/Support/
List archives: http://www.mail-archive.com/infusion-email%40eoscape.com/
Note: You are subscribed as [EMAIL PROTECTED]
==^=======================================================


Reply via email to