Configuration specifications

It is not necessary to configure Emmesmail manually as the program will request from the user as needed the information necessary to create the configuration files. For those who prefer to configure the files manually, the following information is supplied.

There are four main files that configure Emmesmail. These are accounts, director.txt, msm.ini, and msp.ini.

Additionally, addressbook files, also may be configured by hand.

These configuration files all reside in the <u-dir>/config directory.

********************************accounts***************************************

A list of valid accounts on the local PC is kept, along with other information, in the file <u-dir>/config/accounts. This file may be edited with any ASCII-file editor. The format for the accounts file is, one line per account,


<username>|*|<real-name>|<return-address>|<optional-action>|<archive-directory>

All saved and also all sent emails are stored in the archive-directory, the former in a file called "defin", the later in a file called "defout". All incoming mail that is requested to be saved also will be archived in that direcory. If the archive cannot be opened, incoming mail will be saved in "<u-dir>/userstuff/in.account-name". If the archive-directory entry is "-", mail will not be archived even if a save is requested.

It is seen that the fourth entry for each account can be an action. If that field is left blank (no action), the mail is delivered to <u-dir>/mail/account-name. A typical action entry might be

msm -b %b -t username@vacation_address

The example above allows for automatic mail forwarding, msm being Emmesmail's mail-sending program. The "%b" means that the mailer program, msm, should mail the arriving email to username@vacation_address. If the name of a file appeared instead of %b, that file would be mailed to username@vacation_address. If "%s" appears after "-t", the mail or file will be sent back to the sender.

********************************director.txt********************************

The proper account for each email address that mail may properly be addressed to is determined from the file <u-dir>/config/director.txt The director.txt file contains one or more lines of the format:

RECIPIENT_EMAIL_ADDY|ORIGINATOR_ADDY|SUBJECT TOKEN|ACCOUNT

The way the director file works is that if an email is sent to recipient A, was sent by sender B, and has the subject C, Emmesmail goes through each line in the director file sequentially and compares the recipient to the first field, the sender to the second field, and sees if the subject contains words which match the third field. If that is the case, mail is delivered to the ACCOUNT listed in the fourth field. Any of the first three fields may be represented as a "*", which matches all items it is compared to.

Emmes Technologies' director.txt file looks as follows:

*|*|**SPAM**|spam
Postmaster*|*|*|mark
markie@emmestech.com|ALUMNI NEWS|*|university
markie@emmestech.com|*|*|mark
markie@emmestech.com|*|*||vacationer
jaymie@netvision.net.il|*|*|mark
MITISRA@MITVMA.MIT.EDU|*|*|null

The first line insures that all mail that arrives with "**SPAM**" in the subject line gets sent to the spam mailbox. The second line ensures that mail intended for the Postmaster, gets delivered to the sytem mailbox for the "mark" account, mark being the system administrator. The third line ensures that mail addressed to markie@emmestech.com with the words "ALUMNI NEWS" as part of the subject gets sent to the the mailbox for the "university" account, rather than the "mark" account. The fourth line sends mail addressed to markie@emmestech.com to the "mark" account. When mark goes on vacation, he places the fifth line before the fourth and arranges for the "vacationer" account to have an action that results in forwarding the mail to his vacation address. The sixth line ensures that mail addressed to jamie@netvision.net.il gets sent to the "mark" account. The seventh line ensures that all mail sent to MITISRA@MITVMA.MIT.EDU gets deleted.

********************************msm.ini*************************************

The configuration file msm.ini contains entries of the form mail_PARAM = parameter, where valid values for PARAM are handler, to, from, buf, or subj.

Additionally, the parameters to_info, to_ask, and auth_int, also may be defined.

The command line usage for msm is

     msm [-d] [-vN] -h mail_host -p mail_port -f mail_from -t mail_to
         -b mail_buf  -s mail_subj [-n real_name] [-i to_info]

The optional "-vN", or " -v N", where N is an integer, determines the level of error logging to msm.log. Larger values of N, put more information in the logfiles. Values greater than 30 have no additional effect. The logfiles are kept in <u-dir>/logs. Similar log files exist for msp and msv.

Any of the command line parameters may be omitted if they are defined in msm.ini. If mail_port is totally omitted from both the command line and msm.ini, it will be taken as 25.

