This is mostly a bug-fix release for issues found in the v11.4.3 release of Dada Mail.
https://github.com/justingit/dada-mail/issues/823
https://github.com/justingit/dada-mail/issues/822
https://github.com/justingit/dada-mail/issues/820
This is mostly a bug-fix release for issues found in the v11.4.2 release of Dada Mail.
https://github.com/justingit/dada-mail/issues/817
https://github.com/justingit/dada-mail/issues/818
https://github.com/justingit/dada-mail/issues/821
This is mostly a bug-fix release for issues found in the v11.4.1 release of Dada Mail.
https://github.com/justingit/dada-mail/issues/815
This is mostly a bug-fix release for issues found in the v11.4.0 release of Dada Mail.
https://github.com/justingit/dada-mail/issues/814
https://github.com/justingit/dada_mail_foundation_email_templates/issues/10
This release has changes mostly that relate to the Tracker plugin:
Support to add a Google Maps API Key has been added
Ability to log full (rather than anonymized) IP addresses has been restored
On June 1st, Google will require anyone that accesses their maps API to get an API Key (and thus, sign up for Google Cloud Platform). Dada Mail uses the map charts to show location data, and this falls under using their maps. Rather than remove this feature from Dada Mail, we've instead added support to add this Maps API Key into Dada Mail.
You can grab an API key using these instructions:
https://developers.google.com/maps/documentation/javascript/get-api-key
Once you have a key, you may add it to Dada Mail through the Dada Mail Installer - look for a checkbox labeled,
Configure Google Maps
Check it, then add your Google Maps API Key in the textbox labeled,
Google Maps API Key
If this API Key is not available, none of the map charts will be shown, but tabular data will be available where that makes sense. You can also disable showing maps in the Tracker plugin with a new option labeled,
Show maps in message reports
Dada Mail now has the ability - install-wide to control just what personally identifying information is allowed to be collected. New options are available in the installer under the option,
Configure Handling Personally Identifiable Information (PII)
Options are:
Default: disabled
If enabled, Dada Mail will then enable an option in the Tracker plugin labeled,
Track with email addresses
Which may be enabled/disabled per mailing list.
When this option is enabled, the Tracker plugin will log and report data that includes the email address.
If disabled, the following message will be shown in the Tracker plugin,
Disabled. Logging email addresses for analytical purposes is not enabled.
Default: anonymized
Dada Mail by default anonymizes IP addresses before logging them. If you would like to enable saving the actual IP address being reported, you now have the option to do so.
Make sure to be educated on these options - if you need to follow the guidelines put forth by the GDPR, neither tracking with an email address, nor logging IP addresses should be things you should be doing, unless you've been given consent to do so. See also
https://dadamailproject.com/d/gdpr_guide.pod.html
One of the places that full IP addresses are useful, is when reporting where opens, clickthroughs, etc are done geographically, and Dada Mail reports this using it's map charts.
If IP address logging is anonymized, this location lookup by IP address is negatively impacted.
This is now noted in the Tracker plugin, and a new option is available to simple enable/disable maps from being shown completely. Look for the option labeled,
Show location data in message reports
These topics are touched upon in then following blog post:
https://github.com/justingit/dada-mail/issues/812
This is mostly a bug-fix release for issues found in the v11.3.0 release of Dada Mail.
https://github.com/justingit/dada-mail/issues/810
https://github.com/justingit/dada-mail/issues/812
Google+ has been effectively shuttered, so we've removed support for it from the app.
Dada Mail has supported "one-click unsubscribe" when a user clicsk one of the unsubscribe buttons/links in the mailing list message, as well as via the List-Unsubscribe
email header. The latter of which isn't shown directly to a subscriber, but may be used by their mail reader to provide a mechanism to unsubscribe through it's own UI.
There's a problem though with this List-Unsubscribe
header:
Sometimes the unsubscription link in the header is visted by anti-virus software which, after visiting the link will unsubscribe the user without any direct action from the subscriber themselves! This leads to all sort of administration problems, as list owners are losing subscribers who would like very much to stay on their mailing list.
Dada Mail now supports one-click unsubscribe via the List-Unsubscribe
header without this problem happening. This is done by following RFC 8058, which provides a mechanism to utilize one-click unsubscribe via the headers, but stops the scenario described above from happening.
Any email reader that supports RFC 8058 will allow your subscribers one-click unsubscribe. Any mail reader that doesn't support this mechanism will still be able to use the fallback, email-only option, also located in the mail header. Either way, incorrect unsubscriptions throught his mechanism shouldn't happen anymore. In our testing, we've found that most email readers actually only support emailing the list owner, when a user clicks the email reader-provided unsubscribe link.
If the above mechanism isn't supported by the mail reader, there's a good chance that the fallback is. That fallback being: the mail reader sends an actual email message to the list owner. This email message option has also now been made a bit more useful. In past versions of Dada Mail, an email would be sent to the list owner, telling them the address that wants to be removed as well as the list they should be removed from. It was up to the list owner to go through the list control panel to remove this address.
Starting with v11.3.1, the unsubscription link itself needed to unsubscribe the address from the list will be embedded within the email message the list owner receives, so all they have to do now is click that link.
If one decides instead to not have the List-Unsubscribe
header available at all, there is a new option to not enable/disable it from being used. This option is available in the list control panel under,
Mass Mailing: Options: Headers: Use, "List-Unsubscribe" headers
https://tools.ietf.org/html/rfc8058
To coincide with the enhancements to the List-Unsubscribe
header, we've expanded the options on what happens when a subscriber clicks the unsubscription buttons/links in mailing list messages themselves.
The three options are now:
Once a subscriber clicks on a unsubscription link/button in the mailing list message, they'll be unsubscribed right away, with no further action by the user. Super convenient for the subscriber! And one we suggest, especially since the enhancements to the List-Unsubscribe
header have been made and the problem with anti-virus software getting in the way have now been worked out.
One issue with this option though is that a user may inadvertantly click the unsubscription button/link, or forward the mailing list message to someone else, that then clicks that same button/link. Yikes!
Once a subscriber clicks on a unsubscription link/button in the mailing list message, they will be presented with a screen, that just asks them to click a link/button to complete the unsubscription. This method may help with people inadvertantly clicking the unsubscribe link/buttons in the mailing list message by mistake. It's the option selected by default. This option is also the newest option added.
Once a subscriber clicks on a unsubscription link/button in the mailing list message, they will be present with a screen with a form in it, that just asks them to fill in their email address to complete the unsubscription.
This option is a good one, if you're running a discussion mailing list where email messages are commonly replied to/forwarded to other members.
The unsubscription buttons/links embedded in the message may be clicked upon by a different user than the one that received the message, and this simple form can help stop unsubscriptoions done inadvertantly.
All these options work ndependently to the "one-click unsubscribe" support through the List-Unsubsribe
header, which doesn't requires (and cannot have!) any user intervention.
Set up the Bounce Handler to connect to your Bounce Handler Email address via IMAP. This additional option (along with original option of connecting via POP3) gives you more flexibility on how to connect to your Bounce Handler Email address to help fit more email hosting scenarios. For example, those who are using Microsoft Exchange to administrate email may find better success using IMAP, rather than POP3.
Option to select IMAP is available in the Dada Mail Installer.
IMAP support requires that you separately install the Net::IMAP::Simple
CPAN Perl module, or install/upgrade the Bundle::DadaMail
CPAN Perl Module.
Add a link to your Instagram profile in your Mailing List Information, the link will be shown in your mailing list messages, along with Facebook, Twitter, Youtube, and your website links.
This is mostly a bug-fix release for issues found in the v11.2.8 release of Dada Mail.
https://github.com/justingit/dada-mail/issues/805
https://github.com/justingit/dada-mail/issues/799
This is mostly a bug-fix release for issues found in the v11.2.7 release of Dada Mail.
https://github.com/justingit/dada-mail/issues/794
https://github.com/justingit/dada-mail/issues/793
This is mostly a bug-fix release for issues found in the v11.2.6 release of Dada Mail. A few small changes and features did sneak in:
By default, closed/private lists can still invite subscibers, but the subscription form does not show any profile fields. This option, found in: Membership: Options, will allow you to show those fields.
If you're wondering how many, or even if you have any profile fields, that information is now shown in the admin menu itself, saving you a click.
The following logs will now always be shown first (if the log is available):
Usage Log
Error Log
Bounce Handler Log
Cronjob Output
Then, any other log will be shown - most likely, "Mass Mailing" logs. These logs will stop NOT be in any useful order, but that issue will be addressed in a future release. This is currently an open issue:
https://github.com/justingit/dada-mail/issues/761
https://github.com/justingit/dada-mail/issues/790
https://github.com/justingit/dada-mail/issues/789
https://github.com/justingit/dada-mail/issues/787
https://github.com/justingit/dada-mail/issues/784
This is mostly a bug-fix release for issues found in the v11.2.5 release of Dada Mail.
https://github.com/justingit/dada_mail_foundation_email_templates/issues/9
https://github.com/justingit/dada-mail/issues/782
This is mostly a bug-fix release for issues found in the v11.2.4 release of Dada Mail.
https://github.com/justingit/dada-mail/issues/774
https://github.com/justingit/dada-mail/issues/773
https://github.com/justingit/dada-mail/issues/772
This is mostly a bug-fix release for issues found in the v11.2.3 release of Dada Mail.
https://github.com/justingit/dada-mail/issues/771
https://github.com/justingit/dada-mail/issues/770
https://github.com/justingit/dada-mail/issues/769
This is mostly a bug-fix release for issues found in the v11.2.2 release of Dada Mail.
https://github.com/justingit/dada-mail/issues/768
https://github.com/justingit/dada_mail_foundation_email_templates/issues/8
https://github.com/justingit/dada_mail_foundation_email_templates/issues/7
https://github.com/justingit/dada_mail_foundation_email_templates/issues/6
This is mostly a bug-fix release for issues found in the v11.2.1 release of Dada Mail.
https://github.com/justingit/dada-mail/issues/766
Sometimes, you want to send only PlainText mass mailings.
This new feature makes this much easier to configure. In v11.2.1 (and above), go to:
Mass Mailing: Options
Under,
Formatting
set,
Default to authoring:
to,
PlainText Version
Doing so will:
select, "PlainText Version" tab by default, instea of "HTML Version""
select, "Write/Paste Text by default" in the PlainText Version tab
select, "Do not send an HTML version (only PlainText version)" in the HTML Version tab
https://github.com/justingit/dada-mail/issues/763
https://github.com/justingit/dada-mail/issues/762
https://github.com/justingit/dada-mail/issues/759
https://github.com/justingit/dada-mail/issues/758
The Send a Message part of the app has been given a healthy UI refresh - some things to look for:
If you try to leave a draft message screen without saving your changes, you'll be reminded of this with a prompt. This should help stop you from inadvertently leaving the screen prematurely.
When you log into your mailing list's list control panel, the default screen is now the All Drafts/Stationery/Schedules screen, rather than the Send a Message screen. This is to make loading of the list control panel go a little faster, since the Send a Message screen is very complex, and takes a while to fully load.
Having two screens that can send a mass mailing seems like one too many, so we've removed the Send a Webpage screen. Don't worry - all the features on that screen have been added to the Send a Message screen, so no features have been removed. What has been removed is a lot of duplicate code in the backend. Getting rid of this code makes things just that much more simplier to keep well-maintained.
A mass mailing message can be created by:
Writing or pasting content into the rich text editor
fetching the message from a specific URL
creating the message from a RSS/Atom feed
from the Send a Message screen
Individual Drafts/Stationery/Schedules now how a button to Preview the message, without having to open them individually for editing.
All messages are now sorted by creation date, rather than last-modified date, and this creation date is shown.
Send a Message has been renamed + New Draft Message. Clicking it will always create a new draft message. In previous versions of Dada Mail, any previous draft message would get loaded. This was problematic, if you had more than one draft message - things got confusing on just what draft message was now loaded. This menu item has moved one item below in the top menu bar of Mass Mailing
Drafts/Stationery/Schedules has been renamed, All Drafts/Stationery/Schedules and has been moved to the top of the Mass Mailing top bar menu. As has been mentioned, this is the defalt screen now when you log into your mailing list's list control panel.
Many times, people would like to re-use a previously sent message for a new mass mailing. Now, Dada Mail has an option to save previously sent messages you've authored in the list control panel as new stationery messarges, which you can then use to create a new draft message from.
Some users have reported problems with addresses they know are valid, but which that bounce anyways: there's a (hopefully) temporary problem on the receiving mail server.
To counter this, Dada Mail now allows you to set up a list of addresses that the Bounce Handler will not process as it does usually. Instead, bounces from the addresses will just be ignored.
Addresses can be added simonilar to the Black List and White List: segments of addresses are allowed.
For example, if you want to ignore a specific email address, you can. If you want to ignore all address from a domain, you can do that as well.
The RESTful API now supports updating profile fields (look for, update_profile_fields
in the API docs) for an individual email address at a time.
https://github.com/justingit/dada-mail/issues/755
https://github.com/justingit/dada-mail/issues/754
https://github.com/justingit/dada-mail/issues/751
https://github.com/justingit/dada-mail/issues/750
https://github.com/justingit/dada-mail/issues/749
Many pieces of plain text copy in Dada Mail are now treated as Markdown markup, and will be treated as such if/when the copy is used as HTML.
List Settings that will get this treatment include:
Mailing List Description
Mailing List Physical Address
Mailing List Privacy Policy
Along with these list settings, mass mailing messages that are authored in plaintext will be treated as Markdown markup if they are converted to HTML.
https://github.com/justingit/dada-mail/issues/744
This bug, unfortunately, will affect ALL users of at least version 11.0.5 of Dada Mail. If you are using that version, it's recommended to upgrade.
https://github.com/justingit/dada-mail/issues/745
Similar story on this bug.
https://github.com/justingit/dada-mail/issues/743
https://github.com/justingit/dada-mail/issues/740
This most likely affect v11.0.2 users, as changes in that ver. touched on the code where this bug was introduced.
https://github.com/justingit/dada-mail/issues/741
https://github.com/justingit/dada-mail/issues/736
https://github.com/justingit/dada-mail/issues/735
https://github.com/justingit/dada-mail/issues/734
https://github.com/justingit/dada-mail/issues/733
<https://github.com/justingit/dada-mail/issues/721>
https://github.com/justingit/dada-mail/issues/732
https://github.com/justingit/dada-mail/issues/731
Unfortunately, I had to choose one setting to work with one feature, and make the other setting use a different key.
I've chosen to have the "backlink" URL and Nmae to use different keys.
https://github.com/justingit/dada-mail/issues/730
https://github.com/justingit/dada-mail/issues/727
https://github.com/justingit/dada-mail/issues/726
This version has been released almost exclusively to help users/administrators of Dada Mail to more easily comply with the GDPR. More information about what has changed can be found in the included GDRP Guide for Dada Mail