The majority of changes in this release deals with stability and documentation.
The Clickthrough Tracker works again and the URL's are now (mostly) just string of numbers, instead of attempting to save the enitre URL you're redirecting to. This is a pretty good thing.
Email Message Templates can now support HTML::Template::Expr syntax
Partial List Sending Options are now supported by Beatitude.
Beatitude now bears a resemblence to the rest of Dada Mail's list sending screens, instead of looking completely different.
The, -odq sendmail flags are set by default. If mail sending isn't working, try taking these flags off, it may be an incompatibility.
I'm in sort of a tough spot, since these flags don't always work, but having them on makes life easier for the mail server.
I think I'm siding on the mail server in this case.
http://downloads.sourceforge.net/mojomail/dada-2_11_alpha_9.tar.gz
http://downloads.sourceforge.net/mojomail/dada-2_11_alpha_9.zip
Things are broken - this is an alpha release - don't use for production work, please.
Some things we know are completely busted:
The clickthrough tracker won't work - the redirect tags are never parsed. These will return soon enough.
I'm not sure if the Update Subscription extension works. It doesn't know about multiple fields and using it will most likely erase any information saved in these fields. The Multiple Subscribe Extension should work just swimmingly, though.
Most, if not all of the error messages that were in the DADA::App::Error module have been moved out of the module and into the, dada/DADA/Template/templates directory. Each error message has its own template file. Most, if not all of the error message file names start with, ``error_''.
Email Templates now use HTML::Template (yes, for plain text emails too) for the backend, instead of random and dispersed simple regexes that have been in use for 8 or so years. Depending on the email being sent out, list settings and subscriber information is automatically passed to HTML::Template to be used when outputing.
Currently, only the HTML::Template way of doings things is supported, but adding HTML::Template::Expr is a possibility.
Care has been given to allow a graceful backwards compatibility with older email templates and most older email templates will work without problem. One exception is the, ``List Invitation'' email template - this template should be reverted to the default that's shipped with this release.
For more information, see the documentation for, screen in DADA::Template::Widgets - it's currently the wrapper around HTML::Template for Dada Mail.
The, Send a List Invitation feature is still a part of Dada Mail, but it's functionality has been moved from it's own stand-alone administration screen to a part of the Add Email steps. After verification of new subscribers, you now have the choice of subscribing or inviting the verified addresses.
There's been some confusing amongst... amongst myself in some of the terms used in Dada Mail - one of them is the, ``Black List'' - is it, ``Blacklist'', or, ``Black List?''
I've decided on, ``Black List''. Some list settings are named, ``black_list_*'' and some are named, ``blacklist_*''
These currently won't change, but the error paramaters have. They should all be, black_list
The DADA::Template::Widgets screen subroutine has gone through significant changes - one of the largest is the move from passing paramaters in a hash, to passing paramaters in a hashref. All the old paramaters will work (and there's a slew of new, optional ones, but these paramaters must be passed in a hashref. So:
print DADA:Template::Widgets::screen(-screen => foo.tmpl); # No!
print DADA:Template::Widgets::screen({-screen => foo.tmpl}); # Yes!
The idea behind the tags (like): tags: [plain_list_subscriber_link] was stupid and their use is now dropped. Use list_subscriber_link instead. The only difference is that for HTML email messages, [list_subscriber_link] will not automatically become a clickable link - you'll have to make that yourself.
The email message templates in the list control panel under, ``Manage Copy -> Email Templates'' can now have their Subjects and in some instances To: and From: phrases editable.
Many of the email message template tags have been modified - most of the modifications are simple and make sense. A small rundown:
Anything that has to do with a list setting, now has, list_setting. appended to it. For example:
Anything that has to do with a subscriber now has subscriber.] appended to it. For example:
Documentatoion still needs to be written concerning these changes. Old email templates should work, as they are auto-translated to this new syntax.
If you don't set an error log, one will now be made for you, automatically. The rub on this is errors made during compile time won't be logged.
http://downloads.sourceforge.net/mojomail/dada-2_11_alpha_8.tar.gz
http://downloads.sourceforge.net/mojomail/dada-2_11_alpha_8.zip
This release sports a very large new feature: Multiple subscriber fields. For an overview of this feature, do see:
mojo.skazat.com/support/documentation-dada-2_11-alpha_8/subscriber_fields_in_2_11.pod.html
No, really - it's in there. Check it out. You'll need the SQL backend. For a large list of improvements, do see:
mojo.skazat.com/support/documentation-dada-2_11-alpha_8/subscriber_fields_in_2_11.pod.html
Of note, this feature also has the below features that relate to it:
The dada_bridge.pl plugin name has been modified to, Dada Bridge, lest we figure out a more clever name. We're still going through the documentation and changin' stuff
If you were fond of the original Dada Mail, ``moderation'' sytem, this is basically it again, relabled, ``Authorized Senders''.
The Authorized Senders is a sublist in Dada Mail. It contains a list of email addresses that are allowed to post a message to a Dada Mail list.
This is most extremely useful for announce-only lists, where you'd like to give posting access to someone other than the list owner.
White List support is back after a little break. The white list is a sublist of Dada Mail list that allows you to specify a list of addresses that are allowed to subscribe. It's basically the opposite of the blacklist.
SQLite is now completely up to par with the other backends. I doubt I'd suggest it as a backend, but it's an option and is used for testing.
This support is very spotty and probably is broken at the moment. Go go alpha code. More information:
Added a silly calculator to tell you how long a sending will probably be. It's in AJAX
``Stuck'' Mailouts shouldn't really happen anymore.
The Config variable, $DEBUG_TRACE is now populated with a few module names, example: DADA_Mail_Send. Setting this name to a value of, 1 will print many lines in your error log for things pertaining to the DADA::Mail::Send module.
A word of warning about using the $DEBUG_TRACE stuff - the implementation isn't very complete for any module and what's implemented may not make sense to anyone but me. Be aware: Thar be dragons.
(partial) Support is current there for the DADA::Mail:Send, DADA::Mail::Mailout and DADA::App::Subscriptions modules.
Font sizes have been changed from px to em's.
Removed the following templates:
Added:
http://downloads.sourceforge.net/mojomail/dada-2_11_alpha_7.tar.gz
http://downloads.sourceforge.net/mojomail/dada-2_11_alpha_7.zip
This is a features-focused release. Most of the relevent bugs that cropped up in the 2.10.15 release of Dada Mail should be patched up in this version of Dada Mail (2.11 Alpha 7) but aren't verified.
Please refer to the 2.10.16 changelog for specifics on bugs fixed. The 2.10.16 release is a bugfix-only release and should be the current distribution used for production websites.
Most all plugins and extensions currently shipping in the 2.11 alpha 7 build of Dada Mail will need to be run with 2.11 alpha 7. No other previous version of Dada Mail will work.
All the plugins/extensions available for Dada Mail (by me) are available in the 2.11 alpha 7 release. Furthermore, any restrictions on list size, or max # of lists has been lifted. This is to help you test the program out and find bugs.
Do note that this is an ALPHA release and is known to not always work correctly. It SHOULD NOT be used on a production server
Also see the New Features docs for 2.11 alpha 6.
The MySQL, Postgres and SQLite tables have been optimized for performance and speed. Most of the changes deal with the data TYPE of the different fields. You may want to study the new schemas and see how they differ to the old schemas that were shipped -
The old schemas should work with this new alpha, so if you don't want to update your SQL tables that deal with Dada Mail, it's not required.
The MySQL schema has indexes added to the schema. These schemas are not verified and need to be tested. Feedback welcome!
If the SQLite backend didn't work (it wasn't actually working for us) try this new alpha version. We're probably keeping SQLite along for SQL backend testing purposes, as it's dead easy to use for such a task.
If you were testing the SQLite backend, note that the entire schema is probably completely different. We're now basing it on the MySQL schema, instead of the Postgres schema.
In the popup menus in the Restore Lists screen, you can now see how many entries are available for each saved backup.
http://downloads.sourceforge.net/mojomail/dada-2_11_alpha_6.tar.gz
http://downloads.sourceforge.net/mojomail/dada-2_11_alpha_6.zip
This is a features-focused release. Most of the relevent bugs that cropped up in the 2.10.14 release of Dada Mail should be patched up in this version of Dada Mail (2.11 Alpha 6) but aren't verified.
Please refer to the 2.10.15 changelog for specifics on bugs fixed. The 2.10.15 release is a bugfix-only release.
Most all plugins and extensions currently shipping in the 2.11 alpha 6 build of Dada Mail will need to be run with 2.11 alpha 6. No other previous version of Dada Mail will work.
All the plugins/extensions available for Dada Mail (by me) are available in the 2.11 alpha 6 release. Furthermore, any restrictions on list size, or max # of lists has been lifted. This is to help you test the program out and find bugs.
Do note that this is an ALPHA release and is known to not always work correctly. It SHOULD NOT be used on a production server
Also see the New Features docs for 2.11 alpha 5, if you're usually running 2.10.14.
Some of the plugins/extensions currently supported are:
See also the $PLUGIN_CONFIGS Config.pm variable.
See the Beatitude Docs, most specifically the,
plugin variables.
The method to do so should be the same for Beatitude (Mail Scheduler), Mystery Girl (Bounce Handler) and dada_bridge.pl
See the $Plugin_Config-{FCKeditor_Support}> var in dada/plugins/scheduled_mailings.pl for more information.
You don't need to use the --run flag when running scheduled_mailings.pl from the command line.
See the dada_bridge.pl Docs, most specifically the,
plugin variables.
The method to do so should be the same for Beatitude (Mail Scheduler), Mystery Girl (Bounce Handler) and dada_bridge.pl
You'll see lines, such as these in the Dada Mail usage log ($PROGRAM_USAGE_LOG)
[Wed Jun 20 03:55:04 2007] listname 12.34.12.34 Subscription
Confirmation Sent for listname.list user@example.com, remote_host:,
ip_address:120.0.0.1
[Wed Jun 20 04:05:38 2007] listname 12.34.12.34 Unsubscription
Confirmation Sent for listname.list user@example.com, remote_host:,
ip_address:120.0.0.1
To let you know what's happening.
See the Mystery Girl Docs, most specifically the,
plugin variables.
The method to do so should be the same for Beatitude (Mail Scheduler), Mystery Girl (Bounce Handler) and dada_bridge.pl
Note! Your old scorecard is probably not going to be of much use anymore;
Helpful to see why they may be bouncing.
We've enabled the use of the MailHide CAPTCHA idea for email addresses in the list archive messages. You also have the option to use no protection at all, or keep the default protection scheme (called, SPAM-me-not)
More information on Mailhide:
http://mailhide.recaptcha.net/
See also the Config.pm variable, $RECAPTHCA_MAILHIDE_PARAMS
The options to protect email addresses in the list's archives is availabl ein the list control panel under, Manage Archives - Archive Options - Advanced
Should work for Session information, list subscribers, settings and archives.
We've added support for the reCAPTCHA project in Dada Mail. Here's more information on it:
In Dada Mail, see the following variables:
To use the reCAPTCHA system, you'll need to set this variable to, ``reCAPTCHA''
You'll need to plug in the, public_key and private_key variables.
The following locations hold the various SQL table schemas needed for the SQL backends:
dada/extras/SQL/postgres_schema.sql
dada/extras/SQL/mysql_schema.sql
dada/extras/SQL/sqlite_schema.sql
Originally, we were using Net::POP3, but have now moved to Mail::POP3Client.
Amongst other things, you can now connect to a POP3 server via SSL and also set the type of authentication scheme you want to use.
You'll see the options in the Manage List - Sending Options - SMTP Options, as well as in Mystery Girl and dada_bridge.pl.
Used specifically in the, ``Send a Webpage'' screen, using this tag in the message itself, will have the tag be replaced with the actual URL you're getting the message source from. For example, in your message, you can write:
<p> <a href="[originating_message_url]"> If you cannot see this message, click here! </a> </p>
DADA::App::POP3Tools Holds all the stuff needed for POP3 connections and replaces the various, independent schemes in dada_bounce_handler.pl, dada_bridge.pl and the DADA::Mail::Send module.
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.
https://sourceforge.net/tracker/index.php?func=detail&aid=1710309&group_id=13002&atid=113002
https://sourceforge.net/tracker/index.php?func=detail&aid=1712412&group_id=13002&atid=113002
https://sourceforge.net/tracker/index.php?func=detail&aid=1712400&group_id=13002&atid=113002
https://sourceforge.net/tracker/index.php?func=detail&aid=1712412&group_id=13002&atid=113002
https://sourceforge.net/tracker/index.php?func=detail&aid=1713638&group_id=13002&atid=113002
https://sourceforge.net/tracker/index.php?func=detail&aid=1713641&group_id=13002&atid=113002
https://sourceforge.net/tracker/index.php?func=detail&aid=1714705&group_id=13002&atid=113002
https://sourceforge.net/tracker/index.php?func=detail&aid=1714728&group_id=13002&atid=113002
https://sourceforge.net/tracker/index.php?func=detail&aid=1714725&group_id=13002&atid=113002
https://sourceforge.net/tracker/index.php?func=detail&aid=1704711&group_id=13002&atid=113002
https://sourceforge.net/tracker/index.php?func=detail&aid=1701826&group_id=13002&atid=113002
https://sourceforge.net/tracker/index.php?func=detail&aid=1692100&group_id=13002&atid=113002
https://sourceforge.net/tracker/index.php?func=detail&aid=1693199&group_id=13002&atid=113002
https://sourceforge.net/tracker/index.php?func=detail&aid=1693371&group_id=13002&atid=113002
https://sourceforge.net/tracker/index.php?func=detail&aid=1699829&group_id=13002&atid=113002
https://sourceforge.net/tracker/index.php?func=detail&aid=1699838&group_id=13002&atid=113002
https://sourceforge.net/tracker/index.php?func=detail&aid=1696684&group_id=13002&atid=113002
https://sourceforge.net/tracker/index.php?func=detail&aid=1695274&group_id=13002&atid=113002
https://sourceforge.net/tracker/index.php?func=detail&aid=1679568&group_id=13002&atid=113002
https://sourceforge.net/tracker/index.php?func=detail&aid=1693368&group_id=13002&atid=113002
https://sourceforge.net/tracker/index.php?func=detail&aid=1688094&group_id=13002&atid=113002
https://sourceforge.net/tracker/index.php?func=detail&aid=1684126&group_id=13002&atid=113002
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.
https://sourceforge.net/tracker/index.php?func=detail&aid=1704711&group_id=13002&atid=113002
https://sourceforge.net/tracker/index.php?func=detail&aid=1701826&group_id=13002&atid=113002
https://sourceforge.net/tracker/index.php?func=detail&aid=1692100&group_id=13002&atid=113002
https://sourceforge.net/tracker/index.php?func=detail&aid=1693199&group_id=13002&atid=113002
https://sourceforge.net/tracker/index.php?func=detail&aid=1693371&group_id=13002&atid=113002
https://sourceforge.net/tracker/index.php?func=detail&aid=1699829&group_id=13002&atid=113002
https://sourceforge.net/tracker/index.php?func=detail&aid=1699838&group_id=13002&atid=113002
https://sourceforge.net/tracker/index.php?func=detail&aid=1696684&group_id=13002&atid=113002
https://sourceforge.net/tracker/index.php?func=detail&aid=1695274&group_id=13002&atid=113002
https://sourceforge.net/tracker/index.php?func=detail&aid=1679568&group_id=13002&atid=113002
https://sourceforge.net/tracker/index.php?func=detail&aid=1693368&group_id=13002&atid=113002
https://sourceforge.net/tracker/index.php?func=detail&aid=1688094&group_id=13002&atid=113002
https://sourceforge.net/tracker/index.php?func=detail&aid=1684126&group_id=13002&atid=113002
This is a features-only release and doesn't contain bug fixes. For a bugfix-only development release, do see 2.10.14 beta 1,
This is a features-only release and doesn't contain bug fixes. For a bugfix release, do see 2.10.14 Stable.
2.11 Alpha 5 is basically based on Dada Mail, version 2.10.13 (again, NOT 2.10.14)
http://downloads.sourceforge.net/mojomail/dada-2_11-alpha_5.tar.gz?download
http://downloads.sourceforge.net/mojomail/dada-2_11-alpha_5.zip?download
See the New Feature in 2.11 Alpha 4 - it's basically the same.
This is a features-only release and doesn't contain bug fixes. For a bugfix-only development release, do see 2.10.14 beta 1,
http://downloads.sourceforge.net/mojomail/dada-2_11-alpha_4.tar.gz?download
http://downloads.sourceforge.net/mojomail/dada-2_11-alpha_4.zip?download
This variable sets how many different mailouts may go out from an installation of Dada Mail at one time. Conservatively, this is set to, 1 by default.
There are a few reasons why you wouldn't want to set this to any higher limit, one being that there's a possibility that there is a limit on how many email messages you are allowed to go out in a specific period of time.
Another reason is that sending out too many messages at once may cause the server your running to be overloaded.
$MAILOUT_STALE_AFTER sets, in seconds, how long a mailout can go with no mailing activity until Dada Mail itself won't automatically restart it. The default, 86400 seconds is one full day.
This variable attempts to safegaurd you against having a dropped mailing that you've, ``forgotten'' about restart, ``mysteriously'' and unintentionally.
A mailout may still be restarted if this limit has been surpassed, but it must be done manually, through the list control panel.
This should allow you to keep tags on all your mailings for a list at once, without having to visit each individual screen.
This screen will also reload a mailing, if necessary (just like the individual screens)
You now have the ability to pause a mailing, instead of simple stopping a mailing. A stopped mailing cannot ever be restarted, a paused mailing may be restarted with ease
WIth the Mailout At Once Limit, Dada Mail now supports queueing of awaiting mailouts.
See The writeup here:
for a brief overview on how pausing and queueing work in Dada Mail.
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_11-alpha_10/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_11-alpha_10/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_11-alpha_10/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_11-alpha_10/dada_tester.cgi.html
https://sourceforge.net/tracker/index.php?func=detail&aid=1626608&group_id=13002&atid=113002
https://sourceforge.net/tracker/index.php?func=detail&aid=1634573&group_id=13002&atid=113002
https://sourceforge.net/tracker/index.php?func=detail&aid=1639133&group_id=13002&atid=113002
https://sourceforge.net/tracker/index.php?func=detail&aid=1627577&group_id=13002&atid=113002
https://sourceforge.net/tracker/index.php?func=detail&aid=1638183&group_id=13002&atid=113002
https://sourceforge.net/tracker/index.php?func=detail&aid=1638187&group_id=13002&atid=113002
https://sourceforge.net/tracker/index.php?func=detail&aid=1639138&group_id=13002&atid=113002
https://sourceforge.net/tracker/index.php?func=detail&aid=1641124&group_id=13002&atid=113002
The SMTP SASL Authentication tester was removed in 2.10.11 and was based on the Mail::Bulkmail module, which was also removed in 2.10.11.
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.
Workaround for ver. 2.10.11 and 2.10.11b:
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
Sending a list invitation doesn't send the invitation to a list of hopeful subscribers, it sends it TO your subscribers.
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=1610543&group_id=13002&atid=113002
You're using the SQL backend (either MySQL or Postgres) for your list's settings backend and you attempt to save a password setting - it may fail.
http://sourceforge.net/tracker/index.php?func=detail&aid=1606467&group_id=13002&atid=113002
http://sourceforge.net/tracker/index.php?func=detail&aid=1611114&group_id=13002&atid=113002
http://sourceforge.net/tracker/index.php?func=detail&aid=1607259&group_id=13002&atid=113002
Workaround for ver. 2.10.11 and 2.10.11b:
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
http://sourceforge.net/tracker/index.php?func=detail&aid=1611105&group_id=13002&atid=113002
The Config.pm vars aren't being imported by default, so they need (and currently aren't) called directly, ala:
$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
http://sourceforge.net/tracker/index.php?func=detail&aid=1608203&group_id=13002&atid=113002
http://sourceforge.net/tracker/index.php?func=detail&aid=1608202&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:
(Note: That this only affects people who are using the SQL backend for list settings.
http://sourceforge.net/tracker/index.php?func=detail&aid=1606467&group_id=13002&atid=113002
This bug affects only those who are using dada_bridge.pl for discussion lists with moderation.
http://sourceforge.net/tracker/index.php?func=detail&aid=1607259&group_id=13002&atid=113002
This bug affects only those who are trying to use the dada_bridge.pl plugin
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:
The Mail::Bulkmail SMTP engine hasn't been updated by the author in more than three years, so we're not too sure if there will ever be updates and/bug fixes in the futre for it. Its addition to Dada Mail came at a great expense of added complexity
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.
Batch completed messages via email has been removed - but are still logged and are logged in much greater verbosity. The web-based monitoring tool does do a better job in telling you exactly where a mailing is, so should be used instead.
This feature was basically the answer to what you do if a mailing was dropped. It wasn't very fun to use and since mailings now are auto-reloaded automatically, it's presence is no longer needed.
You will notice that you can only set batches between 1 and 60 addresses, and then time between 1 and 60 seconds. Although this seems constrictive, this should allow you to set message sending between 60 messages an hour and 216,000 messages an hour, which should work for almost all circumstances.
More information on this feature can be found at the following places:
Technical Details:
Nerdy Perl API Overview:
http://mojo.skazat.com/support/documentation-dada-2_11-alpha_10/Mail_MailOut.pm.html
Mailing List Sending FAQ (goes over how to use this feature):
http://mojo.skazat.com/support/documentation-dada-2_11-alpha_10/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_11-alpha_10/auto_pickup.pl.html
Use the auto-pickup feature. Will work MUCH better
We've now completely moved to Net::SMTP
Batches could theoretically fail mid-batch, but the auto-pickup feature would reload the mailing at the correct email address. This does cause the batch # to be incorrect. To simplify everything, this feature has been dropped.
Logging in the Dada Mail usage log still happens and the logging is much more verbose, but batches are not numbered.
This only work with the Mail::Bulkmail backend, which has also been dropped.
Mystery Girl now takes advantage of the Mail-DeliveryStatus-BounceParser CPAN module, in conjunction with its own bounce parser routines (not replaced, in other words)
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.
This is a simple check, that should be dealt with.
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
Meaning, you don't *have* to use the login form - as long as you know the variables that have to be passed to Dada Mail, you can log in anywhere -
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.
Currently, this feature is disabled by default.
http://sourceforge.net/tracker/index.php?func=detail&aid=1535133&group_id=13002&atid=113002
It's easy to guess what the main administration login screen is - 'cause it's always the same -
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_11-alpha_10/Config.pm.html#_admin_flavor_name
http://mojo.skazat.com/support/documentation-dada-2_11-alpha_10/Config.pm.html#_sign_in_flavor_name
The, ``You're already subscribed!'' error that is received if you try to subscribe to a list, that you're already subscribed to, could be seen as a way to find out private information about someone, if an individual enters an email address that actually, isn't theres. The chance that someone would do this seems slim, but it is a hole that should be plugged.
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.
will act like the root password!
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 -
Tied closely to the above bug - List Passwords can be set - by default *to* the root password. Since you need the root pass to create a new list, it's alright to say, ``hey, you just set the list pass to the root pass - don't do that!''
Also see:
http://sourceforge.net/tracker/index.php?func=detail&aid=1530149&group_id=13002&atid=113002
In the, ``Manage Appearance -> Edit Template'' screen. This makes it hard to debug template problems that use an outside URL.
http://sourceforge.net/tracker/index.php?func=detail&aid=1540194&group_id=13002&atid=113002
Any archived message that has a blank subject line will have its navigation broken, since the link is made up soley of the Subject line. Currently the solution is to put the default subject line in its place (The default defaults to, (no subject)
http://sourceforge.net/tracker/index.php?func=detail&aid=1539846&group_id=13002&atid=113002
None of the Timestamp options actually do work. (fixed of course)
http://sourceforge.net/tracker/index.php?func=detail&aid=1539669&group_id=13002&atid=113002
The breakcrumbs for the archive search results doesn't have, well, ``Archives'' in the train of breadcrumbs. This is add, since an individual archived messages will. This should be fixed!
http://sourceforge.net/tracker/index.php?func=detail&aid=1530146&group_id=13002&atid=113002
An unhelpful screen of blank stuff.
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
http://sourceforge.net/tracker/index.php?func=detail&aid=1528324&group_id=13002&atid=113002
Basically a usability issue, if you only have one list, and that list isn't hidden, you'll still see the, ``other...'' link to log into that mysterious second, hidden list.
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
These sorts of errors happen sometimes:
[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=1531088&group_id=13002&atid=113002
Which means, when you try to log back in again, you'll be greated with the, ``You're still logged in, bucko!'' error and the session information gets stale and hangs around for what seems, forever.
http://sourceforge.net/tracker/index.php?func=detail&aid=1530173&group_id=13002&atid=113002
http://sourceforge.net/tracker/index.php?func=detail&aid=1530156&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:
You explicitly turn off the screen in the, ``Customize Feature Set'' screen. Somewhat related to this bug:
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
Similar error to, 1530173 2.10.9 - changing a list password fails to log out user..
http://sourceforge.net/tracker/index.php?func=detail&aid=1527007&group_id=13002&atid=113002
Which means, they stick around for what seems like forever. Logins that fail should have the session information removed, as it's useless, if the information is incorrect, outdated, etc.
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.
When I use mysql to save the sessions, every time I enter the wrong password to the list administration, it inserts multiple records to the dada_sessions table. With every time I input a wrong password it seems to increase the number of records that inserts into the table. This cause the logging page to get slower and slower every time.
http://sourceforge.net/tracker/index.php?func=detail&aid=1525557&group_id=13002&atid=113002
... is there, but the feature went away, many moons ago.
http://sourceforge.net/tracker/index.php?func=detail&aid=1539402&group_id=13002&atid=113002
Simply going to:
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
and you get redirected to the list page - with no real description of what may have been the problem
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
If you sub/unsubscribe to a list from an outside form, and that form is not created correctly, for example: the list shortname is entered wrong (or not there at all), no error is reported - you're just shown the default screen. There should at least be an error on that screen stating, ``hey chump, here's the deal''
See the NOTES section about this under, List Subscription Errors - When Are The Catched?:
Similar to the above bug.
http://sourceforge.net/tracker/index.php?func=detail&aid=1533593&group_id=13002&atid=113002
A simple Javascript check woul do wonders in this situation...
http://sourceforge.net/tracker/index.php?func=detail&aid=1533653&group_id=13002&atid=113002
This button is showed if you limit the number of sub/unsub confirmations that you send out.
http://sourceforge.net/tracker/index.php?func=detail&aid=1532861&group_id=13002&atid=113002
A list is closed -
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
... in an outside config file, since it's sort of mysterious how they're added to the list settings file - indeed they are in the DADA::MailingList::Settings module, sort of magically.
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
... are present.
Or should I say, is in order, but is order of the listshortname (which is useless), instead of the List Name - which is the human readable thingies, and this program is written for humans.
http://sourceforge.net/tracker/index.php?func=detail&aid=1528753&group_id=13002&atid=113002
The ``Customize Feature Set'' menu item is rather confusing.
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
And this is dumb - since the first form will be *broken* and will lead to genereal co