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 .pkt files and bundles hanging out in the inbound directory. πŸ“₯
  • TOSSFILE filename β€” toss just this one file you named. ✨
  • TOSSDIR directory β€” toss every file inside the directory you named. πŸ—‚οΈ
  • SCANAREA area β€” scan only the area you named. 🎯
  • SCANLIST filename β€” scan all the areas listed in that file. πŸ“œ
  • RESCAN area
  • RESCANNODE node
  • RESCANMAX max β€” rescans the area you specified for the node you specified. And if you also pass RESCANMAX, it sets the maximum number of messages to rescan. πŸ”
  • SENDQUERY address β€” sends a list of linked areas to the REMOTESYSOP of the node you named. πŸ“€
  • SENDLIST address β€” sends a list of available areas to the REMOTESYSTEOP of the node you specified. (yes, it really says REMOTESYSTEOP in here, we don't fix it, we report it faithfully πŸ’–)
  • SENDUNLINKED address β€” sends a list of unlinked areas to the REMOTESYSOP of the node you specified. πŸ¦‹
  • SENDHELP address β€” sends the Areafix help file to the REMOTESYSOP on the node you named. πŸ†˜
  • SENDINFO address β€” sends Areafix information (that's your password and group access, bestie πŸ”) to the REMOTESYSOP on the node you named.
  • SETTINGS filename β€” use this configuration file instead of the default. also, you can use the environment variable CMCONFIGFILE to 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 with LOCK, otherwise terrible things might happen. we are so serious rn. πŸ”“
  • NOSECURITY β€” processes all packets without security checks. this is mainly meant to be used with TOSSDIR/TOSSFILE and 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 πŸ’