CRASHMAIL(1) CrashMail CRASHMAIL(1)NAME
crashmail - A Fidonet *.JAM and MSG tosser
SYNOPSIS
crashmail [SETTINGS filename] [SCAN] [TOSS] [TOSSFILE filename] [TOSSDIR directory] [SCANAREA area] [SCANLIST filename] [RESCAN area RES-
CANNODE node [RESCANMAX max]] [VERSION] [LOCK] [UNLOCK] [NOSECURITY]
DESCRIPTION
Welcome to CrashMail II! CrashMail II is basically a more portable version of CrashMail, my tosser for Amiga computers. Users of the old
Amiga version will probably find some things familiar while some features are gone such as the ARexx port (for obvious reasons!) and the
GUI configuration editor. The only feature that CrashMail II has and the old CrashMail hasn't is support for JAM messagebases.
OPTIONS
SCAN Scan all areas for messages to export.
TOSS Toss all .pkt files and bundles in inbound directory.
TOSSFILE filename
Toss the specified file.
TOSSDIR directory
Toss all files in the specified directory.
SCANAREA area
Scan the specified area.
SCANLIST filename
Scan all areas listed in the specified file.
RESCAN area
RESCANNODE node
RESCANMAX max
Rescans the specied area for the specied node. If RESCANMAX is specified, it sets the maximum number of messages to rescan.
SETTINGS filename
Use this configuration file instead of the default.You can use the environment variable CMCONFIGFILE to set the default configura-
tion file.
VERSION
Show version information about CrashMail.
LOCK Locks CrashMail's configuration file and then exits. CrashMail has a simple locking mechanism to ensure that two instances of Crash-
Mail never use the same configuration file at the same time. You can use this if you want to temporarily want to stop CrashMail from
running, e.g. when updating the nodelist.
UNLOCK Removes the lock on CrashMail's configuration file. Only use this when the configuration file previously has been locked with LOCK,
otherwise terrible things might happen.
NOSECURITY
Process all packets without security checks. This is intended to be used mainly with TOSSDIR/TOSSFILE and with packets created by
CrashWrite.
SEE ALSO crashexport(1), crashlist(1), crashmaint(1), crashwrite(1), crashgetnode(1), crashstats(1)FILES
crashmail.prefs
BUGS
Win32
If you want to use an old reader that only can handle 8+3 filenames, you have to use %8 in the path of your DEFAULT area if you are using
the auto-add feature. This creates an 8 digit serial number to use as the path for the area. Note that if CrashMail is run twice in a
short period of time (a few seconds), it might create duplicate paths. Avoid %8 if it is at all possible.
Linux
Don't use the ~ character in paths. Such paths are expanded to point to your home directory by the shell and not by the i/o functions in
the system. They will not work in CrashMail.
In *.msg areas, make sure that all files are named *.msg and not *.MSG! If they are not named in lowercase, CrashMail will not export
them.
As an extra bonus, the Linux version of CrashMail can use the syslog instead of using its own log file. Just use "syslog" as the name of
your log file.
If the precompiled binaries in the CrashMail archive don't work on your system, you will have to compile your own. See src/ReadMe.txt for
more information about this.
AUTHOR
CrashMail is written by Johan Billing <billing@df.lth.se>
This manual page was written by Peter Karlsson <peter@softwolves.pp.se>
Johan Billing 1999-08-01 CRASHMAIL(1)
Check Out this Related Man Page
SA-COMPILE(1) User Contributed Perl Documentation SA-COMPILE(1)NAME
sa-compile - compile SpamAssassin ruleset into native code
SYNOPSIS
sa-compile [options]
Options:
--list Output base string list to STDOUT
--sudo Use 'sudo' for privilege escalation
--keep-tmps Keep temporary files instead of deleting
-C path, --configpath=path, --config-file=path
Path to standard configuration dir
-p prefs, --prefspath=file, --prefs-file=file
Set user preferences file
--siteconfigpath=path Path for site configs
(default: /etc/mail/spamassassin)
--updatedir=path Directory to place updates
(default: /var/lib/spamassassin/compiled/<perlversion>/3.003002)
--cf='config line' Additional line of configuration
-D, --debug [area=n,...] Print debugging messages
-V, --version Print version
-h, --help Print usage message
DESCRIPTION
sa-compile uses "re2c" to compile the site-wide parts of the SpamAssassin ruleset. No part of user_prefs or any files included from
user_prefs can be built into the compiled set.
This compiled set is then used by the "Mail::SpamAssassin::Plugin::Rule2XSBody" plugin to speed up SpamAssassin's operation, where
possible, and when that plugin is loaded.
"re2c" can match strings much faster than perl code, by constructing a DFA to match many simple strings in parallel, and compiling that to
native object code. Not all SpamAssassin rules are amenable to this conversion, however.
This requires "re2c" (see "http://re2c.org/"), and the C compiler used to build Perl XS modules, be installed.
Note that running this, and creating a compiled ruleset, will have no effect on SpamAssassin scanning speeds unless you also edit your
"v320.pre" file and ensure this line is uncommented:
loadplugin Mail::SpamAssassin::Plugin::Rule2XSBody
OPTIONS --list
Output the extracted base strings to STDOUT, instead of generating the C extension code.
--sudo
Use sudo(8) to run code as 'root' when writing files to the compiled-rules storage area (which is
"/var/lib/spamassassin/compiled/5.016/3.003002" by default).
--quiet
Produce less diagnostic output. Errors will still be displayed.
--keep-tmps
Keep temporary files after the script completes, instead of deleting them.
-C path, --configpath=path, --config-file=path
Use the specified path for locating the distributed configuration files. Ignore the default directories (usually
"/usr/share/spamassassin" or similar).
--siteconfigpath=path
Use the specified path for locating site-specific configuration files. Ignore the default directories (usually
"/etc/mail/spamassassin" or similar).
--updatedir
By default, "sa-compile" will use the system-wide rules update directory:
/var/lib/spamassassin/compiled/5.016/3.003002
If the updates should be stored in another location, specify it here.
Note that use of this option is not recommended; if sa-compile is placing the compiled rules the wrong directory, you probably need to
rebuild SpamAssassin with different "Makefile.PL" arguments, instead of overriding sa-compile's runtime behaviour.
--cf='config line'
Add additional lines of configuration directly from the command-line, parsed after the configuration files are read. Multiple --cf
arguments can be used, and each will be considered a separate line of configuration.
-p prefs, --prefspath=prefs, --prefs-file=prefs
Read user score preferences from prefs (usually "$HOME/.spamassassin/user_prefs") .
-D [area,...], --debug [area,...]
Produce debugging output. If no areas are listed, all debugging information is printed. Diagnostic output can also be enabled for
each area individually; area is the area of the code to instrument.
For more information about which areas (also known as channels) are available, please see the documentation at
<http://wiki.apache.org/spamassassin/DebugChannels>.
-h, --help
Print help message and exit.
-V, --version
Print sa-compile version and exit.
SEE ALSO Mail::SpamAssassin(3)spamassassin(1)spamd(1)PREREQUESITES
"Mail::SpamAssassin" "re2c" "Mail::SpamAssassin::Plugin::Rule2XSBody"
BUGS
See <http://issues.apache.org/SpamAssassin/>
AUTHORS
The Apache SpamAssassin(tm) Project <http://spamassassin.apache.org/>
COPYRIGHT
SpamAssassin is distributed under the Apache License, Version 2.0, as described in the file "LICENSE" included with the distribution.
perl v5.16.3 2014-06-10 SA-COMPILE(1)