Re: [WebDNA] Mass email using WebDNA
This WebDNA talk-list message is from 2008
It keeps the original formatting.
numero = 100838
interpreted = N
texte = Psi Prime, Matthew A Perosi wrote: [snip] I've never tempted fate since the docs say something like "do do > that unless your email server can handle it". Is that a warning from > 10+ years ago when we had Intel 486 chips? Yes. :) .. well from a *long time ago* at least. > As for the [spawn] I recently learned that [spawn] has a processing > limitation. I created a script to parse through imported database > records and import them into another database. The script dies whenever > it processes more than 900 records. Not a [spawn] limitation :-) You are creating 900 "threads" when doing this (if I'm understanding you correctly). ;-) Probably good to keep those very limited (as stated in the docs) It took forever for me to figure > out that the [spawn] routine was dying. I tried to figure out why by > creating internal debug routines for the [spawn] but I was not able to > figure out the exact cause. I assume it's a memory overflow or > limitation of variables. Therefore, depending on the number of emails > sent I would recommend creating an appropriate number of [spawn]s to > complete this task. > > I can also tell you from personal experience that none of the > EMailFolders like more than 2000 files at a time. The server or sandbox > chokes to death! In my early attempts with this I tried process too > many [sendmails] at a time and the server got caught in an endless loop > of sending a single email over and over until I rebooted. > > I wrote a trigger that reorganizes the EMailFolders every night. It > moves the done emails into another subfolder and prevents the choking I > mentioned above. But if you want to send 400000 emails in a day you > need to account for this issue. Right, I guess I'd build an archiving system right into the script for the EMailCompleted directory... The emails that go into the EMailFolder directory waiting to be "sent" should be managed by the system as well... limiting the sends in batches, and accounting for "stuck" email files. You could use some of the file managing contexts to check for "stuck" files I suppose. As far as "time" goes.. yes, I've seen mass email apps take days and it may even be good to run a seperate lic. of WebDNA for huge mass mailings. Donovan (who is afraid he will be getting more spam by talking about this in public) :) > > > Matthew A Perosi | > Psi Prime, Inc. | > http://www.psiprime.com | > http://en.wikipedia.org/wiki/Psi_Prime%2C_Inc | > 323 Union Blvd. | > Totowa, NJ 07512 | > P: 973.413.8210 | > F: 973.413.8217 | > > > > Donovan Brooke wrote: > >> Tom Duke wrote: >> >>> Hi all, >>> >>> I need to upgrade a mass email tool that I have built for a client. >>> They are currently mailing to a list of about 7000. I was wondering >>> if anyone else has built such a tool? >>> >>> Things I need to code in to the upgrade are: >>> >>> - the ability to mail to a list of up 400000 >>> - the ability to track open rates for the email >>> - some method of handling email bounces >>> >>> I figure I need to decide whether WebDNA can do all this or whether I >>> need to look at something else like phpList. >>> >>> Thanks >>> - Tom >> >> >> >> Hi Tom, >> I haven't built quite the robust system.. but why not.. I don't think >> it is a question of whether or not WebDNA could do this, but whether >> or not it's coded correctly... 400000 emails eh? I'm >> not gonna qet more spam am I? ;-) >> >> I guess you'd have to build a robust system that not only plays well >> with the CPU but accounts for errors. I would think 5 spawned threads >> at a time? and make the general page a spawned function as well?.. >> just guessing really. >> >> Maybe instead of one search through the database, your system >> keeps track of the "max" and "startat" params... so you are always >> sending a limited search that gives the system a break between searches?? >> >> then upon failure (if it were to happen), you would know what your >> last startat was?? Just a couple thoughts. >> >> Good luck. >> Donovan >> >> >> > --------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list
. > To unsubscribe, E-mail to: > archives: http://mail.webdna.us/list/talk@webdna.us > old archives: http://dev.webdna.us/TalkListArchive/ -- Donovan D. Brooke PH/FAX: 1 (608) 291-2024 ---------------------------------------------- VP WebDNA Software Corporation 16192 Coastal Highway Lewes, DE 19958
Associated Messages, from the most recent to the oldest:
Psi Prime, Matthew A Perosi wrote: [snip] I've never tempted fate since the docs say something like "do do > that unless your email server can handle it". Is that a warning from > 10+ years ago when we had Intel 486 chips? Yes. :) .. well from a *long time ago* at least. > As for the [spawn] I recently learned that [spawn] has a processing > limitation. I created a script to parse through imported database > records and import them into another database. The script dies whenever > it processes more than 900 records. Not a [spawn] limitation :-) You are creating 900 "threads" when doing this (if I'm understanding you correctly). ;-) Probably good to keep those very limited (as stated in the docs) It took forever for me to figure > out that the [spawn] routine was dying. I tried to figure out why by > creating internal debug routines for the [spawn] but I was not able to > figure out the exact cause. I assume it's a memory overflow or > limitation of variables. Therefore, depending on the number of emails > sent I would recommend creating an appropriate number of [spawn]s to > complete this task. > > I can also tell you from personal experience that none of the > EMailFolders like more than 2000 files at a time. The server or sandbox > chokes to death! In my early attempts with this I tried process too > many [sendmails] at a time and the server got caught in an endless loop > of sending a single email over and over until I rebooted. > > I wrote a trigger that reorganizes the EMailFolders every night. It > moves the done emails into another subfolder and prevents the choking I > mentioned above. But if you want to send 400000 emails in a day you > need to account for this issue. Right, I guess I'd build an archiving system right into the script for the EMailCompleted directory... The emails that go into the EMailFolder directory waiting to be "sent" should be managed by the system as well... limiting the sends in batches, and accounting for "stuck" email files. You could use some of the file managing contexts to check for "stuck" files I suppose. As far as "time" goes.. yes, I've seen mass email apps take days and it may even be good to run a seperate lic. of WebDNA for huge mass mailings. Donovan (who is afraid he will be getting more spam by talking about this in public) :) > > > Matthew A Perosi | > Psi Prime, Inc. | > http://www.psiprime.com | > http://en.wikipedia.org/wiki/Psi_Prime%2C_Inc | > 323 Union Blvd. | > Totowa, NJ 07512 | > P: 973.413.8210 | > F: 973.413.8217 | > > > > Donovan Brooke wrote: > >> Tom Duke wrote: >> >>> Hi all, >>> >>> I need to upgrade a mass email tool that I have built for a client. >>> They are currently mailing to a list of about 7000. I was wondering >>> if anyone else has built such a tool? >>> >>> Things I need to code in to the upgrade are: >>> >>> - the ability to mail to a list of up 400000 >>> - the ability to track open rates for the email >>> - some method of handling email bounces >>> >>> I figure I need to decide whether WebDNA can do all this or whether I >>> need to look at something else like phpList. >>> >>> Thanks >>> - Tom >> >> >> >> Hi Tom, >> I haven't built quite the robust system.. but why not.. I don't think >> it is a question of whether or not WebDNA could do this, but whether >> or not it's coded correctly... 400000 emails eh? I'm >> not gonna qet more spam am I? ;-) >> >> I guess you'd have to build a robust system that not only plays well >> with the CPU but accounts for errors. I would think 5 spawned threads >> at a time? and make the general page a spawned function as well?.. >> just guessing really. >> >> Maybe instead of one search through the database, your system >> keeps track of the "max" and "startat" params... so you are always >> sending a limited search that gives the system a break between searches?? >> >> then upon failure (if it were to happen), you would know what your >> last startat was?? Just a couple thoughts. >> >> Good luck. >> Donovan >> >> >> > --------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list . > To unsubscribe, E-mail to: > archives: http://mail.webdna.us/list/talk@webdna.us > old archives: http://dev.webdna.us/TalkListArchive/ -- Donovan D. Brooke PH/FAX: 1 (608) 291-2024 ---------------------------------------------- VP WebDNA Software Corporation 16192 Coastal Highway Lewes, DE 19958
Donovan Brooke
DOWNLOAD WEBDNA NOW!
Top Articles:
Talk List
The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...
Related Readings:
splitting numbers in webDNA? (1997)
WebTrends (2002)
WebMerchant/MacAuthorize (1998)
Strange error (2000)
[shell] (2002)
I have observed and I am gone. (1998)
WebCat2 - Getting to the browser's username/password data (1997)
RE: [WebDNA] Calendar Edit (2010)
webcat license???? (1997)
Testing the WebCat Email List Members (2000)
New Plug-in and Type 11 errors (1997)
two unique banners on one page (1997)
Smith Micro - no competition (2000)
New Command prefs ... (1997)
Is Web Merchant Necessary? (2000)
XML Parse with XML WebDNA Syntax... (2004)
Rendering out a page (1997)
[GetMIMEHeader] does not work (under Linux?) (2000)
how do ye do this?????? (2001)
Blasted shownext (request for 4.0) (1998)