I think this is one of the better mailing modules availbale for Drupal. It is simple to use, and really quite powerful, but, IMO I think it should support support mailing groups.
An example of this is the mass mailer module.
I understand that this module is in its infancy (just released today, and not yet avaiable for download on the projects pages), but I think it would be a great improvement.
I don't mean to nag, but I am taking a great interest in this project.
Comments
Comment #1
DriesK commentedI totally agree. Actually, this feature is somewhere at the top of my (quite long) todo-list, together with an option to send and edit a welcome email upon subscription, a 'search subscriber' function,...
All other thoughts and suggestions are very welcome!
Comment #2
Boris Mann _Temporary Gmail Account_ commentedI'm not sure what is meant by "mailing groups". This seems like it should stay the simple module it was designed for -- anyone that is subscribed gets sent the newsletter, those who aren't can still see it on the website and/or read it via RSS.
The mass mailer module is there for people that want more power.
DriesK: you should add some of your thoughts as feature requests so that other people can see what you're thinking.
Comment #3
dries commentedNathan: what do you mean with "mailing groups"? Do you mean multiple mailing lists people can subscribe to? Mind to elaborate on this? Looks like Boris is confused too.
Comment #4
DriesK commentedI interpreted the use of "mailing groups" as being able to subscribe to separate newsletters. So using the built-in "add type" option (which just uses the taxonomy system to create a new term), you can create newsletter types among which subscribers can choose to subscribe to.
When the newsletter is then sent, it is only sent to those people that subscribed to that specific newsletter type. This is what Boris suggested in this issue. This is obviously not implemented yet, but that's what I was planning to do.
On the other hand, "mailing groups" in the meaning of having several admin-defined mailing groups (such as an "admin list", a "site maintainer list",....; either created and edited manually or based on the roles as defined by user.module), an then being able to select one or more groups to which the newsletter has to be sent, well, that was not the goal of this module. In my opinion, Simplenews should be kept as simple as possible, and indeed other modules are available for more demanding users.
Comment #5
nathanwastaken commentedHello Guys,
Sorry for the late reply, I have been away (in the snow) for the past week.
To clarify what I mean by mailing groups: Like the mass mailer module, I would like to be able to create multiple lists and independently maintain the subscriptions to each mailing list (group). They could be assigned as public, in which users (both registered and anon. would be able to subscribe) and private (in which admins would add/ subscribe people to the lists).
For my purposes, the subscribe and send to all just is not practicle.
For example, I have many contacts for the one client (A). They all need to be 'kept in the loop', so they should all receive a copy of all emails sent to that client (that client has a list/ group/ role asigned to them... call it what you will). I would add the contacts to that list.
I have another client (B), again, with many contacts. I want to create another list, with ONLY these people subscribed. I also only want to send emails to this client (client B), but I don't want any of the people at (A) to see them.
What I am trying to say (not to clearly I think) is that we should borrow the mulitiple list support from Mass Mailer (not the code, the concept), and apply it to the simple news module.
I understand that it is SIMPLE NEWS, and should be kept neat and simple, but, I think it is the easiest of all the mailing modules. It does not require any third party applications (phpList), and utilises cron.
The structure is here, and I would like to see it expanded. Even if this functionality is included, just NOT activated by default. Admins could then turn the additional features on. This way, only the advanced features would be used by the ADVANCED users.
Feedback would be much appreciated.
Sorry for any confusion.
Comment #6
DriesK commentedPlease post any further comments in this issue.