| |
N5MDT > SYSOP 27.07.26 18:04l 73 Lines 3061 Bytes #999 (0) @ TOPIKA
BID : 2605_N5MDT
Subj: BPQ Suggested Daily Duties
Path: IZ3LSV<I0OJJ<IR0AAB<HB9ON<N5MDT
Sent: 260727/1529Z 2605@N5MDT.#STX.TX.USA.NOAM BPQ6.0.25
>From n5mdt%n5mdt.#stx.tx.usa.noam@i0ojj.ampr.org Mon Jul 27 17:59:52 2026
Received: from i0ojj.ampr.org by i0ojj.ampr.org (JNOS2.0q.1) with SMTP
id AA17066113 ; Mon, 27 Jul 2026 17:59:52 +0200
Message-Id: <2605_N5MDT@ve2pkt.bbs>
>From: n5mdt@n5mdt.#stx.tx.usa.noam
X-JNOS-User-Port: Circuit (SICDRM:IR0AAB-2 IR0AAB-2) -> Sending message
A sysop of a BBS has the duty to make sure his node is operating efficiently and as expected.
Here is my short list of things you can do daily to look for problems in your node or BBS.
This is just my suggestions that I am sharing with you. You are free to ignore, delete, or
pass along to others. This may not apply to other BBS software.
BPQ Sysop Suggested Daily Duties
Using the browser interface to your node...
Check Routes - Ideally you should have a route for each MAP line in your config file.
Check Ports - Are all your ports still working?
Check Stats - See anything unusual? Does Known Nodes = Max Nodes? It shouldn't.
Webmail - Mine
Read all messages to you.
WP messages may be read so that you can spot bad WP records and correct them before you re-send
bad WP Updates to your forwarding partners.
Webmail - Personal Messages
Messages to you should now have a status of PY or PK..
All other Personal messages should either be for local users (PN) or forwarded (PF).
Webmail - Bulls
All bulletins should have a status of BF (forwarded) or B$ (more than 1 queued and not all sent yet).
You may have bulletins with status of BN if you have only one forwarding partner.
Mail Mgmt - Messages
Select each message to see if it has been queued to but not forwarded (yellow). Today's messages may not have sent yet.
Yesterdays and prior messages should have all been sent by now (green). Resolve any forwarding errors.
Node Index - View Log - BBS
Scan for errors. Use browser feature to find on page.
Things like ERROR, Failure, Invalid Command all indicate problems that need to be resolved if multiple instances.
Message Rejected by.... Not fatal. Indicates that message transfer did not occur for stated reason.
Look for messages that are displayed in the log. Either you or your forwarding partner are not allowing
messages to be in binary. But, that's ok if you don't want to use binary. Some software may not do binary.
Node Index - View Log - Telnet
Look for unusual activity. i.e. Unknown users trying to log in to your node.
Node Index - View Logs - CMS Log (if you are a gateway)
Look for any errors. Possibly your gateway password is wrong. Usually a users password is incorrect.
Sometimes a user will connect by hand rather than with Winlink Express. Look for bad commands. It may
be necessary to ban a user.
File not found means that you just have not had any connections yet today. Not fatal.
Note: Topika is my distribution list name for all of my forwarding partners. You received this because
you are one of my forwarding partners. If you received this in error then please contact me.
No, this does not address everything, just the common things.
73,
Mark, N5MDT
Read previous mail | Read next mail
| |
