That thing was originally meant to throttle down mail to a level that a shared ISP 
could handle.  I put it together partially with the advice of one of the guys at 
Virtualscape (which will tell a lot of people how old the code is).

It *may* help you.  I remember I was told that for the mail to be stable that one user 
on the box shouldn't pump out more than (get this) 300 messages per hour.  Personally 
I think they were being deliberately arch-conservative.  I had no problems cranking 
out about quadruple that.

Nowadays I still use the technique for an entirely different reason, as I'm now on a 
dedicated box of my own.  Several months ago it was discussed on some other lists that 
AOL and MSN seemed to have some sort of 'frequency' filter in place that, if it saw a 
lot of mail blasting in to its users from a single source, blocked that sender for 
maybe 30 minutes.  I experienced this myself and the recommendation (on the Imail 
list, I think) was to crank up the server retry count.

However, using that throttler at a speed of about 7200 per hour has kept my clients 
under that radar ever since.  That rate works best if I tie it to the cf server's mail 
fetch rate, so if its set to 15 seconds (it is) I run the mail throttler at 17 second 
intervals so two batches of mail never pile up and get shot out.

Crude but effective.

-------------------------------------------
 Matt Robertson,     [EMAIL PROTECTED]
 MSB Designs, Inc. http://mysecretbase.com
-------------------------------------------


---------- Original Message ----------------------------------
From: "Mark Leder" <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
Date: Tue, 1 Jul 2003 16:35:13 -0400

>I agree with all your comments Matt.
>
>A slightly different issues, related to these attachments.  Doing a send out
>to a list of about 600 emails, the server throws a timeout error midway
>through the process.  When I set the cfmail timeout to, say = "900", I still
>get the error, at the same point in time (I'm on a shared server at an ISP).
>Looking at the archives (1/9/2003, "Email Quandry:), I found a script that
>Matt had posted setting a "run-rate" per hour (throttling) the email send
>outs.  Would you think this script would be effective in this situation?
>
>Thanks, Mark 
>
>-----Original Message-----
>From: Matt Robertson [mailto:[EMAIL PROTECTED] 
>Sent: Tuesday, July 01, 2003 4:10 PM
>To: CF-Talk
>Subject: Re: CFMail Attachments
>
>
>AOL does this themselves and unless someone knows a magic setting and wants
>to share this is out of your control.  The reason for it is that AOL likes
>to make themselves as annoying and difficult as possible.
>
>Oh, and don't forget capricious and intrusive.  That too.
>
>-------------------------------------------
> Matt Robertson,     [EMAIL PROTECTED]
> MSB Designs, Inc. http://mysecretbase.com
>-------------------------------------------
>
>
>---------- Original Message ----------------------------------
>From: "Mark Leder" <[EMAIL PROTECTED]>
>Reply-To: [EMAIL PROTECTED]
>Date: Tue, 1 Jul 2003 15:19:14 -0400
>
>>Hi all,
>>I'm using <cfmailparam> (twice) to send two email attachments (pdf 
>>files). (This is a text only message, no HTML).  Receives fine when 
>>sending to Outlook and Eudora.  However, I find that receiving in AOL 
>>8.0, the two attachments are in Zip format.  I'm concerned that some 
>>folks won't have winzip to unzip these files (such as Mac's).
>>
>>How to I force the attachments not to be zipped up or otherwise 
>>altered?
>>
>>Thanks, Mark
>>
>>
>
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4
Subscription: 
http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribe&forumid=4
FAQ: http://www.thenetprofits.co.uk/coldfusion/faq

Your ad could be here. Monies from ads go to support these lists and provide more 
resources for the community. 
http://www.fusionauthority.com/ads.cfm

                                Unsubscribe: 
http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
                                

Reply via email to