Set Scorecard Prefs per-list, instead of Globally

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.

Decaying Scores

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.

Bounce Scorecard Conveniently on the default screen

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.

Forward bounces to List Owner

Bounce messages can now be forwarded to the List Owner, once the Bounce Handler has reviewed the message.

SES Support

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 support, Faster Template Rendering

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.

Installer: some plugins/extensions installed by default

Mailing Monitor (although the cronjob will still need to be set, manually)

Change Root Password

Screen Cache

Log Viewer

Tracker

Multiple Subscribe

AJAX'd Subscription Form

Blog Index

CPAN Module Changes and Updates

LWP unbundled

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.

MIME::Tools upgraded to v5.502

This upgrade to MIME::Tools has a very positive improvement on sending speed.

Bugfixes 4.9.0

Unsub Notices when removing addresses from the email come with unsub link?

https://github.com/justingit/dada-mail/issues/240

4.8.4

Summary 4.8.4

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).

Changes 4.8.0

CAPTCHA docs

This the addition of docs for reCAPTCHA Mailhide, including how to install the missing CPAN Module needed, via a cPanel setup.

HTML::Scrubber CPAN module included with Dada Mail distro

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.

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.

New tracker features: track forward-to-a-friend usage and archive views by country of origin and over time

Truly, "Closed" and, "Invitation-only" mailing list behaviors

Features 4.7.0

Tracker Reports in Mailing Monitor

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

Invitation-Only Mailing Lists

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.

List Control Panel Subscriptions Enhancements

Send a "Welcome" Message to Addresses Subscribed by the List Owner.

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

Send the Newest Archived Message to Addresses Subscribed by the List Owner.

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.

List Control Panel Unubscriptions Enhancements

Send a "Farewell" Message to Addresses Unsubscribed by the List Owner.

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

Tracker Enhancements

"Forward to a Friend" Logging

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.

Archive Views Logging

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.

Changes 4.6.1

CPAN Module Updates

Features 4.6.1

Bug Fixes 4.6.1

"Revert ALL Text to Defaults" at "Email Message Templates" not working

https://github.com/justingit/dada-mail/issues/175

Discussion Lists with a List Name the same as the List Email can cause Infinite Loops!

https://github.com/justingit/dada-mail/issues/176

Dada Bridge: Ability to subscribe List Email to Subscription List

https://github.com/justingit/dada-mail/issues/177

Dada Bridge: Ability to set List Email address to same address used for List Owner or List Admin address

https://github.com/justingit/dada-mail/issues/178

Dada Bridge: Ability to set List Email to a List Email used on a different list

https://github.com/justingit/dada-mail/issues/179

Closes #180 List-Subscribe: header used even if the list is CLOSED

https://github.com/justingit/dada-mail/issues/180

"Unsubscribe Tag Options" not reflected in, "List-Unsubscribe" header

https://github.com/justingit/dada-mail/issues/181

4.6.0

Summary 4.6.0

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

Features 4.6.0

Amazon SES Mail Sending Support

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!

See Also:

Install Plugins/Extensions with the Dada Mail Installer

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.

Bug Fixes 4.6.0

POP3 Login Paramaters not getting passed correctly?

4.5.2

Summary 4.5.2

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

Bug Fixes 4.5.2

"Download List (CSV)" (PlainText backend) all on one line

https://github.com/justingit/dada-mail/issues/169

Features 4.5.2

Tracker: Domain Breakdown of bouncing email addresses

Tracker: Messages Opens Over Time

Tracker: Messages Clickthroughs Over Time

4.5.1

Summary 4.5.1

v4.5.1 fixes some small bugs found in v4.5.0 of Dada Mail, mostly dealing with the Tracker plugin

Bug Fixes 4.5.1

broken link to Tracker plugin in example_dada_config.tmpl template

https://github.com/justingit/dada-mail/issues/165

Clickthrough.pm misc. debug code (warnings)

https://github.com/justingit/dada-mail/issues/166

Tracker: Clickthrough URL report isn't contained

https://github.com/justingit/dada-mail/issues/167

Tracker: GeoIP Country -> # report table has no order

https://github.com/justingit/dada-mail/issues/168

4.5.0

Features 4.5.0

New Plugin! Tracker

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:

# subscribers when a mass mailing was sent out

# of recorded clickthroughs

# of recorded opens/views

# bounces, both soft and hard

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.

More Information

Changes 4.5.0

clickthrough_tracker.cgi plugin removed

Replaced with the Tracker plugin, which is tons better.

Subscriber and # Mailing Lists Quotas changes

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

