|To store the tagline file, netmail addressbook, etc.|
|A plain text file, one tagline per line.|
|addressbook (address.bk in DOS, OS/2 or Win32)|
|A list of names and corresponding Fido netmail or Internet email addresses. Note that Internet addresses are prefaced with an I.|
|colors||Specifies the colors to use. (See README.col.)|
|To store the packets as they came from the bbs.|
|To store the reply packet(s) which you have to upload to the bbs.|
|The default directory for saving messages.|
The config file (see above) is a plain text file with a series of values, one per line, in the form "KeyWord: Value". The case of the keywords is not signifigant. Additional, comment lines may be present, starting with replaced by the defaults when you upgrade to a new version.) If any of the keywords are missing, default values will be used.
As of version 0.41, any of these keywords except "Version" may also be specified on the command line. Command-line options take precedence over those in the config file, but their effect is not guaranteed -- some internal pathnames are initialized before the command line is read, for example.
Here are the keywords and their functions:
Version Specifies the version of MultiMail which last updated the file. This is used to check whether the file should be updated and the "new version" prompt displayed. Note that old values are preserved when the file is updated; the update merely adds any keywords that are new. This keyword is also used in the colors file. UserName Your name in plain text, e.g., "UserName: William McBrine". This is used together with InetAddr to create a default "From:" line for SOUP replies; and by itself in OMEN for display purposes (the actual From name is set on upload), and for matching personal messages. InetAddr Your Internet email address, e.g., "InetAddr: firstname.lastname@example.org". This is combined with the UserName in the form "UserName <InetAddr>" ("William McBrine <email@example.com>") to create a default "From:" line for SOUP replies. Note that if neither value is specified, and nothing is typed manually into the From: field when creating a message, no From: line will be generated -- which is perfectly acceptable to at least some SOUP programs, like UQWK. QuoteHead, InetQuote These strings are placed at the beginning of the quoted text when replying in normal or Internet/Usenet areas, respectively. (The distinction is made because the quoting conventions for BBSes and the Internet are different.) Replaceable parameters are indicated with a % character, as follows:
%f = "From" in original message
%t = To
%d = Date (of original message)
%s = Subject
%a = Area
%n = newline (for multi-line headers)
%% = insert an actual percent character
Note that you cant put white space at the start of one of these strings (it will be eaten by the config parser), but you can get around that by putting a newline first.
mmHomeDir MultiMails home directory. TempDir This is the directory where MultiMail puts its temporary files -- by default, as of 0.45, the same as mmHomeDir. The files are actually created within a subdirectory of this directory; the subdirectory is named "workNNNN", where NNNN is a random number (checked against any existing files or directories before being created). signature Path to optional signature file, which should be a simple text file. If specified, it will be appended to every message you write. You should give the full path, not just the name. editor The editor MultiMail uses for replies, along with any command-line options. This may also be a good place to insert spell-checkers, etc., by specifying a batch file here. Note that the default value is just the editor thats (almost) guaranteed to be available, for a given OS (although the Unix "EDITOR" environment variable is checked first), and is in no way a preferred editor; you can and should change it. PacketDir Default packet directory. ReplyDir Default reply packet directory. SaveDir Default directory for saved messages. AddressBook Path and filename of the address book. (You might change this to share it with another installation, but basically this keyword isnt too useful.) TaglineFile Path and filename of the tagline file. This could be altered from a batch file to swap between different sets of taglines. (But note that this value is only read at startup.) You could also share taglines with another program, but be careful with that; MultiMail truncates the lines at 76 characters. ColorFile Path and filename of the colors file. See README.col. UseColors Yes/No. This governs whether color is used, or monochrome. When colors are disabled, the terminals default foreground and background colors are used. Its also a crude way to implement transparency (the only way, if youre not using ncurses) -- the entire background will be transparent when using an appropriate terminal. Transparency Yes/No. Only available in ncurses. (The option will appear, but not work, in non-ncurses, non-PDCurses platforms.) When this is set to Yes, all areas where the background color is the same as the background color set in the "Main_Back" line, in the colors file, are instead set to the default background color, and thus become transparent areas in those terminal programs, like Eterm and Gnome Terminal, that support this. BackFill Yes/No. Normally the background area is filled with a checkerboard pattern (ACS_BOARD characters, in curses terms). You can disable that here, leaving those areas as flat background color. This option is intended mostly to make transparency more effective, but it might help with any color scheme. (Unlike the previous two, its available in PDCurses.) *UncompressCommand, *CompressCommand Command lines (program name, options, and optionally the path) for the archivers to compress and uncompress packets and reply packets. ZIP, ARJ, RAR, LHA and tar/gzip are recognized. The "unknown" values are a catch- all, attempted for anything thats not recognized as one of the other four types; if you have to deal with ARC or ZOO files, you might define the archiver for them here. PacketSort The packet list can be sorted either in inverse order of packet date and time (the newest at the top), or in alphabetical order by filename. "Time" specifies the former, and "Name" the latter. (Actually only the first letter is checked, and case is not signifigant. This applies to the other keywords of this type (the kind that have a fixed set of values to choose from) as well.) The sort type specified here is only the default, and can be toggled from the packet window by pressing $. AreaMode The default mode for the area list: "All", "Subscribed", or "Active". This is the mode that will be used on first opening a packet, but it can be changed by pressing L while in the area list or little area list. For a description of the modes, see USAGE. LetterSort The sort used by default in the letter list. Can be "Subject" (subjects sorted alphabetically, with a case-insensitive compare), "Number" (sorted by message number), "From" or "To". (This can be overridden, as in the packet list.) LetterMode The default mode for the letter list: "All" or "Unread". This is the mode used on first opening an area; it can be toggled by pressing L. (The Marked view is also available in the letter list, but cannot be set as the default here.) ClockMode The display mode for the clock in the upper right corner of the letter window: "Time" (of day), "Elapsed" (since MultiMail started running), or "Off". Charset The character set that the console is assumed to use. Either "CP437" (code page 437, the U.S. standard for the IBM PC and clones) or "Latin-1" (aka ISO-8859-1, the standard for most other systems). Note that the character set of messages is determined separately (q.v.). UseTaglines Yes/No. If no, the tagline window is not displayed at all when composing a message. AutoSaveReplies Yes/No. If yes, the reply packet is saved automatically -- the equivalent of pressing F2, but without a confirmation prompt -- whenever the contents of the reply area are changed. This can be convenient, and even a safety feature if your power supply is irregular, but it provides less opportunity to take back a change (like deleting a message). If no, youre prompted whether to save the changes on exiting the packet. Note that if you say no to that prompt, nothing that you wrote during that session will be saved (unless you saved it manually with F2). StripSoftCR Yes/No. Some messages on Fido-type networks contain spurious instances of character 141, which appears as an accented i in code page 437. These are really so-called "soft returns", where the message was wrapped when composing it, but not indicating a paragraph break. Unfortunately, the character can also appear legitimately as that accented i, so this option defaults to no. It can be toggled temporarily via the I key in the letter window, and it doesnt apply to messages in the Latin-1 character set. This is now applied only in Blue Wave mode. BeepOnPers Yes/No. If yes, MultiMail beeps when you open a message addressed to or from yourself in the letter window. (These are the same messages which are highlighted in the letter list.) UseLynxNav Yes/No. See the description under USAGE. ReOnReplies Yes/No. By popular demand. :-) Setting this to "No" will disable the automatic prefixing of "Re: " to the Subject when replying -- except in areas flagged as Internet email or Usenet, where this is the standard, and is still upheld. QuoteWrapCols Numeric. The right margin for quoted material in replies (including the quote indicator). MaxLines Numeric. See the description under REPLY SPLITTING. outCharset String. See the description under CHARACTER SETS. UseQPMailHead Yes/No. Controls the use of RFC 2047 encoding in outgoing mail headers. UseQPNewsHead Yes/No. Controls the use of RFC 2047 encoding in outgoing news headers. UseQPMail Yes/No. Controls the use of quoted-printable encoding in outgoing mail. UseQPNews Yes/No. Controls the use of quoted-printable encoding in outgoing news. ExpertMode Yes/No. If set to No, the onscreen help menus are not shown; instead, the space is used to extend the size of info windows by a few lines. IgnoreNDX Yes/No. This option applies only to QWK packets. If set to yes, the *.NDX files are always ignored, in favor of the "new" indexing method that depends only on MESSAGES.DAT. This method is slightly slower than the *.NDX-based indexing method (though the delay is dwarfed by packet decompression time), but the most common problem with QWK packets is corrupt *.NDX files. MultiMail now recognizes some cases where the *.NDX files are corrupt and switches automatically, but it doesnt catch them all.
The basic upgrade procedure is to simply copy the new executable over the old one. No other files are needed. When you run a new version of MultiMail (0.19 or later) for the first time, it automatically updates your .mmailrc and ColorFile with any new keywords. (Old keywords, and the values youve set for them, are preserved. However, comments are lost.) Some notes on specific upgrades:
Version 0.48 adds the .mmailrc option "Mouse", which allows you to enable or disable mouse input (for instance, if you dont want to see the mouse cursor).
Version 0.45 adds "TempDir". Note that temporary files are handled differently in this version, and the TEMP and TMP environment variables are ignored. "homeDir" has been removed.
Version 0.43 adds "ClockMode", and makes "UseColors" available in all ports. Also note that CPU usage while idle may be higher in some configurations.
Version 0.41 adds the option "IgnoreNDX".
Version 0.39 changes the function of the "Transparency" option slightly. It now operates on the color set in "Main_Back", rather than Black. Also, if youre accustomed to using the mouse to cut and paste under X or gpm, note that you now have to hold down the shift key while doing this.
Version 0.38 adds "ExpertMode", "Transparency", "UseColors", and "BackFill", while removing the options "BuildPersArea", "UseScrollBars", "MakeOldFlags", and "AutoSaveRead".
Version 0.37 adds "tarUncompressCommand" and "tarCompressCommand".
Version 0.36 adds "LetterMode" and "AreaMode".
Version 0.33 adds "ReOnReplies", "outCharset", "UseQPMailHead", "UseQPNewsHead", "UseQPMail" and "UseQPNews"; changes some default values.
Version 0.32 adds "BuildPersArea" and "MakeOldFlags".
Version 0.30 adds "UserName", "InetAddr", "QuoteHead", "InetQuote", and "QuoteWrapCols".
Version 0.29 adds "UseScrollBars" and "UseLynxNav".
Version 0.28 adds "MaxLines", "StripSoftCR", and "BeepOnPers".
Version 0.26 adds "AutoSaveReplies", "AutoSaveRead", and "UseTaglines".
Version 0.25 adds "Charset", "PacketSort", and "LetterSort". The default packet sort is now by time instead of name.
If youre upgrading from 0.19 to 0.20 or later, and you have a customized ColorFile, be sure to note the new options.
The ColorFile is new in 0.19. Check it out (~/mmail/colors, by default).
As of 0.16, the HOME environment variable can be overridden with MMAIL, or omitted altogether.
If youre upgrading from a version before 0.9, and you have existing reply packets (.rep or .new) whose names are partly or wholly in uppercase, you must rename them to lowercase before version 0.9 or higher will recognize them. (Downloaded packets are not at issue.)
If youre upgrading from a version below 0.8, you may want to manually delete the /tmp/$LOGNAME directory created by previous versions. (0.8 and higher clean out their own temp directories, and use different names for each session.)
If youre upgrading from a version prior to 0.7, please note the changes in the default directories; previously they were "~/mmail/bwdown", etc.
Unlike the other archive types, tar/gzip recompresses the entire packet when updating the .red flags, so it can be a bit slow. Also, the supplied command lines assume GNU tar, which has gzip built-in. Seperated gunzip/tar and tar/gzip command lines are possible, but would require a (simple) external script. MultiMail only checks for the gzip signature, and does not actually verify that the gzipped file is a tar file.
OPX reply packets are always created with a .rep extension, which differs from the behavior of some other readers. If you switch from QWK packets to OPX packets on the same board, MultiMail will _not_ open an old QWK .rep in OPX mode, nor vice versa. (It will try, and will terminate with "Error opening reply packet".)
SOUP reply packets are created with the name "basename.rep", where basename is the part of the original packet name before the first period. (Unlike other formats, theres no actual standard for this in SOUP, but this seems to be the most common form among the SOUP readers I surveyed.) Also, not that I expect anyone to try this, but currently MultiMail is only able to read reply packets generated by other SOUP readers if the replies are in b or B mode, and are one to a file within the packet. Most readers meet the first criterion, but some of them batch all mail and news replies into a single file for each type. A future version of MultiMail will be able to read these, too.
When re-editing a reply, it gets pushed to end of the list of replies.
The R)ename function in the packet window can also be used to move files between directories; however, the destination filename must still be specified along with the path.
If youre using the XCurses (PDCurses) version, and your editor isnt an X app, it will work better if you set MultiMails "editor" keyword to "xterm -e filename" (instead of just "filename"). I decided not to do this automatically because someone might actually use it with an X editor.
Editing and deletion of old replies are available through the REPLY area, which always appears at the top of the area list. This differs from Blue Wave and some other readers.
The Escape key works to back out from most screens, but after you press it, youll have to wait a bit for it to be sensed (with ncurses; not true with PDCurses).
Only Blue Wave style taglines (beginning with "...") are recognized by the tagline stealer. The tagline must be visible on the screen to be taken.
Netmail only works in Blue Wave, OMEN and OPX modes, and is still slightly limited. Netmail from points includes the point address. Internet email is available in Blue Wave and OPX modes, for those doors that support it, and in SOUP mode, using the same interface as Fido netmail.
MultiMail was originally developed under Linux by Kolossvary Tamas and Toth Istvan. John Zero was the maintainer for versions 0.2 through 0.6; since version 0.7, the maintainer is William McBrine <firstname.lastname@example.org>.
Additional code has been contributed by Peter Karlsson, Mark D. Rejhon, Ingo Brueckl, Robert Vukovic and Mark Crispin.
The RSX/NT version is reported to be incompatible with 4DOS: shelling to external programs (archivers or editors) fails. Thanks to Tony Summerfelt for figuring this one out. You can set the MultiMail session to use COMMAND.COM while retaining 4DOS elsewhere.
Red Hat Linux 6.0 (and possibly 6.x) comes with a defective installation of ncurses. When linked to this, MultiMail mostly works, but odd effects appear when scrolling. (Users describe it as double-spaced.) The problem can be fixed by reinstalling ncurses from the source -- not the source RPM that comes with Red Hat, but the original source from the ncurses site (see INSTALL).
SOUP area type M is not recognized yet. First I have to find a program that can generate one. :-)
The ANSI viewer eats a lot less memory than it used to, but it can still be a problem. (Each character/attribute pair takes up four bytes in memory. But lines which have the same attribute throughout are stored as plain text.)
The new file list and bulletin viewer is, as yet, a hack. A better means of selecting which ones to view will be forthcoming, if I can ever decide just how it should look. (Your opinion is welcome.)
If you find any bugs, or have ideas for improvement, please write to me.
|-->||MULTIMAIL (1)||July 19, 2007|