The parameter to_info in msm.ini may be 0, 1, or 2. "0" means the "To:" field will be "<Undisclosed-recipients>", "1" means the "To:" field will list only the first email recipient, and "2" means the "To:" field will list all the email recipients.

The parameter to_ask may be 0 or 1. "1" means inquire about the to_info parameter whenever the "To:" field has more than two recipients. "0" means do not inquire, just use the default value of to_info.

The parameter auth_int gives the time after POP3 authorization (in minutes) that an SMTP server using smpt-after-pop authentification, will relay (send) email.

***********************************msp.ini**********************************

The configuration file msp.ini contains entries of the form
mail_PARAM = parameter
valid values for mail_PARAM are mail_handler, mail_box, mail_port, mail_notify, real_name, spam_fate, spam_action, remember_pass, lost_mail, and check_interval.

The mail_box parameter has no effect and is ignored. The mail_notify parameter gives the command to be executed when mail arrives. The default is to launch <installation-dir>/msv, our GUI mail-reading program. mail_handler is the domain name of your ISP's sendmail server. If mail_port is not specified, it is taken as 110.

Valid parameters for spam_fate are the integers 0, 1, or 2. "0" means do not check for spam. "1" means deliver email to user "spam". "2" means delete email. "1" stores the spam and is convenient for examining who is sending you spam. "2" does not retain the spam, although a record of its arrival will be in msp.log.

Valid parameters for return_spam are the integers 0, 1, or 2. "0" means do not return spam. "1" means return email to sender with standard "failed mail delivery" message. "2" means return email to sender with a custom message. Option 2 is not recommended by those agencies that fight spam and has not been implemented as of version 4.11

If remember_pass = 0, username and password will be prompted for at each attempt to log on to POP server.

The parameter, lost_mail, determines the fate of mail that cannot be delivered to a specified account (specified accounts are defined in the file <u-dir>/config/accounts). If lost_mail is 0, homeless mail is deleted, if it is 1, homeless mail is delivered to the Postmaster mailbox, and if it is 2, Emmesmail halts mail delivery temporarily and queries what is desired for the particular homeless mail whose delivery is being attempted.

The parameter, check_interval, the interval, in seconds, between queries of the POP3 server, is not used in the Linux version of Emmesmail. In the Windows version, a program called msc, determined the frequency for querying the POP3 servers. Under Linux, it makes more sense to control this using cron.

The usage for msp is

     msp [-d] [-vN] [-h mail_server] [-p mail_port] [-x profile_handle]

All of the arguments are optional because they may be defined in the msp.ini file. The order of precedence is that msp.ini parameters overide system defaults and command line arguments overide msp.ini entries.

Use the -d option to have msp delete all messages from the POP3 server. They will be delivered first, if not previously delivered. Without the -d option, msp deletes files on the POP server only when msv determines they have been saved in an incoming mail archive (see users file format).

If you want files on the server to be delivered regardless of whether they have been delivered previously, this can be accomplished by making the file <u-dir>/data/mess_deliv null.

As specified above, the default for mail_port is 110.

Msp has a default popserver (the one defined as mail_handler in msp.ini) and default login information. There are two other ways to specify the POP3 server to be used. One is to specify the fully qualified domain name of the POP3 server with the -h commandline option, and the other is to use the -x commandline option.

The -x option enables one to supply a profile handle (one-word reference nickname) to a server, which tells msp how to find the mailserver domain name, the login information, and other optional parameters. With the -h option, msp examines its database of profiles (listed in <u-dir>/popservers/servers), to see if it can obtain valid login information for the specified POP3 server. In all of the above circumstances, upon any failure, msp stops attempting to retrieve mail and a window appears requesting that the user supply valid information as necessary.

****************************address book files******************************

msv, the GUI for Emmesmail, allows each user to have his own address book, which also contains aliases the user may choose. The addressbooks are stored in <u-dir>/config/addresses.<username>. Additions to the address book may be entered through msv, or the file may be edited with any ASCII text editor. The format for each address entry is:

          Last-Name, First-Name:<optional-alias>:<email-address>

The first field is the real name of the person. Since the entries are alphabetized, the last name typically is put before the first name, but this is not necessary. The inclusion of an alias is optional, but the inclusion of the two colons, ":", is not. In other words, "Smith, John:jon:js@aol.com" or "Smith, John::js@aol.com".


Back to main help window