Error FAQ

The Dada Mail Error FAQ


This FAQ is split up into two parts:

The first part will assist you in getting Dada Mail to be more verbose in its error reporting.

The second part will help diagnose the errors it's reporting.

Please Read Before:

Please make sure you've read both the basic installation instructions at:

and The tour at:

Many things are explained in those pages.

The, Known Issues docs also list problems that we know about:

Part One: Error Messages

Generally, Dada Mail will report errors in its own Error Log.

You will probably need to set up the path to this error log yourself.

If you do not set up this error log, errors will also probably be reporting in your web browser. Not all errors are reported there and in some cases, some errors are only reported inside the error log.

Set up the Dada Mail Error Log

The Program Error Log isn't created automatically! You will have to manually set it up. This procedure isn't too hard and is explained at:

Making the Error Log More Verbose (%CPAN_DEBUG_SETTINGS)

Dada Mail using Perl modules from various sources - mostly CPAN. Each of these modules is written by a different person/persons and usually have their own way of setting debug/tracing levels.

In Dada Mail, the CPAN modules that have a debugging/tracing scheme are listed in the, %CPAN_DEBUG_SETTINGS variable. More information:

Enabling debugging settings in these modules may help debug issues such as:

Big Huge Note: If you do post a question about an error to the Dada Mail support boards or dadadev mailing list, the first thing you're usually going to be asked is error log snippets. Please save us the need to ask you and have these already available.

Making the Error Log More Verbose ($DEBUG_TRACE)

Some of the various modules that make up Dada Mail also have their own debug tracing modes. A few things to get clear before we get into setting those:

  • It's advanced hacker stuff

    The logs that will be written will be pretty geeky. It's not meant to help with a moment of clarity, they're there to give you a lot of feedback. Setting them will make you have to wade through a lot of stuff.

  • Not everything is tracebable

    Only a few modules have debug tracing at the moment.

  • Work in progress!

    Even the modules that do have tracing enabled are set in stone - there's no debug tracing API.

As of version 3.0 of Dada Mail, the following modules have debug tracing:

Part Two: Diagnosis Error Messages

Dada Mail isn't working

That's not much to go on, Why isn't it working? If you don't have a clue, find out as much about the server and its software that you can and read on, brave soul!

Dada Mail gives me a 'Server Error 500' Message when I first start it

Check to see that you:

Problems Logging In

Sometimes, people find that it's impossible to log into Dada Mail's list control panel.

Some things to double-check:

If those problems don't help matters, sometimes it helps to set Dada Mail to use a different session type.

