This release of Dada Mail includes fixes for bugs found in the 4.9.0 version of Dada Mail, plus support for the Amazon SES SMTP Interface.
You can learn more about Amazon's SES SMTP Interface here:
http://docs.amazonwebservices.com/ses/latest/DeveloperGuide/SMTP.html
Dada Mail can now be configured to use Amazon's SES SMTP Interface, as well as working with the Amazon SES API - whichever you prefer. See the Amazon SES docs for more information:
http://dadamailproject.com/d/features-amazon_ses_support.pod.html
https://github.com/justingit/dada-mail/issues/246
https://github.com/justingit/dada-mail/issues/245
https://github.com/justingit/dada-mail/issues/244
https://github.com/justingit/dada-mail/issues/243
https://github.com/justingit/dada-mail/issues/242
https://github.com/justingit/dada-mail/issues/241
This release focuses on many parts of Dada Mail to optimize performance. Benefits of all this work include faster mass sending speeds. Potentially must faster.
The Bounce Handler (Known in the past as, "Mystery Girl") has been renamed to simply, Bounce Handler. I don't very much listen to the Yeah Yeah Yeahs anymore.
The config variable $PLUGIN_CONFIGS also referred to this plugin as, "Mystery_Girl" - as in this code snippet:
$PLUGIN_CONFIGS = {
Myster_Girl => {
Server => undef,
Username => undef,
Password => undef,
# ...etc
This has also been change to simply, Bounce_Handler:
$PLUGIN_CONFIGS = {
Bounce_Handler => {
Server => undef,
Username => undef,
Password => undef,
# ...etc
Bounce Handler preferences, including the Soft Bounce Score, Hard Bounce Score and Score Threshold are now set per mailing list, instead of having to be set in the global config.
Bounce Scores can now, decay, or be reduced every time a mass mailing is sent out. This is to help minimize scores from email addresses that temporarily have had problems with delivery, but are otherwise valid email addresses. An email address's bounce score will also now be automatically removed, if the score goes at or below, 0.
The Bounce Scorecard is now presented on the default screen for the bounce handler, instead of being shown on a separate screen. Navigating the scorecard is now a little more intuitive, as well.
Bounce messages can now be forwarded to the List Owner, once the Bounce Handler has reviewed the message.
Dada Mail/Bounce Handler should now have support for Amazon SES sending. This is still marked as, Experimental (as is SES support in total), but SES-specific rules have been whipped up. Please give us feedback!
HTML::Template::Pro renders the templates that Dada Mail uses throughout the app,
including HTML screens and custom email messages, much faster than what's included
with Dada Mail (HTML::Template). HTML::Template::Pro will need to be installed separately.
See the features doc on HTML::Template::Pro for more information:
features-html_template_pro.pod.html
Dada Mail now uses a persistent HTTP connection when talking with Amazon SES. This can speed up sending by .3 - .7 seconds/message.
Dada Mail now has support for various simple Date and Time formats to use in HTML and Email templates,
as well support for more flexible/advanced strftime formats:
features-email_template_syntax.pod#date_related_tags
This script allows you to import archive data from the backup of a DB File, to the SQL backend. This helps if your DB Files are corrupted/incompatible with your current server environment.
A new/update entry in the General FAQ, Tuning Dada Mail to Send Mass Mailings Faster:
FAQ-general.pod.html#tuning_dada_mail_to_send_mass_mailings_faster
The LWP group of Perl modules is no longer available with Dada Mail. LWP is used for
such things as, Send a Webpage and some web services, like Amazon SES. You
will have to install LWP yourself. Most shared hosting companies will have this already installed,
for you.
This upgrade to MIME::Tools has a very positive improvement on sending speed.
https://github.com/justingit/dada-mail/issues/240
This release consists of fixes for issues found in the 4.8.3 release.
Of large note is a big memory leak found and fixed in v4.8.4 that happens whenever you mass mail an HTML email message, regardless of how it was first created.
This memory leak could grow to many 100's of megabytes to gigabytes of memory within a few thousand messages sent and could potentially kill off the sending process and more likely than not, slow down mass mailing by ~10% (potentially much greater, depending on how large the amount of RAM is consumed).
For more information, see this issue:
https://github.com/justingit/dada-mail/issues/236
https://github.com/justingit/dada-mail/issues/229
https://github.com/justingit/dada-mail/issues/230
https://github.com/justingit/dada-mail/issues/231
https://github.com/justingit/dada-mail/issues/232
https://github.com/justingit/dada-mail/issues/234
https://github.com/justingit/dada-mail/issues/234
https://github.com/justingit/dada-mail/issues/235
https://github.com/justingit/dada-mail/issues/236
https://github.com/justingit/dada-mail/issues/237
https://github.com/justingit/dada-mail/issues/239
This release consists of fixes for issues found in the 4.8.2 release.
https://github.com/justingit/dada-mail/issues/226
https://github.com/justingit/dada-mail/issues/225
https://github.com/justingit/dada-mail/issues/173
https://github.com/justingit/dada-mail/issues/224
This release consists of fixes for issues found in the 4.8.1 release.
https://github.com/justingit/dada-mail/issues/219
https://github.com/justingit/dada-mail/issues/221
https://github.com/justingit/dada-mail/issues/222
https://github.com/justingit/dada-mail/issues/223
https://github.com/justingit/dada-mail/issues/227
This release consists of fixes for issues found in the 4.8.0 release.
https://github.com/justingit/dada-mail/issues/213
https://github.com/justingit/dada-mail/issues/215
https://github.com/justingit/dada-mail/issues/216
https://github.com/justingit/dada-mail/issues/217
https://github.com/justingit/dada-mail/issues/218
The following email messages that used to be embedded in the source of Dada Bridge are now saved in the Dada Mail global config and can now be edited in the list control panel of Dada Bridge:
Documentation on the CAPTCHA for Dada Mail has been moved out of the Config.pm docs and expanded.
They're now located at:
http://dadamailproject.com/d/features-CAPTCHA.pod.html
This the addition of docs for reCAPTCHA Mailhide, including how to install the missing CPAN Module needed, via a cPanel setup.
The HTML::Scrubber CPAN module is used in Dada Mail to remove potentially insecure
JavaScripts from email messages. This is particularily important for discussion lists
where messages are coming from a potentially untrusted source.
More information on HTML::Scrubber:
http://search.cpan.org/dist/HTML-Scrubber/
Parameters for HTML::Scrubber are also now saved by default in the Config.pm
file and can be overridden and customized in your own .dada_config file. Look for the
config variable named, $HTML_SCRUBBER_OPTIONS.
https://github.com/justingit/dada-mail/issues/202
https://github.com/justingit/dada-mail/issues/203
https://github.com/justingit/dada-mail/issues/204
https://github.com/justingit/dada-mail/issues/206
https://github.com/justingit/dada-mail/issues/207
https://github.com/justingit/dada-mail/issues/208
https://github.com/justingit/dada-mail/issues/209
https://github.com/justingit/dada-mail/issues/210
https://github.com/justingit/dada-mail/issues/211
https://github.com/justingit/dada-mail/issues/212
This release has a small bug fix from v4.7.1, but is really to fix the problem with the 4.7.1 release, namely the download link is not working on Github.
https://github.com/justingit/dada-mail/issues/205
See Issue #205
This release is a bug fix-only release of bugs found in the 4.7.0 release.
https://github.com/justingit/dada-mail/issues/189
https://github.com/justingit/dada-mail/issues/193
https://github.com/justingit/dada-mail/issues/191
https://github.com/justingit/dada-mail/issues/190
https://github.com/justingit/dada-mail/issues/198
https://github.com/justingit/dada-mail/issues/197
https://github.com/justingit/dada-mail/issues/195
https://github.com/justingit/dada-mail/issues/188
https://github.com/justingit/dada-mail/issues/187
https://github.com/justingit/dada-mail/issues/199
https://github.com/justingit/dada-mail/issues/201
https://github.com/justingit/dada-mail/issues/200
This release of Dada Mail provides additional tools to help you manage your mailing list through the list control panel.
With this version, you now have the ability to:
Tracker Reports are available right in the mailing monitor of mass mailings to your subscribers and updated while your mass mailing goes out.
Enable this option in the Tracker plugin, the option is labeled, Show Message Reports in Mailing Monitor
Mailing Lists can now be truly, Invitation-Only. The list owner of a mailing list must send out an Invitation Message from the list control panel and individuals may not self-subscribe.
Mass subscriptions in the list control panel (if this option is enabled) can automatically be followed up with a, "Welcome" message sent to only the new subscribers.
This welcome message can be customized in the list control panel in the, Appearance and Templates - Email Message Templates screen under, "Welcome" Message to Addresses Subscribed in the List Control Panel
As well as sending out a Welcome Message, you may now send out the newest archived message to just the subscribers that were newly added.
Mass unsubscriptions in the list control panel can automatically be followed up with a, "Farewell" message sent to only addresses that have just been removed.
This Farewell Message can be customized in the list control panel in the, Appearance and Templates - Email Message Templates screen under, "Farewell" Message to Addresses Unsubscribed in the List Control Panel
The Tracker plugin now has the ability to log every time the, "Forward to a Friend" form is used. Enabled by default.
Individual message reports will show the total number of times "Forward to a Friend" was used, as well as usage over time and by geography.
The Tracker plugin now has the ability to log every time an archived message is viewed. Enabled by default.
Individual message reports will show the total number of times an archived message was viewed, as well as views over time and by geography.
The option, Enable, "Subscribe Checked Subscribers" button in the, Manage Subscribers - Invite/Add -> Verify screen > was not removed, but was moved to, Your Mailing List - Mailing List Options under, List Control Panel Subscriptions. The option has been relabled, Enable Adding Subscribers from within the List Control Panel
"Closed" lists are now truly closed, meaning that now subscriptions may be made either by a individual, or in the list control panel.
The behavior you may want instead, if you were running a closed list, is an, "Invitation-Only" list.
The, Send the Newest Archived Message to All New Subscribers. option has been moved from, Message Archives - Archive Options to, Your Mailing List - Mailing List Options under, Subscriptions
https://github.com/justingit/dada-mail/issues/183
https://github.com/justingit/dada-mail/issues/184
https://github.com/justingit/dada-mail/issues/185
https://github.com/justingit/dada-mail/issues/185
https://github.com/justingit/dada-mail/issues/186
This a purely bug fix release, with most of the bugs fixed for the Dada Bridge plugin, to stop potential infinite loops from occuring.
https://github.com/justingit/dada-mail/issues/174
https://github.com/justingit/dada-mail/issues/175
https://github.com/justingit/dada-mail/issues/176
https://github.com/justingit/dada-mail/issues/177
https://github.com/justingit/dada-mail/issues/178
https://github.com/justingit/dada-mail/issues/179
https://github.com/justingit/dada-mail/issues/180
https://github.com/justingit/dada-mail/issues/181
v4.6.0 includes experimental subprojects, like Amazon SES support and unsubscribe tag/link flexibility, as well as updates and refinements to the default mailing list message templates, social bookmarking links, forward to a friend functionality, as well as a new plugin called, Mailing Monitor
Amazon SES allows you to send email messages with Dada Mail using the Amazon SES Web Service. This service could potentially allow someone running a website with a small mailing quota send out mass mailings to a very large list, utilizing Amazon's services.
This feature is currently labeled, Experimental. We need feedback. We want to make the feature better. Give us feedback!
http://dadamailproject.com/d/features-amazon_ses_support.pod.html
It's now possible to place a, "Forward to a Friend" link into your mailing list messages.
The Forward to a Friend form is available to both subscribers as well as visitors to your mailing list archives.
http://dadamailproject.com/d/features_forward_to_a_friend.pod.html
You can now change the behavior of what Dada Mail does, after a user clicks the Unsubscriber Link.
The second option is hoped to thwart absent-minded clicks, as well as auto link prefetching.
This feature is currently labeled, Experimental. We need feedback. We want to make the feature better. Give us feedback!
The, Mailing Monitor plugin replaces the, auto_pickup.pl extension.
Compared to the old extension, the Mailing Monitor plugin has a nicer list control panel interface and much more simplified instructions.
The auto_pickup.pl extension will still be shipped with Dada Mail, but will simply be a redirect to this new plugin.
http://dadamailproject.com/d/mailing_monitor.cgi.html
The installer that comes with Dada Mail now supports the installation of most of the plugins and extensions that come with Dada Mail.
The installer also gives you the option, when used to upgrade your current Dada Mail, to either keep your current .dada_config file, or to create a new .dada_config file, while also keeping your current .dada_files directory structure and contents.
http://dadamailproject.com/d/install_dada_mail.pod.html
Default Mailing List Messages are now much less verbose and more useful, with already-included "Forward to a Friend" link and better design.
The Facebook link has been replaced by the Facebook, Like button and the, Plus Google button has been added.
The freshest GeoIP data has been included with Dada Mail.
Fresh as of 03-Aug-2011, fetched from:
http://geolite.maxmind.com/download/geoip/database/GeoLiteCountry/
https://github.com/justingit/dada-mail/issues/164
v4.5.2 fixes some small bugs found in v4.5.1 of Dada Mail, as well as adding additional capabilities to the Tracker Plugin
https://github.com/justingit/dada-mail/issues/169
v4.5.1 fixes some small bugs found in v4.5.0 of Dada Mail, mostly dealing with the Tracker plugin
https://github.com/justingit/dada-mail/issues/165
https://github.com/justingit/dada-mail/issues/166
https://github.com/justingit/dada-mail/issues/167
https://github.com/justingit/dada-mail/issues/168
Tracker is the heir to the once venerable but now quite rickety clickthrough_tracking.cgi plugin, rewritten to be better at everything clickthrough_tracking.cgi was supposed to be good at.
Tracker tracks the following Mass Mailing events:
Tracker also allows you to automatically track all the links in your mass mailing messages (instead of having to do everything manually) and provides very fancy charts/graphs of the information it compiles, for easy digestion.
See the Documenation for the Tracker plugin at:
http://dadamailproject.com/d/tracker.cgi.html
Replaced with the Tracker plugin, which is tons better.
Dada Mail ships with a limit of 3 (instead of 5) mailing lists and a limit of 10,000 subscribers (instead of 25,000) quotas by default. We encourage you to use Pro Dada, if you need more than that: http://dadamailproject.com/purchase/pro.html
https://github.com/justingit/dada-mail/issues/161
https://github.com/justingit/dada-mail/issues/160
https://github.com/justingit/dada-mail/issues/162
https://github.com/justingit/dada-mail/issues/163
v4.4.2 introduced stricter checking of the redirect tags, to make sure they look like URL's. This essentially broken any redirects that didn't start with, http://, https:// or ftp:// (there's a few others, as well)
One redirect that was being used by some users was a mailto:, like this:
mailto:user@example.com
or,
<a href="[redirect=mailto:user@example.com]">Email Us!</a>
Support for such redirects has be re-introduced.
In the, ajax_include_subscribe.cgi script, you had the choice of either creating a form that allows you to
show ALL lists available, or set a configuration variable within the script, to only show one list by default.
You may now set whichever list you would like the subscription form to use, via the, list query string paramater:
<script type="text/javascript" src="http://example.com/cgi-bin/dada/extensions/ajax_include_subscribe.cgi?list=mylist"></script> to show a subscription form for just that list. This works better than setting it within the extension, as you have the choice of making a specific subscription form, for any of your lists.
New documentation is now shipped to give guidance on how to move Dada Mail between hosting servers/accounts
The docs are readable here:
http://dadamailproject.com/d/move_dada_mail.pod.html
If you don't have any Subscribers/Addresses to show, the View List Screen no longer shows all that Stuff it usually shows.
In the List Control Panel, if you remove addresses from your mailing list, the number of addresses that are then black listed is now displayed, instead of just mysteriously being added.
You can now erase the Bounce Scorecard on a list-per-list basis in the list control panel.
https://github.com/justingit/dada-mail/issues/159
https://github.com/justingit/dada-mail/issues/157
https://github.com/justingit/dada-mail/issues/155
https://github.com/justingit/dada-mail/issues/156
https://github.com/justingit/dada-mail/issues/154
https://github.com/justingit/dada-mail/issues/142
https://github.com/justingit/dada-mail/issues/143
https://github.com/justingit/dada-mail/issues/146
https://github.com/justingit/dada-mail/issues/148
https://github.com/justingit/dada-mail/issues/150
https://github.com/justingit/dada-mail/issues/141
https://github.com/justingit/dada-mail/issues/140
https://github.com/justingit/dada-mail/issues/138
https://github.com/justingit/dada-mail/issues/151
https://github.com/justingit/dada-mail/issues/152
https://github.com/justingit/dada-mail/issues/153
https://github.com/justingit/dada-mail/issues/120
https://github.com/justingit/dada-mail/issues/123
https://github.com/justingit/dada-mail/issues/125
https://github.com/justingit/dada-mail/issues/127
https://github.com/justingit/dada-mail/issues/124
https://github.com/justingit/dada-mail/issues/134
https://github.com/justingit/dada-mail/issues/133
https://github.com/justingit/dada-mail/issues/130
https://github.com/justingit/dada-mail/issues/132
https://github.com/justingit/dada-mail/issues/131
https://github.com/justingit/dada-mail/issues/136
https://github.com/justingit/dada-mail/issues/137
https://github.com/justingit/dada-mail/issues/139
Previously, only v2 of SpamAssassin was supported.
https://github.com/justingit/dada-mail/issues/122
https://github.com/justingit/dada-mail/issues/121
https://github.com/justingit/dada-mail/issues/115
https://github.com/justingit/dada-mail/issues/119
In v4.3.0, Closed-Loop Opt-In Subscription model was applied in Dada Mail to mailing list by default
and by default you were not able to change these list settings to tailor it to your needs, without
first changing the config variable, $ENFORCE_CLOSED_LOOP_OPT_IN to, 0.
It was also noted that in future versions of Dada Mail, features that did not conform to Closed-Loop Opt In would be removed from Dada Mail.
The, $ENFORCE_CLOSED_LOOP_OPT_IN variable is now shipped with a value of, 0 by
default, making Dada Mail's behavior the same as pre-4.3.0 versions of Dada Mail.
We're also opening up the dialogue to all users of Dada Mail on how they see is the best way to balance power and versatility of Dada Mail, with accountability and adherence of the rules of a legitimate mailing list. We will put on hold the plan to deprecate these features, until we got more feedback from the users of Dada Mail. Please join the discussion:
http://dadamailproject.com/support/boards/viewtopic.php
Code cleanup has trimmed 500+ lines from the mail.cgi file. Many of the changes can be seen from
moving from the DADA::MailingList::Settings::save method to the, DADA::MailingList::Settings::save_w_params method
and from moving from the DADA::Templates::Widgets::screen sub to the DADA::Templates::Widgets::wrap_screen sub.
One problem when sending mass mailings - especially one using Dada Mail's templating system, is that you may make an error when using the template tags. This was a difficult error to even know about, since no reporting was made, if an error was found - Dada Mail would simply error out and your message would seem to be, "stuck" in the mass mailing queue, forever.
Now, many syntax errors should now be caught when sending a mass mailing, a webpage, or a list invitation.
Dada Bridge has simplified some of its options to make it more inline with other discussion mailing list apps, when it comes to discussion lists. You now have two choices:
* Have replies always be addressed to the mailing list (with an option to reply-all), or,
* Have replies addressed to the discussion list
The list will also be given back as a CSV file, so most likely, you'll get a little dialog box asking if you want to either open it in some application, or just download it.
You may still download your mailing list in csv format.
You can now download the entire log file, through the log viewer.
If you use the installer to upgrade Dada Mail (as it is noted you may do), old screen cache files will be removed, so that old information/templates won't be shown, with the newer version of Dada Mail.
There's initial support for what's called the, tmpl_set template tag, that basically allows you to set a variable within your template, to be used somewhere else within your template.
This is interesting when coupled with initial support with wrapping one template, with another.
In one way, Dada Mail already supports this - many template screens you see use either the default list template, or the default admin template and add content to another template inside it.
Internally, this was done in a very kludgey way and has now been cleaned up. There could be a potential for a 33% speedup for screen creation (which is nice)
What has also been cleaned up is a problem with the title of many HTML screens in Dada Mail being saved within the program files itself. You can now set the title of the HTML screen from within the template that gets wrapped. You'll see a line like this near the top of many of the templates:
<!-- tmpl_set name="title" value="I am a title!" -->
Since moving to this way of setting the title for HTML screens, many, many of the templates have been changed. If you've made custom changes to the templates, you will want to do a diff on your version, with the version that ships with Dada Mail.
Many instances of using a package called, CGI::Ajax (http://search.cpan.org/dist/CGI-Ajax/)
has been replaced to use prototype (http://www.prototypejs.org/)
The only place that CGI::Ajax is still being used is in the, ajax_include_subscribe.cgi extension - and we'll most likely remove it from there, soon as well.
The Mailing Monitor in the list control panel is now refreshed via AJAX, so that only a portion of the screen you see needs to be updated, instead of a refresh of the entire screen. This seems to make things appear much more snappy.
If there's an error with a subscription/unsubscription request, Dada Mail would
add a list of the errors it came across by passing them in query string with a paramater named, errors.
This name has been changed to, errors[] to help out php folk. This is tied to this bug:
https://github.com/justingit/dada-mail/issues#issue/109
Examples for initiating a subscription request have been updated and added to. Currently there are server/client examples in SOAP and REST. There's also a command line example. Profile Fields are now support for all clients and servers.
The example scripts can be found in the distro, at:
dada/extras/scripts/subscribe
Documentation can be found at:
dada/extras/documentation/pod_source/COOKBOOK-subscriptions.pod dada/extras/documentation/html_version/COOKBOOK-subscriptions.pod.html
If the email address you're using has a profile, its fields ("First Name", "Last Name", etc) will be used in test mass mailings, instead of not using any fields. This is also true if the list owner email has their own profile.
https://github.com/justingit/dada-mail/issues/closed#issue/113
There seems to be a few small problems with both the add/remove verification screens, if the information given is not formed correctly.
Among things that can cause problems: * Invalid comma separated values format * blank lines * blank lines, except for spaces * incorrect information - such as HTML. This HTML will then be viewed in the verification screens, without the HTML be escaped.
This causes a lot of problems with submitting addresses, as there isn't any notification, by Dada Mail that anything is wrong, except part of the screen having no information, what so ever.
https://github.com/justingit/dada-mail/issues/closed#issue/112
https://github.com/justingit/dada-mail/issues/issue/111
https://github.com/justingit/dada-mail/issues/issue/110
https://github.com/justingit/dada-mail/issues/issue/109
https://github.com/justingit/dada-mail/issues/issue/96
This release is a bugfix-only release:
https://github.com/justingit/dada-mail/issues/closed#issue/86
https://github.com/justingit/dada-mail/issues/closed#issue/108
There's some new documentation about upgrading from a Simple Scripts to a Regular Installation of Dada Mail:
http://dadamailproject.com/d/upgrade_from_simple_scripts.pod.html
Bugs were found in a few of the templates Dada Mail uses - the following templates have small changes in them:
Some SOAP proof of concept files have been included in, dada/extras/scripts/SOAP
They can be read at:
http://dadamailproject.com/d/README_SOAP.pod.html
They include a server written in Perl and clients written in Perl and php. They are also documented in the Subscription Cookbook
They are, in fact, Proof of Concepts and are not complete applications.
The mx_lookup.cgi plugin has been cleaned up and documentation added. It's currently listed as, DEPRECATED, but will not go away, until the functionality it has is brought into the core of the program. It's still a good example of how to make a simple Dada Mail plugin.
github user masktos (Mark Stosberg) was kind enough to refactor a ton code into Dada Mail, having to do with Modern Perl/Perl Best Practices coding. Thanks, Mark! Some of the things he worked on include,
foreach() to for()
https://github.com/justingit/dada-mail/issues/closed#issue/107
https://github.com/justingit/dada-mail/issues/closed#issue/106
https://github.com/justingit/dada-mail/issues/closed#issue/105
https://github.com/justingit/dada-mail/issues/closed#issue/104
https://github.com/justingit/dada-mail/issues/closed#issue/103
https://github.com/justingit/dada-mail/issues/closed#issue/102
https://github.com/justingit/dada-mail/issues/closed#issue/101
https://github.com/justingit/dada-mail/issues/closed#issue/100
https://github.com/justingit/dada-mail/issues/closed#issue/73
https://github.com/justingit/dada-mail/issues/closed#issue/90
https://github.com/justingit/dada-mail/issues/closed#issue/91
https://github.com/justingit/dada-mail/issues/closed#issue/93
https://github.com/justingit/dada-mail/issues/closed#issue/92
https://github.com/justingit/dada-mail/issues/closed#issue/97
https://github.com/justingit/dada-mail/issues/closed#issue/99
Installation instructions for 4.3.0 are the same as they were for 4.2.0.
Twitter turned off support for the, "Basic" authorization API they were using, in conjunction with oAuth (the new standard). oAuth isn't very compatible with Dada Mail, so we had to pull support for it.
The Habeas Watermark isn't really used, anymore, anyways.
It's now possible to either ignore messages seen as spam, or send a rejection message.
If someone attempts to unsubscribe an email address that isn't actually subscribed, a notification will be sent, via email to the address, instead of having a notice in the browser. This is to keep the privacy of the subscriber.
This behavior can be enabled/disabled in the list control panel, in,
Your Mailing List - Mailing List Options
Under the option,
If someone not currently subscribed to your mailing list attempts to unsubscribe, send a, "You are not Subscribed!" message via email, instead of showing this error in their web browser.
It is disabled by default.
By default, the following features in Dada Mail are enabled:
By default, the following features in Dada Mail are disabled:
(Invitations are still very much supported)
(Black Listed subscribers may still subscribe themselves)
These are options are set as such to closely follow Closed-Loop Opt-In Subscribing (meaning, a subscriber has to confirm a subscription themselves), which we think is the best way to run a email mailing list.
The options to change these defaults that used to be available have been REMOVED from the List Control Panel.
You may still reveal these options by setting the Config variable, $ENFORCE_CLOSED_LOOP_OPT_IN to, 0. We do not suggest this and we consider the above options DEPRECATED.
To make sure the subscription/removal systems in Dada Mail work correctly, Dada Mail will scan the user-editable email message templates, before it sends them out, to make sure they have the right tags, to perform the right actions. Here's a list of what tags are looked for, in which templates:
The menu labled, "Add" under, "Manage Subscribers" has been change. The line used to read,
{-Title => 'Add',
and now, reads:
{-Title => 'Invite<!-- tmpl_if list_settings.enable_mass_subscribe -->/Add<!-- /tmpl_if -->',
Although you may want to change this line if you're upgrade from v4.x.x to v4.3.0, you won't be required to
The variable, $MAILlING_LIST_MESSAGE has been renamed to, $MAILING_LIST_MESSAGE.
You will need to rename this varialbe in your .dada_config file, if you are currently using it.
Dada Mail will also alert the user of the missing tags in the List Control Panel, Appearance and Templates - Email Message Templates
=head2 Bug Fixes 4.3.0
https://github.com/justingit/dada-mail/issues/closed#issue/89
https://github.com/justingit/dada-mail/issues#issue/87
https://github.com/justingit/dada-mail/issues/closed#issue/84
https://github.com/justingit/dada-mail/issues/closed#issue/82
https://github.com/justingit/dada-mail/issues/closed#issue/83
https://github.com/justingit/dada-mail/issues/closed#issue/71
https://github.com/justingit/dada-mail/issues/closed#issue/72
https://github.com/justingit/dada-mail/issues/closed#issue/74
https://github.com/justingit/dada-mail/issues/closed#issue/79
https://github.com/justingit/dada-mail/issues/closed#issue/78
https://github.com/justingit/dada-mail/issues/closed#issue/75
https://github.com/justingit/dada-mail/issues/closed#issue/80
https://github.com/justingit/dada-mail/issues/closed#issue/81
https://github.com/justingit/dada-mail/issues/closed#issue/77
https://github.com/justingit/dada-mail/issues/closed#issue/76
https://github.com/justingit/dada-mail/issues/issue/66/#comment_546769
https://github.com/justingit/dada-mail/issues/issue/65/#comment_546770
This is basically a bug-fix only release. But of note:
http://github.com/justingit/dada-mail/issues/closed#issue/62
http://github.com/justingit/dada-mail/issues/closed#issue/64
Twitter Support is currently not working, as the type of authorization Dada Mail was utilising (Basic) has been dropped by Twitter in favor of a more substantial authentication scheme called oAuth.
http://github.com/justingit/dada-mail/issues#issue/66
The Habeas Watermark isn't really used anymore, Habeas The Company was bought by a different company, that has a vastly different scheme, other than attempting to legally go after unauthorized use of their copyright material. The new system requires different headers to be present, which Dada Mail does not currently support. We'll see about supporting them, in the future.
Dada Mail now comes with an installer - manually setting up and configuring Dada Mail is now longer needed. Heavens be praised.
Dada Installer directions may be found at:
manually_install_dada_mail.pod.html
Upgrade instructions may be found at:
The installar script may also be run via the command line - instructions can be
found on how to use it, by invoking the script with the, --help flag,
shell>./installer.cgi --help
The, "Advanced" Installation of Dada Mail is just known as a, "Manual" installation of Dada Mail.
The Dada Mail Installer will install Dada Mail the same way as one would install Dada Mail manually. Directions may be found here:
manually_install_dada_mail.pod.html
The, "Basic" Installation method is not recommended or supported. If upgrading from a, "Basic" installation, it's recommended to move to a more contemporary installation setup:
basic_to_contemporary_installation.pod.html
The, "Setup Info" Screen, that you can access using this URL:
http://example.com/cgi-bin/dada/mail.cgi
has been completely rewritten. In light of the Installer, it does not attempt to help
configure Dada Mail for you, but will tell you what type of installation it recognizes,
will present to you the entire contents of your, dada/DADA/Config.pm file as well as your .dada_config
file and will show you how all config variables are being interpreted.
The $ADMIN_MENU variable has been changed to add the, "Dada Mail Setup Info" menu item. It looks like this:
{-Title => '<!-- tmpl_var PROGRAM_NAME --> Setup Info',
-Title_URL => "$S_PROGRAM_URL?f=setup_info",
-Function => 'setup_info',
-Activated => 1,
},
The MySQL schema shipped for Dada Mail, specifically for v4 of MySQL has been removed. The reason for the schema was more because of UTF-8 incompatibilities, rather than problems with this version of MySQL v4.
http://github.com/justingit/dada-mail/issues#issue/60
http://github.com/justingit/dada-mail/issues/issue/61
The Screen Cache API allows Dada Mail to save fully-rendered Dada Mail screens that are commonly viewed.
The Screen Cache is enabled by default, via setting the $SCREEN_CACHE config variable, to 1
A new entry under the, "Plugins" heading has been added to the $ADMIN_MENU variable in the Config.pm, dada/DADA/Template/templates/example_dada_config.tmpl and, dada/extras/examples/example_dada_config.txt
Small Tweaks have been made to the Mass Mailing code in Dada Mail through code profiling which should positively impact Mass Mailing Speeds, upwards of .10 to .25 seconds faster, per message.
Older, unused social bookmarking sites have been removed (as well as Fark, because,well...)
The Facebook link sharing button has also been added.
http://github.com/justingit/dada-mail/issues/closed#issue/57
http://github.com/justingit/dada-mail/issues/closed#issue/56
http://github.com/justingit/dada-mail/issues/closed#issue/55
http://github.com/justingit/dada-mail/issues#issue/54
http://github.com/justingit/dada-mail/issues/closed#issue/48
http://github.com/justingit/dada-mail/issues/closed#issue/49
This is not a security bug/issue/notice - rather, this is a bug that was introduced with the full UTF-8 support.
The binary-in-nature encrypted passwords saved by Dada Mail in the List Settings table/files in Dada Mail may have become unusable/corrupted with version 4.0.3 and/or 4.0.4 of Dada Mail.
If you are having trouble/an impossible time using any of the POP3 or SMTP connection stuff in Dada Mail, including Dada Bridge, Mystery Girl (Bounce Handler) or POP-before-SMTP and/or SMTP SASL authentication - or even the Twitter stuff, you may be bitten by this bug. 4.0.5 should provide a fix for this problem, BUT (big but), 4.0.5 could potentialy break any currently stored passwords.
The fix will be to simply re-save the correct password, after you've upgraded to 4.0.5.
New users of Dada Mail will not be affected by this problem.
This problem does not impact your List Password, or the Dada Mail Root Password - both of which are saved in a one-way encryption, that is separate from the way POP3/SMTP passwords are saved in Dada Mail.
http://github.com/justingit/dada-mail/issues/closed#issue/37
http://github.com/justingit/dada-mail/issues/closed#issue/38
http://github.com/justingit/dada-mail/issues/closed#issue/41
http://github.com/justingit/dada-mail/issues/closed#issue/42
http://github.com/justingit/dada-mail/issues/closed#issue/43
http://github.com/justingit/dada-mail/issues/closed#issue/44
http://github.com/justingit/dada-mail/issues/closed#issue/47
http://github.com/justingit/dada-mail/issues/closed#issue/45
http://github.com/justingit/dada-mail/issues/closed#issue/46
http://github.com/justingit/dada-mail/issues/closed#issue/17
http://github.com/justingit/dada-mail/issues/closed#issue/13
This bug wasn't actually closed with this release, but from a previous release. It has though, been confirmed to be closed with this release.
Some compatibility issues cropped up, regarding UTF-8/unicode character set/encoding
in re: to the SQL schemas. The schemas for all supported SQL backends have been
modified to better work, mostly by changing fields with type, text(320), to type,
varchar(80). Other notes have been added to the UTF-8 FAQ.
Along with looking into changing the default schema in Dada Mail, the v3 to v4 migration script will now make the necessary schema and character set changes.
The character encoding changes and SQL schema changes could potentially be desctructive, so we do, in fact, highly encourage you to make a backup of the entire database, before running the migration tool. Most notably, the character encoding change does not work perfectly. If your data contains a lot of non-Latin1 characters, we'd highly suggest you do your own ASCII/Latin1 to UTF-8 migration, before upgrading your Dada Mail.
If you are running a verion of Dada Mail 4.0.0 to 4.0.3, you'll still need to make those schema changes manually if you're having trouble (exactly what to do, including example SQL is located in the UTF-8 FAQ).
http://github.com/justingit/dada-mail/issues/#issue/36
http://github.com/justingit/dada-mail/issues/#issue/35
http://github.com/justingit/dada-mail/issues/closed#issue/34
http://github.com/justingit/dada-mail/issues/closed#issue/33
http://github.com/justingit/dada-mail/issues/closed#issue/32
http://github.com/justingit/dada-mail/issues/closed#issue/31
CGI::Session handles all session management in Dada Mail.
The CPAN perl modules, Scalar::Util and List::Util are included with Dada Mail, but aren't actively used (and are probably outdated), so that any server-wide installed versions will be used, instead. This is because the XS versions of these modules are needed for POP/SMTP SSL connections and having these usable by default, breaks SSL connections. The directories,
dada/DADA/perllib/List
and,
dada/DADA/perllib/Scalar
have been renamed,
dada/DADA/perllib/List-remove_to_install
and,
dada/DADA/perllib/Scalar-remove_to_install
renaming them back to their original name will make them, "active"
We have worked very, very hard to get Dada Mail working with UTF-8/Unicode.
We think we did a pretty good job and you'll have a most amazing experience when comparing this version to any previous version of Dada Mail (ever), but there may be tiny things still to work out.
We need to know about them, don't be shy!
People who upgrade to 4.0.3 (and any version afterwards, until things change!) should note that the MySQL and PostgreSQL Table Schemas have changed!
You may need to update your own tables, to support UTF-8 (if they aren't already in that encoding).
If you're upgrading, please read over the updated UTF-8/Unicode FAQ:
If you're doing a new install, there's nothing you need to know, Dada Mail should work well out of the box in re: to UTF-8/Unicode stuff.
We've changed a few of the default list settings, hopefully so that everyone has a more pleasant experience, right off the bat:
We've enabled the setting to active the Black List, by default.
We're also enabling the below settings:
You still have the option to change new lists to the previous behavior and already created lists will have their previous behavior, if Black List Settings have already been edited.
The option, Print List-Specific Headers has been removed from, Mail Sending -Advanced Sending Preferences has been removed, but the functionality has not. All mailing list messages will have these headers.
Send Unsubscription Confirmation Emails (Closed-Loop Opt-Out) has been disabled by default (you can still enable it)
This option, when enabled, requires that when someone wants to unsubscribe, they have to confirm this unsubscription by clicking on the unsubscription confirmation link in a URL sent their subscribed address.
When disabled (the new default), they simply have to fill out the subscribe/unsubscribe form.
When available, both the Subscription and Unsubscription links will have the potential subscriber's (or unsubscriber's) email address in the link itself, so that the user does not have to do the two-step of first following the link and then typing in their email address.
These links are created per-subscriber (or potential sub/unsub), when you use the:
<!-- tmpl_var list_subscribe_link -->
or,
<!-- tmpl_var list_unsubscribe_link -->
tags. Previously, these tags only provided a link to the subscription/unsubscription form, without the email address embedded within the link itself. There is no way to revert this behaviour, but you can still roll your own links, like this:
Subscription Link:
<!-- tmpl_var PROGRAM_URL -->/s/<!-- tmpl_var list_settings.list -->
Unsubscription Link:
<!-- tmpl_var PROGRAM_URL -->/u/<!-- tmpl_var list_settings.list -->
Dada Mail will now do a quick check to make sure that there is a Dada Mail Unsubscription link in your mass mailing messages, before sending them out.
If one is not found, one will be automatically appended to the end of your message.
It will not be very fancy.
We suggest that you make sure that you have a real, valid, Dada Mail unsubscription link in your Mailing List Messages.
http://github.com/justingit/dada-mail/issues/issue/30
http://github.com/justingit/dada-mail/issues/issue/29
http://github.com/justingit/dada-mail/issues/issue/28
http://github.com/justingit/dada-mail/issues/issue/27
http://github.com/justingit/dada-mail/issues/issue/26
http://github.com/justingit/dada-mail/issues/issue/16
http://github.com/justingit/dada-mail/issues/issue/21
http://github.com/justingit/dada-mail/issues/issue/24
http://github.com/justingit/dada-mail/issues/issue/23
http://github.com/justingit/dada-mail/issues/issue/20
http://github.com/justingit/dada-mail/issues/issue/19
http://github.com/justingit/dada-mail/issues/issue/18
http://github.com/justingit/dada-mail/issues/issue/15
For whatever reason, the, "Allow Open Discussion List" option wasn't viewable, until
you first enabled discussion lists. It will now *always* be viewable, as long as the
Plugin Config Param, Allow_Open_Discussion_List is set to, 1
A new Plugin Config Paramater called, Check_Multiple_From_Addresses has been added
and has a default value of, 1. When enabled, messages that have more than one
sender aren't supported by Dada Bridge and these messages will be ignored.
Set this paramater to, 0 to revert to the previous behavior.
Dada Mail had a very simple test to make sure mail using the sendmail command was successful, by looking at any error messages created from sending mail this way. If a, "broken pipe" message was found while sending a mass mailing, a mass mailing would be stopped, and would be picked up and sending would be attempted starting at the same address that gave the error. The complete logged error may look like this:
[Mon Jan 4 16:40:08 2010] mail.cgi: Pro Dada 4.0.1 Warning:
[Mon Jan 4 16:40:08 2010] mail.cgi: didn't close pipe to '|/usr/sbin/sendmail -t -fbounces@example.com' while
[Mon Jan 4 16:40:08 2010] mail.cgi: attempting to send a message to: '"My Mailing List" <me@example.com> because:' Broken pipe at ..//DADA/MailingList/Schedules.pm line 808
[Mon Jan 4 16:40:08 2010] mail.cgi: Broken Pipe error! returning -1 - Mass Mailing should be exit()ed! at ..//DADA/MailingList/Schedules.pm line 808
[Mon Jan 4 16:40:08 2010] mail.cgi: [listshortname] Mailout:<20100104164007.54315974@nicky510.com> Bailing out of Mailing for now - last message was unable to be sent! exit()ing! at ..//DADA/MailingList/Schedules.pm line 808
This behavior is problematic, since the, "broken pipe" error can happen, even if a message (or part of a message) is actually sent. Sometimes this happens if you have a message that contains a dot by itself on one line, like this:
.
If this is problematic to you (messages being cut off because of a lone dot on one line)
and you're using the sendmail command to send messages, consider changing the $MAIL_SETTINGS
and, $MASS_MAIL_SETTINGS Config variables to include the, -i flag, like this:
$MAIL_SETTINGS = "|$MAILPROG -t -i"; $MASS_MAIL_SETTINGS = "|$MAILPROG -t -i";
http://github.com/justingit/dada-mail/issues/closed/#issue/6
http://github.com/justingit/dada-mail/issues/closed#issue/10
http://github.com/justingit/dada-mail/issues/closed#issue/12
http://github.com/justingit/dada-mail/issues/closed#issue/11
http://github.com/justingit/dada-mail/issues/closed#issue/14
The following topics were added to the documentation:
A MySQL Schema specifically for MySQL 4 is now shipped with Dada Mail at:
dada/extras/SQL/mysql4_schema.sql
Although not heavily documented (yet), a DB Backup to SQL script has been added to the distribution at:
dada/extras/scripts/dada_settings_backup_to_sql.pl
The, New List Screen has been giving minor formatting tweaks.
Some work has been done to speed up DADA::ProfileFieldsManager by caching.
http://github.com/justingit/dada-mail/issues/closed#issue/1
http://github.com/justingit/dada-mail/issues/closed#issue/2
http://github.com/justingit/dada-mail/issues/closed#issue/4
http://github.com/justingit/dada-mail/issues/closed#issue/5
http://github.com/justingit/dada-mail/issues/closed#issue/7
http://github.com/justingit/dada-mail/issues/closed#issue/8
http://github.com/justingit/dada-mail/issues/closed#issue/9
Support has be re-introduced to allow Multiple List Sending. See the separate docs on this feature:
Please see the docs specifically about Dada Mail Subscriber Profiles:
You can now have a, "Label" to your Subscriber Profile Field. A label is what's visibly shown and is not now created from the field's name.
You can now have an, "open to all to subscribe" mailing list, that still requires approval from the list owner.
Please see the docs specifically about this new feature:
This version of Dada Mail is currently shipped with all charsets and encodings to, "UTF-8", but Dada Mail itself is far from support this character set completely.
This is because it is hard.
Please see the docs specifically about this new feature:
Yup. Dada Mail can Tweet. More information:
We're experimenting with bringing CKeditor support to Dada Mail. Please see the embedded Config.pm docs about this:
Config.pm.html#ckeditor_integration____ckeditor_url__experimental__
This means, that anything about the mass mailing is logged for that specific mass mailing - this should hopefully make debugging a little bit easier.
There's a new link entitled, "Open Mass Mailing Log in a New Window -> "
This functionality is currently extremely rough, but is a pretty easy way to see what, in fact, is going on.
We've started catching sendmail errors and, if we find an error, we'll exit out of the sending process, for the message to be automatically picked up and the last email that had a problem, to be tried again. It's currently not perfect, but it's a very small step forward.
You can now clone the settings from one list, to another list, in the, "Create a New List" screen.
You can now Remove all subscribers at once in the, Manage List - View Subscribers screen.
For the most part, AJAX stuff in Dada Mail has been replaced by the prototype.js and Scriptalicious Javascript Libraries.
If it wasn't clear or official before, it should be now:
The black list matching does not work with matching strings, but will only work to match the user or domain of an email address or the entire email address. These are valid black list entries:
Mostly meaning, you can embed images within the email message itself.
You can now specify the Port Number of the POP3 mail server
Simple moderation support is included, to Authorized to moderate messages.
The Clickthrough Tracker now has a new SQL backend option for the URL redirect list.
The log is still in PlainText.
The update_subscriptions.cgi extension has been removed, as its features have been superceded by the Dada Profiles feature. And then some.
The CPAN Perl Libraries needed for Dada Mail are now being saved within the Git Repository of Dada Mail. We don't know if this is the greatest idea, since we don't really plan on making changes to this modules. But, we're doing it. If any problems occur, please report!
There are many new modules in Dada Mail's backend, including: