This screen is used to change the behavior on how mail is sent using Dada Mail.
When checked, mail sending will be done directly through a SMTP server, instead of using the, "sendmail" command. If you have a very large list, it is suggested that you use this option.
You will need to setup the SMTP server and possibly a username and password, this is done in the SMTP Options screen.
Setting up SMTP sending in Dada Mail is very similar to setting up a mail reader, Like Microsoft's Outlook, or Apple's Mail.app for out going mail. Dada Mail needs to know what your SMTP server is to send mail to.
Ask your hosting provider if you're given an SMTP server to use and then ask what the address is of this SMTP server. Commonly, the SMTP server will be located at mail.example.com, or smtp.example.com or even example.com
The SMTP sort is almost always, 25. Only change this if you are told otherwise.
Dada Mail will try a few times to connect to your SMTP server without giving up. Five times is usually enough; any more will be like beating a dead horse.
Most SMTP servers will require some sort of authentication before you can use them. This is to stop anyone that shouldn't use your mail server from using it, such as malicious spammers. There are currently two popular ways to do this, SASL and POP-before-SMTP. If you do not know which to use, ask your hosting provider.
SASL authentication stands for, Simple Authentication and Security Layer, and is an extension to the SMTP protocol to allow authentication to SMTP servers. Ask your hosting provider if your SMTP server supports SASL authentication and what to use for the username and password.
Currently, Dada Mail only supports PlainText authentication.
Pop-before-SMTP authentication works by logging into your POP3 server (The POP3 mail server handles receiving mail). The POP3 server requires its own username/password. A successful login to the mail server will be seen as evidence that you should have access to the SMTP server. It's sort of weird and somewhat of a hack, but it's a popular way to go about things.
If you do not know the details of any of the information needed to log into the POP3 server, ask your system administrator. This login information will be different depending on the email address you use as the list owner. If you check, Set the Sender of SMTP mailings to the list administration email address, make sure you have the POP3 login information for the list admin.
Before saving this information, make sure to test your POP3 login information.
When checked, this option will set the Return-Path header to the list administrator, instead of the list owner. This is handy if you are setting up Mystery Girl, the Bounce Handler for Dada Mail.
Batch Sending essentially allows you to throttle, or slow down, your mail sending. You may want to do this because too much email being sent at one time is bogging down your mail server, or you are being hosted on a shared hosting account that has limitations on the amount of mail sent at one time.
Batch Sending allows you to set an amount of messages to be sent and then an amount of time to pause between another batch of messages.
As a general rule of thumb, set batches to a small number of messages sent and a short length of time, rather than a larger number of messages to send between a large amount of time. For example: 100 messages every five minutes is better than sending 1200 messages every hour.
When checked, will enable batch sending .
When checked, an email will be sent to the list owner, letting them know when a batch has been sent. If the amount of batches you have is generating too many batch confirmations, you can uncheck this option and periodically check the Dada Mail Usage Logs, which can be set in the Config.pm file, under $PROGRAM_USAGE_LOGS
When checked, an email will be sent to the list owner, letting them know that a mailing is complete.
The Precedence header is supposed to help set the priority of an email message. It's somewhat useless and should only be set to either list or nothing at all.
Like the Preference header, the Priority header is supposed to help set the priority of an email message but is now basically useless. It's best to keep this at normal.
A Character Set is used by computers to understand how different letters, numbers etc, are internally represented. Different languages may need a different character set to have email messages seen correctly.
The default in Dada Mail is English (en) iso-8859-1
If you do not see a charset you want in this list, you can modify the list via the Config.pm file by tweaking @CHARSETS
There are several ways to encode an email message for sending. The default, 8bit.
Here is a list of the different encodings and what they do (from the MIME::Lite docs) :
When checked, messages sent using Dada Mail will only have the email address of the person it is From: and To: This option was initially put in to overcome a limitation of the SMTP part of Dada Mail which couldn't understand email addresses with a name, (example: "John Smith <jsmith@example.com>).
When checked, list-specific headers will be written into the email headers of outgoing messages. List-specific headers look like this:
List: examplelist List-Archive: <http://example.com/cgi-bin/dada/mail.cgi?f=archive&l=examplelist> List-ID: <examplelist.example.com> List-Owner: <listowner@example.com> List-Subscribe: <http://example.com/cgi-bin/dada/mail.cgi?f=s&l=examplelist> List-Unsubscribe: <example.com/cgi-bin/dada/mail.cgi?f=u&l=examplelist> List-URL: <example.comcgi-bin/dada/mail.cgi?l=examplelist>
Basically, they'll allow the subscriber information about the mailing list and make your messages sent to your mailing list look more legitimate.
Many mail readers, such as Eudora and even pine read the headers and add functionality to the mail reader itself.
It is suggested the you always use these list-specific headers.
When checked, a flag will be used in the sendmail command, essentially setting the list administrator in the Return-Path header of the email message that you are sending. This is handy if you are setting up Mystery Girl, the Bounce Handler for Dada Mail.
There are a few instances when this won't work and can potentially break sending in Dada Mail. If Dada Mail is being run the webserver (usually as nobody or apache) setting the -f flag is usually prohibited. Ask your system administrator if there is a way to run Dada Mail under your hosting account's user.
When checked, will set the Errors-To header with the list administrator as the value. This header is deprecated and shouldn't be used, but the header used to play the role that the Return-Path header does now.
When checked will manually set the Return-Path header to the list administrator. Will most likely not work.
The Return-Path email header is mostly used to say where a bounced email message should go. You usually cannot set this yourself, but can set it indirectly either by setting the sendmail -f flag, or when sending via SMTP, by setting the Sender. Only use this option if you know you can manually set the Return-Path header.
When checked, messages will be sent with the Habeas Warrant Mark headers. The Habeas Warrant Mark is a way to authenticate that a mailing is really from you. You will definitely need a license to use the Habeas Warrant Mark. (see http://www.habeas.com for details).
"Habeas SWE" is or is part of a trademark of Habeas, Inc., 3045 Park Blvd., Palo Alto, CA 94306
Dada Mail is Free Software and is released under the Gnu
Public License.
Dada Mail is written in Perl because we love Perl.