JAMNNTPD(1)

🌸 NAME 🌸

jamnntpd β€” an NNTP server that lets your fave newsreader slide into a JAM messagebase πŸ’…


✨ SYNOPSIS ✨

jamnntpd [options]

πŸ¦‹ DESCRIPTION πŸ¦‹

So bestie, picture this: JamNNTPd is literally an attempt to merge FTN/Fidonet technology with your standard-issue Usenet newsreaders. That's the whole vibe. Basically?? It's an NNTP server that allows newsreaders to access a JAM messagebase. No cap. πŸ‘‘

The behaviour of JamNNTPd is configurable, and you've got the configuration options listed down below in OPTIONS. You can hand them to JamNNTPd in two ways:

  1. As commandline arguments 🌈
  2. In a configuration file (peep the -config command). The preceding dash (-) is optional when an option is given in a file β€” it'll get added automatically if it's missing. And if you want a configuration file pre-loaded with the default settings, just make one with the -create option. πŸŽ€

If JamNNTPd is run with no commandline arguments at all, it will attempt to read options from a file called jamnntpd.config β€” but only if it's actually present, bestie. Under Linux, JamNNTPd will look for this file in the /etc directory, and under Windows it looks in the current directory. πŸ—‚οΈ

And listen: it is not necessary to specify any configuration options at all unless you're fine-tuning JamNNTPd, because the defaults have been designed to be sensible. The defaults ate, honestly. πŸ’–


πŸ’… OPTIONS πŸ’…

🌟 General options 🌟

  • -port <port> or -p <port> β€” sets the port where JamNNTPd listens for connections. The default is 5000.
  • -max <maxconn> or -m <maxconn> β€” the maximum allowed number of connections at one time. The default is 5.
  • -groups <groupsfile> or -g <groupsfile> β€” use this to override the default locations of the config files.
  • -allow <allowfile> or -a <allowfile> β€” use this to override the default locations of the config files.
  • -users <usersfile> or -u <usersfile> β€” use this to override the default locations of the config files.
  • -xlat <xlatfile> or -x <xlatfile> β€” use this to override the default locations of the config files.
  • -logfile <logfile> or -l <logfile> β€” use this to override the default location of the log file. πŸ“
  • -noecholog β€” disables echoing of log messages to the console window. Silence mode, activated. 🀫
  • -debug β€” if this option is used, JamNNTPd will print all sent and received text to the console window. Useful for testing. πŸ”

πŸŽ€ Options for displaying messages πŸŽ€

  • -readorigin β€” get the address from the Origin line instead of the OADDRESS field of the JAM message header. Heads up: this option makes JamNNTPd slower, but it may be useful if your tosser does not set the OADDRESS field.
  • -noencode β€” JamNNTPd by default MIME-encodes headers with non-ascii characters. If you use this option, JamNNTPd will instead send the headers as plain 8-bit text.
  • -strictnetmail β€” makes JamNNTPd use strict article counters for netmail messages. Normally JamNNTPd uses article counters that include all messages, not only those that the user is allowed to read. That behaviour is much faster, but it may cause your newsreader to indicate the presence of new messages in the netmail area even when there are only messages for other users. 😭 Using this option will make JamNNTPd slower, but speed seems to be acceptable for small netmail areas with up to 1000 messages. And lowkey important: users will never be allowed to actually read netmail messages of other users even when this option is not used. πŸ›‘οΈ
  • -def_flowed onoff β€” sets the default of the flowed setting (if no default is specified on the commandline, it will be on by default).
    • flowed: if flowed is on, JamNNTPd will use format=flowed (section 6.5), otherwise it will wrap long lines to a fixed width.
  • -def_showto onoff β€” sets the default of the showto setting (if no default is specified on the commandline, it will be on by default).
    • showto: since there is no receiver for news messages, JamNNTPd can display the receiver name as a part of the sender name. With this option, this behaviour can be turned on or off.
  • These can be modified by the user by logging in with parameters (section 4.4). ✨

πŸ’– Options for posting messages πŸ’–

  • -nostripre β€” JamNNTPd normally strips "Re:" from subject lines of followups. Use this option if you want to retain the "Re:".
  • -notearline β€” JamNNTPd normally puts the information from the X-Newsreader or User-Agent header field in the tearline of posted messages. This option disables this behaviour and leaves the tearline blank.
  • -noreplyaddr β€” JamNNTPd normally adds a REPLYADDR kludge with the e-mail address of the sender in posted messages. Use this option if you don't want REPLYADDR kludges. See also see section 6.4 in ReadMe.txt.
  • -notzutc β€” JamNNTPd normally writes the timezone into a TZUTC kludge when a message is posted. You can use this option if you don't want to create TZUTC kludges.
  • -nocancel β€” disallows the cancelling (deleting) of messages by the users. If allowed, users can only cancel messages from one of their "realnames" and only if the message has not yet been sent. 🚫
  • -smartquote β€” the quoting style of most newsreaders is different from traditional fidonet software. If you enable this option, JamNNTPd will try to change any quoted lines to fidonet style. This means that it will try to insert the initials of the person you reply to before the '>' character, and also that it will try to compound multiple generations of quotes, i.e. "AA> BB>" will be changed into "BB>>".
Okay so this one's a whole thing, bestie. Reformatting quotes in this way means that the user who posts a message will no longer have final say over the final content of the message, since it will be changed after he or she sends it to JamNNTPd. 😬 Since this in principle is a bad thing even if quoted text will look a lot better after reformatting, this option is turned off by default. Periodt.
  • -origin <origin> β€” normally JamNNTPd uses the text found in the Organization header line as the Origin line text in posted messages. You can use this switch to override the Organization line and set your own origin for all posted messages. πŸ‘‘
  • -guestsuffix <suffix> β€” if desired, JamNNTPd can add a suffix to posts from unauthenticated users. To activate that feature, specify the suffix here.

Example: -guestsuffix " [GUEST]". 🫢

  • -echomailjam <echomail.jam> β€” if you specify a filename here, JamNNTPd will write a line to this file with the messagebase and message number for each message that is posted. The file follows the ECHOMAIL.JAM format supported by some tossers.

🧚 Options for configuration files 🧚

  • -config <configfile> β€” read options from the specified configuration file.
  • -create <configfile> β€” create a configuration file with the default settings. Fresh config, just for you. πŸ’œ

🌈 SEE ALSO 🌈

The ReadMe.txt file and makechs(1). Go read 'em, iykyk πŸ“š


πŸ’€ AUTHOR πŸ’€

jamnntpd was written by Johan Billing <billing@df.lth.se>. 🫑

This manual page was written by Robert James Clay <jame@rocasa.us>, for the Debian project (but may be used by others). πŸ’–


And that's the whole page, bestie!! πŸŽ€ This one comes to you straight out of the General Commands Manual, JAMNNTPD(1), dated May 18, 2013. Slay, go run your NNTP server. πŸ¦‹βœ¨

πŸ“¦ where this page comes from