Self-Hosted, Full Featured, Email Mailing List Manager. Announcement + Discussion Lists, Web-based Installer, Installs with minimal dependencies, sendmail/SMTP/Amazon SES supported
This version of Dada Mail includes experimental support for the Mailgun API, along with a few bug fixes.
Mailgun is a third party email sending service, like Amazon SES. For an overview of third party email sending services, see:
https://dadamailproject.com/d/third_party_email_services.pod.html
Additional information on Mailgun support:
https://dadamailproject.com/d/features-mailgun_support.pod.html
https://github.com/justingit/dada-mail/issues/1171
This version of Dada Mail is a feature release, with a few bug fixes.
Search for message archives has been added to the admin view of the archives in the list control panel.
https://github.com/justingit/dada-mail/issues/1127
Pagination has been added to the user view of messages archives, including search. Along with pagination being a nice-to-have feature, since search results were not pagination in past versions, queries could have been returned with an incredible amount of search results to be shown on the single screen. This realistically could have been a detriment to server performance if too many search queries were returned in a small amount of time.
Pagination has also been added to the admin view of the messag archives in the list control panel, including search.
It seemed a good idea to protect the use of reconfiguring the entire app through this plugin by further protecting the form that allows you to do so with a CAPTCHA. This is now the case.
https://github.com/justingit/dada-mail/issues/1155
The login forms are protected by a simple CSRF-like scheme. The backend using a DB File, rather than having the information needed for the protection saved in the SQL backend. In rare circumstances, the prerequisits to use these DB Files can be unavailable on the account.
This version changes this to have that info saved in a SQL table, and removes the need to use the DB Files.
Using the new backend should be transparent to the user - nothing extra is required. There will be a new table in the database named, dada_simple_auth_str
.
https://github.com/justingit/dada-mail/issues/1161
https://github.com/justingit/dada-mail/issues/1162
https://github.com/justingit/dada-mail/issues/1163
https://github.com/justingit/dada-mail/issues/1164
https://github.com/justingit/dada-mail/issues/1165
This version of Dada Mail is a minor bug release.
https://github.com/justingit/dada-mail/issues/1147
https://github.com/justingit/dada-mail/issues/1132
https://github.com/justingit/dada-mail/issues/1153
https://github.com/justingit/dada-mail/issues/1149
https://github.com/justingit/dada-mail/issues/1151
https://github.com/justingit/dada-mail/issues/1136
https://github.com/justingit/dada-mail/issues/1138
https://github.com/justingit/dada-mail/issues/1154
This version of Dada Mail is a minor bug release.
Of note is a nasty bug in the Bridge plugin that affected some messages that are sent to it. These messages would fail to be sent, and a line in your error log may be found,
parse_data: unable to open in-memory file handle at...
See the following issue:
https://github.com/justingit/dada-mail/issues/1135
https://github.com/justingit/dada-mail/issues/1139
https://github.com/justingit/dada-mail/issues/1140
https://github.com/justingit/dada-mail/issues/1135
https://github.com/justingit/dada-mail/issues/1130
This version of Dada Mail is a major feature release.
In past versions, the only person who could build a working copy of Dada Mail that can be distributed was the main developer (me!), as many different parts of the app lived only on my own Macbook, which are added using a local build script. As development continued, more additional parts were needed to make a working package/distribution of Dada Mail, making this problem worse over time.
This hampers development of others, as no one else can check out Dada Mail and start developing. It has been my goal to remediate this problem. v11.19.0 solved a very large blocker on this, by decoupling the Perl Library bundled with Dada Mail from the main dada-mail distribution.
Starting with Dada Mail v11.20.0, all the needed parts to build Dada Mail are now available on Github, along with the build script. This allows you to build a fully working version of Dada Mail and thus allow you to fork the main Dada Mail repo, as well as any of these other parts to do whatever you'd like. Happy hacking!
See the README on the Dada Mail github for information on how to build Dada Mail:
https://github.com/justingit/dada-mail
as well as the source of the build script,
https://github.com/justingit/dada-mail/blob/main/make_distro.pl
as well as the new doc on how to build Dada Mail from source,
https://dadamailproject.com/d/building_dada_mail_from_source.pod.html
You can now see any bounced message reports have been created for a member, on their own screen, rather than having to search for them on the Bounce Scorecord, or via the Log Viewer.
Screens accessed by unsubscription links in mailing list messages that are followed ("clicked") less than 5 minutes after the message are sent will have their JavaScript disabled. The short time between message sent to unsubsription link clicked is usually a sign that a human is not doing the clicking, and such behavior causes false unsubscribes, which makes list owners pretty sad. The software that is following the link seems to also understand JavaScript, which is why we're disabling it. From my research, this is mostly those who use Outlook 365 with Advanced Threat Protection seems to be the biggest culprit.
This blog post does a good job explaining the problem, and offering a solution, which I've essentially adopted,
https://blog.healthchecks.io/2019/12/preventing-office-365-atp-from-clicking-unsubscribe-links/
The arms race to stop link pre-fetching continues.
This is what Debug Trace Options are:
https://dadamailproject.com/d/install_dada_mail-advanced_configuration.pod.html#Configure-Debugging
A small change/bugfix, but this may help those trying to figure out strange database connection problems, so it's a win.
I've decided to stop shipping with KCFinder. There are some open XSS security vulnerabilkities in the app and Rich Filemanager which is also shipped seems to have more features/is more secure.
If you were using KCFinder, Rich Filemanager will be selected for you by default.
Core 5 Filemanager is still bundled with Dada Mail, and the backend has been updated (by me).
This version of Dada Mail is a major feature release.
In past versions, the only person who could build a working copy of Dada Mail that can be distributed was the main developer (me!), as many different parts of the app lived only on my own Macbook, which are added using a local build script. As development continued, more additional parts were needed to make a working package/distribution of Dada Mail, making this problem worse over time.
This hampers development of others, as no one else can check out Dada Mail and start developing. It has been my goal to remediate this problem. v11.19.0 solved a very large blocker on this, by decoupling the Perl Library bundled with Dada Mail from the main dada-mail distribution.
Starting with Dada Mail v11.20.0, all the needed parts to build Dada Mail are now available on Github, along with the build script. This allows you to build a fully working version of Dada Mail and thus allow you to fork the main Dada Mail repo, as well as any of these other parts to do whatever you'd like. Happy hacking!
See the README on the Dada Mail github for information on how to build Dada Mail:
https://github.com/justingit/dada-mail/tree/features-build_script#readme
as well as the source of the build script,
https://github.com/justingit/dada-mail/blob/features-build_script/make_distro.pl
You can now see any bounced message reports have been created for a member, on their own screen, rather than having to search for them on the Bounce Scorecord, or via the Log Viewer.
Screens accessed by unsubscription links in mailing list messages that are followed ("clicked") less than 5 minutes after the message are sent will have their JavaScript disabled. The short time between message sent to unsubsription link clicked is usually a sign that a human is not doing the clicking, and such behavior causes false unsubscribes, which makes list owners pretty sad. The software that is following the link seems to also understand JavaScript, which is why we're disabling it. From my research, this is mostly those who use Outlook 365 with Advanced Threat Protection seems to be the biggest culprit.
This blog post does a good job explaining the problem, and offering a solution, which I've essentially adopted,
https://blog.healthchecks.io/2019/12/preventing-office-365-atp-from-clicking-unsubscribe-links/
The arms race to stop link pre-fetching continues.
DADA::App::HTMLtoMIMEMessage added to Debug Trace Options
This is what Debug Trace Options are:
https://dadamailproject.com/d/install_dada_mail-advanced_configuration.pod.html#Configure-Debugging
Better error reporting for problems with database connections
A small change/bugfix, but this may help those trying to figure out strange database connection problems, so it's a win.
I've decided to stop shipping with KCFinder. There are some open XSS security vulnerabilkities in the app and Rich Filemanager which is also shipped seems to have more features/is more secure.
If you were using KCFinder, Rich Filemanager will be selected for you by default.
Core 5 Filemanager is still bundled with Dada Mail, and the backend has been updated (by me).
This is the v11.19.0 release of Dada Mail! Download the binary.
https://dadamailproject.com/d/install_dada_mail.pod.html
https://sourceforge.net/projects/dadamail/files/dada-11_19_0.tar.gz/download