I once set something up with this kind of functionality. Simplified
concept was:
1. Two tables, e.g.:
Messages: subject, body
MessQueue: to_id, from_id, message_id, dest, stat, sent_on
note: dest is either an email address or mobile tel no.
2. A message is created and multiple
Instead of using a database table as an intermediary you should take a
look at using an actual message queue. I'm personally using
BeanstalkD with the BeanstalkC python module.
When a new message is created, you could create a bit of JSON that
contains the message and the list of recipients.
I don't have a whole lot of help for you but it does seem that at some
point, this type of application demands asynchronous processing.
I had modest luck with the Background Process outlined here but eventually
switched to per minute cron jobs:
3 matches
Mail list logo
