http://downloads.sourceforge.net/mojomail/dada-2_10_16.tar.gz?download
http://downloads.sourceforge.net/mojomail/dada-2_10_16.zip?download
There are no official new features in 2.10.16 of Dada Mail, when compared to 2.10.15. This is a bugfix only release.
For a features-release version in development, do look at Dada Mail, version 2.11 Alpha 7
These bugs appear in at least the 2.10.15 version of Dada Mail and should be fixed in the 2.10.16 release.
(Submitted by el_baby)
http://downloads.sourceforge.net/mojomail/dada-2_10_15.tar.gz?download
http://downloads.sourceforge.net/mojomail/dada-2_10_15.zip?download
There are no official new features in 2.10.15 of Dada Mail, when compared to 2.10.14. This is a bugfix only release.
For a features-release version in development, do look at Dada Mail, version 2.11 Alpha 6
These bugs appear in at least the 2.10.14 version of Dada Mail and should be fixed in the 2.10.15 release.
http://downloads.sourceforge.net/mojomail/dada-2_10_14.tar.gz?download
http://downloads.sourceforge.net/mojomail/dada-2_10_14.zip?download
There are no official new features in 2.10.14 of Dada Mail, when compared to 2.10.13. This is a bugfix only release.
These bugs appear in at least the 2.10.13 version of Dada Mail and should be fixed in the 2.10.14 release.
http://downloads.sourceforge.net/mojomail/dada-2_10_14-beta_1.tar.gz?download
http://downloads.sourceforge.net/mojomail/dada-2_10_14-beta_1.zip?download
https://sourceforge.net/project/showfiles.php?group_id=13002&package_id=102361&release_id=502753
All bugs are known to be fixed, but require testing and verification.
tar.gz distro:
http://downloads.sourceforge.net/mojomail/dada-2_10_13.tar.gz?download
zip distro:
http://downloads.sourceforge.net/mojomail/dada-2_10_13.zip?download
tar.gz distro:
http://downloads.sourceforge.net/mojomail/dada-2_10_13-rc1.tar.gz?download
zip distro:
http://downloads.sourceforge.net/mojomail/dada-2_10_13-rc1.zip?download
https://sourceforge.net/tracker/index.php?func=detail&aid=1673762&group_id=13002&atid=113002
tar.gz distro:
http://downloads.sourceforge.net/mojomail/dada-2_10_13_beta1.tar.gz?download
zip distro:
http://downloads.sourceforge.net/mojomail/dada-2_10_13_beta1.zip?download
multi_admin_subscribers.cgi is a plugin to allow you to administrate subscriptions/unsubscriptions for multiple lists at one time.
Note: Most likely, this plugin will only be distributed with Pro Dada/The Magicbook in the future, but is released in this beta distribution for testing purposes.
More information:
http://mojo.skazat.com/support/documentation-dada-2_10_16/multi_admin_subscribers.cgi.html
https://sourceforge.net/tracker/index.php?func=detail&aid=1673762&group_id=13002&atid=113002
https://sourceforge.net/tracker/index.php?func=detail&aid=1657018&group_id=13002&atid=113002
https://sourceforge.net/tracker/index.php?func=detail&aid=1654672&group_id=13002&atid=113002
https://sourceforge.net/tracker/index.php?func=detail&aid=1654671&group_id=13002&atid=113002
https://sourceforge.net/tracker/index.php?func=detail&aid=1654669&group_id=13002&atid=113002
https://sourceforge.net/tracker/index.php?func=detail&aid=1648447&group_id=13002&atid=113002
https://sourceforge.net/tracker/index.php?func=detail&aid=1647628&group_id=13002&atid=113002
http://downloads.sourceforge.net/mojomail/dada-2_10_13_alpha1.tar.gz?download
http://downloads.sourceforge.net/mojomail/dada-2_10_13_alpha1.zip?download
See:
http://mojo.skazat.com/support/documentation-dada-2_10_16/FAQ-email_sending.pod.html
Net::SMTP_auth allows us to choose which exact SASL authentication method to use, Net::SMTP would just try to make a best guess.
Note that we are shipping with a module called, Net::SMTP_auth_SSL that allows the same functionality over an SSL/TSL connection. This is not a CPAN module, but a tweak of Net::SMTP_auth to use SSL connections.
Marked at Experimental.
By default, the CAPTCH stuff uses a True Type font called, ``StayPutt.tff'' that's included with Dada Mail. This should make much better CAPTCHA images than the default GD fonts
The process of uploading a file and processing a file has now been split. This may help with large lists amd timeout problems.
It's no longer necessary to have to set the crontab to run dada_bridge.pl as a command line script, you can simply now set a URL for the crontab to visit. This also means you do not have to tweak the environment that dada_bridge.pl runs in, to run correctly as a cronjob.
See:
See:
http://mojo.skazat.com/support/documentation-dada-2_10_16/ajax_include_subscribe.cgi.html
The Dada Mail test suite is available to use in the regular distribution. It can be run using the, prove command or the included web-based Dada Mail extension. More information:
http://mojo.skazat.com/support/documentation-dada-2_10_16/dada_tester.cgi.html
It has now been put back in, based on the new (for us) Net::SMTP module.
Note!: Passwords are shown, albeit in an encoded version, in its results. DO NOT POST the SMTP conversation in this test in any public space.
Find this line in the dada/DADA/Mail/MailOut.pm file:
my ( $junk, $list, $listtype, $id ) = split( '-', $file );
and change it to:
my ( $junk, $list, $listtype, $id ) = split( '-', $file, 4);
http://sourceforge.net/tracker/index.php?func=detail&aid=1609792&group_id=13002&atid=113002
Workaround for ver. 2.10.11 and 2.10.11b:
Find this line in the dada/DADA/Mail/MailOut.pm file:
my $list_type = $args->{-list_tpe} ? $args->{-list_tpe} : 'list';
and change it to:
my $list_type = $args->{-list_type} ? $args->{-list_type} : 'list';
http://sourceforge.net/tracker/index.php?func=detail&aid=1612943&group_id=13002&atid=113002
http://sourceforge.net/tracker/index.php?func=detail&aid=1606467&group_id=13002&atid=113002
Add this key/value pair somewhere in the Config.pm's %LIST_SETUP_DEFAULTS hash:
find_spam_assassin_score_by => 'looking_for_embedded_headers',
http://sourceforge.net/tracker/index.php?func=detail&aid=1606468&group_id=13002&atid=113002
$VER
should be:
$DADA::Config::VER
You'll know you're hitting this error if you receive error message for this plugin that look like this:
Global symbol "$GOOD_JOB_MESSAGE" requires explicit package name at scheduled_mailings.pl line 404. Global symbol "%MIME_TYPES" requires explicit package name at scheduled_mailings.pl line 1487. Global symbol "$FILE_CHMOD" requires explicit package name at scheduled_mailings.pl line 1652. Execution of scheduled_mailings.pl aborted due to compilation errors.
Workaround for ver. 2.10.11 and 2.10.11b:
If you have a version of scheduled_mailings.pl from ver 2.10.11 or 2.10.11b find this line in scheduled_mailings.pl:
use DADA::Config qw(!:DEFAULT);
and change it to:
use DADA::Config;
http://sourceforge.net/tracker/index.php?func=detail&aid=1613740&group_id=13002&atid=113002
A few small, yet quite annoying bugs were found in the 2.10.11 distribution - 2.10.11 has just a few notable bug fixes:
http://sourceforge.net/tracker/index.php?func=detail&aid=1606467&group_id=13002&atid=113002
http://sourceforge.net/tracker/index.php?func=detail&aid=1607259&group_id=13002&atid=113002
http://sourceforge.net/tracker/index.php?func=detail&aid=1606468&group_id=13002&atid=113002
Do see the changes for the 2.11 alpha series - all changes made in 2.11 alpha will also be for 2.10.11.
Mailing List Messages can now be monitored via the list control panel in great detail.
Note: The addition of this feature has also come with the removal of other features that this feature intends to replace (and do so, in a much better way). If you are looking for these features, note that they have been removed:
Do note that SMTP Sending is still, 100% supported, just that Dada Mail has moved to using the Net::SMTP SMTP engine. Along with a simpler interface, secure, encrypted SMTP connections are now supported, as well as various new authentication schemes.
More information on this feature can be found at the following places:
Technical Details:
http://mojo.skazat.com/support/documentation-dada-2_10_16/NOTES.pod.html#autopickup_of_mail_sendings
Nerdy Perl API Overview:
http://mojo.skazat.com/support/documentation-dada-2_10_16/Mail_MailOut.pm.html
Mailing List Sending FAQ (goes over how to use this feature):
http://mojo.skazat.com/support/documentation-dada-2_10_16/FAQ-mailing_list_sending.pod.html
auto_pickup.pl extension docs (extension that makes use of this feature):
http://mojo.skazat.com/support/documentation-dada-2_10_16/auto_pickup.pl.html
Logging in the Dada Mail usage log still happens and the logging is much more verbose, but batches are not numbered.
More information on Mail-DeliveryStatus-BounceParser:
There are MANY changes between this version and the 2.10 series. Please see:
http://mojo.skazat.com/features/2_11_dev/index.html
for details of the new features.
See the, ``NOTES'' for various things concerning this specific version of Dada Mail.
Being a alpha release, there are known bugs and some unknown bugs. If you do use this version, makes sure to understand that it will be a rocky way.
Something as simple as:
<script>alert('foo')</script>
When submitted in either the, ``add'' or, ``remove'' email subscribers will show the Javascript alert box.
http://sourceforge.net/tracker/index.php?func=detail&aid=1540234&group_id=13002&atid=113002
which also means, you can attempt to automate logging in,
as in a robot trying various logins.
The fix has been to employ an, ``auth_id'' hash that's saved in Dada Mail's list files. Dada Mail will make this hash, when it shows any type of login form. If this auth_id is missing or incorrect, Dada Mail will not allow logging in of a list.
See also the, $DISABLE_LIST_LOGINS Config.pm variable.
http://mojo.skazat.com/support/documentation-dada-2_10_16/Config.pm.html#_disable_outside_logins
Currently, this feature is disabled by default.
http://sourceforge.net/tracker/index.php?func=detail&aid=1535133&group_id=13002&atid=113002
http://example.com/cgi-bin/dada/mail.cgi/admin
The fix has been to allow you to change the query string - in this case, admin to basically whatever you want, given some constraints. See the documentation for the $ADMIN_FLAVOR_NAME and, $SIGN_IN_FLAVOR_NAME Config.pm variables:
http://mojo.skazat.com/support/documentation-dada-2_10_16/Config.pm.html#_admin_flavor_name
http://mojo.skazat.com/support/documentation-dada-2_10_16/Config.pm.html#_sign_in_flavor_name
Currently, the fix is to allow you to just email them the, ``you are already subscribed'' message, instead of showing this information in the web browser. The program will act just as if no problem with a subscription request has happened - this includes any errors it may return, in any sort of format.
This fix is currently disabled, but can be enabled in the Manage List -> Mailing List Options screen.
This is a problem, because it could be unbeknowest to the list password haver, that they have credentials that could unluck more stuff than they should have!
The fix is to have the list password, when set to the same as the root password, act as if it's the list password only. More information, List and Dada Mail Root Passwords -
Also see:
http://sourceforge.net/tracker/index.php?func=detail&aid=1530149&group_id=13002&atid=113002
http://sourceforge.net/tracker/index.php?func=detail&aid=1540194&group_id=13002&atid=113002
http://sourceforge.net/tracker/index.php?func=detail&aid=1539846&group_id=13002&atid=113002
http://sourceforge.net/tracker/index.php?func=detail&aid=1539669&group_id=13002&atid=113002
http://sourceforge.net/tracker/index.php?func=detail&aid=1530146&group_id=13002&atid=113002
Should there are least be a note that says, ``There are no archived messages''
Instead of nothin'? (usability issue, really)
http://sourceforge.net/tracker/index.php?func=detail&aid=1529531&group_id=13002&atid=113002
Now, the ``Other...'' link will only show *if* there's another list to log into.
http://sourceforge.net/tracker/index.php?func=detail&aid=1539659&group_id=13002&atid=113002
[Wed Aug 2 19:23:06 2006] mail.cgi: Can't call method ``param'' on an undefined value at /DADA/App/Session.pm line 261. [Wed Aug 2 19:27:45 2006] mail.cgi: Can't call method ``param'' on an undefined value at /DADA/App/Session.pm line 128.
The reason is unclear for me.
WORKAROUND
* Install a server-wide version of CGI::Session
* Set the $SESSION_DB_TYPE to, ``Classic'' (please see the warning in, KNOWN ISSUES, under, CGI::Session Problems
http://sourceforge.net/tracker/index.php?func=detail&aid=1530173&group_id=13002&atid=113002
...this may be important if the new style, well, Just Doesn't Work Right.
Never use this feature unless you understand the security implications, which are described in detail:
1527704 2.10.9 - Customize Feature Set - Function Unclear (huh?!)'
http://sourceforge.net/tracker/index.php?func=detail&aid=1527704&group_id=13002&atid=113002
This is because the, ``-Function'' isn't set in the $ADMIN_MENU variable in the Config.pm file.
http://sourceforge.net/tracker/index.php?func=detail&aid=1529990&group_id=13002&atid=113002
http://sourceforge.net/tracker/index.php?func=detail&aid=1527007&group_id=13002&atid=113002
There's also a minor security issue here, as the sessions do have a copy of the password, encrypted of course, but still, these file should not stick around.
http://sourceforge.net/tracker/index.php?func=detail&aid=1525557&group_id=13002&atid=113002
http://sourceforge.net/tracker/index.php?func=detail&aid=1539402&group_id=13002&atid=113002
http://example.com/cgi-bin/dada/mail.cgi?f=n
Causes a Server 500 error..
http://sourceforge.net/tracker/index.php?func=detail&aid=1534947&group_id=13002&atid=113002
The fix in place is to show a simple message on what needs to be done. The message itself is located in the list_page_screen.tmpl file.
http://sourceforge.net/tracker/index.php?func=detail&aid=1534939&group_id=13002&atid=113002
http://sourceforge.net/tracker/index.php?func=detail&aid=1533593&group_id=13002&atid=113002
http://sourceforge.net/tracker/index.php?func=detail&aid=1533653&group_id=13002&atid=113002
http://sourceforge.net/tracker/index.php?func=detail&aid=1532861&group_id=13002&atid=113002
If so, the subscription form only has the ``Unsubscribe'' radio button, but it's unchecked, meaning, if you try to unsubscribe to the list, w/o checking this button, you'll fail. That's stupid - it should probably be checked by default.
http://sourceforge.net/tracker/index.php?func=detail&aid=1531985&group_id=13002&atid=113002
They should be explicitly set in the $DEFAULT_LIST_SETTINGS Config.pm variable, just like all the rest of the default settings - perhaps the text itself could be saved in an outside variable, as it's done now, so you if you were tweaking these before, it should work a similar way.
(basically is the workaround)
http://sourceforge.net/tracker/index.php?func=detail&aid=1530017&group_id=13002&atid=113002
http://sourceforge.net/tracker/index.php?func=detail&aid=1528753&group_id=13002&atid=113002
When I click on that option, there are unchecked options, for example:
Manage List|Delete this list Manage Subscribers|Options Customize Feature Set
Being unchecked I would assume that means they would not be operational or displayed? Howver, they are both displayed and operational.
http://sourceforge.net/tracker/index.php?func=detail&aid=1527704&group_id=13002&atid=113002
http://sourceforge.net/tracker/index.php?func=detail&aid=1526615&group_id=13002&atid=113002
http://sourceforge.net/tracker/index.php?func=detail&aid=1526251&group_id=13002&atid=113002
http://sourceforge.net/tracker/index.php?func=detail&aid=1525708&group_id=13002&atid=113002
This should really be rectified in the, Send a List Message, Send a List Message -> Advanced and the Send a Webpage, at the very very least.
http://sourceforge.net/tracker/index.php?func=detail&aid=1525671&group_id=13002&atid=113002
This is because something needs to be in the body of the message, and if both the text and HTML version of the message are blank, you get an error.
http://sourceforge.net/tracker/index.php?func=detail&aid=1523618&group_id=13002&atid=113002
The, ``number of subscribers'' notice in the email is off by exactly the number of addresses the bounce handler has supposively unsubscribed.
http://sourceforge.net/tracker/index.php?func=detail&aid=1523529&group_id=13002&atid=113002
Attempting to override this, either in the Config.pm or in an outside config file (.dada_config), will lead to unexpected results.
This is neither documented, or discourgaged, or whatever.
I propose the behavior be that placing a password in any of these locations automagically encrypts the password transparently, so the program Does What You Tell It, and a warning is placed stating the dangers of placing such a password in there.
That shoud do it.
(Proposal accepted by the propose...ie)
http://sourceforge.net/tracker/index.php?func=detail&aid=1521008&group_id=13002&atid=113002
and the signup form to subscribe to a list - which doesn't work.
This should all just be hidden - no?
http://sourceforge.net/tracker/index.php?func=detail&aid=1520969&group_id=13002&atid=113002
Kind of small and niggling, but it's there.
Click here for more information.
This happens if you don't set the, ``$PROGRAM_URL'' or, ``$S_PROGRAM_URL'', but try to access Dada Mail.
If this information is lacking, it tries to use
CGI.pm's url() method. Sometimes this fails.
You *may* be able to also use the environmental variable,
$ENV{SCRIPT_URI}
and then, if that's blank, use the CGI->url() method.
http://sourceforge.net/tracker/index.php?func=detail&aid=1520960&group_id=13002&atid=113002
http://sourceforge.net/tracker/index.php?func=detail&aid=1520961&group_id=13002&atid=113002
http://sourceforge.net/tracker/index.php?func=detail&aid=1539645&group_id=13002&atid=113002
subscribe() etc, not followhttp://sourceforge.net/tracker/index.php?func=detail&aid=1535188&group_id=13002&atid=113002
[Wed Aug 2 23:12:32 2006] mail.cgi: couldn't remove /home/user/.dada_files/.backups/j/settings/1154581249 Directory not empty at /DADA/App/GenericDBFile/Backup.pm line 176.
For some reason, when it tries to remove all the separate files, some get left behind?
Solution seems to be to feed unlink a list of files to remove, instead of calling unlink again and again.
Probably more efficient, too.
http://sourceforge.net/tracker/index.php?func=detail&aid=1533647&group_id=13002&atid=113002
http://sourceforge.net/tracker/index.php?func=detail&aid=1528774&group_id=13002&atid=113002
dada_settings_dbtosql.pl.html
http://sourceforge.net/tracker/index.php?func=detail&aid=1527084&group_id=13002&atid=113002
Server replied: '235 ok, go ahead (#2.0.0)'
Looks like it comes from a server running Mac OS X/postfix...
http://sourceforge.net/tracker/index.php?func=detail&aid=1533640&group_id=13002&atid=113002
(Note: there was an introduction of a white list feature in the alpha versions of 2.10.9 - this has since been removed from 2.10.9 stable.)
Note: yet again! There was integration of some sorts of SpamAssassin into the dada_bridge.pl plugin in the alpha versions. This also has been removed for 2.10.9 stable
This option currently is only available if you use either the sendmail command, or the Net::SMTP SMTP engine - this leaves out the Mail::Bulkmail SMTP engine, which I haven't yet figured out how to hack to make it work well with this option.
See the, $SESSION_DB Config.pm variable; valid values are:
More information on how to use this and the differences between the two versions is located in the General FAQ:
Each type of bounce has a score associated with it and there's a threshold that needs to be hit to have an email address get unsubscribed. Basically, multiple bounces will unsubscribe an email address, instead of just one, ``hard'' bounce.
More information on this feature is located in the Mystery Girl docs:
http://mojo.skazat.com/support/documentation-dada-2_10_16/dada_bounce_handler.pl.html
* 1455896 2.10.7 - Server Error 500 error in SMTP options page
http://sourceforge.net/tracker/index.php?func=detail&aid=1455896&group_id=13002&atid=113002
Pretty easy to set up, create the table located in dada/extras/SQL/dada_settings.sql - which is:
CREATE TABLE dada_settings ( list text, setting text, value text );
and set the, $SETTINGS_DB_TYPE to MySQL, or Postgres
DB FIle to *SQL migration isn't too hard, see the script, dada_settings_dbtosql.pl in the dada/extras/scripts directory,
Whose instructions are:
Name dada_settings_dbtosql.pl Description Cute name, huh?
Basically, this small script takes the information of a Dada Mail list
settings in the DB File and ports it to the MySQL format.
Fairly simple and straightforward.
How to use this script * Backup Everything SQL tables, list files (all of them)
* Create the List Settings SQL table
The SQL statement to run should be saved in a file called
*dada_settings.sql* which is located in the *dada/extras/SQL*
directory of the distribution
* Set $SETTINGS_DB_TYPE to the correct SQL type (MySQL, Postgres)
Directions are located in the Config.pm about this, search for,
*$SETTINGS_DB_TYPE*
* Fill in %SQL_PARAMS in the Config.pm file
Again, directions should be supplied in the Config.pm file.
After the above (do not skip a step) are done, make sure Dada Mail is
still running by visiting it in your webbrowser. The program should run
as if no lists existed - not to worry! We shall fix that soon enough.
Upload this script into the same directory that you have the *mail.cgi*
script in, and run it, either from your web browser, or via the command
line.
That should be it.
ps. backup everything.
=item * Option to add Subscription form in rss/atom feed entries. (enabled by default)
https://sourceforge.net/tracker/index.php?func=detail&aid=1439436&group_id=13002&atid=113002
=item * 1438834 2.10.6 - Invitation Subscribers Never Removed w/SQL backend?
https://sourceforge.net/tracker/index.php?func=detail&aid=1438834&group_id=13002&atid=113002
Bugs Fixed: