Wade, There are several things you'll want to watch for, but let me temper my comments by saying we usually send out significantly more than 1000 emails in a job. A job consists of several volleys, where:
1. We pulse our emails, 500 per volley; 2 minutes between volleys (small send); 1000 per volley, 2 minutes between volley (large send). 2. We make sure that we don't flood a particular domain in a volley, particularly, AOL.com. Max send per volley to AOL is 200. 3. We try to keep up on dead emails, flooding AOL with a bunch of emails for accounts that no logner exist will also get you blacklisted. I'm trying to remember the other stuff, but mainly, that's what we follow here. mj/v On Tue, Mar 30, 2010 at 4:39 PM, Wade Preston Shearer < [email protected]> wrote: > I am about to launch a site for a client that is pre-populated with > accounts for their members. As part of the launch, I will need to run a > script that sends out an email to all of the members introducing them to the > new site, informing them that they have an account, and providing their > username and a randomly generated password. I am concerned about running a > script that cranks out 1,300 emails all at ounce. I know that that is > actually a small number in the world of mass email, but I don't want to get > their server black listed. Do I have anything to worry about? Should I batch > it up and send it out in small chunks? Any suggestions? > > > wade > > _______________________________________________ > > UPHPU mailing list > [email protected] > http://uphpu.org/mailman/listinfo/uphpu > IRC: #uphpu on irc.freenode.net > _______________________________________________ UPHPU mailing list [email protected] http://uphpu.org/mailman/listinfo/uphpu IRC: #uphpu on irc.freenode.net
