----- Original Message ----- 
From: "Philip Brashear" <[EMAIL PROTECTED]>
To: "inFusion Support List" <[EMAIL PROTECTED]>
Sent: Wednesday, September 24, 2003 2:51 PM
Subject: [iMS] POST files


> I've been reading through the archives and the IMS manual, and I think I
> understand more or less what I'm asking here. :)
> 
> Just to be sure I do, let me ask this. If I use CF to write a control file
> and a mail file and stick 'em in the queued and out directories,
> respectively, the POST server will pick 'em up and deliver 'em, right?
> Assuming I have named the files properly, of course
> (control=20hexcharacters_mailfile.mail and mail=20hexcharacters.mbx).
> 

You need to make sure that you write the control file first (especially in later iMS 
versions).  Also, if you are writing more than one control file for a mail source 
file, the server (v2.4f and higher) requires an associated counter file.  If you are 
writing one mail file and one control file then the counter is not needed.

> Is there anything else to this? How far ahead should I set the next value in
> the control file to ensure it gets picked up, or is there some process by
> which I need to notify the POST server that there's new mail to pick up?
> 

The server continually looks for new files.  You would just need to make sure that the 
nextdelivery date/timr is the current date/time or less.

You can always use the spooldir parameter of the cfx tag to write files to a test 
folder for examination (a good way to check the email and control file formats).

HTH,

Howie

> Thanks,
> Philip
> 
==^=======================================================
     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/Developers/
List archives: http://wwwmail-archive.com/infusion-email%40eoscape.com/
Note: You are subscribed as [EMAIL PROTECTED]
==^=======================================================


Reply via email to