CRASHMAIL(1)
π CRASHMAIL β a Fidonet *.JAM and MSG tosser π
okay bestie, welcome to the manual page for crashmail(1), from the CrashMail section of the manual. sit down, grab a snack, we're doing Fidonet mail processing and it's gonna be iconic π
β¨ SYNOPSIS β¨
crashmail [SETTINGS filename] [SCAN] [TOSS] [TOSSFILE filename] [TOSSDIR
directory] [SCANAREA area] [SCANLIST filename] [SENDLIST address]
[SENDQUERY address] [SENDUNLINKED address] [SENDHELP address] [SENDINFO
address] [REMOVE address] [RESCAN area RESCANNODE node [RESCANMAX max]]
[VERSION] [LOCK] [UNLOCK] [NOSECURITY]
π DESCRIPTION π
Welcome to CrashMail II!! π So basically, CrashMail II is a more portable version of CrashMail β which was my tosser for Amiga computers, no cap. If you're an old Amiga-version user you'll probably clock some familiar stuff, but some features are gone, like the ARexx port (for obvious reasons, bestie π) and the GUI configuration editor. And the one single feature CrashMail II has that the old CrashMail doesn't? support for JAM messagebases. that's the whole tea. β
π OPTIONS π
SCANβ scan every single area for messages that need to be exported. go off, queen. πTOSSβ toss all the.pktfiles and bundles hanging out in the inbound directory. π₯TOSSFILEfilenameβ toss just this one file you named. β¨TOSSDIRdirectoryβ toss every file inside the directory you named. ποΈSCANAREAareaβ scan only the area you named. π―SCANLISTfilenameβ scan all the areas listed in that file. πRESCANareaRESCANNODEnodeRESCANMAXmaxβ rescans the area you specified for the node you specified. And if you also passRESCANMAX, it sets the maximum number of messages to rescan. πSENDQUERYaddressβ sends a list of linked areas to theREMOTESYSOPof the node you named. π€SENDLISTaddressβ sends a list of available areas to theREMOTESYSTEOPof the node you specified. (yes, it really saysREMOTESYSTEOPin here, we don't fix it, we report it faithfully π)SENDUNLINKEDaddressβ sends a list of unlinked areas to theREMOTESYSOPof the node you specified. π¦SENDHELPaddressβ sends the Areafix help file to theREMOTESYSOPon the node you named. πSENDINFOaddressβ sends Areafix information (that's your password and group access, bestie π) to theREMOTESYSOPon the node you named.SETTINGSfilenameβ use this configuration file instead of the default. also, you can use the environment variableCMCONFIGFILEto set the default configuration file. π οΈVERSIONβ shows version information about CrashMail. βLOCKβ locks CrashMail's configuration file, then peaces out and exits. CrashMail has a simple locking mechanism so that two instances of CrashMail never use the same configuration file at the same time. you can use this if you want to temporarily stop CrashMail from running β like, say, when you're updating the nodelist. πUNLOCKβ removes the lock on CrashMail's configuration file. β οΈ Only use this when the configuration file was previously locked withLOCK, otherwise terrible things might happen. we are so serious rn. πNOSECURITYβ processes all packets without security checks. this is mainly meant to be used withTOSSDIR/TOSSFILEand with packets created by CrashWrite. π
π SEE ALSO π
crashexport(1), crashgetnode(1), crashlist(1), crashlistout(1), crashmaint(1), crashstats(1) crashwrite(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're using the auto-add feature. this creates an 8 digit serial number to use as the path for the area. β¨
heads up: 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, bestie, i'm begging. π
Linux
Don't use the ~ character in paths. those paths get expanded to point to your home directory by the shell and not by the i/o functions in the system, so they will not work in CrashMail. π«
In *.msg areas, make sure all files are named *.msg and not *.MSG! if they're not named in lowercase, CrashMail will not export them. lowercase or nothing, periodt. π₯
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>
and that's the whole page, bestie π«Ά credit where credit is due: this one's from Johan Billing, dated 2014-05-01, CRASHMAIL(1) energy only π slay, stay tossed, and don't forget the lowercase *.msg π
π¦ where this page comes from
- debian bookworm: crashmail 1.7-4 Β· permissive
- debian trixie: crashmail 1.7-4 Β· permissive
- ubuntu jammy: crashmail 1.7-2build1 Β· permissive
- ubuntu noble: crashmail 1.7-4 Β· permissive
- ubuntu questing: crashmail 1.7-5
- ubuntu resolute: crashmail 1.7-5build1 Β· permissive
- ubuntu stonking: crashmail 1.7-5build1 Β· permissive
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms