are you saying that if I send a mail for example to [EMAIL PROTECTED] that 
has 100000000000000000 users on data.cfm the pop/smtp client will not 
desconect untill the data.cfm is finish?

if that is the case, would sending a  RESULT=ACCEPT on data.cfm to the the 
pop/smtp client and sending the list request to other template would do it?

At 10:31 p.m. 26/03/01 -0500, you wrote:
>The disadvantage to processing the mail right away is that the remote side
>will wait while the list mail is processed.  This may not be a problem with
>small lists but with larger lists the remote side could time out or if the
>sender is a local POP user then they may get an error that their server has
>not responded (the default timeout in Outlook Express is 60 seconds).
>
>Regards,
>
>Howie
>
>----- Original Message -----
>From: "Guillermo Dewey" <[EMAIL PROTECTED]>
>To: "inFusion Support List" <[EMAIL PROTECTED]>
>Sent: Monday, March 26, 2001 10:28 PM
>Subject: Re: [iMS] list server
>
>
> > would you see a disadvantage on identifying the list on data.cfm and make
> > the process right away ?
> >
> >
> > our data.cfm is divided on 5 filters and 4 processes. all of them are made
> > on includes .. they all set keys and depending on the Combinations
>function
> > 4 ease or keeps the mail file. Ever cfximsmail has its own priority
> > depending on the task .. list server has a low priority..
> >
> >                                  <!--- Function 1 "List Server" --->
> >                                            <cfinclude
> > template="data/function1.cfm">
> >                                  <!--- Function 2 "Forwards" --->
> >                                             <cfinclude
> > template="data/function2.cfm">
> >                                  <!--- Function 3 "Autoresponders" --->
> >                                            <cfinclude
> > template="data/function3.cfm">
> >                                  <!--- Function 4 "Check for mail to store
> > or delete" --->
> >                                             <cfinclude
> > template="data/function4.cfm">
> >
> > At the beginning option 1 you mention came to me but I had some problem
> > dealing with attachments.. specially with more than one.. code started to
> > get complex and became slow on the execution..   The largest list I have
> > test using our actual code is 120 users.. and its doing good..  but I will
> > wait an see how it does with 10000 members on a list..
> >
> > option 2
> > I have to see.. its looks pretty cool :) I will try it as soon as I get
> > some things finish.,
> >
> > thanks howie
> >
>
>
>
>========================================================================
>      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/
>========================================================================


********************************************
*   Guillermo Dewey Guerra
*   Metro Solutions S.A. de C.V.
*   [EMAIL PROTECTED]
*   ICQ: 25876549 (GDewey)
*
*   http://www.metro.com.mx
*   http://www.ablecommerce.com.mx
*
*   Tel. (011) (52) (8) 3-90-7000
*   Fax (011) (52) (8) 3-90-7001
*   Cel. (011) (52) (044) (8) 3-09-24-16
*   Monterrey N.L. Mexico
  ********************************************


========================================================================
     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/
========================================================================

Reply via email to