HTML screens are control by the Config.pm variable, $HTML_CHARSET. You can change this to whatever you'd like. For example, if I'd want to change this to, ut-8 I'd write: $HTML_CHARSET ||= 'utf-8'; Email messages are controlled per list. In the list control, go to: Manage List - Sending Options - Advanced and select the charset you'd like to use under, Default Character Set of Mailings If you do not see the charset you want to set Dada Mail to use, you can add the charset in the Config.

Yes. The translations of previous versions are preserved when you upload updated versions of your HTML files.

If all you want to do is tweak the CSS styles of Dada Mail, the global CSS file is located at: dada/DADA/Template/templates/default_css.css 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: If you're comfortable with CSS, a lot can be changed with this file alone, from fonts and colors to the overall page layouts.

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.

Most browsers allow you to view a page in your chosen encoding by selecting View->Encoding from the browser's main menu. Note, however, that your choice of encoding may not "stick"--that is, when you visit another page, the encoding may change and you may need to set your browser's character encoding again.

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.

In some cases web applications set the response character encoding (which corresponds to the charset value of the content type), but the web page sent to the browser is actually encoded in a different encoding. This problem can occur when using a Servlet 2.3 based container together with the JavaServer Pages Standard Tag Library. The sequence of events is: Application sets the content type including a charset value. This sets the response character encoding.

Email messages that are formatted with text, images, etc. are done by writing the message in HTML. So, write your message in HTML! 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 use a character output stream to instantiate the StreamResult object which holds the transformation output, the Writer uses its own encoding, not the encoding you specify in the stylesheet. If you want to use the stylesheet output encoding, do not use StreamResult(java.io.Writer) to instantiate the holder for the output. Alternatively, you can specify the encoding when you create a Writer (java.io.OutputStreamWriter). Once the Writer exists, you cannot change its encoding.

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.

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.

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.

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:

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.

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.

Change the value that follows it (UTF-8) to your desired character set. For example: AddDefaultCharset UTF-8 would read: AddDefaultCharset ISO-8859-1

Create a new instance of the Marshaller class and use the setEncoding method. You'll also need to make sure the encoding for the Writer is set properly as well: ... String encoding = "ISO-8859-1"; FileOutputStream fos = new FileOutputStream("result.xml"); OutputStreamWriter osw = new OuputStreamWriter(fos, encoding); Marshaller marshaller = new Marshaller(osw); marshaller.setEncoding(encoding); ... The issue occurs with newer versions of Xerces than the version 1.4 that ships with Castor.

http://mojomail.sourceforge.net/support/documentation-dada-2_11-alpha_6/Dada-ized_FormMail_README.pod.html http://mojomail.sourceforge.net/support/documentation-dada-2_11-alpha_6/Dada-ized_TFMail_README.pod.html 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. 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.

The correct SQL table schemas to use to create both the Subscriber and Archive tables are located at: 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.

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. 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.

RFC-1947 M7 is Windows CP1253. At the time the RFC was written I was not aware of that code page designation.

Outbound messages sent from WebMail are fully standards compliant with The Unicode Standard, the Internationally recognized standard for multilingual communication on the Internet and all modern computer systems worldwide. Unicode ensures that the characters you use in your message are the same characters that the recipient of your message sees.

Basic ASCII, Latin1, or UTF8 encoding. Certain characters that are used in the Windows ANSI encoding will not parse properly with an XML parser.

an administrator, login, go to "Admin Menu", "Server", and you will see a field where you can enter an explicit charset for messages sent by FIT. (Override Charset) Download invoker. It's a free, distributable command line utility for creating registered services, created by Idetix (www.idetix.com). Steps: Unzip invoker.zip to your C:\winnt\system32 directory. It consists of three files: invoker.exe, invoker_readme.txt, and invoker_license.txt. There are problems with invoker and Windows 2000.