editor=/usr/bin/vi
The above example would make Citadel call the vi editor when using
-the .Enter Editor command. You can also make
+the .Enter Editor command, or when a user
+selects the "Always compose messages with the full-screen
+editor" option. You can also make
it the default editor for the Enter command by editing
the citadel.rc file. But be warned: external editors
on public systems can
@@ -1739,7 +1736,8 @@ document.
The final set of options configures system-wide defaults for the auto-purger:
-Default user purge time (days) [120]:+
Default room purge time (days) [30]:
System default message expire policy (? for list) [0]:
Keep how many messages online? [150]:
Mailbox default message expire policy (? for list) [0]:
How often to run network jobs (in seconds) [1800]:
Enable full text search index (warning: resource intensive) [Yes]: Yes
Hour to run purges (0-23) [4]:
Default user purge time (days) [120]:
Default room purge time (days) [30]:
System default message expire policy (? for list) [0]:
Keep how many messages online? [150]:
Mailbox default message expire policy (? for list) [0]:
How often to run network jobs (in seconds) [1800]:
Enable full text search index (warning: resource intensive) [Yes]: Yes
Hour to run purges (0-23) [4]:
+Perform journaling of email messages [No]:
Perform journaling of non-email messages [No]:
Email destination of journalized messages [example@example.com]:
Any user who does not log in for the period specified in 'Default user purge time' will be deleted the next time a purge is run. This setting may be modified on a per-user basis.
@@ -1787,8 +1785,17 @@ incrementally and will not have any noticeable impact on the interactive response time of your system. The full text index is currently only searchable when using IMAP clients; other search facilities will be -made available in the near future.The "Perform journaling..." options allow you to configure +your Citadel server to send an extra copy of every message, along with +recipient information if applicable, to the email address of your choice. +The journaling destination address may be an account on the local Citadel +server, an account on another Citadel server on your network, or an Internet +email address. These options, used in conjunction with an archiving service, +allow you to build an archive of all messages which flow through your Citadel +system. This is typically used for regulatory compliance in industries which +require such things. Please refer to the journaling +guide for more details on this subject.
Save this configuration? No
When you're done, enter 'Yes' to confirm the changes, or 'No' to @@ -1874,9 +1881,13 @@ sites; you may require (due to local convention, security policy, or whatever) that all outbound mail be sent to an SMTP relay or forwarder. To configure this functionality, simply enter the domain name or IP address of your relay -as a 'smart-host' entry. If your relay server is running on a port other +as a 'smart-host' entry.
+If your relay server is running on a port other than the standard SMTP port 25, you can also specify the port number using "host:port" syntax; i.e. relay99.myisp.com:2525
+Furthermore, if your relay server requires authentication, you can +specify it using username:password@host or username:password@host:port +syntax; i.e. jsmith:pass123@relay99.myisp.com:25
directory: a domain for which you are participating in directory services across any number of Citadel nodes. For example, if users who have addresses in the domain citadel.org are spread