v11.7.0 Released

From: "Justin J justin@PROTECTED [Dada Mail Developers]" <dadadev@PROTECTED>
Subject: v11.7.0 Released
Date: December 13th 2019

Howdy everyone, v11.7.0 has been released. Download and Install:


Changelog (and below) http://dadamailproject.com/d/changes_11_x.pod.html#pod11.7.0

I'm pasting in the changelog for v11.6.0 as well, as I don't think that was announced on this list:



Bridge Announcement List and Authorized Senders Enhancements

The Bridge plugin allows you to send messages with Dada Mail through your mail reader without having to log into Dada Mail's own list control panel. You can set up a list of Authorized Senders who are allowed to send to the mailing list. This is an easy way to allow more than just the List Owner the ability to send to your mailing list, without needing to give out your mailing list's administration credentials to anyone else.

We have added several features to allow you to send more effective announce-only messages through Bridge:

Rewrite From: Header Correctly

The first change we've made is actually a bug fix. One way to run your announcement list utilizing Authorized Senders is to rewrite the From: header, so all messages sent to your mailing list use the List Owner in the From: header, no matter what Authorized Sender sent the message.

Look for the radio button labeled,

Rewrite From header to List Owner

in Bridge

Another option available is to preserve the original From: header so that any replies go to that address, rather than the List Onwer. The issue was that the From: header wasn't correctly managed to deal with DMARC restrictions.

Say you have an Authorized Sender that's using a Gmail account, and you've set up your mailing list to send using your own SMTP server. Sending a mass mailing from your own server with (for example) a Gmail address in the From: header won't work. You'll need to instead send the message "on behalf of" the original sender, just like we do for discussion lists. In past versions, this wasn't happening, and in v11.7- it now is. Rejoice!

Look for the radio button labeled,

Rewrite From header to be "on behalf of" List Owner

in Bridge.

Don't rewrite the From header for email addresses from certain domains

We've also added an option to list domains that you would not like this rewrite to happen, just in case your mail system has already allowed certain additional domains to be sent through it.

Look for textbox labeled,

Don't rewrite From header for the following domains: (one domain per line)

Set the Reply-To: header

The ability to set the Reply-To header to the List Owner or the original sender (or no one!) has been kept, even though the From: header need to be sent "On Behalf Of".

Mention the original sender

Similar to what you're able to do already for discussion lists, you can now set your mailing list to mention who the original authorized sender was, who sent the message. This option can be enabled (default) and disabled in Bridge for both announce-only and discussion lists. Look for the checkbox labeled:

Mention the original sender of the message at the top of the message itself

in Bridge.

Under the hood, this is implemented using Dada Mail's template tags, which you can use too, in your own custom mass mailing layout. See our docs on Dada Mail's email template tag syntax to learn more:


Bug Fixes

Authorized Senders do not have their addresses re-written in announce-only messages. Open


Moderation is active even if mailing list is announce-only




WhatsApp Number Support

Add your WhatsApp Number! A link to start a WhatsApp chat will appear at the bottom of your email messages, below your physical address and phone number.

Theme being used now displayed in Admin Menu

See which theme is currently applied to your email messages without having to visit the Email Themes screen

Better error reporting in individual mass mailing log

In an effort to more easily debug problems with mass mailings, the individual mass mailing log will show more errors.

Better error reporting for problems with messages received with the Bridge plugin

In an effort to more easily debug problems with messages received via the Bridfge plugin, more information will be printed to the error log, when a problem occurs.

New Safety Checks When Removing All List Members

In Dada Mail, it's very easy to remove all list members from the, Membership: View screen. Although an alert box does come up when you click this button, it's not entirely clear if Global Unsubscribe is enabled for your installation. If it is, removing all your members from one list may remove all your members from all your mailing lists, which most likely is not what you want to do.

To help with this issue, we've disabled this button per mailing list. You can re-enabled it in the, Membership: Options screen. We've also put a alert box on the top of the, Membership: View to remind you if you Global Unsubscribe is enabled. The alert box that comes up if you do try to remove all your members will again remind you that global unsubscribe is enabled.

