[Subversion] View of /DadaFork/extras/documentation/html

View of /DadaFork/extras/documentation/html_version/faq.pod.html

Parent Directory

Revision Log

Revision: 2253 - (download) (as text)
Wed Jan 10 14:34:26 2007 UTC (17 years, 4 months ago) by pje
File size: 104229 byte(s)

Base version: DadaMail 2.10.12

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> <html xmlns="http://www.w3.org/1999/xhtml"> <head> <title>General FAQ</title> <link rel="stylesheet" href="/Users/justin/Documents/DADA/DISTRO/dada/extras/documentation/pod_source/pod_styles.css" type="text/css" /> <link rev="made" href="mailto:root@b28.apple.com" /> </head> <body> <a name="__index__"></a>  <ul> <li><a href="#frequently_asked_questions">Frequently Asked Questions</a></li> <li><a href="#general">General</a></li> <ul> <li><a href="#what_do_i_need_to_run_dada_mail">What do I need to run Dada Mail?</a></li> <li><a href="#but_i_have_a_windows_server__the_system_requirements_clearly_state_that_it_s_not_supported__is_this_true">But I have a Windows Server, The system requirements clearly state that it's not supported - is this true?</a></li> <li><a href="#is_dada_mail_a_server_a_daemon">Is Dada Mail a Server? A Daemon?</a></li> <li><a href="#is_dada_mail_an_autoresponder">Is Dada Mail an Autoresponder?</a></li> </ul> <li><a href="#hosting">Hosting</a></li> <ul> <li><a href="#do_you_host_dada_mail_or_do_i_host_dada_mail">Do you host Dada Mail or do I host Dada Mail?</a></li> <li><a href="#do_you_provide_hosting_services">Do you provide hosting services?</a></li> <li><a href="#dada_mail_looks_awesome__installation_is_way_over_my_head__do_you_provide_installation_services">Dada Mail looks awesome! Installation is way over my head, do you provide installation services?</a></li> </ul> <li><a href="#upgrading">Upgrading</a></li> <ul> <li><a href="#i_have_an_older_version_of_dada_mail__or_something_called_mojo_mail__should_i_upgrade">I have an older version of Dada Mail, or something called Mojo Mail, should I upgrade?</a></li> </ul> <li><a href="#features">Features</a></li> <ul> <li><a href="#does_dada_mail_handle_announceonly_lists_discussion_lists">Does Dada Mail handle announce-only lists? Discussion Lists?</a></li> <li><a href="#does_dada_mail_handle_bounced_messages">Does Dada Mail handle bounced messages?</a></li> <li><a href="#how_do_i_create_the_html_subscription_form_code_to_place_on_my_web_pages_to_allow_people_to_subscribe_to_my_list">How do I create the HTML Subscription form code to place on my web pages to allow people to subscribe to my list?</a></li> <li><a href="#can_i_hook_dada_mail_up_to_a_form_on_my_website">Can I hook Dada Mail up to a form on my website?</a></li> <li><a href="#can_you_compare_dada_mail_to_another_program_for_me">Can you compare Dada Mail to another program for me?</a></li> <li><a href="#is_there_a_demo_of_dada_mail_set_up_that_i_can_use">Is there a Demo of Dada Mail set up that I can use?</a></li> <li><a href="#do_i_need_to_keep_my_browser_window_open_for_the_entire_mail_sending">Do I need to keep my browser window open for the entire mail sending?</a></li> <li><a href="#how_do_i_send_email_messages_with_formatted_text_images">How do I send email messages with formatted text/images?</a></li> <li><a href="#how_do_i_get_the_file_browser_working_in_fckeditor">How do I get the File Browser working in FCKeditor?</a></li> </ul> <li><a href="#the_list_confirmation_process">The List Confirmation Process</a></li> <ul> <li><a href="#can_you_explain_some_of_the_terminology_of_the_confirmation_process">Can you explain some of the terminology of the confirmation process?</a></li> </ul> <li><a href="#errors">Errors</a></li> <li><a href="#dada_mail_and_html_templates">Dada Mail and HTML Templates</a></li> <ul> <li><a href="#how_do_i_change_the_default_look_of_dada_mail">How do I change the default look of Dada Mail?</a></li> <li><a href="#are_there_any_official_translations_of_dada_mail">Are there any official translations of Dada Mail?</a></li> <li><a href="#how_do_you_translate_dada_mail">How do you translate Dada Mail?</a></li> </ul> <li><a href="#sql_and_dada_mail">SQL and Dada Mail</a></li> <ul> <li><a href="#does_dada_mail_need_an_sql_server_to_run">Does Dada Mail need an SQL server to run?</a></li> <li><a href="#does_dada_mail_support_an_sql_backend">Does Dada Mail support an SQL backend?</a></li> <li><a href="#what_do_i_have_to_do_to_have_dada_mail_use_its_sql_backend">What do I have to do to have Dada Mail use its SQL backend?</a></li> <li><a href="#what_are_the_benifits_of_using_the_sql_backends">What are the benifits of using the SQL backends?</a></li> <li><a href="#what_are_the_disadvantages_of_using_the_sql_backends">What are the disadvantages of using the SQL backends?</a></li> <li><a href="#how_do_i_move_from_the_default_backends_to_the_sql_backends">How do I move from the default backends to the SQL backends?</a></li> </ul> <li><a href="#mailing_list_messages">Mailing List Messages</a></li> <ul> <li><a href="#i_want_to_edit_the_unsubscribe_footer_of_my_mailing_list_message__how">I want to edit the unsubscribe footer of my Mailing List Message - how?</a></li> <li><a href="#hey__are_the_messages_i_send_traceable_back_to_me">Hey, are the messages I send traceable back to me?</a></li> </ul> <li><a href="#everyday_tasks">Everyday Tasks</a></li> <ul> <li><a href="#how_do_i_delete_a_list">How do I delete a list?</a></li> <li><a href="#can_i_rename_the_mail_cgi_file">Can I rename the mail.cgi file?</a></li> <li><a href="#how_do_i_fetch_reset_the_dada_mail_root_password">How do I fetch/reset the Dada Mail Root Password</a></li> <li><a href="#is_there_any_way_to_stop_a_mass_mailing_once_it_is_started">Is there any way to stop a mass mailing once it is started?</a></li> </ul> <li><a href="#list_subscribers">List Subscribers</a></li> <ul> <li><a href="#how_many_subscribers_can_dada_mail_handle">How many subscribers can Dada Mail handle?</a></li> <li><a href="#is_there_a_set_limit">Is there a set limit?</a></li> <li><a href="#can_i_track_statistics_like__who_opens_my_email_messages__who_clicks_on_my_urls_or_anything_else_that_ties_activity_of_my_mailing_list_to_specific_email_addresses">Can I track statistics like, who opens my email messages, who clicks on my URLs or anything else that ties activity of my mailing list to specific email addresses?</a></li> <li><a href="#can_i_directly_work_with_the_subscription_list">Can I directly work with the subscription list?</a></li> </ul> <li><a href="#performance">Performance</a></li> <ul> <li><a href="#how_can_i_get_the_highest_performance_when_using_dada_mail">How can I get the highest performance when using Dada Mail?</a></li> <li><a href="#is_there_a_way_to_speed_up_screen_rendering__how_to_use_the_screen_cache_">Is there a way to speed up screen rendering? (How to use the Screen Cache)</a></li> </ul> <li><a href="#mail_sending">Mail Sending</a></li> <ul> <li><a href="#i_see_dada_mail_can_send_its_list_messages_in_batches__what_s_the_best_batch_setting">I see Dada Mail can send its list messages in batches. What's the best batch setting?</a></li> <li><a href="#where_are_my_bounce_messages_going">Where are my bounce messages going?</a></li> <li><a href="#smtp_authentication__huh">SMTP Authentication - huh?</a></li> <li><a href="#what_s_the_differences_between_the_two_smtp_engines">What's the differences between the two SMTP Engines?</a></li> </ul> <li><a href="#archiving">Archiving</a></li> <ul> <li><a href="#how_do_you_edit_an_archived_message__2_10_7_and_above_">How do you edit an archived message? (2.10.7 and above)</a></li> <li><a href="#how_do_you_edit_an_archived_message__2_10_6_and_below_">How do you edit an archived message? (2.10.6 and below)</a></li> <li><a href="#how_do_you_edit_an_archive_message_with_anything_that_s_below_2_10_2">How do you edit an archive message with anything that's below 2.10.2?</a></li> <li><a href="#i_remember_that_you_used_to_be_able_to_edit_an_archived_message__what_happened">I remember that you used to be able to edit an archived message - what happened?</a></li> <li><a href="#ok__i_get_it__there_is_no_way_to_edit_archived_messages__in_versions_below_2_10_2___is_there_a_workaround">OK, I get it, there is no way to edit archived messages (in versions below 2.10.2) - is there a workaround?</a></li> </ul> <li><a href="#glossary_terms">Glossary Terms</a></li> <ul> <li><a href="#path_to_sendmail">path to sendmail</a></li> <li><a href="#absolute_path">absolute path</a></li> </ul> <li><a href="#about_the_author">About The Author</a></li> <ul> <li><a href="#so__you_re_a_computer_science_grad__genius">So, you're a Computer Science grad, genius?</a></li> <li><a href="#so__you_make_a_living_off_of_dada_mail">So, you make a living off of Dada Mail?</a></li> <li><a href="#you_re_rich__huh">You're rich, huh?</a></li> <li><a href="#i_don_t_get_it__why_do_you_give_the_thing_away_you_could_be_making_some_real_money_">I don't get it, why do you give the thing away? You could be making some REAL money!</a></li> <li><a href="#can_i_outright_buy_out_dada_mail">Can I outright BUY OUT Dada Mail?</a></li> </ul> <li><a href="#etc__etc">Etc, Etc</a></li> <ul> <li><a href="#what_is_dada_mail">What is Dada Mail?</a></li> <li><a href="#what_does_dada_mail_do">What does Dada Mail do?</a></li> <li><a href="#how_does_dada_mail_save_its_information">How does Dada Mail save its information?</a></li> <li><a href="#does_dada_mail_support_the_saving_of_more_than_the_email_address">Does Dada Mail support the saving of more than the email address?</a></li> <li><a href="#who_develops_dada_mail">Who develops Dada Mail?</a></li> <li><a href="#how_is_dada_mail_developed">How is Dada Mail developed?</a></li> <li><a href="#can_i_help">Can I help?</a></li> <li><a href="#is_there_a_cvs_server_i_can_check_in_out_of">Is there a CVS server I can check in/out of?</a></li> </ul> </ul>  <hr />   <h1><a name="frequently_asked_questions">Frequently Asked Questions</a></h1>   <hr /> <h1><a name="general">General</a></h1>   <h2><a name="what_do_i_need_to_run_dada_mail">What do I need to run Dada Mail?</a></h2> <a href="http://mojo.skazat.com/support/requirements.html">http://mojo.skazat.com/support/requirements.html</a>   <h2><a name="but_i_have_a_windows_server__the_system_requirements_clearly_state_that_it_s_not_supported__is_this_true">But I have a Windows Server, The system requirements clearly state that it's not supported - is this true?</a></h2> Short answer: yes Long answer: <a href="http://mojo.skazat.com/support/documentation/README-windows.pod.html">http://mojo.skazat.com/support/documentation/README-windows.pod.html</a> ...yes I do get this asked a lot, so I'm sorry I have to repeat myself - it's a project for someone else, I'm personally not interested in making it happen. So please understand - at the moment - no, Dada Mail does not work on a Windows Server.   <h2><a name="is_dada_mail_a_server_a_daemon">Is Dada Mail a Server? A Daemon?</a></h2> No and no. Dada Mail does not listen to any particular port, nor does it always run in the background awaiting a request. Dada Mail runs (mostly) as a simple CGI script. Dada Mail does have some modes where it can be run from a command line/cron job, but even then, it runs and exits; there is no daemon activity in Dada Mail. Dada Mail should always be run as a regular user and never as root.   <h2><a name="is_dada_mail_an_autoresponder">Is Dada Mail an Autoresponder?</a></h2> No. Dada Mail is not an autoresponder.   <hr /> <h1><a name="hosting">Hosting</a></h1>   <h2><a name="do_you_host_dada_mail_or_do_i_host_dada_mail">Do you host Dada Mail or do I host Dada Mail?</a></h2> Dada Mail is installed on your hosting account; thus, you will be the one hosting it.   <h2><a name="do_you_provide_hosting_services">Do you provide hosting services?</a></h2> Personally, no - I do have some suggestions on hosting: <a href="http://mojo.skazat.com/support/hosting.html">http://mojo.skazat.com/support/hosting.html</a> I don't use them myself, but <a href="http://textdrive.com">http://textdrive.com</a> seems like some good folks.   <h2><a name="dada_mail_looks_awesome__installation_is_way_over_my_head__do_you_provide_installation_services">Dada Mail looks awesome! Installation is way over my head, do you provide installation services?</a></h2> Yes: <a href="http://mojo.skazat.com/installation/request.html">http://mojo.skazat.com/installation/request.html</a>   <hr /> <h1><a name="upgrading">Upgrading</a></h1>   <h2><a name="i_have_an_older_version_of_dada_mail__or_something_called_mojo_mail__should_i_upgrade">I have an older version of Dada Mail, or something called Mojo Mail, should I upgrade?</a></h2> Yes! Always try to stay current with the latest version of Dada Mail. Great lengths are taken to make sure that the program for the most part is backwards compatible with previous versions, so you shouldn't have many problems. Before upgrading, you may want to look at the NOTES, that will list any change/incompatibility: <a href="http://mojo.skazat.com/support/documentation/NOTES.pod.html">http://mojo.skazat.com/support/documentation/NOTES.pod.html</a> There's an upgrade FAQ available as well: <a href="http://mojo.skazat.com/support/documentation/UPGRADE_README.pod.html">http://mojo.skazat.com/support/documentation/UPGRADE_README.pod.html</a> I also provide upgrade services - it's fairly inexpensive: <a href="http://mojo.skazat.com/installation/request.html">http://mojo.skazat.com/installation/request.html</a>   <hr /> <h1><a name="features">Features</a></h1>   <h2><a name="does_dada_mail_handle_announceonly_lists_discussion_lists">Does Dada Mail handle announce-only lists? Discussion Lists?</a></h2> Dada Mail handles announce only lists with ease - a standard installation will be all you need to run Dada Mail as an announce-only list. Dada Mail can also be set up to allow discussion lists. At the moment, this is done using a plugin called dada_bridge.pl <a href="http://mojo.skazat.com/support/documentation/dada_bridge.pl.html">http://mojo.skazat.com/support/documentation/dada_bridge.pl.html</a> dada_bridge.pl can also be set up to provide announce-only message sending from your mail reader - so instead of having to log into Dada Mail to write your message, you write the message in your mail reader and send it to a specific address for the message to be broadcasted to your list. Note: even with the installation of dada_bridge.pl, you're list won't ``automatically'' become a discussion list. A list will only become a discussion list after you have checked the,  Make this list a discussion list  option in the dada_bridge administration screen.   <h2><a name="does_dada_mail_handle_bounced_messages">Does Dada Mail handle bounced messages?</a></h2> See Mystery Girl, the bounce handler for Dada Mail: <a href="http://mojo.skazat.com/support/documentation/dada_bounce_handler.pl.html">http://mojo.skazat.com/support/documentation/dada_bounce_handler.pl.html</a>   <h2><a name="how_do_i_create_the_html_subscription_form_code_to_place_on_my_web_pages_to_allow_people_to_subscribe_to_my_list">How do I create the HTML Subscription form code to place on my web pages to allow people to subscribe to my list?</a></h2> Log into your list control panel, click,  Manage Appearance - Subscription Form HTML   <h2><a name="can_i_hook_dada_mail_up_to_a_form_on_my_website">Can I hook Dada Mail up to a form on my website?</a></h2> Sure - in fact there are two different form handlers to choose from, FormMail.pl <a href="http://mojo.skazat.com/support/documentation/Dada-ized_FormMail_README.pod.html">http://mojo.skazat.com/support/documentation/Dada-ized_FormMail_README.pod.html</a> and: TFmail.pl <a href="http://mojo.skazat.com/support/documentation/Dada-ized_TFMail_README.pod.html">http://mojo.skazat.com/support/documentation/Dada-ized_TFMail_README.pod.html</a> Both do a similar job, emailing you the fields filled out on your form and subscribing an email address, also filled out on a form, to a Dada Mail list. You can also make your own - you may want to look at the cookbook for Mailing List Subscribers: If you know a little Perl, it isn't too hard. A great place to see a working example is in the FormMail and TFmail scripts themselves. Do a search for, ``dada'' and you'll see the relevant changes.   <h2><a name="can_you_compare_dada_mail_to_another_program_for_me">Can you compare Dada Mail to another program for me?</a></h2> Not really. I can't in good faith tell you what Dada Mail has and Brand X lacks, since I, personally, only use Dada Mail. The feature list of Dada Mail is very verbose, so the easiest way to get an idea of what Dada Mail can do is try it out. From the very begining of the project in 1999, I set out to make something that was a little different than what was out there and I'm still doing that. Dada Mail is an experiment, if anything.   <h2><a name="is_there_a_demo_of_dada_mail_set_up_that_i_can_use">Is there a Demo of Dada Mail set up that I can use?</a></h2> Yes! - see: <a href="http://dadademo.orty.com/cgi-bin/dada/mail.cgi">http://dadademo.orty.com/cgi-bin/dada/mail.cgi</a>   <h2><a name="do_i_need_to_keep_my_browser_window_open_for_the_entire_mail_sending">Do I need to keep my browser window open for the entire mail sending?</a></h2> It's not the worst idea - the best thing to do is put on the, ``Sending Monitor'' screen to the mailing you currently want to keep an eye on. There are chances that a mailing will stop unexpectantly, and keeping this monitor up will prevent that. There are also ways to not have to have this sending monitor screen open, regardless of your hosting setup. This topic has it's own FAQ: <a href="http://mojo.skazat.com/support/documentation/FAQ-mailing_list_sending.pod.htm">http://mojo.skazat.com/support/documentation/FAQ-mailing_list_sending.pod.htm</a> Which is a must-read.   <h2><a name="how_do_i_send_email_messages_with_formatted_text_images">How do I send email messages with formatted text/images?</a></h2> Short Answer: Email messages that are formatted with text, images, etc. are done by writing the message in HTML. So, write your message in HTML! Long Answer: (See short answer first) There are many many MANY ways to send an HTML-formatted email using Dada Mail. <ul> <li><a name="item_the_2c__22send_a_list_message_22_basic_2fadvanced_">The, ``Send a List Message'' Basic/Advanced screen</a>  </li> In the list control panel, go to, Send a List Message. In the basic screen, there is a pulldown menu labeled, Format: Select, HTML and write your message in HTML. In the same screen, click the, Advanced Link. You will see an entire textarea labeled, HTML Version: in which to write your HTML message. If you do not know HTML, or are setting Dada Mail up for someone who does not know HTML, but wants to create HTML images, you can transform this textarea into a WYSIWYG HTML editor by installing FCKeditor (which is relatively painless). Directions on how to do so are at: <a href="http://mojo.skazat.com/support/documentation/Config.pm.html#fckeditor_integration___fckeditor_url">http://mojo.skazat.com/support/documentation/Config.pm.html#fckeditor_integration___fckeditor_url</a>  <li><a name="item_the_2c__22send_a_webpage_22_screen">The, ``Send a Webpage'' screen</a>  </li> Create an HTML document using your favorite HTML editor. Post it somewhere on your website. Make sure you do one of the following: <ul> <li><a name="item_put_a__3cbase_3e_tag_in_the_head_of_the_document_2">put a <base> tag in the head of the document, to make all the URLs in your document work when viewed from a different location that where you've saved it on yours server</a>  </li> <li><a name="item_make_all_urls_in_your_html_document_absolute__2d_m">make all URLs in your HTML document absolute - meaning:</a>  </li> <ul> <li><a name="item_no_21">NO!</a>  </li> <pre> <img src="../../images/love.png" /></pre> <li><a name="item_yes_21">Yes!</a>  </li> <pre> <img src="<a href="http://example.com/images/love.png&quot">http://example.com/images/love.png&quot</a>; /></pre> <li>NO!  </li> <pre> <a href="index.html">This is my link!</a></pre> <li>Yes!  </li> <pre> <a href="<a href="http://example.com/index.html">http://example.com/index.html</a>">This is my link!</a></pre> </ul> In the list control panel, go to, <Send a Webpage>. Under, HTML Verson (Your Webpage), check: Grab content from this webpage address (URL): and fill in the url to use. <li><a name="item_install_the_dada_bridge_2epl_plugin_and_format_and">Install the dada_bridge.pl plugin and format and send your messages from your mail reader. Your messages should come through almost exactly as you've created them.</a>  </li> </ul> NOTE: Before being sent, all HTML messages will be changed to a multipart/alternative message and have a PlainText version of your message created, if one is not present already. This is absolutely required these days and there is currently no way to turn off this behavior in Dada Mail. </ul>   <h2><a name="how_do_i_get_the_file_browser_working_in_fckeditor">How do I get the File Browser working in FCKeditor?</a></h2> I want to upload images to then put in my message - any help on that? These directions are currently for version 2.3 of the FCKEditor - Note also as well that I didn't author FCKEditor, so YMMV with these instructions. First, get FCKeditor up and running: <a href="http://mojo.skazat.com/support/documentation/Config.pm.html#fckeditor_integration___fckeditor_url">http://mojo.skazat.com/support/documentation/Config.pm.html#fckeditor_integration___fckeditor_url</a> To add to these instructions: <ul> <li><a name="item_in_the_fckeditor_directory_you_uploaded_in_your_ho">In the FCKEditor directory you uploaded in your hosting account delete these directories:</a>  </li> <ul> <li><a name="item__samples">_samples</a>  </li> <li><a name="item__testcases">_testcases</a>  </li> </ul> (security purposes). <ul> <li><a name="item_for_using_the_perl_connector_3a">For Using The Perl Connector:</a>  </li> <ul> <li><a name="item_tweak_the_2c__22_filebrowserlanguage_22">Tweak the, ``_FileBrowserLanguage''</a>  </li> I'm a Perl guy, so I'm going to be using the Perl connector. You have to open up the, ``fckconfig.js'' file and change this line: <pre> var _FileBrowserLanguage = 'asp' ; // asp | aspx | cfm | lasso | perl | php | py</pre> to:  <pre> var _FileBrowserLanguage = 'perl';</pre>  <li><a name="item_change_permissions_on_the__2epl_2f_2ecgi_files">Change permissions on the .pl/.cgi files</a>  </li> Next, navigate to: editor/filemanager/browser/default/connectors/perl and change the permission of every file with either a, .cgi or, .pl extension to, 755. For my account, this directory isn't a directory that you can execute cgi scripts, but if I do this step, somehow it all works. Mysterious.  <li><a name="item_uncomment_the_security_thingy_in_2c__22connector_2">Uncomment the Security thingy in, ``connector.cgi''</a>  </li> Open up the, connector.cgi file, find this line: <pre> &SendError( 1, 'This connector is disabled. Please check the "editor/filemanager/browser/default/connectors/perl/connector.cgi" file' ) ;</pre> And comment it/remove it: <pre> # &SendError( 1, 'This connector is disabled. Please check the "editor/filemanager/browser/default/connectors/perl/connector.cgi" file' ) ;</pre>  <li><a name="item_tweak_the_basexml_2epl_file">Tweak the basexml.pl file</a>  </li> Still with me? OK - (whew). Open up ``basexml.pl'' and find this line: <pre> print '<CurrentFolder path="' . ConvertToXmlAttribute($currentFolder) . '" url="' . ConvertToXmlAttribute(GetUrlFromPath($resourceType,$currentFolder)) . '" />';</pre> and change it to: <pre> print '<CurrentFolder path="' . ConvertToXmlAttribute($currentFolder) . '" url="' . '<a href="http://yoursite.com">http://yoursite.com</a>' . ConvertToXmlAttribute(GetUrlFromPath($resourceType,$currentFolder)) . '" />';</pre> where, <a href="http://yoursite.com">http://yoursite.com</a> is the URL of your website. Once it's all up and running, you can navigate to ``Send a List Message -> Advanced'' (among other places) and get the WYSIWYG editor. </ul> <li><a name="item_for_using_the_php_connector">For Using the PHP Connector</a>  </li> <ul> <li>Tweak the, ``_FileBrowserLanguage''  </li> Open up the, ``fckconfig.js'' file and change these lines: <pre> var _FileBrowserLanguage = 'asp' ; // asp | aspx | cfm | lasso | perl | php | py var _QuickUploadLanguage = 'asp' ; // asp | aspx | cfm | lasso | php</pre> to: <pre> var _FileBrowserLanguage = 'php' ; // asp | aspx | cfm | lasso | perl | php | py var _QuickUploadLanguage = 'php' ; // asp | aspx | cfm | lasso | php</pre> Note: I have NOT gotten the, ``Quick upload'' thingy to work at all - so I guess YMMV  <li><a name="item_tweak_the_config_2ephp_file">Tweak the config.php file</a>  </li> Open up the, FCKeditor/editor/filemanager/browser/default/connectors/php/config.php file, Find this line: <pre> $Config['Enabled'] = false ;</pre> And change it to: <pre> $Config['Enabled'] = true ;</pre>  <li><a name="item_tweak_the_basexml_2ephp_file">Tweak the basexml.php file</a>  </li> Open up the, FInd this line: <pre> echo '<CurrentFolder path="' . ConvertToXmlAttribute( $currentFolder ) . '" url="' . ConvertToXmlAttribute( GetUrlFromPath( $resourceType, $currentFolder ) ) . '" />' ;</pre> and change it to: <pre> echo '<CurrentFolder path="' . ConvertToXmlAttribute( $currentFolder ) . '" url="' . '<a href="http://yoursite.com">http://yoursite.com</a>' . ConvertToXmlAttribute(GetUrlFromPath($resourceType,$currentFolder)) . '" />' ;</pre> where, <a href="http://yoursite.com">http://yoursite.com</a> is the URL of your website.  <li><a name="item_getting_the_2c__22quick_upload_22_feature_working">Getting the, ``Quick Upload'' feature working</a>  </li> The php connector also allows you to use the, ``Quick Upload'' feature. Two additional steps: <ul> <li><a name="item_tweak_the_2c__22config_2ephp_22_file">Tweak the, ``config.php'' file</a>  </li> open FCKeditor/editor/filemanager/upload/php/config.php and change these lines: <pre> // SECURITY: You must explicitelly enable this "uploader". $Config['Enabled'] = false;</pre> to: <pre> // SECURITY: You must explicitelly enable this "uploader". $Config['Enabled'] = true ;</pre>  <li><a name="item_tweak_the_2c__22upload_2ephp_22_file">Tweak the, ``upload.php'' file</a>  </li> open FCKeditor/editor/filemanager/upload/php/upload.php and change the line: <pre> $sFileUrl = $Config["UserFilesPath"] . $sFileName ;</pre> to: <pre> $sFileUrl = '<a href="http://www.mysite.com">http://www.mysite.com</a>' . $Config["UserFilesPath"] . $sFileName ;</pre> where, <a href="http://yoursite.com">http://yoursite.com</a> is the URL of your website. </ul> </ul> </ul> Once it's all up and running, you can navigate to ``Send a List Message -> Advanced'' (among other places) and get the WYSIWYG editor. Here's how the ``Insert/Edit Image'' thingy works: <ul> <li><a name="item_click_the_insert_2fedit_image_button_2c_you_27ll_g">Click the Insert/Edit Image button, you'll get the, ``Image Properties'' Window</a>  </li> <li><a name="item_click_the_2c__22browse_server_22_button_2e">Click the, ``Browse Server'' button.</a>  </li> You'll get this odd, empty file browser looking thing. It doesn't show anything, but you can select an image/whatever on your desktop and upload it to your account! Cool!  <li><a name="item_click_the_2c__22browse_2e_2e_2e_22_button_at_the_b">Click the, ``Browse...'' button at the bottom of the screen,</a>  </li> <li><a name="item_select_an_image_and_click_2c__22upload_22">select an image and click, ``Upload''</a>  </li> That image will now show up in the file browser! Click on it and the file browser goes away and you get a preview of the image.  <li><a name="item_click_2c__22ok_22_and_the_image_will_be_inserted_i">Click, ``OK'' and the image will be inserted into your message.</a>  </li> </ul> Now, to have this image be embedded into your newsletter and sent within the image as an attachment, do all these steps, not in the, ``Send a List Message -> Advanced'' screen, but in the, ``Send a Webpage'' screen: <ul> <li><a name="item_check_the_2c__22use_the_following_html_as_content_">Check the, ``Use the following HTML as content: '' option.</a>  </li> <li><a name="item_click_2c__22show_2fhide_advanced_options_22_and_se">Click, ``Show/Hide Advanced Options'' and select,</a>  </li> ( Images in this Webpage Should:) ``be embedded in the message itself. '' </ul> </ul>   <hr /> <h1><a name="the_list_confirmation_process">The List Confirmation Process</a></h1>   <h2><a name="can_you_explain_some_of_the_terminology_of_the_confirmation_process">Can you explain some of the terminology of the confirmation process?</a></h2> Why, yes. Here are some terms you'll hear: <ul> <li><a name="item_double_2dopt_in_2c_closed_2dloop_2c_confirmed_opt_">Double-Opt In, Closed-loop, Confirmed Opt-in</a>  </li> These terms are all for the same idea: The subscriber of a mailing list has to first ask to be on the list to start with, and confirm via some means that the email address they want to subscribe with is theres. This is the one main reason why you'd want to use a mailing list manager. It uses are to the point where there may be legal steps against you if you run a mailing list without this system. Saying that, Dada Mail is completely compatible with this methodology. In Dada Mail this feature is called, ``Subscription Confirmation Emails'' and the option can be enabled/disabled in the Manage List - Mailing List Options screen. Under no circumstances should you disable this feature. Even though you may not like to have a would-be subscriber make two steps to subscribe, it's incredibly important that they do. </ul>   <hr /> <h1><a name="errors">Errors</a></h1> Running the Program Generates a 500 Server Error Message when I do, ``x'' See the error FAQ: <a href="http://mojo.skazat.com/support/documentation/error_faq.pod.html">http://mojo.skazat.com/support/documentation/error_faq.pod.html</a>   <hr /> <h1><a name="dada_mail_and_html_templates">Dada Mail and HTML Templates</a></h1>   <h2><a name="how_do_i_change_the_default_look_of_dada_mail">How do I change the default look of Dada Mail?</a></h2> Short Answer: If all you want to do is tweak the CSS styles of Dada Mail, the global CSS file is located at: <pre> dada/DADA/Template/templates/default_css.css</pre> You will never see this file directly in use in Dada Mail, but you can view it in your web browser by adding /css to the end of the URL to Dada Mail: <a href="http://example.com/cgi-bin/dada/mail.cgi/css">http://example.com/cgi-bin/dada/mail.cgi/css</a> If you're comfortable with CSS, a lot can be changed with this file alone, from fonts and colors to the overall page layouts. Everything is nicely organized in there, and the few hacks used are thoroughly commented - it may be all you need. Really Long Answer: Going even beyond the considerable CSS control outlined above, Dada Mail is extremely flexible in this respect. Extremely. Check out the free chapter of the Magicbook all about Templates at: <a href="http://mojo.skazat.com/purchase/sample_chapter_templates.html">http://mojo.skazat.com/purchase/sample_chapter_templates.html</a> That'll give you even more information than what's below. First: Clarification. Dada Mail uses different templating systems depending on what needs to be done, but there's basically two types: <ul> <li><a name="item_system">The Internal Templating System (HTML::Template)</a>  </li> Most of the HTML that Dada Mail produces is stored in templates in the: <pre> dada/DADA/Template/templates</pre> directory. The templates themselves are written in a templating language called HTML::Template. More info here: <a href="http://search.cpan.org/~samtregar/HTML-Template-2.7/Template.pm">http://search.cpan.org/~samtregar/HTML-Template-2.7/Template.pm</a> A description of the templating language, by the author, is: just a normal HTML file with a few extra tags, the simplest being <TMPL_VAR meaning, if you read the HTML::Template docs, you should have a pretty firm understanding on how to play with these templates. These templates control many of the administration screens. You'll want to play around with these templates if there are some layout/formatting/content output changes you want to do to the program itself. Note: that by design, these templates have almost no programatic logic to them - they are almost strictly layout only, so don't expect to change the behavior of the program by editing the template files. To find the correct template to modify: visit the screen you'd like to modify, view its source code (``view source'' in your browser options), find the section in the source code that you'd like to change, and then continue reading down until you see a comment, <!-- end template_name.tmpl --> ...or read up (that is, backwards) until you bump into a: <!-- start template_name.tmpl --> comment. Either way, ``template_name.tmpl'' is the template that created that section of source code. Or if you prefer, just have a look at the screen's URL - usually, the template will be named similarily to the function name that responded to it (the ``flavor'' parameter, sometimes shortened to ``f'', will tell you the name of the function), and usually, the template name matches that function name. For example, the, ``Send a List Message'' screen, has a flavor parameter query string of, send_email. The template that creates this screen is called, send_email_screen.tmpl Easy enough.  <li><a name="item_dada_mail_templating_system">Dada Mail Templating System</a>  </li> The Dada Mail Templating system - used primarily for Email Messages and the List/User Template - is tragically simple. Tags are replaced with what they are supposed to represent. A tag looks like this: <pre> [i_am_a_tag]</pre> There are no conditional statements in this system. Sometimes, you'll see a tag that looks like this: <pre> <!--[i_am_another_tag]--></pre> When interpolated, the entire tag, including the comment around it, will be replaced. This templating system is the one that is disclosed to a user of the Dada Mail program. Some of the places this system is used are as follows: <ul> <li><a name="item_the_default_list_template">The Default List Template</a>  </li> Sometimes called the User Template, the default template lives at: <pre> dada/DADA/Template/templates/default_list_template.tmpl</pre> You may edit this file directly, although you most likely do not want to, since your changes will be lost when you upgrade the program. There are a few ways to make changes to this template, without changing this copy. <ul> <li><a name="item_use_the__24user_template_config_2epm_variable">Use the $USER_TEMPLATE Config.pm variable</a>  </li> This is the preferred method. Simply make a copy of the default_list_template.tmpl file, save it in a another location on your server and set the Config.pm variable, $USER_TEMPLATE to the absolute path of its location. You can also set $USER_TEMPLATE to a URL - if your server supports that. There's more overhead involved with Dada Mail fetching the program this way, but it does allow you to preprocess the Template before it's seen by Dada Mail. For example, you want to have PHP calls in the template itself, or generate any sort of dynamic content.  <li><a name="item_make_a_copy_of_default_list_template_2etmpl_and_pl">Make a copy of default_list_template.tmpl and place it in your $TEMPLATES directory</a>  </li> Dada Mail will actually look for any of the template that are located in the default template directory, <pre> dada/DADA/Template/templates</pre> in whichever directory you set the $TEMPLATES Config.pm variable to. If you did not set this variable, it defaults to whatever you set the $FILES variable to. Making changes to this copy will override the copy in the dada/DADA/Template/templates location. The above information is valid for any of the templates located in the dada/DADA/Template/templates directory. </ul> NOTE: The List/User Template can be overridden by any of the lists; meaning, each list has its own copy of the list template that it can change. This can be of some confusion if you're trying to edit the main template, and you don't see the changes taking effect for one of your lists, or, you make a change to the list template, and it's not affecting the default screen you see in Dada Mail. If you want to have all your lists use the default List/User Template: <ul> <li><a name="item_remove_any_file_that_ends_in_the_2c__22_2etemplate">Remove any file that ends in the, ``.template'' file ending in your $TEMPLATES directory.</a>  </li> These are the list templates that correspond to each of your lists.  <li><a name="item_change_the_default_list_template_2c_using_the_tech">Change the default list template, using the techniques above.</a>  </li> Either, don't edit the individual copy of the list template in the admin control panel under, Manage Appearance - Edit Template, check the option, `` Use the default list template.'' in that same screen, or, to be even more authorative, add this to your %LIST_SETUP_OVERRIDES Config.pm hash: <pre> get_template_data => 'from_default_template',</pre> Information on the %LIST_SETUP_OVERRIDES hash can be found at: <a href="http://mojo.skazat.com/support/documentation/Config.pm.html#list_setting_defaults">http://mojo.skazat.com/support/documentation/Config.pm.html#list_setting_defaults</a> </ul> Again, any list screen that does not have a single list associated with it, will be given the default list template look. <li><a name="item_the_default_admin_template">The Default Admin Template</a>  </li> The Default Admin Template lives at: <pre> default_admin_template.tmpl</pre> The information about the Default List Template also follows for the Default Admin Template. The Config.pm variable for it is: $DEFAULT_ADMIN_TEMPLATE You may also be interested in the admin_menu_widget.tmpl, which is used to created the left hand menu. It's written using the HTML::Template templating system.  <li><a name="item_error_messages">Error Messages</a>  </li> Most Error Messages in Dada Mail live in the dada/DADA/App/Errors.pm Perl module. They're not templated out into individual files, since we've just haven't gotten around to it. Be careful when editing, since the file is a Perl program and follows the conventions and syntax requirements of Perl itseld.  <li><a name="item_email_messages">Email Messages</a>  </li> The default email messages that are easily editable are located in the Config.pm file itself. The variables are called: <ul> <li><a name="item__24subscribed_message">$SUBSCRIBED_MESSAGE</a>  </li> <li><a name="item__24unsubscribed_message">$UNSUBSCRIBED_MESSAGE</a>  </li> <li><a name="item__24confirmation_message">$CONFIRMATION_MESSAGE</a>  </li> <li><a name="item__24unsub_confirmation_message">$UNSUB_CONFIRMATION_MESSAGE</a>  </li> <li><a name="item__24mailling_list_message">$MAILlING_LIST_MESSAGE</a>  </li> <li><a name="item__24mailling_list_message_html">$MAILlING_LIST_MESSAGE_HTML</a>  </li> <li><a name="item__24not_allowed_to_post_message">$NOT_ALLOWED_TO_POST_MESSAGE</a>  </li> <li><a name="item__24text_invite_message">$TEXT_INVITE_MESSAGE</a>  </li> <li><a name="item__24html_invite_message">$HTML_INVITE_MESSAGE</a>  </li> <li><a name="item__24send_archived_message">$SEND_ARCHIVED_MESSAGE</a>  </li> </ul> Again, we just haven't gotten to placing these in separate template files. You can edit these messages separately for each list under: Manage Copy - Email Messages. To reset these messages to their default, select all the text in the textarea you want to reset, delete the text and click, Save all Changes <li><a name="item_list_html_screens">List HTML Screens</a>  </li> List HTML screens are used for the operation of a mailing list. The screens that are easily editable are in the Config.pm file itself. The variables are called: <ul> <li><a name="item__24html_send_archived_message">$HTML_SEND_ARCHIVED_MESSAGE</a>  </li> <li><a name="item__24html_confirmation_message">$HTML_CONFIRMATION_MESSAGE</a>  </li> <li><a name="item__24html_unsub_confirmation_message">$HTML_UNSUB_CONFIRMATION_MESSAGE</a>  </li> <li><a name="item__24html_subscribed_message">$HTML_SUBSCRIBED_MESSAGE</a>  </li> <li><a name="item__24html_unsubscribed_message">$HTML_UNSUBSCRIBED_MESSAGE</a>  </li> </ul> You can edit these HTML screens separately for each list under: Manage Copy - HTML Messages. </ul> <li><a name="item_misc_2e_html">Misc. HTML</a>  </li> Some HTML/Email Messages created by Dada Mail are done within the Perl code itself. This amount is now strikingly a minority, but it's still present. It comes in a variety of flavors, that don't really makes sense. But, here's some pointers: <ul> <li><a name="item_the_cgi_2epm_module">The CGI.pm module</a>  </li> Lots of the inline HTML is created using the venerable CGI.pm module. Here's the docs: <a href="http://search.cpan.org/dist/CGI.pm/CGI.pm">http://search.cpan.org/dist/CGI.pm/CGI.pm</a> to spot it in the code, you'll want to look for Perl subroutines/functions that are named similar to HTML tags. </ul> </ul>   <h2><a name="are_there_any_official_translations_of_dada_mail">Are there any official translations of Dada Mail?</a></h2> At the moment, no, but check: <a href="http://sourceforge.net/project/showfiles.php?group_id=13002">http://sourceforge.net/project/showfiles.php?group_id=13002</a> For translations provided by Dada Mail users. For example: <a href="http://prdownloads.sourceforge.net/mojomail/dada-2_10_2de.tar.gz?download">http://prdownloads.sourceforge.net/mojomail/dada-2_10_2de.tar.gz?download</a> Is Dada Mail, version 2.10.2 translated into German. A more user-friendly list of translations is probably located at the main download page at: <a href="http://mojo.skazat.com/download">http://mojo.skazat.com/download</a>   <h2><a name="how_do_you_translate_dada_mail">How do you translate Dada Mail?</a></h2> Basically, follow the instructions used to customize the Dada Mail templates (above)   <hr /> <h1><a name="sql_and_dada_mail">SQL and Dada Mail</a></h1>   <h2><a name="does_dada_mail_need_an_sql_server_to_run">Does Dada Mail need an SQL server to run?</a></h2> No. But, SQL is an option.   <h2><a name="does_dada_mail_support_an_sql_backend">Does Dada Mail support an SQL backend?</a></h2> Short answer, yes Long Answer: Dada Mail supports MySQL and Postgres with saving its: <ul> <li><a name="item_list_archives">List Archives</a>  </li> <li><a name="item_list_subscribers">List Subscribers</a>  </li> <li><a name="item_list_settings_2fpreferences">List Settings/Preferences</a>  </li> </ul> It does not support SQL with saving its: <ul> <li><a name="item_logs">Logs</a>  </li> Most always, PlainText  <li><a name="item_mail_schedules">Mail Schedules</a>  </li> Again, DB File flavor - with a wrapper to provide saving complex data structures </ul>   <h2><a name="what_do_i_have_to_do_to_have_dada_mail_use_its_sql_backend">What do I have to do to have Dada Mail use its SQL backend?</a></h2> You'll need to create the needed SQL tables manually. The correct SQL table schemas to use to create both the Subscriber and Archive tables are located at: dada/extras/SQL and at: <a href="http://mojo.skazat.com/support/documentation/Config.pm.html#_sql_params">http://mojo.skazat.com/support/documentation/Config.pm.html#_sql_params</a> the above URL also gives more information on how to setup Dada Mail to use the SQL backend - basically, you have to set some of the Config.pm variables - no real surprises.   <h2><a name="what_are_the_benifits_of_using_the_sql_backends">What are the benifits of using the SQL backends?</a></h2> Well, there are the basic benifits of SQL over a, ``Flat File'' DB: <ul> <li><a name="item_speed">Speed</a>  </li> <li><a name="item_scalability">Scalability</a>  </li> <li><a name="item_interoperability">Interoperability</a>  </li> <li><a name="item_data_integrity">Data Integrity</a>  </li> </ul> There are also certain features that are available when you use the SQL backend that are not available to you when using the (default) alternative. These include: <dl> <dt><a name="item_archiving_3a">Archiving:</a>  </dt> <ul> <li><a name="item_ability_to_view_embedded_inline_images_in_the_arch">Ability to View Embedded Inline Images in the archive</a>  </li> <li><a name="item_ability_to_download_attachments">Ability to download attachments</a>  </li> </ul> <li><a name="item_subscribers_3a">Subscribers:</a>  </li> <ul> <li><a name="item_using_the_global_black_list">Using the Global Black List</a>  </li> <li><a name="item_sending">Global List Sending (Sending to more than one list at one time, without duplicates)</a>  </li> <li><a name="item_global_unsubscribe">Global Unsubscribe</a>  </li> </ul> </dl>   <h2><a name="what_are_the_disadvantages_of_using_the_sql_backends">What are the disadvantages of using the SQL backends?</a></h2> The DB File backend for the Archives and Settings has an auto backup feature; the SQL backend does not - it is advised to you create a simple auto-backup routine for your SQL tables. Not really a disadvantage, but the SQL backend will not speed up your mailing list sendings. It is now my official recommendation that you use the SQL backend, if possible. This is not set by default for an easier installation process.   <h2><a name="how_do_i_move_from_the_default_backends_to_the_sql_backends">How do I move from the default backends to the SQL backends?</a></h2> There are various scripts that'll move over the default backend of the various types of files that Dada Mail uses to the SQL backend. Advice: Convert the Settings backend first, before doing any of the other backends. <ul> <li><a name="item_settings">Settings</a>  </li> There's a script called, dada_settings_dbtosql.pl which is located in: /dada/extras/scripts/dada_settings_dbtosql.pl It's documentation is at: <a href="http://mojo.skazat.com/support/documentation/dada_settings_dbtosql.pl.html">http://mojo.skazat.com/support/documentation/dada_settings_dbtosql.pl.html</a>  <li><a name="item_archives">Archives</a>  </li> There's a script called, dada_archive_dbtosql.pl which is located in: /dada/extras/scripts/dada_archive_dbtosql.pl It's documentation is at: <a href="http://mojo.skazat.com/support/documentation/dada_archive_dbtosql.pl.html">http://mojo.skazat.com/support/documentation/dada_archive_dbtosql.pl.html</a>  <li><a name="item_subscribers">Subscribers</a>  </li> There's a script called, dada_subscribers_plaintext2sql.pl which is located in: /dada/extras/scripts/dada_subscribers_plaintext2sql.pl It's documentation is at: <a href="http://mojo.skazat.com/support/documentation/dada_subscribers_plaintext2sql.pl.html">http://mojo.skazat.com/support/documentation/dada_subscribers_plaintext2sql.pl.html</a> </ul>   <hr /> <h1><a name="mailing_list_messages">Mailing List Messages</a></h1>   <h2><a name="i_want_to_edit_the_unsubscribe_footer_of_my_mailing_list_message__how">I want to edit the unsubscribe footer of my Mailing List Message - how?</a></h2> By default, the Mailing List Messages - meaning, messages that are sent to everyone on a list, provide quite a bit of information about the list and how to unsubscribe. It's very verbose, but we feel that it's a good start. To change the mailing list message template, login into your list control panel and navigate to: Manage Copy - Email Messages You'll see many text fields with all the email message templates that are easy to change. You are looking for two:  Mailing List Message (Text Version)  and  Mailing List Message (HTML Version)  Edit to your liking - one special tag that you're going to want to make sure you still include is the: [message_body] tag. This tag will be replaced by your actually message body - meaning, what you wrote, when your mailing list message is sent. If your mailing list messages are coming to you as blank, make sure you did not remove the, [message_body] tag! These two messages can be changed globaly in the Config.pm file, under the variables: $MAILlING_LIST_MESSAGE and $MAILlING_LIST_MESSAGE_HTML If a list already has edited any of the email message templates, your global changes will not take affect for that list.   <h2><a name="hey__are_the_messages_i_send_traceable_back_to_me">Hey, are the messages I send traceable back to me?</a></h2> Oh yeah. Dada Mail makes absolutely no effort to, ``mask'', ``hide'', put you in, ``stealth mode'', or any other such tom-foolery. If you're dealing with software that touts these very features, stop using it, as you're using spamming software. In fact, Dada Mail goes out of its way to present a traceable path from the messages it sends, to its source. Some techniques that Dada Mail does not employ: <ul> <li><a name="item_invalid">The creation of invalid (as in broken) message headers</a>  </li> <li><a name="item_the_creation_of_2c__22faked_22_message_headers">The creation of, ``faked'' message headers</a>  </li> <li><a name="item_incorrect_from_3a_2c_to_3a_2c_etc_headers">Incorrect From:, To:, etc headers</a>  </li> <li><a name="item_unsubscribe_links_that_do_not_work">Unsubscribe links that do not work</a>  </li> </ul> Some techniques Dada Mail does take advantage of include: <ul> <li><a name="item_full_use_of_list_2d_2a_headers_2c">Full use of List-* headers,</a>  </li> Including: List, List-Archive, List-ID, List-Owner, List-Post, List-Subscribe, List-Unsubscribe and List-URL See RFC 2919 for more information: <a href="http://www.faqs.org/rfcs/rfc2919.html">http://www.faqs.org/rfcs/rfc2919.html</a> and RFC 2369: <a href="http://www.faqs.org/rfcs/rfc2369.html">http://www.faqs.org/rfcs/rfc2369.html</a>  <li><a name="item_and_many_2c_many_other_things">And many, many other things</a>  </li> </ul> Basically, Dada Mail sends an email message exactly as you're supposed to send one - no tricks. Mom taught us the best defense is honestly.   <hr /> <h1><a name="everyday_tasks">Everyday Tasks</a></h1>   <h2><a name="how_do_i_delete_a_list">How do I delete a list?</a></h2> Log into a list using the Dada Mail Root Password. You'll see the option under the, Manage List heading.   <h2><a name="can_i_rename_the_mail_cgi_file">Can I rename the mail.cgi file?</a></h2> Yes. You can rename the, mail.cgi file to any other valid filename, like newsletter.cgi or craaaaazyname.cgi. You'll most likely have to keep the file ending either, .cgi or .pl The only place that this variable is hardcoded is in the, PROGRAM_URL variable - so make sure to change this variable as well to reflect the file name changes.   <h2><a name="how_do_i_fetch_reset_the_dada_mail_root_password">How do I fetch/reset the Dada Mail Root Password</a></h2> There is a plugin, described here: <a href="http://mojo.skazat.com/support/documentation/change_root_password.cgi.html">http://mojo.skazat.com/support/documentation/change_root_password.cgi.html</a> That will allow you to change the Dada Mail Root Password. Other than that plugin, there is currently no way, through the Dada Mail web-based interface to fetch the Dada Mail Root Password - you'll have to actually retrieve it from a config file - here's how: Usually, The Dada Mail Root Password is stored in the Config.pm file, which itself is located in the, dada/DADA/ directory of your cgi-bin. It's under the variable, $PROGRAM_ROOT_PASSWORD. It should look something like this: <pre> $PROGRAM_ROOT_PASSWORD ||= 'sneakysneaky';</pre> In this case, the Dada Mail Root Password is, sneakysneaky. If this variable is set to, root_password and that doesn't work, see if the password isn't set in the outside config file. The outside config file is saved in the directory set in the same Config.pm file we are talking about, in a variable called, $PROGRAM_CONFIG_FILE_DIR. That variable should hold the absolute server path to a directory that holds a file named, .dada_config. The file is a plain text file, so open it up in a text editor and again look for the, $PROGRAM_ROOT_PASSWORD variable. If, in either of these locations you find that the Dada Mail Root Password has been set to an odd mixture of numbers/letters/dashes, etc - the Dada Mail Root Password is most likely encrypted and there is no way to decrypt the password, so the best you can do is reset it. You can encrypt a password by visiting your Dada Mail with a query string like this: <a href="http://example.com/cgi-bin/dada/mail.cgi?f=pass_gen">http://example.com/cgi-bin/dada/mail.cgi?f=pass_gen</a> and follow the instructions.   <h2><a name="is_there_any_way_to_stop_a_mass_mailing_once_it_is_started">Is there any way to stop a mass mailing once it is started?</a></h2> Yes. In the list control panel, click on, ``Monitor Your Mailings'', click on the mailing you want to stop and when on that specific message screen, click the, STOP Mailing button. 2.10.10 and below: Yes, but not from the web ui. There are two techniques, kill the process outright and removing the temporary copy of the subscriber list. <ul> <li><a name="item_killing_the_sending_process">Killing the sending process</a>  </li> If you have shell access, issue the kill command with the process id (pid) of the sending process. This id should be writtern down in Dada Mail's usage log - if you haven't set this log explicitly, it should be saved as, dada_usage.txt in whatever directory you set the $LOGS variable to - if you haven't set that variable explicitly, that variable will be set to whatever $FILES is set to (*whew*!) You'll see an entry in the log that looks sort of like this: <pre> [Fri Feb 3 03:45:03 2006] listshortname Message pid: 76354 Subject:This is my subject!</pre> The message pid for this message is, 76354. You'll then want to type in the kill command: <pre> kill 76354 The exact format of issuing the command my be different for your server, but that's the jist of it.</pre>  <li><a name="item_deleting_the_temporary_subscriber_list">Deleting the temporary subscriber list</a>  </li> When mass mailings occur, a temporary file is created, holding all your list subscribers. This keeps the main list free for subscriptions/unsubscriptions while the mailing is going out. Handy. If you remove this file while a mailing is going out, you'll essentially stop the mass mailing. This file is saved in whichever directory you set the, $TMP variable to. If you haven't set the variable, it'll be saved in the directory you set the, $FILES variable to. It looks sort of like this: <pre> mylist.list.20051120131106.78619561_at_example.com</pre> The format is, your list shortname, the type of list you're sending (usually, 'list'), a whole string of numbers that correspond to the Message-id header of the message you're sending out. Remove this file, and you're mailing will stop - you may receive a, ``List Completed'' message, this is normal. </ul>   <hr /> <h1><a name="list_subscribers">List Subscribers</a></h1>   <h2><a name="how_many_subscribers_can_dada_mail_handle">How many subscribers can Dada Mail handle?</a></h2> The amount of subscribers that Dada Mail can handle depends on your server setup. Roughly, the cheaper a setup you have, the smaller a subscription list you're going to be successfully be able to have. Cheap webhosts usually impose limits on the resources available to their clients. These limitations include the amount of emails that can be sent in a window of time, the amount of CPU time a program like Dada Mail can use and software libraries and helper applications available to Dada Mail. Basically, you get what you pay for with web hosts. I do not have any stats. I have listed some hosts I like here: <a href="http://mojo.skazat.com/support/hosting.html">http://mojo.skazat.com/support/hosting.html</a>   <h2><a name="is_there_a_set_limit">Is there a set limit?</a></h2> At the moment, no, there is no factory set limit. You can impose a limit on the amount of subscribers per list by logging into a list using the Dada Mail Root Password. Navigate to: Manage Subscribers - Options Check: Limit The Number of Subscribers And then select what that limit should be. To impose a limit on the amount of lists that can be created, set the Config.pm variable, $LIST_QUOTA to the number of lists you allow. Setting this variable to, undef will allow you to have an unlimited number of lists.   <h2><a name="can_i_track_statistics_like__who_opens_my_email_messages__who_clicks_on_my_urls_or_anything_else_that_ties_activity_of_my_mailing_list_to_specific_email_addresses">Can I track statistics like, who opens my email messages, who clicks on my URLs or anything else that ties activity of my mailing list to specific email addresses?</a></h2> See the clickthrough_tracking.cgi plugin that comes in the Magicbook. It can keep track of url clickthroughs, email opens, # subscribers per message sent and bounces. <a href="http://mojo.skazat.com/support/documentation/clickthrough_tracking.cgi.html">http://mojo.skazat.com/support/documentation/clickthrough_tracking.cgi.html</a>   <h2><a name="can_i_directly_work_with_the_subscription_list">Can I directly work with the subscription list?</a></h2> Sure - although Dada Mail's, ``Add'' admin screen does a good job in keeping your list's clean of invalid email addresses, duplicates, blacklisted addresses - etc. If you're starting a new list and know for sure that you're list is squeaky clean and you're using the default, PlainText subscription backend, you can just open the subscription list. The list itself is saved in a file called: listshortname.list where, listshortname is the shortname of your list. The file itself is probably saved in the directory you've saved in the $FILES Config.pm variable. The format is as follows: One email address per line, followed immediately by a newline. The end of the file has a newline all by itself. All newlines are Unix style. Be very careful when editing the file manually, as unexpected things may happen if the format is broken.   <hr /> <h1><a name="performance">Performance</a></h1>   <h2><a name="how_can_i_get_the_highest_performance_when_using_dada_mail">How can I get the highest performance when using Dada Mail?</a></h2> <ul> <li><a name="item_use_the_sql_backends">Use the SQL backends</a>  </li> <li><a name="item_use_the_smtp_engine">Use the SMTP Engine</a>  </li> <li><a name="item_get_a_dedicated_server_2e">Get a dedicated server.</a>  </li> <li><a name="item_have_a_dedicated_mail_server_2e">Have a dedicated mail server.</a>  </li> <li><a name="item_set_the_config_2epm_variable_2c__24mime_optimize_t">Set the Config.pm variable, $MIME_OPTIMIZE to, faster</a>  </li> <li><a name="item_use_mystery_girl_2c_the_bounce_handler_to_remove_b">use Mystery Girl, the bounce handler to remove bad email addresses</a>  </li> </ul>   <h2><a name="is_there_a_way_to_speed_up_screen_rendering__how_to_use_the_screen_cache_">Is there a way to speed up screen rendering? (How to use the Screen Cache)</a></h2> Yes. As of version 2.10.6, Dada Mail has a caching system for the HTML screens displayed in web browsers. This is handy, since many of the screens Dada Mail creates can be quite resource-intensive. To turn on the Screen Cache, set the Config.pm variable, $SCREEN_CACHE to, 1 <pre> $SCREEN_CACHE = 1;</pre> Screens cached include: <ul> <li><a name="item_the_default_screen">The default screen</a>  </li> <li><a name="item_the_admin_screen">The admin screen</a>  </li> <li><a name="item_list_screens">List screens</a>  </li> <li><a name="item_list_archive_index_screens">List Archive Index screens</a>  </li> <li><a name="item_individual_archived_messages_screens">Individual Archived Messages screens</a>  </li> <li><a name="item_results">Archive Search Results (if the search term is a single word - no funny characters)</a>  </li> <li><a name="item_file_attachments_in_archived_messages">File Attachments in archived messages</a>  </li> <li><a name="item_inline_images_in_archived_messages">Inline Images in archived messages</a>  </li> <li><a name="item_list_atom_feeds">List Atom Feeds</a>  </li> <li><a name="item_list_rss_feeds">List RSS Feeds</a>  </li> </ul> Of particular, archived messages take quite a bit of resources to parse, edit and display. The cache is, flushed, or deleted every time each list changes any list setting via the list control panel, add/edit/removes an archived message in any list and when any change is made in the, ``Edit Template'' list control panel screen. You can also administrate the cache by visiting: <a href="http://example.com/cgi-bin/dada/mail.cgi?f=clear_screen_cache">http://example.com/cgi-bin/dada/mail.cgi?f=clear_screen_cache</a> You'll be able to view cached screens, etc, remove individual cached items and flush the entire cache. Handy. You may also manually remove these files from the cache. The cache is saved in the directory called, cache which itself is created in the directory set in the, $TMP Config variable. If you have not explicitly set this variable, it will be set to the directory you set in the, $FILES Config variable. Each file in the cache directory corresponds to a different screen cached. The names of the cache files correspond loosely to what they represent - for example: <pre> archive_rss.mylist</pre> is the cache for the RSS feed for the list, mylist. Another example: <pre> archive.mylist.20060129172502</pre> is the cache for the archived message with the key (internal identification number) for the list, mylist. You can visit this screen by visiting: <a href="http://example.com/cgi-bin/dada/mail.cgi/achive/mylist/20060129172502/">http://example.com/cgi-bin/dada/mail.cgi/achive/mylist/20060129172502/</a> Note that cached screens are not wholly HTML, RSS, Atom, Image, etc files, but will also include the HTTP headers required to be sent from the webserver for correct viewing. When the cache is enabled, be sure to realize that any changes to Dada Mail's Templates may not be viewable until the cache is flushed. Also remember that any dynamic content from outside of Dada Mail will be made static via the caching scheme. For example, if you pull a list template from a URL and the list template is actually a php script that dynamically creates, say, a side navigation bar, this navigation bar will become static. If you would like to flush the Cache on a regular basis, create a script like: <pre> #!/usr/bin/perl # change the below line to absolute values: use lib qw(./ ./DADA ./DADA/perllib); use DADA::App::ScreenCache; my $c = DADA::App::ScreenCache->new; $c->flush;</pre> And run it as a cron job.   <hr /> <h1><a name="mail_sending">Mail Sending</a></h1>   <h2><a name="i_see_dada_mail_can_send_its_list_messages_in_batches__what_s_the_best_batch_setting">I see Dada Mail can send its list messages in batches. What's the best batch setting?</a></h2> There is no ``best'' batch setting, and the batching feature is meant to be flexible. Some hosting providers only allow a certain amount of email to be sent in a length of time. If, all of a sudden you're getting error messages from the SMTP server or from the sendmail command, you most likely have overburdened the mail server. The best thing to do is to experiment and see what works best with you and your specific constraints. Generally, it's best not to go too overboard with the length of time between batches; I would generally recommend never going over 5 or 10 minutes. I would also recommend not having a batch of more than 1,000 messages. If these limits don't seem reasonable, it's best to lessen the time between batches (from 5 minutes, to 4), instead of having more messages per batch.   <h2><a name="where_are_my_bounce_messages_going">Where are my bounce messages going?</a></h2> Short Answer: Bounces will go to which ever email address is set in the Return-Path of your list messages. Look at the source of an email message sent by Dada Mail, to find where the Return-Path header is set. Longer Answer: A brief tutorial in email sending: An email message has basically two parts: the Message Headers and the Message Body. The Message Body is the easiest thing grasp - it's the message itself. The Message Headers all serve different roles, but a few should be familiar to anyone. For example, the Subject: header is where the subject of the message is, the From header tells you where the message originated from, the To: header tells you where it's going. Easy enough. I'll throw in two more headers at you, that sometimes do not visually appear when you view a message in your mail reader. The first is the Reply-To header. It'll hold a email address, just like the From: and To header. When you reply to a message, and the Reply-To header is present, it'll be sent to that address. If the Reply-To header is not present, your message will be sent to the email address that's present in the, From header. The other header I want to talk about is the Return-Path header. This header also contains an email address and serves a similar purpose as the Reply-To: header, but is instead used for automatic response systems - like when a server bounces your message back, or a vacation script sends a note to you. It'll never be used by a real live human being, so it's not something you need to check. So, in general: <ul> <li><a name="item_reply_2dto">Reply-To</a>  </li> Humans!  <li><a name="item_return_2dpath">Return-Path</a>  </li> Computers! </ul> Saying all that, Dada Mail's list administrator should be what's being set in its message Return-Path. By default, this is probably not the case - you'll have to do some minor tweaks to your list. If you don't, the best bet is that the Return-Path header is set to a email address that is quite foreign to you. Depending on how your sending options are setup, you need to do different tweaks. Here they are: <ul> <li><a name="item_setting_up_the_return_2dpath_when_sending_via_smtp">Setting up the Return-Path when sending via SMTP</a>  </li> In Sending Options - SMTP Options check, Set the Sender of SMTP mailings to the list administration email address  You're all done.  <li><a name="item_setting_up_the_return_2dpath_when_sending_via_the_">Setting up the Return-Path when sending via the sendmail command line</a>  </li> Usually this works: In Sending Options - Advanced check, Add the Sendmail '-f' flag when sending messages You're all done. After checking this option, test and see if mailing is still functioning. Depending on how Sendmail is setup, this could in fact stop messages from being delivered. If this doesn't work, uncheck that option and try checking, Print the 'Return-Path' header in all list emails In my findings, this sometimes works for servers running Qmail - although you're not supposed to be able to directly set the Return-Path header. </ul> And, that's it. Now that you know how to set the Return-Path header, put it to some good use! Set up Mystery Girl, the Bounce Handler for Dada Mail: <a href="http://mojo.skazat.com/support/documentation/dada_bounce_handler.pl.html">http://mojo.skazat.com/support/documentation/dada_bounce_handler.pl.html</a>   <h2><a name="smtp_authentication__huh">SMTP Authentication - huh?</a></h2> One of the main disadvantages of using the, Send via SMTP feature in Dada Mail is actually, setting up a mailing list to use it. Not that you have to jump through flaming hoops to do so, it should be very similar to how you'd set up a desktop mail reader to send messages. But, if you haven't done that, it can be slightly intimidating. <ul> <li><a name="item_sasl_authentication_or_pop_2dbefore_2dsmtp__2d_whi">SASL Authentication or POP-before-SMTP - which one to use?</a>  </li> Currently, there are two different authentication schemes that Dada Mail supports for sending via SMTP. Note: Be very wary if your SMTP server requires no authentication. This is also known as an, ``open relay'' mail server. Any mail sent through an open relay these days will be black listed by spam filters. Because of this fact, most SMTP servers require some sort of authentication. <ul> <li><a name="item_sasl_authentication_2e">SASL Authentication.</a>  </li> The first is called, SASL Authentication. Basically, Dada Mail will log into an SMTP mail server and the SMTP mail server will ask for the correct username and password. When Dada Mail gives this to the SMTP mail server, it can then send mail. Pretty simple. Now, what username and password are you supposed to give the SMTP server? Usually, you'll want to give the username and password that's associated with the list owner's email address. How do you know you're supposed to use SASL authentication? Usually, the documentation provided by your hosting company will tell you if you need to use SASL authentication. If you do not need to use SASL authentication, you'll most likely need to use POP-before-SMTP authentication.  <li><a name="item_pop_2dbefore_2dsmtp_authentication">POP-before-SMTP Authentication</a>  </li> POP-before-SMTP Authentication is slightly different than SASL Auth. Instead of the SMTP mail server requesting the appropriate username and password to log into the SMTP mail server, you'll instead have to first, successfully log into the POP mail server. To clarify, a POP mail server is usually used to fetch received mail, as opposed to an SMTP mail server, which is used to send mail. So POP mail server: receives mail; SMTP mail server, sends mail. The SMTP server will know if you've recently successfully logged into the POP mail server and if so, will allow you to send mail through the SMTP mail server. Sounds weird, right? I think so too. Again, you'll probably want to use the list owner's email address's username/password to log into the POP mail server and again, your hosting company will most likely let you know which authentication is required. </ul> </ul>   <h2><a name="what_s_the_differences_between_the_two_smtp_engines">What's the differences between the two SMTP Engines?</a></h2> Note: As of version 2.10.11, the Mail::Bulkmail engine has removed and the Net::SMTP engine has been used as a replacement. Mail::Bulkmail was the original SMTP engine for Dada Mail. Net::SMTP is a newer (to us) choice. They do a similar job in fairly different ways. Benefits of Mail::Bulkmail: <ul> <li><a name="item_can_send_more_than_one_message_per_smtp_connection">Can send more than one message per SMTP connection.</a>  </li> Connecting to an SMTP server does takes a little time (could be seconds). Multiplied by a list of thousands of email addresses, this time may add up. So, if you find that you need a very speedy delivery, maybe look at using Mail::Bulkmail as the backend. This is the main advertised benefit of Mail::Bulkmail.  <li><a name="item_supports_multiple_tries_at_connecting_to_an_smtp_s">Supports multiple tries at connecting to an SMTP server.</a>  </li> Instead of completely stopping a mailing because it cannot connect to the SMTP server, Mail::Bulkmail does have the option to attempt an SMTP connection more than once. The Net::SMTP engine will simply fail at delivering the message (currently). Although, if Mail::Bulkmail does reach its limit of connections per sending to your entire list, sending will halt entirely. In the Net::SMTP engine, if a message cannot be sent out because of a connection not being established, that specific email address will simply be skipped (check the error logs for the reason, hopefully, as to why). </ul> Disadvantaged of Mail::Bulkmail: <ul> <li><a name="item_multiple_connections_may_not_work_well_with_your_s">Multiple connections may not work well with your SMTP server</a>  </li> There seems to be some problems with this very feature (as been reported to me). It seems to not always work and the entire delivery of a mailing list message to your subscription list may fail half way when Mail::Bulkmail miscommunicates with the SMTP server.  <li><a name="item_bolted_on_sasl_authentication">Bolted on SASL authentication</a>  </li> SASL authentication - basically a way to authorize access to an SMTP server isn't a part of Mail::Bulkmail but was added to the engine by the developer of Dada Mail. Also, it does not support as wide of a range of different authentication schemes as the other choice, Net::SMTP does. It's also most probable that the robustness of SASL authentication via Net::SMTP engine is much better as well. </ul> Advantages of Net::SMTP: <ul> <li><a name="item_good_sasl_support">Good SASL Support</a>  </li> Out of the box it should support, PLAIN, AUTH PLAIN LOGIN and CRAM-MD5 authentication schemes and use the correct one needed, automatically. Mail::Bulkmail has been tweaked to include SASL support, but only the, PLAIN version.  <li><a name="item_ssl_2ftls_support">SSL/TLS support</a>  </li> Net::SMTP support sending via port 465 on a secure sockets layer connection. You will need to manually make sure the, IO::Socket::SSL CPAN module is installed on your server - there isn't really a way to bundle it in the Dada Mail distribution.  <li><a name="item_net_3a_3asmtp_widely_used">Net::SMTP widely used</a>  </li> The Net::SMTP engine is more widely used in Perl applications than Mail::Bulkmail. </ul> Disadvantages to Net::SMTP <ul> <li><a name="item_new">New (to us)</a>  </li> The only real drawback, other than the advantage of Mail::Bulkmail of being able to send more than one message per SMTP connection is that Net::SMTP is a very new addition to Dada Mail and as such, hasn't seen much Real World use. This may cause unexpected results (erm, ``bugs'') with taking advantage of this engine. Let us know, please!  <li><a name="item_ssl_support_requires_io_3a_3asocket_3a_3assl_cpan_">SSL support requires IO::Socket::SSL CPAN module</a>  </li> You'll need to either have the, IO::Socket::SSL module installed, or install it yourself. This module itself requires the OpenSSL library. Long story short, if you were hoping that you can just use SSL connections with Dada Mail - you can, but you'll need a few things already available on your server. The upshot is that these things may already be available. The downshot is, if they're not, it can be difficult to install, if you are not well-versed in administrating your own webserver. But, the support in Dada Mail is there.  <li><a name="item_different_logging_schemes">Different Logging Schemes</a>  </li> Mail::Bulkmail could be set up with different logs for both errors specifically from mail errors (the, $SMTP_ERROR_LOG) and also something called a, conversation log (the, $SMTP_CONVERSATION_LOG) which would have snippets of the actual conversation between the SMTP server and Mail::Bulkmail. These are handy. Currently, any errors reported by Net::SMTP will be logged into the main Dada Mail Error Log ($PROGRAM_ERROR_LOG) and the $SMTP_ERROR_LOG will not be used at all. A similar feature to the $SMTP_CONVERSATION_LOG is available in Net::SMTP, although this log will still be printed into the $PROGRAM_ERROR_LOG. So - To activate very verbose logging of the SMTP conversation when using when using the Net::SMTP engine, set the Config.pm variable, $SMTP_CONVERSATION_LOG to, 1. Please note that sensitive information will be logged, while this variable is set, so DO NOT have this variable set when you are in production. </ul> Both engines do support all the other features of sending and SMTP sending that are supported by Dada Mail: VERP support, batching, etc. Many of the advanced features of Mail Bulkmail including envelop sending and dynamic headers were never supported by Dada Mail, so you shouldn't be missing them in the Net::SMTP engine. More information - <ul> <li><a name="item_mail_3a_3abulkmail">Mail::Bulkmail</a>  </li> <a href="http://search.cpan.org/~jimt/Mail-Bulkmail/Bulkmail.pm">http://search.cpan.org/~jimt/Mail-Bulkmail/Bulkmail.pm</a> Note: Currently Dada Mail uses a fairly customized version of Mail::Bulkmail, based on version 3.09.  <li><a name="item_net_3a_3asmtp">Net::SMTP</a>  </li> <a href="http://search.cpan.org/~gbarr/libnet/Net/SMTP.pm">http://search.cpan.org/~gbarr/libnet/Net/SMTP.pm</a> Also, look at Net::SMTP::SSL, which handles SSL/TLS connections <a href="http://search.cpan.org/~cwest/Net-SMTP-SSL/lib/Net/SMTP/SSL.pm">http://search.cpan.org/~cwest/Net-SMTP-SSL/lib/Net/SMTP/SSL.pm</a> </ul>   <hr /> <h1><a name="archiving">Archiving</a></h1>   <h2><a name="how_do_you_edit_an_archived_message__2_10_7_and_above_">How do you edit an archived message? (2.10.7 and above)</a></h2> Archive editing is built into (again) the main program, you'll see, ``edit'' buttons wherever you'd see the archived message itself, while in the list control panel.   <h2><a name="how_do_you_edit_an_archived_message__2_10_6_and_below_">How do you edit an archived message? (2.10.6 and below)</a></h2> See the archive editor plugin: <a href="http://mojo.skazat.com/support/documentation/archive_editor.cgi.html">http://mojo.skazat.com/support/documentation/archive_editor.cgi.html</a> It works with Dada Mail 2.10.2 and above. Fairly easy to install.   <h2><a name="how_do_you_edit_an_archive_message_with_anything_that_s_below_2_10_2">How do you edit an archive message with anything that's below 2.10.2?</a></h2> You can't.   <h2><a name="i_remember_that_you_used_to_be_able_to_edit_an_archived_message__what_happened">I remember that you used to be able to edit an archived message - what happened?</a></h2> It was broken beyond repair and I threw it away. MIME-messages - the kind that Dada Mail understands how to create and send are non-trivial to edit. I have yet to create a Web-based MIME-editor written in Perl. I'm not sure if anyone has created this: A web-based MIME editor, written in Perl which can take a valid, but incredibly varied format. Not to beat a dead horse, but it's just non-trivial and I haven't gotten the time to create it. Besides, when is the last time you were able to edit the messages you sent from your mail reader?   <h2><a name="ok__i_get_it__there_is_no_way_to_edit_archived_messages__in_versions_below_2_10_2___is_there_a_workaround">OK, I get it, there is no way to edit archived messages (in versions below 2.10.2) - is there a workaround?</a></h2> Yes! There are a few ways. <ul> <li><a name="item_the_2c__22best_22_way">The, ``Best'' Way</a>  </li> Or, How to add a new message to Dada Mail's archive, without sending an actual message: <ol> <li><a name="item_find_the_message_you_would_like_to_edit_2e_copy_it">Find the message you would like to edit. Copy its contents.</a>  </li> If you're just adding a new message, skip this step.  <li><a name="item_log_into_dada_mail_27s_list_control_panel_and_go_t">Log into Dada Mail's List control panel and go to, ``Send a List Message''. (Re)write the message.</a>  </li> <li><a name="item_find_the_link_at_the_bottom_of_the_page_titled_2c_">Find the link at the bottom of the page titled,  Show/Hide Archive Options -. Click it.</a>  </li> <li><a name="item_check_3a_archive_this_message">Check: Archive this message</a>  </li> <li><a name="item_check_3a_archive_but_do_not_send">Check: Archive but DO NOT send</a>  </li> <li><a name="item_date">Change: Back Date ( month/day/year - hour:minute:second )</a>  </li> To whatever you so desire.  <li><a name="item_click_3a_submit_mailing_list_message">Click: Submit Mailing List Message</a>  </li> </ol> This option is also available in the, ``Send a Webpage'' screen. <li><a name="item_the_2c__22edit_the_sql_table_directly_22_2c_way">The, ``Edit the SQL Table directly'', way</a>  </li> If you're using the SQL backend for archives, just edit the message in the SQL table. You'll most likely want to change the, ``subject'' and, ``raw_msg'' columns. Not for the faint of heart.  <li><a name="item_the_2c__22edit_the_archive_backups_and_reload_22_w">The, ``Edit the archive backups and reload'' way</a>  </li> This is definetely not for the faint of heart. HACK ahead: If you are not using the SQL backend for Archives, Dada Mail keeps a backup of your list's archives. If you set the $BACKUPS variable in the Config.pm, they'll be located in this location, in a directory named the same as your list's Short Name. If you did not set this variable, look in the directory you set in, $FILES Inside this directory, you should see another directory called, archives. Navigate into there. Inside that directory, you should see one or more directories, who's names are all in numbers. Find the newest directory and navigate to that one. In that directory, you should see a whole lot of files, whose names are also numbers. Find the message that corresponds to the message-id of the message you want to edit. The format of the file is explained in this faq under, How does Dada Mail save its information? Edit that file. Visit: <a href="http://example.com/cgi-bin/dada/mail.cgi?f=restore_lists">http://example.com/cgi-bin/dada/mail.cgi?f=restore_lists</a> and go through the process of restoring your lists. Heed the warning of making redundant backups. Told you it was a hack.  <li><a name="item_the_2c__22use_an_older_version_of_dada_mail_to_edi">The, ``Use an older version of Dada Mail to edit archives'', way</a>  </li> Install an older version of Dada Mail (2.8.15 or earlier), that's configured to use the same, $FILES directory as your new Dada Mail version, but install it in a separate directory. Use the, ``Add/Edit'' archive features in that version. Your mileage will vary wildly. This will not work well if you're using the SQL backend. Amen. </ul>   <hr /> <h1><a name="glossary_terms">Glossary Terms</a></h1> What the heck is...   <h2><a name="path_to_sendmail">path to sendmail</a></h2> sendmail is a command on the server itself that... sends mail! It's a utility that Dada Mail can use for its mail sending. Usually, it's located at: <pre> /usr/sbin/sendmail</pre> which is the default location set in Dada Mail. If you do not know what the path of sendmail is for your hosting account, use this value. If mail doesn't seem to be sent, ask your hosting provider what the, ``Path to sendmail'' is.   <h2><a name="absolute_path">absolute path</a></h2> An absolute path is a path to some sort of file or directory that starts at the root of the filesystem. Example: <pre> /home/youraccount/ may be the absolute path to your, "home" directory.</pre> When accessing your account via FTP, you may not be able to navigate up to the, ``root'' of your filesystem. This is for security purposes. See also: <a href="http://www.computerhope.com/jargon/a/absopath.htm">http://www.computerhope.com/jargon/a/absopath.htm</a>   <hr /> <h1><a name="about_the_author">About The Author</a></h1>   <h2><a name="so__you_re_a_computer_science_grad__genius">So, you're a Computer Science grad, genius?</a></h2> Ha. No. I actually went to school for Art (Painting/Drawing). I partly worked on Dada Mail, because I thought I could do anything I set myself out to do. Anyone, with enough time, can do something similar - no genius involved, just an open mind.   <h2><a name="so__you_make_a_living_off_of_dada_mail">So, you make a living off of Dada Mail?</a></h2> Basically, yes.   <h2><a name="you_re_rich__huh">You're rich, huh?</a></h2> Ha. No. I live very simply, in a communal living space, with about 10 other people. We all share common resources. I don't have a car, nor many pleasantries. That's just fine with me - to each his/her own I guess.   <h2><a name="i_don_t_get_it__why_do_you_give_the_thing_away_you_could_be_making_some_real_money_">I don't get it, why do you give the thing away? You could be making some REAL money!</a></h2> First, thank you for the advice. I know this way of doing business isn't especially common. I will attempt to break this down: <ul> <li><a name="item_the_program_is_given_away_for_free">The program is given away for free</a>  </li> <li><a name="item_the_support_for_it_2c_is_not_2e">The support for it, is not.</a>  </li> </ul> Allow me to elaborate on this second point: The majority of support for the program is given away for free, and is mostly done so, by me. This comes in the from of posts to the support forum, email lists, personal email correspondences, IM conversations, phone calls, taps on the shoulder at coffee shops (honestly!), etc. There is a minority of people who actually pay for support, mainly with installations of the program: I provide a service for a product that is free. A good majority of people who pay for installation actually pay me and I'm thankful for that majority. Thank you majority! Hiss! minority! A minority of this minority (people who cough up some green) ask for new features to be added to the program. This is: a very small minority. The rest of the features are put in, by myself, written for free, and then given away for free. The idea is that the work will pay off, ``In the future''. This future is usually pretty hazy. The small minority that do pay for support, also (indirectly) support the program for everyone else, including keeping the developer alive. Interesting, no? Business-minded people will agree with me that this is not the best way to maximize my profit margin. This, as ludicris it may sound, is not my intention. The intention is to create a sustainable project, that does make enough money to keep me afloat. The less money that comes in, the less time I'll personally spend on the project. The more money comes in, the more I'll spend. Ebbs and flows. Also interesting. Bottom line: You like the program, help out by supporting it with some money - or like anything you don't believe in - it'll go away. So - can you use this same model for your business? Sure. But, be willing to work a few years for free to become an expert on something you made up. In this respect, it's very much similar to having a small business.   <h2><a name="can_i_outright_buy_out_dada_mail">Can I outright BUY OUT Dada Mail?</a></h2> I suppose so - but I have no idea what you'd buy. If what you want to do is transfer the copyrights of the program to yourself and then relicense the program, I guess you could do that. Don't expect me to catch a low-ball figure.   <hr /> <h1><a name="etc__etc">Etc, Etc</a></h1>   <h2><a name="what_is_dada_mail">What is Dada Mail?</a></h2> Dada Mail is a light-weight, fully featured announce-only Mailing List Manager. It does also support discussion lists, with the help of the dada_bridge.pl script. Discussion support is minimal, compared to its announce-only capabilities. Dada Mail is primarily run as a plain old CGI script, it does not need any special modules installed, except the one it comes with. It does not run as a mod_perl enabled script and needs no special treatment. If you can run CGI scripts on your hosting account, Dada Mail will work for you.   <h2><a name="what_does_dada_mail_do">What does Dada Mail do?</a></h2> Dada Mail takes care of much of the drudgery of maintaining a mailing list. It primarily does three things very very well: <ul> <li><a name="item_list_subscriptions">List Subscriptions</a>  </li> Dada Mail will take care of subscriptions and unsubscriptions from each list it manages. Subscription and Unsubscription requests are done via web forms on web pages. Would-be subscribers fill out a form with their email address. When submitted, Dada Mail will take the request and email a confirmation. This email confirmation will include a special URL that includes a special 'pin' number, which is used to confirm the correct person wants to subscribe. Following this link will subscribe the email address. Unsubscription is a similar process, where someone who wants to unsubscribe will fill out a web form with their email address and receive a confirmation email. Dada Mail does not support email confirmation. That is, confirming an address by having to replying to an email. The URL confirmation is usually much simpler and doesn't make you create an alias email that goes to a program that does the confirmation. We circumvent quite a bit of complexity this way. Dada Mail can be configured to do these two simple things in a variety of ways. Dada Mail also takes account of if the email is already subscribed to the list, if the email is 'blacklisted' and thus unable to subscribe, invalid emails, and a plethora of 'gotchas' when dealing with these things.  <li><a name="item_message_sending">Message Sending</a>  </li> Dada Mail can send List Messages; email messages that go to the entire mailing list. Dada Mail can use the sendmail program to use to mail to, as well as qmail, exim and smail - anything that masquerades as the sendmail program (usually located at /usr/sbin/sendmail) will work. Dada Mail can also send out list messages using an SMTP connection to a SMTP server. Message sending can also be done in 'batches' a desired amount of emails are sent in timed intervals.  <li><a name="item_archiving">Archiving</a>  </li> Dada Mail can archive all list messages it sends. Archived messages are archived with the list message, its subject and the date it was sent. The SQL archive backend saves a raw version of the message, that includes all headers. Archives are viewable and Dada Mail provides many features to make this quite a pleasant experience. </ul>   <h2><a name="how_does_dada_mail_save_its_information">How does Dada Mail save its information?</a></h2> Dada Mail saves its information in many different files, in two (possibly three...) formats, plain text and DB_File and SQL flavors. The list subscription list is saved in either: <ul> <li><a name="item_a_plain_text_file">a plain text file</a>  </li> with one email per line. The file is called 'list_name.list' where 'list_name' is the name of your list, with underscores instead of spaces. Blacklists are stored in a similar way, but with a 'blacklist' extension.  <li><a name="item_an_sql_table">An SQL table</a>  </li> The schema which can be found in the dada/extras/SQL directory of the distribution. </ul> List Settings are saved in DB Files. Dada Mail is flexible in what DB_File package you use, be it DB_File, GDBM, ODBM, or SDBM, the Berkeley DB_File format is preferred. Settings are stored with one setting per key, the key name the same as the setting name. Message archives can also be stored in: <ul> <li><a name="item_db_files">DB_Files</a>  </li> Archived messages are saved with the date sent as the key, looking like: 20010308151009 (YYYYMMDDHHMMSS) with the value being the subject, the message and then the message format, delimited by double colons wrapped in brackets '[::]'. We wish we thought of something better, but we live with it.  <li><a name="item_an_sql_table">An SQL Table</a>  </li> The schema which can be found in the dada/extras/SQL directory of the distribution. </ul>   <h2><a name="does_dada_mail_support_the_saving_of_more_than_the_email_address">Does Dada Mail support the saving of more than the email address?</a></h2> Not yet! But we are currently in the process of fundraising the necessary money to let Justin (erm, me!) to work on it. More information: <a href="http://mojo.skazat.com/features/multiple_fields.html">http://mojo.skazat.com/features/multiple_fields.html</a> <a href="https://www.fundable.org/groupactions/dadamailmultiplefields">https://www.fundable.org/groupactions/dadamailmultiplefields</a>   <h2><a name="who_develops_dada_mail">Who develops Dada Mail?</a></h2> Justin Simoni is the lead designer of Dada Mail. Many other people have helped out along the way, but most everything is the work of his grubby little hands. Justin prides himself on being one of those people who gets into everything. He holds a Bachelors of Fine Art in Painting and doesn't have any ``official'' Computer Science training. A Hacker and Painter ala Paul Graham's book. See his portfolio: <a href="http://justinsimoni.com">http://justinsimoni.com</a> Purchase some art. This kid's going places.   <h2><a name="how_is_dada_mail_developed">How is Dada Mail developed?</a></h2> Dada Mail is developed using the Sourceforge suite of tools. <a href="http://sourceforge.net">http://sourceforge.net</a> I use BBEdit as my text editor - <a href="http://www.barebones.com/products/bbedit">http://www.barebones.com/products/bbedit</a> Transmit as my FTP program - <a href="http://panic.com/transmit/">http://panic.com/transmit/</a> I use jCVS as my CVS client - <a href="http://jcvs.org">http://jcvs.org</a> And not much else;   <h2><a name="can_i_help">Can I help?</a></h2> Yes. In so many ways, depending on your knowledge of the technology involved - and there's a lot, including Network programming, UI design, HTML, CSS, Perl, CGI - lots and gobs more on top of that. If you're at all interested, join the Dada Developers mailing list: <a href="http://mojo.skazat.com/cgi-bin/dada/mail.cgi/list/dadadev/">http://mojo.skazat.com/cgi-bin/dada/mail.cgi/list/dadadev/</a> To get an idea on what's going on. As far as I'm concerned, I'm an absolute gear head when it comes to layout, design and usability. Not always shows up in Dada Mail's design, but I try. Got that BFA and all... I'm passable when it comes to Perl. Really. I'm an absolute clutz when it comes to SQL database design. If you don't know anything about the underlying technology, but are having problems using the program, describe your problem to the developers, either on the boards or on the mailing lists If you know a little about the underlying technology, point us to the problem with error log snippets, etc. If you'd like to start hacking away at the program, start by submitting patches to be applied to the latest version checked out from the CVS server. If you rock the patches, I'll be happy to give you checkin rights - honestly, you'd be my saviour. If you're really good at that, we can talk about babysitter the bunny that lives with me. He's cute.   <h2><a name="is_there_a_cvs_server_i_can_check_in_out_of">Is there a CVS server I can check in/out of?</a></h2> Yes.  <a href="http://mojo.skazat.com/download/cvs.html">http://mojo.skazat.com/download/cvs.html</a>  </body> </html>

View of /DadaFork/extras/documentation/html_version/faq.pod.html

ViewCVS and CVS Help