Re: [web2py] Re: Create an email queing feature...
On 05/28/2011 12:17 AM, pbreit wrote: I'd also suggest SendGrid (200/day free, 10 cents for 1,000). It looks like you are now trying it as a background process. I've had better luck with cron. And since you only want to send every hour or so, you could set the cron to run hourly. I didn't know these services existed. I think I will try my way first then then try those if I need more speed. BR, Jason Brower
Re: [web2py] Re: Create an email queing feature...
It's not for speed so much as for deliverability.
Re: [web2py] Re: Create an email queing feature...
After looking at the site I see what you mean. I will keep it in mind as the program increases in size. BR, Jason Brower On Sat, May 28, 2011 at 4:55 PM, pbreit pbreitenb...@gmail.com wrote: It's not for speed so much as for deliverability.
[web2py] Re: Create an email queing feature...
What about using something like Sendgrid (http://sendgrid.com)? Or Postmark (http://postmarkapp.com/)? Let somebody else worry about throttling and blacklists and all of the headaches of smtp servers. Matt On May 26, 10:50 pm, Jason Brower encomp...@gmail.com wrote: Yes, I practically have that now. The issue is how do I create the cron task and script to execute it? One way I am taking this further is, as long as the conference is alive I can compair this list with who has signed into the conference to get an idea of how many people have reacted to the email and are now attending the conference. Like an RSVP list so to say. :) There is a lot of information actually, that I think I can gather from this. BR, Jason Brower On 05/27/2011 04:11 AM, ron_m wrote: A possible idea, each email insert into a table. When the cron job wakes up have it read X number of emails with the smallest ID value from the table and process them. Delete the row as each one is completed.
[web2py] Re: Create an email queing feature...
+1 On May 27, 4:02 pm, mattgorecki m...@goelephant.com wrote: What about using something like Sendgrid (http://sendgrid.com)?Or Postmark (http://postmarkapp.com/)? Let somebody else worry about throttling and blacklists and all of the headaches of smtp servers. Matt On May 26, 10:50 pm, Jason Brower encomp...@gmail.com wrote: Yes, I practically have that now. The issue is how do I create the cron task and script to execute it? One way I am taking this further is, as long as the conference is alive I can compair this list with who has signed into the conference to get an idea of how many people have reacted to the email and are now attending the conference. Like an RSVP list so to say. :) There is a lot of information actually, that I think I can gather from this. BR, Jason Brower On 05/27/2011 04:11 AM, ron_m wrote: A possible idea, each email insert into a table. When the cron job wakes up have it read X number of emails with the smallest ID value from the table and process them. Delete the row as each one is completed.
[web2py] Re: Create an email queing feature...
I'd also suggest SendGrid (200/day free, 10 cents for 1,000). It looks like you are now trying it as a background process. I've had better luck with cron. And since you only want to send every hour or so, you could set the cron to run hourly.
[web2py] Re: Create an email queing feature...
A possible idea, each email insert into a table. When the cron job wakes up have it read X number of emails with the smallest ID value from the table and process them. Delete the row as each one is completed.
Re: [web2py] Re: Create an email queing feature...
Yes, I practically have that now. The issue is how do I create the cron task and script to execute it? One way I am taking this further is, as long as the conference is alive I can compair this list with who has signed into the conference to get an idea of how many people have reacted to the email and are now attending the conference. Like an RSVP list so to say. :) There is a lot of information actually, that I think I can gather from this. BR, Jason Brower On 05/27/2011 04:11 AM, ron_m wrote: A possible idea, each email insert into a table. When the cron job wakes up have it read X number of emails with the smallest ID value from the table and process them. Delete the row as each one is completed.