RAD Canyon BMX Email Updates

[J Gallo]

I just wanted to apologize for the issues over the last few weeks with RAD Canyon BMX's email updates. I've tried every trick I know (and a few I found) to get it right, but it still only wants to email about half of our registered users. I really believe at this point it's a host server issue, so I just need to program a workaround.

I have a plan of what I believe will solve the issue, and will attempt to finish up the programming over the next few days. My goal is to have it finished by this weekend, before next week's update, and before I go on vacation. Please know that you may see a test email or two as I debug the program.

Thank you for your continued support!

[srloth]

You might want to look at how many SMTP Relays you have with your ISP.
Bypass ISP restrictions on your outbound emails with SMTP Email Relay.
I host a bunch of my sites with GoDaddy and they allow me 250 relays per day (as part of my basic hosing package).
Users can have their ISP bump up the amount of relays per day, but they usually charge for that.

To get around this, I query up to 250 of my users in the database, send out the email and then do the next 250 the next day and so on...I automate this process. Sucks that users get newsletters over a day or so, but it works.

Hope this helps, Sean

[J Gallo]

You might want to look at how many SMTP Relays you have with your ISP.

Thanks for the info! I'm not sure all the technical terms my host uses, but this sounds like exactly the problem we had early on. They don't like "bulk" emails, so we would hit our limit quickly. They have since raised our limit to I believe 1,000 per week. Unfortunately, this issue has not solved our current problem, which may or may not be exactly what you are referring to.

It seems like we are having more of a "time out" issue. The program works great until about user 200 or so (it varies each time, so I know it's not an issue with database data), then it just stops; for regular sized emails. If we send an update with just a couple words, it works perfectly. So I think I'm going to do something very similar to what you suggested; break down the full list into smaller parts, say 150. So we'll run the program in 150 user increments until the end of the list. This should allow us to send the full email update to all users the same day, but theoritically prevent the time out issue.

Thanks for the info! If you can think of anything else please let me know!!