savannah-cvs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Savannah-cvs] administration/docs/hacking_savannah hacking_sa...


From: Sylvain Beucler
Subject: [Savannah-cvs] administration/docs/hacking_savannah hacking_sa...
Date: Sat, 26 Mar 2005 05:22:14 -0500

CVSROOT:        /cvsroot/administration
Module name:    administration
Branch:         
Changes by:     Sylvain Beucler <address@hidden>        05/03/26 10:22:14

Modified files:
        docs/hacking_savannah: hacking_savannah.texi 

Log message:
        First part of the Mailman local installation

CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/administration/administration/docs/hacking_savannah/hacking_savannah.texi.diff?tr1=1.100&tr2=1.101&r1=text&r2=text

Patches:
Index: administration/docs/hacking_savannah/hacking_savannah.texi
diff -u administration/docs/hacking_savannah/hacking_savannah.texi:1.100 
administration/docs/hacking_savannah/hacking_savannah.texi:1.101
--- administration/docs/hacking_savannah/hacking_savannah.texi:1.100    Wed Mar 
16 23:45:32 2005
+++ administration/docs/hacking_savannah/hacking_savannah.texi  Sat Mar 26 
10:22:14 2005
@@ -1,5 +1,5 @@
 \input texinfo   @c -*-texinfo-*-
address@hidden $Id: hacking_savannah.texi,v 1.100 2005/03/16 23:45:32 Beuc Exp $
address@hidden $Id: hacking_savannah.texi,v 1.101 2005/03/26 10:22:14 Beuc Exp $
 @comment %**start of header
 @setfilename hacking_savannah.info
 @include version.texi
@@ -577,7 +577,7 @@
 [TODO: explain how to reproduce this configuration file instead. Well,
 at least explain it]
 
