Hi, thanks for all the input Ryan.
Yes it doesn’t support any fancy queueing support right now. That’s the reason why the versio number still 0.2,

It’s not full fledged newsletter system yet. I’m looking forward for more support on this part. The queueing part, I might added in the future releases, so everytime it send out an email, it will write a log to itself, and by the time the time out happened, it will continue sending the newsletter from the last list that are not being sent out.
As far as using mmbercheck snippet, I think everything is being supported built in. The reason to that, because the anchor and the newsletter admin need the same permission, so there is no point in differentiating the auth. I also need to have the ability to allow both super, manager, and web user, which I have my little API being included with it.
Regading about the {++}, I just don’t want to messed up with built in placeholder from MODx. In case if there is another snippet assigning the same placeholder name, and usually it will cause some problem. It’s just a special tag that I use for all my snippet. I will still use placeholder for its own usefulness, like the the newslisting snippet did its job.
As far as the effectiveness of the code. I’m not to for sure about the count(array()), but as far as I know, PHP has their own way to optimize the array counting, instead of going through the array in one loop to count it, but they have their own memory to remember the current array capacity. I might be wrong, so correct me.
The array_flip is the most resource usage function, but I need that to ensure that there is no duplication in the emails list.
I also want to add more functionality to this system. Any inputs/suggestions are welcomed.
Thanks Ryan for pointing that out.