From 41b52b44f0e19e2bcfe36dd6f1101fa03198969d Mon Sep 17 00:00:00 2001 From: Art Cancro Date: Tue, 9 Sep 2003 02:42:31 +0000 Subject: [PATCH] * Documentation update for LMTP --- citadel/ChangeLog | 4 +++- citadel/docs/citadel.html | 32 +++++++++++++++++++++++++++----- 2 files changed, 30 insertions(+), 6 deletions(-) diff --git a/citadel/ChangeLog b/citadel/ChangeLog index 9e5c9dd4c..ccd61176d 100644 --- a/citadel/ChangeLog +++ b/citadel/ChangeLog @@ -1,4 +1,7 @@ $Log$ + Revision 610.14 2003/09/09 02:42:28 ajc + * Documentation update for LMTP + Revision 610.13 2003/09/09 01:47:02 ajc * Suppress domain forgery check when using LMTP @@ -5015,4 +5018,3 @@ Sat Jul 11 00:20:48 EDT 1998 Nathan Bryant Fri Jul 10 1998 Art Cancro * Initial CVS import - diff --git a/citadel/docs/citadel.html b/citadel/docs/citadel.html index 899042ff9..99da5de62 100644 --- a/citadel/docs/citadel.html +++ b/citadel/docs/citadel.html @@ -374,7 +374,8 @@ the other work under the scope of this License.

3. You may copy and distribute the Program (or a work based on it, under Section 2) in object code or executable form under the terms of Sections 1 and 2 above provided that -you also do one of the following:

+you also do one of the following: +

  • a) Accompany it with the complete corresponding @@ -696,7 +697,8 @@ If you wish to place it in a different directory, you can instead do:

    If you've got Berkeley DB installed in a non-standard location, you can help the configure script find it by doing something like this:

    ./configure --with-db=/usr/local/BerkeleyDB-4.1
    -

    Keep in mind that if you're using Berkeley DB from a non-standard location, +

    Keep in mind that if you're using Berkeley DB from a non-standard +location, you'll have to make sure that location is available at runtime.

    File permissions are always a bother to work with. You don't want Citadel to crash because someone couldn't access a file, but you also @@ -1796,7 +1798,7 @@ sendmail/pop and start your Citadel server again.

    host system. For example, you might have multiple groups of users, some of which are using Citadel and some of which are using a legacy Unix mail -spool. This type of configuration is discouraged, but a tool is +spool. This type of configuration is discouraged, but two tools are provided to allow it.

    The tool is called citmail and it is, quite simply, a @@ -1805,8 +1807,28 @@ for final delivery of incoming messages to Citadel users. A full discussion of the finer points of complex Sendmail configurations is beyond the scope of this document; however, you might want to visit Pixel BBS where some -useful HOWTO documents are provided.

    -

    For outbound mail, you can either allow Citadel to perform +useful HOWTO documents are provided.
    +

    +

    The other tool is an RFC2033 +compliant LMTP service running on a local socket.  If you're +running a mailer that speaks LMTP (such as Postfix), you can simply point your +mailer at the socket called citadel.socket +in your Citadel directory.  For example, in Postfix you might put +the following line into main.cf +in order to tell it to use Citadel to deliver mail to local recipients:
    +

    +
    local_transport = lmtp:unix:/usr/local/citadel/lmtp.socket
    +

    Postfix also has something called a "fallback transport" which can +be used to implement Citadel as a "secondary" mail system on your +server, while keeping the existing Unix mailboxes intact.  +However, it is beyond the scope of this document to detail the finer +points of the configuration of Postfix or any other mailer, so refer to +the documentation to those programs and keep in mind that Citadel has +LMTP support.
    +

    +

    For outbound mail, you +can either allow Citadel to perform deliveries directly (this won't affect your other mail system because outbound mail doesn't tie -- 2.39.2