[nycphp-talk] email system for website
ajai at bitblit.net
Sun Jan 3 17:24:14 EST 2010
On Sun, 3 Jan 2010, Matt Juszczak wrote:
> > This is a good suggestion, I'd also recommend logging the email text
> > (database or text log) and putting some kind of sanity check on the
> > number of emails your app is sending out at any time.
> What you are both suggesting makes sense, but correct me if I'm wrong, it
> duplicates email functionality. Our front ends are programmed in two
> different languages (forgot to mention that), so if I keep the active
> emails in the front end web code, I have to write the code twice, plus I
> have to code backend functionality to allow passive emails to go out (an
> example of a passive email: someone posts a reply to a thread, and I want
> to alert all of the users who are subscribed to that thread that there's a
> new message - too much to put in the code I would think, as there could be
> 1000's of subscribers).
Of course, you would send out the emails in batches right? If you're using
an MTA to do the heavy lifting (and you probably should be), then queuing
emails via a batch process is better.
More information about the talk