From: Justin J ...@dadamailproject.com>
Subject: [dadadev] 4.0.3 is out
Date: March 12th 2010

I recently release 4.0.3 of Dada Mail, coupling the UTF-8/unicode support stuff I've been working on with the bug fixes since 4.0.2.

Thanks for all the feedback (as always)

Here's the direct downloads:

http://github.com/downloads/justingit/dada-mail/dada-4_0_3.zip

http://github.com/downloads/justingit/dada-mail/dada-4_0_3.tar.gz

It's also tagged as:

http://github.com/justingit/dada-mail/tree/v4_0_3_stable-2010_03_07

I could really use some verification that that UTF-8/unicode stuff is working.

The changelog is below. I have run into a few issues already:

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

Another issue has been with converting current MySQL (in particular - I haven't really looked at SQLite or PostgreSQL) from whatever character set was used, to UTF-8. There's no easy way to do that.

There's also the problem with errors, like this:

Specified key was too long; max key length is 767 bytes

When creating tables. This is directly related to the new charset being set. The resolution seems to be to change the schema, to make certain fields a little smaller. I talk a little about this, here:

http://dadamailproject.com/support/boards/viewtopic.php?f=5&t=1902&p=7211&hilit=too+long#p7211

I also talk about problems with converting the character set:

http://dadamailproject.com/support/boards/viewtopic.php?f=4&t=1904&start=0&hilit=CONVERT+TO+CHARACTER+SET+utf8+COLLATE

using something like this SQL:

ALTER TABLE `dada_settings` CONVERT TO CHARACTER SET utf8 COLLATE utf8_bin;

From my experience, this'll muck up everything that's not Latin1, unfortunately. There's a lot about this problem around the intertubes:

http://www.mysqlperformanceblog.com/2009/03/17/converting-character-sets/

With a lot of different things to try, each getting a lot more complex than the first. You guys have any insight? :)

Dada Mail Change Log for version 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 upgrading, please read over the updated UTF-8/Unicode FAQ:

http://dadamailproject.com/support/documentation/features-UTF-8.pod.html

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) - disabled by default

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 PROGRAM_URL -->/s/<!-- tmpl_var list_settings.list -->/<!-- tmpl_var subscriber.email_name -->/<!-- tmpl_var subscriber.email_domain -->/

or,

<!-- tmpl_var PROGRAM_URL -->/u/<!-- tmpl_var list_settings.list -->/<!-- tmpl_var subscriber.email_name -->/<!-- tmpl_var subscriber.email_domain -->/

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

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

• Double Subscriptions when using List Invitation

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

• Archived messages not templated out in publicly displayed archives

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

*Link to edit subscriber information broken when using the search

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

• Unsubsciption Notice to List Owner doesn't have subscriber (profile) fields

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

• Disabled Menu items return server error when using the, "Classic" session type

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