All the above also applies to the Global Black List, and you'll get similar notifications in the interface if you try to remove any of the blacklisted members, and have the Global Black List enabled.


Images that cannot be fetched via URL embedded anyways


Some form values (URLs, HTML comments) get rejected by web server firewalls (mod_security)

"some form values (URLs, HTML comments) get rejected by web server firewalls (mod_security)"

Verbose Error Logs re: temp mass mailing subscriber file


Individual Mass Mailing Log should show errors


references to, "http://dadamailproject.com" needs to be changed to, "https://dadamailproject.com"


If Global Unsubscribe/Global Black List is enabled, the, "Remove ALL $List_Type" alert box should remind the user


Internal Changes

Moving Away from MIME::Lite::HTML to MIME::Entity

The largest change in this release is moving away from using the, MIME::Lite::HTML module. MIME::Lite::HTML was an important part of Dada Mail, as it was used to embed images into email messages and was the original engine that turned URL's into email messsages.

But, MIME::Lite and therefore MIME::Lite::HTML are known to be a little buggy, and aren't well supported these days, so we've moved to it's larger brother: MIME::Entity. MIME::Entity and the rest of the MIME::Tools collection of modules is already well-entrenched within Dada Mail's codebase. Removing MIME::Lite::HTML also removes a substantial amount of redundant code.

jQuery upgraded from v2.1.4 to v2.2.4


Justin J: Lead Dadaist.url: http://dadamailproject.com email: justin@PROTECTED twitter: @dadamail skype: leaddadaist

Dada Mail Announcements:http://dadamailproject.com/cgi-bin/dada/mail.cgi/list/dada_announce/

  • This mailing list is a public mailing list - anyone may join or leave, at any time.
  • This mailing list is a group discussion list (unmoderated)
  • Start a new thread, email:


This mailing list is to discuss the nerdy programming development of Dada Mail -

If you are just looking for support Dada Mail, consult the message boards at:


To post to this list, send a message to:


All subscribers of this list may post to the list itself.

Some on topic... topics include:

  • Positive Crits on the program (I like, "x", but, "y" needs some work - here's an idea on how to make this better...)
  • Bug/Error reports
  • Bug fixes
  • Request For Comments on any changes to the program
  • Help customizing Dada Mail for your own internal needs
  • Patches
  • Language Translations
  • Support Documentation/Doc editing, FAQ's, etc.
  • Discussion of any changes that you would like to be committed to the next version of Dada Mail -

At the moment, there aren't many people with CVS access for Dada Mail - if you would like CVS access, please first talk about the changes you propose and how it will affect the program. If the idea is sound and agreed upon, the change will be comitted. A good track record of this will allow you to have CVS access. Some reasons that patches will not be accepted is if the patch breaks compatibility with a previous version of the program, the patch is too centric to your own problem or the patch simply isn't very good.

Please, please please familiarize yourself with the documentation at:


Since no one wants to answer the same question twice.

Another sneaky reason for this mailing list is to test out the discussion list capabilities of Dada Mail, since Dada Mail is used for the mailing list itself.

NOTE - because of this, there may be times that this list will be somewhat broken. Although we're not planning on breaking the program by using it, we're giving you the heads up that this may well happen anyways.

Privacy Policy:

This Privacy Policy is for this mailing list, and this mailing list only.

Email addresses collection through this mailing list are used explicitly to work within this email discussion list.

We only collect email addresses through our Closed-Loop Opt-In system.

We don't use your email address for any other purpose.

We won't be sharing your email address with any other entity.

Unsubscription can be done at any time. Please contact us at: justin@dadamailproject.com for any help regarding your subscription, including removal from the mailing list.

All mailing list messages sent from us will include a subscription removal link, which will allow you to remove yourself from this mailing list automatically, and permanently.

All consent to use your email address for any other purpose stated at the time of the mailing list subscription will also be revoked upon mailing list removal.

Dada Mail Project