tags:

views:

3179

answers:

9

I am currently writing a music blog. The administrator posts a new article every 2-3 days. Once the administrator posts an article, a mass email will be sent to around 5000 subscribers immediately.

What is the best way to implement the mass mail feature?

Does the following function work?

function massmail() 
{
  $content = '...';
  foreach ($recipients as $r) {
    $_content = $content . '<img src="http://xxx/trackOpenRate.php?id='.$r.'"&gt;';
    mail($r, 'subject', $_content);
  }
}

Another question: If all 5000 subscribers are using Yahoo Mail, will Yahoo treat it as a DDOS attack and block the IP address of my SMTP server?

+11  A: 

First off, using the mail() function that comes with PHP is not an optimal solution. It is easily marked as spammed, and you need to set up header to ensure that you are sending HTML emails correctly. As for whether the code snippet will work, it would, but I doubt you will get HTML code inside it correctly without specifying extra headers

I'll suggest you take a look at SwiftMailer, which has HTML support, support for different mime types and SMTP authentication (which is less likely to mark your mail as spam).

Extrakun
+1 You may also want to do some delayed/timed sending, depending on how well you can control the mail server. Some destination servers may block you if you send hundreds of messages at once. Also, you may want to keep a detailed log on the status of each email sent.Having 100+ test email accounts (your test accounts), and testing them incrementally with different content will help.
Mercer Traieste
+1 for SwiftMailer
alex
+5  A: 

This is advice, not an answer: You are much, much better off using dedicated mailing list software. mailman is an oft-used example, but something as simple as mlmmj may suffice. Sending mass mails is actually a more difficult task than it actually appears to be. Not only do you have to send the mails, you also have to keep track of "dead" addresses to avoid your mail, or worse, your mailserver, being marked as spam. You have to handle people unsubscribing for much the same reason.

You can implement these things yourself, but particularly bounce handling is difficult and unrewarding work. Using a mailing list manager will make things a lot easier.

As for how to make your mail palatable for yahoo, that is another matter entirely. For all its faults, they seem to put great stock in SPF and DomainKey. You probably will have to implement them, which will require co-operation from your mail server administrator.

Michiel Buddingh'
+4  A: 

You may consider using CRON for that kind of operation. Sending mass mail at once is certainly not good, it may be detected as spam, ddos, crash your server etc.

So CRON could be a great solution, send 100 mails at once, then wait a few minutes, next 100, etc.

usoban
+1  A: 

Also have a look at the PHPmailer class. PHPMailer

Roland
If I am not wrong, isn't SwiftMailer built on top of PHPMailer?
Extrakun
There are alot of things built on top of PHPMailer, PHPList is also built on top of PHPMailer
Roland
+3  A: 

I would insert all the emails into a database (sort of like a queue), then process them one at a time as you have done in your code (if you want to use swiftmailer or phpmailer etc, you can do that too.)

After each mail is sent, update the database to record the date/time it was sent.

By putting them in the database first you have

  1. a record of who you sent it to
  2. if your script times out or fails and you have to run it again, then you won't end up sending the same email out to people twice
  3. you can run the send process from a cron job and do a batch at a time, so that your mail server is not overwhelmed, and keep track of what has been sent

Keep in mind, how to automate bounced emails or invalid emails so they can automatically removed from your list.

If you are sending that many emails you are bound to get a few bounces.

bumperbox
+3  A: 

Why don't you rather use phplist? It's also built on top of PHP Mailer and a lot of industry leaders are using it. I've used it myself a couple of times to send out bulk mails to my clients. The nice thing about phplist is that you can throttle your messages on a domain level plus a time limit level. For a complete list of features have a look at: http://www.phplist.com/details

What we've also done with a couple of internal capture systems we've got was to push our user base to the mailling list and then have a cron entry triggering a given mail each day. The possibilities are endless, that's the awesome thing about open source!

Conrad
+2  A: 

Do not send email to 5,000 people using standard PHP tools. You'll get banned by most ISPs in seconds and never even know it. You should either use some mailing lists software or an Email Service Provider do to this.

Nir Levy
That might be true yes, but if you keep your mails below 100 messages per hour then most ISP's wouldn't give you to much grief; however as soon as you abuse their network then you're in for it! Just make sure your headers are structured to standards; Don't abuse networks and you'll be safe.
Conrad
+1  A: 

Also the Pear packages:

http://pear.php.net/package/Mail_Mime http://pear.php.net/package/Mail http://pear.php.net/package/Mail_Queue

sob.

PS: DO NOT use mail() to send those 5000 emails. In addition to what everyone else said, it is extremely inefficient since mail() creates a separate socket per email set, even to the same MTA.

bucabay
A: 

There is already a solution in place for people getting updates in their inbox when a blog entry is posted. It's called RSS. Wouldn't you be happier putting your blog somewhere that provides an RSS feed for it and having people subscribe to you the usual way? Reinventing the wheel is rarely a good use of anyone's time.

Kate Gregory
This isn't really reinventing the wheel. Email and RSS are separate comm channels. Bad idea to ignore one channel (especially when email has wider adoption than RSS) just because there's an alternative.
Travis Leleu