We don't have any plans of altering the way iMS searches for templates.  However, 
there are some things that you can do.
If you have two IP addresses on the machine - one for development and one for 
production then you can separate templates
by IP address.  For example:

\ims\domains\10.1.1.1\
\ims\domains\10.1.1.2\

Both the POP and SMTP server would follow the IP address naming.

Or, you can set up a development server.  iMS developer licenses are free.

Regards,

Howie

----- Original Message -----
From: "Tac" <[EMAIL PROTECTED]>
To: "inFusion Support List" <[EMAIL PROTECTED]>
Sent: Monday, October 21, 2002 4:05 PM
Subject: [iMS] script directory naming request


> Currently the scripts are stored in a directory defaulting to ims\domains,
> and if you want different domains to run different scripts, you put the
> scripts into a subdirectory of that same name.
>
> This is somewhat difficult to incorporate into our source control system.
> What I'd prefer to see is a directory of directories, so that the scripts
> run were based on ims\scripts\<domain_name>, with a default of
> ims\scripts\default, or something like that.
>
> Or, I'm open for suggestions.  I've always found it very difficult to debug
> IMS, maybe I'm using the wrong approach.  We've rewritten all the core
> scripts (data, rcpt, etc.) in PHP, customized for a listserv environment,
> and would like a way to use one domain for testing and the other for the
> real mail.
>
> Thx for any ideas you might have about this.
>
> Tac
>
==^=======================================================
     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/iMSSupport.cfm
Need an iMS Developer license?  Sign up for a free license here:
http://www.coolfusion.com/iMSDevelopers.cfm
List archives: http://www.mail-archive.com/infusion-email%40eoscape.com/
Note: You are subscribed as [email protected]
==^=======================================================


Reply via email to