Revision: 80
http://svn.sv.gnu.org/viewvc/?view=rev&root=administration&revision=80
Author: karl
Date: 2014-03-11 18:22:51 +0000 (Tue, 11 Mar 2014)
Log Message:
-----------
merge InternalMailSystem
Modified Paths:
--------------
trunk/sviki/FrontPage.mdwn
trunk/sviki/MailSystem.mdwn
Removed Paths:
-------------
trunk/sviki/InternalMailSystem.mdwn
Modified: trunk/sviki/FrontPage.mdwn
===================================================================
--- trunk/sviki/FrontPage.mdwn 2014-03-11 18:08:07 UTC (rev 79)
+++ trunk/sviki/FrontPage.mdwn 2014-03-11 18:22:51 UTC (rev 80)
@@ -151,10 +151,7 @@
- [[UsingHg]]
- [[HomePage]]
- - [[InternalMailSystem]]
- [[JustSFTP]]
- - [[SCMs]]
-
- [[MailSystem]]
- [[ManuallyInstalledPackages]]
- [[RemountableHome]]
@@ -162,7 +159,6 @@
- [[ShellAccess]]
- [[Stats]]
- [[SqlQueries]]
- - [[XCache]]
- Subversion
- [[SvN]]
Deleted: trunk/sviki/InternalMailSystem.mdwn
===================================================================
--- trunk/sviki/InternalMailSystem.mdwn 2014-03-11 18:08:07 UTC (rev 79)
+++ trunk/sviki/InternalMailSystem.mdwn 2014-03-11 18:22:51 UTC (rev 80)
@@ -1,19 +0,0 @@
-How mails are sent from within Savannah
-
-The `internal` vserver (10.1.0.101) is the reference mail server.
-
-In particular, there is a Savane cron job there to create alias tables:
-`/etc/aliases` and `/etc/email-adresses`. This is used to map Unix user
-accounts to an outgoing e-mail, based on the 'email' field in the user's
-Savane account. alias tables are only updated in 'internal'.
-
-All other systems delegate sending mail to `internal`.
-
-- accounts, builder, frontend, sftp, vcs-noshell \_and\_ the
- host/dom0: an exim4 system is configured (see
- infra/exim\_forwarder.txt):
-
-> - smarthost = 10.1.0.101
-> - `QUEUERUNNER='queueonly'`
-
-- [[ZWiki]]: `/MailHost` object, SMTP Host = 10.1.0.101
Modified: trunk/sviki/MailSystem.mdwn
===================================================================
--- trunk/sviki/MailSystem.mdwn 2014-03-11 18:08:07 UTC (rev 79)
+++ trunk/sviki/MailSystem.mdwn 2014-03-11 18:22:51 UTC (rev 80)
@@ -1,18 +1,17 @@
-The principal email server is lists.gnu.org, managed by FSF sysadmin.
-Savannah does not have root access.
+The principal GNU (and FSF?) email server is lists.gnu.org, managed by
+FSF sysadmin. Savannah people and programs do not have root access.
-Note: for an overview of how mail is sent from Savannah, please check
-[[InternalMailSystem]].
+For outgoing mail from Savannah, the `internal` host is used; see below.
Mailman
-------
-There are no static Mailman aliases; instead, it looks at
-`/var/lib/mailman/lists/listname/domains/` and checks for files that
-represent the domain of the list, such as `gnu.org`, `nongnu.org`, and
-the like.
+On lists.gnu.org, the usual per-list static Mailman aliases do not
+exist; instead, it looks at `/var/lib/mailman/lists/listname/domains/`
+and checks for files that represent the domain of the list, such as
+`gnu.org`, `nongnu.org`, and the like.
-### Then, I don't really know:
+Then, I don't really know:
- there is some Exim code to take those files into account
- currently (?), there is a replication script that copies all the
@@ -24,32 +23,36 @@
--------
Archives are updated every 30 minutes (?) as of May 2011.
+They are located at 2 places:
-### They are located at 2 places:
-
- private archives are managed by Mailman:
`/var/lib/mailman/archives/private/list_name.mbox/list_name.mbox`
(use mailman's `arch` command to manage them; look at the --wipe command)
-- public archives are managed by mharc: `\~mharc/mbox` and
- `\~mharc/html` (check [[ImportMailingListArchive]])
+- public archives are managed by mharc: `~mharc/mbox` and
+ `~mharc/html` (check [[ImportMailingListArchive]]).
Mailing list creation
---------------------
-I (Sylvain) basically installed sv\_mailman on internal.sv.gnu.org,
+I (Sylvain) basically installed sv_mailman on internal.sv.gnu.org,
modified it to support mailman virtual hosts (and use the proper admin
mail instead of usern...@sv.gnu.org). Then I wrote a fake
`/usr/sbin/newlist` that connects to l...@lists.gnu.org via SSH and call
-an helper script there (`savannah\_wrapper.pl`). This happens via a
-Savannah public key in l...@lists.gnu.org's `authorized\_keys` with a
+an helper script there (`savannah_wrapper.pl`). This happens via a
+Savannah public key in l...@lists.gnu.org's `authorized_keys` with a
`command=` restriction.
There is also an empty `/usr/sbin/config_list` on internal that does
nothing; we don't want what Savane currently does there.
-The cron jobs related to sv\_mailman run on internal, file
-/etc/cron.d/sv. The script being run is named sv\_mailman.
+The cron job runs on internal every five minutes, file
+`/etc/cron.d/sv`. The script being run is named sv_mailman.
+On lists.gnu.org, there is a script `mycreate_list.pl` which can be used
+to create lists by hand. It duplicates what `savannah_wrapper.pl` does
+for Savannah actions. (The scripts must be kept in sync by hand. They
+should be merged so there is only one.)
+
Valid sender
------------
@@ -65,6 +68,25 @@
Antispam
--------
-Mail can be forwarded to listhel...@gnu.org which, using the Mailman
-mail interface, can pipeline your list with a conservatively-configured
-spamassassin, cf. [[ListHelperAntiSpam]]
+If listhel...@gnu.org is listed as a moderator for a Mailman list, it
+wil use a conservatively-configured spamassassin to automatically
+(though asynchronously) remove spam. Details at [[ListHelperAntiSpam]].
+
+How mails are sent from within Savannah
+---------------------------------------
+
+The `internal` vserver handles email stuff for Savannah.
+All other systems delegate sending mail to `internal`.
+
+A Savane cron job creates alias tables: `/etc/aliases` and
+`/etc/email-adresses`. This is used to map Unix user accounts to an
+outgoing email, based on the `email' field in the user's Savane
+account. Alias tables are only updated on `internal'.
+
+- (clearly stale info as we don't own the dom0 any more, but leaving
+ for what it may be worth) frontend, sftp, vcs-noshell \_and\_ the
+ host/dom0: an exim4 system is configured (see
+ infra/exim\_forwarder.txt):
+
+> - smarthost = 10.1.0.101
+> - `QUEUERUNNER='queueonly'`