Bug Fixes 4.5.0

Link to Add Authorized Senders not available if they're aren't any, yet

https://github.com/justingit/dada-mail/issues/160

Advanced Sending Preferences: Unable to change three settings

https://github.com/justingit/dada-mail/issues/162

Dadaized FormMail.pl - syntax errors?

https://github.com/justingit/dada-mail/issues/163

4.4.3

Changes 4.4.3

Clickthrough Tracking Redirect Tags Now Support mailto: URLS

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.

Wishlist: mailto:user@example.com supported in the redirect tags

https://github.com/justingit/dada-mail/issues/145

ajax_include_subscribe.cgi - set the mailing list you want the form to use, by query string parameter

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 parameter:

signing into a single list (via f=sign_in) produces an error.

4.4.0

Changes 4.4.0

Closed-Loop Opt-In Subscription Not Enforced by Default, Anymore

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:

Code Cleanup

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.

Mass Mailing: Better Error Reporting

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: Reply and Reply-All Behavior

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,

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.

View List: Email Your List Button is Gone

You may still download your mailing list in csv format.

Log View: Download the Raw Log

You can now download the entire log file, through the log viewer.

Installer: Old Screen Cache Files Removed

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.

Template System: initial "tmpl_set support", template wrapping

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.

AJAX: internal changes

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.

Mailing Monitor: AJAX

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.

Subscription/Unsubscription Custom URL Redirect API Change

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 parameter named, errors. This name has been changed to, errors[] to help out php folk. This is tied to this bug:

Web Services Examples

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.

Test Mass Mailings, Mail Merging

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.

Bug Fixes 4.4.0

blank "Verify" screen when adding/removing addresses in the list control panel

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.

SOAP Examples for Subscribing Included

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.

Plugin: mx_lookup.cgi cleaned up

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.

Code Cleanup

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,

No .htaccess in .dada_files directory by default, when installing w/the installer

https://github.com/justingit/dada-mail/issues/closed#issue/99

4.3.0

Installation instructions for 4.3.0 are the same as they were for 4.2.0.

Changes 4.3.0

CPAN module Captcha::reCAPTCHA upgraded from v.92 to v.94

Twitter Support Removed

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.

Habeas Watermark Support Removed

The Habeas Watermark isn't really used, anymore, anyways.

Features 4.3.0

Dada Bridge: Ignore/Send a Rejection message for Spam Messages

It's now possible to either ignore messages seen as spam, or send a rejection message.

Unsubscription Confirmations: Email Notice

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.

Closed-Loop Opt-In Subscription now Enforced by default

By default, the following features in Dada Mail are enabled:

Closed-Loop Opt-In Subscriptions

By default, the following features in Dada Mail are disabled:

Subscribing Address via the List Control Panel without confirmation

(Invitations are still very much supported)

Subscribing/Inviting Black Listed Addresses

(Black Listed subscribers may still subscribe themselves)

Skipping the confirmation step for subscriptions if a user is logged into their profile

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.

Email Message Templates Scanned for Correct Tags, Fixed if Missing.

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:

List Subscription Confirmation Link

Subscription Confirmation Email

List Invitation Message (PlainText)

List Invitation Message (HTML)

List Unsubscribe Link

Mailing List Message (PlainText)

Mailing List Message (HTML)

List Unsubscribe/Removal Confirmation Link

Unsubscription Confirmation Email

Config variable changes

$ADMIN_MENU

The menu labled, "Add" under, "Manage Subscribers" has been change. The line used to read,

Habeas Watermark Not Really used Anymore?

4.2.1

Changes 4.2.1

Peppered through some of the directories are .htaccess files, to stop unwanted access to these directories. This is simply a safegaurd and shouldn't really be seen as a security issue.

Bug Fixes 4.2.1

"Setup Info" screen incorrectly determines a installation as, "Basic" if the $PROGRAM_CONFIG_FILE_DIR is set to, "auto"

http://github.com/justingit/dada-mail/issues/closed#issue/62

Reply-To in %EMAIL_HEADERS will never be used

http://github.com/justingit/dada-mail/issues/closed#issue/64

KNOWN ISSUES 4.2.1

Twitter Support

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

Habeas Watermark

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.

4.2.0

Changes 4.2.0

Dada Mail Installer

Dada Mail now comes with an installer - manually setting up and configuring Dada Mail is now longer needed. Heavens be praised.

Setup Info Screen

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.

$ADMIN_MENU Changes

The $ADMIN_MENU variable has been changed to add the, "Dada Mail Setup Info" menu item. It looks like this:

