I'm heading up to my 14th year of developing the application. It's currently free to download from its own support site as well as from various installer services that have popped up in the last few years (Mojo Marketplace, Installatron, Softaculous, etc) Follow along with the project on Twitter, or hey - we have a mailing list too!
There's lots of things a like about working on it, but the application has become quite monolithic, and a little less flexible in its underlying code, than I'd like. In the next few months, I'm hoping to alleviate that, without falling into the problem of totally rewriting the app (it would be almost impossible to do so, with a one-dude team).
My initial idea is to move from basically no framework, to working with CGI::Application. That should help me gain some sort of framework, and a way to break the overgrowth of parts of this app, into more manageable pieces. It'll also hopefully give me a bridge to be able to have Dada Mail run as a CGI script (how people are used to running Dada Mail), as well as a PSGI app (a great alternative, that has a TON of benefits, one being SPEED!).
From there, we'll see how it works, but it may be time to move on to some more whiz-bang things that a framework like Mojolicious would provide. The bummer with trying to move to Mojolicious is that the Perl version required is rarely met on the shared hosting accounts that the majority of people who run Dada Mail are on. Saying, "hey, just install perlbrew!" is a far cry on what lots of people are capable of. They're used to a one-click install. Sigh.
Maybe cPanel, being a Perl-based shop, knows of a better way to have available a more up-to-date Perl version? A how-to, so not to fudge this up, would be super-helpful and somewhat break huge shackles from those that ship apps for this types of hosting situations. (maybe you know?)
Without further ado, here's the changelog from this last release:
- Sending Error Detection and Reporting
- Redesigned Membership Admin Screen
- New RESTful API for Subscriptions
Dada Mail is now tuned to catch addresses causing problems and perform some intelligent tasks:
After this wait, Dada Mail will start its mass mailing process at the address that was having the delivery problems and try for another round of three more times - just to make sure. If this is successful, great! Business as usual. If the address fails in sending, the address is logged, and skipped over and the next address is then sent to.
Now that you know this information, you can then take some action to fix it. The majority of problems on cheap, shared hosting platforms are related to mass mailing speed: you're sending too fast.
This is also the eaisest types of problem sto fix, as Dada Mail supports changing how fast a mass mailing goes out, through it's batch sending system. For more complicated problems, you can then look in Dada Mail's error logs for more details - Dada Mail's Log Viewer plugin also makes this easy.
Sending Errors are also reported in the right-hand table, under, Sending Errors as both the total number of Sending Errors, and the percentage compared to how many addresses were sent to.
But, Dada Mail has other sublists that provide different roles. For example, Dada Mail's Black List allows you to have a list of addresses that aren't allowed to join your list. This is also known as a, Suppression List
The, Authorized Senders sublist is a list of addresses that are allowed to send out a message from their own mail reader, without having to log into Dada Mail, that then gets delivered to your Subscribers (this is done with the Bridge plugin, which is bundled with Dada Mail)
The Membership tab allows you to Add/Update/Remove addresses across these sublists. If you're logged into a mailing list with the Dada Mail Root Password, you'll also be able to do all things things, across all your mailing lists.
Dada Mail is smart when allowing you to work with the addresses that make up your mailing list, as these addresses are the most valuable asset of the whole system. Checks are done to make sure you're not going to mess up subscriptions, and all these functions only happen after Dada Mail validates your request and you confirm the changes.
Listed in the Membership tab will be all the sublists an individual email address is a member of, for the Mailing List you're currently logged into. Be aware that one address may be a member of multiple sublists.
For example, an address may be both a Subscriber (Subscribers receive mass mailings sent to the mailing list), an Authorized Sender (Authorized Senders are able to send messages via Bridge, as well as moderate messages sent via Bridge to a mailing list set up as a discussion list), as well as being on the White List (Only White Listed members are allowed to subscribe to a mailing list).
An address could also be simply on the Black List, with no permission to be a member of your Subscribers, until they're first removed from the Black List and added to the Subscribers sublist.
If an address is currently on the Subscription Requests sublist, they will be awaiting approval from the List Owner to join the Subscribers sublist. You may Approve or Deny this request on this screen as well.
This information can also be exported in a .csv format, to be opened and worked with, in any application that understand this format - things like Excel or other spreadsheet applications.
If you have logged into your mailing list with the Dada Mail Root Password, you may view the history for the mailing list you're currently logged into, as well as all mailing lists - the latter can also be exported to .csv format.
Like the Subscriber History, this data can also be exported in .csv format, to be opened up in an outside application. Data that's exported includes the data and time of the activity, what type of activity this was, if it was a clickthrough, what URL was clicked through, the message id of the message, as well as the IP address the subscriber was coming from.
These fields can be edited by the user themselves, as well as in this tab. You may also change the password used by your user to access their own information.
Earlier REST and SOAP experimental client/server scripts, located in the dada/extras/scripts/subscribe have now been removed. For this new RESTful interface, no additional scripts are needed to be installed.
email@example.com parts of email addresses, like this:
@example.comIt wasn't entirely clear what was meant by, "part" of an address, so this has been clarified:
The part of an email address must include the, @ symbol, to remove the ambiguity of if you want to Black List the user or domain part of the address and something like this doesn't happen:
firstname.lastname@example.orgSo the following are now not valid Black List (or White List) entries:
example.comIf you do have entries like this in your current Black List/White List, they simply won't do much of anything.
It's still suggested to install the JSON Perl module yourself to get the XS-version for speed, either manually, or using cpan/cpanmin
The, Using Tracker chapter has also been updated to reflect the new features in this released (logging and reporting Sending Errors)
The, Mailing Sending - Options screen has also been updated to reflect the current options available.
If a subscriber was a member of one mailing list, and was then subscribed to another mailing list, any saved Profile Fields tied to that address would be lost - even if that new subscription didn't have any new Profile Fields passed to Dada Mail.
This behavior has now changed:
If an address, that has saved Profile Field information, and is subscribed to a mailing list, that original information will now be preserved. If an address is subscribed, but had no profile field information saved, any new information would then be saved.
It's unclear yet what to do with a subscriber, that has saved Profile Field information that's subscribed to another mailing list, along with new Profile Field information - should the new information be used instead? Should the old information be kept? Shoudl some sort of sophisticated folding of data happen? Should it be a pref. somewhere? (per mass import, in the list control panel?)
We're not sure yet, but we encourage feedback.
uncompress_dada.cgiis kept intentionally simple, so as to be super-quick to download, and easy to read along, if little niggling changes need to be made for your environment. We've changed a few things to make things more flexible:
Some people moving from Basic Dada Mail, to Pro Dada mail noticed that if BOTH the
pro_dada-6_x_ydistro are present in your installing directory, the
dada-6_x_y.tar.gzwill be used, causing confusion.
uncompress_dada.cgiwill now explicitly look for the
""Welcome" Message to Addresses Subscribed in the List Control Panel" does not provide unsub link, warning in the list control panelhttps://github.com/justingit/dada-mail/issues/395