1 <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
4 <title>Citadel/UX Documentation</title>
7 <meta http-equiv="content-type"
8 content="text/html; charset=ISO-8859-1">
15 <h2>a messaging and collaboration platform for BBS and groupware applications</h2>
16 Copyright ©1987-2003 by the Citadel development team:<br>
19 <table cellpadding="2" cellspacing="2" border="0" align="center">
22 <td valign="top">Clint Adams<br>
24 <td valign="top"><i>portability enhancements<br>
28 <td valign="top">Steven M. Bellovin<br>
30 <td valign="top"><i>author of public domain 'parsedate'
35 <td valign="top">Nathan Bryant<br>
37 <td valign="top"><i>build system, security, database
38 access, and others<br>
42 <td valign="top">Art Cancro<br>
44 <td valign="top"><i>overall system design and lead developer<br>
48 <td valign="top">Brian Costello<br>
50 <td valign="top"><i>cosmetics, additional commands<br>
54 <td valign="top">Nick Georbit<br>
56 <td valign="top"><i>additional client features<br>
60 <td valign="top">Michael Hampton<br>
62 <td valign="top"><i>client software development<br>
66 <td valign="top">Andru Luvisi<br>
68 <td valign="top"><i>troubleshooting and development assistance<br>
72 <td valign="top">Daniel Malament<br>
74 <td valign="top"><i>string compare function for IMAP
79 <td valign="top">Stu Mark<br>
81 <td valign="top"><i>additional client features, IGnet
86 <td valign="top">Ben Mehlman<br>
88 <td valign="top"><i>additional client features<br>
92 <td valign="top">Ari Samson<br>
94 <td valign="top"><i>assistance with project management<br>
98 <td valign="top">John Walker<br>
100 <td valign="top"><i>author of public domain base64 encoder/decoder<br>
104 <td valign="top">Steve Williams<br>
106 <td valign="top"><i>documentation<br>
110 <td valign="top">Ethan Young<br>
112 <td valign="top"><i>IGnet protocol design<br>
121 <div align="justify">The entire package is open source; you can redistribute
122 and/or modify it under the terms of the GNU General Public License
123 as published by the Free Software Foundation; either version 2 of the
124 License, or (at your option) any later version.<br>
126 This program is distributed in the hope that it will be useful,
127 but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY
128 or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public
129 License for more details. </div>
131 <div align="justify"><br>
132 For more information, visit either of these locations on the
136 <li>The Citadel home page: <a
137 href="http://www.citadel.org">http://www.citadel.org</a></li>
138 <li>UNCENSORED! BBS, the home of Citadel: <a
139 href="http://uncensored.citadel.org">http://uncensored.citadel.org</a></li>
143 <hr width="100%" size="2">
144 <h2 align="center">Table of Contents</h2>
147 <li><a href="#GPL">License</a></li>
148 <li><a href="#Installation">Installation</a></li>
151 <li><a href="#Everything_in_its_place...">Everything in its place...</a></li>
152 <li><a href="#The_BBS_Login">Creating a system account for Citadel</a></li>
153 <li><a href="#Bypassing_the_login:_prompt">Bypassing the login:
155 <li><a href="#Compiling_the_programs">Compiling the programs</a></li>
156 <li><a href="#Upgrading">Upgrading</a></li>
157 <li><a href="#The_citadel.rc_file">The citadel.rc file</a></li>
158 <li><a href="#Using_an_external_editor_for_message">Using an external
159 editor for message composition</a></li>
160 <li><a href="#Printing_messages">Printing messages</a></li>
161 <li><a href="#URL_viewing">URL viewing</a></li>
162 <li><a href="#Setup_and_login">Setup and login</a></li>
163 <li><a href="#Configuring_your_host_system_to_start">Configuring
164 your host system to start the service</a></li>
165 <li><a href="#Logging_in_for_the_first_time">Logging in for the
167 <li><a href="#Welcoming_new_users">Welcoming new users</a></li>
168 <li><a href="#Space_for_adding_your_own_client">Space for adding
169 your own client features (doors)</a></li>
170 <li><a href="#Troubleshooting_and_getting_help">Troubleshooting
171 and getting help</a><br>
175 <li><a href="#sysop">System Administration</a></li>
178 <li><a href="#Overview_">Overview</a></li>
179 <li><a href="#Aide_commands">Aide commands</a></li>
180 <li><a href="#Editing_rooms">Editing rooms</a></li>
181 <li><a href="#File_directories">File directories</a></li>
182 <li><a href="#Creating_and_editing_user_accounts">Creating and
183 editing user accounts</a></li>
184 <li><a href="#Deleting_and_moving_messages">Deleting and moving
186 <li><a href="#Customizing_the_help_files">Customizing the help
188 <li><a href="#Site_configuration">Site configuration</a><br>
192 <li> <a href="#Configuring_Citadel_for_Internet_e-mail">Configuring
193 Citadel for Internet e-mail</a></li>
196 <li><a href="#Introduction">Introduction</a></li>
197 <li><a href="#Basic_site_configuration">Basic site configuration</a></li>
198 <li><a href="#Enabling_the_Internet_mail_protocols">Enabling the
199 Internet mail protocols</a></li>
200 <li><a href="#Hosting_an_Internet_mailing_list">Hosting an Internet
203 <li><a href="#citmail">Using Citadel in conjunction with another
207 <li><a href="#Building_or_joining_a_Citadel_network">Building or joining
208 a Citadel network</a></li>
211 <li><a href="#Overview__">Overview</a></li>
212 <li><a href="#Conventions_and_etiquette_when">Conventions and etiquette
213 when connecting to the public Citadel network</a></li>
214 <li><a href="#Getting_ready_to_join_the_network">Getting ready to
215 join the network</a></li>
216 <li><a href="#Defining_neighbor_nodes">Defining neighbor nodes</a></li>
217 <li><a href="#Sharing_rooms">Sharing rooms</a></li>
218 <li><a href="#Sending_mail">Sending mail</a></li>
219 <li><a href="#Changing_the_polling_interval">Changing the polling
223 <li><a href="#Database_maintenance">Database maintenance</a></li>
226 <li><a href="#Introduction_">Introduction</a></li>
227 <li><a href="#Database_repair">Database repair</a></li>
228 <li><a href="#ImportingExporting_your_Citadel">Importing/Exporting
229 your Citadel database</a><br>
233 <li><a href="#utilities">Included utilities</a></li>
235 <LI><A HREF="#overview">Overview</a></LI>
236 <LI><A HREF="#aidepost">aidepost</a></LI>
237 <LI><A HREF="#whobbs">whobbs</a></LI>
238 <LI><A HREF="#stats">stats</a></LI>
239 <LI><A HREF="#msgform">msgform</a></LI>
240 <LI><A HREF="#userlist">userlist</a></LI>
241 <LI><A HREF="#readlog">readlog</a></LI>
242 <LI><A HREF="#sendcommand">sendcommand</a></LI>
248 <hr width="100%" size="2"><br>
250 <h2 align="center"><a name="GPL"></a>GNU General Public License<br>
254 <p> Version 2, June 1991 </p>
256 <pre>Copyright (C) 1989, 1991 Free Software Foundation, Inc. <br>59 Temple Place - Suite 330, Boston, MA 02111-1307, USA<br><br>Everyone is permitted to copy and distribute verbatim copies<br>of this license document, but changing it is not allowed.<br></pre>
258 <h3 align="justify">Preamble</h3>
260 <div align="justify"> </div>
262 <p align="justify"> The licenses for most software are designed to take
263 away your freedom to share and change it. By contrast, the GNU General
264 Public License is intended to guarantee your freedom to share and change
265 free software--to make sure the software is free for all its users.
266 This General Public License applies to most of the Free Software Foundation's
267 software and to any other program whose authors commit to using it.
268 (Some other Free Software Foundation software is covered by the GNU Library
269 General Public License instead.) You can apply it to your programs, too.
272 <div align="justify"> </div>
274 <p align="justify"> When we speak of free software, we are referring to
275 freedom, not price. Our General Public Licenses are designed to make
276 sure that you have the freedom to distribute copies of free software
277 (and charge for this service if you wish), that you receive source code
278 or can get it if you want it, that you can change the software or use pieces
279 of it in new free programs; and that you know you can do these things. </p>
281 <div align="justify"> </div>
283 <p align="justify"> To protect your rights, we need to make restrictions
284 that forbid anyone to deny you these rights or to ask you to surrender
285 the rights. These restrictions translate to certain responsibilities
286 for you if you distribute copies of the software, or if you modify it.
289 <div align="justify"> </div>
291 <p align="justify"> For example, if you distribute copies of such a program,
292 whether gratis or for a fee, you must give the recipients all the rights
293 that you have. You must make sure that they, too, receive or can get
294 the source code. And you must show them these terms so they know their
297 <div align="justify"> </div>
299 <p align="justify"> We protect your rights with two steps: (1) copyright
300 the software, and (2) offer you this license which gives you legal permission
301 to copy, distribute and/or modify the software. </p>
303 <div align="justify"> </div>
305 <p align="justify"> Also, for each author's protection and ours, we want
306 to make certain that everyone understands that there is no warranty
307 for this free software. If the software is modified by someone else and
308 passed on, we want its recipients to know that what they have is not
309 the original, so that any problems introduced by others will not reflect
310 on the original authors' reputations. </p>
312 <div align="justify"> </div>
314 <p align="justify"> Finally, any free program is threatened constantly by
315 software patents. We wish to avoid the danger that redistributors of a free
316 program will individually obtain patent licenses, in effect making the program
317 proprietary. To prevent this, we have made it clear that any patent must
318 be licensed for everyone's free use or not licensed at all. </p>
320 <div align="justify"> </div>
322 <p align="justify"> The precise terms and conditions for copying, distribution
323 and modification follow. </p>
325 <div align="justify"> </div>
327 <h3>TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION</h3>
329 <div align="justify"> </div>
331 <p align="justify"> <strong>0.</strong> This License applies to any program
332 or other work which contains a notice placed by the copyright holder
333 saying it may be distributed under the terms of this General Public License.
334 The "Program", below, refers to any such program or work, and a "work
335 based on the Program" means either the Program or any derivative work
336 under copyright law: that is to say, a work containing the Program or
337 a portion of it, either verbatim or with modifications and/or translated
338 into another language. (Hereinafter, translation is included without limitation
339 in the term "modification".) Each licensee is addressed as "you". </p>
341 <p align="justify"> Activities other than copying, distribution and modification
342 are not covered by this License; they are outside its scope. The act
343 of running the Program is not restricted, and the output from the Program
344 is covered only if its contents constitute a work based on the Program
345 (independent of having been made by running the Program). Whether that
346 is true depends on what the Program does. </p>
348 <p align="justify"> <strong>1.</strong> You may copy and distribute verbatim
349 copies of the Program's source code as you receive it, in any medium,
350 provided that you conspicuously and appropriately publish on each copy
351 an appropriate copyright notice and disclaimer of warranty; keep intact
352 all the notices that refer to this License and to the absence of any
353 warranty; and give any other recipients of the Program a copy of this License
354 along with the Program. </p>
356 <p align="justify"> You may charge a fee for the physical act of transferring
357 a copy, and you may at your option offer warranty protection in exchange
360 <p align="justify"> <strong>2.</strong> You may modify your copy or copies
361 of the Program or any portion of it, thus forming a work based on the
362 Program, and copy and distribute such modifications or work under the
363 terms of Section 1 above, provided that you also meet all of these conditions:
366 <p align="justify"> </p>
368 <div align="justify">
370 <li><strong>a)</strong> You must cause the modified files
371 to carry prominent notices stating that you changed the files and
372 the date of any change.
376 <li><strong>b)</strong> You must cause any work that
377 you distribute or publish, that in whole or in part contains or
378 is derived from the Program or any part thereof, to be licensed
379 as a whole at no charge to all third parties under the terms of this
384 <li><strong>c)</strong> If the modified program normally
385 reads commands interactively when run, you must cause it, when
386 started running for such interactive use in the most ordinary way,
387 to print or display an announcement including an appropriate copyright
388 notice and a notice that there is no warranty (or else, saying that
389 you provide a warranty) and that users may redistribute the program
390 under these conditions, and telling the user how to view a copy of
391 this License. (Exception: if the Program itself is interactive but
392 does not normally print such an announcement, your work based on
393 the Program is not required to print an announcement.) </li>
396 These requirements apply to the modified work as a whole.
397 If identifiable sections of that work are not derived from the Program,
398 and can be reasonably considered independent and separate works in themselves,
399 then this License, and its terms, do not apply to those sections when
400 you distribute them as separate works. But when you distribute the
401 same sections as part of a whole which is a work based on the Program,
402 the distribution of the whole must be on the terms of this License, whose
403 permissions for other licensees extend to the entire whole, and thus
404 to each and every part regardless of who wrote it. </div>
406 <p align="justify"> Thus, it is not the intent of this section to claim rights
407 or contest your rights to work written entirely by you; rather, the intent
408 is to exercise the right to control the distribution of derivative or collective
409 works based on the Program. </p>
411 <p align="justify"> In addition, mere aggregation of another work not based
412 on the Program with the Program (or with a work based on the Program)
413 on a volume of a storage or distribution medium does not bring the other
414 work under the scope of this License. </p>
416 <p align="justify"> <strong>3.</strong> You may copy and distribute the
417 Program (or a work based on it, under Section 2) in object code or executable
418 form under the terms of Sections 1 and 2 above provided that you also
419 do one of the following: <!-- we use this doubled UL to get the sub-sections indented, -->
420 <!-- while making the bullets as unobvious as possible. --> </p>
422 <div align="justify">
424 <li><strong>a)</strong> Accompany it with the complete
425 corresponding machine-readable source code, which must be distributed
426 under the terms of Sections 1 and 2 above on a medium customarily
427 used for software interchange; or,
431 <li><strong>b)</strong> Accompany it with a written offer,
432 valid for at least three years, to give any third party, for a
433 charge no more than your cost of physically performing source distribution,
434 a complete machine-readable copy of the corresponding source code,
435 to be distributed under the terms of Sections 1 and 2 above on a
436 medium customarily used for software interchange; or,
440 <li><strong>c)</strong> Accompany it with the information
441 you received as to the offer to distribute corresponding source
442 code. (This alternative is allowed only for noncommercial distribution
443 and only if you received the program in object code or executable
444 form with such an offer, in accord with Subsection b above.) </li>
447 The source code for a work means the preferred form of the
448 work for making modifications to it. For an executable work, complete
449 source code means all the source code for all modules it contains, plus
450 any associated interface definition files, plus the scripts used to control
451 compilation and installation of the executable. However, as a special
452 exception, the source code distributed need not include anything that
453 is normally distributed (in either source or binary form) with the major
454 components (compiler, kernel, and so on) of the operating system on which
455 the executable runs, unless that component itself accompanies the executable.
458 <p align="justify"> If distribution of executable or object code is made
459 by offering access to copy from a designated place, then offering equivalent
460 access to copy the source code from the same place counts as distribution
461 of the source code, even though third parties are not compelled to copy
462 the source along with the object code. </p>
464 <p align="justify"> <strong>4.</strong> You may not copy, modify, sublicense,
465 or distribute the Program except as expressly provided under this License.
466 Any attempt otherwise to copy, modify, sublicense or distribute the
467 Program is void, and will automatically terminate your rights under this
468 License. However, parties who have received copies, or rights, from
469 you under this License will not have their licenses terminated so long
470 as such parties remain in full compliance. </p>
472 <p align="justify"> <strong>5.</strong> You are not required to accept
473 this License, since you have not signed it. However, nothing else grants
474 you permission to modify or distribute the Program or its derivative
475 works. These actions are prohibited by law if you do not accept this
476 License. Therefore, by modifying or distributing the Program (or any work
477 based on the Program), you indicate your acceptance of this License to
478 do so, and all its terms and conditions for copying, distributing or modifying
479 the Program or works based on it. </p>
481 <p align="justify"> <strong>6.</strong> Each time you redistribute the Program
482 (or any work based on the Program), the recipient automatically receives a
483 license from the original licensor to copy, distribute or modify the Program
484 subject to these terms and conditions. You may not impose any further
485 restrictions on the recipients' exercise of the rights granted herein.
486 You are not responsible for enforcing compliance by third parties to this
489 <p align="justify"> <strong>7.</strong> If, as a consequence of a court
490 judgment or allegation of patent infringement or for any other reason
491 (not limited to patent issues), conditions are imposed on you (whether
492 by court order, agreement or otherwise) that contradict the conditions
493 of this License, they do not excuse you from the conditions of this License.
494 If you cannot distribute so as to satisfy simultaneously your obligations
495 under this License and any other pertinent obligations, then as a consequence
496 you may not distribute the Program at all. For example, if a patent
497 license would not permit royalty-free redistribution of the Program by
498 all those who receive copies directly or indirectly through you, then
499 the only way you could satisfy both it and this License would be to refrain
500 entirely from distribution of the Program. </p>
502 <p align="justify"> If any portion of this section is held invalid or unenforceable
503 under any particular circumstance, the balance of the section is intended
504 to apply and the section as a whole is intended to apply in other circumstances.
507 <p align="justify"> It is not the purpose of this section to induce you to
508 infringe any patents or other property right claims or to contest validity
509 of any such claims; this section has the sole purpose of protecting
510 the integrity of the free software distribution system, which is implemented
511 by public license practices. Many people have made generous contributions
512 to the wide range of software distributed through that system in reliance
513 on consistent application of that system; it is up to the author/donor
514 to decide if he or she is willing to distribute software through any other
515 system and a licensee cannot impose that choice. </p>
517 <p align="justify"> This section is intended to make thoroughly clear what
518 is believed to be a consequence of the rest of this License. </p>
520 <p align="justify"> <strong>8.</strong> If the distribution and/or use of
521 the Program is restricted in certain countries either by patents or by copyrighted
522 interfaces, the original copyright holder who places the Program under this
523 License may add an explicit geographical distribution limitation excluding
524 those countries, so that distribution is permitted only in or among countries
525 not thus excluded. In such case, this License incorporates the limitation
526 as if written in the body of this License. </p>
528 <p align="justify"> <strong>9.</strong> The Free Software Foundation may
529 publish revised and/or new versions of the General Public License from
530 time to time. Such new versions will be similar in spirit to the present
531 version, but may differ in detail to address new problems or concerns.
534 <p align="justify"> Each version is given a distinguishing version number.
535 If the Program specifies a version number of this License which applies
536 to it and "any later version", you have the option of following the terms
537 and conditions either of that version or of any later version published
538 by the Free Software Foundation. If the Program does not specify a version
539 number of this License, you may choose any version ever published by
540 the Free Software Foundation. </p>
542 <p align="justify"> <strong>10.</strong> If you wish to incorporate parts
543 of the Program into other free programs whose distribution conditions
544 are different, write to the author to ask for permission. For software
545 which is copyrighted by the Free Software Foundation, write to the Free
546 Software Foundation; we sometimes make exceptions for this. Our decision
547 will be guided by the two goals of preserving the free status of all derivatives
548 of our free software and of promoting the sharing and reuse of software
551 <p align="justify"><strong>NO WARRANTY</strong></p>
553 <div align="justify"> </div>
555 <p align="justify"> <strong>11.</strong> BECAUSE THE PROGRAM IS LICENSED
556 FREE OF CHARGE, THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT
557 PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING
558 THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS"
559 WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING,
560 BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS
561 FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE
562 OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME
563 THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION. </p>
565 <p align="justify"> <strong>12.</strong> IN NO EVENT UNLESS REQUIRED BY
566 APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR
567 ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE PROGRAM AS PERMITTED
568 ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL
569 OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE
570 PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED
571 INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE
572 OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER
573 OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. </p>
575 <p align="justify"> </p>
577 <h3>END OF TERMS AND CONDITIONS</h3>
580 <hr width="100%" size="2"><br>
583 <h2><a name="Installation"></a>Installation</h2>
586 <div align="justify">
589 <p>Citadel/UX is an advanced, multiuser, client/server messaging system
590 suitable for BBS, e-mail, and groupware applications.
591 It is designed to handle the needs of both small dialup systems and
592 large-scale Internet-connected systems. It was originally developed on
593 an Altos system running Xenix, and has been installed and tested on various
594 Unix and Unix-like platforms. The current development environment
595 (and public BBS) is an ordinary Linux system. The current distribution
600 <li>The Citadel/UX server (this is the back end that does all
602 <li>A text-based client program designed with the traditional
603 Citadel "look and feel" (room prompts, dot commands, and the like)
605 <li>Setup programs </li>
606 <li>A set of utilities for system administration and maintenance
608 <li>Documentation </li>
612 <p>Some knowledge of the Unix system is necessary to install and manage the
613 system. It is mandatory that the sysop have "root" access to the operating
614 system. The following are required to install Citadel/UX: </p>
617 <li>A Unix operating system (Linux, BSD, Solaris, Tru64, HP/UX)
619 <li>C compiler (such as gcc or egcs) and "make" </li>
620 <li>POSIX threads (the "pthreads" library) </li>
622 <li><a href="http://www.sleepycat.com">Berkeley DB</a> v4.1
623 or newer (GDBM also works, but its use is officially depracated. If
624 you are building a new system, do <i>not</i> use GDBM. If you have an
625 existing system which uses GDBM, you should migrate it to Berkeley DB
626 as soon as possible.) </li>
627 <li>Enough disk space to hold all of the programs and data </li>
631 <p>If you are running Citadel/UX on a Linux system, it is STRONGLY recommended
632 that you run it on a recent distribution (such as <a
633 href="http://www.redhat.com">Red Hat</a> 7.3 or newer). A new-ish distribution
634 will have most or all of the prerequisite tools and libraries already
635 integrated for you.</p>
637 <h3>Now available:</h3>
640 <li>"WebCit", a gateway program to allow full access to Citadel
641 via the World Wide Web. Interactive access through any Web browser.
643 <li>Access to Citadel via <i>any</i> standards-compliant e-mail
644 program, thanks to Citadel's built-in SMTP, POP, and IMAP services.
645 You can use Netscape/Mozilla, Evolution, Eudora, Pine, or even Microsoft
646 VirusSpreader (better known as "Outlook") with Citadel. </li>
650 <h3>Coming soon:</h3>
653 <li>Newer and better GUI-based clients. </li>
657 <h3><a name="Everything_in_its_place..."></a>Everything in its place...</h3>
659 <p>Hopefully you've unpacked the distribution archive into its own directory.
660 This is the directory in which all Citadel files are located and in
661 which all activity will take place. Several subdirectories have already
662 been created during the unpacking process, and others may be created
663 by the software if needed. Make sure you have Berkeley DB installed on
664 your system, and that you have all the development libraries and headers
665 in place so that you can compile against them. If you don't, you can
666 get the latest Berkeley DB at <a href="http://www.sleepycat.com">http://www.sleepycat.com</a>.
667 If your operating system uses a separate library to support POSIX threads
668 (pthreads), make sure that library is installed as well. This is almost
669 never the case with Linux, but some commercial Unix flavors might need
672 <h3><a name="The_BBS_Login"></a></h3>
674 <h3>Creating a system account for Citadel</h3>
676 <p>As with many Unix programs, Citadel wants to run under its own user ID.
677 Unlike other programs, however, this user ID will do double-duty as a
678 public login for your system if you are running a BBS. This account is
679 typically called "bbs" or "citadel" or something to that effect. You will
680 tell Citadel what the user-id of that account is, and when someone logs
681 in under that account, Citadel will prompt for a user name.</p>
683 <p>The Citadel user should have a unique uid. The home directory should be
684 the one your Citadel installation resides in (in this example we will
685 use <TT>/usr/local/citadel</TT>) and the shell should be either "citadel" in
686 that directory, or a script that will start up citadel (you may wish to set
687 up an external text editor; see below). Example:</p>
689 <pre>bbs::100:1:Citadel Login:/usr/local/citadel:/usr/local/citadel/citadel<br></pre>
691 <p>When you run setup later, you will be required to tell it the username or
692 user ID of the account you created is,
693 so it knows what user to run as. If you create
694 an account called <tt>bbs</tt>, <tt>guest</tt>, or <tt>citadel</tt>, the
695 setup program will automatically pick up the user ID by default.</p>
697 <p>For all other users in /etc/passwd, Citadel will automatically set up
698 an account using the full name (or 'gecos' in Unixspeak) of the user. It'll
699 also ignore any password you supply, because it uses the user's password
700 on the host system. This allows a 'single sign on' type of environment.
701 Note that this does have to be enabled at compile time -- it's the configure
702 option called <tt>--enable-autologin</tt>. Keep in mind that these users
703 can use *either* their Citadel login name or their login name on the host
704 computer, and their password on the host computer.</p>
706 <h3><a name="Bypassing_the_login:_prompt"></a></h3>
708 <h3>Bypassing the <tt>login:</tt> prompt</h3>
710 <p>If you normally log in to your host system using some method other than
711 telnet (such as ssh), you might want the telnet service to go straight
712 into Citadel, instead of displaying the <tt>login:</tt> prompt first.
713 You can do this by having telnetd start citadel directly instead of
714 <tt>/bin/login</tt>. This is actually very simple to implement; all you
715 need to do is make a simple change to your <tt>inetd</tt> or <tt>xinetd</tt>
716 configuration. Here are some configuration examples.</p>
718 <p>An example for <tt>inetd</tt> (put the following line in <tt>/etc/inetd.conf</tt>,
719 replacing any existing telnet configuration line already there):</p>
721 <pre>telnet stream tcp nowait root /usr/sbin/tcpd in.telnetd -L /usr/local/citadel/citadel<br></pre>
723 <p>An example for <tt>xinetd</tt> (if you have a file called <tt>/etc/xinetd.d/telnet</tt>
724 then simply replace that file with this one):</p>
726 <pre>service telnet<br>{<br> flags = REUSE<br> socket_type = stream<br> wait = no<br> user = root<br> server = /usr/sbin/in.telnetd<br> server_args = -L /usr/local/citadel/citadel<br> log_on_failure += USERID<br> disable = no<br>}<br></pre>
728 <p>Please make sure you know what you're doing before you install this! If
729 you are going to put Citadel somewhere other than <tt>/usr/local/citadel</tt>
730 then change the directory name accordingly. If you know of any other
731 local peculiarities which need to be observed, edit the above configuration
732 accordingly as well. And, of course, if you're working remotely, make
733 sure you can successfully log in using SSH before you start changing your
734 telnet configuration, otherwise you could lock yourself out of your system
735 (ask any networking specialist about the dangers of "working inband" --
736 then pull up a chair and get a fresh cup of coffee, because you're going
737 to hear some war stories).</p>
739 <h3><a name="Compiling_the_programs"></a>Compiling the programs</h3>
741 <p>You can easily compile the Citadel system with the following commands:</p>
743 <pre>./configure<br>make<br>make install<br></pre>
745 <p>The 'configure' script will generate a Makefile from the Makefile.in,
746 and it will also write the file "sysdep.h" to your Citadel directory. Please
747 do not edit sysdep.h or Makefile.in yourself. The configure script will
748 figure out your system dependencies and set everything correctly.</p>
750 <p>Mac OS X 10.1 and later are now supported. (Sorry, 10.0 cannot be
752 now or in the future.) You need to install the Developer Tools CD, which
753 you can purchase or download for free from
754 <a href="http://developer.apple.com">http://developer.apple.com</a>. Then run
755 configure like this:</p>
757 <pre>env CC=/usr/bin/cc ./configure (options - see below)<br></pre>
759 <p>By default, the Citadel system will install in <tt>/usr/local/citadel</tt>.
760 If you wish to place it in a different directory, you can instead do:</p>
762 <pre>./configure --prefix=/export/home/citadel (or whatever)<br></pre>
764 <p>If you've got Berkeley DB installed in a non-standard location, you can
765 help the configure script find it by doing something like this:</p>
767 <pre>./configure --with-db=/usr/local/BerkeleyDB-4.1<br></pre>
769 <p>The configure script prefers Berkeley DB if it is available, but will fall
770 back to GDBM if it has to.</p>
772 <p>File permissions are always a bother to work with. You don't want Citadel
773 to crash because someone couldn't access a file, but you also don't want
774 shell users peeking into the binaries to do things like reading others'
775 mail, finding private rooms, etc. The Citadel server needs to be started
776 as root in order to bind to privileged ports, but as soon as its initialization
777 is finished, it changes its user ID to your Citadel user in order to avoid
780 <h3><a name="Upgrading"></a></h3>
784 <p>Any existing Citadel installation which is at version 5.50 or newer may
785 be upgraded in place without the need to discard your existing data files.</p>
787 <p>Upgrading to a new version uses the same build procedure as compiling
788 the program for a fresh install, except that you want to do <tt>make install-exec</tt>
789 instead of <tt>make install</tt>. This will overwrite the programs but
790 not your data. <b>Be sure to shut down citserver during this process!</b>
791 If Citadel is running while you upgrade, you may face data corruption issues.<br>
794 <p>After doing <tt>make install-exec</tt>, you should run <tt>setup</tt>
795 again to bring your data files up to date. Please see the setup section
796 below for more information on this.</p>
798 <h3><a name="The_citadel.rc_file"></a>The <tt>citadel.rc</tt> file</h3>
800 <p>The text-based client included with Citadel is suitable for BBS
802 Much of its command set and other behavior is configurable through a Run
803 Control (RC) file. The standard client looks for this file in the following
807 <li><tt>$HOME/.citadelrc</tt></li>
808 <li><tt>/usr/local/lib/citadel.rc</tt></li>
809 <li><i>your-Citadel-directory</i><tt>/citadel.rc</tt></li>
812 The next couple of sections deal with client-side configuration.
814 <h3><a name="Using_an_external_editor_for_message"></a>Using an external editor
815 for message composition</h3>
817 <p>Citadel/UX has a built-in message editor. However, you can also use your
818 favorite text editor to write messages. To do this you simply put a line
819 in your citadel.rc file like this:</p>
821 <pre>editor=/usr/bin/vi<br></pre>
823 <p>The above example would make Citadel call the vi editor when using the
824 <tt><b>.E</b>nter <b>E</b>ditor</tt> command. You can also make it the
825 default editor for the <tt><b>E</b>nter</tt> command by editing the <tt>citadel.rc</tt>
826 file. <b>But be warned:</b> external editors on public systems can be
827 a security hole, because they usually provide users with the ability to
828 drop into a shell on the host system, or save files using names other than
829 the name of the temporary file they are editing. If you intend to use an
830 external editor on a public BBS, make sure you use one that has been hardened
831 for such a purpose -- one which has had the 'shell' and 'save as' commands
832 disabled, as well as any other functions which a destructive user could
833 use to gain unauthorized access to your host system.</p>
835 <h3><a name="Printing_messages"></a>Printing messages</h3>
837 <p>Citadel/UX can send messages to a printer, or just about anywhere else
838 in your system. The variable <tt>PRINTCMD</tt> in <tt>citadel.rc</tt>
839 specifies what command you use to print. Text is sent to the standard input
840 (stdin) of the print command.</p>
842 <p>So if you did this:</p>
844 <pre>printcmd="nl|pr|lpr -Plocal"<br></pre>
846 <p>...that would add line numbers, then paginate, then print on the printer
847 named "local". There's tons of stuff you can do with this feature. For
848 example, you could use a command like <tt>cat <<$HOME/archive</tt>
849 to save copies of important messages in a textfile. Again, this is probably
850 something you don't want to configure for a public BBS host -- most system
851 administrators don't want remote users sending arbitrary things to local
854 <h3><a name="URL_viewing"></a>URL viewing</h3>
856 <p>This is one more feature which is appropriate for local users. While reading
857 a message that has Internet URL's in it, you can select the <tt><b>U</b>RL-view</tt>
858 command, and it will perform some pre-defined action (usually, this is
859 to open up the URL in a web browser). For example:</p>
861 <pre>urlcmd=netscape -remote "openURL(%s)"<br></pre>
863 <p>In the above example, it would open up the URL in an open <a
864 href="http://www.netscape.com/download">Netscape</a> window.</p>
866 <h3><a name="Setup_and_login"></a></h3>
868 <h3>Setup and login</h3>
870 <p>Before logging in for the first time, you must run the setup program.
871 To begin this procedure, enter the following commands:</p>
873 <pre>cd /usr/local/citadel<br>./setup<br></pre>
875 <p>The setup program will guide you through a simple configuration procedure.
876 It will ask you what directory to place your data files in -- the default
877 is the current directory, which is usually the sensible thing to select.
878 If you want to run more than one instance of Citadel on the same host,
879 however, you can specify a different directory here -- just remember to
880 specify the directory name again when you start up the server later on.</p>
882 <p><tt>setup</tt> will then shut down the Citadel service if it is found to
885 <p>You will then be prompted for the name of the system administrator. This
886 is not merely a cosmetic option -- when you log in to your system a little
887 while from now, you'll log in with this name, and it will automatically
888 assign your account the highest access level.</p>
890 <p>Next, you will be prompted for the User ID of the Citadel account on your
891 host system. If you have an account called <tt>bbs</tt>, <tt>guest</tt>,
892 or <tt>citadel</tt>, that account's UID will be the default. If you
893 are upgrading or reconfiguring an existing system, the existing value
894 will be preserved.</p>
896 <p>Then you will be prompted for a server port number. This is the TCP port
897 which Citadel clients use to connect to your Citadel server. In almost
898 all cases, you want to use the default -- port 504, which is the official
899 port number assigned by the IANA for Citadel implementations.</p>
901 <p>The Citadel service will then be started, and you will see the following
904 <pre>Setup is finished. You may now log in.<br></pre>
906 <p>Setup is now complete, on most systems, anyway. Please see below to find
907 out if you need to do anything else:</p>
909 <h3><a name="Configuring_your_host_system_to_start"></a>Configuring your host
910 system to start the service</h3>
912 <p><b>Please note:</b> this topic involves modifications made to <tt>/etc/services</tt>
913 and <tt>/etc/inittab</tt> in order to configure your host system to automatically
914 start the Citadel service. <tt>setup</tt> will automatically perform these
915 steps if it can, and if you allow it to -- just answer 'Yes' when prompted,
916 and everything will be taken care of for you. If you answer 'No' -- or
917 if your system is a little bit odd (for example, BSD systems don't have
918 <tt>/etc/inittab</tt>) -- read this section and do what you need to in order
919 to get things configured.</p>
921 <p>Before you can use Citadel, you must define the "citadel" service to your
922 system. This is accomplished by adding a line to your /etc/services file
923 that looks something like this:</p>
925 <pre>citadel 504/tcp # Citadel/UX Server<br></pre>
927 <p>504 is the port number officially designated by the IANA for use by Citadel.
928 There should not be any need to use a different port number, unless you
929 are running multiple Citadels on the same computer and therefore need a
930 different port for each one.</p>
932 <p>The next step is to arrange for the server to start. The <tt>citserver</tt>
933 program is the main Citadel server. Before we cover the recommended method
934 of starting the server, let's examine its usage options:</p>
936 <pre>citserver [-hHomeDir] [-xDebugLevel] [-tTraceFile] [-d] [-f]<br></pre>
938 <p>The options are as follows:</p>
940 <p><tt>-hHomeDir</tt> - the directory your Citadel data files live in.
942 of course, be a directory that you've run the <tt>setup</tt> program against
943 to set up some data files. If a directory is not specified, the directory
944 name which was specified in the <tt>Makefile</tt> will be used.</p>
946 <p><tt>-xDebugLevel</tt> - Set the verbosity of trace messages printed. The
947 available debugging levels are: </p>
950 <li>1 - Internal errors (failed thread creation, malloc problems,
952 <li>2 - Network errors (broken sockets, failed socket creation)
954 <li>3 - Begin and end of sessions, startup/shutdown of server </li>
955 <li>5 - Server commands being sent from clients </li>
956 <li>7 - Entry and exit of various functions </li>
957 <li>8 - Entry and exit of critical sections </li>
958 <li>9 - Various debugging checkpoints (insanely verbose) </li>
962 <p><tt>-tTraceFile</tt> - Tell the server where to send its debug/trace output.
963 Normally it is sent to stdout.</p>
965 <p><tt>-d</tt> - Run as a daemon; i.e. in the background. This switch would
966 be necessary if you were starting the Citadel server, for example, from
967 an rc.local script (which is not recommended, because this won't allow
968 the server to automatically restart when it is shut down).</p>
970 <p><tt>-f</tt> - Defragment all the databases upon startup. This isn't normally
971 necessary due to the nature of the data stored in Citadel, but the option
972 is provided in case you need it. (Note that this only applies to GDBM
973 installations; if you are using Berkeley DB it has no effect.)</p>
975 <p>The preferred method of starting the Citadel server is to place an entry
976 in your /etc/inittab file. This will conveniently bring the server up
977 when your system is up, and terminate it gracefully when your system is
978 shutting down. The exact syntax for your system may vary, but here's an
979 entry that could be used on a Linux system:</p>
981 <pre>cit:2345:respawn:/usr/local/citadel/citserver -h/usr/local/citadel -t/dev/tty9 -x3<br></pre>
983 <p>In this example, we've chosen debugging level 3, and have the trace stuff
984 output to one of the virtual consoles. It's important to remember to turn
985 off any getty that is set up on that virtual console, if you do this.
986 After making this change, the command <tt>init q</tt> works on most systems
987 to tell init to re-read the file. If in doubt, just reboot the computer.</p>
989 <h3><a name="Logging_in_for_the_first_time"></a>Logging in for the first time</h3>
991 <p>At this point, your system is ready to run. Run the <tt>citadel</tt> program
992 from the shell and log in as a new user. NOTE: the first user account
993 to be created will automatically be set to access level 6 (Aide). This
994 overcomes some obvious logistical problems - normally, Aide access is given
995 by another Aide, but since there aren't any on your system yet, this isn't
998 <h3><a name="Welcoming_new_users"></a>Welcoming new users</h3>
1000 <p>Sometimes you might decide that you want a welcome message (or several
1001 different messages) automatically mailed to new users upon their first
1002 login. Now there is a way to do this. If you create a room called <tt>New
1003 User Greetings</tt>, and it is a <i>private</i> room (invitation-only probably
1004 makes the most sense), any messages you enter into that room will automatically
1005 be delivered to all new users upon registration.</p>
1007 <p>You can put anything you want there: a welcome message, system policies,
1008 special information, etc. You can also put as many messages there as you
1009 want to (although it really doesn't make sense to clutter new users' mailboxes
1010 with lots of junk).</p>
1012 <p>Don't worry about wasting disk space, either. Citadel has a single-instance
1013 message store, so all the new users are actually looking at the same copy
1014 of the message on disk.</p>
1016 <h3><a name="Space_for_adding_your_own_client"></a>Space for adding your own
1017 client features (doors)</h3>
1019 <p><b>Please take note!</b> This function really represents the "old" way
1020 of doing things, and it doesn't fit in well with the client/server paradigm.
1021 Please consider it "deprecated" because it may be removed someday.</p>
1023 <p>The "doorway" feature is just a generic way to add features to the system.
1024 I called it "Doorway" to make it resemble the doors on non-Unix boards,
1025 but as we all know, us Unix types don't have to write special code to access
1026 the modem. :-) Anyway, when a user hits the <tt><b>*</b></tt> (doorway)
1027 command, Citadel does...</p>
1029 <pre>USERNAME=(username); export USERNAME<br>./subsystem (user-number) (screen-width) (access level)<br></pre>
1031 <p>...so you can put whatever you want in there. I suggest putting in a menu
1032 program to allow the users to pick one of a number of programs, etc. Do
1033 be aware that door programs will only be available when the client and server
1034 programs are running on the <i>same</i> computer, and when the user is running
1035 the text-mode client. Because of these restrictions, Door programs are being
1036 utilized less and less every day.</p>
1038 <h3><a name="Troubleshooting_and_getting_help"></a>Troubleshooting and getting
1041 <p>That's just about all the information you need to install the system.
1042 But if you get stuck, you can visit
1043 <a href="http://uncensored.citadel.org">UNCENSORED! BBS</a>
1044 and report a problem or
1045 ask for help. But if you intend to report a problem getting the Citadel server
1046 to run, <i>please</i> double-check the following things first: </p>
1049 <li>Did you do <tt>./configure && make && make install</tt>
1051 <li>Did you run setup? </li>
1052 <li>Did you start the server? </li>
1056 <p>To report a problem, you can log on to
1057 <a href="http://uncensored.citadel.org">UNCENSORED!</A>
1059 the Citadel network which carries the <tt>Citadel/UX></tt> room. Please
1060 DO NOT e-mail the developers directly. Post a request for help on the
1061 BBS, with all of the following information: </p>
1064 <li>The exact nature of your difficulty </li>
1065 <li>A transcript of the error message(s) if possible </li>
1066 <li>The version of Citadel you are running </li>
1067 <li>The version of Berkeley DB present on your system </li>
1068 <li>Which operating system you are running, and what version </li>
1069 <li>If you are running a Linux system, we need to know which distribution,
1070 and the version of the kernel, libc, and pthreads you are using (it would
1071 help to post the output of a <tt>ldd ./citserver</tt> command). </li>
1076 <div align="center">
1077 <hr width="100%" size="2">
1078 <h2><a name="sysop"></a>System Administration</h2>
1081 <div align="justify">
1082 <h3><a name="Overview_"></a>Overview</h3>
1084 <p>Citadel/UX, when installed properly, will do most of its maintenance by
1085 itself. It is intended to be run unattended for extended periods of
1086 time, and most installations do just that without any software failures.</p>
1088 <p>The system has seven access levels. Most users are at the bottom and have
1089 no special privileges. Aides are selected people who have special access within
1090 the Citadel program. Room Aides only have this access in a certain room.
1091 Preferred users can be selected by Aides for access to preferred only rooms.
1092 A sysop is anyone who has access to the various sysop utilities - these
1093 are in their own executable files, which should have their permissions set
1094 to allow only sysops to run them. You should either create a sysops group
1095 in /etc/group, or use some other existing group for this purpose.</p>
1097 <p>Aides have access to EVERY room on the system, public and private (all
1098 types). They also have access to commands starting with <tt>.<b>A</b>ide</tt>
1099 in addition to being able to delete and move messages. The system room,
1100 <tt>Aide></tt>, is accessible only by those users designated as Aides.</p>
1102 <h3><a name="Aide_commands"></a>Aide commands</h3>
1104 <p>Aides have the following commands available to them that are not available
1105 to normal users. They are:</p>
1110 <td width="30%"><tt> .<b>A</b>ide <b>K</b>ill this room </tt></td>
1111 <td> Deletes the current room from the system. </td>
1114 <td width="30%"><tt> .<b>A</b>ide <b>E</b>dit this room </tt></td>
1115 <td> Allows editing of the properties of the current room.
1116 This is explained in greater detail below. </td>
1119 <td width="30%"><tt> .<b>A</b>ide <b>W</b>ho knows room </tt></td>
1120 <td> For private rooms with access controls, or mailbox rooms,
1121 this command displays a list of users who have access to the current room.
1125 <td width="30%"><tt> .<b>A</b>ide edit <b>U</b>ser </tt></td>
1126 <td> Allows editing of the properties of any user account on
1130 <td width="30%"><tt> .<b>A</b>ide <b>V</b>alidate new users
1132 <td> For public access systems, this command reviews all new
1133 user registrations and allows you to set each new user's access level (or
1134 simply delete the accounts). </td>
1137 <td width="30%"><tt> .<b>A</b>ide enter <b>I</b>nfo file </tt></td>
1138 <td> Each room may contain a short textual description of its
1139 purpose, which is displayed to users upon entering the room for the first
1140 time (or in the room banner, for users of the Web client). This command
1141 allows you to enter or edit that description. </td>
1144 <td width="30%"><tt> .<b>A</b>ide <b>R</b>oom <b>I</b>nvite
1146 <td> Access control command to grant any specific user access
1147 to a private room. </td>
1150 <td width="30%"><tt> .<b>A</b>ide <b>R</b>oom <b>K</b>ick out
1152 <td> Access control command to revoke any specifc user's access
1153 to the current room. This works regardless of whether the room is public
1157 <td width="30%"><tt> .<b>A</b>ide <b>F</b>ile <b>D</b>elete
1159 <td> If the current room has an associated file directory, this
1160 command may be used to delete files from it. </td>
1163 <td width="30%"><tt> .<b>A</b>ide <b>F</b>ile <b>S</b>end over
1165 <td> If the current room has an associated file directory, this
1166 command may be used to transmit a copy of any file in that directory to
1167 another node on a Citadel network. </td>
1170 <td width="30%"><tt> .<b>A</b>ide <b>F</b>ile <b>M</b>ove </tt></td>
1171 <td> If the current room has an associated file directory, this
1172 command may be used to move any file in that directory to another room.
1173 The target room must also have an associated file directory. </td>
1176 <td width="30%"><tt> .<b>A</b>ide <b>M</b>essage edit </tt></td>
1177 <td> This command allows editing of any of the various system
1178 banners and messages which are displayed to users. Type the name of the
1179 banner or message you wish to edit. </td>
1182 <td width="30%"><tt> .<b>A</b>ide <b>P</b>ost </tt></td>
1183 <td> This is the functional equivalent of the <tt><b>E</b>nter
1184 message</tt> command available to all users, except that it allows you
1185 to post using any user name. </td>
1188 <td width="30%"><tt> .<b>A</b>ide <b>S</b>ystem configuration
1189 <b>G</b>eneral </tt></td>
1190 <td> This command allows configuration of a large number of
1191 global settings for your Citadel system. These settings will be explained
1192 in greater detail below. </td>
1195 <td width="30%"><tt> .<b>A</b>ide <b>S</b>ystem configuration
1196 <b>I</b>nternet </tt></td>
1197 <td> This command allows configuration of settings which affect
1198 how your Citadel system sends and receives messages on the Internet. </td>
1201 <td width="30%"><tt> .<b>A</b>ide <b>S</b>ystem configuration
1202 check <b>M</b>essage base </tt></td>
1203 <td> Perform a consistency check on your message store. This
1204 is a very time-consuming operation which should not be performed unless
1205 you have reason to believe there is trouble with your database. </td>
1208 <td width="30%"><tt> .<b>A</b>ide <b>S</b>ystem configuration
1209 <b>N</b>etwork </tt></td>
1210 <td> Configure networking (e-mail, room sharing, etc.) with
1211 other Citadel nodes. </td>
1214 <td width="30%"><tt> .<b>A</b>ide <b>S</b>ystem configuration
1215 network <b>F</b>ilter list </tt></td>
1216 <td> If you are on a large public or semi-public network of
1217 Citadel nodes and you find content from certain systems or individuals
1218 objectionable, you can use this command to define a rule set to automatically
1219 reject those messages when they arrive on your system. </td>
1222 <td width="30%"><tt> .<b>A</b>ide <b>T</b>erminate server <b>N</b>ow
1224 <td> Immediately shut down the Citadel service, disconnecting
1225 any users who are logged in. Please keep in mind that it will start right
1226 back up again if you are running the service from <tt>/etc/inittab</tt>,
1227 so in practice this command will probably not get much use. </td>
1230 <td width="30%"><tt> .<b>A</b>ide <b>T</b>erminate server <b>S</b>cheduled
1232 <td> Shut down the Citadel service the next time there are zero
1233 users connected. This allows you to automatically wait until all users
1234 are logged out. </td>
1237 <td width="30%"><tt> .<b>A</b>ide mailing <b>L</b>ist recipients
1239 <td> Any room may be made into a mailing list. Enter this command
1240 to open an editor window containing the list of Internet e-mail addresses
1241 to which every message posted in the room will be sent. </td>
1244 <td width="30%"><tt> .<b>A</b>ide mailing list <b>D</b>igest
1245 recipients </tt></td>
1246 <td> Similar to the regular mailing list command, except the
1247 messages will be sent out in 'digest' form -- recipients will see messages
1248 from the address of the room itself rather than the address of the author
1249 of each message, and a digest may contain more than one message. Each room
1250 may have any combination of List and Digest recipients. </td>
1253 <td width="30%"><tt> .<b>A</b>ide <b>N</b>etwork room sharing
1255 <td> Configures the sharing of the current room's contents with
1256 other Citadel nodes. Messages posted in this room on any Citadel system
1257 will automatically be replicated to other Citadel systems carrying the
1264 <h3><a name="Editing_rooms"></a>Editing rooms</h3>
1266 <p>This command allows any aide to change the parameters of a room. Go to
1267 the room you wish to edit and enter the <tt><b>.A</b>ide <b>E</b>dit
1268 room</tt> command. A series of prompts will be displayed. The existing
1269 parameters will be displayed in brackets; simply press return if you want
1270 to leave any or all of them unchanged.</p>
1272 <pre> <br>Room name [IG's Fun Room]:<br></pre>
1274 <p>...the name of the room.</p>
1276 <pre>Private room [Yes]? <br></pre>
1278 <p>...enter Yes if you wish to restrict access to the room, or no if the room
1279 is to be accessible by all users. Note that Citadel doesn't bother users
1280 about access to rooms every time they need to access the room. Once a user
1281 gains access to a private room, it then behaves like a public room to them.
1282 The following four questions will only be asked if you selected Private...</p>
1284 <pre>Accessible by guessing room name [No]?<br></pre>
1286 <p>...if you enter Yes, the room will not show up in users' <tt><b>K</b>nown
1287 rooms</tt> listing, but if they <tt><b>.G</b>oto</tt> the room (typing
1288 the room's full name), they will gain access to the room.</p>
1290 <pre>Accessible by entering a password [No]?<br>Room password [mypasswd]: <br></pre>
1292 <p>...this adds an additional layer of security to the room, prompting users
1293 for a password before they can gain access to the room.</p>
1295 <p>If you did not select guessname or passworded, then the only way users
1296 can access the room is if an Aide explicitly invites them to the room using
1297 the <tt><b>.A</b>ide <b>R</b>oom <b>I</b>nvite user</tt> command.</p>
1299 <pre>Cause current users to forget room [No] ? No<br></pre>
1301 <p>Enter Yes if you wish to kick out anyone who currently has access to the
1304 <pre>Preferred users only [No]? No<br></pre>
1306 <p>Enter Yes if you wish to restrict the room to only users who have level
1307 5 (Preferred User) status (and Aides too, of course). You should make
1308 the room public if you intend to do this, otherwise the two restrictions
1309 will be COMBINED.</p>
1311 <pre>Read-only room [No]? No<br></pre>
1313 <p>If you set a room to Read-Only, then normal users will not be allowed to
1314 post messages in it. Messages may only be posted by Aides, and by utility
1315 programs such as the networker and the "aidepost" utility. This is useful
1316 in situations where a room is used exclusively for important announcements,
1317 or if you've set up a room to receive an Internet mailing list and posting
1318 wouldn't make sense. Other uses will, of course, become apparent as
1319 the need arises.</p>
1321 <p>Now for a few other attributes...</p>
1323 <pre>Directory room [Yes]? Yes<br></pre>
1325 <p>...enter Yes if you wish to associate a directory with this room. This
1326 can be used as a small file repository for files relevant to the topic
1327 of the room. If you enter Yes, you will also be prompted with the following
1330 <pre>Directory name [mydirname]: <br></pre>
1332 <p>...the name of the subdirectory to put this room's files in. The name
1333 of the directory created
1334 will be <tt><i><your Citadel directory></i>/files/<i><room
1335 dir name></i></tt>.</p>
1337 <pre>Uploading allowed [Yes]? Yes<br></pre>
1339 <p>...enter Yes if users are allowed to upload to this room.</p>
1341 <pre>Downloading allowed [Yes]? Yes<br></pre>
1343 <p>...enter Yes if users are allowed to download from this room.</p>
1345 <pre>Visible directory [Yes]? Yes<br></pre>
1347 <p>...enter Yes if users can read the directory of this room.</p>
1349 <pre>Network shared room [No]? No<br></pre>
1351 <p>...you can share a room over a network without setting this flag, and
1352 vice versa, but what this flag does is twofold: </p>
1355 <li>It prevents people with no network access from entering messages
1357 <li>Messages are displayed with the name of their originating system
1358 in the header. </li>
1362 <pre>Permanent room [No]? No<br></pre>
1364 <p>Citadel contains an 'auto purger' which is capable of removing rooms which
1365 have not been posted in for a pre-defined period of time (by default
1366 this is set to two weeks). If you wish to keep this from happening to
1367 a particular room, you can set this option. (Keep in mind that <tt>Lobby></tt>,
1368 <tt>Aide></tt>, any private mailbox rooms, any network shared rooms,
1369 and any rooms with a file directory are automatically permanent.)</p>
1371 <pre>Anonymous messages [No]? No<br>Ask users whether to make messages anonymous [No]? No<br></pre>
1373 <p>...you can have rooms in which all messages are automatically anonymous,
1374 and you can have rooms in which users are prompted whether to make a
1375 message anonymous when they enter it. The real identity of the author
1376 of each message is still revealed to the Room Aide for this room, as well
1377 as any system-wide Aides.</p>
1379 <pre>Room aide [Joe Responsible]: <br></pre>
1381 <p>...on larger systems, it helps to designate a person to be responsible
1382 for a room. Room Aides have access to a restricted set of Aide commands,
1383 ONLY when they are in the room in which they have this privilege. They
1384 can edit the room, delete the room, delete and move messages, and invite
1385 or kick out users (if it is a private room), but they cannot perform aide
1386 commands that are not room-related (such as changing users access levels).</p>
1388 <pre>Listing order [64]: <br></pre>
1390 <p>This is just a simple way to try to control the order rooms are listed
1391 in when users call up a <tt><b>K</b>nown Rooms</tt> listing. Rooms with
1392 a lower listing order are displayed prior to rooms with a higher listing
1393 order. It has no other effect. For users who list rooms in floor order,
1394 the display will sort first by floor, then by listing order.</p>
1396 <pre>Message expire policy (? for list) [0]:<br></pre>
1398 <p>This provides you with the opportunity to select how long each message
1399 will remain in a room before automatically being deleted. Press <tt><b>?</b></tt>
1400 for a list of options. You can choose to keep messages around forever
1401 (or until they are manually deleted), until they become a certain number
1402 of days old, or until a certain number of additional messages are posted
1403 in the room, at which time the oldest ones will scroll out.</p>
1405 <p>You will notice that you can also fall back to the default expire policy
1406 for the floor upon which the room resides. This is the default setting.
1407 You can change the floor's default with the <tt><b>;A</b>ide <b>E</b>dit
1408 floor</tt> command. The default setting for the floor default, in turn,
1409 is the system default setting, which can be changed using the <tt><b>.A</b>ide
1410 <b>S</b>ystem configuration <b>G</b>eneral</tt> command.</p>
1412 <pre>Save changes (y/n)? Yes<br></pre>
1414 <p>...this gives you an opportunity to back out, if you feel you really messed
1415 things up while editing.</p>
1417 <h3><a name="File_directories"></a>File directories</h3>
1419 <p>If you have created any directory rooms, you can attach file descriptions
1420 to the filenames through a special file called <tt>filedir</tt>. Each line
1421 contains the name of a file in the directory, followed by a space and
1422 then a description of the file, such as:</p>
1424 <pre>myfile.txt This is a description of my file.<br>phluff A phile phull of phluff!<br></pre>
1426 <p>...this would create file descriptions for the files <tt>myfile.txt</tt>
1427 and <tt>phluff</tt> which would be displayed along with the directory.
1428 It should also be noted that when users upload files to your system, they
1429 will be prompted for file descriptions, which will be added to the <tt>filedir</tt>
1430 file. If one does not exist, it will be created.</p>
1432 <h3><a name="Creating_and_editing_user_accounts"></a>Creating and editing
1435 <p>Anyone with Aide level access may use the <tt><b>.A</b>ide edit <b>U</b>ser</tt>
1436 command to create and/or edit user accounts. There are several parameters
1437 which can be set here.</p>
1439 <p>To create a user:</p>
1441 <pre>Lobby> . Aide edit User <br>User name: New User Name<br>No such user.<br>Do you want to create this user? Yes<br></pre>
1443 <p>At this point, the new user account has been created, and the command will
1444 continue as if you were editing an existing account. Therefore the remainder
1445 of this procedure is the same for creating and editing:</p>
1447 <pre>Lobby> . Aide edit User <br>User name: person of significance<br>User #70 - Person of Significance PW: <br> <br><br>, <br> <br> <br><br>Current access level: 4 (Network User)<br></pre>
1449 <p>The blank lines are the user's 'registration' information -- personal
1450 information such as full name, address, telephone number, etc. This information
1451 will comprise the user's vCard in both their user profile and in the Global
1454 <pre>Change password [No]: No<br></pre>
1456 <p>...answer Yes to set or change the password for this account.</p>
1458 <pre>Access level [4]: <br></pre>
1460 <p>...this allows you to set or change the access level for this account.
1461 The access levels available are as follows: </p>
1464 <li>0 - Deleted. (This immediately deletes the account.) </li>
1465 <li>1 - New, unvalidated user </li>
1466 <li>2 - Problem user (severely restricts account - use for probationary
1468 <li>3 - User with no network privileges. Same access as a normal
1469 user except cannot post messages in rooms shared on a network. </li>
1470 <li>4 - Normal user </li>
1471 <li>5 - Preferred user (access is granted to privileged rooms) </li>
1472 <li>6 - Aide (administrative access to the whole system) </li>
1476 <pre>Permission to send/receive Internet mail [ No]? No<br></pre>
1478 <p>If your system is configured to only allow Internet mail privileges to
1479 certain users, this is where you can grant or revoke that privilege.</p>
1481 <pre>Ask user to register again [Yes]: Yes<br></pre>
1483 <p>If you answer Yes to this question, the user will be presented with a
1484 'registration' screen or set of prompts, the next time they log in using
1485 a Citadel client. This will prompt them for their full name, address, telephone
1488 <pre>Times called [0]: <br>Messages posted [0]: <br></pre>
1490 <p>These statistics are available for informational purposes only, so there
1491 is normally no need to change them.</p>
1493 <pre>Set last call to now [No]: No<br>Purge time (in days, 0 for system default [0]: <br></pre>
1495 <p>Citadel contains an auto-purger which is capable of automatically deleting
1496 accounts which have not been accessed in a predefined period of time.
1497 If you choose to perform this operation, you can 'touch' the account of
1498 a wayward user by setting their 'last call' time to 'now'. You can also
1499 adjust, on a per-user basis, the amount of time which must pass before
1500 their account is purged by the system. This time is set in days. You
1501 can also specify 0 days to indicate that you wish to use the system default
1504 <h3><a name="Deleting_and_moving_messages"></a>Deleting and moving messages</h3>
1506 <p>Aides and Room Aides have the ability to delete and move messages. After
1507 each message, the normal prompt appears:</p>
1509 <pre>(8) <B>ack <A>gain <Q>uote <R>eply <N>ext <S>top m<Y> next <?>help -><br></pre>
1511 <p>Entering <tt><b>D</b>elete</tt> will delete the message. A <tt>(y/n)</tt>
1512 prompt will appear to confirm that you really want to delete the message.
1513 Entering <tt><b>M</b>ove</tt> will prompt for a room to which the message
1514 should be moved.</p>
1516 <h3><a name="Customizing_the_help_files"></a>Customizing the help files</h3>
1518 <p>The subdirectory called <tt>help</tt> contains your system's help files.
1519 There's nothing hard-coded into the system that dictates what files should
1520 be there. Whenever a user types the command <tt><b>.H</b>elp</tt> followed
1521 by the name of a help file, it displays the contents of that help file.</p>
1523 <p>The help files that come with the system, of course, are enough to guide
1524 a user through its operation. But you can add, change, or remove help
1525 files to suit whatever is appropriate for your system.</p>
1527 <p>There are several strings that you can put in help files that will be automatically
1528 substituted with other strings. They are:</p>
1530 <pre> <br> ^nodename = The node name of your system on a Citadel/UX network<br> ^humannode = Human-readable node name (also your node name on C86Net)<br> ^fqdn = Your system's fully-qualified domain name<br> ^username = The name of the user reading the help file<br> ^usernum = The user number of the user reading the help file<br> ^sysadm = The name of the system administraor (i.e., you)<br> ^variantname = The name of the software you're running<br> ^bbsdir = The directory on the host system in which you have<br> installed the Citadel system.<br></pre>
1532 <p>So, for example, you could create a help file which looked like:</p>
1534 <pre> "Lots of help, of course, is available right here on ^humannode. Of<br>course, if you still have trouble, you could always bug ^sysadm about it!"<br></pre>
1536 <h3><a name="Site_configuration"></a>Site configuration</h3>
1538 <p>Once your Citadel server is up and running, the first thing you'll want
1539 to do is customize and tune it. This can be done from the text-based client
1540 with the <tt><b>.A</b>ide <b>S</b>ystem configuration <b>G</b>eneral</tt>
1541 command, or from WebCit (if you have it installed) by clicking 'Advanced
1542 Options' followed by 'Edit site-wide configuration.' Either method will
1543 offer the same configuration options. This document shows the text mode
1544 client being used.</p>
1546 <p>The first set of options deal with the identification of your system.</p>
1548 <pre>Lobby> . Aide System configuration General<br>Node name [uncnsrd]: <br>Fully qualified domain name [uncensored.citadel.org]: <br>Human readable node name [Uncensored]: <br>Modem dialup number [US 914 999 9999]: <br>Geographic location of this system [Mount Kisco, NY]: <br>Name of system administrator [IGnatius T Foobar]: <br>Paginator prompt [<jinkies
1549 !="" more="" text="" on="" the="" next="" screen="">]: <br></jinkies></pre>
1551 <p>'Node name' refers to the short, unqualified node name by which your system
1552 is known on a Citadel network. Generally it will be the same as the unqualified
1553 host name of your computer; this is, in fact, the default setting.</p>
1555 <p>Then enter the fully-qualified domain name (FQDN) of your system. If you
1556 are not on the Internet, you can simply set it to the same as your unqualified
1557 host name. Otherwise you should set this value to the host name by which
1558 your system is most commonly known.</p>
1560 <p>The field called 'Human-readable node name' (also known as the 'node title'
1561 or 'organization name' in other software) is used solely for display purposes.
1562 Set it to the actual name of your system as you want it to appear in banners,
1565 <p>If you have a modem or bank of modems answering data calls for your system,
1566 enter it in the field marked 'Modem dialup number.' Otherwise you may
1569 <p>'Geographic location of this system' is another display field. Enter a
1570 city and state, or city and country. </p>
1572 <p>'Name of system administrator' is important! Any user who logs on with
1573 the name you enter here will automatically be granted Aide privileges.
1574 This is one of two ways for the system administrator to grant himself/herself
1575 Aide access to the system when initially setting it up. (The other is simply
1576 to have the first account created on a new installation.)</p>
1578 <p>The next set of options are your system's security settings. Before delving
1579 into the actual options, we should review the various access levels available
1580 on the system. Citadel has seven access levels:</p>
1583 <li>0 (Deleted). A user whose access level is set to 0 will automatically
1584 be deleted by the system. </li>
1585 <li>1 (New User). Users at this level may only read messages.
1586 Entering messages is prohibited, except in the <tt>Mail></tt> room,
1587 where a message to 'sysop' may be entered. </li>
1588 <li>2 (Problem User). Also known as 'Twit.' </li>
1589 <li>3 (Local User). May enter messages, except in rooms shared
1590 on a Citadel network. </li>
1591 <li>4 (Network User). May enter messages in every accessible room.
1593 <li>5 (Preferred User). Use of this level is up to the whim of
1594 the system administrator. </li>
1595 <li>6 (Aide). Access is granted to the administrative functions
1596 of the system. (This access level may also be granted to a user only for
1597 a specific room, please see 'Room Aide' for more information.) </li>
1601 <pre>Require registration for new users [No]: No<br>Disable self-service user account creation [No]: No<br>Initial access level for new users [4]:<br>Access level required to create rooms [4]: <br>Automatically give room aide privs to a user who creates a private room [No]: No<br><br>Automatically move problem user messages to twit room [Yes]: Yes<br>Name of twit room [Trashcan]: <br>Restrict Internet mail to only those with that privilege [No]: No<br>Allow Aides to Zap (forget) rooms [Yes]: Yes<br>Allow system Aides access to user mailboxes [Yes]: Yes<br>Log all pages [No]: No<br></pre>
1603 <p>'Registration' refers to the process of a user entering various personal
1604 contact information (real name, address, telephone number, etc.) into
1605 the system. When enabled, this information is stored as a vCard object
1606 on the system in two places: the user's <tt>My Citadel Config></tt> room,
1607 and in the <tt>Global Address Book></tt> room. (Note: the latter should
1608 be made private on publicly-accessible systems, for obvious reasons.)</p>
1610 <p>If you answer Yes to 'Require registration for new users' then each new
1611 user, upon creating a new account, will immediately be entered into the
1612 registration process. On the other hand, if you answer Yes to 'Disable
1613 self-service user account creation' then new users will not be able to log
1614 in at all -- all accounts must be created by an Aide.</p>
1616 <p>'Initial access level for new users' should be set to 1 (New User) if you
1617 would like to review each new user's registration info before granting
1618 them higher access. This would be done periodically with the <tt><b>.A</b>ide
1619 <b>V</b>alidate new users</tt> command. If you do not require registration,
1620 you should set the initial access level to 4 (Network User).</p>
1622 <p>Given the above options, it then becomes clear that there are generally
1623 two ways you can set up your Citadel system, depending on its purpose:</p>
1626 <li><b>A public access BBS or message board</b> - since you do not
1627 know who might want to log in, self-service account creation needs to
1628 stay enabled. If you want to be strict about users identifying themselves,
1629 then you should also require users to register (just remember to post
1630 a privacy policy if you're going to collect personal information) -- then
1631 set the initial access level to 1 (New User), so new users cannot post messages
1632 until after you've validated them. For a more lax environment, you can
1633 remove the registration requirement and grant new accounts level 4 (Normal
1634 User) access on the first visit. </li>
1635 <li><b>A private email/groupware system for your organization</b>
1636 - in this case, disable self-service account creation; you don't want
1637 strangers welcoming themselves to your system. You'll probably also want
1638 to disable registration, because you or some other site administrator
1639 will be entering users' contact info when you create their accounts.
1640 Since this is also how you assign their Internet e-mail addresses, it's
1641 probably a good idea to do it yourself instead of expecting them to do it.
1646 <p>'Access level required to create rooms' is up to you. You might wish to
1647 restrict the creation of new rooms only to Aides, or you might wish to allow
1648 anyone to create a room. The latter is one of the Citadel culture's most
1649 long-standing traditions; the former may be appropriate if users are abusing
1652 <p>You have the ability to 'Automatically give room aide privs to a user who
1653 creates a private room.' If you answer Yes, then any user who creates a
1654 guess-name, passworded, or invitation-only room will automatically become
1655 the room aide, and will have access to a subset of the <tt><b>.A</b>ide</tt>
1656 command set while in that room. If you would rather grant this permission
1657 manually, answer No.</p>
1659 <p>Another tradition in the Citadel culture is to refrain from deleting
1660 problem users, but instead to 'twit' them (reduce their access level to 2
1661 [Problem User]). You can then 'Automatically move problem user messages
1662 to twit room' (answer Yes, then specify 'Name of twit room' and remember
1663 to create that room). If you employ this logic, any user with level 2 (Problem
1664 User) access will continue to have access to the same set of rooms, but all
1665 messages posted will automatically be routed to the Trashcan (or whatever
1666 you call your twit room).</p>
1668 <p>If you have Internet mail configured, you have the option of restricting
1669 its use on a user-by-user basis. If you wish to do this, answer Yes to
1670 'Restrict Internet mail to only those with that privilege.' Obviously this
1671 makes no sense for an internal e-mail system, but for a public BBS it might
1674 <p>Normally, Aides have access to every room, public or private, except for
1675 user mailboxes. They are also forbidden from <tt><b>Z</b>ap</tt>ping rooms,
1676 because the review of content is considered one of their roles. If you
1677 wish to change these policies, the next two options allow you to. You
1678 may 'Allow Aides to Zap (forget) rooms', in which case they may use the
1679 <tt><b>Z</b>ap</tt> command just like any other user. Furthermore, if
1680 you 'Allow system Aides access to user mailboxes', then they may <tt><b>.G</b>oto</tt>
1681 any private mailbox belonging to any user, using a special room name format.</p>
1683 <p>If your local security and/or privacy policy dictates that you keep a
1684 log of all pages (instant messages) that go through the system, then answer
1685 Yes to 'Log all pages'. If you answer Yes, you will be prompted for the
1686 name of a room to which all pages will be logged. If you answer No, then
1687 only the sender and recipient of each individual message will receive a copy.</p>
1689 <p>The next set of options deals with the tuning of your system. It is usually
1690 safe to leave these untouched.</p>
1692 <pre>Server connection idle timeout (in seconds) [900]: <br>Maximum concurrent sessions [20]: <br>Maximum message length [2147483647]: <br>Minimum number of worker threads [5]: <br>Maximum number of worker threads [256]: <br></pre>
1694 <p>The 'Server connection idle timeout' is for the connection between client
1695 and server software. It is <b>not</b> an idle timer for the user interface.
1696 900 seconds (15 minutes) is the default and a sane setting.</p>
1698 <p>'Maximum concurrent sessions' is the highest number of user sessions you
1699 wish to allow on your system at any given time. Citadel can scale to
1700 hundreds of concurrent users, but if you have limited hardware or (more
1701 likely) limited bandwidth, you might wish to set a maximum. You can also
1702 set it to zero for no limit.</p>
1704 <p>'Maximum message length' is just that. This could be a good way to prevent
1705 enormous multimedia files from finding their way into your message base.
1706 This maximum is enforced in all protocols and is also advertised by the
1709 <p>The minimum and maximum number of worker threads can be tuned to your
1710 liking. Citadel will attempt to keep one worker thread running per session,
1711 within these constraints. You should be aware that due to the use of the
1712 worker thread model, Citadel can handle a large number of concurrent sessions
1713 with a much smaller thread pool. If you don't know the programming theory
1714 behind multithreaded servers, you should leave these parameters alone.</p>
1716 <p>The next set of options affect how Citadel behaves on a network.</p>
1719 How often to run network jobs (in seconds) [3600]: <br>
1720 POP3 server port (-1 to disable) [110]:<br>
1721 IMAP server port (-1 to disable) [143]:<br>
1722 SMTP server port (-1 to disable) [25]: <br>
1723 Correct forged From: lines during authenticated SMTP [Yes]:<br>
1726 <p>'How often to run network jobs' refers to the sharing of content on a
1727 Citadel network. If your system is on a Citadel network, this configuration
1728 item dictates how often the Citadel server will contact other Citadel servers
1729 to send and receive messages. In reality, this will happen more frequently
1730 than you specify, because other Citadel servers will be contacting yours
1731 at regular intervals as well.</p>
1733 <p>Then you can specify TCP port numbers for the SMTP, POP3, and IMAP services.
1734 For a system being used primarily for Internet e-mail, these are essential,
1735 so you'll want to specify the standard port numbers: 25, 110, and 143.
1736 If Citadel is running alongside some other mail system, though, then you
1737 might want to choose other, unused port numbers, or enter -1 for any protocol
1738 to disable it entirely.</p>
1740 <p>The question about correcting forged From: lines affects how Citadel
1741 behaves with authenticated SMTP clients. Citadel does not ever allow
1742 third-party SMTP relaying from unauthenticated clients -- any incoming
1743 messages must be addressed to a user on the system or somewhere in a Citadel
1744 network. To use Citadel with SMTP client software such as Netscape, Outlook,
1745 Eudora, or whatever, users must log in with a username and password. In order
1746 to prevent message forgeries, Citadel discards the <TT>From:</TT> line in any
1747 message entered by an authenticated user, and replaces it with a
1748 <TT>From:</TT> line containing the user's genuine name and e-mail address.
1749 Technically, this violates RFC822, because headers are never supposed to be
1750 altered, but common sense dictates that this is a good idea. Nevertheless,
1751 if you want to suppress this behavior, answer 'No' at the prompt (the default
1752 is 'Yes') and the headers will never be altered.</p>
1754 <p>The final set of options configures system-wide defaults for the auto-purger:</p>
1756 <pre>Default user purge time (days) [120]: <br>Default room purge time (days) [30]: <br>System default message expire policy (? for list) [2]: <br>Keep how many messages online? [150]:<br></pre>
1758 <p>Any user who does not log in for the period specified in 'Default user
1759 purge time' will be deleted the next time a purge is run. This setting
1760 may be modified on a per-user basis.</p>
1762 <p>'Default room purge time' behaves the same way, and may also be modified
1763 on a per-room basis.</p>
1765 <p>'System default message expire policy' defines the way in which old messages
1766 are expired (purged) off the system. You can specify any of:</p>
1769 <li>Purge by age (specify in days) </li>
1770 <li>Purge by message count in the room (specify number of messages)
1772 <li>Do not purge at all </li>
1776 <p>Again, this setting may be overridden on a per-floor basis, and the floor
1777 setting may be overridden on a per-room basis.</p>
1779 <pre>Save this configuration? No<br></pre>
1781 <p>When you're done, enter 'Yes' to confirm the changes, or 'No' to discard
1785 <hr width="100%" size="2">
1786 <h2 align="center"><a name="Configuring_Citadel_for_Internet_e-mail"></a>Configuring
1787 Citadel for Internet e-mail</h2>
1789 <div align="justify">
1790 <h3><a name="Introduction"></a>Introduction</h3>
1791 As you know by now, Citadel is a completely self-contained, full-featured
1792 Internet e-mail system. When you run Citadel you do not need any other
1793 mail software on your host system. This eliminates the need for tedious
1794 mucking about with sendmail, qmail, postfix, Cyrus, the UW IMAP server,
1795 or any of countless other needlessly complex programs that lead some people
1796 to the false assumption that Unix systems are difficult to administer.<br>
1798 Some of the many features supported by Citadel are:<br>
1801 <li>Built-in SMTP and ESMTP service, for delivering and receiving
1802 e-mail on the Internet</li>
1803 <li>Built-in POP3 service, for remote fetching of messages</li>
1804 <li>Built-in IMAP service, for access to mail using any standard mail
1806 <li>Web mail (implemented using the "WebCit" middleware, which is
1807 installed separately)</li>
1808 <li>Support for mailing lists, in both "individual message" and "digest"
1810 <li>Multiple/virtual domain support</li>
1811 <li>Any user may have multiple Internet e-mail addresses, in multiple
1813 <li>Global address book (Users with addresses in a domain may be spread
1814 out across many servers on a Citadel network)</li>
1815 <li>Easy-to-configure integration with <a
1816 href="http://www.spamassassin.org/">SpamAssassin</a> can block
1818 it enters the mail system</li>
1819 <li>Easy-to-configuration integration with most Realtime Blackhole
1820 Lists (RBL) provide further defense against spammers</li>
1823 This section of the documentation will demonstrate how to configure
1827 <h3><a name="Basic_site_configuration"></a>Basic site configuration</h3>
1829 <p>Basic configuration of your Citadel system for Internet e-mail begins with
1830 the <tt><b>.A</b>ide <b>S</b>ystem configuration <b>I</b>nternet</tt> command:</p>
1832 <pre>Lobby> <b>.A</b>ide <b>S</b>ystem configuration <b>I</b>nternet<br><br>### Host or domain Record type<br>--- -------------------------------------------------- --------------------<br> 1<br><A>dd <D>elete <S>ave <Q>uit -><br></pre>
1834 <p>This is a "clean" setup. For a simple, standalone e-mail system you simply
1835 have to enter the <tt><b>A</b>dd</tt> command:</p>
1838 <A>dd <D>elete <S>ave <Q>uit -> <b>A</b>dd
1840 Enter host name: schmeep.splorph.com
1841 (1) localhost (Alias for this computer)
1842 (2) gateway domain (Domain for all Citadel systems)
1843 (3) smart-host (Forward all outbound mail to this host)
1844 (4) directory (Consult the Global Address Book)
1845 (5) SpamAssassin (Address of SpamAssassin server)
1846 (6) RBL (domain suffix of spam hunting RBL)
1851 <p><b>localhost:</b> Basically what you're doing here is telling Citadel
1852 what any aliases for your machine are. If your machine were <tt>schmeep.splorph.com</tt>
1853 and you also had a DNS entry set up for <tt>blah.com</tt>, you might want
1854 to enter '1' and enter <tt>blah.com</tt> as your alias, so that e-mail
1855 sent to that address won't bounce.</p>
1857 <p><i>Important tip:</i> if your system is known by one name and <i>only</i>
1858 one domain, you might not even need to do this at all. You will recall
1859 that you entered your system's fully qualified domain name earlier when you
1860 went through the <tt><b>.A</b>ide <b>S</b>ystem configuration <b>G</b>eneral</tt>
1861 command. The domain name you entered there is automatically considered
1862 by Citadel to be a 'localhost' entry in your Internet mail configuration.
1863 It does not hurt to enter it in both locations, though.</p>
1865 <p><b>gateway domain:</b> this is a simple way of mapping various Citadel
1866 hosts in an Internet domain. For example, if you enter <tt>bar.com</tt>
1867 as a gateway domain, then mail to users at <tt>foo.bar.com</tt> will be forwarded
1868 to the host called <tt>foo</tt> on a Citadel network, mail to users at <tt>kunst.bar.com</tt>
1869 will be delivered to the Citadel server called <tt>kunst</tt>, etc. This
1870 feature has limited usefulness; if you are operating a network of Citadel
1871 servers, it is more likely that you will use the 'directory' feature, explained
1874 <p><b>smart-host:</b> Normally, Citadel sends outbound Internet e-mail directly
1875 to its destination. This may not be appropriate for some sites; you may
1876 require (due to local convention, security policy, or whatever) that all
1877 outbound mail be sent to an SMTP relay or forwarder. To configure this
1878 functionality, simply enter the domain name or IP address of your relay
1879 as a 'smart-host' entry.</p>
1881 <p><b>directory:</b> a domain for which you are participating in directory
1882 services across any number of Citadel nodes. For example, if users who
1883 have addresses in the domain <tt>citadel.org</tt> are spread out across multiple
1884 Citadel servers on your network, then enter <tt>citadel.org</tt> as a 'directory'
1885 entry. <i>For this to work, all Citadel servers participating in directory
1886 service <b>must</b> carry and share the <tt>Global Address Book></tt>
1889 <p><b>spamassassin:</b> if you are running a <a
1890 href="http://www.spamassassin.org">SpamAssassin</a> service anywhere on your
1891 <b>local</b> network, enter its name or IP address as a 'spamassassin' entry.
1892 This may be (and, in fact, will usually be) <tt>127.0.0.1</tt> to specify
1893 that the service is running on the same host computer as the Citadel server.</p>
1895 <p>Please install SpamAssassin as per its own documentation. You will want
1896 to run SpamAssassin in client/server mode, where a <tt>spamd</tt> daemon
1897 is always running on your computer. Citadel does not utilize the <tt>spamc</tt>
1898 client; instead, it implements SpamAssassin's protocol on its own.</p>
1900 <p>Connecting to a SpamAssassin service across a wide area network is strongly
1901 discouraged. In order to determine whether an incoming e-mail is spam,
1902 Citadel must feed the <i>entire message</i> to the SpamAssassin service.
1903 Doing this over a wide area network would consume time and bandwidth, which
1904 would affect performance.</p>
1906 <p>Citadel invokes the SpamAssassin service when incoming messages are arriving
1907 via SMTP. Before a message is accepted, it is submitted to SpamAssassin.
1908 If SpamAssassin determines that the message is spam, the Citadel SMTP
1909 service <i>rejects the message,</i> causing a delivery failure on the sending
1910 host. This is superior to software which files away spam in a separate
1911 folder, because delivery failures will cause some spammers to assume the
1912 address is invalid and remove it from their mailing lists.</p>
1914 <p><b>RBL:</b> Realtime Blackhole Lists (RBL's) provide defense against
1915 spammers based on their source IP address. There are many such lists available
1916 on the Internet, some of which may be utilized free of charge. Since they
1917 are DNS based, the lists do not require storage on your server -- they are
1918 queried during the SMTP conversation.</p>
1920 <p>Citadel can utilize any RBL that uses the
1921 <tt>z.y.x.w.nameoflist.org</tt> syntax, where <tt>w.x.y.z</tt> is the
1922 source IP address which is attempting to deliver mail to your server. For
1923 example, <a href="http://www.spamcop.net">SpamCop</a> would use the query
1924 <tt>2.0.0.127.bl.spamcop.net</tt> to determine whether the host at
1925 <tt>127.0.0.2</tt> is a known spammer or open relay. In this case, you
1926 simply select option '6' to add an RBL entry, and provide it with the
1927 domain suffix of <tt>bl.spamcop.net</tt> (the IP address and extra dot will
1928 be automatically prepended for each query).</p>
1930 <p>Now select <tt><b>S</b>ave</tt> and you are just about ready for Internet
1933 <h3><a name="Enabling_the_Internet_mail_protocols"></a>Enabling the Internet
1936 <p>As previously mentioned, Citadel contains its own SMTP, POP3, and IMAP
1937 services. Enabling them is simple.</p>
1939 <p>Check for the existance of a current MTA (sendmail, qmail, etc.) by connecting
1940 to port 25 on your host. If you see something similar to the following
1941 you're running an MTA already and you'll need to shut it down:</p>
1943 <pre>smw @ pixel % telnet localhost 25<br>Trying 127.0.0.1...<br>Connected to localhost.<br>Escape character is '^]'.<br>220 pixel.citadel.org ESMTP Sendmail 8.9.3/8.9.3; Wed, 15 Mar 2000 19:00:53 -0500<br></pre>
1945 <p>In the above example, we see that the host already has Sendmail listening
1946 on port 25. Before Citadel can use port 25, Sendmail must be shut off.
1947 Please consult the documentation for your operating system for instructions
1948 on how to do this. (On a Red Hat Linux system, for example, you can run the
1949 <tt>ntsysv</tt> utility, un-checking <tt>sendmail</tt> to disable it at the
1950 next reboot; then, run <tt>service sendmail stop</tt> to shut off the currently
1951 running service.)</p>
1953 <p>If you get a 'connection refused' message when you telnet to port 25 there's
1954 nothing running and you should be able to continue. You might also want
1955 to turn off POP (try the above test substituting 110 for 25) and IMAP (port
1956 143) and use Citadel's POP and IMAP services.</p>
1958 <p>Citadel will look for an existing pop/smtp server on startup. If they
1959 don't exist (and you've configured them properly) then Citadel should enable
1960 them at startup. You can check your logs to be sure, or you can start the
1961 server from a shell and watch it load. It might look something like this:</p>
1962 <font size="-2"> </font>
1963 <pre><font size="-2">smw @ pixel % ./citserver<br><br>Multithreaded message server for Citadel/UX<br>Copyright (C) 1987-2000 by the Citadel/UX development team.<br>Citadel/UX is open source, covered by the GNU General Public License, and<br>you are welcome to change it and/or distribute copies of it under certain<br>conditions. There is absolutely no warranty for this software. Please<br>read the 'COPYING.txt' file for details.<br><br>Loading citadel.config<br>Opening databases<br>This is GDBM version 1.8.0, as of May 19, 1999.<br>Checking floor reference counts<br>Creating base rooms (if necessary)<br>Registered a new service (TCP port 504)<br>Registered a new service (TCP port 0)<br>Initializing loadable modules<br>Registered server command CHAT (Begin real-time chat)<br>Registered server command PEXP (Poll for express messages)<br>Registered server command GEXP (Get express messages)<br>Registered server command SEXP (Send an express message)<br>Registered server command DEXP (Disable express messages)<br>Registered a new session function (type 0)<br>Registered a new x-msg function (priority 0)<br>Loaded module: $Id$<br>Registered a new session function (type 1)<br>Registered a new message function (type 201)<br>Registered a new message function (type 202)<br>Registered server command REGI (Enter registration info)<br>Registered server command GREG (Get registration info)<br>Registered a new user function (type 100)<br>Loaded module: $Id$<br>Server-hosted upgrade level is 5.62<br>Loaded module: $Id$<br>Registered server command EXPI (Expire old system objects)<br>Registered server command FSCK (Check message ref counts)<br>Loaded module: $Id$<br><b>citserver: Can't bind: Address already in use<br>ERROR: could not bind to TCP port 25.</b><br>Registered a new service (TCP port 0)<br>Registered a new session function (type 50)<br>Loaded module: $Id$<br><b>citserver: Can't bind: Address already in use<br>ERROR: could not bind to TCP port 110.</b><br>Registered a new session function (type 0)<br>Loaded module: $Id$<br>Registered a new message function (type 202)Loaded module: $Id$<br>Registered server command RWHO (Display who is online)<br>Registered server command HCHG (Masquerade hostname)<br>Registered server command RCHG (Masquerade roomname)<br>Registered server command UCHG (Masquerade username)<br>Registered server command STEL (Enter/exit stealth mode)<br>Loaded module: $Id$<br>Changing uid to 513<br>Starting housekeeper thread<br></font></pre>
1965 <p>The lines emphasized in boldface in the above log output tell you that
1966 Citadel "can't bind" to various ports. The error 'address already in use'
1967 generally means that something else is already running on the requested
1968 port. Make SURE you've followed the above steps to remove sendmail/pop and
1969 start your Citadel server again.</p>
1971 <h3><a name="citmail"></a>Using Citadel in conjunction with another MTA</h3>
1973 <p>Occationally it is not practical to remove a non-Citadel MTA on your host
1974 system. For example, you might have multiple groups of users, some of
1975 which are using Citadel and some of which are using a legacy Unix mail
1976 spool. This type of configuration is discouraged, but a tool is provided
1979 <p>The tool is called <tt>citmail</tt> and it is, quite simply, a local MDA
1980 (Mail Delivery Agent) which you can configure into your MTA for final delivery
1981 of incoming messages to Citadel users. A full discussion of the finer
1982 points of complex Sendmail configurations is beyond the scope of
1984 however, you might want to visit <a
1985 href="http://pixel.citadel.org/citadel/docs/">Pixel BBS</a> where some useful
1986 HOWTO documents are provided.</p>
1988 <p>For outbound mail, you can either allow Citadel to perform
1990 (this won't affect your other mail system because outbound mail doesn't tie
1991 up port 25) or enter <tt>127.0.0.1</tt> as your smart-host, which will tell
1992 Citadel to forward all of its outbound mail to your other mail system.</p>
1994 <h3><a name="Hosting_an_Internet_mailing_list"></a>Hosting an Internet mailing
1997 <p>Citadel has built in mailing list service (known in the 'net vernacular
1998 as "listserv") functionality. You can turn any room into a mailing
1999 list. Users can then choose how they participate -- by logging on to
2000 your Citadel server directly, or by having the room's contents mailed to them
2001 somewhere else. Configuring this is easy.</p>
2003 <p>Citadel supports two modes of mailing list delivery: </p>
2006 <li>"List mode" -- each individual message is delivered as a single
2007 e-mail to each list mode recipient. The "From:" header will display
2008 the address of the message's original author.</li>
2009 <li>"Digest mode" -- groups of one or more messages are delivered to
2010 digest mode recipients. The number of messages in the group depends
2011 on how many new messages arrived since the last batch was delivered. The
2012 "From:" header will display the address of the room itself, which allows
2013 replies to be posted back to the room.</li>
2016 A room may have any combination of list mode and digest mode recipients.
2018 <p>As alluded to above, every room on your Citadel system has an Internet
2019 e-mail address of its own. Messages sent to that address will be posted
2020 in the room (and sent back out to mailing list recipients, as well as to
2021 any other Citadels you share the room with). The address format is
2022 <tt>room_</tt> plus the name of the room, with any spaces replaced by underscores,
2023 followed by <tt>@</tt> and your hostname. For example, if your system is
2024 known as <tt>phlargmalb.orc.org</tt> on the Internet, and you have a room
2025 called <tt>Bubblegum Collectors</tt>, you can post to that room from anywhere
2026 on the Internet simply by sending an e-mail to <tt>room_bubblegum_collectors@phlargmalb.orc.org</tt>.
2027 When the message arrives, it's automatically posted in that room.</p>
2029 <p>To manually edit the list of "list mode" recipients, simply enter the <tt><b>.A</b>ide
2030 mailing <b>L</b>ist management</tt> command. Your text editor will open
2031 up and you will be able to create or edit a list of recipients, one per line.
2032 Lines beginning with a hash (<tt>#</tt>) are comments.</p>
2034 <p>To manually edit the list of "digest mode" recipients, enter the <tt><b>.A</b>ide
2035 mailing list <b>D</b>igest recipients</tt> command. As with the previous
2036 command, the text editor will open up and you can edit the list of digest
2037 mode recipients, one per line.</p>
2039 <p>Citadel also has a facility which allows users to subscribe or unsubscribe
2040 to mailing lists using a web browser. In order to do this, WebCit must also
2041 be running on your server in addition to Citadel. WebCit is obtained and
2042 installed separately from the rest of the Citadel system.</p>
2044 <p>In order to prevent "just anyone" from subscribing to any room on your
2045 system, there is a setting in the <tt><b>.A</b>ide <b>E</b>dit room</tt>
2048 <pre>CitaNews} . Aide Edit this room<br>Room name [CitaNews]:<br><br><i>(lots of other stuff omitted for brevity...)</i><br><br>Self-service list subscribe/unsubscribe [No]: Yes<br></pre>
2050 <p>When you answer "Yes" to self-service list subscribe/unsubscribe, you are
2051 enabling that feature. Now, all you have to do is tell the world about the
2052 web page they need to visit. It looks like this:</p>
2054 <center><tt>http://foobar.baz.org:2000/listsub</tt></center>
2056 <p>In this example, the server is called <tt>foobar.baz.org</tt> and WebCit
2057 is running on port 2000. Edit appropriately.</p>
2059 <p>Citadel offers a subscribe/unsubscribe facility that is more intuitive
2060 than other listservs. With most systems, sending commands to the listserv
2061 requires that you e-mail it commands in a special format. It's easy to get
2062 it wrong. Citadel simply uses your web browser. You select the list you
2063 want to subscribe or unsubscribe (hint: it's the list of rooms you've enabled
2064 self-service for), select whether you want list mode or digest mode, and
2065 enter your e-mail address. For security purposes, a confirmation message
2066 is sent to the address you enter. But you don't have to reply to the message
2067 in a weird format, either: the confirmation contains another URL which you
2068 simply click on (or paste into your browser if you can't click on URL's
2069 in your e-mail software) and the confirmation is automatically completed.</p>
2071 <hr width="100%" size="2">
2073 <h2><a name="Building_or_joining_a_Citadel_network"></a>Building or joining
2074 a Citadel network</h2>
2077 <h3><a name="Overview__"></a>Overview</h3>
2079 <p>If you are running Citadel as a BBS or other forum type of application,
2080 one way to 'keep the conversation going' is to share rooms with other Citadel
2081 systems. In a shared room, a message posted to the room is automatically
2082 propagated to every system on the network. It's kind of like
2084 but without the spam.</p>
2086 <p>If you are using Citadel as the e-mail and groupware platform for a large
2087 organization, you can use its networking features to build a large network
2088 of Citadel servers which share content (think of rooms as public folders),
2089 redistribute e-mail throughout the organization, and integrate the global
2090 address book. It might make sense, for example, in a large corporation
2091 to give each department or location its own Citadel server. Thanks
2092 to Citadel's global address book features, you could still have all of the
2093 users share a single e-mail domain.</p>
2095 <p>Obviously, the first thing you have to do is find another Citadel to share
2096 rooms with, and make arrangements with them. The following Citadels are
2097 a good place to start:</p>
2100 <li>UNCENSORED! - <a href="http://uncensored.citadel.org">uncensored.citadel.org</a>
2102 <li>The Dog Pound II - <a href="http://dogpound2.citadel.org">dogpound2.citadel.org</a>
2104 <li>PixelBBS - <a href="http://pixel.citadel.org">pixel.citadel.org</a>
2109 <p>You don't have to be a part of the citadel.org domain to participate in
2110 the public Citadel network, but the DNS service is provided free of charge
2111 by the Citadel community if you wish to do this.</p>
2113 <h3><a name="Conventions_and_etiquette_when"></a>Conventions and etiquette
2114 when connecting to the public Citadel network</h3>
2116 <p>Before we get into the technical nitty gritty, there are two points of
2117 etiquette to keep in mind. The first thing to keep in mind is that the
2118 operator of any particular Citadel may not be willing to share some of his/her
2119 rooms. Some sites are proud to offer exclusive content in certain areas.
2120 Chances are, if a room is already being shared on the network, it's available
2121 for anyone to share; if not, it can't hurt to ask -- but take care not to
2122 demand it of them. Ask if you may share the room instead of telling them
2123 that you wish to share the room. When looking at a <tt><b>K</b></tt>nown
2124 rooms list, network rooms are the ones ending in parentheses instead of angle
2125 brackets. For example, <tt>Gateway)</tt> would be a network room, <tt>Lobby></tt>
2128 <p>The other point of etiquette to remember is that you should be making
2129 the arrangements in advance, and then set it up. It is extremely rude to
2130 simply begin networking with another Citadel, or unilaterally start sharing
2131 a new room, without first obtaining permission from its operator. Always
2132 ask first. Most Citadel operators are more than happy to network with you.
2133 Also, if later on you decide to take your system down, please take the time
2134 to notify the operators of any other Citadels you network with, so they can
2135 unconfigure their end.</p>
2137 <h3><a name="Getting_ready_to_join_the_network"></a>Getting ready to join
2140 <p>Ok, first things first. On a Citadel room sharing network, the first
2141 thing you need to know is your own system's node name. Presumably you set
2142 this up during installation, but if you want to change it you can do so using
2143 the <tt><b>.A</b>ide <b>S</b>ysconfig <b>G</b>eneral</tt> command:</p>
2145 <pre>Lobby> . Aide System configuration General<br>Node name [uncnsrd]:<br>Fully qualified domain name [uncensored.citadel.org]:<br>Human readable node name [Uncensored]:<br></pre>
2147 <p>The "node name" is important, it's how the network identifies messages
2148 coming from your system. The "human readable node name" is simply a label;
2149 it shows up in messages coming from your system. "Fully qualified domain
2150 name" is your DNS name; it's used for routing messages on the Internet.
2151 In the above example, the node name is "uncnsrd".</p>
2153 <h3><a name="Defining_neighbor_nodes"></a>Defining neighbor nodes</h3>
2155 <p>The next thing you need to do is configure your neighbor node(s). You
2156 need to do this for each node you network with. Let's say you wanted to
2157 talk to a Citadel system called "frobozz". Use the <tt><b>.A</b>ide <b>S</b>ysconfig
2158 <b>N</b>etwork</tt> command:</p>
2160 <pre>Lobby> . Aide System configuration Network<br>### Node Secret Host or IP Port#<br>--- ---------------- ---------------- -------------------------------- -----<br><A>dd <D>elete <S>ave <Q>uit -> Add<br><br>Enter node name : frobozz<br>Enter shared secret: frotz<br>Enter host or IP : frobozz.magick.org<br>Enter port number : [504]: 504<br><br>### Node Secret Host or IP Port#<br>--- ---------------- ---------------- -------------------------------- -----<br> 1 frobozz frotz frobozz.magick.org 504<br><A>dd <D>elete <S>ave <Q>uit -> Save<br><br>Lobby><br></pre>
2162 <p>As you can see in the above example, you have to enter the Citadel node
2163 name, the DNS name or IP address of the server, and the port number the
2164 Citadel service is running on. The "shared secret" is a password to allow
2165 the two Citadel nodes to connect to each other to exchange network data.
2166 The password must be <i>identical</i> on both ends of the connection --
2167 when the operator of the other Citadel node sets up the connection with
2168 your system, he/she must use the same password.</p>
2170 <h3><a name="Sharing_rooms"></a>Sharing rooms</h3>
2172 <p>Now you're ready to share rooms. You have to do this for each room you
2173 want to share, and you have to do it from BOTH ENDS -- again, when you
2174 share a room with another Citadel, they must share it with you as well.
2175 Let's say you have a room called "Quiche Recipes>" and you want to share
2176 it with the node you set up above. First, edit the room and flag it as a
2179 <pre>Quiche Recipes> . Aide Edit this room<br>Room name [Quiche Recipes]:<br>Private room [No]: No<br>Preferred users only [No]: No<br>Read-only room [No]: No<br>Directory room [No]: No<br>Permanent room [No]: No<br>Network shared room [No]: Yes<br>Automatically make all messages anonymous [No]: No<br>Ask users whether to make messages anonymous [No]: No<br>Listing order [64]:<br>Room aide (or 'none') [none]:<br>Message expire policy (? for list) [0]:<br>Save changes (y/n)? Yes<br>Ok<br><br>Quiche Recipes)<br></pre>
2181 <p>Notice how the prompt changed? It was > before, but it's ) now. That
2182 means it's a network room. Now you can tell Citadel that you want to share
2183 the room with frobozz. Enter this command:</p>
2185 <pre>Quiche Recipes) . Aide Network room sharing<br></pre>
2187 <p>Your text editor will pop up (you <i>did</i> configure Citadel to use
2188 your favorite text editor, right?) with a screen that looks like this:</p>
2190 <pre># Configuration for room: Quiche Recipes<br># Nodes with which we share this room<br># Specify one per line.<br></pre>
2192 <p>All you have to do is enter the name of the other Citadel node (i.e. "frobozz"
2193 in our example) on a line by itself. As usual, lines starting with a "#"
2194 are comments. Just go to the end of the file, type "frobozz" (without
2195 the quotes), save the file... and you're done!</p>
2197 <p>At this point, you just sit back and enjoy. Your Citadel and the other
2198 one will begin polling each other at regular intervals (once per hour by
2199 default) and sharing messages.</p>
2201 <h3><a name="Sending_mail"></a>Sending mail</h3>
2203 <p>You can send mail to any user on any node of your Citadel network. It
2204 may take a little while for your system to learn the entire node list, though,
2205 as this is done by watching incoming messages on the network and learning
2206 which nodes are out there.</p>
2208 <p>To send a private message, just enter <tt>user @ host</tt> as the recipient:</p>
2210 <pre>Mail> Enter message <br>Enter recipient: Some other user @ frobozz<br> Feb 11 2003 11:36pm from I. M. Me to Some other user @ frobozz<br>type message here...<br><br>Entry command (? for options) -><br></pre>
2212 <h3><a name="Changing_the_polling_interval"></a>Changing the polling interval</h3>
2214 <p>As previously mentioned, Citadel will poll other Citadel nodes for messages
2215 once per hour. If this is not an acceptable interval, you can change it
2216 using the <tt><b>.A</b>ide <b>S</b>ystem configuration <b>G</b>eneral</tt>
2217 command. Enter this command and look for the option:</p>
2219 <pre>How often to run network jobs (in seconds) [3600]:<br></pre>
2221 <p>Change it to whatever you like. For example, 15 minutes is 900 seconds.
2222 So if you changed the default value to 900, network polling would occur
2223 every 15 minutes.</p>
2226 <h2 align="center"><a name="Database_maintenance"></a>Database maintenance</h2>
2228 <h3><a name="Introduction_"></a>Introduction</h3>
2229 The data store used by Citadel is reliable and self-maintaining. It
2230 requires very little maintenance. This is primarily due to its use
2231 of the <a href="http://www.sleepycat.com">Berkeley DB</a> record manager.
2232 It is robust, high-performance, and transactional.<br>
2234 A few small data files are kept in your main Citadel directory, but the
2235 databases are in the <tt>data/</tt> subdirectory. The files with names
2236 that begin with "cdb" are the databases themselves; the files with names that
2237 begin with "log" are the journals. Journal files will come and go as
2238 you use your system; when the database engine has determined that a particular
2239 log file is no longer needed, the file will automatically be deleted. Nevertheless,
2240 you should always ensure that there is ample disk space for the files to
2243 There is no need to shut down Citadel during backups. The data store
2244 may be backed up "hot." The makers of Berkeley DB suggest that you should
2245 back up the data files <i>first</i> and the log files <i>second</i>. This
2246 is the only method that will guarantee that a database which is being changed
2247 while you back it up will still be usable when you restore it from the tape
2251 <h3><a name="Database_repair"></a>Database repair</h3>
2252 Although Citadel's data store is quite reliable, database corruption can
2253 occur in rare instances. External factors such as an operating system
2254 crash or an unexpected loss of power might leave the database in an unknown
2255 state. A utility is provided which may be able to repair your database
2256 if this occurs. If you find that your Citadel server is not running,
2257 and reading the logs shows that it is crashing because of an inability to
2258 validate a database, follow these steps:<br>
2261 <li>Edit <tt>/etc/inittab</tt> and switch the Citadel service from "respawn"
2262 to "off." Type <tt>init q</tt> to make this setting permanent.</li>
2263 <li><b>Make a backup of your data.</b> Either write it out to tape
2264 or copy it to another directory, or a tarball.<br>
2266 <li><tt>cd</tt> to your Citadel directory and type <tt>./database_cleanup.sh</tt></li>
2267 <li>Edit <tt>/etc/inittab</tt> and switch the Citadel service from "off"
2268 to "respawn". Type <tt>init q</tt> to activate your changes.</li>
2271 If this procedure does not work, you must restore from your most recent
2275 <h3><a name="ImportingExporting_your_Citadel"></a>Importing/Exporting your
2276 Citadel database<br>
2279 <p>Citadel/UX now contains an importer/exporter module, affectionaly known
2280 as the "Art Vandelay" module (a not-so-obscure Seinfeld reference). It
2281 allows you to export the entire contents of your Citadel databases to a
2282 flat file, which may then be imported on another system. (This procedure
2283 is also known as "dump and load" to some database gurus.)</p>
2285 <p>Why would you want to do this? Here are some scenarios: </p>
2288 <li>You are moving a Citadel installation to another computer, which uses
2289 a different CPU. Since Citadel stores data in an architecture-dependent
2290 format, the data files wouldn't work on the new computer as-is. </li>
2291 <li>Your computer crashed, lost power, etc. and you suspect that your
2292 databases have become corrupted. </li>
2293 <li>You want to switch to a different back-end data store. (For example,
2294 from GDBM to Berkeley DB) </li>
2298 <p>So ... how do we work this magic? Follow these steps <i>exactly</i> as
2299 documented and you should be able to do it all with very little trouble.</p>
2302 <li>This should be obvious, but it's still worth mentioning: MAKE SURE
2303 YOU TAKE A BACKUP OF EVERYTHING BEFORE YOU START THIS!! You're performing
2304 a major operation here. Don't risk it. </li>
2305 <li>First, get all the users logged off from your system. Disconnect
2306 it from the network if possible. You don't want anyone logging in while
2307 you're doing this. </li>
2308 <li>Log on as root, or some other user that has read/write access to
2309 all relevant files. </li>
2310 <li>Go to the directory that Citadel is installed in. For example, issue
2311 a command like <tt>cd /usr/local/citadel</tt> </li>
2312 <li>Export the databases with the following command:<br>
2314 <tt>./sendcommand "ARTV export" >exported.dat</tt><br>
2316 This command may run for a while. On a very large system it could take
2317 an hour or more. Please be patient! </li>
2318 <li>When the export completes, check to make sure that <tt>exported.dat</tt>
2319 exists and has some data in it. (Type "ls -l exported.dat") </li>
2320 <li>Shut down the Citadel server. If you have a line in <tt>/etc/inittab</tt>
2321 that reads like this:<br>
2323 <tt>c1:2345:respawn:/usr/local/citadel/citserver -h/usr/local/citadel</tt>
2325 ...then you should change the <tt>respawn</tt> to <tt>off</tt> and then
2326 type <tt>/sbin/init q</tt> to make the changes take effect. </li>
2327 <li>Now it's time to delete your current binary databases. Type:<br>
2329 <tt>rm -f citadel.config citadel.control data/*</tt> </li>
2330 <li>If you're moving Citadel to another computer, you should move the
2331 <i>entire</i> directory over at this time. <tt>exported.dat</tt> only
2332 contains the information that was in the binary databases. Information which
2333 was stored in portable formats doesn't need to be exported/imported, so you
2334 must bring it all over in its current form. </li>
2335 <li>Now get Citadel running on the new computer (or whatever). Run <tt>setup</tt>
2336 and turn the service back on (from <tt>/etc/inittab</tt>) but DO NOT log
2338 <li>As root, run the import command:<br>
2340 <tt>./sendcommand "ARTV import" <exported.dat</tt><br>
2342 This will import your databases. Again, it may run for a long time.
2344 <li>Restart the Citadel server. You can do this any way you like. From
2345 the command line, you can do it with a command like:<br>
2347 <tt>./sendcommand "DOWN"</tt> <br>
2349 <li>Now you're finished. Log in and test everything. You may delete
2350 exported.dat at this time, or you might want to save it somewhere as a sort
2351 of pseudo-backup. </li>
2356 <center><h2><a name="utilities"></a>Utilities</center></h2>
2358 <h3><a name="overview"></a>Overview</h3>
2360 <P>The following utilities will be discussed:
2362 <LI><b>aidepost</b> - Post standard input to the Aide> room
2363 <LI><b>whobbs</b> - Who is on the system
2364 <LI><b>stats</b> - Print the calling statistics & graph
2365 <LI><b>msgform</b> - Format a binary message to the screen (stdin or in a file)
2366 <LI><b>userlist</b> - Print the userlist
2367 <LI><b>readlog</b> - Read the caller log
2368 <LI><b>sendcommand</b> - Send a server command
2371 <p>It is up to you to decide which utilities should be made accessible only
2372 to system administrators.
2373 It is important that you set the file permissions correctly. All
2374 utilities should have access to the Citadel data files. We will attempt to
2375 address each program individually.</p>
2377 <h3><a name="aidepost"></a>aidepost</h3>
2379 <p>The nature of this program is rather simple. Standard input (stdin) is
2380 converted into a message, filed in the main message store, and posted
2381 in the Aide> room. This is useful for keeping transcripts of system
2382 activity that has to do with Citadel operations.
2383 You might even elect to send all of your system
2384 logs there, too.</p>
2386 <p><tt>aidepost</tt> also accepts the usage <tt>aidepost -rTargetRoom</tt>,
2388 is the name of a room to which you'd like the message to be sent.</p>
2390 <h3><a name="whobbs"></a>whobbs</h3>
2392 <p>This program is similar to the <tt>who</tt> command.
2393 It lists all of the users
2394 who are currently connected to your Citadel server, either locally or across a
2395 network. Unless you're running a standalone system,
2396 <tt>who</tt> and <tt>whobbs</tt> will
2397 probably not have a one-to-one correspondence. Remember that you will see
2398 sessions for SMTP, POP, and IMAP users, as well as users running a
2401 <p>One thing to keep in mind is that the <tt>whobbs</tt> utility
2403 connection to the server. If the server is maxed out,
2404 <tt>whobbs</tt> will still be
2405 able to provide a listing, because it doesn't need to log in to execute the
2406 <tt>RWHO</tt> command. Note that whobbs does not list its own session.</p>
2408 <p>The <tt>whobbs</tt> utility is smart enough
2409 to know when it is being invoked by a
2410 web server as a CGI program. In this situation, it will output its listing as
2411 a nicely formatted web page instead of plain text. This makes it easy to just
2412 put a link to the whobbs binary in your cgi-bin directory, allowing a quick and
2413 easy way for web surfers to see who is online.</p>
2415 <p>Running the <tt><b>W</b>ho is online</tt> command
2416 from the Citadel client does <b>not</b> call this
2417 utility. It has this functionality built in.</p>
2419 <h3><a name="stats"></a>stats</h3>
2421 <p>This program displays
2422 various statistics on the screen based on the calllog file, such as number
2423 of connects, number of logins, number of logouts, number of disconnects,
2424 bad password attempts, etc. All statistics are provided in three figures:
2425 times per call, times per day, and total times.</p>
2427 <p>After this screen appears, you may press return for the next screen. This
2428 is a graphic representation of system usage, broken down into 20 minute
2429 segments of the day. This will show you when your peak usage is.</p>
2431 <p>Press return again and the stats program will list your system's top
2434 <p>The final screen lists the twenty users with the highest post per call
2435 ratios. Unline the other screens, this statistic is extracted from the user
2436 file itself rather than the call log.</p>
2438 <p><tt>stats</tt> may be called with the <tt>-b</tt> option to
2439 run in batch mode. In this case,
2440 it skips all the prompts and just prints everything out in one bulk output.
2441 Or it may be called with the <tt>-p</tt> option to only print the Post-to-Call
2442 ratios and nothing else. These options may be useful for embedding the
2443 output of <tt>stats</tt> in a batch report or a web page.</p>
2445 <p>Nearly all of the statistics displayed by the <tt>stats</tt> utility
2446 are completely wrong.</p>
2448 <h3><a name="msgform"></a>msgform</h3>
2450 <p>The <tt>msgform</tt> utility reads its standard input (stdin) looking for
2451 Citadel messages stored in the internal format used on disk and over the
2452 network, and sends them in a human-readable format to standard output
2453 (stdout). There is no longer much use for this program, but it is included
2456 <h3><a name="userlist"></a>userlist</h3>
2458 <p>This is a program to print the userlist. There are two flags that may be
2459 set when running this program. When called without any arguments,
2460 <tt>userlist</tt> will display all users (except those who have chosen to
2461 be unlisted), their user numbers, times called, messages posted, screen
2462 width, and date of their most recent call.</p>
2464 <p><tt>userlist</tt> is simply the same user listing code that is in the
2465 client, made into a standalone utility for convenience.</p>
2467 <h3><a name="readlog"></a>readlog</h3>
2469 <p>Called without any arguments, <tt>readlog</tt> dumps the contents of the
2470 call log file. This file records all logins to the Citadel server, as
2471 well as some other statistics.</p>
2473 <h3><a name="sendcommand"></a>sendcommand</h3>
2475 <p><tt>sendcommand</tt> will interpret its arguments (except for
2476 <tt>-hDIRNAME</tt>) as a server command, which is sent to the server.
2477 Commands which require textual input will read it from stdin. Commands
2478 which generate textual output will be sent to stdout.</p>
2480 <p>This utility is intended to be used to enable Citadel server commands to
2481 be executed from shell scripts. Review the script called <tt>weekly</tt>
2482 which ships with the Citadel distribution for an example of how this can
2485 <p><b>NOTE:</b> be sure that this utility is not world-executable. It
2486 connects to the server in privileged mode, and therefore could present a
2487 security hole if not properly restricted.</p>
projects / citadel.git / blob