MySQL 4-specific schema REMOVED

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.

4.1.0

Changes 4.1.0

Screen Cache Working Again, Enabled by Default

Enabled by Default

The Screen Cache is enabled by default, via setting the $SCREEN_CACHE config variable, to 1

Changes to the $ADMIN_MENU

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

"Send Subscribers to List Owner" function not very friendly to use

4.0.5

Changes 4.0.5

POP3 and SMTP Passwords Saved in List Settings

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.

Bug Fixes 4.0.5

Subscriptions are not logged in the usage log.

http://github.com/justingit/dada-mail/issues/closed#issue/37

Subscribers can be subscribed more than once to the black list

http://github.com/justingit/dada-mail/issues/closed#issue/38

Dada Bridge sending broken if, "Strip attachments that have the following file ending or mime-type:" is enabled

POP3/SMTP passwords corrupted?

Archived messages for discussion lists may have member-specific unsubscribe links

http://github.com/justingit/dada-mail/issues/closed#issue/46

Send a Webpage gives unhelpful error if you enter a wrong URL of a missing page

http://github.com/justingit/dada-mail/issues/closed#issue/17

4.0.1 Open discussion lists broken

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.

4.0.4

Changes 4.0.4

UTF-8 Issues

MySQL, PostgreSQL, SQLite schema changes

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.

dada3_to_dada4_sql.pl changes

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).

CPAN Modules 4.0.4

CGI::Sessoion upgraded to: 4.42

CGI::Session handles all session management in Dada Mail.

List-Utils Scalar-Utils

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"

4.0.3

Changes 4.0.3

Unicode/UTF-8 Work

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!

SQL table schema changes!

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).

See Also:

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.

Changes to Default List Settings

We've changed a few of the default list settings, hopefully so that everyone has a more pleasant experience, right off the bat:

Activate Black List

We've enabled the setting to active the Black List, by default.

We're also enabling the below settings:

Move Unsubscribed Subscribers Automatically to the Black List

Continue to Allow Subscriptions From Subscribers of Black Listed Addresses

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.

Print List-Specific Headers option Removed

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.

Subscription and Unsubscription links now include an Email Address

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 -->

Unsubscription Links Now Mandatory for Mass Mailing Messages

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.

Bug Fixes 4.0.3

Send newest archived message may have outdated header information

http://github.com/justingit/dada-mail/issues/issue/30

pop3 username/password not saved when "Save, Then Test..." button pressed in Sending Preferences

http://github.com/justingit/dada-mail/issues/issue/29

Beatitude: Months are listed out of order

http://github.com/justingit/dada-mail/issues/issue/28

profile field names can contain more than just ascii letters, numbers and underscores

http://github.com/justingit/dada-mail/issues/issue/27

list short names can contain more than just ascii letters, numbers and underscores

http://github.com/justingit/dada-mail/issues/issue/26

Beatitude: Scheduled List Not in Any Useable Order?

http://github.com/justingit/dada-mail/issues/issue/16

Dada Bridge: Spam Assassin Level Picker isn't available

http://github.com/justingit/dada-mail/issues/issue/21

Sending Preferences don't correctly state if you can use Use Secure Sockets Layer (SSL) for POP-before-SMTP

4.0.2

Changes 4.0.2

Dada Bridge: "Allow Open Discussion List" option always viewable

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

Dada Bridge: New Plugin Config Param: Check_Multiple_From_Addresses

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 parameter to, 0 to revert to the previous behavior.

Mail Sending - "broken pipe" catch removed

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:

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:

This means, that anything about the mass mailing is logged for that specific mass mailing - this should hopefully make debugging a little bit easier.

View the Mass Mailing Log from the Mailing Monitor

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.

Slightly Smarter Error Handling for failing sendmail mailings

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.

Clone Settings

You can now clone the settings from one list, to another list, in the, "Create a New List" screen.

Remove All Subscribers

You can now Remove all subscribers at once in the, Manage List - View Subscribers screen.

prototype.js/Scriptalicious Support

For the most part, AJAX stuff in Dada Mail has been replaced by the prototype.js and Scriptalicious Javascript Libraries.

Black List Matching

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:

Simple moderation support is included, to Authorized to moderate messages.

Plugins - Clickthrough Tracker

The Clickthrough Tracker now has a new SQL backend option for the URL redirect list.

The log is still in PlainText.

Extensions - Update Subscriptions - REMOVED

The update_subscriptions.cgi extension has been removed, as its features have been superceded by the Dada Profiles feature. And then some.

CPAN Perl Libraries

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!