Last time I checked, GoDaddy had no issues, other than I may have to pay a little more for the extra use of there servers.
Anyway, moving forward.
There are two ways you can prevent others from seeing all the email addresses. One would be to send an individual email for each subscribed user but that can be very inefficient. Especially if you have many users subscribed to a thread. The second option would be to put all the subscribers' emails in the BCC field instead of the standard TO field.
After I made my post, I came up with this solution in pseudo-code only...
- Casts the arguments to Integer
- Runs a Prepared Statement to check if the articleID is found
- Runs a Prepared Statement to check if the memberID is found
- If arguments are found...
- Runs a Prepared Statement to find all Members in the "subscription" table
- Retrieve records
(The part I wasn't sure about...)
- Loop through each record (Email) in the recordset
- Send an e-mail to each email like this...
Re: New Comment to "Postage Meters can save you Money"
For the article "Postage Meters Can Save You Money", the member, "luvTheOutdoors123", has posted a new comment.
To view the article click here.
To view the comment go here.
Doing that would mean ONE E-mail for ONE Member, so I wouldn't have to worry about spilling my entire Subscription List to others.
I suppose that if my website was a successful as SitePoint, then that might require a dedicated E-mail Server, but I think that is a ways down the road considering my static v1.0 website gets maybe 15 visitors per week!!!
As for getting the list of subscribed users ... one good option may be to have a separate "subscribed threads" table with a column for the user, and a column for the thread. That way you can simply do a SELECT for all users subscribed to "the thread that was just updated", and feed the list of emails into your code that builds/sends the email.
Yep, I already built that.
It looks like this...
You probably don't have to worry much about email limits being on a VPS, but you still may want to think about email queueing/throttling, if for any reason for performance. Especially if there's a potential for a lot of subscribers, and/or a lot of thread updates.
What do you mean by "E-mail Queuing" and "E-mail Throttling"? :-/