[Pkg-mailman-hackers] Pkg-mailman commit - rev 341 - trunk/debian

[Thijs Kinkhorst]

Author: thijs
Date: 2006-08-22 07:35:41 +0000 (Tue, 22 Aug 2006)
New Revision: 341

Modified:
   trunk/debian/templates
Log:
more fixes to conform with 'best practices'. had to condense
the note about shunted files to 20 lines, filed a bug about
that but need to fix it in the meantime.


Modified: trunk/debian/templates
===================================================================
--- trunk/debian/templates	2006-08-22 00:23:54 UTC (rev 340)
+++ trunk/debian/templates	2006-08-22 07:35:41 UTC (rev 341)
@@ -13,7 +13,7 @@
  For each supported language, Mailman stores default language
  specific texts in /etc/mailman/LANG/ giving them conffile like
  treatment with the help of ucf.  This means approximately 150kB for
- each supported language on the root FS.
+ each supported language on the root file system.
  .
  If you need a different set of languages at a later time, just run
  dpkg-reconfigure mailman.
@@ -30,8 +30,8 @@
 Type: boolean
 Default: false
 _Description: Gate news to mail?
- Do you want to gate news to mail, that is, send all the messages which
- appear in a newsgroup to a mailing list?
+ Mailman allows to gate news to mail, that is, send all the messages
+ which appear in a Usenet newsgroup to a mailing list.
  .
  Most people won't need this.
 
@@ -63,13 +63,8 @@
 Type: note
 _Description: Old queue files present
  The directory /var/lib/mailman/qfiles contains files. It needs to be
- empty for the upgrade to work properly. If these files contain
- unprocessed messages that are otherwise fine, then you can try to
- handle them by:
-  - Stopping new messages from coming in the queue (at the MTA level:
-    queue them in the MTA's queue or refuse them with a 4xx code). If
-    your site has a relatively low mailman traffic, you can skip this
-    step.
+ empty for the upgrade to work properly. You can try to handle them by:
+  - Stopping new messages from coming in (at the MTA level).
   - Start a mailman queue runner: /etc/init.d/mailman start
   - Let it run until all messages are handled.
     If they don't all get handled in a timely manner, look at the logs
@@ -78,15 +73,12 @@
   - Retry the upgrade.
   - Let messages come in again.
  You can also decide to simply remove the files, which will make
- Mailman forget about (and lose) the corresponding emails; expect
- angry users.
+ Mailman forget about (and lose) the corresponding emails.
  .
  If these files correspond to shunted messages, you have to either
- delete them or unshunt them (with
- /var/lib/mailman/bin/unshunt). Shunted messages are messages on which
- Mailman has already abandoned any further processing because of an
- error condition, but that are kept for admin review, as they usually
- originate from Mailman bugs or other abnormal situations that need
- human inspection. You can use /var/lib/mailman/bin/show_qfiles to
+ delete them or unshunt them (with /var/lib/mailman/bin/unshunt).
+ Shunted messages are messages on which Mailman has already abandoned
+ any further processing because of an error condition, but that are
+ kept for admin review. You can use /var/lib/mailman/bin/show_qfiles to
  examine the contents of the queues.