-Listens only to the appropriate {IP,port}:
+Listens only to the appropriate @{IP,address@hidden:
 @example
 Listen savannah.gnu:80
 Listen savannah.gnu:443
@@ -1648,6 +1648,7 @@
 * Resetting a password::        
 * Archives policies::           
 * Spam::                        
+* Mailman installation::        
 @end menu
 
 @node Access to lists.gnu.org, Manually creating a new list, Mailing lists 
administration, Mailing lists administration
@@ -1903,7 +1904,7 @@
 * Spam::                        
 @end menu
 
address@hidden Spam,  , Archives policies, Mailing lists administration
address@hidden Spam, Mailman installation, Archives policies, Mailing lists 
administration
 @section Spam
 
 Here is a way to way to filter mail sent through lists.gnu.org that I
@@ -1930,6 +1931,215 @@
      
 One can use it in commit notification lists.
 
address@hidden Mailman installation,  , Spam, Mailing lists administration
address@hidden Mailman installation
+
+For our test install, let's first configure a simple and working mail
+system.
+
address@hidden
address@hidden
+You already have an exim configuration. Continuing with eximconfig
+will overwrite it. It will not keep any local modifications you have made.
+If that is not your intention, you should break out now. If you do continue,
+then your existing file will be renamed with .O on the end.
+[---Press return---]
+
+==============================================================================
+You must choose one of the options below:
+
+ (1) Internet site; mail is sent and received directly using SMTP. If your
+     needs don't fit neatly into any category, you probably want to start
+     with this one and then edit the config file by hand.
+
+ (2) Internet site using smarthost: You receive Internet mail on this
+     machine, either directly by SMTP or by running a utility such as
+     fetchmail. Outgoing mail is sent using a smarthost. optionally with
+     addresses rewritten. This is probably what you want for a dialup
+     system.
+
+ (3) Satellite system: All mail is sent to another machine, called a "smart
+     host" for delivery. root and postmaster mail is delivered according
+     to /etc/aliases. No mail is received locally.
+
+ (4) Local delivery only: You are not on a network.  Mail for local users
+     is delivered.
+
+ (5) No configuration: No configuration will be done now; your mail system
+     will be broken and should not be used. You must then do the
+     configuration yourself later or run this script, /usr/sbin/eximconfig,
+     as root. Look in /usr/share/doc/exim/example.conf.gz
+
+Select a number from 1 to 5, from the list above.
+Enter value (default=`1', `x' to restart): @kbd{1}
+
+==============================================================================
+What is the `visible' mail name of your system? This will appear on
+From: lines of outgoing messages.
+Enter value (default=`dr', `x' to restart):
+
+==============================================================================
+Does this system have any other names which may appear on incoming
+mail messages, apart from the visible name above (dr) and
+localhost?
+
+By default all domains will be treated the same; if you want different
+domain names to be treated differently, you will need to edit the config
+file afterwards: see the documentation for the "domains" director
+option.
+
+If there are any more, enter them here, separated with spaces or commas.
+If there are none, say `none'.
+Enter value (default=`none', `x' to restart):
+
+==============================================================================
+All mail from here or specified other local machines to anywhere on
+the internet will be accepted, as will mail from anywhere on the
+internet to here.
+
+Are there any domains you want to relay mail for---that is, you are
+prepared to accept mail for them from anywhere on the internet, but
+they are not local domains.
+
+If there are any, enter them here, separated with spaces or commas. You
+can use wildcards. If there are none, say `none'. If you want to relay
+mail for all domains that specify you as an MX, then say `mx'
+Enter value (default=`none', `x' to restart):
+
+==============================================================================
+Obviously, any machines that use us as a smarthost have to be excluded
+from the relaying controls, as using us to relay mail for them is the
+whole point.
+
+Are there any networks of local machines you want to relay mail for?
+
+If there are any, enter them here, separated with spaces or commas. You
+should use the standard address/length format (e.g. 194.222.242.0/24)
+If there are none, say `none'.
+
+You need to double the colons in IPv6 addreses (e.g. 5f03::1200::836f::::/48)
+Enter value (default=`none', `x' to restart):
+
+==============================================================================
+Obviously, any machines that use us as a smarthost have to be excluded
+from the relaying controls, as using us to relay mail for them is the
+whole point.
+
+Are there any networks of local machines you want to relay mail for?
+
+If there are any, enter them here, separated with spaces or commas. You
+should use the standard address/length format (e.g. 194.222.242.0/24)
+If there are none, say `none'.
+
+You need to double the colons in IPv6 addreses (e.g. 5f03::1200::836f::::/48)
+Enter value (default=`none', `x' to restart):
+Names are localhost:dr!
+
+==============================================================================
+Mail for the `postmaster' and `root' accounts is usually redirected
+to one or more user accounts, of the actual system administrators.
+By default, I'll set things up so that mail for `postmaster' and for
+various system accounts is redirected to `root', and mail for `root'
+is redirected to a real user.  This can be changed by editing /etc/aliases.
+
+Note that postmaster-mail should usually be read on the system it is
+directed to, rather than being forwarded elsewhere, so (at least one of)
+the users you choose should not redirect their mail off this machine.
+
+Which user account(s) should system administrator mail go to ?
+Enter one or more usernames separated by spaces or commas .  Enter
+`none' if you want to leave this mail in `root's mailbox - NB this
+is strongly discouraged.  Also, note that usernames should be lowercase!
+Enter value (`x' to restart): @kbd{none}
+
+==============================================================================
+You already have an /etc/aliases file. Do you want to replace this with
+a new one (the old one will be kept and renamed to aliases.O)? (y/n)
+Enter value (default=`y', `x' to restart): @kbd{y} # unless you already setup 
something there!
+The following configuration has been entered:
+
+==============================================================================
+Mail generated on this system will have `dr' used
+as the domain part (after the @@) in the From: field and similar places.
+
+
+The following domain(s) will be recognised as referring to this system:
+ localhost, dr
+
+Mail for postmaster, root, etc. will be sent to root.
+
+Local mail is delivered.
+
+Outbound remote mail is looked up in the Internet DNS, and delivered
+using that data if any is found; otherwise such messages are bounced.
+
+
+Note that you can set email addresses used for outgoing mail by editing
+/etc/email-addresses.
+
+Is this OK ?  Hit Return or type `y' to confirm it and install,
+or `n' to make changes (in which case we'll go round again, giving you
+your previous answers as defaults.     (Y/n)
+
+Keeping previous /etc/aliases as /etc/aliases.O
+
+Keeping previous /etc/mailname as /etc/mailname.O
+
+Configuration installed.
+
address@hidden example
+
+Restart xinetd:
address@hidden
+/etc/init.d/xinetd restart
address@hidden example
+
+Test with:
address@hidden
address@hidden localhost 25}
+Trying 127.0.0.1...
+Connected to dr.
+Escape character is '^]'.
+220 dr ESMTP Exim 3.35 #1 Wed, 23 Mar 2005 22:58:23 +0100
address@hidden
+221 dr closing connection
+Connection closed.
address@hidden example
+
+You need to make your machine understand its name. Edit @file{/etc/hosts}:
address@hidden
+127.0.0.1       @var{hostname}.localdomain @var{hostname} localhost
address@hidden example
+
+We'll do the same for Exim now, in @file{/etc/exim/exim.conf}:
address@hidden
+qualify_domain = dott.localdomain
+local_domains = 
localhost:@var{hostname}.localdomain:gnu.localdomain:nongnu.localdomain
address@hidden example
+
+Last, we need to tell who answers mail for @samp{gnu.localdomain} and
address@hidden Add to your
address@hidden/etc/bind/db.localdomain}:
address@hidden
+gnu             IN      MX      10 @var{hostname}
+nongnu          IN      MX      10 @var{hostname}
address@hidden example
+
+
+Time to install mailman: @code{apt-get install mailman}.
+
+The mailman Apache configuration is automatically done. Check
address@hidden://localhost/cgi-bin/mailman/listinfo}. We'll customize it a bit 
anyway:
address@hidden
+echo "include mailman.conf" >> /etc/apache/httpd.conf
+cat <<EOF > /etc/apache/mailman.conf
+ScriptAlias /mailman/ /usr/lib/mailman/cgi-bin/
+Alias /pipermail/ /var/lib/mailman/archives/public/
address@hidden example
+
+The package does not
+automatically install the Exim configuration though. We'll need to get
+information from
 
 @node Some Savannah tasks, Frequent support requests, Mailing lists 
administration, Top
 @chapter Some Savannah tasks
@@ -1953,7 +2163,7 @@
 The directory is version controled. What you have to do is make a
 local checkout, then commit as usual, and update the working copy at
 savannah (the link from nongnu/faq to gnu/faq is not version
-controled, but anyway :))
+controled, but can be generated by typing @command{make} :))
 
 And that's it.
 
@@ -2518,7 +2728,7 @@
 https://savannah.gnu.org/support/?func=detailitem&item_id=103027
 @end verbatim
 
-Only listens to the appropriate {IP,port}:
+Only listens to the appropriate @{IP,address@hidden:
 @example
 #Port 22
 ListenAddress savannah.gnu:22




reply via email to

[Prev in Thread] Current Thread [Next in Thread]