The session type is set in the config variable, $SESSION_DB_TYPE. It can be set to, SQL (you'll need to setup the SQL backend for this to work), DB, PlainText - and, if all else fails, Classic.

All these session types work the same way, but Classic is the least secure - we don't recommend using it, but if it helps you get out of a pinch, then it can help you get out of a pinch.

Duplicate Email Addresses in Your Mailing List

If there are duplicate email addresses in your mailing list, please open up a bug report.

At least in the Dada Mail program, duplicates should never be present.

If you are edited the plain text list files (if you're using the default back end), or if you're using the SQL dada_subscribers SQL backend directly, then all bets are off, in terms of duplicates. You CAN, easily add duplicates to a mailing list by working with the backends directly. We suggest not doing this, but rather, using the provided Perl API.

cannot do statement (at add_subscriber)! Duplicate entry '0' for key 1

I've seen this error, when the Dada Mail SQL database isn't imported correctly. My advice is to export your list from within Dada Mail's List Control Panel (Your Subscribers -> View, Open List in New Window) Drop the dada_subscribers table, recreate the table and subscribe the subscribers back into your database via Dada Mail's list control panel (Your Subscribers -> Add)

Died at /usr/lib/perl5/5.8.8/ line 85

Upon visiting Dada Mail in your web browser, you get this fairly unhelpful message:

 Died at /usr/lib/perl5/5.8.8/ line 85.
 BEGIN failed--compilation aborted at /DADA/MailingList/ line 11.
 Compilation failed in require at mail.cgi line 172.
 BEGIN failed--compilation aborted at mail.cgi line 172.

Most likely what's happening is this:

The server you're running Dada Mail on doesn't have a DB file type available. Solution? Use the SQL backends.

If this happens after a server upgrade and a Dada Mail installation that was working, suddenly doesn't, yell at your webhost for taking away support for a DB file backend. I'd say something like:

 Dear Web Host, 
 I was using your fine service, until one day I realized
 you had taken away support for the Berkeley DB database ( or similar) library 
 -- Your Name

If they do, your Dada Mail may magically work. If they don't, restore your lists (instructions are in this FAQ). If *that* doesn't work, you may have to switch to the SQL backend anyways and manually recreate your lists. Thems the breaks, I guess.

Dada Mail works great! Until I try to create a new list...

Once I fill out all the information and click the submit button, the program returns a 500 error message. What's going on?

Most likley, Dada Mail does not have enough permissions to write files into the directory you supplied in the $FILES variable - (If you're using the advanced setup, we're also talking about the $ARCHIVES, $BACKUPS, $TEMPLATES, $TMP and $LOGS directories.)

This usually occurs if the UNIX user that created the directory differs from the UNIX user that Dada Mail is running as. For example, sometimes cgi scripts, like Dada Mail are run as, "nobody", or, "apache", for security reasons. If this is the case, you're going to have to change the permissions of the directories mentioned to: 777.

Note that this gives everyone who has access to these directories read/write permission, so be careful when applying this chmod. If you're uncomfortable doing this, see if you cannot run Dada Mail using a wrapper script. A wrapper script allows you to run a cgi script using a different UNIX user - usually whichever one is associated with your usual login username. A common wrapper script is one called, CGIWrap.

Confirmation Messages just seem to loop! What's going on?

If you upgraded Dada Mail from a version lower than 2.9, you're going to have to update your email messages. See this FAQ:

If you have many lists and changing each and every one doesn't seem to be a fun thing, Try using the below script:

 use strict;
 use lib qw(./ ./dada ./dada/DADA ./dada/DADA/perllib); 
 use CGI::Carp qw(fatalsToBrowser);
 use DADA::Config;
 use DADA::App::Guts; 
 use DADA::MailingList::Settings; 
 use CGI qw(:standard); 
 print header(); 
 print '<pre>'; 
 for my $list(available_lists()){ 
     print "working on $list...\n"; 
     my $ls = DADA::MailingList::Settings->new({-list => $list}); 
     my $li = $ls->get; 
     for my $msg('confirmation_message', 'unsub_confirmation_message'){ 
         $li->{$msg} =~ s/\[list_unsubscribe_link\]/\[list_confirm_unsubscribe_link\]/g;
         $li->{$msg} =~ s/\[list_subscribe_link\]/\[list_confirm_subscribe_link\]/g;
         confirmation_message       => $li->{confirmation_message}, 
         unsub_confirmation_message => $li->{unsub_confirmation_message}, 
 print "\n\ndone."

Regular sending works great! Mailing List Messages to the entire list never finish!

If you're running anything before version 2.10.11, consider upgrading - 2.10.11 has a feature that'll monitor mailings fairly closely and reload a dropped mailing. Here's more information on that:

For reasons on why it may be getting stopped, or if you're using a version below 2.10.11 read on:

Find out the following before proceeding:

If you cannot find a limit to your sending capabilities and your resource limits aren't the problem, here are things to check:

  • Mail Server is Bogged Down

    Even if you don't have any sending limitations, you may just be overwhelming the mail server. Again, adjust the batch settings as appropriate.

    If you're using the sendmail command, you may look into the various flags you can set in the variable, $MAIL_SETTINGS that will force messages to queue up, instead of attempting to be send right away. NOTE: that using a queueing flag will cause a pause before sending that is very noticeable (could be, 15, 30 minutes)

  • account user has no limitations - does the user running Dada Mail have any?

    Sometimes CGI scripts, like Dada Mail are run via the webservers user, instead of your own; they may have different resource limitations that you do.

(Note: The below suggestion will not work after version 2.10.10 of Dada Mail - use the auto-pickup feature instead. It should work 100x better.)

If none of this is working, and you're in a pinch and it's 3:00 am and you need to get this mailing out now, Dada Mail has an option to send a list messsage from a particular part of your list.

Log into your list control panel and when you get to the, "Send a Message" screen, click, "advanced".

At the bottom of the form, you should see the option to send your message from a particular part of your list.

To figure out where your list might have stopped at, consult the batch completed messages. If you didn't setup batchings, consult the usage log, which by default should be called, usage.txt and saved at the same location as all your other list files.

If the usage log isn't there, consult the file variable, $PROGRAM_USAGE_LOG to see where it was set.

If the usage log wasn't set up, consult Dada Mail's error log.

If you don't know where Dada Mail's error log is, consult the variable, PROGRAM_ERROR_LOG

If there is no error log, before the next time you Send a Message out, set up the error and usage logs; as well as setup up batching to something realistic.

Mailing List Message sending is working great! yet some of my messages are ending up in Bulk Mail folders - why?

This is a very difficult question to answer. Here's some things to consider:

To end this discussion, here are some things I'm pretty sure of:

Saying all this, keep in mind that you have a social responsibility when running your mailing list - do not abuse the right your subscribers have granted you with their email addresses. Respect is a two-way street.

lock files?

Dada Mail seems to be not working correctly. Viewing the error logs that I have setup - as per suggestion, give me back some odd cryptic messages about lockfiles not being removed, what do I do? Is it safe to manually remove these lockfiles?

If Dada Mail seems to be completely stuck, displaying only part of a screen, generally unusable, it is safe to delete the lock files - yes. Lock files should only be in use for seconds at the most, and then be automatically removed. If they're not, you can safely delete them yourself.

Lockfiles that aren't removed and still have their filehandle open may because of a larger problem you shouldn't ignore - either there's a bug in Dada Mail, or your server is being bombarded with requests - more than Dada Mail can handle.

I've found this to be true when Dada Mail is trying to load complex archive messages. If this is the case for you as well, you may want to play around with the, $MIME_OPTIMIZE variable.

Data::Dumper object version 2.102 does not match $Data::Dumper::VERSION 2.121 at....


Data::Dumper is probably already installed on your account.

Simply remove the copy that comes with Dada Mail by navigating to the dada/DADA/perllib directory and removing or moving the, Data directory. / < # opening angle bracket

I'm getting an error with the following (or similar) gobble-dee-gook: [Thu Jul 17 22:43:11 2003] / 
 < # opening angle bracket [Thu Jul 17 22:43:11 2003] [Thu Jul 17 22:43:11 2003] [Thu Jul 17 
 22:43:11 2003] [Thu Jul 17 22:43:11 2003] (?: # Non-backreffing grouping paren 
 [Thu Jul 17 22:43:11 2003] [Thu Jul 17 22:43:11 2003] [^>'"] * # 0 or more thi/: regexp *+ operand could be empty 
 at /DADA/App/ line 1217. BEGIN failed--compilation aborted at mail.cgi 
 line 87.

This error happens if you're server is running a version of Perl that's below version 5.005. Dada Mail requires at least version 5.005 of Perl and it's suggested that you use at least Perl 5.6. Dada Mail is developed and tested on a machine running Perl Version 5.8.

Among major hosts that have a version of Perl that's below 5.005 is Earthlink. Dada Mail will not run correctly on an Earthlink account. It's suggested that if you do have an account on Earthlink and want to run Dada Mail that you thoughtfully express your wantings of an up-to-date version of Perl available on their servers. Or, move your account to a hosting company that responds to their customers wants and needs.

To give you a brief history of Perl, Perl version 5.005 was released on 7/22/98. I don't think it's too much to ask that Dada Mail will only run on with a version of Perl that's five years old or less.

can't open /usr/home/path/to/your/dada_lists to read

I'm getting a Software Error that says:

        can't open /usr/home/path/to/your/dada_lists to read: No such file or directory at /DADA/

Did you change the first 4 variables in the file? What's happening is that its looking for a directory on the server that doesn't exists.

can't open /usr/home/myaccout/lists to read: Permission denied

I'm getting a sofware error that says:

        can't open /usr/home/myaccout/lists to read: Permission denied at /DADA/

The directory that you specified in the as the place to put your lists (the $FILES variable) exists, but isn't something Dada Mail can read and possibly write into. You'll need to change the permissions of this directoy. Usually, people on a regular hosting account will have to chmod the $FILES directory to 777.

Just to reiterate, this is a directory not a file. All sorts of files are going to be written inside this directory, so be ready.,

is only avaliable with the XS version

This problems comes to the surface when attempting to use the default CAPTCHA backend, as well as attempting to use the SMTP over SSL

This is a problem with the copies of Scalar::Util and, List::Util CPAN modules that come with Dada Mail.

See if you have the following directories:



If so, renamed them:



and see if this problem clears up.

I get the 'Congratulations' startup screen, but ...

I get the 'Congratulations' startup screen, but when I enter my root password and click the button, I either see a 404 page, or nothing happens

Did you set the $PROGRAM_URL variable in the file? This variable is defaulted to this:

        $PROGRAM_URL ='';

Which, unless your domain is, is wrong. Change it to the URL that you have to access the mail.cgi script from.

In your server configuration, can information be passed to the script using the POST method? If not, you're in trouble, cause Dada Mail needs that. 99.99% of the time, you'll be able to use the POST method to send information to a script, but sometimes, for security reasons, you won't be able to. This can be set in your servers configuration file, like httpd.conf.

No mail is being sent and I get this error in my logs:

        mail.cgi: Broken pipe at DADA/

or I see this Software Error in my browser:

        Error: can't pipe to mail program using settings: |/usr/bin/sendmail -t

This means that the $MAILPROG variable in the file is incorrect. If you have shell access to your server, type in this:

        which sendmail

to find out where the sendmail program is on your server, or ask your system administrator.

If you're on a WinNT server, you're most likely not going to be using Sendmail this way, you should be sending all your mail using an SMTP server. Check out the Windows readme file for more information on how to set up your copy of Dada Mail for Windows.

Use of uninitialized value

Everything is working fine, but when I open up my error log (or even sprinkled on the mail script in my web browser) I see annoying things like this:

        Use of uninitialized value at /home/mysits/web/cgi-bin/dada/mail.cgi line 7064.

Please report these to our issues tracker:

Global symbol "%Config" requires explicit package name

This error should be fixed as of version 3.0.0, but if you're using a version lower then this, place the following code near the top of the mail.cgi script:

    if($] > 5.008){
       require Errno;
       require Config;

Can't locate MIME/

I get an error like this:

        Software error: 
        Can't locate MIME/ in @INC (@INC contains: [...]

but everything is working fine, what's up?

If we only knew. This looks like a bug in Mime::Lite - a part of Dada Mail that we really like (Ok, LOVE) , but wasn't developed by us, so we can't think why it's broken. Basically, don't worry about the message, it's more of a warning than anything, if a slightly annoying warning. There are directions in mail.cgi itself to get rid of 'em.

Software error: ndbm store returned -1, errno 28

A little backgound on how Dada Mail stores its list settings and archives:

Dada Mail stores list settings and archives in what are called "DB Files"; they're simpler than an SQL database, but have their advantages from completely flat file databases. There are a few different DB File formats, and Dada Mail can use many different kinds. Different DB File formats have different limitations. One of these limitations is the amound of information they can store in each key/value pair. If you go over this limit, you're going to receive something like:

        ndbm store returned -1, errno 28

Most likely, you'll experience this when sending out a list message. This is triggered from Dada Mail trying to archive a message into a DB FIle format that has a limitation on the amount of data it can hold. The message goes over this limit. The easiest fix is to turn off archiving.

If you want to, you can play around with how Dada Mail picks what DB FIle to use. In the file, find this line:

        BEGIN { @AnyDBM_File::ISA = qw(DB_File GDBM_File NDBM_File ODBM_File SDBM_File) }

DB_File, GDBM_File, NDBM_File, ODBM_File and SDBM_File are all different DB File Formats. DB_File is the best and they get poorer from there. If Dada Mail isn't using DB_File, it usually means it's not available. If you have root access on your server, you can always install it, it's free. Before doing that, please note that previous lists setup with a different DB File format will not work if you're uswithcing the DB File package. Dada Mail can only use one of these packages at a time. It's possible that all these DB File formats have import/export tools that you may want to investigate. If you don't know what file format you're using, try using the file command.

I moved my lists from one server to another and reinstalled Dada Mail. Now when I try access my lists, I get this error:

 Software error: couldn't tie for reading: Permission denied

See the error faq about restoring your lists.

couldn't tie /home/path/to/your/dada_files/mj-listshortname for reading: File exists at [...]

See the error faq about restoring your lists.

How do I restore my lists?


By default, Dada Mail saves its list settings and archives (there's also an option to saved archived messages in an SQL table) in a binary type file called a Database File, or DB file for short. Sometimes these files can become binary-incompatible with the environment you're running Dada Mail under. This can happen if:

Visit the following URL:

You'll have to enter your Dada Mail Root Password and then you'll enter a screen that will allow you to restore your list settings/archives.

If you're using a version of Dada Mail under 2.10.6 and you're still receive an error after restoring your list settings/archives, take note of the file that's throwing the error and manually back it up and remove it. Usually, this file either did not get restored properly, or, was an archive file that had no archives saved in it. A bug in the program prior to 2.10.6 would have the latter stuck, even with the restoration feature.

Restoring list settings/archives is accomplished because Dada Mail keeps a plain text, platform agnostic version of your list settings/archives. This feature was put in Dada Mail, version 2.8.12. If you have a version of Dada Mail below this, this backup will not have been created. Upgrading Dada Mail will not create backups of a corrupted list to then restore from. List Setting/Archive restoration only worked with well after 2.9. If you have a installation of Dada Mail that needs to have lists restored that dates prior to 2.9, it's advised to upgrade to the latest version (make a backup, of course) of Dada Mail before attempting to restore your lists.

Read below for ways to restore a list if you're running a version below 2.9.

password is blank! - Error.

I receive an error that says,

List password for listshortname is blank! It is advised that you make sure your list settings file is not corrupted, or reset you list password. at /DADA/App/ line 123.

List passwords shouldn't become blank on their own, so if your password isn't set, other settings may have been lost because of whatever had happened too. It *may* be a good idea to start a new list if this is the case.

But! The easiest thing to solve this particular problem is to reset your password. In your web browser go to a URL like this:

Where, is the URL to your Dada Mail and, listshortname is the listshortname that's giving you trouble.

Hosting Company-Specific Problems

Hosting Companies that don't give access to a "true" home directory

For some reason, perhaps simplicity, if you FTP into some hosting accounts, the home directory will actually also be the public html directory. This causing many headaches, because, well, where do you place files/information that you don't want accessable via the web? For example, the files/directories that Dada Mail uses when creating/working with a list.

The best thing to do in this situation, providing that your webhost uses the Apache webserver (which is a very good chance indeed), is to protect the directory via an .htaccess file.

Wherever you have your $FILES variable set, place a file called, .htaccess in this directory and have this as its content:

 deny from all

If you try to access the directory set in the $FILES variable via a web browser, you should get a Forbidden error.

TextDrive -

  • I can't encrypt my Root Password!

    TextDrive uses incredibly secure encryption on its servers (blowfish). Changing Dada Mail to work with it isn't hard:

    Open up the file,

    Change this line:



     $SALT .= $C[rand(@C)] for (0 .. 23);

    Change these lines:

     $FIRST_SUB ||= 0;
     $SEC_SUB   ||= 2;


     $FIRST_SUB ||= 7;
     $SEC_SUB   ||= 24;

    And you're off to the races.


My personal opinion of GoDaddy is the same opinion I have for hosting companies that seem to have such low prices as to be unreal - stay away from them. You always get what you pay for.

Saying that, here are some tips for getting Dada Mail up and running on a GoDaddy account.

First, you need to change the lib path in the mail.cgi file to explicitly look into the Dada Mail library directories.

In the mail.cgi file itself, you'll see the lines:

 use lib qw(

You'll probably want to append the paths to the dada directory, the dada/DADA directory and the dada/DADA/perllib directory, like so:

 use lib qw(

Replacing /home/content/M/Y/A/MYACCOUNT/html/cgi with your correct information, obviously.

The second issue with GoDaddy, is that they break the path info that's set in the URL for Dada Mail. For example, in this URL:

The path info is, /list/yourlist, but this is never given to Dada Mail, so Dada Mail never knows it's doing something wrong.

A quick fix is to change the $PROGRAM_URL variable from something like:




(add a question mark at the end) and Dada Mail will know what you're trying to do and automatically make a workaround for you.

Ensim-based Servers

Ensim is a strange concept. They're file system design is even stranger. Lots of symlinks, etc - not a fan. Maybe I just don't, "get" it all, but it seems to be a big headache for me, but what do I know. Here's some workarounds if you're stumbling around:

If you go through the setup info stuff by visiting:

without actually configuring Dada Mail, it'll report back something like:

Your Public HTML directory is: * /home/virtual/sitexx/fst/var/www/html

Which is strange, because if you ssh into your account, it'll be something completely different! From what I understand, Ensim runs a much different environment, depending on if you run a program via the web, or via a shell. This is strange when it comes to different file paths.

This causes problems, when you want to use plugins/extensions to Dada Mail that rely on a different environment to what you are told when you run the main mail.cgi program via the web. Here's what to do:

Set the $FILES variable to something like:

 my $DIR = $ENV{SITE_ROOT} . "/var/www/data/.dada_files";

In your FTP program, you'll probably have to navigate to:


to actually make the dada_files directory and not to somewhere like, /home/virtual/sitexx/fst/var/www/data cause, you can't!

Also, there's a chance that the, data directory doesn't even exist. If you can't make it, because you lack the permissions to do so, you'll have to put the dada_files directory in the public html directory itself, which is not the best thing to do, but what else are you going to do?

Consider following the directions on what to do to protect the dada_files directory if you need to put this directory under the public html directory.

Since the, $ENV{SITE_ROOT} variable will change, depending on where program will be run, using the Environmental Variable will change automatically to suit whichever environment you're running in. Weird, I know.

The only other step you'll need to do is to take off the, -F flag in the mail.cgi file itself. You may have to repeat this step for some of the plugins/extensions for Dada Mail.

Frontpage Extensions-enabled accounts

Frontpage and Frontpage Extensions do not play well with Dada Mail.

If you receive errors that include file path with, _vti_cnf

For example:

 [Tue Jul 11 13:19:34 2006] mail.cgi: Semicolon seems to be missing at
 DADA/perllib/Mail/Field/_vti_cnf/ line 4.

You've been hit with the mighty, Frontpage-Extensions-Corrupted-My-Dada-Mail problem.

The, _vti_cnf directories have something to do with Frontpage - apparently, they hold some sort of configuration information for the program itself.

Here's one thing you'll have to do - you may not like it, but this is the best way to solve the problem:

You'll need to reinstall Dada Mail (I'm not kidding), or go through ALL the directories that make up Dada Mail, and take out every directory called, _vti_cnf (it's like a virus, I know!)

You'll then have to reinstall Dada Mail, but you have to make sure you do one very important step:

Instead of installing both the, mail.cgi file and DADA (uppercase) directory in the, dada (lowercase) directory in your cgi-bin, you're going to have to place the DADA directory in a place that's somewhere other than under your public html directory, and also update the, use lib statements in the mail.cgi file - and any other script that uses the libraries that make up the DADA directory. Here's what you're looking for:

 use lib qw(

If you placed your, DADA directory at:


You'd change the use lib statement to:

 use lib qw(

An annoyance for sure, but not the end of the world.

Here is the other option:

You can make a wrapper script that first goes through all the directories of Dada Mail for the _vti_cnf directories and removes them and their contents and then runs Dada Mail normally.

This has many disadvantages and can be dangerous - I'll explain the script and how to use it, and then list why this isn't the best idea.

First off, rename your, mail.cgi script to something like, real_mail.cgi. Create a new file called, mail.cgi and have this as its contents:

 #!/usr/bin/perl -w
 use strict; 
 use File::Find; 
 my %findings = (); 
 sub find_vti_cnf { 
     if($File::Find::dir =~ m/_vti_cnf$/){ 
             $findings{$File::Find::dir} = 1;
 find(\&find_vti_cnf, './');
 my $file; 
 for my $dir(keys %findings){ 
     if(opendir(VTI, $dir)){ 
            my @file_deep_six_list; 
                while(defined($file = readdir VTI) ) {
                        next if $file =~ /^\.\.?$/;
                        chmod(0777, "$dir/$file"); 
                        push(@file_deep_six_list, "$dir/$file");
             or warn "couldn't close: " . $dir; 
          my $final_count = unlink(@file_deep_six_list)
                 or warn "could not remove any backup files! $!"; 
         warn "couldn't remove $dir $!"
             unless rmdir($dir);

Upload this script where the other mail.cgi used to be, chmod 755 it to make it executable and you should be in good shape.

Now, saying this - make sure you understand how this script work before ever using it:

This script goes through every single directory, looking for directories named, _vti_cnf. It'll then delete the contents of that directory and then, the directory itself.

You should feel very nervous about running a program that delete massive amounts of files/directories. Don't use this script unless you fully understand that fact, since the possibility - however small, is there that this script could delete a file you didn't want removed.

Send a Webpage Problems

Can't locate object method "redirects" via package "HTTP::Headers"

This problem usually deals with out of date versions of CPAN modules that are shipped with Dada Mail itself.

The easiest fix may for you to just do an upgrade of Dada Mail.

If you can not/do not want to upgrade, you can also try to download the newest version of Dada Mail and just replace the directory:


with the copy of that directory that came from the downloaded distribution. Make sure to make a backup of the original, perllib directory, first!

Can't call method "verify_data" on an undefined value at...

Error message will look something like this:

 Can't call method "verify_data" on an undefined value at DADA/perllib/MIME/ line 1992, <DATA> line 27.
 Can't fetch 
 (Can't locate object method "_is_html" via package "HTTP::Headers") at /DADA/App/ line 707.

In the,


directory of your installed Dada Mail, renamed the, HTTP directory to something like, HTTP-bak and this error should clear up.

Template Problems

Changes made to $USER_TEMPLATE or $ADMIN_TEMPLATE make no difference to layout

If you're trying to change the layout/design of Dada Mail, but any changes you make do no seem to take hold, see if Screen Caching isn't enabled - it should be enabled by default. Your changes will not be visible, until after you have flushed out the cache.

See the doc on the Screen Cache feature for more information: