Syncronize with actual list configs.

25 files changed, 9061 insertions, 8535 deletions

diff --git a/mailman/absynthe.members b/mailman/absynthe.members
index c8f3a77..587fc7d 100644
--- a/mailman/absynthe.members
+++ b/mailman/absynthe.members
@@ -1,5 +1,3 @@
-dr@jones.dk
-go@jones.dk
 izi6@walla.co.il
 nahumury@xs4all.nl
 rurik@disinfo.net
diff --git a/mailman/absynthe.py b/mailman/absynthe.py
index b3966b6..c00311e 100644
--- a/mailman/absynthe.py
+++ b/mailman/absynthe.py
@@ -1,382 +1,369 @@
-## Indstillinger for maillisten "absynthe"  -*- python -*-
-## Dato: Sun Dec 11 16:35:45 2005
+# -*- python -*-
+# -*- coding: us-ascii -*-
+## "absynthe" mailing list configuration settings
+## captured on Tue Mar 20 08:51:53 2007
 
 ## General options
 #
-# Grundlæggende egenskaber for listen, herunder en beskrivelse af
-# listen. 
-
-# Du kan f.eks. stave navnet med stort forbogstav eller ændre andre
-# bogstaver til store, så navnet bliver udtalt rigtigt eller at
-# forkortelser fremhæves. Bemærk at dette navn bruges i e-maillistens
-# adresse (f.eks. i bekræftelser ved tilmeldinger), så navnet kan
-# ikke ændres på nogen anden måde. (e-mailadresser er ikke
-# følsomme for store eller små bogstaver, men de er
-# følsomme for næsten alt andet :-)
+# Fundamental list characteristics, including descriptive info and basic
+# behaviors.
+
+# The capitalization of this name can be changed to make it presentable
+# in polite company as a proper noun, or to make an acronym part all
+# upper case, etc.  However, the name will be advertised as the email
+# address (e.g., in subscribe confirmation notices), so it should not be
+# otherwise altered.  (Email addresses are not case sensitive, but they
+# are sensitive to almost everything else :-)
 real_name = 'Absynthe'
 
-# Der er to roller forbundet med hver mailliste. Listeadministratorerne
-# er dem der som sidste instans har kontrol over alle indstillingerne
-# for maillisten. De kan ændre alle indstillinger der er
-# tilgængelige via disse administrative websider.
-# 
-# Listemoderatorerne har begrænset adgang; de kan ikke ændre
-# indstillinger for e-maillisten, men de kan tage sig af anmodninger i
-# forbindelse med listen, f.eks. anmodning om medlemskab, eller
-# godkende/afvise meddelelser der skal godkendes for at kunne udsendes
-# til listen. Listeadministratorerne kan også udføre disse
-# opgaver.
-# 
-# For at aktivere muligheden for at have listemoderatorer, og på
-# den måde fordele arbejdsopgaverne i forbindelse med listen, skal
-# du anføre din egen moderatoradgangskode, og angive
-# e-mailadresser for den/dem som skal være listemoderator(er).
-# Bemærk at i tekstboksene nedenfor skal du skrive e-mailadresser for
-# listeadministratorer.
+# There are two ownership roles associated with each mailing list.  The
+# list administrators are the people who have ultimate control over all
+# parameters of this mailing list.  They are able to change any list
+# configuration variable available through these administration web
+# pages.
+# 
+# The list moderators have more limited permissions; they are not able
+# to change any list configuration variable, but they are allowed to
+# tend to pending administration requests, including approving or
+# rejecting held subscription requests, and disposing of held postings.
+# Of course, the list administrators can also tend to pending requests.
+# 
+# In order to split the list ownership duties into administrators and
+# moderators, you must set a separate moderator password, and also
+# provide the email addresses of the list moderators.  Note that the
+# field you are changing here specifies the list administrators.
 owner = ['go@jones.dk']
 
-# Der er to ejer-roller forbundet med hver mailliste.
-# Listeadministratorerne er dem der har den endelige kontrol over alle
-# indstillingerne for e-mallisten. De kan ændre alle indstillinger
-# der er tilgængelige via disse administrative websider.
-# 
-# Listemoderatorerne har begrænset adgang; de kan ikke ændre
-# indstillinger for e-maillisten, men de kan tage sig af anmodninger
-# angående listen, f.eks. anmodning om medlemskab, eller
-# godkende/afvise meddelelser der skal godkendes for at kunne udsendes
-# på listen. Listeadministratorerne kan selvsagt også
-# udføre disse opgaver.
-# 
-# For at aktivere muligheden for at have listemoderatorer, og på
-# den måde fordele arbejdsopgaverne i forbindelse med listen, skal
-# du anføre din egen moderatoradgangskode, og indtaste
-# e-mailadresser for den/dem der skal være listemoderatore(r).
-# Bemærk, at i tekstboksene nedenfor skal du skrive listemoderator
-# e-mailadresse(r).
+# There are two ownership roles associated with each mailing list.  The
+# list administrators are the people who have ultimate control over all
+# parameters of this mailing list.  They are able to change any list
+# configuration variable available through these administration web
+# pages.
+# 
+# The list moderators have more limited permissions; they are not able
+# to change any list configuration variable, but they are allowed to
+# tend to pending administration requests, including approving or
+# rejecting held subscription requests, and disposing of held postings.
+# Of course, the list administrators can also tend to pending requests.
+# 
+# In order to split the list ownership duties into administrators and
+# moderators, you must set a separate moderator password, and also
+# provide the email addresses of the list moderators in this section.
+# Note that the field you are changing here specifies the list
+# moderators.
 moderator = []
 
-# Denne beskrivelse benyttes når denne malliste listes op sammen
-# med andre maillister, i toptekster, osv. Den bør være
-# så kort som overhovedet mulig, uden at det bliver uklart hvad
-# meningen med maillisten er eller hvad den skal bruges til.
+# This description is used when the mailing list is listed with other
+# mailing lists, or in headers, and so forth.  It should be as succinct
+# as you can get it, while still identifying what the list is.
 description = ''
 
-# Teksten tolkes som html bortset fra linieskift, der vil blive
-# &aelig;ndret til html-tag'et '<br>', sådan at du kan benytte links,
-# forh&aring;ndsformateret tekst, osv. Men brug alts&aring; kun
-# linieskift der hvor du vil have et nyt afsnit. V&aelig;r meget
-# omhyggelig, hvis du benytter html-kode. Fejl (f.eks. manglende
-# slut-tag's) kan f&oslash;re til at listens informationsside ikke
-# bliver vist s&aring;dan som den skal.
+# The text will be treated as html except that newlines will be
+# translated to <br> - so you can use links, preformatted text, etc, but
+# don't put in carriage returns except where you mean to separate
+# paragraphs.  And review your changes - bad html (like some
+# unterminated HTML constructs) can prevent display of the entire
+# listinfo page.
 info = ''
 
 # This text will be prepended to subject lines of messages posted to the
-# list, to distinguish mailing list messages in in mailbox summaries.
+# list, to distinguish mailing list messages in mailbox summaries.
 # Brevity is premium here, it's ok to shorten long mailing list names to
 # something more concise, as long as it still identifies the mailing
-# list.
+# list. You can also add a sequential number by %d substitution
+# directive. eg.; [listname %d] -> [listname 123] (listname %05d) ->
+# (listname 00123)
+# 
 subject_prefix = '[Absynthe] '
 
-# Skjul afsenderen af meddelelser, ved at erstatte den med e-maillistens
-# adresse (Dette medfører at alle From:, Sender, og Reply-To: felter
-# fjernes)
+# Hide the sender of a message, replacing it with the list address
+# (Removes From, Sender and Reply-To fields)
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 anonymous_list = 0
 
-# Skal eksisterende Reply-To: felt i brevhovedet fjernes? Hvis ja, vil
-# dette blive gjort uanset om Mailman tilføjer et Reply-To: felt eller
-# ikke.
+# Should any existing Reply-To: header found in the original message be
+# stripped?  If so, this will be done regardless of whether an explict
+# Reply-To: header is added by Mailman or not.
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 first_strip_reply_to = 0
 
-# Denne indstillling fort&aelig;ller hvad Mailman skal g&oslash;re med
-# Reply-To: feltet i brevhovedet p&aring; e-mail der sendes til listen.
-# Hvis den er sat til Afsender, vil Mailman ikke tilf&oslash;je noget
-# Reply-To: felt, men findes et s&aring;dant felt allerede, vil det ikke
-# blive fjernet. S&aelig;ttes indstillingen til enten e-maillistens
-# adresse eller Egendefineret adresse, vil Mailman tilf&oslash;je, evt.
-# erstatte, et Reply-To: felt. (Egendefineret adresse inds&aelig;tter
-# v&aelig;rdien af indstillingen reply_to_address).
-# 
-# Der er flere grunde til ikke at indf&oslash;re eller erstatte
-# Reply-To: felter. En grund kan v&aelig;re at nogen af dem der sender
-# mail til listen er afh&aelig;ngige af selv at kunne s&aelig;tte
-# Reply-To: adressen. En anden grund er at modifikation af Reply-To:
-# adressen g&oslash;r det vanskeligere kun at sende svar til afsender.
-# Se 'Reply-To' Munging Considered Harmful for en diskussion omkring
-# emnet. Se Reply-To Munging Considered Useful for modsatte meninger.
-# 
-# Nogle maillister har begr&aelig;nset adgang, med en parallel liste
-# beregnet til diskussioner. Eksempler p&aring; dette er 'patches' eller
-# 'checkin' lister, som system for revisionskontrol sender
-# &aelig;ndringer i programmet til, men diskussioner omkring udvikling
-# af programmet sendes til udviklernes egen mailliste. For at
-# underst&oslash;tte lignende e-maillister, v&aelig;lg Egendefineret
-# adresse og s&aelig;t Reply-To: adressen i indstillingen
-# reply_to_address til at pege på den parallelle diskussionsliste.
-#
-# gyldige værdier:
-#    0 = "Afsender"
-#    1 = "mail listens adresse"
-#    2 = "Egendefineret adresse"
+# This option controls what Mailman does to the Reply-To: header in
+# messages flowing through this mailing list.  When set to Poster, no
+# Reply-To: header is added by Mailman, although if one is present in
+# the original message, it is not stripped.  Setting this value to
+# either This list or Explicit address causes Mailman to insert a
+# specific Reply-To: header in all messages, overriding the header in
+# the original message if necessary (Explicit address inserts the value
+# of <a href="?VARHELP=general/reply_to_address">reply_to_address).
+# 
+# There are many reasons not to introduce or override the Reply-To:
+# header.  One is that some posters depend on their own Reply-To:
+# settings to convey their valid return address.  Another is that
+# modifying Reply-To: makes it much more difficult to send private
+# replies.  See <a
+# href="http://www.unicom.com/pw/reply-to-harmful.html">`Reply-To'
+# Munging Considered Harmful for a general discussion of this issue.
+# See <a
+# href="http://www.metasystema.net/essays/reply-to.mhtml">Reply-To
+# Munging Considered Useful for a dissenting opinion.
+# 
+# Some mailing lists have restricted posting privileges, with a parallel
+# list devoted to discussions.  Examples are `patches' or `checkin'
+# lists, where software changes are posted by a revision control system,
+# but discussion about the changes occurs on a developers mailing list.
+# To support these types of mailing lists, select Explicit address and
+# set the Reply-To: address below to point to the parallel list.
+#
+# legal values are:
+#    0 = "Poster"
+#    1 = "This list"
+#    2 = "Explicit address"
 reply_goes_to_list = 1
 
-# Her definerer du adressen der skal s&aelig;ttes i Reply-To: feltet
-# n&aring;r indstillingen reply_goes_to_list er sat til Egendefineret
-# adresse.
-# 
-# Der findes mange grunde til at ikke indf&oslash;re eller erstatte
-# Reply-To: felter. En grund kan v&aelig;re at nogen af dem der sender
-# e-mail til listen er afh&aelig;ngige af selv at kunne s&aelig;tte
-# Reply-To: adressen. En anden grund er at modificering af Reply-To:
-# adressen g&oslash;r det vanskeligere at sende svar kun til afsender.
-# Se 'Reply-To' Munging Considered Harmful for en diskussion omkring
-# temaet. Se Reply-To Munging Considered Useful for modsatte meninger.
-# 
-# Nogle maillister har begr&aelig;nset adgang, med en egen parallel
-# liste beregnet for diskussioner. Eksempler p&aring; dette er 'patches'
-# eller 'checkin' lister, som system for revisionskontrol sender
-# &aelig;ndringer i programmet til, mens diskussioner omkring udvikling
-# af programmet sendes til udviklernes egen mailliste. For at
-# underst&oslash;tte s&aring;danne maillister, kan du definere Reply-To:
-# adressen her, og vælge Egendefineret adresse i indstillingen
-# reply_goes_to_list.
-# 
-# Bem&aelig;rk at hvis den oprindelige meddelelse indeholder et
-# Reply-To: felt, vil det ikke &aelig;ndres.
+# This is the address set in the Reply-To: header when the <a
+# href="?VARHELP=general/reply_goes_to_list">reply_goes_to_list option
+# is set to Explicit address.
+# 
+# There are many reasons not to introduce or override the Reply-To:
+# header.  One is that some posters depend on their own Reply-To:
+# settings to convey their valid return address.  Another is that
+# modifying Reply-To: makes it much more difficult to send private
+# replies.  See <a
+# href="http://www.unicom.com/pw/reply-to-harmful.html">`Reply-To'
+# Munging Considered Harmful for a general discussion of this issue.
+# See <a
+# href="http://www.metasystema.net/essays/reply-to.mhtml">Reply-To
+# Munging Considered Useful for a dissenting opinion.
+# 
+# Some mailing lists have restricted posting privileges, with a parallel
+# list devoted to discussions.  Examples are `patches' or `checkin'
+# lists, where software changes are posted by a revision control system,
+# but discussion about the changes occurs on a developers mailing list.
+# To support these types of mailing lists, specify the explicit
+# Reply-To: address here.  You must also specify Explicit address in the
+# reply_goes_to_list variable.
+# 
+# Note that if the original message contains a Reply-To: header, it will
+# not be changed.
 reply_to_address = ''
 
-# V&aelig;lg kun 'ja' her, hvis listen skal bruges som  "paraply" for
-# andre lister. Hvis 'ja' er valgt, vil bekr&aelig;ftelser og
-# meddelelser med adgangskode blive sendt til en adresse som konstrueres
-# ud fra medlemmets e-mailadresse - v&aelig;rdien af indstillingen
-# "umbrella_member_suffix" tilf&oslash;jes medlemmets kontonavn (det som
-# st&aring;r f&oslash;r @-tegnet).
+# Set this to yes when this list is intended to cascade only to other
+# mailing lists.  When set, meta notices like confirmations and password
+# reminders will be directed to an address derived from the member's
+# address - it will have the value of "umbrella_member_suffix" appended
+# to the member's account name.
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 umbrella_list = 0
 
-# N&aring;r "umbrella_list" indikerer at denne liste har andre
-# maillister som medlemmer, skal administrative meddelelser som f.eks.
-# bekr&aelig;ftelser og p&aring;mindelser om adgangskode ikke sendes til
-# selve listen, men snarere til administrator for listen. V&aelig;rdien
-# af denne indstilling bestemmer, hvilken adresse administrative
-# meddelelser skal sendes til. '-owner' er et almindeligt valg for denne
-# indstilling. Denne indstilling har ingen effekt n&aring;r
-# "umbrella_list" er sat til "Nej".
+# When "umbrella_list" is set to indicate that this list has other
+# mailing lists as members, then administrative notices like
+# confirmations and password reminders need to not be sent to the member
+# list addresses, but rather to the owner of those member lists.  In
+# that case, the value of this setting is appended to the member's
+# account name for such notices.  `-owner' is the typical choice.  This
+# setting has no effect when "umbrella_list" is "No".
 umbrella_member_suffix = '-owner'
 
-# Aktiver denne, hvis der skal sendes en p&aring;mindelse om adgangskode
-# til medlemmerne en gang hver m&aring;ned. Husk at medlemmerne
-# ogs&aring; selv kan frav&aelig;lge dette.
+# Turn this on if you want password reminders to be sent once per month
+# to your members.  Note that members may disable their own individual
+# password reminders.
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 send_reminders = 0
 
-# Tekst du skriver her vil blive tilf&oslash;jet &oslash;verst i
-# velkomsthilsenen der sendes til nye medlemmer. Velkomshilsenen
-# indeholder i forvejen vigtige adresser og URLer knyttet til
-# maillisten, s&aring; den slags information er det ikke
-# n&oslash;dvendigt at inkludere her. Her kan du tilf&oslash;je f.eks.
-# oplysning om etikette eller regler for brug af listen, o.l.
-# 
-# Bem&aelig;rk: Linierne i denne tekst vil brydes efter f&oslash;lgende
-# regler:
+# This value, if any, will be added to the front of the new-subscriber
+# welcome message.  The rest of the welcome message already describes
+# the important addresses and URLs for the mailing list, so you don't
+# need to include any of that kind of stuff here.  This should just
+# contain mission-specific kinds of things, like etiquette policies or
+# team orientation, or that kind of thing.
 # 
-# Hvert afsnit udfyldes s&aringdan at ingen linie er l&aelig;ngere en 70
-# tegn. Enhver linie der begynder med tomme tegn udfyldes ikke. Tomme
-# linier adskiller afsnit.
+# Note that this text will be wrapped, according to the following rules:
+# Each paragraph is filled so that no line is longer than 70 characters.
+# Any line that begins with whitespace is not filled. A blank line
+# separates paragraphs.
 # 
 welcome_msg = ''
 
-# S&aelig;t kun denne til 'Nej' hvis du skal tilf&oslash;je nye
-# medlemmer manuelt, og ikke vil have at de f&aring;r det at vide. Dette
-# er meget nyttigt n&aring;r man g&aring;r fra et andet mallistesystem
-# og til Mailman, og vil have at overgangen skal v&aelig;re s&aring;
-# lidt m&aelig;rkbar som muligt.
+# Turn this off only if you plan on subscribing people manually and
+# don't want them to know that you did so.  This option is most useful
+# for transparently migrating lists from some other mailing list manager
+# to Mailman.
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 send_welcome_msg = 1
 
-# Tekst der sendes til medlemmer der framelder sig listen. Hvis feltet
-# er tomt, tilf&oslash;jes der ikke nogen speciel tekst til
-# frameldingen.
+# Text sent to people leaving the list.  If empty, no special text will
+# be added to the unsubscribe message.
 goodbye_msg = ''
 
-# Send afskedshilsen til medlemmer n&aring;r de frameldes?
+# Send goodbye message to members when they are unsubscribed?
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 send_goodbye_msg = 1
 
-# Der udsendes en p&aring;mindelse til listemoderator (og
-# listeadministrator) dagligt om anmodninger der af en eller anden grund
-# venter p&aring; behandling. V&aelig;lger du "Ja", vil
-# listeadminstrator ogs&aring; modtage en meddelelse s&aring; snart en
-# anmodning ankommer.
+# List moderators (and list administrators) are sent daily reminders of
+# requests pending approval, like subscriptions to a moderated list, or
+# postings that are being held for one reason or another.  Setting this
+# option causes notices to be sent immediately on the arrival of new
+# requests as well.
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 admin_immed_notify = 1
 
-# Skal listeadministrator modtage meddelelse om tilmeldinger og
-# afmeldinger?
+# Should administrator get notices of subscribes and unsubscribes?
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 admin_notify_mchanges = 0
 
-# Approval notices are sent when mail triggers certain of the limits
-# except routine list moderation and spam filters, for which notices are
-# not sent.  This option overrides ever sending the notice.
+# Send mail to poster when their posting is held for approval?
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 respond_to_post_requests = 1
 
-# Når dette valg er aktiveret, vil al e-mail til listen blive modereret.
-# Dette valg kan være nyttigt når din mailliste f.eks. har en såkaldt
-# "flamewar", altså en "krig" hvor medlemmer kun skælder ud på hinanden.
-# En "nød-moderering" kan da hjælpe dig at fjerne usaglige meddelelser
-# til listen, og på den måde dysse en ophedet diskussion ned.
+# When this option is enabled, all list traffic is emergency moderated,
+# i.e. held for moderation.  Turn this option on when your list is
+# experiencing a flamewar and you want a cooling off period.
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 emergency = 0
 
-# Når et nyt medlem tilmeldes listen, bliver medlemmets indstillinger
-# taget herfra.
+# When a new member is subscribed to this list, their initial set of
+# options is taken from the this variable's setting.
 new_member_options = 256
 
-# Filter for administrative meddelelser vil unders&oslash;ge om
-# meddelelsen egentligt er ment som en administrativ anmodning (f.eks.
-# tilmelding, framelding, o.l.), og i s&aring; fald sende meddelelsen
-# til listeadministrator i stedet for.
+# Administrivia tests will check postings to see whether it's really
+# meant as an administrative request (like subscribe, unsubscribe, etc),
+# and will add it to the the administrative requests queue, notifying
+# the administrator of the new request, in the process.
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 administrivia = 1
 
-# Maximum st&oslash;rrelse i kilobytes (KB) for indholdet i e-mail der
-# sendes til listen. Brug v&aelig;rdien '0' for ikke at have nogen
-# begr&aelig;nsning.
+# Maximum length in kilobytes (KB) of a message body.  Use 0 for no
+# limit.
 max_message_size = 40
 
-# "Maskinnavnet" er det navn som skal benyttes for e-mailadresser
-# relateret til Mailman p&aring; denne maskine, og er normalt navnet der
-# er forbundet med e-mail-servicen p&aring; maskinen. Denne indstilling
-# kan v&aelig;re nyttig hvis maskinen har flere navne.
+# The "host_name" is the preferred name for email to mailman-related
+# addresses on this host, and generally should be the mail host's
+# exchanger address, if any.  This setting can be useful for selecting
+# among alternative names of a host that has multiple addresses.
 host_name = 'jones.dk'
 
-# I RFC 2369 defineres en r&aelig;kke List-* felter i brevhovedet, der
-# normalt tilf&oslash;jes enhver meddelelse der sendes ud via listen.
-# Disse felter er til stor gavn for brugere , som benytter et
-# e-mailprogram der f&oslash;lger standarden. Disse felter b&oslash;r
-# derfor altid v&aelig;re med.
-# 
-# Ikke alle e-mailprogrammer f&oslash;lger denne standard. Hvis der er
-# mange medlemmer p&aring; listen, der benytter e-mailprogrammer, der
-# ikke kan h&aring;ndtere disse felter i brevhovedet, kan du v&aelig;lge
-# at udelade dem. Men du b&oslash;r f&oslash;rst fors&oslash;ge at
-# l&aelig;re og forklare medlemmerne hvad hensigten med s&aring;danne
-# felter er, og hvordan de kan skjule dem i deres e-mailprogram. Som en
-# sidste udvej kan du udelade felterne, men det anbefales ikke (og denne
-# mulighed kan faktisk ogs&aring; blive fjernet i senere versioner af
-# Mailman).
-#
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# RFC 2369 defines a set of List-* headers that are normally added to
+# every message sent to the list membership. These greatly aid end-users
+# who are using standards compliant mail readers.  They should normally
+# always be enabled.
+# 
+# However, not all mail readers are standards compliant yet, and if you
+# have a large number of members who are using non-compliant mail
+# readers, they may be annoyed at these headers.  You should first try
+# to educate your members as to why these headers exist, and how to hide
+# them in their mail clients.  As a last resort you can disable these
+# headers, but this is not recommended (and in fact, your ability to
+# disable these headers may eventually go away).
+#
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 include_rfc2369_headers = 1
 
-# List-Post: feltet er et af felterne anbefalet i RFC 2369. P&aring;
-# nogle e-maillister (som f.eks. kun bruges til
-# offentligg&oslash;relser), er det kun bestemte personer der har lov
-# til at poste til listen. Almindelige medlemmer af listen har normalt
-# ikke lov til at poste til listen. For den slags lister, er List-Post:
-# feltet misvisende. S&aelig;t denne indstilling til Nej, for at
-# undg&aring; at feltet tilf&oslash;jes. (Dette p&aring;virker ikke
-# andre List-*: felter.)
-#
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# The List-Post: header is one of the headers recommended by RFC 2369.
+# However for some announce-only mailing lists, only a very select group
+# of people are allowed to post to the list; the general membership is
+# usually not allowed to post.  For lists of this nature, the List-Post:
+# header is misleading. Select No to disable the inclusion of this
+# header. (This does not affect the inclusion of the other List-*:
+# headers.)
+#
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 include_list_post_header = 1
 
+# Discard held messages older than this number of days. Use 0 for no
+# automatic discarding.
+max_days_to_hold = 0
+
 ## Language options
 #
-# Underst&oslash;ttelse af flere sprog. (Internationalisering)
-
-# Dette er standardsproget som benyttes for denne mailliste. Hvis flere
-# end et sprog/ underst&oslash;ttes, vil medlemmer af listen selv kunne
-# v&aelig;lge hvilket sprog der skal benyttes n&aring;r de g&aring;r ind
-# p&aring; deres personlige webside, og n&aring;r meddelelser fra
-# systemet sendes til dem. Hvis medlemmerne ikke &aelig;ndrer noget
-# selv, vil dette standardsprog blive benyttet. Dette g&aelig;lder
-# b&aring;de web-baserede og e-mail-baserede meddelelser, men ikke
-# meddelelser sendt af listens medlemmer.
+# Natural language (internationalization) options.
+
+# This is the default natural language for this mailing list. If more
+# than one language is supported then users will be able to select their
+# own preferences for when they interact with the list.  All other
+# interactions will be conducted in the default language.  This applies
+# to both web-based and email-based messages, but not to email posted by
+# list members.
 preferred_language = 'en'
 
-# Her er alle sprog, som denne liste har underst&oslash;ttelse for.
-# Bem&aelig;rk at standardsproget skal v&aelig;re med.
+# These are all the natural languages supported by this list. Note that
+# the default language must be included.
 available_languages = ['en', 'da']
 
-# Hvis standardsproget for din mailliste benytter et andet tegns&aelig;t
-# end ASCII og Emne prefixet for listen indeholder tegn som ikke findes
-# i ASCII-tegns&aelig;ttet, vil prefixet altid blive kodet i henhold til
-# den relevante standard. Hvis Emne prefixet kun indeholder ASCII tegn,
-# ønsker du måske at vælge Aldrig for at undgå kodning. Dette kan gøre
-# emnet lidt mere læseligt for brugere med e-mailprogrammer der ikke kan
-# håndtere andre tegnsæt end ASCII.
-# 
-# Bemærk imidlertid, at hvis din mailliste modtager både kodede og
-# ukodede emnefelter , kan det være bedst at vælge Efter behov. Med
-# denne indstilling vil Mailman ikke kode ASCII prefixer hvis resten af
-# titelfeltet kun indeholder ASCII tegn, men vil kode prefixet hvis det
-# indeholder tegn som ikke er ASCII tegn. På denne måde undgås en
-# tvetydighed i standarderne, som forårsager at visse e-mailprogrammer
-# vil vise ekstra eller manglende mellemrum imellem emne prefixet og det
-# oprindelige emne.
-#
-# gyldige værdier:
-#    0 = "Aldrig"
-#    1 = "Altid"
-#    2 = "Efter behov"
+# If your mailing list's default language uses a non-ASCII character set
+# and the prefix contains non-ASCII characters, the prefix will always
+# be encoded according to the relevant standards.  However, if your
+# prefix contains only ASCII characters, you may want to set this option
+# to Never to disable prefix encoding.  This can make the subject
+# headers slightly more readable for users with mail readers that don't
+# properly handle non-ASCII encodings.
+# 
+# Note however, that if your mailing list receives both encoded and
+# unencoded subject headers, you might want to choose As needed.  Using
+# this setting, Mailman will not encode ASCII prefixes when the rest of
+# the header contains only ASCII characters, but if the original header
+# contains non-ASCII characters, it will encode the prefix.  This avoids
+# an ambiguity in the standards which could cause some mail readers to
+# display extra, or missing spaces between the prefix and the original
+# header.
+#
+# legal values are:
+#    0 = "Never"
+#    1 = "Always"
+#    2 = "As needed"
 encode_ascii_prefixes = 0
 
 ## Nondigest options
 #
-# Regler for levering i normal-modus.
+# Policies concerning immediately delivered list traffic.
 
-# Kan medlemmer vælge normal-modus?
+# Can subscribers choose to receive mail immediately, rather than in
+# batched digests?
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 nondigestable = 1
 
-# Tekst der tilføjes &oslash;verst i e-mail der sendes til listens
-# medlemmer. This text can include Python format strings which are
-# resolved against list attributes.  The list of substitutions allowed
-# are:
+# Text prepended to the top of every immediately-delivery message. This
+# text can include Python format strings which are resolved against list
+# attributes.  The list of substitutions allowed are:
 # 
 # 
 # real_name - The "pretty" name of the list; usually the list name with
@@ -401,10 +388,9 @@ nondigestable = 1
 # 
 msg_header = ''
 
-# Tekst som tilf&oslash;jes nederst i e-mail der sendes til listens
-# medlemmer. This text can include Python format strings which are
-# resolved against list attributes.  The list of substitutions allowed
-# are:
+# Text appended to the bottom of every immediately-delivery message.
+# This text can include Python format strings which are resolved against
+# list attributes.  The list of substitutions allowed are:
 # 
 # 
 # real_name - The "pretty" name of the list; usually the list name with
@@ -432,45 +418,54 @@ msg_footer = """_______________________________________________
 %(real_name)s@%(host_name)s
 %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s"""
 
+# When you scrub attachments, they are stored in archive area and links
+# are made in the message so that the member can access via web browser.
+# If you want the attachments totally disappear, you can use content
+# filter options.
+#
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
+scrub_nondigest = False
+
 ## Digest options
 #
-# Opsætning af sammendrag-modus.
+# Batched-delivery digest characteristics.
 
-# Kan medlemmer af listen vælge sammendrag-modus?
+# Can list members choose to receive list traffic bunched in digests?
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 digestable = 1
 
-# Hvilken modus er standard for nye brugere?
+# Which delivery mode is the default for new users?
 #
-# gyldige værdier:
-#    0 = "Normal"
-#    1 = "Sammendrag"
+# legal values are:
+#    0 = "Regular"
+#    1 = "Digest"
 digest_is_default = 0
 
-# Hvilket format skal benyttes som standard for samle-email?
+# When receiving digests, which format is default?
 #
-# gyldige værdier:
-#    0 = "Ren tekst"
+# legal values are:
+#    0 = "Plain"
 #    1 = "MIME"
 mime_is_default_digest = 0
 
-# Hvor stor (i KB) m&aring; en samle-email h&oslash;jst v&aelig;re
-# f&oslash;r den udsendes?
+# How big in Kb should a digest be before it gets sent out?
 digest_size_threshhold = 30
 
-# Skal der sendes en samle-email dagligt, selv om st&oslash;rrelsen ikke
-# er opn&aring;et?
+# Should a digest be dispatched daily when the size threshold isn't
+# reached?
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 digest_send_periodic = 1
 
-# Tekst som tilf&oslash;jes &oslash;verst i samle-emailen, f&oslash;r
-# indholdsfortegnelsen.This text can include Python format strings which
+# Text attached (as an initial message, before the table of contents) to
+# the top of digests. This text can include Python format strings which
 # are resolved against list attributes.  The list of substitutions
 # allowed are:
 # 
@@ -497,10 +492,9 @@ digest_send_periodic = 1
 # 
 digest_header = ''
 
-# Tekst der tilføjes nederst i hver samle-email, som sidste
-# information.This text can include Python format strings which are
-# resolved against list attributes.  The list of substitutions allowed
-# are:
+# Text attached (as a final message) to the bottom of digests. This text
+# can include Python format strings which are resolved against list
+# attributes.  The list of substitutions allowed are:
 # 
 # 
 # real_name - The "pretty" name of the list; usually the list name with
@@ -528,277 +522,279 @@ digest_footer = """_______________________________________________
 %(real_name)s@%(host_name)s
 %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s"""
 
-# N&aring;r et nyt volume startes, &oslash;ges volume nummeret, og
-# udgavenummeret s&aelig;ttes til 1.
+# When a new digest volume is started, the volume number is incremented
+# and the issue number is reset to 1.
 #
-# gyldige værdier:
-#    0 = "&Aring;rlig"
-#    1 = "M&aring;nedlig"
-#    2 = "Kvartalsvis"
-#    3 = "Ugentlig"
-#    4 = "Daglig"
+# legal values are:
+#    0 = "Yearly"
+#    1 = "Monthly"
+#    2 = "Quarterly"
+#    3 = "Weekly"
+#    4 = "Daily"
 digest_volume_frequency = 1
 
 ## Privacy options
 #
-# Her kan du bestemme hvad der kr&aelig;ves for at tilmelde sig til
-# maillisten, og bl.a. bestemme om maillisten skal v&aelig;re skjult
-# eller ikke. Se ogs&aring; <a
-# href="http://mail.jones.dk/cgi-bin/mailman/admin/absynthe/archive">Indstillinger 
-# for arkivering</a> for egne indstillinger, n&aring;r det g&aelig;lder
-# arkivet og arkivering.
+# This section allows you to configure subscription and membership
+# exposure policy.  You can also control whether this list is public or
+# not.  See also the <a
+# href="http://mail.jones.dk/cgi-bin/mailman/admin/absynthe/archive">Archival 
+# Options</a> section for separate archive-related privacy settings.
 
-# Vis denne mailliste n&aring;r nogen beder om at se en oversigt over
-# maillister p&aring; denne maskine?
+# Advertise this list when people ask what lists are on this machine?
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 advertised = 1
 
-# bekræftelse(*) - bekr&aelig;ftelse via e-mail er n&oslash;dvendig
-# godkendelse - anmodning om medlemskab skal godkendes af
-# listeadministrator (eller evt. listemoderator) bekr&aelig;ftelse +
-# godkendelse - b&aring;de bekr&aelig;ftelse via e-mail og godkendelse
-# fra listeadministrator (evt. listemoderator) er n&oslash;dvendig
-# 
-# (*) n&aring;r nogen vil tilmelde sig en liste, sender Mailman en
-# meddelelse med en unik identifikator som skal angives for at
-# bekr&aelig;fte tilmeldingen. P&aring; den m&aring;de vil det ikke
-# v&aelig;re muligt at tilmelde nogen imod deres vilje.
-#
-# gyldige værdier:
-#    1 = "Bekr&aelig;ftelse"
-#    2 = "Godkendelse"
-#    3 = "Bekr&aelig;ftelse og godkendelse"
+# Confirm (*) - email confirmation required Require approval - require
+# list administrator approval for subscriptions Confirm and approve -
+# both confirm and approve
+# 
+# (*) when someone requests a subscription, Mailman sends them a notice
+# with a unique subscription request number that they must reply to in
+# order to subscribe. This prevents mischievous (or malicious) people
+# from creating subscriptions for others without their consent.
+#
+# legal values are:
+#    1 = "Confirm"
+#    2 = "Require approval"
+#    3 = "Confirm and approve"
 subscribe_policy = 1
 
-# N&aring;r medlemmer &oslash;nsker at forlade en mailliste, sender de
-# en anmodning om framelding, enten via web, eller via e-mail. Normalt
-# er det bedst at disse anmodninger automatisk godkendes, s&aring;
-# medlemmer kan afmelde sig n&aring;r de &oslash;nsker det (mange
-# &oslash;nsker selv at kunne administrere en framelding). For nogle
-# f&aring; maillister kan det alligevel v&aelig;re aktuelt at have
-# kontrol over om medlemmer kan afmelde sig selv eller ej. En liste som
-# alle ansatte i et firma SKAL v&aelig;re medlem af, er et eksempel
-# p&aring; en s&aring;dan liste.
-#
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# When members want to leave a list, they will make an unsubscription
+# request, either via the web or via email. Normally it is best for you
+# to allow open unsubscriptions so that users can easily remove
+# themselves from mailing lists (they get really upset if they can't get
+# off lists!).
+# 
+# For some lists though, you may want to impose moderator approval
+# before an unsubscription request is processed.  Examples of such lists
+# include a corporate mailing list that all employees are required to be
+# members of.
+#
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 unsubscribe_policy = 0
 
-# Alle e-mailadresser som angives her vil blive udelukket fra listen, og
-# kan ikke tilmelde sig. Indtast e-mailadresser, en pr. linie, start
-# linien med tegnet ^ for at angive et regexp-udtryk der skal stemme
-# overens med afsenderadressen.
+# Addresses in this list are banned outright from subscribing to this
+# mailing list, with no further moderation required.  Add addresses one
+# per line; start the line with a ^ character to designate a regular
+# expression match.
 ban_list = []
 
-# Hvis denne indstilling ikke er sat til 'Alle', vil medlemslisten blive
-# beskyttet af medlemmernes eller administrators adgangskode.
+# When set, the list of subscribers is protected by member or admin
+# password authentication.
 #
-# gyldige værdier:
-#    0 = "Alle"
-#    1 = "Kun medlemmer af listen"
-#    2 = "Kun listeadministrator"
+# legal values are:
+#    0 = "Anyone"
+#    1 = "List members"
+#    2 = "List admin only"
 private_roster = 0
 
-# V&aelig;lger du 'Ja' her, vil medlemmers e-mailadresser blive
-# omskrevet n&aring;r de vises i en oversigt p&aring; websiderne
-# (b&aring;de som tekst og som links), s&aring; de ikke er nemme at
-# tolke som e-mailadresser. Formålet er at undg&aring; at medlemmernes
-# mailadresser bliver opsamlet af e-mailsniffere som skanner websider
-# for e-mailadresser (og derefter bruger dem til at udsende spam/junk
-# mail).
-#
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# Setting this option causes member email addresses to be transformed
+# when they are presented on list web pages (both in text and as links),
+# so they're not trivially recognizable as email addresses.  The
+# intention is to prevent the addresses from being snarfed up by
+# automated web scanners for use by spammers.
+#
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 obscure_addresses = 1
 
 ## Privacy options
 #
-# N&aring;r en meddelelse sendes til maillisten, g&aring;r den igennem
-# nogle trin for at afg&oslash;re om moderator skal godkende meddelelsen
-# eller ikke. Her finder du indstillinger til at kontrollere moderation
-# af e-mail fra b&aring;de medlemmer og ikke-medlemmer.
-# 
-# <p>E-mail fra medlemmer holdes tilbage for godkendelse hvis deres
-# <b>moderationsflag</b> er sat. Du kan bestemme om e-mail fra medlemmer
-# normalt skal vurderes eller ikke f&oslash;r den sendes til listen.
-# 
-# <p>E-mail som ikke er sendt af medlemmer af listen, kan automatisk
-# blive <a
-# href="?VARHELP=privacy/sender/accept_these_nonmembers">godkendt</a>,
-# <a href="?VARHELP=privacy/sender/hold_these_nonmembers">holdt tilbage
-# for godkendelse</a>, <a
-# href="?VARHELP=privacy/sender/reject_these_nonmembers">afvist (sendt
-# retur)</a>, eller <a
-# href="?VARHELP=privacy/sender/discard_these_nonmembers">slettet</a>,
-# enten enkeltvis eller som en gruppe. Al e-mail fra ikke-medlemmer, som
-# ikke specifikt bliver godkendt, sendt retur eller slettet, vil blive
-# behandlet alt efter hvad <a
-# href="?VARHELP=privacy/sender/generic_nonmember_action">generelle
-# regler for ikke-medlemmer</a> viser.
-# 
-# <p>I tekstboksene nedenfor kan du tilf&oslash;je en e-mailadresse pr.
-# linie. Du kan ogs&aring; tilf&oslash;je  <a
-# href="http://www.python.org/doc/current/lib/module-re.html">Python
-# regexp-udtryk</a>. Begynd i s&aring; fald linien med tegnet ^ for at
-# markere at det er et s&aring;dant udtryk. N&aring;r du benytter
-# backslash, skriv da lige som i rene strings (Python raw strings)
-# (normalt kun &eacute;n backslash ad gangen).
-# 
-# <p>Bem&aelig;rk: sammenligning med normale e-mailadresser
-# udf&oslash;res f&oslash;rst, regexp-udtryk vil derfor blive behandlet
-# sidst.
-
-# Hvert medlem af listen har et moderationsflag som fort&aelig;ller om
-# e-mails fra medlemmet kan sendes direkte til e-maillisten, eller om de
-# f&oslash;rst skal godkendes af listemoderator. N&aring;r
-# moderationsflaget er sat til, skal e-mails fra medlemmet godkendes af
-# listemoderator f&oslash;r de udsendes til alle p&aring; listen. Som
-# listeadministrator kan du for hvert enkelt medlem bestemme om
-# medlemmets e-mail skal modereres eller ikke. N&aring;r et nyt medlem
-# tilmeldes listen, s&aelig;ttes moderationsflaget til den indstilling
-# du v&aelig;lger her. S&aelig;t den til 'Nej' hvis du &oslash;nsker at
-# e-mail fra medlemmer normalt skal g&aring; lige til listen. S&aelig;t
-# den til 'Ja' hvis du &oslash;nsker at e-mail fra nye medlemmer skal
-# godkendes f&oslash;r de udsendes til hele listen. Du kan altid
-# s&aelig;tte moderationsflaget for hvert enkelt medlem fra
-# Administration af medlemmer siden.
-#
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# When a message is posted to the list, a series of moderation steps are
+# take to decide whether the a moderator must first approve the message
+# or not.  This section contains the controls for moderation of both
+# member and non-member postings.
+# 
+# <p>Member postings are held for moderation if their <b>moderation
+# flag</b> is turned on.  You can control whether member postings are
+# moderated by default or not.
+# 
+# <p>Non-member postings can be automatically <a
+# href="?VARHELP=privacy/sender/accept_these_nonmembers" >accepted</a>,
+# <a href="?VARHELP=privacy/sender/hold_these_nonmembers">held for
+# moderation</a>, <a
+# href="?VARHELP=privacy/sender/reject_these_nonmembers" >rejected</a>
+# (bounced), or <a
+# href="?VARHELP=privacy/sender/discard_these_nonmembers"
+# >discarded</a>, either individually or as a group.  Any posting from a
+# non-member who is not explicitly accepted, rejected, or discarded,
+# will have their posting filtered by the <a
+# href="?VARHELP=privacy/sender/generic_nonmember_action">general
+# non-member rules</a>.
+# 
+# <p>In the text boxes below, add one address per line; start the line
+# with a ^ character to designate a <a href=
+# "http://www.python.org/doc/current/lib/module-re.html" >Python regular
+# expression</a>.  When entering backslashes, do so as if you were using
+# Python raw strings (i.e. you generally just use a single backslash).
+# 
+# <p>Note that non-regexp matches are always done first.
+
+# Each list member has a moderation flag which says whether messages
+# from the list member can be posted directly to the list, or must first
+# be approved by the list moderator.  When the moderation flag is turned
+# on, list member postings must be approved first.  You, the list
+# administrator can decide whether a specific individual's postings will
+# be moderated or not.
+# 
+# When a new member is subscribed, their initial moderation flag takes
+# its value from this option.  Turn this option off to accept member
+# postings by default.  Turn this option on to, by default, moderate
+# member postings first.  You can always manually set an individual
+# member's moderation bit by using the membership management screens.
+#
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 default_member_moderation = 0
 
+# Hold -- this holds the message for approval by the list moderators.
 # 
-# Hold tilbage -- meddelelsen holdes tilbage for godkendelse af
-# listemoderator(er). Afvis -- meddelelsen sendes automatisk retur til
-# afsender. Begrundelsen der sendes kan du skrive selv Slet --
-# meddelelsen bliver fjernet uden at give besked om dette til afsender.
+# Reject -- this automatically rejects the message by sending a bounce
+# notice to the post's author.  The text of the bounce notice can be <a
+# href="?VARHELP=privacy/sender/member_moderation_notice" >configured by
+# you.
+# 
+# Discard -- this simply discards the message, with no notice sent to
+# the post's author.
 # 
 #
-# gyldige værdier:
-#    0 = "Hold&nbsp;tilbage"
-#    1 = "Afvis"
-#    2 = "Slet"
+# legal values are:
+#    0 = "Hold"
+#    1 = "Reject"
+#    2 = "Discard"
 member_moderation_action = 0
 
-# Tekst som skal sendes med meddelelsen om afvisning som sendes til
-# modererede medlemmer af listen.
+# Text to include in any <a
+# href="?VARHELP/privacy/sender/member_moderation_action" >rejection
+# notice to be sent to moderated members who post to this list.
 member_moderation_notice = ''
 
-# E-mail fra disse ikke-medlemmer vil automatisk blive godkendt.
-# Tilf&oslash;j e-mailadresser, en pr. linie. Start linien med tegnet ^
-# for at angive et regexp-udtryk som skal stemme overens med
-# afsenderadressen.
+# Postings from any of these non-members will be automatically accepted
+# with no further moderation applied.  Add member addresses one per
+# line; start the line with a ^ character to designate a regular
+# expression match.
 accept_these_nonmembers = []
 
-# e-mail fra disse ikke-medlemmer vil automatisk blive holdt tilbage for
-# vurdering af listemoderator. Afsenderen vil modtage en meddelelse om
-# dette, med bl.a. instruktioner om hvordan han/hun kan
-# tilbagetr&aelig;kke sin e-mail. Indtast e-mailadresser, en pr. linie.
-# Start linien med tegnet ^ for at angive et regexp-udtryk som skal
-# stemme overens med afsenderadressen.
+# Postings from any of these non-members will be immediately and
+# automatically held for moderation by the list moderators. The sender
+# will receive a notification message which will allow them to cancel
+# their held message.  Add member addresses one per line; start the line
+# with a ^ character to designate a regular expression match.
 hold_these_nonmembers = []
 
-# E-mail fra disse ikke-medlemmer vil automatisk blive afvist. De vil
-# f&aring; mailen retur, med en meddelelse om at den blev automatisk
-# afvist. Dette valg b&oslash;r ikke benyttes for kendte spammere, de
-# b&oslash;r automatisk slettes. Indtast e-mailadresser, en pr. linie.
-# Start linien med tegnet ^ for at angive et regexp-udtryk som skal
-# stemme overens med afsenderadressen.
+# Postings from any of these non-members will be automatically rejected.
+# In other words, their messages will be bounced back to the sender with
+# a notification of automatic rejection.  This option is not appropriate
+# for known spam senders; their messages should be <a
+# href="?VARHELP=privacy/sender/discard_these_nonmembers" >automatically
+# discarded.
+# 
+# Add member addresses one per line; start the line with a ^ character
+# to designate a regular expression match.
 reject_these_nonmembers = []
 
-# E-mail fra disse ikke-medlemmer vil automatisk blive slettet. Det vil
-# sige at meddelelsen afvises uden nogen form for tilbagemelding, men
-# listemoderator kan (om &oslash;nsket) modtage en kopi af den afviste
-# e-mail. Tilf&oslash;j e-mailadresser, en pr. linie, start linien med
-# tegnet ^ for at angive et regexp-udtryk der skal stemme overens med
-# afsenderadressen.
+# Postings from any of these non-members will be automatically
+# discarded.  That is, the message will be thrown away with no further
+# processing or notification.  The sender will not receive a
+# notification or a bounce, however the list moderators can optionally
+# <a href="?VARHELP=privacy/sender/forward_auto_discards" >receive
+# copies of auto-discarded messages..
+# 
+# Add member addresses one per line; start the line with a ^ character
+# to designate a regular expression match.
 discard_these_nonmembers = []
 
-# N&aring;r en e-mail fra et ikke-medlem bliver modtaget, sammenlignes
-# e-mailens afsender med listen over e-mailadresser der skal godkendes,
-# holdes tilbage, <a
-# href="?VARHELP=privacy/sender/reject_these_nonmembers" >afvises
-# (sendes retur), eller slettes. Hvis afsenderadressen ikke stemmer
-# overens med en adresse der findes i listerne, bliver f&oslash;lgende
-# afg&oslash;relse truffet.
-#
-# gyldige værdier:
-#    0 = "Godkend"
-#    1 = "Hold&nbsp;tilbage"
-#    2 = "Afvis"
-#    3 = "Slet"
+# When a post from a non-member is received, the message's sender is
+# matched against the list of explicitly <a
+# href="?VARHELP=privacy/sender/accept_these_nonmembers" >accepted,
+# held, <a href="?VARHELP=privacy/sender/reject_these_nonmembers"
+# >rejected (bounced), and <a
+# href="?VARHELP=privacy/sender/discard_these_nonmembers" >discarded
+# addresses.  If no match is found, then this action is taken.
+#
+# legal values are:
+#    0 = "Accept"
+#    1 = "Hold"
+#    2 = "Reject"
+#    3 = "Discard"
 generic_nonmember_action = 1
 
-# Skal meddelelser fra ikke-medlemmer, hvis mail automatisk slettes,
-# videresendes til listemoderator?
+# Should messages from non-members, which are automatically discarded,
+# be forwarded to the list moderator?
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 forward_auto_discards = 1
 
+# Text to include in any rejection notice to be sent to non-members who
+# post to this list. This notice can include the list's owner address by
+# %(listowner)s and replaces the internally crafted default message.
+nonmember_rejection_notice = ''
+
 ## Privacy options
 #
-# Her kan du ops&aelig;tte filtrering baseret på modtageren af
-# meddelelsen.
+# This section allows you to configure various filters based on the
+# recipient of the message.
 
-# Meget (faktisk det meste) spam/junk mail har ikke de endelige
-# modtagere i modtagerfelterne. Faktisk indeholder felterne To: og/eller
-# Cc: oftest en helt ugyldig adresse. Begr&aelig;nsningen du
-# s&aelig;tter her har kun indvirkning p&aring; det som st&aring;r
-# f&oslash;r '@' tegnet i adressen, men filtret vil alligevel opfange og
-# blokere det meste spam/junk mail.
+# Many (in fact, most) spams do not explicitly name their myriad
+# destinations in the explicit destination addresses - in fact often the
+# To: field has a totally bogus address for obfuscation.  The constraint
+# applies only to the stuff in the address before the '@' sign, but
+# still catches all such spams.
+# 
+# The cost is that the list will not accept unhindered any postings
+# relayed from other addresses, unless
+# 
 # 
-# Prisen for dette er, at listen ikke uhindret vil kunne modtage e-mail
-# videresendt via andre e-mailadresser, med mindre
+# The relaying address has the same name, or
 # 
+# The relaying address name is included on the options that specifies
+# acceptable aliases for the list.
 # 
-# Adressen der videresendes fra hedder det samme, eller Adressen der
-# videresendes fra inkluderes i indstillingen som bestemmer gyldige
-# aliaser for listen.
 # 
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 require_explicit_destination = 1
 
-# Alternative e-mailadresser som godtages n&aring;r
-# 'require_explicit_destination' er sat til. Som v&aelig;rdi for denne
-# indstilling skal du angive regexp-udtryk ("regular expressions"), et
-# udtryk pr. linie, der sammenlignes med hver modtageradresse i
-# meddelelsen. Sammenligningen udf&oslash;res med Pythons re.match()
-# funktion, som betyder at de kun g&aelig;lder for begyndelsen af
-# strengen.
-# 
-# For bagudkompatibilitet med Mailman 1.1, hvis regexp-udtryk ikke
-# indeholder en '@', sammenlignes udtrykket kun med den f&oslash;rste
-# del (det som st&aring;r f&oslash;r '@') i modtageradressen. Hvis
-# sammenligningen ikke lykkes, eller hvis udtrykket ikke indholder en
-# '@', sammenlignes udtrykket med hele modtageradressen.
-# 
-# Sammenligning med kun den f&oslash;rste del af en modtageradresse
-# underst&oslash;ttes ikke l&aelig;ngere. I fremtidige versioner af
-# Mailman vil kun sammenligning med hele modtageradresser blive
-# underst&oslash;ttet.
+# Alternate addresses that are acceptable when
+# `require_explicit_destination' is enabled.  This option takes a list
+# of regular expressions, one per line, which is matched against every
+# recipient address in the message.  The matching is performed with
+# Python's re.match() function, meaning they are anchored to the start
+# of the string.
+# 
+# For backwards compatibility with Mailman 1.1, if the regexp does not
+# contain an `@', then the pattern is matched against just the local
+# part of the recipient address.  If that match fails, or if the pattern
+# does contain an `@', then the pattern is matched against the entire
+# recipient address.
+# 
+# Matching against the local part is deprecated; in a future release,
+# the pattern will always be matched against the entire recipient
+# address.
 acceptable_aliases = ''
 
-# Hvis en mail der er sendt til listen indeholder s&aring; mange som
-# eller flere modtagere end denne v&aelig;rdi, holdes mailen tilbage,
-# s&aring; listeadministrator eventuelt kan godkende den. Brug
-# v&aelig;rdien 0 for ingen begr&aelig;nsning.
+# If a posting has this number, or more, of recipients, it is held for
+# admin approval.  Use 0 for no ceiling.
 max_num_recipients = 10
 
 ## Privacy options
 #
-# Her kan du opsætte forskellige anti-spam filtre, som kan bidrage til
-# at reducere mængden af spam der distribueres via e-maillisten.
+# This section allows you to configure various anti-spam filters posting
+# filters, which can help reduce the amount of spam your list members
+# end up receiving.
+# 
 
 # Each header filter rule has two parts, a list of regular expressions,
 # one per line, and an action to take.  Mailman matches the message's
@@ -809,22 +805,23 @@ max_num_recipients = 10
 # You can have more than one filter rule for your list.  In that case,
 # each rule is matched in turn, with processing stopped after the first
 # match.
+# 
+# Note that headers are collected from all the attachments (except for
+# the mailman administrivia message) and matched against the regular
+# expressions. With this feature, you can effectively sort out messages
+# with dangerous file types or file name extensions.
 header_filter_rules = []
 
-# Brug denne indstilling til at bortfiltrere mail til listen, baseret
-# p&aring; indholdet af et eller flere felter i brevhovedet. Her skal du
-# skrive regexp-udtryk (regular expressions), et pr. linie, som
-# sammenlignes med det aktuelle felt. Sammenligningen skelner ikke
-# imellem store og sm&aring; bogstaver. Linier der begynder med '#'
-# sammenlignes ikke.
+# Use this option to prohibit posts according to specific header values.
+# The target value is a regular-expression for matching against the
+# specified header.  The match is done disregarding letter case.  Lines
+# beginning with '#' are ignored as comments.
 # 
-# For eksempel: udtrykket to: .*@public.com fort&aelig;ller at al mail
-# som indeholder '@public.com' i To: feltet, skal holdes tilbage for
-# godkendelse.
+# For example:to: .*@public.com  says to hold all postings with a To:
+# mail header containing '@public.com' anywhere among the addresses.
 # 
-# Bem&aelig;rk: tomme tegn i starten af regexp-udtrykket fjernes. Dette
-# kan omg&aring;s p&aring; flere m&aring;der, f.eks. ved at bruge
-# escape-tegn eller parenteser.
+# Note that leading whitespace is trimmed from the regexp.  This can be
+# circumvented in a number of ways, e.g. by escaping or bracketing it.
 bounce_matching_headers = """# Lines that *start* with a '#' are comments.
 to: friend@public.com
 message-id: relay.comanche.denmark.eu
@@ -833,415 +830,439 @@ from: .*@uplinkpro.com"""
 
 ## Bounce options
 #
-# Disse regler bestemmer hvordan automatisk behandling af returmails
-# skal foreg&aring;. Her er en oversigt over hvordan det virker.
-# 
-# <p>N&aring;r Mailman modtager en returmail, bliver to ting
-# fors&oslash;gt tolket. Den ene er e-mailadressen for medlemmet som
-# egentlig skulle modtage e-mailen, og den anden er &aring;rsagen til
-# problemet. &Aring;rsagen tolkes til at v&aelig;re <em>alvorlig</em>
-# eller <em>harml&oslash;s</em> alt efter om &aring;rsagen er af kritisk
-# eller af mindre alvorlig art. Hvis der er tvivl, tolkes &aring;rsagen
-# som alvorlig.
-# 
-# <p>Hvis ingen e-mailadresse kan hentes ud af meddelelsen, bliver den
-# normalt afvist. Ellers vil medlemmet som har e-mailadressen f&aring;
-# tildelt et <em>returtal</em>, og hver gang der kommer en
-# returmeddelelse vil tallet &oslash;ges. Alvorlige &aring;rsager
-# f&oslash;rer til at tallet &oslash;ges med 1, harml&oslash;se
-# &aring;rsager f&oslash;rer til at det &oslash;ges med 0.5. Dette sker
-# kun &eacute;n gang pr. dag, s&aring; selv om der kommer 10 alvorlige
-# returmails fra et medlem p&aring; &eacute;n dag, vil tallet kun
-# &oslash;ges med 1.
-# 
-# <p>N&aring;r returtallet for et medlem n&aring;r en vis <a
-# href="?VARHELP=bounce/bounce_score_threshold">gr&aelig;nse</a>,
-# stoppes levering til medlemmet. Dermed vil medlemmet ikke modtage
-# e-mail fra listen f&oslash;r levering s&aelig;ttes til igen. Medlemmet
-# vil med j&aelig;vne mellemrum modtage meddelelse om at dette er sket,
-# og hvad han/hun skal g&oslash;re for at f&aring; e-mail fra listen
-# igen.
-# 
-# <p>Du kan bestemme <a
-# href="?VARHELP=bounce/bounce_you_are_disabled_warnings">hvor mange
-# advarsler</a> medlemmet skal have og <a
-# href="?VARHELP=bounce/bounce_you_are_disabled_warnings_interval">hvor
-# ofte</a> han/hun skal modtage s&aring;danne advarsler.
-# 
-# <p>Der er en vigtig indstilling mere: efter en vis tid -- hvor ingen
-# returmeddelelser dukker op -- regnes returinformation for at
-# v&aelig;re <a
-# href="?VARHELP=bounce/bounce_info_stale_after">for&aelig;ldet</a> og
-# stoppes. Ved at justere denne v&aelig;rdi, og s&aelig;tte en
-# gr&aelig;nse for returantallet, kan du bestemme hvor lang tid der skal
-# g&aring; f&oslash;r levering til et medlem stoppes. Begge disse
-# v&aelig;rdier b&oslash;r tilpasses efter hvor ofte og hvor meget
-# e-mail der sendes til din liste.
-
-# Ved at sætte denne værdi til Nej, slår du al automatisk tolkning af
-# returmeddelelser for denne liste fra. Bemærk at hvis meddelelser
-# afvises vil listeadministratoren ikke blive forstyrret med dem.
-#
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# These policies control the automatic bounce processing system in
+# Mailman.  Here's an overview of how it works.
+# 
+# <p>When a bounce is received, Mailman tries to extract two pieces of
+# information from the message: the address of the member the message
+# was intended for, and the severity of the problem causing the bounce.
+# The severity can be either <em>hard</em> or <em>soft</em> meaning
+# either a fatal error occurred, or a transient error occurred.  When in
+# doubt, a hard severity is used.
+# 
+# <p>If no member address can be extracted from the bounce, then the
+# bounce is usually discarded.  Otherwise, each member is assigned a
+# <em>bounce score</em> and every time we encounter a bounce from this
+# member we increment the score.  Hard bounces increment by 1 while soft
+# bounces increment by 0.5.  We only increment the bounce score once per
+# day, so even if we receive ten hard bounces from a member per day,
+# their score will increase by only 1 for that day.
+# 
+# <p>When a member's bounce score is greater than the <a
+# href="?VARHELP=bounce/bounce_score_threshold">bounce score
+# threshold</a>, the subscription is disabled.  Once disabled, the
+# member will not receive any postings from the list until their
+# membership is explicitly re-enabled (either by the list administrator
+# or the user).  However, they will receive occasional reminders that
+# their membership has been disabled, and these reminders will include
+# information about how to re-enable their membership.
+# 
+# <p>You can control both the <a
+# href="?VARHELP=bounce/bounce_you_are_disabled_warnings">number of
+# reminders</a> the member will receive and the <a
+# href="?VARHELP=bounce/bounce_you_are_disabled_warnings_interval"
+# >frequency</a> with which these reminders are sent.
+# 
+# <p>There is one other important configuration variable; after a
+# certain period of time -- during which no bounces from the member are
+# received -- the bounce information is <a
+# href="?VARHELP=bounce/bounce_info_stale_after">considered stale</a>
+# and discarded.  Thus by adjusting this value, and the score threshold,
+# you can control how quickly bouncing members are disabled.  You should
+# tune both of these to the frequency and traffic volume of your list.
+
+# By setting this value to No, you disable all automatic bounce
+# processing for this list, however bounce messages will still be
+# discarded so that the list administrator isn't inundated with them.
+#
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 bounce_processing = 1
 
-# Hvert medlem tildeles et returtal, og hver gang der kommer en
-# returmeddelelse vil dette tal &oslash;ges.  Alvorlige (&aring;rsager
-# f&oslash;rer til at det &oslash;ges med 1, mens harml&oslash;se
-# &aring;rsager f&oslash;rer til at det &oslash;ges med 0.5. Dette sker
-# kun &eacute;n gang pr. dag, s&aring; selv om der kommer 10 alvorlige
-# returmails fra et medlem p&aring; &eacute;n dag, vil tallet kun
-# &oslash;ges med 1.
-# 
-# Her s&aelig;ttes den &oslash;vre gr&aelig;nse for medlemmets returtal
-# Overskrides denne gr&aelig;nse stoppes levering automatisk, men
-# medlemmet bliver ikke fjernet fra listen.
+# Each subscriber is assigned a bounce score, as a floating point
+# number.  Whenever Mailman receives a bounce from a list member, that
+# member's score is incremented.  Hard bounces (fatal errors) increase
+# the score by 1, while soft bounces (temporary errors) increase the
+# score by 0.5.  Only one bounce per day counts against a member's
+# score, so even if 10 bounces are received for a member on the same
+# day, their score will increase by just 1.
+# 
+# This variable describes the upper limit for a member's bounce score,
+# above which they are automatically disabled, but not removed from the
+# mailing list.
 bounce_score_threshold = 5.0
 
-# Antal dage f&oslash;r returinformation stoppes hvis der ikke dukker
-# flere returmails op. Dette tal skal v&aelig;re et heltal.
+# The number of days after which a member's bounce information is
+# discarded, if no new bounces have been received in the interim.  This
+# value must be an integer.
 bounce_info_stale_after = 7
 
-# Hvor mange Levering til dig er stoppet advarsler der skal sendes til
-# et medlem f&oslash;r medlemmet frameldes listen. S&aelig;t denne værdi
-# til 0 for at fjerne et medlem fra listen straks, hvis der kommer
-# returmails fra medlemmets e-mailadresse. Dette tal skal være et
-# heltal.
+# How many Your Membership Is Disabled warnings a disabled member should
+# get before their address is removed from the mailing list.  Set to 0
+# to immediately remove an address from the list once their bounce score
+# exceeds the threshold.  This value must be an integer.
 bounce_you_are_disabled_warnings = 3
 
-# Antal dage imellem hver gang en Levering til dig er stoppet advarsel
-# skal sendes ud. Dette tal skal være et heltal.
+# The number of days between sending the Your Membership Is Disabled
+# warnings.  This value must be an integer.
 bounce_you_are_disabled_warnings_interval = 7
 
-# Mailmans automatiske returmailh&aring;ndtering er meget robust, men
-# det er alligevel umuligt at genkende alle typer returmails der kommer.
-# Du b&oslash;r v&aelig;lge Ja her, af to grunde: 1) Hvis det virkelig
-# er en permanent returmail fra et medlem af listen, b&oslash;r du
-# antagelig manuelt afmelde medlemmet fra listen, og 2) du vil
-# m&aring;ske sende en meddelelse til udviklerne af Mailman s&aring;dan
-# at returmails automatisk genkendes af Mailman i senere versioner. Hvis
-# du ikke vil g&oslash;re nogen af delene, s&aelig;ttes denne
-# indstilling til Nej. S&aring; vil alle returmails afvises automatisk
-# uden videre behandling. Bem&aelig;rk: Denne indstilling vil ogs&aring;
-# indvirke p&aring; al e-mail der sendes til listens -admin adresse. Den
-# adresse er for&aelig;ldet og udg&aring;et, men måske vil nogen
-# alligevel fortsat sende e-mail til den. Hvis nogen g&oslash;r det, og
-# du har sat denne indstilling til Nej, vil disse mails ogs&aring; blive
-# afvist. M&aring;ske vil du ogs&aring; ops&aelig;tte et automatisk svar
-# p&aring; e-mail sendt til -owner og -admin adresserne.
-#
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# While Mailman's bounce detector is fairly robust, it's impossible to
+# detect every bounce format in the world.  You should keep this
+# variable set to Yes for two reasons: 1) If this really is a permanent
+# bounce from one of your members, you should probably manually remove
+# them from your list, and 2) you might want to send the message on to
+# the Mailman developers so that this new format can be added to its
+# known set.
+# 
+# If you really can't be bothered, then set this variable to No and all
+# non-detected bounces will be discarded without further processing.
+# 
+# Note: This setting will also affect all messages sent to your list's
+# -admin address.  This address is deprecated and should never be used,
+# but some people may still send mail to this address.  If this happens,
+# and this variable is set to No those messages too will get discarded.
+# You may want to set up an autoresponse message for email to the -owner
+# and -admin address.
+#
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 bounce_unrecognized_goes_to_list_owner = 1
 
-# Ved at sætte denne til Nej, fravælges beskeden der normalt sendes til
-# ejer(e) af listen, når levering af e-mail til et medlem stoppes på
-# grund af for mange returmails. Der vil til gengæld altid blive forsøgt
-# afsendt en e-mail med besked til medlemmet.
+# By setting this value to No, you turn off notification messages that
+# are normally sent to the list owners when a member's delivery is
+# disabled due to excessive bounces. An attempt to notify the member
+# will always be made.
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 bounce_notify_owner_on_disable = 1
 
-# Ved at sætte denne til Nej, fravælges beskeden der normalt sendes til
-# ejer(e) af listen, når et medlem frameldes listen på grund af for
-# mange returmails. Der vil til gengæld altid blive forsøgt afsendt en
-# e-mail med besked til medlemmet.
+# By setting this value to No, you turn off notification messages that
+# are normally sent to the list owners when a member is unsubscribed due
+# to excessive bounces.  An attempt to notify the member will always be
+# made.
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 bounce_notify_owner_on_removal = 1
 
 ## Archive options
 #
-# Regler for arkivering
+# List traffic archival policies.
 
-# Arkiver e-mail i et arkiv?
+# Archive messages?
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 archive = 1
 
-# Skal arkivet v&aelig;re offentligt eller privat?
+# Is archive file source for public or private archival?
 #
-# gyldige værdier:
-#    0 = "Offentligt"
-#    1 = "Privat"
+# legal values are:
+#    0 = "public"
+#    1 = "private"
 archive_private = 0
 
-# Hvor ofte skal arkivet deles op?
+# How often should a new archive volume be started?
 #
-# gyldige værdier:
-#    0 = "&Aring;rlig"
-#    1 = "M&aring;nedlig"
-#    2 = "Kvartalsvis"
-#    3 = "Ugentlig"
-#    4 = "Daglig"
+# legal values are:
+#    0 = "Yearly"
+#    1 = "Monthly"
+#    2 = "Quarterly"
+#    3 = "Weekly"
+#    4 = "Daily"
 archive_volume_frequency = 0
 
 ## Gateway options
 #
-# E-mail-Til-Nyhedsgruppe og Nyhedsgruppe-Til-E-mail tjeneste.
+# Mail-to-News and News-to-Mail gateway services.
 
-# Nyhedsgruppe-tjeneste er ikke en del af Mailman. Du skal have adgang
-# til en eksisterende NNTP tjeneste, og maskinen som denne mailliste
-# k&oslash;rer p&aring; skal have adgang til at hente og afsende
-# meddelelser til NNTP tjenesten.
+# This value may be either the name of your news server, or optionally
+# of the format name:port, where port is a port number.
+# 
+# The news server is not part of Mailman proper.  You have to already
+# have access to an NNTP server, and that NNTP server must recognize the
+# machine this mailing list runs on as a machine capable of reading and
+# posting news.
 nntp_host = ''
 
-# Navn p&aring; nyhedsgruppe der skal sendes til og/eller fra.
+# The name of the Usenet group to gateway to and/or from.
 linked_newsgroup = ''
 
-# Skal nye meddelelser til denne liste sendes til nyhedsgruppen?
+# Should new posts to the mailing list be sent to the newsgroup?
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 gateway_to_news = 0
 
-# Skal nye meddelelser til nyhedsgruppen sendes til denne mailliste?
+# Should new posts to the newsgroup be sent to the mailing list?
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 gateway_to_mail = 0
 
-# Denne indstilling fort&aelig;ller Mailman hvilken slags
-# moderationsregler nyhedsgruppen har og hvordan de koordineres med
-# maillistens moderationsregler. Dette g&aelig;lder kun nyhedgrupper du
-# overfører meddelelser til, s&aring; hvis du kun overf&oslash;rer fra
-# en nyhedsgruppe, eller nyhedsgruppen du overf&oslash;rer til ikke er
-# modereret, s&aelig;ttes indstillingen til Ingen.
-# 
-# Hvis nyhedsgruppen er modereret, kan du s&aelig;tte maillisten til at
-# v&aelig;re moderationsadressen for nyhedsgruppen. Ved at vælge
-# Modereret, vil en ekstra meddelelse holdes tilbage i
-# godkendelsesprocessen. Al mail sendt til maillisten skal godkendes
-# f&oslash;r den sendes til nyhedsgruppen, eller til medlemmerne af
-# listen.
-# 
-# Vær opm&aelig;rksom p&aring; at hvis brevhovedet i mailen har et
-# Approved: felt med listens administrative adgangskode, vil denne regel
-# ikke blive benyttet. På den m&aring;de kan priviligerede afsendere
-# sende mail direkte til listen og nyhedsgruppen.
-# 
-# Hvis nyhedsgruppen er modereret, men du alligevel vil have en
-# &aring;ben liste, b&oslash;r du vælge Åben liste, modereret
-# nyhedsgruppe. S&aring; vil de s&aelig;dvanlige mekanismer for
-# moderation blive benyttet i Mailman, men alle meddelelser der sendes
-# til Usenet vil f&aring; et Approved felt i brevhovedet.
-#
-# gyldige værdier:
-#    0 = "Ingen"
-#    1 = "Åben liste, modereret nyhedsgruppe"
-#    2 = "Modereret"
+# This setting determines the moderation policy of the newsgroup and its
+# interaction with the moderation policy of the mailing list.  This only
+# applies to the newsgroup that you are gatewaying to, so if you are
+# only gatewaying from Usenet, or the newsgroup you are gatewaying to is
+# not moderated, set this option to None.
+# 
+# If the newsgroup is moderated, you can set this mailing list up to be
+# the moderation address for the newsgroup.  By selecting Moderated, an
+# additional posting hold will be placed in the approval process.  All
+# messages posted to the mailing list will have to be approved before
+# being sent on to the newsgroup, or to the mailing list membership.
+# 
+# Note that if the message has an Approved header with the list's
+# administrative password in it, this hold test will be bypassed,
+# allowing privileged posters to send messages directly to the list and
+# the newsgroup.
+# 
+# Finally, if the newsgroup is moderated, but you want to have an open
+# posting policy anyway, you should select Open list, moderated group.
+# The effect of this is to use the normal Mailman moderation facilities,
+# but to add an Approved header to all messages that are gatewayed to
+# Usenet.
+#
+# legal values are:
+#    0 = "None"
+#    1 = "Open list, moderated group"
+#    2 = "Moderated"
 news_moderation = 0
 
-# Mailman tilføjer normalt en tekst du selv kan tilrette (emne prefix)
-# foran emnefeltet i mail som sendes til listen, og normalt sker dette
-# også for mail som sendes videre til Usenet. Du kan sætte denne
-# indstilling til Nej hvis du ikke ønsker emne prefix tilføjet til mail
-# som sendes til Usenet. Sættes emne prefix for listen til off, vil
-# videresendte meddelelser heller ikke få prefix tilføjet.
+# Mailman prefixes Subject: headers with text you can customize and
+# normally, this prefix shows up in messages gatewayed to Usenet.  You
+# can set this option to No to disable the prefix on gated messages.  Of
+# course, if you turn off normal Subject: prefixes, they won't be
+# prefixed for gated messages either.
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 news_prefix_subject_too = 1
 
 ## Autoreply options
 #
-# Indstillinger for automatiske svar.<p>
+# Auto-responder characteristics.<p>
 # 
-# I tekstboksene nedenfor kan du bruge følgende variabler: (skriv:
-# %(&lt;variabelnavn&gt;)s ) for at indsætte ønsket information: <p><ul>
-# <li><b>listname</b> - <em>navnet p&aring; listen</em>
-# <li><b>listurl</b> - <em>URL til listens webside</em>
-# <li><b>requestemail</b> - <em>listens -request e-mailadresse</em>
-# <li><b>owneremail</b> - <em>listens -owner e-mailadresse</em> </ul>
+# In the text fields below, string interpolation is performed with the
+# following key/value substitutions: <p><ul> <li><b>listname</b> -
+# <em>gets the name of the mailing list</em> <li><b>listurl</b> -
+# <em>gets the list's listinfo URL</em> <li><b>requestemail</b> -
+# <em>gets the list's -request address</em> <li><b>owneremail</b> -
+# <em>gets the list's -owner address</em> </ul>
 # 
-# <p>Du kan enten skrive teksten direkte i tekstboksene, eller du kan
-# angive navnet p&aring; en fil som indeholder teksten. Denne fil vil
-# s&aring; blive indl&aelig;st i tekstboksen, fra dit lokale filsystem.
+# <p>For each text field, you can either enter the text directly into
+# the text box, or you can specify a file on your local system to upload
+# as the text.
 
-# Skal Mailman sende et automatisk svar til dem der sender e-mail til
-# listen?
+# Should Mailman send an auto-response to mailing list posters?
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 autorespond_postings = 0
 
-# Automatisk svar der skal sendes.
+# Auto-response text to send to mailing list posters.
 autoresponse_postings_text = ''
 
-# Skal Mailman sende et automatisk svar p&aring; e-mail der sendes til
-# -owner adressen?
+# Should Mailman send an auto-response to emails sent to the -owner
+# address?
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 autorespond_admin = 0
 
-# Automatisk svar p&aring; e-mail til -owner adressen.
+# Auto-response text to send to -owner emails.
 autoresponse_admin_text = ''
 
-# Skal Mailman sende et automatisk svar p&aring; e-mail der sendes til
-# -request adressen? Hvis du v&aelig;lger ja, kan du ogs&aring;
-# v&aelig;lge om e-mailen der blev sendt til -request adressen skal
-# medtages i det automatiske svar.
+# Should Mailman send an auto-response to emails sent to the -request
+# address?  If you choose yes, decide whether you want Mailman to
+# discard the original email, or forward it on to the system as a normal
+# mail command.
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja, men uden den originale e-mail"
-#    2 = "Ja, og medtag den originale e-mail"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes, w/discard"
+#    2 = "Yes, w/forward"
 autorespond_requests = 0
 
-# Automatisk svar p&aring; e-mail til -request adressen.
+# Auto-response text to send to -request emails.
 autoresponse_request_text = ''
 
-# Antal dage imellem automatisk svar p&aring; e-mail, fra samme
-# afsender, til listen eller til -request/-owner adresserne. S&aelig;t
-# denne v&aelig;rdi til 0 (eller et negativt tal) for at sende
-# automatisk svar hver gang.
+# Number of days between auto-responses to either the mailing list or
+# -request/-owner address from the same poster.  Set to zero (or
+# negative) for no grace period (i.e. auto-respond to every message).
 autoresponse_graceperiod = 90
 
 ## Contentfilter options
 #
-# Regler for indhold i e-mail sendt til listen.
-# 
-# <p>Filtrering af indhold fungerer således: når listen modtager en
-# e-mail og du har beskyttelse med filtrering af indhold aktiveret,
-# sammenlignes først eventuelle vedh&aelig;ftninger med <a
-# href="?VARHELP=contentfilter/filter_mime_types">MIME filtrene</a>.
-# Hvis en vedh&aelig;ftning passer med et af disse filtre, bliver
-# vedh&aelig;ftningen fjernet.
-# 
-# <p>Derefter sammenlignes eventuelle vedh&aelig;ftninger med <a
-# href="?VARHELP=contentfilter/pass_mime_types">gyldige MIME typer</a>,
-# hvis nogen er defineret. Alle vedh&aelig;ftninger som ikke stemmer
-# overens med de angivne MIME typer, bliver fjernet.
-# 
-# <p>Efter filtreringen vil alle tomme <tt>multipart</tt>
-# vedh&aelig;ftninger v&aelig;re fjernet. Hvis selve meddelelsen er helt
-# tom efter denne filtrering, vil meddelelsen blive afvist. Derefter vil
-# enhver <tt>multipart/alternative</tt> vedh&aelig;ftning blive
-# erstattet af den første alternative som ikke er tom.
-# 
-# <p>Til sidst vil alle <tt>text/html</tt> vedh&aelig;ftninger som måtte
-# v&aelig;re tilbage i meddelelsen blive konverteret til
-# <tt>text/plain</tt> hvis <a
-# href="?VARHELP=contentfilter/convert_html_to_plaintext">konverter til
-# ren tekst</a> er sat til og serveren er konfigureret til at tillade
-# sådanne konverteringer.
-
-# Skal Mailman filtrere indhold i e-mail sendt til listen som angivet
-# nedenfor?
-#
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# Policies concerning the content of list traffic.
+# 
+# <p>Content filtering works like this: when a message is received by
+# the list and you have enabled content filtering, the individual
+# attachments are first compared to the <a
+# href="?VARHELP=contentfilter/filter_mime_types">filter types</a>.  If
+# the attachment type matches an entry in the filter types, it is
+# discarded.
+# 
+# <p>Then, if there are <a
+# href="?VARHELP=contentfilter/pass_mime_types">pass types</a> defined,
+# any attachment type that does <em>not</em> match a pass type is also
+# discarded.  If there are no pass types defined, this check is skipped.
+# 
+# <p>After this initial filtering, any <tt>multipart</tt> attachments
+# that are empty are removed.  If the outer message is left empty after
+# this filtering, then the whole message is discarded.
+# 
+# <p> Then, each <tt>multipart/alternative</tt> section will be replaced
+# by just the first alternative that is non-empty after filtering if <a
+# href="?VARHELP=contentfilter/collapse_alternatives"
+# >collapse_alternatives</a> is enabled.
+# 
+# <p>Finally, any <tt>text/html</tt> parts that are left in the message
+# may be converted to <tt>text/plain</tt> if <a
+# href="?VARHELP=contentfilter/convert_html_to_plaintext"
+# >convert_html_to_plaintext</a> is enabled and the site is configured
+# to allow these conversions.
+
+# Should Mailman filter the content of list traffic according to the
+# settings below?
+#
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 filter_content = 0
 
-# Brug denne indstilling til at fjerne vedh&aelig;ftninger der passer
-# til MIME typer. Hver linie skal her indeholde navnet på en MIME
-# type/subtype, f.eks. image/gif. Hvis du ønsker at fjerne alle
-# vedh&aelig;ftninger som har en given hoved MIME type, kan du undlade
-# at angive subtype, f.eks. image.
+# Use this option to remove each message attachment that matches one of
+# these content types.  Each line should contain a string naming a MIME
+# type/subtype, e.g. image/gif.  Leave off the subtype to remove all
+# parts with a matching major content type, e.g. image.
 # 
-# Tomme linier medtages ikke.
+# Blank lines are ignored.
 # 
-# Se også gyldige MIME typer for whitelist af MIME typer.
+# See also <a href="?VARHELP=contentfilter/pass_mime_types"
+# >pass_mime_types for a content type whitelist.
 filter_mime_types = ''
 
-# Brug denne indstilling for at definere hvilke MIME typer der skal være
-# tilladt. Krav og format for filtrering er identisk med MIME filtre.
+# Use this option to remove each message attachment that does not have a
+# matching content type.  Requirements and formats are exactly like <a
+# href="?VARHELP=contentfilter/filter_mime_types" >filter_mime_types.
 # 
-# Bem&aelig;rk: hvis du lægger noget ind her, men ikke angiver
-# multipart, vil ingen e-mail med vedh&aelig;ftninger blive medtaget.
+# Note: if you add entries to this list but don't add multipart to this
+# list, any messages with attachments will be rejected by the pass
+# filter.
 pass_mime_types = """multipart/mixed
 multipart/alternative
 text/plain"""
 
-# Skal Mailman konvertere text/html dele til ren tekst? Denne
-# konvertering vil finde sted efter at MIME filteret har fjernet de
-# uønskede dele.
+# Remove message attachments that have a matching filename extension.
+filter_filename_extensions = """exe
+bat
+cmd
+com
+pif
+scr
+vbs
+cpl"""
+
+# Remove message attachments that don't have a matching filename
+# extension.  Leave this field blank to skip this filter test.
+pass_filename_extensions = ''
+
+# Should Mailman collapse multipart/alternative to its first part
+# content?
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
+collapse_alternatives = True
+
+# Should Mailman convert text/html parts to plain text?  This conversion
+# happens after MIME attachments have been stripped.
+#
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 convert_html_to_plaintext = 1
 
-# Her bestemmer du hvad der skal ske, når en meddelelse filtreres fra af
-# et filter, altså hvis vedh&aelig;ftningen filtreres fra af MIME
-# filteret, eller en vedh&aelig;ftning ikke har en af de gyldige MIME
-# typer, eller meddelelsen ender med at være tom efter filtrering.
-# 
-# Bemærk at det du vælger her ikke vil ske hvis en meddelelse stadig
-# indeholder noget efter filtrering. Så vil meddelelsen altid blive
-# sendt videre til listen.
-# 
-# Når meddelelsen afvises, skrives Message-ID for den afviste meddelelse
-# til loggen. Når meddelelsen sendes retur eller videresendes til
-# listens ejer, vil en begrundelse altid blive inkluderet i den
-# returmail der sendes til afsenderen. Når meddelelserne skal bevares,
-# gemmes de i et specielt køkatalog på disken, sådan at
-# serveradministrator kan se (og måske gøre noget med) dem, men bliver
-# ellers fjernet. Dette sidste valg er kun tilgængeligt hvis
-# serveradministrator har tilladt det.
-#
-# gyldige værdier:
-#    0 = "Slet"
-#    1 = "Afvis"
-#    2 = "Videresend til Listens Ejer"
-#    3 = "Bevar"
+# One of these actions is taken when the message matches one of the
+# content filtering rules, meaning, the top-level content type matches
+# one of the <a href="?VARHELP=contentfilter/filter_mime_types"
+# >filter_mime_types, or the top-level content type does not match one
+# of the <a href="?VARHELP=contentfilter/pass_mime_types"
+# >pass_mime_types, or if after filtering the subparts of the message,
+# the message ends up empty.
+# 
+# Note this action is not taken if after filtering the message still
+# contains content.  In that case the message is always forwarded on to
+# the list membership.
+# 
+# When messages are discarded, a log entry is written containing the
+# Message-ID of the discarded message.  When messages are rejected or
+# forwarded to the list owner, a reason for the rejection is included in
+# the bounce message to the original author.  When messages are
+# preserved, they are saved in a special queue directory on disk for the
+# site administrator to view (and possibly rescue) but otherwise
+# discarded.  This last option is only available if enabled by the site
+# administrator.
+#
+# legal values are:
+#    0 = "Discard"
+#    1 = "Reject"
+#    2 = "Forward to List Owner"
+#    3 = "Preserve"
 filter_action = 0
 
 ## Topics options
 #
-# Emneord for listen
-
-# Emnefilteret kategoriserer hver e-mail som kommer til listen, efter de
-# regexp-udtryk du skriver nedenfor. Hvis felterne Subject: eller
-# Keywords: i brevhovedet i en mail stemmer overens med et af disse
-# udtryk, bliver mailen placeret under det p&aring;g&aelig;ldende emne.
-# Hvert medlem af listen kan vælge kun at modtage mail der passer til de
-# &oslash;nskede emner. E-mail som ikke h&oslash;rer under noget emne,
-# bliver ikke leveret.
-# 
-# Bem&aeligrk: Dette fungerer kun i normal-modus, ikke i
-# sammendrag-modus.
-# 
-# Indholdet i meddelelsen kan ogs&aring; unders&oslash;ges for Subject:
-# og Keyword: felter, alt efter hvad indstillingen
-# topics_bodylines_limit er sat til.
+# List topic keywords
+
+# The topic filter categorizes each incoming email message according to
+# <a href="http://www.python.org/doc/current/lib/module-re.html">regular
+# expression filters you specify below.  If the message's Subject: or
+# Keywords: header contains a match against a topic filter, the message
+# is logically placed into a topic bucket.  Each user can then choose to
+# only receive messages from the mailing list for a particular topic
+# bucket (or buckets).  Any message not categorized in a topic bucket
+# registered with the user is not delivered to the list.
+# 
+# Note that this feature only works with regular delivery, not digest
+# delivery.
+# 
+# The body of the message can also be optionally scanned for Subject:
+# and Keywords: headers, as specified by the <a
+# href="?VARHELP=topics/topics_bodylines_limit">topics_bodylines_limit
+# configuration variable.
 #
-# gyldige værdier:
-#    0 = "Ikke tilgængeligt"
-#    1 = "Tilgængeligt"
+# legal values are:
+#    0 = "Disabled"
+#    1 = "Enabled"
 topics_enabled = 0
 
-# Her angiver du hvor mange linier af mailens indhold emnefilteret skal
-# gennems&oslash;ge. En s&oslash;gning stopper n&aring;r det antal
-# linier er gennems&oslash;gt, eller n&aring;r den m&oslash;der en linie
-# som ikke ligner et brevhoved-felt. S&aelig;ttes denne v&aelig;rdi til
-# nul (0), vil ingen linier i indholdet blive unders&oslash;gt (dvs. kun
-# Keywords: og Subject: i brevhovedet unders&oslash;ges). S&aelig;ttes
-# denne v&aelig;rdi til et negativt tal, vil alle linier blive
-# unders&oslash;gt frem til den f&oslash;rste linie som ikke ligner et
-# brevhoved-felt.
+# The topic matcher will scan this many lines of the message body
+# looking for topic keyword matches.  Body scanning stops when either
+# this many lines have been looked at, or a non-header-like body line is
+# encountered.  By setting this value to zero, no body lines will be
+# scanned (i.e. only the Keywords: and Subject: headers will be
+# scanned).  By setting this value to a negative number, then all body
+# lines will be scanned until a non-header-like line is encountered.
+# 
 topics_bodylines_limit = 5
 
-# Hvert emneord er faktisk et regexp-udtryk, der sammenlignes med dele
-# af mailen, nemlig felterne Keywords: og Subject: i brevhovedet.
-# Bem&aelig;rk at de f&oslash;rste linier i mailens indhold ogs&aring;
-# kan best&aring; af s&aring;danne "felter", og de kan dermed ogs&aring;
-# blive unders&oslash;gt.
+# Each topic keyword is actually a regular expression, which is matched
+# against certain parts of a mail message, specifically the Keywords:
+# and Subject: message headers. Note that the first few lines of the
+# body of the message can also contain a Keywords: and Subject: "header"
+# on which matching is also performed.
 topics = []
 
diff --git a/mailman/assilissat.members b/mailman/assilissat.members
index d717ed3..7b0e709 100644
--- a/mailman/assilissat.members
+++ b/mailman/assilissat.members
@@ -1,19 +1,13 @@
-a_funch@post12.tele.dk
 arnaaraq_85@hotmail.com
-assilissat@film.dk
 elsenuna@greennet.gl
 gant@cfk.hum.aau.dk
-georg@knr.gl
 imondrup@hotmail.com
 inuk@jones.dk
 inukmedia@greennet.gl
 jacobsenmiki@hotmail.com
 jessie@greennet.gl
-jrs@asiaq.gl
-kaneq@hotmail.com
 knudps@knr.gl
 lucas@greennet.gl
-mazz@ofir.dk
 olekrist@greennet.gl
 polarjan@hotmail.com
 puilasoq@hotmail.com
diff --git a/mailman/assilissat.py b/mailman/assilissat.py
index 2c9b318..d1dba4b 100644
--- a/mailman/assilissat.py
+++ b/mailman/assilissat.py
@@ -1,382 +1,369 @@
-## Indstillinger for maillisten "assilissat"  -*- python -*-
-## Dato: Sun Dec 11 16:35:47 2005
+# -*- python -*-
+# -*- coding: us-ascii -*-
+## "assilissat" mailing list configuration settings
+## captured on Tue Mar 20 08:51:57 2007
 
 ## General options
 #
-# Grundlæggende egenskaber for listen, herunder en beskrivelse af
-# listen. 
-
-# Du kan f.eks. stave navnet med stort forbogstav eller ændre andre
-# bogstaver til store, s&aring; navnet bliver udtalt rigtigt eller at
-# forkortelser fremhæves. Bemærk at dette navn bruges i e-maillistens
-# adresse (f.eks. i bekræftelser ved tilmeldinger), s&aring; navnet kan
-# ikke ændres p&aring; nogen anden m&aring;de. (e-mailadresser er ikke
-# f&oslash;lsomme for store eller sm&aring; bogstaver, men de er
-# f&oslash;lsomme for n&aelig;sten alt andet :-)
+# Fundamental list characteristics, including descriptive info and basic
+# behaviors.
+
+# The capitalization of this name can be changed to make it presentable
+# in polite company as a proper noun, or to make an acronym part all
+# upper case, etc.  However, the name will be advertised as the email
+# address (e.g., in subscribe confirmation notices), so it should not be
+# otherwise altered.  (Email addresses are not case sensitive, but they
+# are sensitive to almost everything else :-)
 real_name = 'Assilissat'
 
-# Der er to roller forbundet med hver mailliste. Listeadministratorerne
-# er dem der som sidste instans har kontrol over alle indstillingerne
-# for maillisten. De kan &aelig;ndre alle indstillinger der er
-# tilg&aelig;ngelige via disse administrative websider.
-# 
-# Listemoderatorerne har begrænset adgang; de kan ikke ændre
-# indstillinger for e-maillisten, men de kan tage sig af anmodninger i
-# forbindelse med listen, f.eks. anmodning om medlemskab, eller
-# godkende/afvise meddelelser der skal godkendes for at kunne udsendes
-# til listen. Listeadministratorerne kan ogs&aring; udf&oslash;re disse
-# opgaver.
-# 
-# For at aktivere muligheden for at have listemoderatorer, og p&aring;
-# den m&aring;de fordele arbejdsopgaverne i forbindelse med listen, skal
-# du anf&oslash;re din egen moderatoradgangskode, og angive
-# e-mailadresser for den/dem som skal v&aelig;re listemoderator(er).
-# Bemærk at i tekstboksene nedenfor skal du skrive e-mailadresser for
-# listeadministratorer.
+# There are two ownership roles associated with each mailing list.  The
+# list administrators are the people who have ultimate control over all
+# parameters of this mailing list.  They are able to change any list
+# configuration variable available through these administration web
+# pages.
+# 
+# The list moderators have more limited permissions; they are not able
+# to change any list configuration variable, but they are allowed to
+# tend to pending administration requests, including approving or
+# rejecting held subscription requests, and disposing of held postings.
+# Of course, the list administrators can also tend to pending requests.
+# 
+# In order to split the list ownership duties into administrators and
+# moderators, you must set a separate moderator password, and also
+# provide the email addresses of the list moderators.  Note that the
+# field you are changing here specifies the list administrators.
 owner = ['inuk@jones.dk']
 
-# Der er to ejer-roller forbundet med hver mailliste.
-# Listeadministratorerne er dem der har den endelige kontrol over alle
-# indstillingerne for e-mallisten. De kan &aelig;ndre alle indstillinger
-# der er tilgængelige via disse administrative websider.
-# 
-# Listemoderatorerne har begr&aelig;nset adgang; de kan ikke &aelig;ndre
-# indstillinger for e-maillisten, men de kan tage sig af anmodninger
-# ang&aring;ende listen, f.eks. anmodning om medlemskab, eller
-# godkende/afvise meddelelser der skal godkendes for at kunne udsendes
-# p&aring; listen. Listeadministratorerne kan selvsagt ogs&aring;
-# udf&oslash;re disse opgaver.
-# 
-# For at aktivere muligheden for at have listemoderatorer, og p&aring;
-# den m&aring;de fordele arbejdsopgaverne i forbindelse med listen, skal
-# du anf&oslash;re din egen moderatoradgangskode, og indtaste
-# e-mailadresser for den/dem der skal v&aelig;re listemoderatore(r).
-# Bemærk, at i tekstboksene nedenfor skal du skrive listemoderator
-# e-mailadresse(r).
+# There are two ownership roles associated with each mailing list.  The
+# list administrators are the people who have ultimate control over all
+# parameters of this mailing list.  They are able to change any list
+# configuration variable available through these administration web
+# pages.
+# 
+# The list moderators have more limited permissions; they are not able
+# to change any list configuration variable, but they are allowed to
+# tend to pending administration requests, including approving or
+# rejecting held subscription requests, and disposing of held postings.
+# Of course, the list administrators can also tend to pending requests.
+# 
+# In order to split the list ownership duties into administrators and
+# moderators, you must set a separate moderator password, and also
+# provide the email addresses of the list moderators in this section.
+# Note that the field you are changing here specifies the list
+# moderators.
 moderator = []
 
-# Denne beskrivelse benyttes n&aring;r denne malliste listes op sammen
-# med andre maillister, i toptekster, osv. Den b&oslash;r v&aelig;re
-# s&aring; kort som overhovedet mulig, uden at det bliver uklart hvad
-# meningen med maillisten er eller hvad den skal bruges til.
+# This description is used when the mailing list is listed with other
+# mailing lists, or in headers, and so forth.  It should be as succinct
+# as you can get it, while still identifying what the list is.
 description = ''
 
-# Teksten tolkes som html bortset fra linieskift, der vil blive
-# &aelig;ndret til html-tag'et '<br>', sådan at du kan benytte links,
-# forh&aring;ndsformateret tekst, osv. Men brug alts&aring; kun
-# linieskift der hvor du vil have et nyt afsnit. V&aelig;r meget
-# omhyggelig, hvis du benytter html-kode. Fejl (f.eks. manglende
-# slut-tag's) kan f&oslash;re til at listens informationsside ikke
-# bliver vist s&aring;dan som den skal.
+# The text will be treated as html except that newlines will be
+# translated to <br> - so you can use links, preformatted text, etc, but
+# don't put in carriage returns except where you mean to separate
+# paragraphs.  And review your changes - bad html (like some
+# unterminated HTML constructs) can prevent display of the entire
+# listinfo page.
 info = ''
 
 # This text will be prepended to subject lines of messages posted to the
-# list, to distinguish mailing list messages in in mailbox summaries.
+# list, to distinguish mailing list messages in mailbox summaries.
 # Brevity is premium here, it's ok to shorten long mailing list names to
 # something more concise, as long as it still identifies the mailing
-# list.
+# list. You can also add a sequential number by %d substitution
+# directive. eg.; [listname %d] -> [listname 123] (listname %05d) ->
+# (listname 00123)
+# 
 subject_prefix = '[Assilissat] '
 
-# Skjul afsenderen af meddelelser, ved at erstatte den med e-maillistens
-# adresse (Dette medfører at alle From:, Sender, og Reply-To: felter
-# fjernes)
+# Hide the sender of a message, replacing it with the list address
+# (Removes From, Sender and Reply-To fields)
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 anonymous_list = 0
 
-# Skal eksisterende Reply-To: felt i brevhovedet fjernes? Hvis ja, vil
-# dette blive gjort uanset om Mailman tilføjer et Reply-To: felt eller
-# ikke.
+# Should any existing Reply-To: header found in the original message be
+# stripped?  If so, this will be done regardless of whether an explict
+# Reply-To: header is added by Mailman or not.
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 first_strip_reply_to = 0
 
-# Denne indstillling fort&aelig;ller hvad Mailman skal g&oslash;re med
-# Reply-To: feltet i brevhovedet p&aring; e-mail der sendes til listen.
-# Hvis den er sat til Afsender, vil Mailman ikke tilf&oslash;je noget
-# Reply-To: felt, men findes et s&aring;dant felt allerede, vil det ikke
-# blive fjernet. S&aelig;ttes indstillingen til enten e-maillistens
-# adresse eller Egendefineret adresse, vil Mailman tilf&oslash;je, evt.
-# erstatte, et Reply-To: felt. (Egendefineret adresse inds&aelig;tter
-# v&aelig;rdien af indstillingen reply_to_address).
-# 
-# Der er flere grunde til ikke at indf&oslash;re eller erstatte
-# Reply-To: felter. En grund kan v&aelig;re at nogen af dem der sender
-# mail til listen er afh&aelig;ngige af selv at kunne s&aelig;tte
-# Reply-To: adressen. En anden grund er at modifikation af Reply-To:
-# adressen g&oslash;r det vanskeligere kun at sende svar til afsender.
-# Se 'Reply-To' Munging Considered Harmful for en diskussion omkring
-# emnet. Se Reply-To Munging Considered Useful for modsatte meninger.
-# 
-# Nogle maillister har begr&aelig;nset adgang, med en parallel liste
-# beregnet til diskussioner. Eksempler p&aring; dette er 'patches' eller
-# 'checkin' lister, som system for revisionskontrol sender
-# &aelig;ndringer i programmet til, men diskussioner omkring udvikling
-# af programmet sendes til udviklernes egen mailliste. For at
-# underst&oslash;tte lignende e-maillister, v&aelig;lg Egendefineret
-# adresse og s&aelig;t Reply-To: adressen i indstillingen
-# reply_to_address til at pege på den parallelle diskussionsliste.
-#
-# gyldige værdier:
-#    0 = "Afsender"
-#    1 = "mail listens adresse"
-#    2 = "Egendefineret adresse"
+# This option controls what Mailman does to the Reply-To: header in
+# messages flowing through this mailing list.  When set to Poster, no
+# Reply-To: header is added by Mailman, although if one is present in
+# the original message, it is not stripped.  Setting this value to
+# either This list or Explicit address causes Mailman to insert a
+# specific Reply-To: header in all messages, overriding the header in
+# the original message if necessary (Explicit address inserts the value
+# of <a href="?VARHELP=general/reply_to_address">reply_to_address).
+# 
+# There are many reasons not to introduce or override the Reply-To:
+# header.  One is that some posters depend on their own Reply-To:
+# settings to convey their valid return address.  Another is that
+# modifying Reply-To: makes it much more difficult to send private
+# replies.  See <a
+# href="http://www.unicom.com/pw/reply-to-harmful.html">`Reply-To'
+# Munging Considered Harmful for a general discussion of this issue.
+# See <a
+# href="http://www.metasystema.net/essays/reply-to.mhtml">Reply-To
+# Munging Considered Useful for a dissenting opinion.
+# 
+# Some mailing lists have restricted posting privileges, with a parallel
+# list devoted to discussions.  Examples are `patches' or `checkin'
+# lists, where software changes are posted by a revision control system,
+# but discussion about the changes occurs on a developers mailing list.
+# To support these types of mailing lists, select Explicit address and
+# set the Reply-To: address below to point to the parallel list.
+#
+# legal values are:
+#    0 = "Poster"
+#    1 = "This list"
+#    2 = "Explicit address"
 reply_goes_to_list = 0
 
-# Her definerer du adressen der skal s&aelig;ttes i Reply-To: feltet
-# n&aring;r indstillingen reply_goes_to_list er sat til Egendefineret
-# adresse.
-# 
-# Der findes mange grunde til at ikke indf&oslash;re eller erstatte
-# Reply-To: felter. En grund kan v&aelig;re at nogen af dem der sender
-# e-mail til listen er afh&aelig;ngige af selv at kunne s&aelig;tte
-# Reply-To: adressen. En anden grund er at modificering af Reply-To:
-# adressen g&oslash;r det vanskeligere at sende svar kun til afsender.
-# Se 'Reply-To' Munging Considered Harmful for en diskussion omkring
-# temaet. Se Reply-To Munging Considered Useful for modsatte meninger.
-# 
-# Nogle maillister har begr&aelig;nset adgang, med en egen parallel
-# liste beregnet for diskussioner. Eksempler p&aring; dette er 'patches'
-# eller 'checkin' lister, som system for revisionskontrol sender
-# &aelig;ndringer i programmet til, mens diskussioner omkring udvikling
-# af programmet sendes til udviklernes egen mailliste. For at
-# underst&oslash;tte s&aring;danne maillister, kan du definere Reply-To:
-# adressen her, og vælge Egendefineret adresse i indstillingen
-# reply_goes_to_list.
-# 
-# Bem&aelig;rk at hvis den oprindelige meddelelse indeholder et
-# Reply-To: felt, vil det ikke &aelig;ndres.
+# This is the address set in the Reply-To: header when the <a
+# href="?VARHELP=general/reply_goes_to_list">reply_goes_to_list option
+# is set to Explicit address.
+# 
+# There are many reasons not to introduce or override the Reply-To:
+# header.  One is that some posters depend on their own Reply-To:
+# settings to convey their valid return address.  Another is that
+# modifying Reply-To: makes it much more difficult to send private
+# replies.  See <a
+# href="http://www.unicom.com/pw/reply-to-harmful.html">`Reply-To'
+# Munging Considered Harmful for a general discussion of this issue.
+# See <a
+# href="http://www.metasystema.net/essays/reply-to.mhtml">Reply-To
+# Munging Considered Useful for a dissenting opinion.
+# 
+# Some mailing lists have restricted posting privileges, with a parallel
+# list devoted to discussions.  Examples are `patches' or `checkin'
+# lists, where software changes are posted by a revision control system,
+# but discussion about the changes occurs on a developers mailing list.
+# To support these types of mailing lists, specify the explicit
+# Reply-To: address here.  You must also specify Explicit address in the
+# reply_goes_to_list variable.
+# 
+# Note that if the original message contains a Reply-To: header, it will
+# not be changed.
 reply_to_address = ''
 
-# V&aelig;lg kun 'ja' her, hvis listen skal bruges som  "paraply" for
-# andre lister. Hvis 'ja' er valgt, vil bekr&aelig;ftelser og
-# meddelelser med adgangskode blive sendt til en adresse som konstrueres
-# ud fra medlemmets e-mailadresse - v&aelig;rdien af indstillingen
-# "umbrella_member_suffix" tilf&oslash;jes medlemmets kontonavn (det som
-# st&aring;r f&oslash;r @-tegnet).
+# Set this to yes when this list is intended to cascade only to other
+# mailing lists.  When set, meta notices like confirmations and password
+# reminders will be directed to an address derived from the member's
+# address - it will have the value of "umbrella_member_suffix" appended
+# to the member's account name.
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 umbrella_list = 0
 
-# N&aring;r "umbrella_list" indikerer at denne liste har andre
-# maillister som medlemmer, skal administrative meddelelser som f.eks.
-# bekr&aelig;ftelser og p&aring;mindelser om adgangskode ikke sendes til
-# selve listen, men snarere til administrator for listen. V&aelig;rdien
-# af denne indstilling bestemmer, hvilken adresse administrative
-# meddelelser skal sendes til. '-owner' er et almindeligt valg for denne
-# indstilling. Denne indstilling har ingen effekt n&aring;r
-# "umbrella_list" er sat til "Nej".
+# When "umbrella_list" is set to indicate that this list has other
+# mailing lists as members, then administrative notices like
+# confirmations and password reminders need to not be sent to the member
+# list addresses, but rather to the owner of those member lists.  In
+# that case, the value of this setting is appended to the member's
+# account name for such notices.  `-owner' is the typical choice.  This
+# setting has no effect when "umbrella_list" is "No".
 umbrella_member_suffix = '-owner'
 
-# Aktiver denne, hvis der skal sendes en p&aring;mindelse om adgangskode
-# til medlemmerne en gang hver m&aring;ned. Husk at medlemmerne
-# ogs&aring; selv kan frav&aelig;lge dette.
+# Turn this on if you want password reminders to be sent once per month
+# to your members.  Note that members may disable their own individual
+# password reminders.
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
-send_reminders = 1
-
-# Tekst du skriver her vil blive tilf&oslash;jet &oslash;verst i
-# velkomsthilsenen der sendes til nye medlemmer. Velkomshilsenen
-# indeholder i forvejen vigtige adresser og URLer knyttet til
-# maillisten, s&aring; den slags information er det ikke
-# n&oslash;dvendigt at inkludere her. Her kan du tilf&oslash;je f.eks.
-# oplysning om etikette eller regler for brug af listen, o.l.
-# 
-# Bem&aelig;rk: Linierne i denne tekst vil brydes efter f&oslash;lgende
-# regler:
-# 
-# Hvert afsnit udfyldes s&aringdan at ingen linie er l&aelig;ngere en 70
-# tegn. Enhver linie der begynder med tomme tegn udfyldes ikke. Tomme
-# linier adskiller afsnit.
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
+send_reminders = 0
+
+# This value, if any, will be added to the front of the new-subscriber
+# welcome message.  The rest of the welcome message already describes
+# the important addresses and URLs for the mailing list, so you don't
+# need to include any of that kind of stuff here.  This should just
+# contain mission-specific kinds of things, like etiquette policies or
+# team orientation, or that kind of thing.
+# 
+# Note that this text will be wrapped, according to the following rules:
+# Each paragraph is filled so that no line is longer than 70 characters.
+# Any line that begins with whitespace is not filled. A blank line
+# separates paragraphs.
 # 
 welcome_msg = ''
 
-# S&aelig;t kun denne til 'Nej' hvis du skal tilf&oslash;je nye
-# medlemmer manuelt, og ikke vil have at de f&aring;r det at vide. Dette
-# er meget nyttigt n&aring;r man g&aring;r fra et andet mallistesystem
-# og til Mailman, og vil have at overgangen skal v&aelig;re s&aring;
-# lidt m&aelig;rkbar som muligt.
+# Turn this off only if you plan on subscribing people manually and
+# don't want them to know that you did so.  This option is most useful
+# for transparently migrating lists from some other mailing list manager
+# to Mailman.
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 send_welcome_msg = 1
 
-# Tekst der sendes til medlemmer der framelder sig listen. Hvis feltet
-# er tomt, tilf&oslash;jes der ikke nogen speciel tekst til
-# frameldingen.
+# Text sent to people leaving the list.  If empty, no special text will
+# be added to the unsubscribe message.
 goodbye_msg = ''
 
-# Send afskedshilsen til medlemmer n&aring;r de frameldes?
+# Send goodbye message to members when they are unsubscribed?
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 send_goodbye_msg = 1
 
-# Der udsendes en p&aring;mindelse til listemoderator (og
-# listeadministrator) dagligt om anmodninger der af en eller anden grund
-# venter p&aring; behandling. V&aelig;lger du "Ja", vil
-# listeadminstrator ogs&aring; modtage en meddelelse s&aring; snart en
-# anmodning ankommer.
+# List moderators (and list administrators) are sent daily reminders of
+# requests pending approval, like subscriptions to a moderated list, or
+# postings that are being held for one reason or another.  Setting this
+# option causes notices to be sent immediately on the arrival of new
+# requests as well.
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 admin_immed_notify = 1
 
-# Skal listeadministrator modtage meddelelse om tilmeldinger og
-# afmeldinger?
+# Should administrator get notices of subscribes and unsubscribes?
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 admin_notify_mchanges = 0
 
-# Approval notices are sent when mail triggers certain of the limits
-# except routine list moderation and spam filters, for which notices are
-# not sent.  This option overrides ever sending the notice.
+# Send mail to poster when their posting is held for approval?
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 respond_to_post_requests = 1
 
-# Når dette valg er aktiveret, vil al e-mail til listen blive modereret.
-# Dette valg kan være nyttigt når din mailliste f.eks. har en såkaldt
-# "flamewar", altså en "krig" hvor medlemmer kun skælder ud på hinanden.
-# En "nød-moderering" kan da hjælpe dig at fjerne usaglige meddelelser
-# til listen, og på den måde dysse en ophedet diskussion ned.
+# When this option is enabled, all list traffic is emergency moderated,
+# i.e. held for moderation.  Turn this option on when your list is
+# experiencing a flamewar and you want a cooling off period.
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 emergency = 0
 
-# Når et nyt medlem tilmeldes listen, bliver medlemmets indstillinger
-# taget herfra.
+# When a new member is subscribed to this list, their initial set of
+# options is taken from the this variable's setting.
 new_member_options = 256
 
-# Filter for administrative meddelelser vil unders&oslash;ge om
-# meddelelsen egentligt er ment som en administrativ anmodning (f.eks.
-# tilmelding, framelding, o.l.), og i s&aring; fald sende meddelelsen
-# til listeadministrator i stedet for.
+# Administrivia tests will check postings to see whether it's really
+# meant as an administrative request (like subscribe, unsubscribe, etc),
+# and will add it to the the administrative requests queue, notifying
+# the administrator of the new request, in the process.
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 administrivia = 1
 
-# Maximum st&oslash;rrelse i kilobytes (KB) for indholdet i e-mail der
-# sendes til listen. Brug v&aelig;rdien '0' for ikke at have nogen
-# begr&aelig;nsning.
+# Maximum length in kilobytes (KB) of a message body.  Use 0 for no
+# limit.
 max_message_size = 40
 
-# "Maskinnavnet" er det navn som skal benyttes for e-mailadresser
-# relateret til Mailman p&aring; denne maskine, og er normalt navnet der
-# er forbundet med e-mail-servicen p&aring; maskinen. Denne indstilling
-# kan v&aelig;re nyttig hvis maskinen har flere navne.
+# The "host_name" is the preferred name for email to mailman-related
+# addresses on this host, and generally should be the mail host's
+# exchanger address, if any.  This setting can be useful for selecting
+# among alternative names of a host that has multiple addresses.
 host_name = 'jones.dk'
 
-# I RFC 2369 defineres en r&aelig;kke List-* felter i brevhovedet, der
-# normalt tilf&oslash;jes enhver meddelelse der sendes ud via listen.
-# Disse felter er til stor gavn for brugere , som benytter et
-# e-mailprogram der f&oslash;lger standarden. Disse felter b&oslash;r
-# derfor altid v&aelig;re med.
-# 
-# Ikke alle e-mailprogrammer f&oslash;lger denne standard. Hvis der er
-# mange medlemmer p&aring; listen, der benytter e-mailprogrammer, der
-# ikke kan h&aring;ndtere disse felter i brevhovedet, kan du v&aelig;lge
-# at udelade dem. Men du b&oslash;r f&oslash;rst fors&oslash;ge at
-# l&aelig;re og forklare medlemmerne hvad hensigten med s&aring;danne
-# felter er, og hvordan de kan skjule dem i deres e-mailprogram. Som en
-# sidste udvej kan du udelade felterne, men det anbefales ikke (og denne
-# mulighed kan faktisk ogs&aring; blive fjernet i senere versioner af
-# Mailman).
-#
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# RFC 2369 defines a set of List-* headers that are normally added to
+# every message sent to the list membership. These greatly aid end-users
+# who are using standards compliant mail readers.  They should normally
+# always be enabled.
+# 
+# However, not all mail readers are standards compliant yet, and if you
+# have a large number of members who are using non-compliant mail
+# readers, they may be annoyed at these headers.  You should first try
+# to educate your members as to why these headers exist, and how to hide
+# them in their mail clients.  As a last resort you can disable these
+# headers, but this is not recommended (and in fact, your ability to
+# disable these headers may eventually go away).
+#
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 include_rfc2369_headers = 1
 
-# List-Post: feltet er et af felterne anbefalet i RFC 2369. P&aring;
-# nogle e-maillister (som f.eks. kun bruges til
-# offentligg&oslash;relser), er det kun bestemte personer der har lov
-# til at poste til listen. Almindelige medlemmer af listen har normalt
-# ikke lov til at poste til listen. For den slags lister, er List-Post:
-# feltet misvisende. S&aelig;t denne indstilling til Nej, for at
-# undg&aring; at feltet tilf&oslash;jes. (Dette p&aring;virker ikke
-# andre List-*: felter.)
-#
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# The List-Post: header is one of the headers recommended by RFC 2369.
+# However for some announce-only mailing lists, only a very select group
+# of people are allowed to post to the list; the general membership is
+# usually not allowed to post.  For lists of this nature, the List-Post:
+# header is misleading. Select No to disable the inclusion of this
+# header. (This does not affect the inclusion of the other List-*:
+# headers.)
+#
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 include_list_post_header = 1
 
+# Discard held messages older than this number of days. Use 0 for no
+# automatic discarding.
+max_days_to_hold = 0
+
 ## Language options
 #
-# Underst&oslash;ttelse af flere sprog. (Internationalisering)
-
-# Dette er standardsproget som benyttes for denne mailliste. Hvis flere
-# end et sprog/ underst&oslash;ttes, vil medlemmer af listen selv kunne
-# v&aelig;lge hvilket sprog der skal benyttes n&aring;r de g&aring;r ind
-# p&aring; deres personlige webside, og n&aring;r meddelelser fra
-# systemet sendes til dem. Hvis medlemmerne ikke &aelig;ndrer noget
-# selv, vil dette standardsprog blive benyttet. Dette g&aelig;lder
-# b&aring;de web-baserede og e-mail-baserede meddelelser, men ikke
-# meddelelser sendt af listens medlemmer.
+# Natural language (internationalization) options.
+
+# This is the default natural language for this mailing list. If more
+# than one language is supported then users will be able to select their
+# own preferences for when they interact with the list.  All other
+# interactions will be conducted in the default language.  This applies
+# to both web-based and email-based messages, but not to email posted by
+# list members.
 preferred_language = 'en'
 
-# Her er alle sprog, som denne liste har underst&oslash;ttelse for.
-# Bem&aelig;rk at standardsproget skal v&aelig;re med.
+# These are all the natural languages supported by this list. Note that
+# the default language must be included.
 available_languages = ['en', 'da']
 
-# Hvis standardsproget for din mailliste benytter et andet tegns&aelig;t
-# end ASCII og Emne prefixet for listen indeholder tegn som ikke findes
-# i ASCII-tegns&aelig;ttet, vil prefixet altid blive kodet i henhold til
-# den relevante standard. Hvis Emne prefixet kun indeholder ASCII tegn,
-# ønsker du måske at vælge Aldrig for at undgå kodning. Dette kan gøre
-# emnet lidt mere læseligt for brugere med e-mailprogrammer der ikke kan
-# håndtere andre tegnsæt end ASCII.
-# 
-# Bemærk imidlertid, at hvis din mailliste modtager både kodede og
-# ukodede emnefelter , kan det være bedst at vælge Efter behov. Med
-# denne indstilling vil Mailman ikke kode ASCII prefixer hvis resten af
-# titelfeltet kun indeholder ASCII tegn, men vil kode prefixet hvis det
-# indeholder tegn som ikke er ASCII tegn. På denne måde undgås en
-# tvetydighed i standarderne, som forårsager at visse e-mailprogrammer
-# vil vise ekstra eller manglende mellemrum imellem emne prefixet og det
-# oprindelige emne.
-#
-# gyldige værdier:
-#    0 = "Aldrig"
-#    1 = "Altid"
-#    2 = "Efter behov"
+# If your mailing list's default language uses a non-ASCII character set
+# and the prefix contains non-ASCII characters, the prefix will always
+# be encoded according to the relevant standards.  However, if your
+# prefix contains only ASCII characters, you may want to set this option
+# to Never to disable prefix encoding.  This can make the subject
+# headers slightly more readable for users with mail readers that don't
+# properly handle non-ASCII encodings.
+# 
+# Note however, that if your mailing list receives both encoded and
+# unencoded subject headers, you might want to choose As needed.  Using
+# this setting, Mailman will not encode ASCII prefixes when the rest of
+# the header contains only ASCII characters, but if the original header
+# contains non-ASCII characters, it will encode the prefix.  This avoids
+# an ambiguity in the standards which could cause some mail readers to
+# display extra, or missing spaces between the prefix and the original
+# header.
+#
+# legal values are:
+#    0 = "Never"
+#    1 = "Always"
+#    2 = "As needed"
 encode_ascii_prefixes = 0
 
 ## Nondigest options
 #
-# Regler for levering i normal-modus.
+# Policies concerning immediately delivered list traffic.
 
-# Kan medlemmer vælge normal-modus?
+# Can subscribers choose to receive mail immediately, rather than in
+# batched digests?
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 nondigestable = 1
 
-# Tekst der tilføjes &oslash;verst i e-mail der sendes til listens
-# medlemmer. This text can include Python format strings which are
-# resolved against list attributes.  The list of substitutions allowed
-# are:
+# Text prepended to the top of every immediately-delivery message. This
+# text can include Python format strings which are resolved against list
+# attributes.  The list of substitutions allowed are:
 # 
 # 
 # real_name - The "pretty" name of the list; usually the list name with
@@ -401,10 +388,9 @@ nondigestable = 1
 # 
 msg_header = ''
 
-# Tekst som tilf&oslash;jes nederst i e-mail der sendes til listens
-# medlemmer. This text can include Python format strings which are
-# resolved against list attributes.  The list of substitutions allowed
-# are:
+# Text appended to the bottom of every immediately-delivery message.
+# This text can include Python format strings which are resolved against
+# list attributes.  The list of substitutions allowed are:
 # 
 # 
 # real_name - The "pretty" name of the list; usually the list name with
@@ -432,45 +418,54 @@ msg_footer = """_______________________________________________
 %(real_name)s@%(host_name)s
 %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s"""
 
+# When you scrub attachments, they are stored in archive area and links
+# are made in the message so that the member can access via web browser.
+# If you want the attachments totally disappear, you can use content
+# filter options.
+#
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
+scrub_nondigest = False
+
 ## Digest options
 #
-# Opsætning af sammendrag-modus.
+# Batched-delivery digest characteristics.
 
-# Kan medlemmer af listen vælge sammendrag-modus?
+# Can list members choose to receive list traffic bunched in digests?
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 digestable = 1
 
-# Hvilken modus er standard for nye brugere?
+# Which delivery mode is the default for new users?
 #
-# gyldige værdier:
-#    0 = "Normal"
-#    1 = "Sammendrag"
+# legal values are:
+#    0 = "Regular"
+#    1 = "Digest"
 digest_is_default = 0
 
-# Hvilket format skal benyttes som standard for samle-email?
+# When receiving digests, which format is default?
 #
-# gyldige værdier:
-#    0 = "Ren tekst"
+# legal values are:
+#    0 = "Plain"
 #    1 = "MIME"
 mime_is_default_digest = 0
 
-# Hvor stor (i KB) m&aring; en samle-email h&oslash;jst v&aelig;re
-# f&oslash;r den udsendes?
+# How big in Kb should a digest be before it gets sent out?
 digest_size_threshhold = 30
 
-# Skal der sendes en samle-email dagligt, selv om st&oslash;rrelsen ikke
-# er opn&aring;et?
+# Should a digest be dispatched daily when the size threshold isn't
+# reached?
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 digest_send_periodic = 1
 
-# Tekst som tilf&oslash;jes &oslash;verst i samle-emailen, f&oslash;r
-# indholdsfortegnelsen.This text can include Python format strings which
+# Text attached (as an initial message, before the table of contents) to
+# the top of digests. This text can include Python format strings which
 # are resolved against list attributes.  The list of substitutions
 # allowed are:
 # 
@@ -497,10 +492,9 @@ digest_send_periodic = 1
 # 
 digest_header = ''
 
-# Tekst der tilføjes nederst i hver samle-email, som sidste
-# information.This text can include Python format strings which are
-# resolved against list attributes.  The list of substitutions allowed
-# are:
+# Text attached (as a final message) to the bottom of digests. This text
+# can include Python format strings which are resolved against list
+# attributes.  The list of substitutions allowed are:
 # 
 # 
 # real_name - The "pretty" name of the list; usually the list name with
@@ -528,277 +522,279 @@ digest_footer = """_______________________________________________
 %(real_name)s@%(host_name)s
 %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s"""
 
-# N&aring;r et nyt volume startes, &oslash;ges volume nummeret, og
-# udgavenummeret s&aelig;ttes til 1.
+# When a new digest volume is started, the volume number is incremented
+# and the issue number is reset to 1.
 #
-# gyldige værdier:
-#    0 = "&Aring;rlig"
-#    1 = "M&aring;nedlig"
-#    2 = "Kvartalsvis"
-#    3 = "Ugentlig"
-#    4 = "Daglig"
+# legal values are:
+#    0 = "Yearly"
+#    1 = "Monthly"
+#    2 = "Quarterly"
+#    3 = "Weekly"
+#    4 = "Daily"
 digest_volume_frequency = 1
 
 ## Privacy options
 #
-# Her kan du bestemme hvad der kr&aelig;ves for at tilmelde sig til
-# maillisten, og bl.a. bestemme om maillisten skal v&aelig;re skjult
-# eller ikke. Se ogs&aring; <a
-# href="http://mail.jones.dk/cgi-bin/mailman/admin/assilissat/archive">Indstillinger 
-# for arkivering</a> for egne indstillinger, n&aring;r det g&aelig;lder
-# arkivet og arkivering.
+# This section allows you to configure subscription and membership
+# exposure policy.  You can also control whether this list is public or
+# not.  See also the <a
+# href="http://mail.jones.dk/cgi-bin/mailman/admin/assilissat/archive">Archival 
+# Options</a> section for separate archive-related privacy settings.
 
-# Vis denne mailliste n&aring;r nogen beder om at se en oversigt over
-# maillister p&aring; denne maskine?
+# Advertise this list when people ask what lists are on this machine?
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 advertised = 1
 
-# bekræftelse(*) - bekr&aelig;ftelse via e-mail er n&oslash;dvendig
-# godkendelse - anmodning om medlemskab skal godkendes af
-# listeadministrator (eller evt. listemoderator) bekr&aelig;ftelse +
-# godkendelse - b&aring;de bekr&aelig;ftelse via e-mail og godkendelse
-# fra listeadministrator (evt. listemoderator) er n&oslash;dvendig
-# 
-# (*) n&aring;r nogen vil tilmelde sig en liste, sender Mailman en
-# meddelelse med en unik identifikator som skal angives for at
-# bekr&aelig;fte tilmeldingen. P&aring; den m&aring;de vil det ikke
-# v&aelig;re muligt at tilmelde nogen imod deres vilje.
-#
-# gyldige værdier:
-#    1 = "Bekr&aelig;ftelse"
-#    2 = "Godkendelse"
-#    3 = "Bekr&aelig;ftelse og godkendelse"
+# Confirm (*) - email confirmation required Require approval - require
+# list administrator approval for subscriptions Confirm and approve -
+# both confirm and approve
+# 
+# (*) when someone requests a subscription, Mailman sends them a notice
+# with a unique subscription request number that they must reply to in
+# order to subscribe. This prevents mischievous (or malicious) people
+# from creating subscriptions for others without their consent.
+#
+# legal values are:
+#    1 = "Confirm"
+#    2 = "Require approval"
+#    3 = "Confirm and approve"
 subscribe_policy = 1
 
-# N&aring;r medlemmer &oslash;nsker at forlade en mailliste, sender de
-# en anmodning om framelding, enten via web, eller via e-mail. Normalt
-# er det bedst at disse anmodninger automatisk godkendes, s&aring;
-# medlemmer kan afmelde sig n&aring;r de &oslash;nsker det (mange
-# &oslash;nsker selv at kunne administrere en framelding). For nogle
-# f&aring; maillister kan det alligevel v&aelig;re aktuelt at have
-# kontrol over om medlemmer kan afmelde sig selv eller ej. En liste som
-# alle ansatte i et firma SKAL v&aelig;re medlem af, er et eksempel
-# p&aring; en s&aring;dan liste.
-#
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# When members want to leave a list, they will make an unsubscription
+# request, either via the web or via email. Normally it is best for you
+# to allow open unsubscriptions so that users can easily remove
+# themselves from mailing lists (they get really upset if they can't get
+# off lists!).
+# 
+# For some lists though, you may want to impose moderator approval
+# before an unsubscription request is processed.  Examples of such lists
+# include a corporate mailing list that all employees are required to be
+# members of.
+#
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 unsubscribe_policy = 0
 
-# Alle e-mailadresser som angives her vil blive udelukket fra listen, og
-# kan ikke tilmelde sig. Indtast e-mailadresser, en pr. linie, start
-# linien med tegnet ^ for at angive et regexp-udtryk der skal stemme
-# overens med afsenderadressen.
+# Addresses in this list are banned outright from subscribing to this
+# mailing list, with no further moderation required.  Add addresses one
+# per line; start the line with a ^ character to designate a regular
+# expression match.
 ban_list = ['afygrobo@hotmail.com', 'hxufesemwr@aaiworldmarket.com', 'nddtu@yahoo.com', 'uznnmnok@aaiworldmarket.com']
 
-# Hvis denne indstilling ikke er sat til 'Alle', vil medlemslisten blive
-# beskyttet af medlemmernes eller administrators adgangskode.
+# When set, the list of subscribers is protected by member or admin
+# password authentication.
 #
-# gyldige værdier:
-#    0 = "Alle"
-#    1 = "Kun medlemmer af listen"
-#    2 = "Kun listeadministrator"
+# legal values are:
+#    0 = "Anyone"
+#    1 = "List members"
+#    2 = "List admin only"
 private_roster = 0
 
-# V&aelig;lger du 'Ja' her, vil medlemmers e-mailadresser blive
-# omskrevet n&aring;r de vises i en oversigt p&aring; websiderne
-# (b&aring;de som tekst og som links), s&aring; de ikke er nemme at
-# tolke som e-mailadresser. Formålet er at undg&aring; at medlemmernes
-# mailadresser bliver opsamlet af e-mailsniffere som skanner websider
-# for e-mailadresser (og derefter bruger dem til at udsende spam/junk
-# mail).
-#
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# Setting this option causes member email addresses to be transformed
+# when they are presented on list web pages (both in text and as links),
+# so they're not trivially recognizable as email addresses.  The
+# intention is to prevent the addresses from being snarfed up by
+# automated web scanners for use by spammers.
+#
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 obscure_addresses = 1
 
 ## Privacy options
 #
-# N&aring;r en meddelelse sendes til maillisten, g&aring;r den igennem
-# nogle trin for at afg&oslash;re om moderator skal godkende meddelelsen
-# eller ikke. Her finder du indstillinger til at kontrollere moderation
-# af e-mail fra b&aring;de medlemmer og ikke-medlemmer.
-# 
-# <p>E-mail fra medlemmer holdes tilbage for godkendelse hvis deres
-# <b>moderationsflag</b> er sat. Du kan bestemme om e-mail fra medlemmer
-# normalt skal vurderes eller ikke f&oslash;r den sendes til listen.
-# 
-# <p>E-mail som ikke er sendt af medlemmer af listen, kan automatisk
-# blive <a
-# href="?VARHELP=privacy/sender/accept_these_nonmembers">godkendt</a>,
-# <a href="?VARHELP=privacy/sender/hold_these_nonmembers">holdt tilbage
-# for godkendelse</a>, <a
-# href="?VARHELP=privacy/sender/reject_these_nonmembers">afvist (sendt
-# retur)</a>, eller <a
-# href="?VARHELP=privacy/sender/discard_these_nonmembers">slettet</a>,
-# enten enkeltvis eller som en gruppe. Al e-mail fra ikke-medlemmer, som
-# ikke specifikt bliver godkendt, sendt retur eller slettet, vil blive
-# behandlet alt efter hvad <a
-# href="?VARHELP=privacy/sender/generic_nonmember_action">generelle
-# regler for ikke-medlemmer</a> viser.
-# 
-# <p>I tekstboksene nedenfor kan du tilf&oslash;je en e-mailadresse pr.
-# linie. Du kan ogs&aring; tilf&oslash;je  <a
-# href="http://www.python.org/doc/current/lib/module-re.html">Python
-# regexp-udtryk</a>. Begynd i s&aring; fald linien med tegnet ^ for at
-# markere at det er et s&aring;dant udtryk. N&aring;r du benytter
-# backslash, skriv da lige som i rene strings (Python raw strings)
-# (normalt kun &eacute;n backslash ad gangen).
-# 
-# <p>Bem&aelig;rk: sammenligning med normale e-mailadresser
-# udf&oslash;res f&oslash;rst, regexp-udtryk vil derfor blive behandlet
-# sidst.
-
-# Hvert medlem af listen har et moderationsflag som fort&aelig;ller om
-# e-mails fra medlemmet kan sendes direkte til e-maillisten, eller om de
-# f&oslash;rst skal godkendes af listemoderator. N&aring;r
-# moderationsflaget er sat til, skal e-mails fra medlemmet godkendes af
-# listemoderator f&oslash;r de udsendes til alle p&aring; listen. Som
-# listeadministrator kan du for hvert enkelt medlem bestemme om
-# medlemmets e-mail skal modereres eller ikke. N&aring;r et nyt medlem
-# tilmeldes listen, s&aelig;ttes moderationsflaget til den indstilling
-# du v&aelig;lger her. S&aelig;t den til 'Nej' hvis du &oslash;nsker at
-# e-mail fra medlemmer normalt skal g&aring; lige til listen. S&aelig;t
-# den til 'Ja' hvis du &oslash;nsker at e-mail fra nye medlemmer skal
-# godkendes f&oslash;r de udsendes til hele listen. Du kan altid
-# s&aelig;tte moderationsflaget for hvert enkelt medlem fra
-# Administration af medlemmer siden.
-#
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# When a message is posted to the list, a series of moderation steps are
+# take to decide whether the a moderator must first approve the message
+# or not.  This section contains the controls for moderation of both
+# member and non-member postings.
+# 
+# <p>Member postings are held for moderation if their <b>moderation
+# flag</b> is turned on.  You can control whether member postings are
+# moderated by default or not.
+# 
+# <p>Non-member postings can be automatically <a
+# href="?VARHELP=privacy/sender/accept_these_nonmembers" >accepted</a>,
+# <a href="?VARHELP=privacy/sender/hold_these_nonmembers">held for
+# moderation</a>, <a
+# href="?VARHELP=privacy/sender/reject_these_nonmembers" >rejected</a>
+# (bounced), or <a
+# href="?VARHELP=privacy/sender/discard_these_nonmembers"
+# >discarded</a>, either individually or as a group.  Any posting from a
+# non-member who is not explicitly accepted, rejected, or discarded,
+# will have their posting filtered by the <a
+# href="?VARHELP=privacy/sender/generic_nonmember_action">general
+# non-member rules</a>.
+# 
+# <p>In the text boxes below, add one address per line; start the line
+# with a ^ character to designate a <a href=
+# "http://www.python.org/doc/current/lib/module-re.html" >Python regular
+# expression</a>.  When entering backslashes, do so as if you were using
+# Python raw strings (i.e. you generally just use a single backslash).
+# 
+# <p>Note that non-regexp matches are always done first.
+
+# Each list member has a moderation flag which says whether messages
+# from the list member can be posted directly to the list, or must first
+# be approved by the list moderator.  When the moderation flag is turned
+# on, list member postings must be approved first.  You, the list
+# administrator can decide whether a specific individual's postings will
+# be moderated or not.
+# 
+# When a new member is subscribed, their initial moderation flag takes
+# its value from this option.  Turn this option off to accept member
+# postings by default.  Turn this option on to, by default, moderate
+# member postings first.  You can always manually set an individual
+# member's moderation bit by using the membership management screens.
+#
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 default_member_moderation = 0
 
+# Hold -- this holds the message for approval by the list moderators.
+# 
+# Reject -- this automatically rejects the message by sending a bounce
+# notice to the post's author.  The text of the bounce notice can be <a
+# href="?VARHELP=privacy/sender/member_moderation_notice" >configured by
+# you.
 # 
-# Hold tilbage -- meddelelsen holdes tilbage for godkendelse af
-# listemoderator(er). Afvis -- meddelelsen sendes automatisk retur til
-# afsender. Begrundelsen der sendes kan du skrive selv Slet --
-# meddelelsen bliver fjernet uden at give besked om dette til afsender.
+# Discard -- this simply discards the message, with no notice sent to
+# the post's author.
 # 
 #
-# gyldige værdier:
-#    0 = "Hold&nbsp;tilbage"
-#    1 = "Afvis"
-#    2 = "Slet"
+# legal values are:
+#    0 = "Hold"
+#    1 = "Reject"
+#    2 = "Discard"
 member_moderation_action = 0
 
-# Tekst som skal sendes med meddelelsen om afvisning som sendes til
-# modererede medlemmer af listen.
+# Text to include in any <a
+# href="?VARHELP/privacy/sender/member_moderation_action" >rejection
+# notice to be sent to moderated members who post to this list.
 member_moderation_notice = ''
 
-# E-mail fra disse ikke-medlemmer vil automatisk blive godkendt.
-# Tilf&oslash;j e-mailadresser, en pr. linie. Start linien med tegnet ^
-# for at angive et regexp-udtryk som skal stemme overens med
-# afsenderadressen.
+# Postings from any of these non-members will be automatically accepted
+# with no further moderation applied.  Add member addresses one per
+# line; start the line with a ^ character to designate a regular
+# expression match.
 accept_these_nonmembers = []
 
-# e-mail fra disse ikke-medlemmer vil automatisk blive holdt tilbage for
-# vurdering af listemoderator. Afsenderen vil modtage en meddelelse om
-# dette, med bl.a. instruktioner om hvordan han/hun kan
-# tilbagetr&aelig;kke sin e-mail. Indtast e-mailadresser, en pr. linie.
-# Start linien med tegnet ^ for at angive et regexp-udtryk som skal
-# stemme overens med afsenderadressen.
+# Postings from any of these non-members will be immediately and
+# automatically held for moderation by the list moderators. The sender
+# will receive a notification message which will allow them to cancel
+# their held message.  Add member addresses one per line; start the line
+# with a ^ character to designate a regular expression match.
 hold_these_nonmembers = []
 
-# E-mail fra disse ikke-medlemmer vil automatisk blive afvist. De vil
-# f&aring; mailen retur, med en meddelelse om at den blev automatisk
-# afvist. Dette valg b&oslash;r ikke benyttes for kendte spammere, de
-# b&oslash;r automatisk slettes. Indtast e-mailadresser, en pr. linie.
-# Start linien med tegnet ^ for at angive et regexp-udtryk som skal
-# stemme overens med afsenderadressen.
+# Postings from any of these non-members will be automatically rejected.
+# In other words, their messages will be bounced back to the sender with
+# a notification of automatic rejection.  This option is not appropriate
+# for known spam senders; their messages should be <a
+# href="?VARHELP=privacy/sender/discard_these_nonmembers" >automatically
+# discarded.
+# 
+# Add member addresses one per line; start the line with a ^ character
+# to designate a regular expression match.
 reject_these_nonmembers = []
 
-# E-mail fra disse ikke-medlemmer vil automatisk blive slettet. Det vil
-# sige at meddelelsen afvises uden nogen form for tilbagemelding, men
-# listemoderator kan (om &oslash;nsket) modtage en kopi af den afviste
-# e-mail. Tilf&oslash;j e-mailadresser, en pr. linie, start linien med
-# tegnet ^ for at angive et regexp-udtryk der skal stemme overens med
-# afsenderadressen.
+# Postings from any of these non-members will be automatically
+# discarded.  That is, the message will be thrown away with no further
+# processing or notification.  The sender will not receive a
+# notification or a bounce, however the list moderators can optionally
+# <a href="?VARHELP=privacy/sender/forward_auto_discards" >receive
+# copies of auto-discarded messages..
+# 
+# Add member addresses one per line; start the line with a ^ character
+# to designate a regular expression match.
 discard_these_nonmembers = ['afygrobo@hotmail.com', 'hxufesemwr@aaiworldmarket.com', 'nddtu@yahoo.com', 'uznnmnok@aaiworldmarket.com']
 
-# N&aring;r en e-mail fra et ikke-medlem bliver modtaget, sammenlignes
-# e-mailens afsender med listen over e-mailadresser der skal godkendes,
-# holdes tilbage, <a
-# href="?VARHELP=privacy/sender/reject_these_nonmembers" >afvises
-# (sendes retur), eller slettes. Hvis afsenderadressen ikke stemmer
-# overens med en adresse der findes i listerne, bliver f&oslash;lgende
-# afg&oslash;relse truffet.
-#
-# gyldige værdier:
-#    0 = "Godkend"
-#    1 = "Hold&nbsp;tilbage"
-#    2 = "Afvis"
-#    3 = "Slet"
+# When a post from a non-member is received, the message's sender is
+# matched against the list of explicitly <a
+# href="?VARHELP=privacy/sender/accept_these_nonmembers" >accepted,
+# held, <a href="?VARHELP=privacy/sender/reject_these_nonmembers"
+# >rejected (bounced), and <a
+# href="?VARHELP=privacy/sender/discard_these_nonmembers" >discarded
+# addresses.  If no match is found, then this action is taken.
+#
+# legal values are:
+#    0 = "Accept"
+#    1 = "Hold"
+#    2 = "Reject"
+#    3 = "Discard"
 generic_nonmember_action = 0
 
-# Skal meddelelser fra ikke-medlemmer, hvis mail automatisk slettes,
-# videresendes til listemoderator?
+# Should messages from non-members, which are automatically discarded,
+# be forwarded to the list moderator?
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 forward_auto_discards = 1
 
+# Text to include in any rejection notice to be sent to non-members who
+# post to this list. This notice can include the list's owner address by
+# %(listowner)s and replaces the internally crafted default message.
+nonmember_rejection_notice = ''
+
 ## Privacy options
 #
-# Her kan du ops&aelig;tte filtrering baseret på modtageren af
-# meddelelsen.
+# This section allows you to configure various filters based on the
+# recipient of the message.
 
-# Meget (faktisk det meste) spam/junk mail har ikke de endelige
-# modtagere i modtagerfelterne. Faktisk indeholder felterne To: og/eller
-# Cc: oftest en helt ugyldig adresse. Begr&aelig;nsningen du
-# s&aelig;tter her har kun indvirkning p&aring; det som st&aring;r
-# f&oslash;r '@' tegnet i adressen, men filtret vil alligevel opfange og
-# blokere det meste spam/junk mail.
+# Many (in fact, most) spams do not explicitly name their myriad
+# destinations in the explicit destination addresses - in fact often the
+# To: field has a totally bogus address for obfuscation.  The constraint
+# applies only to the stuff in the address before the '@' sign, but
+# still catches all such spams.
+# 
+# The cost is that the list will not accept unhindered any postings
+# relayed from other addresses, unless
 # 
-# Prisen for dette er, at listen ikke uhindret vil kunne modtage e-mail
-# videresendt via andre e-mailadresser, med mindre
 # 
+# The relaying address has the same name, or
+# 
+# The relaying address name is included on the options that specifies
+# acceptable aliases for the list.
 # 
-# Adressen der videresendes fra hedder det samme, eller Adressen der
-# videresendes fra inkluderes i indstillingen som bestemmer gyldige
-# aliaser for listen.
 # 
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 require_explicit_destination = 1
 
-# Alternative e-mailadresser som godtages n&aring;r
-# 'require_explicit_destination' er sat til. Som v&aelig;rdi for denne
-# indstilling skal du angive regexp-udtryk ("regular expressions"), et
-# udtryk pr. linie, der sammenlignes med hver modtageradresse i
-# meddelelsen. Sammenligningen udf&oslash;res med Pythons re.match()
-# funktion, som betyder at de kun g&aelig;lder for begyndelsen af
-# strengen.
-# 
-# For bagudkompatibilitet med Mailman 1.1, hvis regexp-udtryk ikke
-# indeholder en '@', sammenlignes udtrykket kun med den f&oslash;rste
-# del (det som st&aring;r f&oslash;r '@') i modtageradressen. Hvis
-# sammenligningen ikke lykkes, eller hvis udtrykket ikke indholder en
-# '@', sammenlignes udtrykket med hele modtageradressen.
-# 
-# Sammenligning med kun den f&oslash;rste del af en modtageradresse
-# underst&oslash;ttes ikke l&aelig;ngere. I fremtidige versioner af
-# Mailman vil kun sammenligning med hele modtageradresser blive
-# underst&oslash;ttet.
+# Alternate addresses that are acceptable when
+# `require_explicit_destination' is enabled.  This option takes a list
+# of regular expressions, one per line, which is matched against every
+# recipient address in the message.  The matching is performed with
+# Python's re.match() function, meaning they are anchored to the start
+# of the string.
+# 
+# For backwards compatibility with Mailman 1.1, if the regexp does not
+# contain an `@', then the pattern is matched against just the local
+# part of the recipient address.  If that match fails, or if the pattern
+# does contain an `@', then the pattern is matched against the entire
+# recipient address.
+# 
+# Matching against the local part is deprecated; in a future release,
+# the pattern will always be matched against the entire recipient
+# address.
 acceptable_aliases = ''
 
-# Hvis en mail der er sendt til listen indeholder s&aring; mange som
-# eller flere modtagere end denne v&aelig;rdi, holdes mailen tilbage,
-# s&aring; listeadministrator eventuelt kan godkende den. Brug
-# v&aelig;rdien 0 for ingen begr&aelig;nsning.
+# If a posting has this number, or more, of recipients, it is held for
+# admin approval.  Use 0 for no ceiling.
 max_num_recipients = 10
 
 ## Privacy options
 #
-# Her kan du opsætte forskellige anti-spam filtre, som kan bidrage til
-# at reducere mængden af spam der distribueres via e-maillisten.
+# This section allows you to configure various anti-spam filters posting
+# filters, which can help reduce the amount of spam your list members
+# end up receiving.
+# 
 
 # Each header filter rule has two parts, a list of regular expressions,
 # one per line, and an action to take.  Mailman matches the message's
@@ -809,22 +805,23 @@ max_num_recipients = 10
 # You can have more than one filter rule for your list.  In that case,
 # each rule is matched in turn, with processing stopped after the first
 # match.
+# 
+# Note that headers are collected from all the attachments (except for
+# the mailman administrivia message) and matched against the regular
+# expressions. With this feature, you can effectively sort out messages
+# with dangerous file types or file name extensions.
 header_filter_rules = []
 
-# Brug denne indstilling til at bortfiltrere mail til listen, baseret
-# p&aring; indholdet af et eller flere felter i brevhovedet. Her skal du
-# skrive regexp-udtryk (regular expressions), et pr. linie, som
-# sammenlignes med det aktuelle felt. Sammenligningen skelner ikke
-# imellem store og sm&aring; bogstaver. Linier der begynder med '#'
-# sammenlignes ikke.
+# Use this option to prohibit posts according to specific header values.
+# The target value is a regular-expression for matching against the
+# specified header.  The match is done disregarding letter case.  Lines
+# beginning with '#' are ignored as comments.
 # 
-# For eksempel: udtrykket to: .*@public.com fort&aelig;ller at al mail
-# som indeholder '@public.com' i To: feltet, skal holdes tilbage for
-# godkendelse.
+# For example:to: .*@public.com  says to hold all postings with a To:
+# mail header containing '@public.com' anywhere among the addresses.
 # 
-# Bem&aelig;rk: tomme tegn i starten af regexp-udtrykket fjernes. Dette
-# kan omg&aring;s p&aring; flere m&aring;der, f.eks. ved at bruge
-# escape-tegn eller parenteser.
+# Note that leading whitespace is trimmed from the regexp.  This can be
+# circumvented in a number of ways, e.g. by escaping or bracketing it.
 bounce_matching_headers = """
 # Lines that *start* with a '#' are comments.
 to: friend@public.com
@@ -834,415 +831,439 @@ from: .*@uplinkpro.com"""
 
 ## Bounce options
 #
-# Disse regler bestemmer hvordan automatisk behandling af returmails
-# skal foreg&aring;. Her er en oversigt over hvordan det virker.
-# 
-# <p>N&aring;r Mailman modtager en returmail, bliver to ting
-# fors&oslash;gt tolket. Den ene er e-mailadressen for medlemmet som
-# egentlig skulle modtage e-mailen, og den anden er &aring;rsagen til
-# problemet. &Aring;rsagen tolkes til at v&aelig;re <em>alvorlig</em>
-# eller <em>harml&oslash;s</em> alt efter om &aring;rsagen er af kritisk
-# eller af mindre alvorlig art. Hvis der er tvivl, tolkes &aring;rsagen
-# som alvorlig.
-# 
-# <p>Hvis ingen e-mailadresse kan hentes ud af meddelelsen, bliver den
-# normalt afvist. Ellers vil medlemmet som har e-mailadressen f&aring;
-# tildelt et <em>returtal</em>, og hver gang der kommer en
-# returmeddelelse vil tallet &oslash;ges. Alvorlige &aring;rsager
-# f&oslash;rer til at tallet &oslash;ges med 1, harml&oslash;se
-# &aring;rsager f&oslash;rer til at det &oslash;ges med 0.5. Dette sker
-# kun &eacute;n gang pr. dag, s&aring; selv om der kommer 10 alvorlige
-# returmails fra et medlem p&aring; &eacute;n dag, vil tallet kun
-# &oslash;ges med 1.
-# 
-# <p>N&aring;r returtallet for et medlem n&aring;r en vis <a
-# href="?VARHELP=bounce/bounce_score_threshold">gr&aelig;nse</a>,
-# stoppes levering til medlemmet. Dermed vil medlemmet ikke modtage
-# e-mail fra listen f&oslash;r levering s&aelig;ttes til igen. Medlemmet
-# vil med j&aelig;vne mellemrum modtage meddelelse om at dette er sket,
-# og hvad han/hun skal g&oslash;re for at f&aring; e-mail fra listen
-# igen.
-# 
-# <p>Du kan bestemme <a
-# href="?VARHELP=bounce/bounce_you_are_disabled_warnings">hvor mange
-# advarsler</a> medlemmet skal have og <a
-# href="?VARHELP=bounce/bounce_you_are_disabled_warnings_interval">hvor
-# ofte</a> han/hun skal modtage s&aring;danne advarsler.
-# 
-# <p>Der er en vigtig indstilling mere: efter en vis tid -- hvor ingen
-# returmeddelelser dukker op -- regnes returinformation for at
-# v&aelig;re <a
-# href="?VARHELP=bounce/bounce_info_stale_after">for&aelig;ldet</a> og
-# stoppes. Ved at justere denne v&aelig;rdi, og s&aelig;tte en
-# gr&aelig;nse for returantallet, kan du bestemme hvor lang tid der skal
-# g&aring; f&oslash;r levering til et medlem stoppes. Begge disse
-# v&aelig;rdier b&oslash;r tilpasses efter hvor ofte og hvor meget
-# e-mail der sendes til din liste.
-
-# Ved at sætte denne værdi til Nej, slår du al automatisk tolkning af
-# returmeddelelser for denne liste fra. Bemærk at hvis meddelelser
-# afvises vil listeadministratoren ikke blive forstyrret med dem.
-#
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# These policies control the automatic bounce processing system in
+# Mailman.  Here's an overview of how it works.
+# 
+# <p>When a bounce is received, Mailman tries to extract two pieces of
+# information from the message: the address of the member the message
+# was intended for, and the severity of the problem causing the bounce.
+# The severity can be either <em>hard</em> or <em>soft</em> meaning
+# either a fatal error occurred, or a transient error occurred.  When in
+# doubt, a hard severity is used.
+# 
+# <p>If no member address can be extracted from the bounce, then the
+# bounce is usually discarded.  Otherwise, each member is assigned a
+# <em>bounce score</em> and every time we encounter a bounce from this
+# member we increment the score.  Hard bounces increment by 1 while soft
+# bounces increment by 0.5.  We only increment the bounce score once per
+# day, so even if we receive ten hard bounces from a member per day,
+# their score will increase by only 1 for that day.
+# 
+# <p>When a member's bounce score is greater than the <a
+# href="?VARHELP=bounce/bounce_score_threshold">bounce score
+# threshold</a>, the subscription is disabled.  Once disabled, the
+# member will not receive any postings from the list until their
+# membership is explicitly re-enabled (either by the list administrator
+# or the user).  However, they will receive occasional reminders that
+# their membership has been disabled, and these reminders will include
+# information about how to re-enable their membership.
+# 
+# <p>You can control both the <a
+# href="?VARHELP=bounce/bounce_you_are_disabled_warnings">number of
+# reminders</a> the member will receive and the <a
+# href="?VARHELP=bounce/bounce_you_are_disabled_warnings_interval"
+# >frequency</a> with which these reminders are sent.
+# 
+# <p>There is one other important configuration variable; after a
+# certain period of time -- during which no bounces from the member are
+# received -- the bounce information is <a
+# href="?VARHELP=bounce/bounce_info_stale_after">considered stale</a>
+# and discarded.  Thus by adjusting this value, and the score threshold,
+# you can control how quickly bouncing members are disabled.  You should
+# tune both of these to the frequency and traffic volume of your list.
+
+# By setting this value to No, you disable all automatic bounce
+# processing for this list, however bounce messages will still be
+# discarded so that the list administrator isn't inundated with them.
+#
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 bounce_processing = 1
 
-# Hvert medlem tildeles et returtal, og hver gang der kommer en
-# returmeddelelse vil dette tal &oslash;ges.  Alvorlige (&aring;rsager
-# f&oslash;rer til at det &oslash;ges med 1, mens harml&oslash;se
-# &aring;rsager f&oslash;rer til at det &oslash;ges med 0.5. Dette sker
-# kun &eacute;n gang pr. dag, s&aring; selv om der kommer 10 alvorlige
-# returmails fra et medlem p&aring; &eacute;n dag, vil tallet kun
-# &oslash;ges med 1.
-# 
-# Her s&aelig;ttes den &oslash;vre gr&aelig;nse for medlemmets returtal
-# Overskrides denne gr&aelig;nse stoppes levering automatisk, men
-# medlemmet bliver ikke fjernet fra listen.
+# Each subscriber is assigned a bounce score, as a floating point
+# number.  Whenever Mailman receives a bounce from a list member, that
+# member's score is incremented.  Hard bounces (fatal errors) increase
+# the score by 1, while soft bounces (temporary errors) increase the
+# score by 0.5.  Only one bounce per day counts against a member's
+# score, so even if 10 bounces are received for a member on the same
+# day, their score will increase by just 1.
+# 
+# This variable describes the upper limit for a member's bounce score,
+# above which they are automatically disabled, but not removed from the
+# mailing list.
 bounce_score_threshold = 5.0
 
-# Antal dage f&oslash;r returinformation stoppes hvis der ikke dukker
-# flere returmails op. Dette tal skal v&aelig;re et heltal.
+# The number of days after which a member's bounce information is
+# discarded, if no new bounces have been received in the interim.  This
+# value must be an integer.
 bounce_info_stale_after = 7
 
-# Hvor mange Levering til dig er stoppet advarsler der skal sendes til
-# et medlem f&oslash;r medlemmet frameldes listen. S&aelig;t denne værdi
-# til 0 for at fjerne et medlem fra listen straks, hvis der kommer
-# returmails fra medlemmets e-mailadresse. Dette tal skal være et
-# heltal.
+# How many Your Membership Is Disabled warnings a disabled member should
+# get before their address is removed from the mailing list.  Set to 0
+# to immediately remove an address from the list once their bounce score
+# exceeds the threshold.  This value must be an integer.
 bounce_you_are_disabled_warnings = 3
 
-# Antal dage imellem hver gang en Levering til dig er stoppet advarsel
-# skal sendes ud. Dette tal skal være et heltal.
+# The number of days between sending the Your Membership Is Disabled
+# warnings.  This value must be an integer.
 bounce_you_are_disabled_warnings_interval = 7
 
-# Mailmans automatiske returmailh&aring;ndtering er meget robust, men
-# det er alligevel umuligt at genkende alle typer returmails der kommer.
-# Du b&oslash;r v&aelig;lge Ja her, af to grunde: 1) Hvis det virkelig
-# er en permanent returmail fra et medlem af listen, b&oslash;r du
-# antagelig manuelt afmelde medlemmet fra listen, og 2) du vil
-# m&aring;ske sende en meddelelse til udviklerne af Mailman s&aring;dan
-# at returmails automatisk genkendes af Mailman i senere versioner. Hvis
-# du ikke vil g&oslash;re nogen af delene, s&aelig;ttes denne
-# indstilling til Nej. S&aring; vil alle returmails afvises automatisk
-# uden videre behandling. Bem&aelig;rk: Denne indstilling vil ogs&aring;
-# indvirke p&aring; al e-mail der sendes til listens -admin adresse. Den
-# adresse er for&aelig;ldet og udg&aring;et, men måske vil nogen
-# alligevel fortsat sende e-mail til den. Hvis nogen g&oslash;r det, og
-# du har sat denne indstilling til Nej, vil disse mails ogs&aring; blive
-# afvist. M&aring;ske vil du ogs&aring; ops&aelig;tte et automatisk svar
-# p&aring; e-mail sendt til -owner og -admin adresserne.
-#
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# While Mailman's bounce detector is fairly robust, it's impossible to
+# detect every bounce format in the world.  You should keep this
+# variable set to Yes for two reasons: 1) If this really is a permanent
+# bounce from one of your members, you should probably manually remove
+# them from your list, and 2) you might want to send the message on to
+# the Mailman developers so that this new format can be added to its
+# known set.
+# 
+# If you really can't be bothered, then set this variable to No and all
+# non-detected bounces will be discarded without further processing.
+# 
+# Note: This setting will also affect all messages sent to your list's
+# -admin address.  This address is deprecated and should never be used,
+# but some people may still send mail to this address.  If this happens,
+# and this variable is set to No those messages too will get discarded.
+# You may want to set up an autoresponse message for email to the -owner
+# and -admin address.
+#
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 bounce_unrecognized_goes_to_list_owner = 1
 
-# Ved at sætte denne til Nej, fravælges beskeden der normalt sendes til
-# ejer(e) af listen, når levering af e-mail til et medlem stoppes på
-# grund af for mange returmails. Der vil til gengæld altid blive forsøgt
-# afsendt en e-mail med besked til medlemmet.
+# By setting this value to No, you turn off notification messages that
+# are normally sent to the list owners when a member's delivery is
+# disabled due to excessive bounces. An attempt to notify the member
+# will always be made.
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 bounce_notify_owner_on_disable = 1
 
-# Ved at sætte denne til Nej, fravælges beskeden der normalt sendes til
-# ejer(e) af listen, når et medlem frameldes listen på grund af for
-# mange returmails. Der vil til gengæld altid blive forsøgt afsendt en
-# e-mail med besked til medlemmet.
+# By setting this value to No, you turn off notification messages that
+# are normally sent to the list owners when a member is unsubscribed due
+# to excessive bounces.  An attempt to notify the member will always be
+# made.
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 bounce_notify_owner_on_removal = 1
 
 ## Archive options
 #
-# Regler for arkivering
+# List traffic archival policies.
 
-# Arkiver e-mail i et arkiv?
+# Archive messages?
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 archive = 1
 
-# Skal arkivet v&aelig;re offentligt eller privat?
+# Is archive file source for public or private archival?
 #
-# gyldige værdier:
-#    0 = "Offentligt"
-#    1 = "Privat"
+# legal values are:
+#    0 = "public"
+#    1 = "private"
 archive_private = 0
 
-# Hvor ofte skal arkivet deles op?
+# How often should a new archive volume be started?
 #
-# gyldige værdier:
-#    0 = "&Aring;rlig"
-#    1 = "M&aring;nedlig"
-#    2 = "Kvartalsvis"
-#    3 = "Ugentlig"
-#    4 = "Daglig"
+# legal values are:
+#    0 = "Yearly"
+#    1 = "Monthly"
+#    2 = "Quarterly"
+#    3 = "Weekly"
+#    4 = "Daily"
 archive_volume_frequency = 1
 
 ## Gateway options
 #
-# E-mail-Til-Nyhedsgruppe og Nyhedsgruppe-Til-E-mail tjeneste.
+# Mail-to-News and News-to-Mail gateway services.
 
-# Nyhedsgruppe-tjeneste er ikke en del af Mailman. Du skal have adgang
-# til en eksisterende NNTP tjeneste, og maskinen som denne mailliste
-# k&oslash;rer p&aring; skal have adgang til at hente og afsende
-# meddelelser til NNTP tjenesten.
+# This value may be either the name of your news server, or optionally
+# of the format name:port, where port is a port number.
+# 
+# The news server is not part of Mailman proper.  You have to already
+# have access to an NNTP server, and that NNTP server must recognize the
+# machine this mailing list runs on as a machine capable of reading and
+# posting news.
 nntp_host = ''
 
-# Navn p&aring; nyhedsgruppe der skal sendes til og/eller fra.
+# The name of the Usenet group to gateway to and/or from.
 linked_newsgroup = ''
 
-# Skal nye meddelelser til denne liste sendes til nyhedsgruppen?
+# Should new posts to the mailing list be sent to the newsgroup?
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 gateway_to_news = 0
 
-# Skal nye meddelelser til nyhedsgruppen sendes til denne mailliste?
+# Should new posts to the newsgroup be sent to the mailing list?
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 gateway_to_mail = 0
 
-# Denne indstilling fort&aelig;ller Mailman hvilken slags
-# moderationsregler nyhedsgruppen har og hvordan de koordineres med
-# maillistens moderationsregler. Dette g&aelig;lder kun nyhedgrupper du
-# overfører meddelelser til, s&aring; hvis du kun overf&oslash;rer fra
-# en nyhedsgruppe, eller nyhedsgruppen du overf&oslash;rer til ikke er
-# modereret, s&aelig;ttes indstillingen til Ingen.
-# 
-# Hvis nyhedsgruppen er modereret, kan du s&aelig;tte maillisten til at
-# v&aelig;re moderationsadressen for nyhedsgruppen. Ved at vælge
-# Modereret, vil en ekstra meddelelse holdes tilbage i
-# godkendelsesprocessen. Al mail sendt til maillisten skal godkendes
-# f&oslash;r den sendes til nyhedsgruppen, eller til medlemmerne af
-# listen.
-# 
-# Vær opm&aelig;rksom p&aring; at hvis brevhovedet i mailen har et
-# Approved: felt med listens administrative adgangskode, vil denne regel
-# ikke blive benyttet. På den m&aring;de kan priviligerede afsendere
-# sende mail direkte til listen og nyhedsgruppen.
-# 
-# Hvis nyhedsgruppen er modereret, men du alligevel vil have en
-# &aring;ben liste, b&oslash;r du vælge Åben liste, modereret
-# nyhedsgruppe. S&aring; vil de s&aelig;dvanlige mekanismer for
-# moderation blive benyttet i Mailman, men alle meddelelser der sendes
-# til Usenet vil f&aring; et Approved felt i brevhovedet.
-#
-# gyldige værdier:
-#    0 = "Ingen"
-#    1 = "Åben liste, modereret nyhedsgruppe"
-#    2 = "Modereret"
+# This setting determines the moderation policy of the newsgroup and its
+# interaction with the moderation policy of the mailing list.  This only
+# applies to the newsgroup that you are gatewaying to, so if you are
+# only gatewaying from Usenet, or the newsgroup you are gatewaying to is
+# not moderated, set this option to None.
+# 
+# If the newsgroup is moderated, you can set this mailing list up to be
+# the moderation address for the newsgroup.  By selecting Moderated, an
+# additional posting hold will be placed in the approval process.  All
+# messages posted to the mailing list will have to be approved before
+# being sent on to the newsgroup, or to the mailing list membership.
+# 
+# Note that if the message has an Approved header with the list's
+# administrative password in it, this hold test will be bypassed,
+# allowing privileged posters to send messages directly to the list and
+# the newsgroup.
+# 
+# Finally, if the newsgroup is moderated, but you want to have an open
+# posting policy anyway, you should select Open list, moderated group.
+# The effect of this is to use the normal Mailman moderation facilities,
+# but to add an Approved header to all messages that are gatewayed to
+# Usenet.
+#
+# legal values are:
+#    0 = "None"
+#    1 = "Open list, moderated group"
+#    2 = "Moderated"
 news_moderation = 0
 
-# Mailman tilføjer normalt en tekst du selv kan tilrette (emne prefix)
-# foran emnefeltet i mail som sendes til listen, og normalt sker dette
-# også for mail som sendes videre til Usenet. Du kan sætte denne
-# indstilling til Nej hvis du ikke ønsker emne prefix tilføjet til mail
-# som sendes til Usenet. Sættes emne prefix for listen til off, vil
-# videresendte meddelelser heller ikke få prefix tilføjet.
+# Mailman prefixes Subject: headers with text you can customize and
+# normally, this prefix shows up in messages gatewayed to Usenet.  You
+# can set this option to No to disable the prefix on gated messages.  Of
+# course, if you turn off normal Subject: prefixes, they won't be
+# prefixed for gated messages either.
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 news_prefix_subject_too = 1
 
 ## Autoreply options
 #
-# Indstillinger for automatiske svar.<p>
+# Auto-responder characteristics.<p>
 # 
-# I tekstboksene nedenfor kan du bruge følgende variabler: (skriv:
-# %(&lt;variabelnavn&gt;)s ) for at indsætte ønsket information: <p><ul>
-# <li><b>listname</b> - <em>navnet p&aring; listen</em>
-# <li><b>listurl</b> - <em>URL til listens webside</em>
-# <li><b>requestemail</b> - <em>listens -request e-mailadresse</em>
-# <li><b>owneremail</b> - <em>listens -owner e-mailadresse</em> </ul>
+# In the text fields below, string interpolation is performed with the
+# following key/value substitutions: <p><ul> <li><b>listname</b> -
+# <em>gets the name of the mailing list</em> <li><b>listurl</b> -
+# <em>gets the list's listinfo URL</em> <li><b>requestemail</b> -
+# <em>gets the list's -request address</em> <li><b>owneremail</b> -
+# <em>gets the list's -owner address</em> </ul>
 # 
-# <p>Du kan enten skrive teksten direkte i tekstboksene, eller du kan
-# angive navnet p&aring; en fil som indeholder teksten. Denne fil vil
-# s&aring; blive indl&aelig;st i tekstboksen, fra dit lokale filsystem.
+# <p>For each text field, you can either enter the text directly into
+# the text box, or you can specify a file on your local system to upload
+# as the text.
 
-# Skal Mailman sende et automatisk svar til dem der sender e-mail til
-# listen?
+# Should Mailman send an auto-response to mailing list posters?
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 autorespond_postings = 0
 
-# Automatisk svar der skal sendes.
+# Auto-response text to send to mailing list posters.
 autoresponse_postings_text = ''
 
-# Skal Mailman sende et automatisk svar p&aring; e-mail der sendes til
-# -owner adressen?
+# Should Mailman send an auto-response to emails sent to the -owner
+# address?
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 autorespond_admin = 0
 
-# Automatisk svar p&aring; e-mail til -owner adressen.
+# Auto-response text to send to -owner emails.
 autoresponse_admin_text = ''
 
-# Skal Mailman sende et automatisk svar p&aring; e-mail der sendes til
-# -request adressen? Hvis du v&aelig;lger ja, kan du ogs&aring;
-# v&aelig;lge om e-mailen der blev sendt til -request adressen skal
-# medtages i det automatiske svar.
+# Should Mailman send an auto-response to emails sent to the -request
+# address?  If you choose yes, decide whether you want Mailman to
+# discard the original email, or forward it on to the system as a normal
+# mail command.
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja, men uden den originale e-mail"
-#    2 = "Ja, og medtag den originale e-mail"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes, w/discard"
+#    2 = "Yes, w/forward"
 autorespond_requests = 0
 
-# Automatisk svar p&aring; e-mail til -request adressen.
+# Auto-response text to send to -request emails.
 autoresponse_request_text = ''
 
-# Antal dage imellem automatisk svar p&aring; e-mail, fra samme
-# afsender, til listen eller til -request/-owner adresserne. S&aelig;t
-# denne v&aelig;rdi til 0 (eller et negativt tal) for at sende
-# automatisk svar hver gang.
+# Number of days between auto-responses to either the mailing list or
+# -request/-owner address from the same poster.  Set to zero (or
+# negative) for no grace period (i.e. auto-respond to every message).
 autoresponse_graceperiod = 90
 
 ## Contentfilter options
 #
-# Regler for indhold i e-mail sendt til listen.
-# 
-# <p>Filtrering af indhold fungerer således: når listen modtager en
-# e-mail og du har beskyttelse med filtrering af indhold aktiveret,
-# sammenlignes først eventuelle vedh&aelig;ftninger med <a
-# href="?VARHELP=contentfilter/filter_mime_types">MIME filtrene</a>.
-# Hvis en vedh&aelig;ftning passer med et af disse filtre, bliver
-# vedh&aelig;ftningen fjernet.
-# 
-# <p>Derefter sammenlignes eventuelle vedh&aelig;ftninger med <a
-# href="?VARHELP=contentfilter/pass_mime_types">gyldige MIME typer</a>,
-# hvis nogen er defineret. Alle vedh&aelig;ftninger som ikke stemmer
-# overens med de angivne MIME typer, bliver fjernet.
-# 
-# <p>Efter filtreringen vil alle tomme <tt>multipart</tt>
-# vedh&aelig;ftninger v&aelig;re fjernet. Hvis selve meddelelsen er helt
-# tom efter denne filtrering, vil meddelelsen blive afvist. Derefter vil
-# enhver <tt>multipart/alternative</tt> vedh&aelig;ftning blive
-# erstattet af den første alternative som ikke er tom.
-# 
-# <p>Til sidst vil alle <tt>text/html</tt> vedh&aelig;ftninger som måtte
-# v&aelig;re tilbage i meddelelsen blive konverteret til
-# <tt>text/plain</tt> hvis <a
-# href="?VARHELP=contentfilter/convert_html_to_plaintext">konverter til
-# ren tekst</a> er sat til og serveren er konfigureret til at tillade
-# sådanne konverteringer.
-
-# Skal Mailman filtrere indhold i e-mail sendt til listen som angivet
-# nedenfor?
-#
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# Policies concerning the content of list traffic.
+# 
+# <p>Content filtering works like this: when a message is received by
+# the list and you have enabled content filtering, the individual
+# attachments are first compared to the <a
+# href="?VARHELP=contentfilter/filter_mime_types">filter types</a>.  If
+# the attachment type matches an entry in the filter types, it is
+# discarded.
+# 
+# <p>Then, if there are <a
+# href="?VARHELP=contentfilter/pass_mime_types">pass types</a> defined,
+# any attachment type that does <em>not</em> match a pass type is also
+# discarded.  If there are no pass types defined, this check is skipped.
+# 
+# <p>After this initial filtering, any <tt>multipart</tt> attachments
+# that are empty are removed.  If the outer message is left empty after
+# this filtering, then the whole message is discarded.
+# 
+# <p> Then, each <tt>multipart/alternative</tt> section will be replaced
+# by just the first alternative that is non-empty after filtering if <a
+# href="?VARHELP=contentfilter/collapse_alternatives"
+# >collapse_alternatives</a> is enabled.
+# 
+# <p>Finally, any <tt>text/html</tt> parts that are left in the message
+# may be converted to <tt>text/plain</tt> if <a
+# href="?VARHELP=contentfilter/convert_html_to_plaintext"
+# >convert_html_to_plaintext</a> is enabled and the site is configured
+# to allow these conversions.
+
+# Should Mailman filter the content of list traffic according to the
+# settings below?
+#
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 filter_content = 0
 
-# Brug denne indstilling til at fjerne vedh&aelig;ftninger der passer
-# til MIME typer. Hver linie skal her indeholde navnet på en MIME
-# type/subtype, f.eks. image/gif. Hvis du ønsker at fjerne alle
-# vedh&aelig;ftninger som har en given hoved MIME type, kan du undlade
-# at angive subtype, f.eks. image.
+# Use this option to remove each message attachment that matches one of
+# these content types.  Each line should contain a string naming a MIME
+# type/subtype, e.g. image/gif.  Leave off the subtype to remove all
+# parts with a matching major content type, e.g. image.
 # 
-# Tomme linier medtages ikke.
+# Blank lines are ignored.
 # 
-# Se også gyldige MIME typer for whitelist af MIME typer.
+# See also <a href="?VARHELP=contentfilter/pass_mime_types"
+# >pass_mime_types for a content type whitelist.
 filter_mime_types = ''
 
-# Brug denne indstilling for at definere hvilke MIME typer der skal være
-# tilladt. Krav og format for filtrering er identisk med MIME filtre.
+# Use this option to remove each message attachment that does not have a
+# matching content type.  Requirements and formats are exactly like <a
+# href="?VARHELP=contentfilter/filter_mime_types" >filter_mime_types.
 # 
-# Bem&aelig;rk: hvis du lægger noget ind her, men ikke angiver
-# multipart, vil ingen e-mail med vedh&aelig;ftninger blive medtaget.
+# Note: if you add entries to this list but don't add multipart to this
+# list, any messages with attachments will be rejected by the pass
+# filter.
 pass_mime_types = """multipart/mixed
 multipart/alternative
 text/plain"""
 
-# Skal Mailman konvertere text/html dele til ren tekst? Denne
-# konvertering vil finde sted efter at MIME filteret har fjernet de
-# uønskede dele.
+# Remove message attachments that have a matching filename extension.
+filter_filename_extensions = """exe
+bat
+cmd
+com
+pif
+scr
+vbs
+cpl"""
+
+# Remove message attachments that don't have a matching filename
+# extension.  Leave this field blank to skip this filter test.
+pass_filename_extensions = ''
+
+# Should Mailman collapse multipart/alternative to its first part
+# content?
+#
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
+collapse_alternatives = True
+
+# Should Mailman convert text/html parts to plain text?  This conversion
+# happens after MIME attachments have been stripped.
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 convert_html_to_plaintext = 1
 
-# Her bestemmer du hvad der skal ske, når en meddelelse filtreres fra af
-# et filter, altså hvis vedh&aelig;ftningen filtreres fra af MIME
-# filteret, eller en vedh&aelig;ftning ikke har en af de gyldige MIME
-# typer, eller meddelelsen ender med at være tom efter filtrering.
-# 
-# Bemærk at det du vælger her ikke vil ske hvis en meddelelse stadig
-# indeholder noget efter filtrering. Så vil meddelelsen altid blive
-# sendt videre til listen.
-# 
-# Når meddelelsen afvises, skrives Message-ID for den afviste meddelelse
-# til loggen. Når meddelelsen sendes retur eller videresendes til
-# listens ejer, vil en begrundelse altid blive inkluderet i den
-# returmail der sendes til afsenderen. Når meddelelserne skal bevares,
-# gemmes de i et specielt køkatalog på disken, sådan at
-# serveradministrator kan se (og måske gøre noget med) dem, men bliver
-# ellers fjernet. Dette sidste valg er kun tilgængeligt hvis
-# serveradministrator har tilladt det.
-#
-# gyldige værdier:
-#    0 = "Slet"
-#    1 = "Afvis"
-#    2 = "Videresend til Listens Ejer"
-#    3 = "Bevar"
+# One of these actions is taken when the message matches one of the
+# content filtering rules, meaning, the top-level content type matches
+# one of the <a href="?VARHELP=contentfilter/filter_mime_types"
+# >filter_mime_types, or the top-level content type does not match one
+# of the <a href="?VARHELP=contentfilter/pass_mime_types"
+# >pass_mime_types, or if after filtering the subparts of the message,
+# the message ends up empty.
+# 
+# Note this action is not taken if after filtering the message still
+# contains content.  In that case the message is always forwarded on to
+# the list membership.
+# 
+# When messages are discarded, a log entry is written containing the
+# Message-ID of the discarded message.  When messages are rejected or
+# forwarded to the list owner, a reason for the rejection is included in
+# the bounce message to the original author.  When messages are
+# preserved, they are saved in a special queue directory on disk for the
+# site administrator to view (and possibly rescue) but otherwise
+# discarded.  This last option is only available if enabled by the site
+# administrator.
+#
+# legal values are:
+#    0 = "Discard"
+#    1 = "Reject"
+#    2 = "Forward to List Owner"
+#    3 = "Preserve"
 filter_action = 0
 
 ## Topics options
 #
-# Emneord for listen
-
-# Emnefilteret kategoriserer hver e-mail som kommer til listen, efter de
-# regexp-udtryk du skriver nedenfor. Hvis felterne Subject: eller
-# Keywords: i brevhovedet i en mail stemmer overens med et af disse
-# udtryk, bliver mailen placeret under det p&aring;g&aelig;ldende emne.
-# Hvert medlem af listen kan vælge kun at modtage mail der passer til de
-# &oslash;nskede emner. E-mail som ikke h&oslash;rer under noget emne,
-# bliver ikke leveret.
-# 
-# Bem&aeligrk: Dette fungerer kun i normal-modus, ikke i
-# sammendrag-modus.
-# 
-# Indholdet i meddelelsen kan ogs&aring; unders&oslash;ges for Subject:
-# og Keyword: felter, alt efter hvad indstillingen
-# topics_bodylines_limit er sat til.
+# List topic keywords
+
+# The topic filter categorizes each incoming email message according to
+# <a href="http://www.python.org/doc/current/lib/module-re.html">regular
+# expression filters you specify below.  If the message's Subject: or
+# Keywords: header contains a match against a topic filter, the message
+# is logically placed into a topic bucket.  Each user can then choose to
+# only receive messages from the mailing list for a particular topic
+# bucket (or buckets).  Any message not categorized in a topic bucket
+# registered with the user is not delivered to the list.
+# 
+# Note that this feature only works with regular delivery, not digest
+# delivery.
+# 
+# The body of the message can also be optionally scanned for Subject:
+# and Keywords: headers, as specified by the <a
+# href="?VARHELP=topics/topics_bodylines_limit">topics_bodylines_limit
+# configuration variable.
 #
-# gyldige værdier:
-#    0 = "Ikke tilgængeligt"
-#    1 = "Tilgængeligt"
+# legal values are:
+#    0 = "Disabled"
+#    1 = "Enabled"
 topics_enabled = 0
 
-# Her angiver du hvor mange linier af mailens indhold emnefilteret skal
-# gennems&oslash;ge. En s&oslash;gning stopper n&aring;r det antal
-# linier er gennems&oslash;gt, eller n&aring;r den m&oslash;der en linie
-# som ikke ligner et brevhoved-felt. S&aelig;ttes denne v&aelig;rdi til
-# nul (0), vil ingen linier i indholdet blive unders&oslash;gt (dvs. kun
-# Keywords: og Subject: i brevhovedet unders&oslash;ges). S&aelig;ttes
-# denne v&aelig;rdi til et negativt tal, vil alle linier blive
-# unders&oslash;gt frem til den f&oslash;rste linie som ikke ligner et
-# brevhoved-felt.
+# The topic matcher will scan this many lines of the message body
+# looking for topic keyword matches.  Body scanning stops when either
+# this many lines have been looked at, or a non-header-like body line is
+# encountered.  By setting this value to zero, no body lines will be
+# scanned (i.e. only the Keywords: and Subject: headers will be
+# scanned).  By setting this value to a negative number, then all body
+# lines will be scanned until a non-header-like line is encountered.
+# 
 topics_bodylines_limit = 5
 
-# Hvert emneord er faktisk et regexp-udtryk, der sammenlignes med dele
-# af mailen, nemlig felterne Keywords: og Subject: i brevhovedet.
-# Bem&aelig;rk at de f&oslash;rste linier i mailens indhold ogs&aring;
-# kan best&aring; af s&aring;danne "felter", og de kan dermed ogs&aring;
-# blive unders&oslash;gt.
+# Each topic keyword is actually a regular expression, which is matched
+# against certain parts of a mail message, specifically the Keywords:
+# and Subject: message headers. Note that the first few lines of the
+# body of the message can also contain a Keywords: and Subject: "header"
+# on which matching is also performed.
 topics = []
 
diff --git a/mailman/bestyrelse.members b/mailman/bestyrelse.members
index 79d4203..2786dae 100644
--- a/mailman/bestyrelse.members
+++ b/mailman/bestyrelse.members
@@ -1,8 +1,6 @@
 Anna Margrete Majgaard <Anna.Margrete.Majgaard@munksoegaard.dk>
 Lone Samuelsson <LOS@munksoegaard.dk>
 Bodil Arlif <bodil.arlif@munksoegaard.dk>
-Jacob B?kke <jacob_baekke@munksoegaard.dk>
 Niels Th?gersen <niels.thoegersen@munksoegaard.dk>
 Per Helmer Roos <per_roos@munksoegaard.dk>
 Siri Reiter <siri_snell_reiter@munksoegaard.dk>
-S?ren Magnusson <soeren_magnusson@munksoegaard.dk>
diff --git a/mailman/bestyrelse.py b/mailman/bestyrelse.py
index ec6864b..b0b25e1 100644
--- a/mailman/bestyrelse.py
+++ b/mailman/bestyrelse.py
@@ -1,5 +1,7 @@
-## Indstillinger for maillisten "bestyrelse"  -*- python -*-
-## Dato: Sun Dec 11 16:35:49 2005
+# -*- python -*-
+# -*- coding: iso-8859-1 -*-
+## "bestyrelse" mailing list configuration settings
+## captured on Tue Mar 20 08:52:03 2007
 
 ## General options
 #
@@ -74,11 +76,15 @@ info = """Lukket liste til bestyrelsen af Olinesgaard.
  * Alle kan se medlemmer af listen.
  * Emails arkiveres. Arkivet er kun for listens medlemmer."""
 
-# This text will be prepended to subject lines of messages posted to the
-# list, to distinguish mailing list messages in in mailbox summaries.
-# Brevity is premium here, it's ok to shorten long mailing list names to
-# something more concise, as long as it still identifies the mailing
-# list.
+# Denne tekst vil blive placeret foran emnet i mails sendt til listen
+# for nemmere og kunne skelne mail fra listen i indboksen i
+# postprogrammet. Teksten b&oslash;r holdes kort. Det er iorden og
+# sk&aelig;re et langt listenavn ned til et mere kortfattet navn
+# s&aring;l&aelig;nge det stadig er beskrivende for listen. Du kan
+# ogs&aring; tilf&oslash;je et fortl&oslash;bende nummer ved at bruge %d
+# substitutions direktivet f.eks. [listenavn %d] -> [listenavn 123]
+# (listenavn %05d) -> (listenavn 00123)
+# 
 subject_prefix = '[Oline bestyrelse] '
 
 # Skjul afsenderen af meddelelser, ved at erstatte den med e-maillistens
@@ -99,31 +105,32 @@ anonymous_list = False
 #    1 = "Ja"
 first_strip_reply_to = False
 
-# Denne indstillling fort&aelig;ller hvad Mailman skal g&oslash;re med
-# Reply-To: feltet i brevhovedet p&aring; e-mail der sendes til listen.
-# Hvis den er sat til Afsender, vil Mailman ikke tilf&oslash;je noget
-# Reply-To: felt, men findes et s&aring;dant felt allerede, vil det ikke
-# blive fjernet. S&aelig;ttes indstillingen til enten e-maillistens
-# adresse eller Egendefineret adresse, vil Mailman tilf&oslash;je, evt.
-# erstatte, et Reply-To: felt. (Egendefineret adresse inds&aelig;tter
-# v&aelig;rdien af indstillingen reply_to_address).
-# 
-# Der er flere grunde til ikke at indf&oslash;re eller erstatte
-# Reply-To: felter. En grund kan v&aelig;re at nogen af dem der sender
-# mail til listen er afh&aelig;ngige af selv at kunne s&aelig;tte
-# Reply-To: adressen. En anden grund er at modifikation af Reply-To:
-# adressen g&oslash;r det vanskeligere kun at sende svar til afsender.
-# Se 'Reply-To' Munging Considered Harmful for en diskussion omkring
-# emnet. Se Reply-To Munging Considered Useful for modsatte meninger.
-# 
-# Nogle maillister har begr&aelig;nset adgang, med en parallel liste
-# beregnet til diskussioner. Eksempler p&aring; dette er 'patches' eller
-# 'checkin' lister, som system for revisionskontrol sender
-# &aelig;ndringer i programmet til, men diskussioner omkring udvikling
-# af programmet sendes til udviklernes egen mailliste. For at
-# underst&oslash;tte lignende e-maillister, v&aelig;lg Egendefineret
-# adresse og s&aelig;t Reply-To: adressen i indstillingen
-# reply_to_address til at pege på den parallelle diskussionsliste.
+# This option controls what Mailman does to the Reply-To: header in
+# messages flowing through this mailing list.  When set to Poster, no
+# Reply-To: header is added by Mailman, although if one is present in
+# the original message, it is not stripped.  Setting this value to
+# either This list or Explicit address causes Mailman to insert a
+# specific Reply-To: header in all messages, overriding the header in
+# the original message if necessary (Explicit address inserts the value
+# of <a href="?VARHELP=general/reply_to_address">reply_to_address).
+# 
+# There are many reasons not to introduce or override the Reply-To:
+# header.  One is that some posters depend on their own Reply-To:
+# settings to convey their valid return address.  Another is that
+# modifying Reply-To: makes it much more difficult to send private
+# replies.  See <a
+# href="http://www.unicom.com/pw/reply-to-harmful.html">`Reply-To'
+# Munging Considered Harmful for a general discussion of this issue.
+# See <a
+# href="http://www.metasystema.net/essays/reply-to.mhtml">Reply-To
+# Munging Considered Useful for a dissenting opinion.
+# 
+# Some mailing lists have restricted posting privileges, with a parallel
+# list devoted to discussions.  Examples are `patches' or `checkin'
+# lists, where software changes are posted by a revision control system,
+# but discussion about the changes occurs on a developers mailing list.
+# To support these types of mailing lists, select Explicit address and
+# set the Reply-To: address below to point to the parallel list.
 #
 # gyldige værdier:
 #    0 = "Afsender"
@@ -131,29 +138,31 @@ first_strip_reply_to = False
 #    2 = "Egendefineret adresse"
 reply_goes_to_list = 0
 
-# Her definerer du adressen der skal s&aelig;ttes i Reply-To: feltet
-# n&aring;r indstillingen reply_goes_to_list er sat til Egendefineret
-# adresse.
-# 
-# Der findes mange grunde til at ikke indf&oslash;re eller erstatte
-# Reply-To: felter. En grund kan v&aelig;re at nogen af dem der sender
-# e-mail til listen er afh&aelig;ngige af selv at kunne s&aelig;tte
-# Reply-To: adressen. En anden grund er at modificering af Reply-To:
-# adressen g&oslash;r det vanskeligere at sende svar kun til afsender.
-# Se 'Reply-To' Munging Considered Harmful for en diskussion omkring
-# temaet. Se Reply-To Munging Considered Useful for modsatte meninger.
-# 
-# Nogle maillister har begr&aelig;nset adgang, med en egen parallel
-# liste beregnet for diskussioner. Eksempler p&aring; dette er 'patches'
-# eller 'checkin' lister, som system for revisionskontrol sender
-# &aelig;ndringer i programmet til, mens diskussioner omkring udvikling
-# af programmet sendes til udviklernes egen mailliste. For at
-# underst&oslash;tte s&aring;danne maillister, kan du definere Reply-To:
-# adressen her, og vælge Egendefineret adresse i indstillingen
-# reply_goes_to_list.
-# 
-# Bem&aelig;rk at hvis den oprindelige meddelelse indeholder et
-# Reply-To: felt, vil det ikke &aelig;ndres.
+# This is the address set in the Reply-To: header when the <a
+# href="?VARHELP=general/reply_goes_to_list">reply_goes_to_list option
+# is set to Explicit address.
+# 
+# There are many reasons not to introduce or override the Reply-To:
+# header.  One is that some posters depend on their own Reply-To:
+# settings to convey their valid return address.  Another is that
+# modifying Reply-To: makes it much more difficult to send private
+# replies.  See <a
+# href="http://www.unicom.com/pw/reply-to-harmful.html">`Reply-To'
+# Munging Considered Harmful for a general discussion of this issue.
+# See <a
+# href="http://www.metasystema.net/essays/reply-to.mhtml">Reply-To
+# Munging Considered Useful for a dissenting opinion.
+# 
+# Some mailing lists have restricted posting privileges, with a parallel
+# list devoted to discussions.  Examples are `patches' or `checkin'
+# lists, where software changes are posted by a revision control system,
+# but discussion about the changes occurs on a developers mailing list.
+# To support these types of mailing lists, specify the explicit
+# Reply-To: address here.  You must also specify Explicit address in the
+# reply_goes_to_list variable.
+# 
+# Note that if the original message contains a Reply-To: header, it will
+# not be changed.
 reply_to_address = ''
 
 # V&aelig;lg kun 'ja' her, hvis listen skal bruges som  "paraply" for
@@ -249,9 +258,8 @@ admin_immed_notify = True
 #    1 = "Ja"
 admin_notify_mchanges = False
 
-# Approval notices are sent when mail triggers certain of the limits
-# except routine list moderation and spam filters, for which notices are
-# not sent.  This option overrides ever sending the notice.
+# Send e-mail til afsendere n&aring;r deres e-mail til listen holdes
+# tilbage for godkendelse?
 #
 # gyldige værdier:
 #    0 = "Nej"
@@ -329,6 +337,10 @@ include_rfc2369_headers = 1
 #    1 = "Ja"
 include_list_post_header = 1
 
+# Slet alle tilbageholdte beskeder der er ældre end dette antal dage.
+# Brug 0 for at slå automatisk sletning fra.
+max_days_to_hold = 0
+
 ## Language options
 #
 # Underst&oslash;ttelse af flere sprog. (Internationalisering)
@@ -382,59 +394,57 @@ encode_ascii_prefixes = 2
 nondigestable = True
 
 # Tekst der tilføjes &oslash;verst i e-mail der sendes til listens
-# medlemmer. Teksten kan inneholde formateringskoder som byttes ut med
-# verdier fra listens oppsett. For detaljer, se Pythons
+# medlemmer. Teksten kan indeholde formateringskoder som udskiftes med
+# v&aelig;rdier fra listens ops&aelig;tning. For detaljer, se Pythons
 # formateringsregler (engelsk). Gyldige koder er:
 # 
 # 
 # real_name - Listens formaterede navn; normalt listenavnet med stort
 # forbogstav eller store bogstaver enkelte steder.
 # 
-# list_name - Listens navn som brugt i URLer, der det har betydning om
+# list_name - Listens navn som brugt i URLer, hvor det har betydning om
 # den staves med store eller sm&aring; bogstaver. (For
 # bagudkompatibilitet, er _internal_name det samme.)
 # 
-# host_name - Internetadressen (fully qulified domain name) til maskinen
-# som listeserveren g&aring;r p&aring;.
+# host_name - Internetadressen (fully qualified domain name) til
+# maskinen som listeserveren k&oslash;rer p&aring;.
 # 
-# web_page_url - Basis URL for Mailman. Denne kan laegges til sammen
-# med, f.eks. listinfo/%(internal_name)s for &aring; danne URLen til en
-# listes infoside.
+# web_page_url - Basis URL for Mailman. Denne kan kombineres med f.eks.
+# listinfo/%(list_name)s for at danne URLen til en listes infoside.
 # 
 # description - En kort beskrivelse af listen.
 # 
-# info - Full beskrivelse af listen.
+# info - Fuld beskrivelse af listen.
 # 
-# cgiext - Tillaeg som laegges til CGI scripts.
+# cgiext - Extension som tilf&oslash;jes CGI scripts.
 # 
 # 
 msg_header = ''
 
 # Tekst som tilf&oslash;jes nederst i e-mail der sendes til listens
-# medlemmer. Teksten kan inneholde formateringskoder som byttes ut med
-# verdier fra listens oppsett. For detaljer, se Pythons
+# medlemmer. Teksten kan indeholde formateringskoder som udskiftes med
+# v&aelig;rdier fra listens ops&aelig;tning. For detaljer, se Pythons
 # formateringsregler (engelsk). Gyldige koder er:
 # 
 # 
 # real_name - Listens formaterede navn; normalt listenavnet med stort
 # forbogstav eller store bogstaver enkelte steder.
 # 
-# list_name - Listens navn som brugt i URLer, der det har betydning om
+# list_name - Listens navn som brugt i URLer, hvor det har betydning om
 # den staves med store eller sm&aring; bogstaver. (For
 # bagudkompatibilitet, er _internal_name det samme.)
 # 
-# host_name - Internetadressen (fully qulified domain name) til maskinen
-# som listeserveren g&aring;r p&aring;.
+# host_name - Internetadressen (fully qualified domain name) til
+# maskinen som listeserveren k&oslash;rer p&aring;.
 # 
-# web_page_url - Basis URL for Mailman. Denne kan laegges til sammen
-# med, f.eks. listinfo/%(internal_name)s for &aring; danne URLen til en
-# listes infoside.
+# web_page_url - Basis URL for Mailman. Denne kan kombineres med f.eks.
+# listinfo/%(list_name)s for at danne URLen til en listes infoside.
 # 
 # description - En kort beskrivelse af listen.
 # 
-# info - Full beskrivelse af listen.
+# info - Fuld beskrivelse af listen.
 # 
-# cgiext - Tillaeg som laegges til CGI scripts.
+# cgiext - Extension som tilf&oslash;jes CGI scripts.
 # 
 # 
 msg_footer = """-- 
@@ -442,6 +452,17 @@ msg_footer = """--
 %(real_name)s@%(host_name)s
 %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s"""
 
+# Når du fjerner vedh&aelig;ftninger, gemmes de i et arkiv område og der
+# laves istedet links i e-mailen således at medlemmer kan tilgå
+# vedh&aelig;ftninger via en webbrowser. Hvis du vil have
+# vedh&aelig;ftninger til helt og forsvinde så kan du bruge et
+# indholdsfilter.
+#
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
+scrub_nondigest = False
+
 ## Digest options
 #
 # Opsætning af sammendrag-modus.
@@ -480,59 +501,57 @@ digest_size_threshhold = 300
 digest_send_periodic = True
 
 # Tekst som tilf&oslash;jes &oslash;verst i samle-emailen, f&oslash;r
-# indholdsfortegnelsen.Teksten kan inneholde formateringskoder som
-# byttes ut med verdier fra listens oppsett. For detaljer, se Pythons
-# formateringsregler (engelsk). Gyldige koder er:
+# indholdsfortegnelsen.Teksten kan indeholde formateringskoder som
+# udskiftes med v&aelig;rdier fra listens ops&aelig;tning. For detaljer,
+# se Pythons formateringsregler (engelsk). Gyldige koder er:
 # 
 # 
 # real_name - Listens formaterede navn; normalt listenavnet med stort
 # forbogstav eller store bogstaver enkelte steder.
 # 
-# list_name - Listens navn som brugt i URLer, der det har betydning om
+# list_name - Listens navn som brugt i URLer, hvor det har betydning om
 # den staves med store eller sm&aring; bogstaver. (For
 # bagudkompatibilitet, er _internal_name det samme.)
 # 
-# host_name - Internetadressen (fully qulified domain name) til maskinen
-# som listeserveren g&aring;r p&aring;.
+# host_name - Internetadressen (fully qualified domain name) til
+# maskinen som listeserveren k&oslash;rer p&aring;.
 # 
-# web_page_url - Basis URL for Mailman. Denne kan laegges til sammen
-# med, f.eks. listinfo/%(internal_name)s for &aring; danne URLen til en
-# listes infoside.
+# web_page_url - Basis URL for Mailman. Denne kan kombineres med f.eks.
+# listinfo/%(list_name)s for at danne URLen til en listes infoside.
 # 
 # description - En kort beskrivelse af listen.
 # 
-# info - Full beskrivelse af listen.
+# info - Fuld beskrivelse af listen.
 # 
-# cgiext - Tillaeg som laegges til CGI scripts.
+# cgiext - Extension som tilf&oslash;jes CGI scripts.
 # 
 # 
 digest_header = ''
 
 # Tekst der tilføjes nederst i hver samle-email, som sidste
-# information.Teksten kan inneholde formateringskoder som byttes ut med
-# verdier fra listens oppsett. For detaljer, se Pythons
+# information.Teksten kan indeholde formateringskoder som udskiftes med
+# v&aelig;rdier fra listens ops&aelig;tning. For detaljer, se Pythons
 # formateringsregler (engelsk). Gyldige koder er:
 # 
 # 
 # real_name - Listens formaterede navn; normalt listenavnet med stort
 # forbogstav eller store bogstaver enkelte steder.
 # 
-# list_name - Listens navn som brugt i URLer, der det har betydning om
+# list_name - Listens navn som brugt i URLer, hvor det har betydning om
 # den staves med store eller sm&aring; bogstaver. (For
 # bagudkompatibilitet, er _internal_name det samme.)
 # 
-# host_name - Internetadressen (fully qulified domain name) til maskinen
-# som listeserveren g&aring;r p&aring;.
+# host_name - Internetadressen (fully qualified domain name) til
+# maskinen som listeserveren k&oslash;rer p&aring;.
 # 
-# web_page_url - Basis URL for Mailman. Denne kan laegges til sammen
-# med, f.eks. listinfo/%(internal_name)s for &aring; danne URLen til en
-# listes infoside.
+# web_page_url - Basis URL for Mailman. Denne kan kombineres med f.eks.
+# listinfo/%(list_name)s for at danne URLen til en listes infoside.
 # 
 # description - En kort beskrivelse af listen.
 # 
-# info - Full beskrivelse af listen.
+# info - Fuld beskrivelse af listen.
 # 
-# cgiext - Tillaeg som laegges til CGI scripts.
+# cgiext - Extension som tilf&oslash;jes CGI scripts.
 # 
 # 
 digest_footer = """-- 
@@ -755,6 +774,12 @@ generic_nonmember_action = 0
 #    1 = "Ja"
 forward_auto_discards = 1
 
+# Tekst der skal inkluderes i en meddelelse om afvisning der sendes til
+# ikke-medlemmer der poster til listen. Denne meddelelse kan inkludere
+# listeejerens adresse vha. %(listowner)s og den erstatter den
+# automatisk konstruerede standard meddelelse.
+nonmember_rejection_notice = ''
+
 ## Privacy options
 #
 # Her kan du ops&aelig;tte filtrering baseret på modtageren af
@@ -812,15 +837,22 @@ max_num_recipients = 0
 # Her kan du opsætte forskellige anti-spam filtre, som kan bidrage til
 # at reducere mængden af spam der distribueres via e-maillisten.
 
-# Each header filter rule has two parts, a list of regular expressions,
-# one per line, and an action to take.  Mailman matches the message's
-# headers against every regular expression in the rule and if any match,
-# the message is rejected, held, or discarded based on the action you
-# specify.  Use Defer to temporarily disable a rule.
-# 
-# You can have more than one filter rule for your list.  In that case,
-# each rule is matched in turn, with processing stopped after the first
-# match.
+# Hver filterregel best&aring;r af to dele: en liste med regexp-udtryk,
+# et pr. linie, og en aktion der skal udf&oslash;res. Mailman
+# sammenligner meddelelsens brevhoved med alle regexp-udtryk i reglen,
+# og hvis der er overensstemmelse, vil meddelelsen blive afvist,
+# tilbageholdt eller slettet, afh&aelig;ngigt af hvilken aktion du har
+# angivet her. Brug Afvent for midlertidigt at s&aelig;tte en regel ud
+# af kraft.
+# 
+# Du kan have flere end en regel for din liste.  I s&aring; fald vil
+# hver regel blive anvendt efter tur, og processen stopper f&oslash;rste
+# gang der findes overensstemmelse.
+# 
+# Bemærk at brevhovedlinier indsamles fra alle vedh&aelig;ftninger
+# (undtagen fra mailman administrivia meddelelser) og sammenlignes med
+# regexp-udtrykkene. Ved brug af denne funktionalitet kan du effektivt
+# sortere meddelelser fra med farlige filtyper eller filnavn-endelser.
 header_filter_rules = []
 
 # Brug denne indstilling til at bortfiltrere mail til listen, baseret
@@ -1127,32 +1159,34 @@ autoresponse_graceperiod = 90
 
 ## Contentfilter options
 #
-# Regler for indhold i e-mail sendt til listen.
-# 
-# <p>Filtrering af indhold fungerer således: når listen modtager en
-# e-mail og du har beskyttelse med filtrering af indhold aktiveret,
-# sammenlignes først eventuelle vedh&aelig;ftninger med <a
-# href="?VARHELP=contentfilter/filter_mime_types">MIME filtrene</a>.
-# Hvis en vedh&aelig;ftning passer med et af disse filtre, bliver
-# vedh&aelig;ftningen fjernet.
-# 
-# <p>Derefter sammenlignes eventuelle vedh&aelig;ftninger med <a
-# href="?VARHELP=contentfilter/pass_mime_types">gyldige MIME typer</a>,
-# hvis nogen er defineret. Alle vedh&aelig;ftninger som ikke stemmer
-# overens med de angivne MIME typer, bliver fjernet.
-# 
-# <p>Efter filtreringen vil alle tomme <tt>multipart</tt>
-# vedh&aelig;ftninger v&aelig;re fjernet. Hvis selve meddelelsen er helt
-# tom efter denne filtrering, vil meddelelsen blive afvist. Derefter vil
-# enhver <tt>multipart/alternative</tt> vedh&aelig;ftning blive
-# erstattet af den første alternative som ikke er tom.
-# 
-# <p>Til sidst vil alle <tt>text/html</tt> vedh&aelig;ftninger som måtte
-# v&aelig;re tilbage i meddelelsen blive konverteret til
-# <tt>text/plain</tt> hvis <a
-# href="?VARHELP=contentfilter/convert_html_to_plaintext">konverter til
-# ren tekst</a> er sat til og serveren er konfigureret til at tillade
-# sådanne konverteringer.
+# Policies concerning the content of list traffic.
+# 
+# <p>Content filtering works like this: when a message is received by
+# the list and you have enabled content filtering, the individual
+# attachments are first compared to the <a
+# href="?VARHELP=contentfilter/filter_mime_types">filter types</a>.  If
+# the attachment type matches an entry in the filter types, it is
+# discarded.
+# 
+# <p>Then, if there are <a
+# href="?VARHELP=contentfilter/pass_mime_types">pass types</a> defined,
+# any attachment type that does <em>not</em> match a pass type is also
+# discarded.  If there are no pass types defined, this check is skipped.
+# 
+# <p>After this initial filtering, any <tt>multipart</tt> attachments
+# that are empty are removed.  If the outer message is left empty after
+# this filtering, then the whole message is discarded.
+# 
+# <p> Then, each <tt>multipart/alternative</tt> section will be replaced
+# by just the first alternative that is non-empty after filtering if <a
+# href="?VARHELP=contentfilter/collapse_alternatives"
+# >collapse_alternatives</a> is enabled.
+# 
+# <p>Finally, any <tt>text/html</tt> parts that are left in the message
+# may be converted to <tt>text/plain</tt> if <a
+# href="?VARHELP=contentfilter/convert_html_to_plaintext"
+# >convert_html_to_plaintext</a> is enabled and the site is configured
+# to allow these conversions.
 
 # Skal Mailman filtrere indhold i e-mail sendt til listen som angivet
 # nedenfor?
@@ -1182,6 +1216,28 @@ pass_mime_types = """multipart/mixed
 multipart/alternative
 text/plain"""
 
+# Fjern e-mailvedh&aelig;ftninger med passende filnavn-endelser.
+filter_filename_extensions = """exe
+bat
+cmd
+com
+pif
+scr
+vbs
+cpl"""
+
+# Fjern alle vedh&aelig;ftninger der ikke har en passende
+# filnavn-endelse. Lad dette felt være tomt for at udelade dette filter.
+pass_filename_extensions = ''
+
+# Should Mailman collapse multipart/alternative to its first part
+# content?
+#
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
+collapse_alternatives = True
+
 # Skal Mailman konvertere text/html dele til ren tekst? Denne
 # konvertering vil finde sted efter at MIME filteret har fjernet de
 # uønskede dele.
diff --git a/mailman/debat.py b/mailman/debat.py
index 0a936b6..2eeab00 100644
--- a/mailman/debat.py
+++ b/mailman/debat.py
@@ -1,5 +1,7 @@
-## Indstillinger for maillisten "debat"  -*- python -*-
-## Dato: Sun Dec 11 16:35:50 2005
+# -*- python -*-
+# -*- coding: iso-8859-1 -*-
+## "debat" mailing list configuration settings
+## captured on Tue Mar 20 08:52:09 2007
 
 ## General options
 #
@@ -75,11 +77,15 @@ info = """&Aring;ben liste til l&oslash;st og fast om Olineg&aring;rd-aktivitete
  * Emails arkiveres. Arkivet er offentligt tilg&aelig;ngeligt.
  * Alle kan tilmelde sig listen."""
 
-# This text will be prepended to subject lines of messages posted to the
-# list, to distinguish mailing list messages in in mailbox summaries.
-# Brevity is premium here, it's ok to shorten long mailing list names to
-# something more concise, as long as it still identifies the mailing
-# list.
+# Denne tekst vil blive placeret foran emnet i mails sendt til listen
+# for nemmere og kunne skelne mail fra listen i indboksen i
+# postprogrammet. Teksten b&oslash;r holdes kort. Det er iorden og
+# sk&aelig;re et langt listenavn ned til et mere kortfattet navn
+# s&aring;l&aelig;nge det stadig er beskrivende for listen. Du kan
+# ogs&aring; tilf&oslash;je et fortl&oslash;bende nummer ved at bruge %d
+# substitutions direktivet f.eks. [listenavn %d] -> [listenavn 123]
+# (listenavn %05d) -> (listenavn 00123)
+# 
 subject_prefix = '[Oline debat] '
 
 # Skjul afsenderen af meddelelser, ved at erstatte den med e-maillistens
@@ -100,31 +106,32 @@ anonymous_list = False
 #    1 = "Ja"
 first_strip_reply_to = False
 
-# Denne indstillling fort&aelig;ller hvad Mailman skal g&oslash;re med
-# Reply-To: feltet i brevhovedet p&aring; e-mail der sendes til listen.
-# Hvis den er sat til Afsender, vil Mailman ikke tilf&oslash;je noget
-# Reply-To: felt, men findes et s&aring;dant felt allerede, vil det ikke
-# blive fjernet. S&aelig;ttes indstillingen til enten e-maillistens
-# adresse eller Egendefineret adresse, vil Mailman tilf&oslash;je, evt.
-# erstatte, et Reply-To: felt. (Egendefineret adresse inds&aelig;tter
-# v&aelig;rdien af indstillingen reply_to_address).
-# 
-# Der er flere grunde til ikke at indf&oslash;re eller erstatte
-# Reply-To: felter. En grund kan v&aelig;re at nogen af dem der sender
-# mail til listen er afh&aelig;ngige af selv at kunne s&aelig;tte
-# Reply-To: adressen. En anden grund er at modifikation af Reply-To:
-# adressen g&oslash;r det vanskeligere kun at sende svar til afsender.
-# Se 'Reply-To' Munging Considered Harmful for en diskussion omkring
-# emnet. Se Reply-To Munging Considered Useful for modsatte meninger.
-# 
-# Nogle maillister har begr&aelig;nset adgang, med en parallel liste
-# beregnet til diskussioner. Eksempler p&aring; dette er 'patches' eller
-# 'checkin' lister, som system for revisionskontrol sender
-# &aelig;ndringer i programmet til, men diskussioner omkring udvikling
-# af programmet sendes til udviklernes egen mailliste. For at
-# underst&oslash;tte lignende e-maillister, v&aelig;lg Egendefineret
-# adresse og s&aelig;t Reply-To: adressen i indstillingen
-# reply_to_address til at pege på den parallelle diskussionsliste.
+# This option controls what Mailman does to the Reply-To: header in
+# messages flowing through this mailing list.  When set to Poster, no
+# Reply-To: header is added by Mailman, although if one is present in
+# the original message, it is not stripped.  Setting this value to
+# either This list or Explicit address causes Mailman to insert a
+# specific Reply-To: header in all messages, overriding the header in
+# the original message if necessary (Explicit address inserts the value
+# of <a href="?VARHELP=general/reply_to_address">reply_to_address).
+# 
+# There are many reasons not to introduce or override the Reply-To:
+# header.  One is that some posters depend on their own Reply-To:
+# settings to convey their valid return address.  Another is that
+# modifying Reply-To: makes it much more difficult to send private
+# replies.  See <a
+# href="http://www.unicom.com/pw/reply-to-harmful.html">`Reply-To'
+# Munging Considered Harmful for a general discussion of this issue.
+# See <a
+# href="http://www.metasystema.net/essays/reply-to.mhtml">Reply-To
+# Munging Considered Useful for a dissenting opinion.
+# 
+# Some mailing lists have restricted posting privileges, with a parallel
+# list devoted to discussions.  Examples are `patches' or `checkin'
+# lists, where software changes are posted by a revision control system,
+# but discussion about the changes occurs on a developers mailing list.
+# To support these types of mailing lists, select Explicit address and
+# set the Reply-To: address below to point to the parallel list.
 #
 # gyldige værdier:
 #    0 = "Afsender"
@@ -132,29 +139,31 @@ first_strip_reply_to = False
 #    2 = "Egendefineret adresse"
 reply_goes_to_list = 0
 
-# Her definerer du adressen der skal s&aelig;ttes i Reply-To: feltet
-# n&aring;r indstillingen reply_goes_to_list er sat til Egendefineret
-# adresse.
-# 
-# Der findes mange grunde til at ikke indf&oslash;re eller erstatte
-# Reply-To: felter. En grund kan v&aelig;re at nogen af dem der sender
-# e-mail til listen er afh&aelig;ngige af selv at kunne s&aelig;tte
-# Reply-To: adressen. En anden grund er at modificering af Reply-To:
-# adressen g&oslash;r det vanskeligere at sende svar kun til afsender.
-# Se 'Reply-To' Munging Considered Harmful for en diskussion omkring
-# temaet. Se Reply-To Munging Considered Useful for modsatte meninger.
-# 
-# Nogle maillister har begr&aelig;nset adgang, med en egen parallel
-# liste beregnet for diskussioner. Eksempler p&aring; dette er 'patches'
-# eller 'checkin' lister, som system for revisionskontrol sender
-# &aelig;ndringer i programmet til, mens diskussioner omkring udvikling
-# af programmet sendes til udviklernes egen mailliste. For at
-# underst&oslash;tte s&aring;danne maillister, kan du definere Reply-To:
-# adressen her, og vælge Egendefineret adresse i indstillingen
-# reply_goes_to_list.
-# 
-# Bem&aelig;rk at hvis den oprindelige meddelelse indeholder et
-# Reply-To: felt, vil det ikke &aelig;ndres.
+# This is the address set in the Reply-To: header when the <a
+# href="?VARHELP=general/reply_goes_to_list">reply_goes_to_list option
+# is set to Explicit address.
+# 
+# There are many reasons not to introduce or override the Reply-To:
+# header.  One is that some posters depend on their own Reply-To:
+# settings to convey their valid return address.  Another is that
+# modifying Reply-To: makes it much more difficult to send private
+# replies.  See <a
+# href="http://www.unicom.com/pw/reply-to-harmful.html">`Reply-To'
+# Munging Considered Harmful for a general discussion of this issue.
+# See <a
+# href="http://www.metasystema.net/essays/reply-to.mhtml">Reply-To
+# Munging Considered Useful for a dissenting opinion.
+# 
+# Some mailing lists have restricted posting privileges, with a parallel
+# list devoted to discussions.  Examples are `patches' or `checkin'
+# lists, where software changes are posted by a revision control system,
+# but discussion about the changes occurs on a developers mailing list.
+# To support these types of mailing lists, specify the explicit
+# Reply-To: address here.  You must also specify Explicit address in the
+# reply_goes_to_list variable.
+# 
+# Note that if the original message contains a Reply-To: header, it will
+# not be changed.
 reply_to_address = ''
 
 # V&aelig;lg kun 'ja' her, hvis listen skal bruges som  "paraply" for
@@ -251,9 +260,8 @@ admin_immed_notify = True
 #    1 = "Ja"
 admin_notify_mchanges = False
 
-# Approval notices are sent when mail triggers certain of the limits
-# except routine list moderation and spam filters, for which notices are
-# not sent.  This option overrides ever sending the notice.
+# Send e-mail til afsendere n&aring;r deres e-mail til listen holdes
+# tilbage for godkendelse?
 #
 # gyldige værdier:
 #    0 = "Nej"
@@ -331,6 +339,10 @@ include_rfc2369_headers = 1
 #    1 = "Ja"
 include_list_post_header = 1
 
+# Slet alle tilbageholdte beskeder der er ældre end dette antal dage.
+# Brug 0 for at slå automatisk sletning fra.
+max_days_to_hold = 0
+
 ## Language options
 #
 # Underst&oslash;ttelse af flere sprog. (Internationalisering)
@@ -384,59 +396,57 @@ encode_ascii_prefixes = 2
 nondigestable = True
 
 # Tekst der tilføjes &oslash;verst i e-mail der sendes til listens
-# medlemmer. Teksten kan inneholde formateringskoder som byttes ut med
-# verdier fra listens oppsett. For detaljer, se Pythons
+# medlemmer. Teksten kan indeholde formateringskoder som udskiftes med
+# v&aelig;rdier fra listens ops&aelig;tning. For detaljer, se Pythons
 # formateringsregler (engelsk). Gyldige koder er:
 # 
 # 
 # real_name - Listens formaterede navn; normalt listenavnet med stort
 # forbogstav eller store bogstaver enkelte steder.
 # 
-# list_name - Listens navn som brugt i URLer, der det har betydning om
+# list_name - Listens navn som brugt i URLer, hvor det har betydning om
 # den staves med store eller sm&aring; bogstaver. (For
 # bagudkompatibilitet, er _internal_name det samme.)
 # 
-# host_name - Internetadressen (fully qulified domain name) til maskinen
-# som listeserveren g&aring;r p&aring;.
+# host_name - Internetadressen (fully qualified domain name) til
+# maskinen som listeserveren k&oslash;rer p&aring;.
 # 
-# web_page_url - Basis URL for Mailman. Denne kan laegges til sammen
-# med, f.eks. listinfo/%(internal_name)s for &aring; danne URLen til en
-# listes infoside.
+# web_page_url - Basis URL for Mailman. Denne kan kombineres med f.eks.
+# listinfo/%(list_name)s for at danne URLen til en listes infoside.
 # 
 # description - En kort beskrivelse af listen.
 # 
-# info - Full beskrivelse af listen.
+# info - Fuld beskrivelse af listen.
 # 
-# cgiext - Tillaeg som laegges til CGI scripts.
+# cgiext - Extension som tilf&oslash;jes CGI scripts.
 # 
 # 
 msg_header = ''
 
 # Tekst som tilf&oslash;jes nederst i e-mail der sendes til listens
-# medlemmer. Teksten kan inneholde formateringskoder som byttes ut med
-# verdier fra listens oppsett. For detaljer, se Pythons
+# medlemmer. Teksten kan indeholde formateringskoder som udskiftes med
+# v&aelig;rdier fra listens ops&aelig;tning. For detaljer, se Pythons
 # formateringsregler (engelsk). Gyldige koder er:
 # 
 # 
 # real_name - Listens formaterede navn; normalt listenavnet med stort
 # forbogstav eller store bogstaver enkelte steder.
 # 
-# list_name - Listens navn som brugt i URLer, der det har betydning om
+# list_name - Listens navn som brugt i URLer, hvor det har betydning om
 # den staves med store eller sm&aring; bogstaver. (For
 # bagudkompatibilitet, er _internal_name det samme.)
 # 
-# host_name - Internetadressen (fully qulified domain name) til maskinen
-# som listeserveren g&aring;r p&aring;.
+# host_name - Internetadressen (fully qualified domain name) til
+# maskinen som listeserveren k&oslash;rer p&aring;.
 # 
-# web_page_url - Basis URL for Mailman. Denne kan laegges til sammen
-# med, f.eks. listinfo/%(internal_name)s for &aring; danne URLen til en
-# listes infoside.
+# web_page_url - Basis URL for Mailman. Denne kan kombineres med f.eks.
+# listinfo/%(list_name)s for at danne URLen til en listes infoside.
 # 
 # description - En kort beskrivelse af listen.
 # 
-# info - Full beskrivelse af listen.
+# info - Fuld beskrivelse af listen.
 # 
-# cgiext - Tillaeg som laegges til CGI scripts.
+# cgiext - Extension som tilf&oslash;jes CGI scripts.
 # 
 # 
 msg_footer = """-- 
@@ -444,6 +454,17 @@ msg_footer = """--
 %(real_name)s@%(host_name)s
 %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s"""
 
+# Når du fjerner vedh&aelig;ftninger, gemmes de i et arkiv område og der
+# laves istedet links i e-mailen således at medlemmer kan tilgå
+# vedh&aelig;ftninger via en webbrowser. Hvis du vil have
+# vedh&aelig;ftninger til helt og forsvinde så kan du bruge et
+# indholdsfilter.
+#
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
+scrub_nondigest = False
+
 ## Digest options
 #
 # Opsætning af sammendrag-modus.
@@ -482,59 +503,57 @@ digest_size_threshhold = 300
 digest_send_periodic = True
 
 # Tekst som tilf&oslash;jes &oslash;verst i samle-emailen, f&oslash;r
-# indholdsfortegnelsen.Teksten kan inneholde formateringskoder som
-# byttes ut med verdier fra listens oppsett. For detaljer, se Pythons
-# formateringsregler (engelsk). Gyldige koder er:
+# indholdsfortegnelsen.Teksten kan indeholde formateringskoder som
+# udskiftes med v&aelig;rdier fra listens ops&aelig;tning. For detaljer,
+# se Pythons formateringsregler (engelsk). Gyldige koder er:
 # 
 # 
 # real_name - Listens formaterede navn; normalt listenavnet med stort
 # forbogstav eller store bogstaver enkelte steder.
 # 
-# list_name - Listens navn som brugt i URLer, der det har betydning om
+# list_name - Listens navn som brugt i URLer, hvor det har betydning om
 # den staves med store eller sm&aring; bogstaver. (For
 # bagudkompatibilitet, er _internal_name det samme.)
 # 
-# host_name - Internetadressen (fully qulified domain name) til maskinen
-# som listeserveren g&aring;r p&aring;.
+# host_name - Internetadressen (fully qualified domain name) til
+# maskinen som listeserveren k&oslash;rer p&aring;.
 # 
-# web_page_url - Basis URL for Mailman. Denne kan laegges til sammen
-# med, f.eks. listinfo/%(internal_name)s for &aring; danne URLen til en
-# listes infoside.
+# web_page_url - Basis URL for Mailman. Denne kan kombineres med f.eks.
+# listinfo/%(list_name)s for at danne URLen til en listes infoside.
 # 
 # description - En kort beskrivelse af listen.
 # 
-# info - Full beskrivelse af listen.
+# info - Fuld beskrivelse af listen.
 # 
-# cgiext - Tillaeg som laegges til CGI scripts.
+# cgiext - Extension som tilf&oslash;jes CGI scripts.
 # 
 # 
 digest_header = ''
 
 # Tekst der tilføjes nederst i hver samle-email, som sidste
-# information.Teksten kan inneholde formateringskoder som byttes ut med
-# verdier fra listens oppsett. For detaljer, se Pythons
+# information.Teksten kan indeholde formateringskoder som udskiftes med
+# v&aelig;rdier fra listens ops&aelig;tning. For detaljer, se Pythons
 # formateringsregler (engelsk). Gyldige koder er:
 # 
 # 
 # real_name - Listens formaterede navn; normalt listenavnet med stort
 # forbogstav eller store bogstaver enkelte steder.
 # 
-# list_name - Listens navn som brugt i URLer, der det har betydning om
+# list_name - Listens navn som brugt i URLer, hvor det har betydning om
 # den staves med store eller sm&aring; bogstaver. (For
 # bagudkompatibilitet, er _internal_name det samme.)
 # 
-# host_name - Internetadressen (fully qulified domain name) til maskinen
-# som listeserveren g&aring;r p&aring;.
+# host_name - Internetadressen (fully qualified domain name) til
+# maskinen som listeserveren k&oslash;rer p&aring;.
 # 
-# web_page_url - Basis URL for Mailman. Denne kan laegges til sammen
-# med, f.eks. listinfo/%(internal_name)s for &aring; danne URLen til en
-# listes infoside.
+# web_page_url - Basis URL for Mailman. Denne kan kombineres med f.eks.
+# listinfo/%(list_name)s for at danne URLen til en listes infoside.
 # 
 # description - En kort beskrivelse af listen.
 # 
-# info - Full beskrivelse af listen.
+# info - Fuld beskrivelse af listen.
 # 
-# cgiext - Tillaeg som laegges til CGI scripts.
+# cgiext - Extension som tilf&oslash;jes CGI scripts.
 # 
 # 
 digest_footer = """-- 
@@ -757,6 +776,12 @@ generic_nonmember_action = 0
 #    1 = "Ja"
 forward_auto_discards = 1
 
+# Tekst der skal inkluderes i en meddelelse om afvisning der sendes til
+# ikke-medlemmer der poster til listen. Denne meddelelse kan inkludere
+# listeejerens adresse vha. %(listowner)s og den erstatter den
+# automatisk konstruerede standard meddelelse.
+nonmember_rejection_notice = ''
+
 ## Privacy options
 #
 # Her kan du ops&aelig;tte filtrering baseret på modtageren af
@@ -814,15 +839,22 @@ max_num_recipients = 10
 # Her kan du opsætte forskellige anti-spam filtre, som kan bidrage til
 # at reducere mængden af spam der distribueres via e-maillisten.
 
-# Each header filter rule has two parts, a list of regular expressions,
-# one per line, and an action to take.  Mailman matches the message's
-# headers against every regular expression in the rule and if any match,
-# the message is rejected, held, or discarded based on the action you
-# specify.  Use Defer to temporarily disable a rule.
-# 
-# You can have more than one filter rule for your list.  In that case,
-# each rule is matched in turn, with processing stopped after the first
-# match.
+# Hver filterregel best&aring;r af to dele: en liste med regexp-udtryk,
+# et pr. linie, og en aktion der skal udf&oslash;res. Mailman
+# sammenligner meddelelsens brevhoved med alle regexp-udtryk i reglen,
+# og hvis der er overensstemmelse, vil meddelelsen blive afvist,
+# tilbageholdt eller slettet, afh&aelig;ngigt af hvilken aktion du har
+# angivet her. Brug Afvent for midlertidigt at s&aelig;tte en regel ud
+# af kraft.
+# 
+# Du kan have flere end en regel for din liste.  I s&aring; fald vil
+# hver regel blive anvendt efter tur, og processen stopper f&oslash;rste
+# gang der findes overensstemmelse.
+# 
+# Bemærk at brevhovedlinier indsamles fra alle vedh&aelig;ftninger
+# (undtagen fra mailman administrivia meddelelser) og sammenlignes med
+# regexp-udtrykkene. Ved brug af denne funktionalitet kan du effektivt
+# sortere meddelelser fra med farlige filtyper eller filnavn-endelser.
 header_filter_rules = []
 
 # Brug denne indstilling til at bortfiltrere mail til listen, baseret
@@ -1129,32 +1161,34 @@ autoresponse_graceperiod = 90
 
 ## Contentfilter options
 #
-# Regler for indhold i e-mail sendt til listen.
-# 
-# <p>Filtrering af indhold fungerer således: når listen modtager en
-# e-mail og du har beskyttelse med filtrering af indhold aktiveret,
-# sammenlignes først eventuelle vedh&aelig;ftninger med <a
-# href="?VARHELP=contentfilter/filter_mime_types">MIME filtrene</a>.
-# Hvis en vedh&aelig;ftning passer med et af disse filtre, bliver
-# vedh&aelig;ftningen fjernet.
-# 
-# <p>Derefter sammenlignes eventuelle vedh&aelig;ftninger med <a
-# href="?VARHELP=contentfilter/pass_mime_types">gyldige MIME typer</a>,
-# hvis nogen er defineret. Alle vedh&aelig;ftninger som ikke stemmer
-# overens med de angivne MIME typer, bliver fjernet.
-# 
-# <p>Efter filtreringen vil alle tomme <tt>multipart</tt>
-# vedh&aelig;ftninger v&aelig;re fjernet. Hvis selve meddelelsen er helt
-# tom efter denne filtrering, vil meddelelsen blive afvist. Derefter vil
-# enhver <tt>multipart/alternative</tt> vedh&aelig;ftning blive
-# erstattet af den første alternative som ikke er tom.
-# 
-# <p>Til sidst vil alle <tt>text/html</tt> vedh&aelig;ftninger som måtte
-# v&aelig;re tilbage i meddelelsen blive konverteret til
-# <tt>text/plain</tt> hvis <a
-# href="?VARHELP=contentfilter/convert_html_to_plaintext">konverter til
-# ren tekst</a> er sat til og serveren er konfigureret til at tillade
-# sådanne konverteringer.
+# Policies concerning the content of list traffic.
+# 
+# <p>Content filtering works like this: when a message is received by
+# the list and you have enabled content filtering, the individual
+# attachments are first compared to the <a
+# href="?VARHELP=contentfilter/filter_mime_types">filter types</a>.  If
+# the attachment type matches an entry in the filter types, it is
+# discarded.
+# 
+# <p>Then, if there are <a
+# href="?VARHELP=contentfilter/pass_mime_types">pass types</a> defined,
+# any attachment type that does <em>not</em> match a pass type is also
+# discarded.  If there are no pass types defined, this check is skipped.
+# 
+# <p>After this initial filtering, any <tt>multipart</tt> attachments
+# that are empty are removed.  If the outer message is left empty after
+# this filtering, then the whole message is discarded.
+# 
+# <p> Then, each <tt>multipart/alternative</tt> section will be replaced
+# by just the first alternative that is non-empty after filtering if <a
+# href="?VARHELP=contentfilter/collapse_alternatives"
+# >collapse_alternatives</a> is enabled.
+# 
+# <p>Finally, any <tt>text/html</tt> parts that are left in the message
+# may be converted to <tt>text/plain</tt> if <a
+# href="?VARHELP=contentfilter/convert_html_to_plaintext"
+# >convert_html_to_plaintext</a> is enabled and the site is configured
+# to allow these conversions.
 
 # Skal Mailman filtrere indhold i e-mail sendt til listen som angivet
 # nedenfor?
@@ -1184,6 +1218,28 @@ pass_mime_types = """multipart/mixed
 multipart/alternative
 text/plain"""
 
+# Fjern e-mailvedh&aelig;ftninger med passende filnavn-endelser.
+filter_filename_extensions = """exe
+bat
+cmd
+com
+pif
+scr
+vbs
+cpl"""
+
+# Fjern alle vedh&aelig;ftninger der ikke har en passende
+# filnavn-endelse. Lad dette felt være tomt for at udelade dette filter.
+pass_filename_extensions = ''
+
+# Should Mailman collapse multipart/alternative to its first part
+# content?
+#
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
+collapse_alternatives = True
+
 # Skal Mailman konvertere text/html dele til ren tekst? Denne
 # konvertering vil finde sted efter at MIME filteret har fjernet de
 # uønskede dele.
diff --git a/mailman/debian.members b/mailman/debian.members
index 194d77d..5024c2e 100644
--- a/mailman/debian.members
+++ b/mailman/debian.members
@@ -1,6 +1,8 @@
-Jonas Smedegard <dr@jones.dk>
+Jonas Smedegaard <dr@jones.dk>
 gaudenz@soziologie.ch
 Juri Jensen <juri@xenux.dk>
+Kasper Myram <kmyram@gmail.com>
 kun.stoej@stoej.org
+oz@bluemonk.de
 ruggero@jones.dk
 Thijs Kroesbergen <thijs@brokenwire.net>
diff --git a/mailman/debian.py b/mailman/debian.py
index d1c22a0..1f745fc 100644
--- a/mailman/debian.py
+++ b/mailman/debian.py
@@ -1,382 +1,369 @@
-## Indstillinger for maillisten "debian"  -*- python -*-
-## Dato: Sun Dec 11 16:35:54 2005
+# -*- python -*-
+# -*- coding: us-ascii -*-
+## "debian" mailing list configuration settings
+## captured on Tue Mar 20 08:52:14 2007
 
 ## General options
 #
-# Grundlæggende egenskaber for listen, herunder en beskrivelse af
-# listen. 
-
-# Du kan f.eks. stave navnet med stort forbogstav eller ændre andre
-# bogstaver til store, s&aring; navnet bliver udtalt rigtigt eller at
-# forkortelser fremhæves. Bemærk at dette navn bruges i e-maillistens
-# adresse (f.eks. i bekræftelser ved tilmeldinger), s&aring; navnet kan
-# ikke ændres p&aring; nogen anden m&aring;de. (e-mailadresser er ikke
-# f&oslash;lsomme for store eller sm&aring; bogstaver, men de er
-# f&oslash;lsomme for n&aelig;sten alt andet :-)
+# Fundamental list characteristics, including descriptive info and basic
+# behaviors.
+
+# The capitalization of this name can be changed to make it presentable
+# in polite company as a proper noun, or to make an acronym part all
+# upper case, etc.  However, the name will be advertised as the email
+# address (e.g., in subscribe confirmation notices), so it should not be
+# otherwise altered.  (Email addresses are not case sensitive, but they
+# are sensitive to almost everything else :-)
 real_name = 'Debian'
 
-# Der er to roller forbundet med hver mailliste. Listeadministratorerne
-# er dem der som sidste instans har kontrol over alle indstillingerne
-# for maillisten. De kan &aelig;ndre alle indstillinger der er
-# tilg&aelig;ngelige via disse administrative websider.
-# 
-# Listemoderatorerne har begrænset adgang; de kan ikke ændre
-# indstillinger for e-maillisten, men de kan tage sig af anmodninger i
-# forbindelse med listen, f.eks. anmodning om medlemskab, eller
-# godkende/afvise meddelelser der skal godkendes for at kunne udsendes
-# til listen. Listeadministratorerne kan ogs&aring; udf&oslash;re disse
-# opgaver.
-# 
-# For at aktivere muligheden for at have listemoderatorer, og p&aring;
-# den m&aring;de fordele arbejdsopgaverne i forbindelse med listen, skal
-# du anf&oslash;re din egen moderatoradgangskode, og angive
-# e-mailadresser for den/dem som skal v&aelig;re listemoderator(er).
-# Bemærk at i tekstboksene nedenfor skal du skrive e-mailadresser for
-# listeadministratorer.
+# There are two ownership roles associated with each mailing list.  The
+# list administrators are the people who have ultimate control over all
+# parameters of this mailing list.  They are able to change any list
+# configuration variable available through these administration web
+# pages.
+# 
+# The list moderators have more limited permissions; they are not able
+# to change any list configuration variable, but they are allowed to
+# tend to pending administration requests, including approving or
+# rejecting held subscription requests, and disposing of held postings.
+# Of course, the list administrators can also tend to pending requests.
+# 
+# In order to split the list ownership duties into administrators and
+# moderators, you must set a separate moderator password, and also
+# provide the email addresses of the list moderators.  Note that the
+# field you are changing here specifies the list administrators.
 owner = ['dr@jones.dk']
 
-# Der er to ejer-roller forbundet med hver mailliste.
-# Listeadministratorerne er dem der har den endelige kontrol over alle
-# indstillingerne for e-mallisten. De kan &aelig;ndre alle indstillinger
-# der er tilgængelige via disse administrative websider.
-# 
-# Listemoderatorerne har begr&aelig;nset adgang; de kan ikke &aelig;ndre
-# indstillinger for e-maillisten, men de kan tage sig af anmodninger
-# ang&aring;ende listen, f.eks. anmodning om medlemskab, eller
-# godkende/afvise meddelelser der skal godkendes for at kunne udsendes
-# p&aring; listen. Listeadministratorerne kan selvsagt ogs&aring;
-# udf&oslash;re disse opgaver.
-# 
-# For at aktivere muligheden for at have listemoderatorer, og p&aring;
-# den m&aring;de fordele arbejdsopgaverne i forbindelse med listen, skal
-# du anf&oslash;re din egen moderatoradgangskode, og indtaste
-# e-mailadresser for den/dem der skal v&aelig;re listemoderatore(r).
-# Bemærk, at i tekstboksene nedenfor skal du skrive listemoderator
-# e-mailadresse(r).
+# There are two ownership roles associated with each mailing list.  The
+# list administrators are the people who have ultimate control over all
+# parameters of this mailing list.  They are able to change any list
+# configuration variable available through these administration web
+# pages.
+# 
+# The list moderators have more limited permissions; they are not able
+# to change any list configuration variable, but they are allowed to
+# tend to pending administration requests, including approving or
+# rejecting held subscription requests, and disposing of held postings.
+# Of course, the list administrators can also tend to pending requests.
+# 
+# In order to split the list ownership duties into administrators and
+# moderators, you must set a separate moderator password, and also
+# provide the email addresses of the list moderators in this section.
+# Note that the field you are changing here specifies the list
+# moderators.
 moderator = []
 
-# Denne beskrivelse benyttes n&aring;r denne malliste listes op sammen
-# med andre maillister, i toptekster, osv. Den b&oslash;r v&aelig;re
-# s&aring; kort som overhovedet mulig, uden at det bliver uklart hvad
-# meningen med maillisten er eller hvad den skal bruges til.
+# This description is used when the mailing list is listed with other
+# mailing lists, or in headers, and so forth.  It should be as succinct
+# as you can get it, while still identifying what the list is.
 description = 'Discussions regarding unofficial Debian packages at debian.jones.dk'
 
-# Teksten tolkes som html bortset fra linieskift, der vil blive
-# &aelig;ndret til html-tag'et '<br>', sådan at du kan benytte links,
-# forh&aring;ndsformateret tekst, osv. Men brug alts&aring; kun
-# linieskift der hvor du vil have et nyt afsnit. V&aelig;r meget
-# omhyggelig, hvis du benytter html-kode. Fejl (f.eks. manglende
-# slut-tag's) kan f&oslash;re til at listens informationsside ikke
-# bliver vist s&aring;dan som den skal.
+# The text will be treated as html except that newlines will be
+# translated to <br> - so you can use links, preformatted text, etc, but
+# don't put in carriage returns except where you mean to separate
+# paragraphs.  And review your changes - bad html (like some
+# unterminated HTML constructs) can prevent display of the entire
+# listinfo page.
 info = ''
 
 # This text will be prepended to subject lines of messages posted to the
-# list, to distinguish mailing list messages in in mailbox summaries.
+# list, to distinguish mailing list messages in mailbox summaries.
 # Brevity is premium here, it's ok to shorten long mailing list names to
 # something more concise, as long as it still identifies the mailing
-# list.
+# list. You can also add a sequential number by %d substitution
+# directive. eg.; [listname %d] -> [listname 123] (listname %05d) ->
+# (listname 00123)
+# 
 subject_prefix = '[Debian] '
 
-# Skjul afsenderen af meddelelser, ved at erstatte den med e-maillistens
-# adresse (Dette medfører at alle From:, Sender, og Reply-To: felter
-# fjernes)
+# Hide the sender of a message, replacing it with the list address
+# (Removes From, Sender and Reply-To fields)
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 anonymous_list = 0
 
-# Skal eksisterende Reply-To: felt i brevhovedet fjernes? Hvis ja, vil
-# dette blive gjort uanset om Mailman tilføjer et Reply-To: felt eller
-# ikke.
+# Should any existing Reply-To: header found in the original message be
+# stripped?  If so, this will be done regardless of whether an explict
+# Reply-To: header is added by Mailman or not.
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 first_strip_reply_to = 0
 
-# Denne indstillling fort&aelig;ller hvad Mailman skal g&oslash;re med
-# Reply-To: feltet i brevhovedet p&aring; e-mail der sendes til listen.
-# Hvis den er sat til Afsender, vil Mailman ikke tilf&oslash;je noget
-# Reply-To: felt, men findes et s&aring;dant felt allerede, vil det ikke
-# blive fjernet. S&aelig;ttes indstillingen til enten e-maillistens
-# adresse eller Egendefineret adresse, vil Mailman tilf&oslash;je, evt.
-# erstatte, et Reply-To: felt. (Egendefineret adresse inds&aelig;tter
-# v&aelig;rdien af indstillingen reply_to_address).
-# 
-# Der er flere grunde til ikke at indf&oslash;re eller erstatte
-# Reply-To: felter. En grund kan v&aelig;re at nogen af dem der sender
-# mail til listen er afh&aelig;ngige af selv at kunne s&aelig;tte
-# Reply-To: adressen. En anden grund er at modifikation af Reply-To:
-# adressen g&oslash;r det vanskeligere kun at sende svar til afsender.
-# Se 'Reply-To' Munging Considered Harmful for en diskussion omkring
-# emnet. Se Reply-To Munging Considered Useful for modsatte meninger.
-# 
-# Nogle maillister har begr&aelig;nset adgang, med en parallel liste
-# beregnet til diskussioner. Eksempler p&aring; dette er 'patches' eller
-# 'checkin' lister, som system for revisionskontrol sender
-# &aelig;ndringer i programmet til, men diskussioner omkring udvikling
-# af programmet sendes til udviklernes egen mailliste. For at
-# underst&oslash;tte lignende e-maillister, v&aelig;lg Egendefineret
-# adresse og s&aelig;t Reply-To: adressen i indstillingen
-# reply_to_address til at pege på den parallelle diskussionsliste.
-#
-# gyldige værdier:
-#    0 = "Afsender"
-#    1 = "mail listens adresse"
-#    2 = "Egendefineret adresse"
+# This option controls what Mailman does to the Reply-To: header in
+# messages flowing through this mailing list.  When set to Poster, no
+# Reply-To: header is added by Mailman, although if one is present in
+# the original message, it is not stripped.  Setting this value to
+# either This list or Explicit address causes Mailman to insert a
+# specific Reply-To: header in all messages, overriding the header in
+# the original message if necessary (Explicit address inserts the value
+# of <a href="?VARHELP=general/reply_to_address">reply_to_address).
+# 
+# There are many reasons not to introduce or override the Reply-To:
+# header.  One is that some posters depend on their own Reply-To:
+# settings to convey their valid return address.  Another is that
+# modifying Reply-To: makes it much more difficult to send private
+# replies.  See <a
+# href="http://www.unicom.com/pw/reply-to-harmful.html">`Reply-To'
+# Munging Considered Harmful for a general discussion of this issue.
+# See <a
+# href="http://www.metasystema.net/essays/reply-to.mhtml">Reply-To
+# Munging Considered Useful for a dissenting opinion.
+# 
+# Some mailing lists have restricted posting privileges, with a parallel
+# list devoted to discussions.  Examples are `patches' or `checkin'
+# lists, where software changes are posted by a revision control system,
+# but discussion about the changes occurs on a developers mailing list.
+# To support these types of mailing lists, select Explicit address and
+# set the Reply-To: address below to point to the parallel list.
+#
+# legal values are:
+#    0 = "Poster"
+#    1 = "This list"
+#    2 = "Explicit address"
 reply_goes_to_list = 1
 
-# Her definerer du adressen der skal s&aelig;ttes i Reply-To: feltet
-# n&aring;r indstillingen reply_goes_to_list er sat til Egendefineret
-# adresse.
-# 
-# Der findes mange grunde til at ikke indf&oslash;re eller erstatte
-# Reply-To: felter. En grund kan v&aelig;re at nogen af dem der sender
-# e-mail til listen er afh&aelig;ngige af selv at kunne s&aelig;tte
-# Reply-To: adressen. En anden grund er at modificering af Reply-To:
-# adressen g&oslash;r det vanskeligere at sende svar kun til afsender.
-# Se 'Reply-To' Munging Considered Harmful for en diskussion omkring
-# temaet. Se Reply-To Munging Considered Useful for modsatte meninger.
-# 
-# Nogle maillister har begr&aelig;nset adgang, med en egen parallel
-# liste beregnet for diskussioner. Eksempler p&aring; dette er 'patches'
-# eller 'checkin' lister, som system for revisionskontrol sender
-# &aelig;ndringer i programmet til, mens diskussioner omkring udvikling
-# af programmet sendes til udviklernes egen mailliste. For at
-# underst&oslash;tte s&aring;danne maillister, kan du definere Reply-To:
-# adressen her, og vælge Egendefineret adresse i indstillingen
-# reply_goes_to_list.
-# 
-# Bem&aelig;rk at hvis den oprindelige meddelelse indeholder et
-# Reply-To: felt, vil det ikke &aelig;ndres.
+# This is the address set in the Reply-To: header when the <a
+# href="?VARHELP=general/reply_goes_to_list">reply_goes_to_list option
+# is set to Explicit address.
+# 
+# There are many reasons not to introduce or override the Reply-To:
+# header.  One is that some posters depend on their own Reply-To:
+# settings to convey their valid return address.  Another is that
+# modifying Reply-To: makes it much more difficult to send private
+# replies.  See <a
+# href="http://www.unicom.com/pw/reply-to-harmful.html">`Reply-To'
+# Munging Considered Harmful for a general discussion of this issue.
+# See <a
+# href="http://www.metasystema.net/essays/reply-to.mhtml">Reply-To
+# Munging Considered Useful for a dissenting opinion.
+# 
+# Some mailing lists have restricted posting privileges, with a parallel
+# list devoted to discussions.  Examples are `patches' or `checkin'
+# lists, where software changes are posted by a revision control system,
+# but discussion about the changes occurs on a developers mailing list.
+# To support these types of mailing lists, specify the explicit
+# Reply-To: address here.  You must also specify Explicit address in the
+# reply_goes_to_list variable.
+# 
+# Note that if the original message contains a Reply-To: header, it will
+# not be changed.
 reply_to_address = ''
 
-# V&aelig;lg kun 'ja' her, hvis listen skal bruges som  "paraply" for
-# andre lister. Hvis 'ja' er valgt, vil bekr&aelig;ftelser og
-# meddelelser med adgangskode blive sendt til en adresse som konstrueres
-# ud fra medlemmets e-mailadresse - v&aelig;rdien af indstillingen
-# "umbrella_member_suffix" tilf&oslash;jes medlemmets kontonavn (det som
-# st&aring;r f&oslash;r @-tegnet).
+# Set this to yes when this list is intended to cascade only to other
+# mailing lists.  When set, meta notices like confirmations and password
+# reminders will be directed to an address derived from the member's
+# address - it will have the value of "umbrella_member_suffix" appended
+# to the member's account name.
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 umbrella_list = 0
 
-# N&aring;r "umbrella_list" indikerer at denne liste har andre
-# maillister som medlemmer, skal administrative meddelelser som f.eks.
-# bekr&aelig;ftelser og p&aring;mindelser om adgangskode ikke sendes til
-# selve listen, men snarere til administrator for listen. V&aelig;rdien
-# af denne indstilling bestemmer, hvilken adresse administrative
-# meddelelser skal sendes til. '-owner' er et almindeligt valg for denne
-# indstilling. Denne indstilling har ingen effekt n&aring;r
-# "umbrella_list" er sat til "Nej".
+# When "umbrella_list" is set to indicate that this list has other
+# mailing lists as members, then administrative notices like
+# confirmations and password reminders need to not be sent to the member
+# list addresses, but rather to the owner of those member lists.  In
+# that case, the value of this setting is appended to the member's
+# account name for such notices.  `-owner' is the typical choice.  This
+# setting has no effect when "umbrella_list" is "No".
 umbrella_member_suffix = '-owner'
 
-# Aktiver denne, hvis der skal sendes en p&aring;mindelse om adgangskode
-# til medlemmerne en gang hver m&aring;ned. Husk at medlemmerne
-# ogs&aring; selv kan frav&aelig;lge dette.
+# Turn this on if you want password reminders to be sent once per month
+# to your members.  Note that members may disable their own individual
+# password reminders.
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 send_reminders = 0
 
-# Tekst du skriver her vil blive tilf&oslash;jet &oslash;verst i
-# velkomsthilsenen der sendes til nye medlemmer. Velkomshilsenen
-# indeholder i forvejen vigtige adresser og URLer knyttet til
-# maillisten, s&aring; den slags information er det ikke
-# n&oslash;dvendigt at inkludere her. Her kan du tilf&oslash;je f.eks.
-# oplysning om etikette eller regler for brug af listen, o.l.
-# 
-# Bem&aelig;rk: Linierne i denne tekst vil brydes efter f&oslash;lgende
-# regler:
+# This value, if any, will be added to the front of the new-subscriber
+# welcome message.  The rest of the welcome message already describes
+# the important addresses and URLs for the mailing list, so you don't
+# need to include any of that kind of stuff here.  This should just
+# contain mission-specific kinds of things, like etiquette policies or
+# team orientation, or that kind of thing.
 # 
-# Hvert afsnit udfyldes s&aringdan at ingen linie er l&aelig;ngere en 70
-# tegn. Enhver linie der begynder med tomme tegn udfyldes ikke. Tomme
-# linier adskiller afsnit.
+# Note that this text will be wrapped, according to the following rules:
+# Each paragraph is filled so that no line is longer than 70 characters.
+# Any line that begins with whitespace is not filled. A blank line
+# separates paragraphs.
 # 
 welcome_msg = ''
 
-# S&aelig;t kun denne til 'Nej' hvis du skal tilf&oslash;je nye
-# medlemmer manuelt, og ikke vil have at de f&aring;r det at vide. Dette
-# er meget nyttigt n&aring;r man g&aring;r fra et andet mallistesystem
-# og til Mailman, og vil have at overgangen skal v&aelig;re s&aring;
-# lidt m&aelig;rkbar som muligt.
+# Turn this off only if you plan on subscribing people manually and
+# don't want them to know that you did so.  This option is most useful
+# for transparently migrating lists from some other mailing list manager
+# to Mailman.
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 send_welcome_msg = 1
 
-# Tekst der sendes til medlemmer der framelder sig listen. Hvis feltet
-# er tomt, tilf&oslash;jes der ikke nogen speciel tekst til
-# frameldingen.
+# Text sent to people leaving the list.  If empty, no special text will
+# be added to the unsubscribe message.
 goodbye_msg = ''
 
-# Send afskedshilsen til medlemmer n&aring;r de frameldes?
+# Send goodbye message to members when they are unsubscribed?
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 send_goodbye_msg = 1
 
-# Der udsendes en p&aring;mindelse til listemoderator (og
-# listeadministrator) dagligt om anmodninger der af en eller anden grund
-# venter p&aring; behandling. V&aelig;lger du "Ja", vil
-# listeadminstrator ogs&aring; modtage en meddelelse s&aring; snart en
-# anmodning ankommer.
+# List moderators (and list administrators) are sent daily reminders of
+# requests pending approval, like subscriptions to a moderated list, or
+# postings that are being held for one reason or another.  Setting this
+# option causes notices to be sent immediately on the arrival of new
+# requests as well.
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 admin_immed_notify = 1
 
-# Skal listeadministrator modtage meddelelse om tilmeldinger og
-# afmeldinger?
+# Should administrator get notices of subscribes and unsubscribes?
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 admin_notify_mchanges = 1
 
-# Approval notices are sent when mail triggers certain of the limits
-# except routine list moderation and spam filters, for which notices are
-# not sent.  This option overrides ever sending the notice.
+# Send mail to poster when their posting is held for approval?
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 respond_to_post_requests = 1
 
-# Når dette valg er aktiveret, vil al e-mail til listen blive modereret.
-# Dette valg kan være nyttigt når din mailliste f.eks. har en såkaldt
-# "flamewar", altså en "krig" hvor medlemmer kun skælder ud på hinanden.
-# En "nød-moderering" kan da hjælpe dig at fjerne usaglige meddelelser
-# til listen, og på den måde dysse en ophedet diskussion ned.
+# When this option is enabled, all list traffic is emergency moderated,
+# i.e. held for moderation.  Turn this option on when your list is
+# experiencing a flamewar and you want a cooling off period.
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 emergency = 0
 
-# Når et nyt medlem tilmeldes listen, bliver medlemmets indstillinger
-# taget herfra.
+# When a new member is subscribed to this list, their initial set of
+# options is taken from the this variable's setting.
 new_member_options = 256
 
-# Filter for administrative meddelelser vil unders&oslash;ge om
-# meddelelsen egentligt er ment som en administrativ anmodning (f.eks.
-# tilmelding, framelding, o.l.), og i s&aring; fald sende meddelelsen
-# til listeadministrator i stedet for.
+# Administrivia tests will check postings to see whether it's really
+# meant as an administrative request (like subscribe, unsubscribe, etc),
+# and will add it to the the administrative requests queue, notifying
+# the administrator of the new request, in the process.
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 administrivia = 1
 
-# Maximum st&oslash;rrelse i kilobytes (KB) for indholdet i e-mail der
-# sendes til listen. Brug v&aelig;rdien '0' for ikke at have nogen
-# begr&aelig;nsning.
+# Maximum length in kilobytes (KB) of a message body.  Use 0 for no
+# limit.
 max_message_size = 40
 
-# "Maskinnavnet" er det navn som skal benyttes for e-mailadresser
-# relateret til Mailman p&aring; denne maskine, og er normalt navnet der
-# er forbundet med e-mail-servicen p&aring; maskinen. Denne indstilling
-# kan v&aelig;re nyttig hvis maskinen har flere navne.
+# The "host_name" is the preferred name for email to mailman-related
+# addresses on this host, and generally should be the mail host's
+# exchanger address, if any.  This setting can be useful for selecting
+# among alternative names of a host that has multiple addresses.
 host_name = 'jones.dk'
 
-# I RFC 2369 defineres en r&aelig;kke List-* felter i brevhovedet, der
-# normalt tilf&oslash;jes enhver meddelelse der sendes ud via listen.
-# Disse felter er til stor gavn for brugere , som benytter et
-# e-mailprogram der f&oslash;lger standarden. Disse felter b&oslash;r
-# derfor altid v&aelig;re med.
-# 
-# Ikke alle e-mailprogrammer f&oslash;lger denne standard. Hvis der er
-# mange medlemmer p&aring; listen, der benytter e-mailprogrammer, der
-# ikke kan h&aring;ndtere disse felter i brevhovedet, kan du v&aelig;lge
-# at udelade dem. Men du b&oslash;r f&oslash;rst fors&oslash;ge at
-# l&aelig;re og forklare medlemmerne hvad hensigten med s&aring;danne
-# felter er, og hvordan de kan skjule dem i deres e-mailprogram. Som en
-# sidste udvej kan du udelade felterne, men det anbefales ikke (og denne
-# mulighed kan faktisk ogs&aring; blive fjernet i senere versioner af
-# Mailman).
-#
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# RFC 2369 defines a set of List-* headers that are normally added to
+# every message sent to the list membership. These greatly aid end-users
+# who are using standards compliant mail readers.  They should normally
+# always be enabled.
+# 
+# However, not all mail readers are standards compliant yet, and if you
+# have a large number of members who are using non-compliant mail
+# readers, they may be annoyed at these headers.  You should first try
+# to educate your members as to why these headers exist, and how to hide
+# them in their mail clients.  As a last resort you can disable these
+# headers, but this is not recommended (and in fact, your ability to
+# disable these headers may eventually go away).
+#
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 include_rfc2369_headers = 1
 
-# List-Post: feltet er et af felterne anbefalet i RFC 2369. P&aring;
-# nogle e-maillister (som f.eks. kun bruges til
-# offentligg&oslash;relser), er det kun bestemte personer der har lov
-# til at poste til listen. Almindelige medlemmer af listen har normalt
-# ikke lov til at poste til listen. For den slags lister, er List-Post:
-# feltet misvisende. S&aelig;t denne indstilling til Nej, for at
-# undg&aring; at feltet tilf&oslash;jes. (Dette p&aring;virker ikke
-# andre List-*: felter.)
-#
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# The List-Post: header is one of the headers recommended by RFC 2369.
+# However for some announce-only mailing lists, only a very select group
+# of people are allowed to post to the list; the general membership is
+# usually not allowed to post.  For lists of this nature, the List-Post:
+# header is misleading. Select No to disable the inclusion of this
+# header. (This does not affect the inclusion of the other List-*:
+# headers.)
+#
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 include_list_post_header = 1
 
+# Discard held messages older than this number of days. Use 0 for no
+# automatic discarding.
+max_days_to_hold = 0
+
 ## Language options
 #
-# Underst&oslash;ttelse af flere sprog. (Internationalisering)
-
-# Dette er standardsproget som benyttes for denne mailliste. Hvis flere
-# end et sprog/ underst&oslash;ttes, vil medlemmer af listen selv kunne
-# v&aelig;lge hvilket sprog der skal benyttes n&aring;r de g&aring;r ind
-# p&aring; deres personlige webside, og n&aring;r meddelelser fra
-# systemet sendes til dem. Hvis medlemmerne ikke &aelig;ndrer noget
-# selv, vil dette standardsprog blive benyttet. Dette g&aelig;lder
-# b&aring;de web-baserede og e-mail-baserede meddelelser, men ikke
-# meddelelser sendt af listens medlemmer.
+# Natural language (internationalization) options.
+
+# This is the default natural language for this mailing list. If more
+# than one language is supported then users will be able to select their
+# own preferences for when they interact with the list.  All other
+# interactions will be conducted in the default language.  This applies
+# to both web-based and email-based messages, but not to email posted by
+# list members.
 preferred_language = 'en'
 
-# Her er alle sprog, som denne liste har underst&oslash;ttelse for.
-# Bem&aelig;rk at standardsproget skal v&aelig;re med.
+# These are all the natural languages supported by this list. Note that
+# the default language must be included.
 available_languages = ['da', 'de', 'en', 'no', 'sv']
 
-# Hvis standardsproget for din mailliste benytter et andet tegns&aelig;t
-# end ASCII og Emne prefixet for listen indeholder tegn som ikke findes
-# i ASCII-tegns&aelig;ttet, vil prefixet altid blive kodet i henhold til
-# den relevante standard. Hvis Emne prefixet kun indeholder ASCII tegn,
-# ønsker du måske at vælge Aldrig for at undgå kodning. Dette kan gøre
-# emnet lidt mere læseligt for brugere med e-mailprogrammer der ikke kan
-# håndtere andre tegnsæt end ASCII.
-# 
-# Bemærk imidlertid, at hvis din mailliste modtager både kodede og
-# ukodede emnefelter , kan det være bedst at vælge Efter behov. Med
-# denne indstilling vil Mailman ikke kode ASCII prefixer hvis resten af
-# titelfeltet kun indeholder ASCII tegn, men vil kode prefixet hvis det
-# indeholder tegn som ikke er ASCII tegn. På denne måde undgås en
-# tvetydighed i standarderne, som forårsager at visse e-mailprogrammer
-# vil vise ekstra eller manglende mellemrum imellem emne prefixet og det
-# oprindelige emne.
-#
-# gyldige værdier:
-#    0 = "Aldrig"
-#    1 = "Altid"
-#    2 = "Efter behov"
+# If your mailing list's default language uses a non-ASCII character set
+# and the prefix contains non-ASCII characters, the prefix will always
+# be encoded according to the relevant standards.  However, if your
+# prefix contains only ASCII characters, you may want to set this option
+# to Never to disable prefix encoding.  This can make the subject
+# headers slightly more readable for users with mail readers that don't
+# properly handle non-ASCII encodings.
+# 
+# Note however, that if your mailing list receives both encoded and
+# unencoded subject headers, you might want to choose As needed.  Using
+# this setting, Mailman will not encode ASCII prefixes when the rest of
+# the header contains only ASCII characters, but if the original header
+# contains non-ASCII characters, it will encode the prefix.  This avoids
+# an ambiguity in the standards which could cause some mail readers to
+# display extra, or missing spaces between the prefix and the original
+# header.
+#
+# legal values are:
+#    0 = "Never"
+#    1 = "Always"
+#    2 = "As needed"
 encode_ascii_prefixes = 0
 
 ## Nondigest options
 #
-# Regler for levering i normal-modus.
+# Policies concerning immediately delivered list traffic.
 
-# Kan medlemmer vælge normal-modus?
+# Can subscribers choose to receive mail immediately, rather than in
+# batched digests?
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 nondigestable = 1
 
-# Tekst der tilføjes &oslash;verst i e-mail der sendes til listens
-# medlemmer. This text can include Python format strings which are
-# resolved against list attributes.  The list of substitutions allowed
-# are:
+# Text prepended to the top of every immediately-delivery message. This
+# text can include Python format strings which are resolved against list
+# attributes.  The list of substitutions allowed are:
 # 
 # 
 # real_name - The "pretty" name of the list; usually the list name with
@@ -401,10 +388,9 @@ nondigestable = 1
 # 
 msg_header = ''
 
-# Tekst som tilf&oslash;jes nederst i e-mail der sendes til listens
-# medlemmer. This text can include Python format strings which are
-# resolved against list attributes.  The list of substitutions allowed
-# are:
+# Text appended to the bottom of every immediately-delivery message.
+# This text can include Python format strings which are resolved against
+# list attributes.  The list of substitutions allowed are:
 # 
 # 
 # real_name - The "pretty" name of the list; usually the list name with
@@ -432,45 +418,54 @@ msg_footer = """_______________________________________________
 %(real_name)s@%(host_name)s
 %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s"""
 
+# When you scrub attachments, they are stored in archive area and links
+# are made in the message so that the member can access via web browser.
+# If you want the attachments totally disappear, you can use content
+# filter options.
+#
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
+scrub_nondigest = False
+
 ## Digest options
 #
-# Opsætning af sammendrag-modus.
+# Batched-delivery digest characteristics.
 
-# Kan medlemmer af listen vælge sammendrag-modus?
+# Can list members choose to receive list traffic bunched in digests?
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 digestable = 1
 
-# Hvilken modus er standard for nye brugere?
+# Which delivery mode is the default for new users?
 #
-# gyldige værdier:
-#    0 = "Normal"
-#    1 = "Sammendrag"
+# legal values are:
+#    0 = "Regular"
+#    1 = "Digest"
 digest_is_default = 0
 
-# Hvilket format skal benyttes som standard for samle-email?
+# When receiving digests, which format is default?
 #
-# gyldige værdier:
-#    0 = "Ren tekst"
+# legal values are:
+#    0 = "Plain"
 #    1 = "MIME"
 mime_is_default_digest = 0
 
-# Hvor stor (i KB) m&aring; en samle-email h&oslash;jst v&aelig;re
-# f&oslash;r den udsendes?
+# How big in Kb should a digest be before it gets sent out?
 digest_size_threshhold = 30
 
-# Skal der sendes en samle-email dagligt, selv om st&oslash;rrelsen ikke
-# er opn&aring;et?
+# Should a digest be dispatched daily when the size threshold isn't
+# reached?
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 digest_send_periodic = 1
 
-# Tekst som tilf&oslash;jes &oslash;verst i samle-emailen, f&oslash;r
-# indholdsfortegnelsen.This text can include Python format strings which
+# Text attached (as an initial message, before the table of contents) to
+# the top of digests. This text can include Python format strings which
 # are resolved against list attributes.  The list of substitutions
 # allowed are:
 # 
@@ -497,10 +492,9 @@ digest_send_periodic = 1
 # 
 digest_header = ''
 
-# Tekst der tilføjes nederst i hver samle-email, som sidste
-# information.This text can include Python format strings which are
-# resolved against list attributes.  The list of substitutions allowed
-# are:
+# Text attached (as a final message) to the bottom of digests. This text
+# can include Python format strings which are resolved against list
+# attributes.  The list of substitutions allowed are:
 # 
 # 
 # real_name - The "pretty" name of the list; usually the list name with
@@ -528,277 +522,279 @@ digest_footer = """_______________________________________________
 %(real_name)s@%(host_name)s
 %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s"""
 
-# N&aring;r et nyt volume startes, &oslash;ges volume nummeret, og
-# udgavenummeret s&aelig;ttes til 1.
+# When a new digest volume is started, the volume number is incremented
+# and the issue number is reset to 1.
 #
-# gyldige værdier:
-#    0 = "&Aring;rlig"
-#    1 = "M&aring;nedlig"
-#    2 = "Kvartalsvis"
-#    3 = "Ugentlig"
-#    4 = "Daglig"
+# legal values are:
+#    0 = "Yearly"
+#    1 = "Monthly"
+#    2 = "Quarterly"
+#    3 = "Weekly"
+#    4 = "Daily"
 digest_volume_frequency = 1
 
 ## Privacy options
 #
-# Her kan du bestemme hvad der kr&aelig;ves for at tilmelde sig til
-# maillisten, og bl.a. bestemme om maillisten skal v&aelig;re skjult
-# eller ikke. Se ogs&aring; <a
-# href="http://mail.jones.dk/cgi-bin/mailman/admin/debian/archive">Indstillinger 
-# for arkivering</a> for egne indstillinger, n&aring;r det g&aelig;lder
-# arkivet og arkivering.
+# This section allows you to configure subscription and membership
+# exposure policy.  You can also control whether this list is public or
+# not.  See also the <a
+# href="http://mail.jones.dk/cgi-bin/mailman/admin/debian/archive">Archival 
+# Options</a> section for separate archive-related privacy settings.
 
-# Vis denne mailliste n&aring;r nogen beder om at se en oversigt over
-# maillister p&aring; denne maskine?
+# Advertise this list when people ask what lists are on this machine?
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 advertised = 1
 
-# bekræftelse(*) - bekr&aelig;ftelse via e-mail er n&oslash;dvendig
-# godkendelse - anmodning om medlemskab skal godkendes af
-# listeadministrator (eller evt. listemoderator) bekr&aelig;ftelse +
-# godkendelse - b&aring;de bekr&aelig;ftelse via e-mail og godkendelse
-# fra listeadministrator (evt. listemoderator) er n&oslash;dvendig
-# 
-# (*) n&aring;r nogen vil tilmelde sig en liste, sender Mailman en
-# meddelelse med en unik identifikator som skal angives for at
-# bekr&aelig;fte tilmeldingen. P&aring; den m&aring;de vil det ikke
-# v&aelig;re muligt at tilmelde nogen imod deres vilje.
-#
-# gyldige værdier:
-#    1 = "Bekr&aelig;ftelse"
-#    2 = "Godkendelse"
-#    3 = "Bekr&aelig;ftelse og godkendelse"
+# Confirm (*) - email confirmation required Require approval - require
+# list administrator approval for subscriptions Confirm and approve -
+# both confirm and approve
+# 
+# (*) when someone requests a subscription, Mailman sends them a notice
+# with a unique subscription request number that they must reply to in
+# order to subscribe. This prevents mischievous (or malicious) people
+# from creating subscriptions for others without their consent.
+#
+# legal values are:
+#    1 = "Confirm"
+#    2 = "Require approval"
+#    3 = "Confirm and approve"
 subscribe_policy = 1
 
-# N&aring;r medlemmer &oslash;nsker at forlade en mailliste, sender de
-# en anmodning om framelding, enten via web, eller via e-mail. Normalt
-# er det bedst at disse anmodninger automatisk godkendes, s&aring;
-# medlemmer kan afmelde sig n&aring;r de &oslash;nsker det (mange
-# &oslash;nsker selv at kunne administrere en framelding). For nogle
-# f&aring; maillister kan det alligevel v&aelig;re aktuelt at have
-# kontrol over om medlemmer kan afmelde sig selv eller ej. En liste som
-# alle ansatte i et firma SKAL v&aelig;re medlem af, er et eksempel
-# p&aring; en s&aring;dan liste.
-#
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# When members want to leave a list, they will make an unsubscription
+# request, either via the web or via email. Normally it is best for you
+# to allow open unsubscriptions so that users can easily remove
+# themselves from mailing lists (they get really upset if they can't get
+# off lists!).
+# 
+# For some lists though, you may want to impose moderator approval
+# before an unsubscription request is processed.  Examples of such lists
+# include a corporate mailing list that all employees are required to be
+# members of.
+#
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 unsubscribe_policy = 0
 
-# Alle e-mailadresser som angives her vil blive udelukket fra listen, og
-# kan ikke tilmelde sig. Indtast e-mailadresser, en pr. linie, start
-# linien med tegnet ^ for at angive et regexp-udtryk der skal stemme
-# overens med afsenderadressen.
+# Addresses in this list are banned outright from subscribing to this
+# mailing list, with no further moderation required.  Add addresses one
+# per line; start the line with a ^ character to designate a regular
+# expression match.
 ban_list = []
 
-# Hvis denne indstilling ikke er sat til 'Alle', vil medlemslisten blive
-# beskyttet af medlemmernes eller administrators adgangskode.
+# When set, the list of subscribers is protected by member or admin
+# password authentication.
 #
-# gyldige værdier:
-#    0 = "Alle"
-#    1 = "Kun medlemmer af listen"
-#    2 = "Kun listeadministrator"
+# legal values are:
+#    0 = "Anyone"
+#    1 = "List members"
+#    2 = "List admin only"
 private_roster = 0
 
-# V&aelig;lger du 'Ja' her, vil medlemmers e-mailadresser blive
-# omskrevet n&aring;r de vises i en oversigt p&aring; websiderne
-# (b&aring;de som tekst og som links), s&aring; de ikke er nemme at
-# tolke som e-mailadresser. Formålet er at undg&aring; at medlemmernes
-# mailadresser bliver opsamlet af e-mailsniffere som skanner websider
-# for e-mailadresser (og derefter bruger dem til at udsende spam/junk
-# mail).
-#
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# Setting this option causes member email addresses to be transformed
+# when they are presented on list web pages (both in text and as links),
+# so they're not trivially recognizable as email addresses.  The
+# intention is to prevent the addresses from being snarfed up by
+# automated web scanners for use by spammers.
+#
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 obscure_addresses = 1
 
 ## Privacy options
 #
-# N&aring;r en meddelelse sendes til maillisten, g&aring;r den igennem
-# nogle trin for at afg&oslash;re om moderator skal godkende meddelelsen
-# eller ikke. Her finder du indstillinger til at kontrollere moderation
-# af e-mail fra b&aring;de medlemmer og ikke-medlemmer.
-# 
-# <p>E-mail fra medlemmer holdes tilbage for godkendelse hvis deres
-# <b>moderationsflag</b> er sat. Du kan bestemme om e-mail fra medlemmer
-# normalt skal vurderes eller ikke f&oslash;r den sendes til listen.
-# 
-# <p>E-mail som ikke er sendt af medlemmer af listen, kan automatisk
-# blive <a
-# href="?VARHELP=privacy/sender/accept_these_nonmembers">godkendt</a>,
-# <a href="?VARHELP=privacy/sender/hold_these_nonmembers">holdt tilbage
-# for godkendelse</a>, <a
-# href="?VARHELP=privacy/sender/reject_these_nonmembers">afvist (sendt
-# retur)</a>, eller <a
-# href="?VARHELP=privacy/sender/discard_these_nonmembers">slettet</a>,
-# enten enkeltvis eller som en gruppe. Al e-mail fra ikke-medlemmer, som
-# ikke specifikt bliver godkendt, sendt retur eller slettet, vil blive
-# behandlet alt efter hvad <a
-# href="?VARHELP=privacy/sender/generic_nonmember_action">generelle
-# regler for ikke-medlemmer</a> viser.
-# 
-# <p>I tekstboksene nedenfor kan du tilf&oslash;je en e-mailadresse pr.
-# linie. Du kan ogs&aring; tilf&oslash;je  <a
-# href="http://www.python.org/doc/current/lib/module-re.html">Python
-# regexp-udtryk</a>. Begynd i s&aring; fald linien med tegnet ^ for at
-# markere at det er et s&aring;dant udtryk. N&aring;r du benytter
-# backslash, skriv da lige som i rene strings (Python raw strings)
-# (normalt kun &eacute;n backslash ad gangen).
-# 
-# <p>Bem&aelig;rk: sammenligning med normale e-mailadresser
-# udf&oslash;res f&oslash;rst, regexp-udtryk vil derfor blive behandlet
-# sidst.
-
-# Hvert medlem af listen har et moderationsflag som fort&aelig;ller om
-# e-mails fra medlemmet kan sendes direkte til e-maillisten, eller om de
-# f&oslash;rst skal godkendes af listemoderator. N&aring;r
-# moderationsflaget er sat til, skal e-mails fra medlemmet godkendes af
-# listemoderator f&oslash;r de udsendes til alle p&aring; listen. Som
-# listeadministrator kan du for hvert enkelt medlem bestemme om
-# medlemmets e-mail skal modereres eller ikke. N&aring;r et nyt medlem
-# tilmeldes listen, s&aelig;ttes moderationsflaget til den indstilling
-# du v&aelig;lger her. S&aelig;t den til 'Nej' hvis du &oslash;nsker at
-# e-mail fra medlemmer normalt skal g&aring; lige til listen. S&aelig;t
-# den til 'Ja' hvis du &oslash;nsker at e-mail fra nye medlemmer skal
-# godkendes f&oslash;r de udsendes til hele listen. Du kan altid
-# s&aelig;tte moderationsflaget for hvert enkelt medlem fra
-# Administration af medlemmer siden.
-#
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# When a message is posted to the list, a series of moderation steps are
+# take to decide whether the a moderator must first approve the message
+# or not.  This section contains the controls for moderation of both
+# member and non-member postings.
+# 
+# <p>Member postings are held for moderation if their <b>moderation
+# flag</b> is turned on.  You can control whether member postings are
+# moderated by default or not.
+# 
+# <p>Non-member postings can be automatically <a
+# href="?VARHELP=privacy/sender/accept_these_nonmembers" >accepted</a>,
+# <a href="?VARHELP=privacy/sender/hold_these_nonmembers">held for
+# moderation</a>, <a
+# href="?VARHELP=privacy/sender/reject_these_nonmembers" >rejected</a>
+# (bounced), or <a
+# href="?VARHELP=privacy/sender/discard_these_nonmembers"
+# >discarded</a>, either individually or as a group.  Any posting from a
+# non-member who is not explicitly accepted, rejected, or discarded,
+# will have their posting filtered by the <a
+# href="?VARHELP=privacy/sender/generic_nonmember_action">general
+# non-member rules</a>.
+# 
+# <p>In the text boxes below, add one address per line; start the line
+# with a ^ character to designate a <a href=
+# "http://www.python.org/doc/current/lib/module-re.html" >Python regular
+# expression</a>.  When entering backslashes, do so as if you were using
+# Python raw strings (i.e. you generally just use a single backslash).
+# 
+# <p>Note that non-regexp matches are always done first.
+
+# Each list member has a moderation flag which says whether messages
+# from the list member can be posted directly to the list, or must first
+# be approved by the list moderator.  When the moderation flag is turned
+# on, list member postings must be approved first.  You, the list
+# administrator can decide whether a specific individual's postings will
+# be moderated or not.
+# 
+# When a new member is subscribed, their initial moderation flag takes
+# its value from this option.  Turn this option off to accept member
+# postings by default.  Turn this option on to, by default, moderate
+# member postings first.  You can always manually set an individual
+# member's moderation bit by using the membership management screens.
+#
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 default_member_moderation = 0
 
+# Hold -- this holds the message for approval by the list moderators.
 # 
-# Hold tilbage -- meddelelsen holdes tilbage for godkendelse af
-# listemoderator(er). Afvis -- meddelelsen sendes automatisk retur til
-# afsender. Begrundelsen der sendes kan du skrive selv Slet --
-# meddelelsen bliver fjernet uden at give besked om dette til afsender.
+# Reject -- this automatically rejects the message by sending a bounce
+# notice to the post's author.  The text of the bounce notice can be <a
+# href="?VARHELP=privacy/sender/member_moderation_notice" >configured by
+# you.
+# 
+# Discard -- this simply discards the message, with no notice sent to
+# the post's author.
 # 
 #
-# gyldige værdier:
-#    0 = "Hold&nbsp;tilbage"
-#    1 = "Afvis"
-#    2 = "Slet"
+# legal values are:
+#    0 = "Hold"
+#    1 = "Reject"
+#    2 = "Discard"
 member_moderation_action = 0
 
-# Tekst som skal sendes med meddelelsen om afvisning som sendes til
-# modererede medlemmer af listen.
+# Text to include in any <a
+# href="?VARHELP/privacy/sender/member_moderation_action" >rejection
+# notice to be sent to moderated members who post to this list.
 member_moderation_notice = ''
 
-# E-mail fra disse ikke-medlemmer vil automatisk blive godkendt.
-# Tilf&oslash;j e-mailadresser, en pr. linie. Start linien med tegnet ^
-# for at angive et regexp-udtryk som skal stemme overens med
-# afsenderadressen.
+# Postings from any of these non-members will be automatically accepted
+# with no further moderation applied.  Add member addresses one per
+# line; start the line with a ^ character to designate a regular
+# expression match.
 accept_these_nonmembers = []
 
-# e-mail fra disse ikke-medlemmer vil automatisk blive holdt tilbage for
-# vurdering af listemoderator. Afsenderen vil modtage en meddelelse om
-# dette, med bl.a. instruktioner om hvordan han/hun kan
-# tilbagetr&aelig;kke sin e-mail. Indtast e-mailadresser, en pr. linie.
-# Start linien med tegnet ^ for at angive et regexp-udtryk som skal
-# stemme overens med afsenderadressen.
+# Postings from any of these non-members will be immediately and
+# automatically held for moderation by the list moderators. The sender
+# will receive a notification message which will allow them to cancel
+# their held message.  Add member addresses one per line; start the line
+# with a ^ character to designate a regular expression match.
 hold_these_nonmembers = []
 
-# E-mail fra disse ikke-medlemmer vil automatisk blive afvist. De vil
-# f&aring; mailen retur, med en meddelelse om at den blev automatisk
-# afvist. Dette valg b&oslash;r ikke benyttes for kendte spammere, de
-# b&oslash;r automatisk slettes. Indtast e-mailadresser, en pr. linie.
-# Start linien med tegnet ^ for at angive et regexp-udtryk som skal
-# stemme overens med afsenderadressen.
+# Postings from any of these non-members will be automatically rejected.
+# In other words, their messages will be bounced back to the sender with
+# a notification of automatic rejection.  This option is not appropriate
+# for known spam senders; their messages should be <a
+# href="?VARHELP=privacy/sender/discard_these_nonmembers" >automatically
+# discarded.
+# 
+# Add member addresses one per line; start the line with a ^ character
+# to designate a regular expression match.
 reject_these_nonmembers = []
 
-# E-mail fra disse ikke-medlemmer vil automatisk blive slettet. Det vil
-# sige at meddelelsen afvises uden nogen form for tilbagemelding, men
-# listemoderator kan (om &oslash;nsket) modtage en kopi af den afviste
-# e-mail. Tilf&oslash;j e-mailadresser, en pr. linie, start linien med
-# tegnet ^ for at angive et regexp-udtryk der skal stemme overens med
-# afsenderadressen.
+# Postings from any of these non-members will be automatically
+# discarded.  That is, the message will be thrown away with no further
+# processing or notification.  The sender will not receive a
+# notification or a bounce, however the list moderators can optionally
+# <a href="?VARHELP=privacy/sender/forward_auto_discards" >receive
+# copies of auto-discarded messages..
+# 
+# Add member addresses one per line; start the line with a ^ character
+# to designate a regular expression match.
 discard_these_nonmembers = []
 
-# N&aring;r en e-mail fra et ikke-medlem bliver modtaget, sammenlignes
-# e-mailens afsender med listen over e-mailadresser der skal godkendes,
-# holdes tilbage, <a
-# href="?VARHELP=privacy/sender/reject_these_nonmembers" >afvises
-# (sendes retur), eller slettes. Hvis afsenderadressen ikke stemmer
-# overens med en adresse der findes i listerne, bliver f&oslash;lgende
-# afg&oslash;relse truffet.
-#
-# gyldige værdier:
-#    0 = "Godkend"
-#    1 = "Hold&nbsp;tilbage"
-#    2 = "Afvis"
-#    3 = "Slet"
-generic_nonmember_action = 0
-
-# Skal meddelelser fra ikke-medlemmer, hvis mail automatisk slettes,
-# videresendes til listemoderator?
-#
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# When a post from a non-member is received, the message's sender is
+# matched against the list of explicitly <a
+# href="?VARHELP=privacy/sender/accept_these_nonmembers" >accepted,
+# held, <a href="?VARHELP=privacy/sender/reject_these_nonmembers"
+# >rejected (bounced), and <a
+# href="?VARHELP=privacy/sender/discard_these_nonmembers" >discarded
+# addresses.  If no match is found, then this action is taken.
+#
+# legal values are:
+#    0 = "Accept"
+#    1 = "Hold"
+#    2 = "Reject"
+#    3 = "Discard"
+generic_nonmember_action = 1
+
+# Should messages from non-members, which are automatically discarded,
+# be forwarded to the list moderator?
+#
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 forward_auto_discards = 1
 
+# Text to include in any rejection notice to be sent to non-members who
+# post to this list. This notice can include the list's owner address by
+# %(listowner)s and replaces the internally crafted default message.
+nonmember_rejection_notice = ''
+
 ## Privacy options
 #
-# Her kan du ops&aelig;tte filtrering baseret på modtageren af
-# meddelelsen.
+# This section allows you to configure various filters based on the
+# recipient of the message.
 
-# Meget (faktisk det meste) spam/junk mail har ikke de endelige
-# modtagere i modtagerfelterne. Faktisk indeholder felterne To: og/eller
-# Cc: oftest en helt ugyldig adresse. Begr&aelig;nsningen du
-# s&aelig;tter her har kun indvirkning p&aring; det som st&aring;r
-# f&oslash;r '@' tegnet i adressen, men filtret vil alligevel opfange og
-# blokere det meste spam/junk mail.
+# Many (in fact, most) spams do not explicitly name their myriad
+# destinations in the explicit destination addresses - in fact often the
+# To: field has a totally bogus address for obfuscation.  The constraint
+# applies only to the stuff in the address before the '@' sign, but
+# still catches all such spams.
+# 
+# The cost is that the list will not accept unhindered any postings
+# relayed from other addresses, unless
 # 
-# Prisen for dette er, at listen ikke uhindret vil kunne modtage e-mail
-# videresendt via andre e-mailadresser, med mindre
 # 
+# The relaying address has the same name, or
+# 
+# The relaying address name is included on the options that specifies
+# acceptable aliases for the list.
 # 
-# Adressen der videresendes fra hedder det samme, eller Adressen der
-# videresendes fra inkluderes i indstillingen som bestemmer gyldige
-# aliaser for listen.
 # 
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 require_explicit_destination = 1
 
-# Alternative e-mailadresser som godtages n&aring;r
-# 'require_explicit_destination' er sat til. Som v&aelig;rdi for denne
-# indstilling skal du angive regexp-udtryk ("regular expressions"), et
-# udtryk pr. linie, der sammenlignes med hver modtageradresse i
-# meddelelsen. Sammenligningen udf&oslash;res med Pythons re.match()
-# funktion, som betyder at de kun g&aelig;lder for begyndelsen af
-# strengen.
-# 
-# For bagudkompatibilitet med Mailman 1.1, hvis regexp-udtryk ikke
-# indeholder en '@', sammenlignes udtrykket kun med den f&oslash;rste
-# del (det som st&aring;r f&oslash;r '@') i modtageradressen. Hvis
-# sammenligningen ikke lykkes, eller hvis udtrykket ikke indholder en
-# '@', sammenlignes udtrykket med hele modtageradressen.
-# 
-# Sammenligning med kun den f&oslash;rste del af en modtageradresse
-# underst&oslash;ttes ikke l&aelig;ngere. I fremtidige versioner af
-# Mailman vil kun sammenligning med hele modtageradresser blive
-# underst&oslash;ttet.
+# Alternate addresses that are acceptable when
+# `require_explicit_destination' is enabled.  This option takes a list
+# of regular expressions, one per line, which is matched against every
+# recipient address in the message.  The matching is performed with
+# Python's re.match() function, meaning they are anchored to the start
+# of the string.
+# 
+# For backwards compatibility with Mailman 1.1, if the regexp does not
+# contain an `@', then the pattern is matched against just the local
+# part of the recipient address.  If that match fails, or if the pattern
+# does contain an `@', then the pattern is matched against the entire
+# recipient address.
+# 
+# Matching against the local part is deprecated; in a future release,
+# the pattern will always be matched against the entire recipient
+# address.
 acceptable_aliases = ''
 
-# Hvis en mail der er sendt til listen indeholder s&aring; mange som
-# eller flere modtagere end denne v&aelig;rdi, holdes mailen tilbage,
-# s&aring; listeadministrator eventuelt kan godkende den. Brug
-# v&aelig;rdien 0 for ingen begr&aelig;nsning.
+# If a posting has this number, or more, of recipients, it is held for
+# admin approval.  Use 0 for no ceiling.
 max_num_recipients = 10
 
 ## Privacy options
 #
-# Her kan du opsætte forskellige anti-spam filtre, som kan bidrage til
-# at reducere mængden af spam der distribueres via e-maillisten.
+# This section allows you to configure various anti-spam filters posting
+# filters, which can help reduce the amount of spam your list members
+# end up receiving.
+# 
 
 # Each header filter rule has two parts, a list of regular expressions,
 # one per line, and an action to take.  Mailman matches the message's
@@ -809,22 +805,23 @@ max_num_recipients = 10
 # You can have more than one filter rule for your list.  In that case,
 # each rule is matched in turn, with processing stopped after the first
 # match.
+# 
+# Note that headers are collected from all the attachments (except for
+# the mailman administrivia message) and matched against the regular
+# expressions. With this feature, you can effectively sort out messages
+# with dangerous file types or file name extensions.
 header_filter_rules = []
 
-# Brug denne indstilling til at bortfiltrere mail til listen, baseret
-# p&aring; indholdet af et eller flere felter i brevhovedet. Her skal du
-# skrive regexp-udtryk (regular expressions), et pr. linie, som
-# sammenlignes med det aktuelle felt. Sammenligningen skelner ikke
-# imellem store og sm&aring; bogstaver. Linier der begynder med '#'
-# sammenlignes ikke.
+# Use this option to prohibit posts according to specific header values.
+# The target value is a regular-expression for matching against the
+# specified header.  The match is done disregarding letter case.  Lines
+# beginning with '#' are ignored as comments.
 # 
-# For eksempel: udtrykket to: .*@public.com fort&aelig;ller at al mail
-# som indeholder '@public.com' i To: feltet, skal holdes tilbage for
-# godkendelse.
+# For example:to: .*@public.com  says to hold all postings with a To:
+# mail header containing '@public.com' anywhere among the addresses.
 # 
-# Bem&aelig;rk: tomme tegn i starten af regexp-udtrykket fjernes. Dette
-# kan omg&aring;s p&aring; flere m&aring;der, f.eks. ved at bruge
-# escape-tegn eller parenteser.
+# Note that leading whitespace is trimmed from the regexp.  This can be
+# circumvented in a number of ways, e.g. by escaping or bracketing it.
 bounce_matching_headers = """
 # Lines that *start* with a '#' are comments.
 to: friend@public.com
@@ -834,415 +831,439 @@ from: .*@uplinkpro.com"""
 
 ## Bounce options
 #
-# Disse regler bestemmer hvordan automatisk behandling af returmails
-# skal foreg&aring;. Her er en oversigt over hvordan det virker.
-# 
-# <p>N&aring;r Mailman modtager en returmail, bliver to ting
-# fors&oslash;gt tolket. Den ene er e-mailadressen for medlemmet som
-# egentlig skulle modtage e-mailen, og den anden er &aring;rsagen til
-# problemet. &Aring;rsagen tolkes til at v&aelig;re <em>alvorlig</em>
-# eller <em>harml&oslash;s</em> alt efter om &aring;rsagen er af kritisk
-# eller af mindre alvorlig art. Hvis der er tvivl, tolkes &aring;rsagen
-# som alvorlig.
-# 
-# <p>Hvis ingen e-mailadresse kan hentes ud af meddelelsen, bliver den
-# normalt afvist. Ellers vil medlemmet som har e-mailadressen f&aring;
-# tildelt et <em>returtal</em>, og hver gang der kommer en
-# returmeddelelse vil tallet &oslash;ges. Alvorlige &aring;rsager
-# f&oslash;rer til at tallet &oslash;ges med 1, harml&oslash;se
-# &aring;rsager f&oslash;rer til at det &oslash;ges med 0.5. Dette sker
-# kun &eacute;n gang pr. dag, s&aring; selv om der kommer 10 alvorlige
-# returmails fra et medlem p&aring; &eacute;n dag, vil tallet kun
-# &oslash;ges med 1.
-# 
-# <p>N&aring;r returtallet for et medlem n&aring;r en vis <a
-# href="?VARHELP=bounce/bounce_score_threshold">gr&aelig;nse</a>,
-# stoppes levering til medlemmet. Dermed vil medlemmet ikke modtage
-# e-mail fra listen f&oslash;r levering s&aelig;ttes til igen. Medlemmet
-# vil med j&aelig;vne mellemrum modtage meddelelse om at dette er sket,
-# og hvad han/hun skal g&oslash;re for at f&aring; e-mail fra listen
-# igen.
-# 
-# <p>Du kan bestemme <a
-# href="?VARHELP=bounce/bounce_you_are_disabled_warnings">hvor mange
-# advarsler</a> medlemmet skal have og <a
-# href="?VARHELP=bounce/bounce_you_are_disabled_warnings_interval">hvor
-# ofte</a> han/hun skal modtage s&aring;danne advarsler.
-# 
-# <p>Der er en vigtig indstilling mere: efter en vis tid -- hvor ingen
-# returmeddelelser dukker op -- regnes returinformation for at
-# v&aelig;re <a
-# href="?VARHELP=bounce/bounce_info_stale_after">for&aelig;ldet</a> og
-# stoppes. Ved at justere denne v&aelig;rdi, og s&aelig;tte en
-# gr&aelig;nse for returantallet, kan du bestemme hvor lang tid der skal
-# g&aring; f&oslash;r levering til et medlem stoppes. Begge disse
-# v&aelig;rdier b&oslash;r tilpasses efter hvor ofte og hvor meget
-# e-mail der sendes til din liste.
-
-# Ved at sætte denne værdi til Nej, slår du al automatisk tolkning af
-# returmeddelelser for denne liste fra. Bemærk at hvis meddelelser
-# afvises vil listeadministratoren ikke blive forstyrret med dem.
-#
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# These policies control the automatic bounce processing system in
+# Mailman.  Here's an overview of how it works.
+# 
+# <p>When a bounce is received, Mailman tries to extract two pieces of
+# information from the message: the address of the member the message
+# was intended for, and the severity of the problem causing the bounce.
+# The severity can be either <em>hard</em> or <em>soft</em> meaning
+# either a fatal error occurred, or a transient error occurred.  When in
+# doubt, a hard severity is used.
+# 
+# <p>If no member address can be extracted from the bounce, then the
+# bounce is usually discarded.  Otherwise, each member is assigned a
+# <em>bounce score</em> and every time we encounter a bounce from this
+# member we increment the score.  Hard bounces increment by 1 while soft
+# bounces increment by 0.5.  We only increment the bounce score once per
+# day, so even if we receive ten hard bounces from a member per day,
+# their score will increase by only 1 for that day.
+# 
+# <p>When a member's bounce score is greater than the <a
+# href="?VARHELP=bounce/bounce_score_threshold">bounce score
+# threshold</a>, the subscription is disabled.  Once disabled, the
+# member will not receive any postings from the list until their
+# membership is explicitly re-enabled (either by the list administrator
+# or the user).  However, they will receive occasional reminders that
+# their membership has been disabled, and these reminders will include
+# information about how to re-enable their membership.
+# 
+# <p>You can control both the <a
+# href="?VARHELP=bounce/bounce_you_are_disabled_warnings">number of
+# reminders</a> the member will receive and the <a
+# href="?VARHELP=bounce/bounce_you_are_disabled_warnings_interval"
+# >frequency</a> with which these reminders are sent.
+# 
+# <p>There is one other important configuration variable; after a
+# certain period of time -- during which no bounces from the member are
+# received -- the bounce information is <a
+# href="?VARHELP=bounce/bounce_info_stale_after">considered stale</a>
+# and discarded.  Thus by adjusting this value, and the score threshold,
+# you can control how quickly bouncing members are disabled.  You should
+# tune both of these to the frequency and traffic volume of your list.
+
+# By setting this value to No, you disable all automatic bounce
+# processing for this list, however bounce messages will still be
+# discarded so that the list administrator isn't inundated with them.
+#
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 bounce_processing = 1
 
-# Hvert medlem tildeles et returtal, og hver gang der kommer en
-# returmeddelelse vil dette tal &oslash;ges.  Alvorlige (&aring;rsager
-# f&oslash;rer til at det &oslash;ges med 1, mens harml&oslash;se
-# &aring;rsager f&oslash;rer til at det &oslash;ges med 0.5. Dette sker
-# kun &eacute;n gang pr. dag, s&aring; selv om der kommer 10 alvorlige
-# returmails fra et medlem p&aring; &eacute;n dag, vil tallet kun
-# &oslash;ges med 1.
-# 
-# Her s&aelig;ttes den &oslash;vre gr&aelig;nse for medlemmets returtal
-# Overskrides denne gr&aelig;nse stoppes levering automatisk, men
-# medlemmet bliver ikke fjernet fra listen.
+# Each subscriber is assigned a bounce score, as a floating point
+# number.  Whenever Mailman receives a bounce from a list member, that
+# member's score is incremented.  Hard bounces (fatal errors) increase
+# the score by 1, while soft bounces (temporary errors) increase the
+# score by 0.5.  Only one bounce per day counts against a member's
+# score, so even if 10 bounces are received for a member on the same
+# day, their score will increase by just 1.
+# 
+# This variable describes the upper limit for a member's bounce score,
+# above which they are automatically disabled, but not removed from the
+# mailing list.
 bounce_score_threshold = 5.0
 
-# Antal dage f&oslash;r returinformation stoppes hvis der ikke dukker
-# flere returmails op. Dette tal skal v&aelig;re et heltal.
+# The number of days after which a member's bounce information is
+# discarded, if no new bounces have been received in the interim.  This
+# value must be an integer.
 bounce_info_stale_after = 7
 
-# Hvor mange Levering til dig er stoppet advarsler der skal sendes til
-# et medlem f&oslash;r medlemmet frameldes listen. S&aelig;t denne værdi
-# til 0 for at fjerne et medlem fra listen straks, hvis der kommer
-# returmails fra medlemmets e-mailadresse. Dette tal skal være et
-# heltal.
+# How many Your Membership Is Disabled warnings a disabled member should
+# get before their address is removed from the mailing list.  Set to 0
+# to immediately remove an address from the list once their bounce score
+# exceeds the threshold.  This value must be an integer.
 bounce_you_are_disabled_warnings = 3
 
-# Antal dage imellem hver gang en Levering til dig er stoppet advarsel
-# skal sendes ud. Dette tal skal være et heltal.
+# The number of days between sending the Your Membership Is Disabled
+# warnings.  This value must be an integer.
 bounce_you_are_disabled_warnings_interval = 7
 
-# Mailmans automatiske returmailh&aring;ndtering er meget robust, men
-# det er alligevel umuligt at genkende alle typer returmails der kommer.
-# Du b&oslash;r v&aelig;lge Ja her, af to grunde: 1) Hvis det virkelig
-# er en permanent returmail fra et medlem af listen, b&oslash;r du
-# antagelig manuelt afmelde medlemmet fra listen, og 2) du vil
-# m&aring;ske sende en meddelelse til udviklerne af Mailman s&aring;dan
-# at returmails automatisk genkendes af Mailman i senere versioner. Hvis
-# du ikke vil g&oslash;re nogen af delene, s&aelig;ttes denne
-# indstilling til Nej. S&aring; vil alle returmails afvises automatisk
-# uden videre behandling. Bem&aelig;rk: Denne indstilling vil ogs&aring;
-# indvirke p&aring; al e-mail der sendes til listens -admin adresse. Den
-# adresse er for&aelig;ldet og udg&aring;et, men måske vil nogen
-# alligevel fortsat sende e-mail til den. Hvis nogen g&oslash;r det, og
-# du har sat denne indstilling til Nej, vil disse mails ogs&aring; blive
-# afvist. M&aring;ske vil du ogs&aring; ops&aelig;tte et automatisk svar
-# p&aring; e-mail sendt til -owner og -admin adresserne.
-#
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# While Mailman's bounce detector is fairly robust, it's impossible to
+# detect every bounce format in the world.  You should keep this
+# variable set to Yes for two reasons: 1) If this really is a permanent
+# bounce from one of your members, you should probably manually remove
+# them from your list, and 2) you might want to send the message on to
+# the Mailman developers so that this new format can be added to its
+# known set.
+# 
+# If you really can't be bothered, then set this variable to No and all
+# non-detected bounces will be discarded without further processing.
+# 
+# Note: This setting will also affect all messages sent to your list's
+# -admin address.  This address is deprecated and should never be used,
+# but some people may still send mail to this address.  If this happens,
+# and this variable is set to No those messages too will get discarded.
+# You may want to set up an autoresponse message for email to the -owner
+# and -admin address.
+#
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 bounce_unrecognized_goes_to_list_owner = 1
 
-# Ved at sætte denne til Nej, fravælges beskeden der normalt sendes til
-# ejer(e) af listen, når levering af e-mail til et medlem stoppes på
-# grund af for mange returmails. Der vil til gengæld altid blive forsøgt
-# afsendt en e-mail med besked til medlemmet.
+# By setting this value to No, you turn off notification messages that
+# are normally sent to the list owners when a member's delivery is
+# disabled due to excessive bounces. An attempt to notify the member
+# will always be made.
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 bounce_notify_owner_on_disable = 1
 
-# Ved at sætte denne til Nej, fravælges beskeden der normalt sendes til
-# ejer(e) af listen, når et medlem frameldes listen på grund af for
-# mange returmails. Der vil til gengæld altid blive forsøgt afsendt en
-# e-mail med besked til medlemmet.
+# By setting this value to No, you turn off notification messages that
+# are normally sent to the list owners when a member is unsubscribed due
+# to excessive bounces.  An attempt to notify the member will always be
+# made.
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 bounce_notify_owner_on_removal = 1
 
 ## Archive options
 #
-# Regler for arkivering
+# List traffic archival policies.
 
-# Arkiver e-mail i et arkiv?
+# Archive messages?
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 archive = 1
 
-# Skal arkivet v&aelig;re offentligt eller privat?
+# Is archive file source for public or private archival?
 #
-# gyldige værdier:
-#    0 = "Offentligt"
-#    1 = "Privat"
+# legal values are:
+#    0 = "public"
+#    1 = "private"
 archive_private = 0
 
-# Hvor ofte skal arkivet deles op?
+# How often should a new archive volume be started?
 #
-# gyldige værdier:
-#    0 = "&Aring;rlig"
-#    1 = "M&aring;nedlig"
-#    2 = "Kvartalsvis"
-#    3 = "Ugentlig"
-#    4 = "Daglig"
+# legal values are:
+#    0 = "Yearly"
+#    1 = "Monthly"
+#    2 = "Quarterly"
+#    3 = "Weekly"
+#    4 = "Daily"
 archive_volume_frequency = 2
 
 ## Gateway options
 #
-# E-mail-Til-Nyhedsgruppe og Nyhedsgruppe-Til-E-mail tjeneste.
+# Mail-to-News and News-to-Mail gateway services.
 
-# Nyhedsgruppe-tjeneste er ikke en del af Mailman. Du skal have adgang
-# til en eksisterende NNTP tjeneste, og maskinen som denne mailliste
-# k&oslash;rer p&aring; skal have adgang til at hente og afsende
-# meddelelser til NNTP tjenesten.
+# This value may be either the name of your news server, or optionally
+# of the format name:port, where port is a port number.
+# 
+# The news server is not part of Mailman proper.  You have to already
+# have access to an NNTP server, and that NNTP server must recognize the
+# machine this mailing list runs on as a machine capable of reading and
+# posting news.
 nntp_host = ''
 
-# Navn p&aring; nyhedsgruppe der skal sendes til og/eller fra.
+# The name of the Usenet group to gateway to and/or from.
 linked_newsgroup = ''
 
-# Skal nye meddelelser til denne liste sendes til nyhedsgruppen?
+# Should new posts to the mailing list be sent to the newsgroup?
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 gateway_to_news = 0
 
-# Skal nye meddelelser til nyhedsgruppen sendes til denne mailliste?
+# Should new posts to the newsgroup be sent to the mailing list?
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 gateway_to_mail = 0
 
-# Denne indstilling fort&aelig;ller Mailman hvilken slags
-# moderationsregler nyhedsgruppen har og hvordan de koordineres med
-# maillistens moderationsregler. Dette g&aelig;lder kun nyhedgrupper du
-# overfører meddelelser til, s&aring; hvis du kun overf&oslash;rer fra
-# en nyhedsgruppe, eller nyhedsgruppen du overf&oslash;rer til ikke er
-# modereret, s&aelig;ttes indstillingen til Ingen.
-# 
-# Hvis nyhedsgruppen er modereret, kan du s&aelig;tte maillisten til at
-# v&aelig;re moderationsadressen for nyhedsgruppen. Ved at vælge
-# Modereret, vil en ekstra meddelelse holdes tilbage i
-# godkendelsesprocessen. Al mail sendt til maillisten skal godkendes
-# f&oslash;r den sendes til nyhedsgruppen, eller til medlemmerne af
-# listen.
-# 
-# Vær opm&aelig;rksom p&aring; at hvis brevhovedet i mailen har et
-# Approved: felt med listens administrative adgangskode, vil denne regel
-# ikke blive benyttet. På den m&aring;de kan priviligerede afsendere
-# sende mail direkte til listen og nyhedsgruppen.
-# 
-# Hvis nyhedsgruppen er modereret, men du alligevel vil have en
-# &aring;ben liste, b&oslash;r du vælge Åben liste, modereret
-# nyhedsgruppe. S&aring; vil de s&aelig;dvanlige mekanismer for
-# moderation blive benyttet i Mailman, men alle meddelelser der sendes
-# til Usenet vil f&aring; et Approved felt i brevhovedet.
-#
-# gyldige værdier:
-#    0 = "Ingen"
-#    1 = "Åben liste, modereret nyhedsgruppe"
-#    2 = "Modereret"
+# This setting determines the moderation policy of the newsgroup and its
+# interaction with the moderation policy of the mailing list.  This only
+# applies to the newsgroup that you are gatewaying to, so if you are
+# only gatewaying from Usenet, or the newsgroup you are gatewaying to is
+# not moderated, set this option to None.
+# 
+# If the newsgroup is moderated, you can set this mailing list up to be
+# the moderation address for the newsgroup.  By selecting Moderated, an
+# additional posting hold will be placed in the approval process.  All
+# messages posted to the mailing list will have to be approved before
+# being sent on to the newsgroup, or to the mailing list membership.
+# 
+# Note that if the message has an Approved header with the list's
+# administrative password in it, this hold test will be bypassed,
+# allowing privileged posters to send messages directly to the list and
+# the newsgroup.
+# 
+# Finally, if the newsgroup is moderated, but you want to have an open
+# posting policy anyway, you should select Open list, moderated group.
+# The effect of this is to use the normal Mailman moderation facilities,
+# but to add an Approved header to all messages that are gatewayed to
+# Usenet.
+#
+# legal values are:
+#    0 = "None"
+#    1 = "Open list, moderated group"
+#    2 = "Moderated"
 news_moderation = 0
 
-# Mailman tilføjer normalt en tekst du selv kan tilrette (emne prefix)
-# foran emnefeltet i mail som sendes til listen, og normalt sker dette
-# også for mail som sendes videre til Usenet. Du kan sætte denne
-# indstilling til Nej hvis du ikke ønsker emne prefix tilføjet til mail
-# som sendes til Usenet. Sættes emne prefix for listen til off, vil
-# videresendte meddelelser heller ikke få prefix tilføjet.
+# Mailman prefixes Subject: headers with text you can customize and
+# normally, this prefix shows up in messages gatewayed to Usenet.  You
+# can set this option to No to disable the prefix on gated messages.  Of
+# course, if you turn off normal Subject: prefixes, they won't be
+# prefixed for gated messages either.
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 news_prefix_subject_too = 1
 
 ## Autoreply options
 #
-# Indstillinger for automatiske svar.<p>
+# Auto-responder characteristics.<p>
 # 
-# I tekstboksene nedenfor kan du bruge følgende variabler: (skriv:
-# %(&lt;variabelnavn&gt;)s ) for at indsætte ønsket information: <p><ul>
-# <li><b>listname</b> - <em>navnet p&aring; listen</em>
-# <li><b>listurl</b> - <em>URL til listens webside</em>
-# <li><b>requestemail</b> - <em>listens -request e-mailadresse</em>
-# <li><b>owneremail</b> - <em>listens -owner e-mailadresse</em> </ul>
+# In the text fields below, string interpolation is performed with the
+# following key/value substitutions: <p><ul> <li><b>listname</b> -
+# <em>gets the name of the mailing list</em> <li><b>listurl</b> -
+# <em>gets the list's listinfo URL</em> <li><b>requestemail</b> -
+# <em>gets the list's -request address</em> <li><b>owneremail</b> -
+# <em>gets the list's -owner address</em> </ul>
 # 
-# <p>Du kan enten skrive teksten direkte i tekstboksene, eller du kan
-# angive navnet p&aring; en fil som indeholder teksten. Denne fil vil
-# s&aring; blive indl&aelig;st i tekstboksen, fra dit lokale filsystem.
+# <p>For each text field, you can either enter the text directly into
+# the text box, or you can specify a file on your local system to upload
+# as the text.
 
-# Skal Mailman sende et automatisk svar til dem der sender e-mail til
-# listen?
+# Should Mailman send an auto-response to mailing list posters?
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 autorespond_postings = 0
 
-# Automatisk svar der skal sendes.
+# Auto-response text to send to mailing list posters.
 autoresponse_postings_text = ''
 
-# Skal Mailman sende et automatisk svar p&aring; e-mail der sendes til
-# -owner adressen?
+# Should Mailman send an auto-response to emails sent to the -owner
+# address?
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 autorespond_admin = 0
 
-# Automatisk svar p&aring; e-mail til -owner adressen.
+# Auto-response text to send to -owner emails.
 autoresponse_admin_text = ''
 
-# Skal Mailman sende et automatisk svar p&aring; e-mail der sendes til
-# -request adressen? Hvis du v&aelig;lger ja, kan du ogs&aring;
-# v&aelig;lge om e-mailen der blev sendt til -request adressen skal
-# medtages i det automatiske svar.
+# Should Mailman send an auto-response to emails sent to the -request
+# address?  If you choose yes, decide whether you want Mailman to
+# discard the original email, or forward it on to the system as a normal
+# mail command.
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja, men uden den originale e-mail"
-#    2 = "Ja, og medtag den originale e-mail"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes, w/discard"
+#    2 = "Yes, w/forward"
 autorespond_requests = 0
 
-# Automatisk svar p&aring; e-mail til -request adressen.
+# Auto-response text to send to -request emails.
 autoresponse_request_text = ''
 
-# Antal dage imellem automatisk svar p&aring; e-mail, fra samme
-# afsender, til listen eller til -request/-owner adresserne. S&aelig;t
-# denne v&aelig;rdi til 0 (eller et negativt tal) for at sende
-# automatisk svar hver gang.
+# Number of days between auto-responses to either the mailing list or
+# -request/-owner address from the same poster.  Set to zero (or
+# negative) for no grace period (i.e. auto-respond to every message).
 autoresponse_graceperiod = 90
 
 ## Contentfilter options
 #
-# Regler for indhold i e-mail sendt til listen.
-# 
-# <p>Filtrering af indhold fungerer således: når listen modtager en
-# e-mail og du har beskyttelse med filtrering af indhold aktiveret,
-# sammenlignes først eventuelle vedh&aelig;ftninger med <a
-# href="?VARHELP=contentfilter/filter_mime_types">MIME filtrene</a>.
-# Hvis en vedh&aelig;ftning passer med et af disse filtre, bliver
-# vedh&aelig;ftningen fjernet.
-# 
-# <p>Derefter sammenlignes eventuelle vedh&aelig;ftninger med <a
-# href="?VARHELP=contentfilter/pass_mime_types">gyldige MIME typer</a>,
-# hvis nogen er defineret. Alle vedh&aelig;ftninger som ikke stemmer
-# overens med de angivne MIME typer, bliver fjernet.
-# 
-# <p>Efter filtreringen vil alle tomme <tt>multipart</tt>
-# vedh&aelig;ftninger v&aelig;re fjernet. Hvis selve meddelelsen er helt
-# tom efter denne filtrering, vil meddelelsen blive afvist. Derefter vil
-# enhver <tt>multipart/alternative</tt> vedh&aelig;ftning blive
-# erstattet af den første alternative som ikke er tom.
-# 
-# <p>Til sidst vil alle <tt>text/html</tt> vedh&aelig;ftninger som måtte
-# v&aelig;re tilbage i meddelelsen blive konverteret til
-# <tt>text/plain</tt> hvis <a
-# href="?VARHELP=contentfilter/convert_html_to_plaintext">konverter til
-# ren tekst</a> er sat til og serveren er konfigureret til at tillade
-# sådanne konverteringer.
-
-# Skal Mailman filtrere indhold i e-mail sendt til listen som angivet
-# nedenfor?
-#
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# Policies concerning the content of list traffic.
+# 
+# <p>Content filtering works like this: when a message is received by
+# the list and you have enabled content filtering, the individual
+# attachments are first compared to the <a
+# href="?VARHELP=contentfilter/filter_mime_types">filter types</a>.  If
+# the attachment type matches an entry in the filter types, it is
+# discarded.
+# 
+# <p>Then, if there are <a
+# href="?VARHELP=contentfilter/pass_mime_types">pass types</a> defined,
+# any attachment type that does <em>not</em> match a pass type is also
+# discarded.  If there are no pass types defined, this check is skipped.
+# 
+# <p>After this initial filtering, any <tt>multipart</tt> attachments
+# that are empty are removed.  If the outer message is left empty after
+# this filtering, then the whole message is discarded.
+# 
+# <p> Then, each <tt>multipart/alternative</tt> section will be replaced
+# by just the first alternative that is non-empty after filtering if <a
+# href="?VARHELP=contentfilter/collapse_alternatives"
+# >collapse_alternatives</a> is enabled.
+# 
+# <p>Finally, any <tt>text/html</tt> parts that are left in the message
+# may be converted to <tt>text/plain</tt> if <a
+# href="?VARHELP=contentfilter/convert_html_to_plaintext"
+# >convert_html_to_plaintext</a> is enabled and the site is configured
+# to allow these conversions.
+
+# Should Mailman filter the content of list traffic according to the
+# settings below?
+#
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 filter_content = 0
 
-# Brug denne indstilling til at fjerne vedh&aelig;ftninger der passer
-# til MIME typer. Hver linie skal her indeholde navnet på en MIME
-# type/subtype, f.eks. image/gif. Hvis du ønsker at fjerne alle
-# vedh&aelig;ftninger som har en given hoved MIME type, kan du undlade
-# at angive subtype, f.eks. image.
+# Use this option to remove each message attachment that matches one of
+# these content types.  Each line should contain a string naming a MIME
+# type/subtype, e.g. image/gif.  Leave off the subtype to remove all
+# parts with a matching major content type, e.g. image.
 # 
-# Tomme linier medtages ikke.
+# Blank lines are ignored.
 # 
-# Se også gyldige MIME typer for whitelist af MIME typer.
+# See also <a href="?VARHELP=contentfilter/pass_mime_types"
+# >pass_mime_types for a content type whitelist.
 filter_mime_types = ''
 
-# Brug denne indstilling for at definere hvilke MIME typer der skal være
-# tilladt. Krav og format for filtrering er identisk med MIME filtre.
+# Use this option to remove each message attachment that does not have a
+# matching content type.  Requirements and formats are exactly like <a
+# href="?VARHELP=contentfilter/filter_mime_types" >filter_mime_types.
 # 
-# Bem&aelig;rk: hvis du lægger noget ind her, men ikke angiver
-# multipart, vil ingen e-mail med vedh&aelig;ftninger blive medtaget.
+# Note: if you add entries to this list but don't add multipart to this
+# list, any messages with attachments will be rejected by the pass
+# filter.
 pass_mime_types = """multipart/mixed
 multipart/alternative
 text/plain"""
 
-# Skal Mailman konvertere text/html dele til ren tekst? Denne
-# konvertering vil finde sted efter at MIME filteret har fjernet de
-# uønskede dele.
+# Remove message attachments that have a matching filename extension.
+filter_filename_extensions = """exe
+bat
+cmd
+com
+pif
+scr
+vbs
+cpl"""
+
+# Remove message attachments that don't have a matching filename
+# extension.  Leave this field blank to skip this filter test.
+pass_filename_extensions = ''
+
+# Should Mailman collapse multipart/alternative to its first part
+# content?
+#
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
+collapse_alternatives = True
+
+# Should Mailman convert text/html parts to plain text?  This conversion
+# happens after MIME attachments have been stripped.
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 convert_html_to_plaintext = 1
 
-# Her bestemmer du hvad der skal ske, når en meddelelse filtreres fra af
-# et filter, altså hvis vedh&aelig;ftningen filtreres fra af MIME
-# filteret, eller en vedh&aelig;ftning ikke har en af de gyldige MIME
-# typer, eller meddelelsen ender med at være tom efter filtrering.
-# 
-# Bemærk at det du vælger her ikke vil ske hvis en meddelelse stadig
-# indeholder noget efter filtrering. Så vil meddelelsen altid blive
-# sendt videre til listen.
-# 
-# Når meddelelsen afvises, skrives Message-ID for den afviste meddelelse
-# til loggen. Når meddelelsen sendes retur eller videresendes til
-# listens ejer, vil en begrundelse altid blive inkluderet i den
-# returmail der sendes til afsenderen. Når meddelelserne skal bevares,
-# gemmes de i et specielt køkatalog på disken, sådan at
-# serveradministrator kan se (og måske gøre noget med) dem, men bliver
-# ellers fjernet. Dette sidste valg er kun tilgængeligt hvis
-# serveradministrator har tilladt det.
-#
-# gyldige værdier:
-#    0 = "Slet"
-#    1 = "Afvis"
-#    2 = "Videresend til Listens Ejer"
-#    3 = "Bevar"
+# One of these actions is taken when the message matches one of the
+# content filtering rules, meaning, the top-level content type matches
+# one of the <a href="?VARHELP=contentfilter/filter_mime_types"
+# >filter_mime_types, or the top-level content type does not match one
+# of the <a href="?VARHELP=contentfilter/pass_mime_types"
+# >pass_mime_types, or if after filtering the subparts of the message,
+# the message ends up empty.
+# 
+# Note this action is not taken if after filtering the message still
+# contains content.  In that case the message is always forwarded on to
+# the list membership.
+# 
+# When messages are discarded, a log entry is written containing the
+# Message-ID of the discarded message.  When messages are rejected or
+# forwarded to the list owner, a reason for the rejection is included in
+# the bounce message to the original author.  When messages are
+# preserved, they are saved in a special queue directory on disk for the
+# site administrator to view (and possibly rescue) but otherwise
+# discarded.  This last option is only available if enabled by the site
+# administrator.
+#
+# legal values are:
+#    0 = "Discard"
+#    1 = "Reject"
+#    2 = "Forward to List Owner"
+#    3 = "Preserve"
 filter_action = 0
 
 ## Topics options
 #
-# Emneord for listen
-
-# Emnefilteret kategoriserer hver e-mail som kommer til listen, efter de
-# regexp-udtryk du skriver nedenfor. Hvis felterne Subject: eller
-# Keywords: i brevhovedet i en mail stemmer overens med et af disse
-# udtryk, bliver mailen placeret under det p&aring;g&aelig;ldende emne.
-# Hvert medlem af listen kan vælge kun at modtage mail der passer til de
-# &oslash;nskede emner. E-mail som ikke h&oslash;rer under noget emne,
-# bliver ikke leveret.
-# 
-# Bem&aeligrk: Dette fungerer kun i normal-modus, ikke i
-# sammendrag-modus.
-# 
-# Indholdet i meddelelsen kan ogs&aring; unders&oslash;ges for Subject:
-# og Keyword: felter, alt efter hvad indstillingen
-# topics_bodylines_limit er sat til.
+# List topic keywords
+
+# The topic filter categorizes each incoming email message according to
+# <a href="http://www.python.org/doc/current/lib/module-re.html">regular
+# expression filters you specify below.  If the message's Subject: or
+# Keywords: header contains a match against a topic filter, the message
+# is logically placed into a topic bucket.  Each user can then choose to
+# only receive messages from the mailing list for a particular topic
+# bucket (or buckets).  Any message not categorized in a topic bucket
+# registered with the user is not delivered to the list.
+# 
+# Note that this feature only works with regular delivery, not digest
+# delivery.
+# 
+# The body of the message can also be optionally scanned for Subject:
+# and Keywords: headers, as specified by the <a
+# href="?VARHELP=topics/topics_bodylines_limit">topics_bodylines_limit
+# configuration variable.
 #
-# gyldige værdier:
-#    0 = "Ikke tilgængeligt"
-#    1 = "Tilgængeligt"
+# legal values are:
+#    0 = "Disabled"
+#    1 = "Enabled"
 topics_enabled = 0
 
-# Her angiver du hvor mange linier af mailens indhold emnefilteret skal
-# gennems&oslash;ge. En s&oslash;gning stopper n&aring;r det antal
-# linier er gennems&oslash;gt, eller n&aring;r den m&oslash;der en linie
-# som ikke ligner et brevhoved-felt. S&aelig;ttes denne v&aelig;rdi til
-# nul (0), vil ingen linier i indholdet blive unders&oslash;gt (dvs. kun
-# Keywords: og Subject: i brevhovedet unders&oslash;ges). S&aelig;ttes
-# denne v&aelig;rdi til et negativt tal, vil alle linier blive
-# unders&oslash;gt frem til den f&oslash;rste linie som ikke ligner et
-# brevhoved-felt.
+# The topic matcher will scan this many lines of the message body
+# looking for topic keyword matches.  Body scanning stops when either
+# this many lines have been looked at, or a non-header-like body line is
+# encountered.  By setting this value to zero, no body lines will be
+# scanned (i.e. only the Keywords: and Subject: headers will be
+# scanned).  By setting this value to a negative number, then all body
+# lines will be scanned until a non-header-like line is encountered.
+# 
 topics_bodylines_limit = 5
 
-# Hvert emneord er faktisk et regexp-udtryk, der sammenlignes med dele
-# af mailen, nemlig felterne Keywords: og Subject: i brevhovedet.
-# Bem&aelig;rk at de f&oslash;rste linier i mailens indhold ogs&aring;
-# kan best&aring; af s&aring;danne "felter", og de kan dermed ogs&aring;
-# blive unders&oslash;gt.
+# Each topic keyword is actually a regular expression, which is matched
+# against certain parts of a mail message, specifically the Keywords:
+# and Subject: message headers. Note that the first few lines of the
+# body of the message can also contain a Keywords: and Subject: "header"
+# on which matching is also performed.
 topics = []
 
diff --git a/mailman/friends.members b/mailman/friends.members
index 999b8ad..fec2d04 100644
--- a/mailman/friends.members
+++ b/mailman/friends.members
@@ -8,74 +8,52 @@ alo@jones.dk
 anarres@postmaster.co.uk
 anders@jones.dk
 ane@jones.dk
-anne@jones.dk
 ascanius@jones.dk
 assenbjerg@jones.dk
-awh@jones.dk
-benny@jones.dk
 bering@binx.com
-betina@jones.dk
 bettina@jones.dk
 bjorn@daimi.au.dk
 bolette@jones.dk
 borking@jones.dk
 bsmedegaard@sol.dk
-camilla@jones.dk
 chr.h@pobox.com
 chsje@tdk.dk
-cm@jones.dk
 cpoll@get2net.dk
 cro@kaosman.com
 daenzer@debian.org
-dewd@jones.dk
 diva@jones.dk
-dolmer@jones.dk
 donvet1@hotmail.com
 dreijer@jones.dk
 elaksj@post10.tele.dk
 elmahan@yahoo.com
 emilie@jones.dk
 emilmail@another.com
-emma@jones.dk
 erica@kaospilot.dk
 esben@jones.dk
-eva@jones.dk
-evamaria@jones.dk
 fair@get2net.dk
-fire@jones.dk
-flip@jones.dk
-frederik@jones.dk
-fsl@jones.dk
 gio@jones.dk
 global@jones.dk
-go@jones.dk
 grit@jones.dk
-grohmann@jones.dk
 helle_dk24@hotmail.com
-henrik@jones.dk
-hh@jones.dk
 hilde@jones.dk
-hvam@jones.dk
+id@jones.dk
 ingersme@pobox.com
 izi6@walla.co.il
-izi@jones.dk
 izi_versano@hotmail.com
 izig@walla.co.il
+jais@jones.dk
 janus@netcetera.dk
-jason@jones.dk
-jens@jones.dk
-jfe@jones.dk
 jgh@jones.dk
 joachim@jones.dk
 jonas@jones.dk
 jorgen@jones.dk
 jourand.jorgensen@get2net.dk
-joy@jones.dk
 jukka.rajala@iki.fi
 juri_j@yahoo.com
 justadewd@altavista.net
 karenringsmose@hotmail.com
 karina@jones.dk
+karineggert@jones.dk
 katja@jones.dk
 keld@jones.dk
 kim@jones.dk
@@ -121,14 +99,11 @@ mogens@jones.dk
 morgan@jones.dk
 mortenp@tuba.dk
 mp@jones.dk
-mr@jones.dk
 nahumury@xs4all.nl
 nancy@jones.dk
 negon@pop.agora.dk
 nelle@chaos.wit.no
-nicolai@jones.dk
 niels@jones.dk
-nils@jones.dk
 nina@jones.dk
 nors@jones.dk
 o.smedegaard@mobilixnet.dk
@@ -159,14 +134,12 @@ rune@jones.dk
 sa@minisoft.dk
 samuel@jones.dk
 sanna@jones.dk
-saturn@jones.dk
 scn73@hotmail.com
 sebwijk@jones.dk
 sg@jones.dk
 sj@jones.dk
 skafte75@hotmail.com
 skkh@jones.dk
-sm@jones.dk
 smedegaard@12move.dk
 snovz@hotmail.com
 spannung@post7.tele.dk
diff --git a/mailman/friends.py b/mailman/friends.py
index efc46bb..c51e4d7 100644
--- a/mailman/friends.py
+++ b/mailman/friends.py
@@ -1,386 +1,373 @@
-## Indstillinger for maillisten "friends"  -*- python -*-
-## Dato: Sun Dec 11 16:35:56 2005
+# -*- python -*-
+# -*- coding: us-ascii -*-
+## "friends" mailing list configuration settings
+## captured on Tue Mar 20 08:52:18 2007
 
 ## General options
 #
-# Grundlæggende egenskaber for listen, herunder en beskrivelse af
-# listen. 
-
-# Du kan f.eks. stave navnet med stort forbogstav eller ændre andre
-# bogstaver til store, s&aring; navnet bliver udtalt rigtigt eller at
-# forkortelser fremhæves. Bemærk at dette navn bruges i e-maillistens
-# adresse (f.eks. i bekræftelser ved tilmeldinger), s&aring; navnet kan
-# ikke ændres p&aring; nogen anden m&aring;de. (e-mailadresser er ikke
-# f&oslash;lsomme for store eller sm&aring; bogstaver, men de er
-# f&oslash;lsomme for n&aelig;sten alt andet :-)
+# Fundamental list characteristics, including descriptive info and basic
+# behaviors.
+
+# The capitalization of this name can be changed to make it presentable
+# in polite company as a proper noun, or to make an acronym part all
+# upper case, etc.  However, the name will be advertised as the email
+# address (e.g., in subscribe confirmation notices), so it should not be
+# otherwise altered.  (Email addresses are not case sensitive, but they
+# are sensitive to almost everything else :-)
 real_name = 'Friends'
 
-# Der er to roller forbundet med hver mailliste. Listeadministratorerne
-# er dem der som sidste instans har kontrol over alle indstillingerne
-# for maillisten. De kan &aelig;ndre alle indstillinger der er
-# tilg&aelig;ngelige via disse administrative websider.
-# 
-# Listemoderatorerne har begrænset adgang; de kan ikke ændre
-# indstillinger for e-maillisten, men de kan tage sig af anmodninger i
-# forbindelse med listen, f.eks. anmodning om medlemskab, eller
-# godkende/afvise meddelelser der skal godkendes for at kunne udsendes
-# til listen. Listeadministratorerne kan ogs&aring; udf&oslash;re disse
-# opgaver.
-# 
-# For at aktivere muligheden for at have listemoderatorer, og p&aring;
-# den m&aring;de fordele arbejdsopgaverne i forbindelse med listen, skal
-# du anf&oslash;re din egen moderatoradgangskode, og angive
-# e-mailadresser for den/dem som skal v&aelig;re listemoderator(er).
-# Bemærk at i tekstboksene nedenfor skal du skrive e-mailadresser for
-# listeadministratorer.
+# There are two ownership roles associated with each mailing list.  The
+# list administrators are the people who have ultimate control over all
+# parameters of this mailing list.  They are able to change any list
+# configuration variable available through these administration web
+# pages.
+# 
+# The list moderators have more limited permissions; they are not able
+# to change any list configuration variable, but they are allowed to
+# tend to pending administration requests, including approving or
+# rejecting held subscription requests, and disposing of held postings.
+# Of course, the list administrators can also tend to pending requests.
+# 
+# In order to split the list ownership duties into administrators and
+# moderators, you must set a separate moderator password, and also
+# provide the email addresses of the list moderators.  Note that the
+# field you are changing here specifies the list administrators.
 owner = ['dr@jones.dk']
 
-# Der er to ejer-roller forbundet med hver mailliste.
-# Listeadministratorerne er dem der har den endelige kontrol over alle
-# indstillingerne for e-mallisten. De kan &aelig;ndre alle indstillinger
-# der er tilgængelige via disse administrative websider.
-# 
-# Listemoderatorerne har begr&aelig;nset adgang; de kan ikke &aelig;ndre
-# indstillinger for e-maillisten, men de kan tage sig af anmodninger
-# ang&aring;ende listen, f.eks. anmodning om medlemskab, eller
-# godkende/afvise meddelelser der skal godkendes for at kunne udsendes
-# p&aring; listen. Listeadministratorerne kan selvsagt ogs&aring;
-# udf&oslash;re disse opgaver.
-# 
-# For at aktivere muligheden for at have listemoderatorer, og p&aring;
-# den m&aring;de fordele arbejdsopgaverne i forbindelse med listen, skal
-# du anf&oslash;re din egen moderatoradgangskode, og indtaste
-# e-mailadresser for den/dem der skal v&aelig;re listemoderatore(r).
-# Bemærk, at i tekstboksene nedenfor skal du skrive listemoderator
-# e-mailadresse(r).
+# There are two ownership roles associated with each mailing list.  The
+# list administrators are the people who have ultimate control over all
+# parameters of this mailing list.  They are able to change any list
+# configuration variable available through these administration web
+# pages.
+# 
+# The list moderators have more limited permissions; they are not able
+# to change any list configuration variable, but they are allowed to
+# tend to pending administration requests, including approving or
+# rejecting held subscription requests, and disposing of held postings.
+# Of course, the list administrators can also tend to pending requests.
+# 
+# In order to split the list ownership duties into administrators and
+# moderators, you must set a separate moderator password, and also
+# provide the email addresses of the list moderators in this section.
+# Note that the field you are changing here specifies the list
+# moderators.
 moderator = []
 
-# Denne beskrivelse benyttes n&aring;r denne malliste listes op sammen
-# med andre maillister, i toptekster, osv. Den b&oslash;r v&aelig;re
-# s&aring; kort som overhovedet mulig, uden at det bliver uklart hvad
-# meningen med maillisten er eller hvad den skal bruges til.
+# This description is used when the mailing list is listed with other
+# mailing lists, or in headers, and so forth.  It should be as succinct
+# as you can get it, while still identifying what the list is.
 description = 'News about me to all of my friends'
 
-# Teksten tolkes som html bortset fra linieskift, der vil blive
-# &aelig;ndret til html-tag'et '<br>', sådan at du kan benytte links,
-# forh&aring;ndsformateret tekst, osv. Men brug alts&aring; kun
-# linieskift der hvor du vil have et nyt afsnit. V&aelig;r meget
-# omhyggelig, hvis du benytter html-kode. Fejl (f.eks. manglende
-# slut-tag's) kan f&oslash;re til at listens informationsside ikke
-# bliver vist s&aring;dan som den skal.
+# The text will be treated as html except that newlines will be
+# translated to <br> - so you can use links, preformatted text, etc, but
+# don't put in carriage returns except where you mean to separate
+# paragraphs.  And review your changes - bad html (like some
+# unterminated HTML constructs) can prevent display of the entire
+# listinfo page.
 info = """Once upon a time I started spreading newsletters to people I thought would be happy to know about my thoughts, work and sparetime.
 
 Now I have put it into a regular maling list server, giving you the option *not* to receive these mails - or how and when..."""
 
 # This text will be prepended to subject lines of messages posted to the
-# list, to distinguish mailing list messages in in mailbox summaries.
+# list, to distinguish mailing list messages in mailbox summaries.
 # Brevity is premium here, it's ok to shorten long mailing list names to
 # something more concise, as long as it still identifies the mailing
-# list.
+# list. You can also add a sequential number by %d substitution
+# directive. eg.; [listname %d] -> [listname 123] (listname %05d) ->
+# (listname 00123)
+# 
 subject_prefix = '[Friends] '
 
-# Skjul afsenderen af meddelelser, ved at erstatte den med e-maillistens
-# adresse (Dette medfører at alle From:, Sender, og Reply-To: felter
-# fjernes)
+# Hide the sender of a message, replacing it with the list address
+# (Removes From, Sender and Reply-To fields)
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 anonymous_list = 0
 
-# Skal eksisterende Reply-To: felt i brevhovedet fjernes? Hvis ja, vil
-# dette blive gjort uanset om Mailman tilføjer et Reply-To: felt eller
-# ikke.
+# Should any existing Reply-To: header found in the original message be
+# stripped?  If so, this will be done regardless of whether an explict
+# Reply-To: header is added by Mailman or not.
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 first_strip_reply_to = 0
 
-# Denne indstillling fort&aelig;ller hvad Mailman skal g&oslash;re med
-# Reply-To: feltet i brevhovedet p&aring; e-mail der sendes til listen.
-# Hvis den er sat til Afsender, vil Mailman ikke tilf&oslash;je noget
-# Reply-To: felt, men findes et s&aring;dant felt allerede, vil det ikke
-# blive fjernet. S&aelig;ttes indstillingen til enten e-maillistens
-# adresse eller Egendefineret adresse, vil Mailman tilf&oslash;je, evt.
-# erstatte, et Reply-To: felt. (Egendefineret adresse inds&aelig;tter
-# v&aelig;rdien af indstillingen reply_to_address).
-# 
-# Der er flere grunde til ikke at indf&oslash;re eller erstatte
-# Reply-To: felter. En grund kan v&aelig;re at nogen af dem der sender
-# mail til listen er afh&aelig;ngige af selv at kunne s&aelig;tte
-# Reply-To: adressen. En anden grund er at modifikation af Reply-To:
-# adressen g&oslash;r det vanskeligere kun at sende svar til afsender.
-# Se 'Reply-To' Munging Considered Harmful for en diskussion omkring
-# emnet. Se Reply-To Munging Considered Useful for modsatte meninger.
-# 
-# Nogle maillister har begr&aelig;nset adgang, med en parallel liste
-# beregnet til diskussioner. Eksempler p&aring; dette er 'patches' eller
-# 'checkin' lister, som system for revisionskontrol sender
-# &aelig;ndringer i programmet til, men diskussioner omkring udvikling
-# af programmet sendes til udviklernes egen mailliste. For at
-# underst&oslash;tte lignende e-maillister, v&aelig;lg Egendefineret
-# adresse og s&aelig;t Reply-To: adressen i indstillingen
-# reply_to_address til at pege på den parallelle diskussionsliste.
-#
-# gyldige værdier:
-#    0 = "Afsender"
-#    1 = "mail listens adresse"
-#    2 = "Egendefineret adresse"
+# This option controls what Mailman does to the Reply-To: header in
+# messages flowing through this mailing list.  When set to Poster, no
+# Reply-To: header is added by Mailman, although if one is present in
+# the original message, it is not stripped.  Setting this value to
+# either This list or Explicit address causes Mailman to insert a
+# specific Reply-To: header in all messages, overriding the header in
+# the original message if necessary (Explicit address inserts the value
+# of <a href="?VARHELP=general/reply_to_address">reply_to_address).
+# 
+# There are many reasons not to introduce or override the Reply-To:
+# header.  One is that some posters depend on their own Reply-To:
+# settings to convey their valid return address.  Another is that
+# modifying Reply-To: makes it much more difficult to send private
+# replies.  See <a
+# href="http://www.unicom.com/pw/reply-to-harmful.html">`Reply-To'
+# Munging Considered Harmful for a general discussion of this issue.
+# See <a
+# href="http://www.metasystema.net/essays/reply-to.mhtml">Reply-To
+# Munging Considered Useful for a dissenting opinion.
+# 
+# Some mailing lists have restricted posting privileges, with a parallel
+# list devoted to discussions.  Examples are `patches' or `checkin'
+# lists, where software changes are posted by a revision control system,
+# but discussion about the changes occurs on a developers mailing list.
+# To support these types of mailing lists, select Explicit address and
+# set the Reply-To: address below to point to the parallel list.
+#
+# legal values are:
+#    0 = "Poster"
+#    1 = "This list"
+#    2 = "Explicit address"
 reply_goes_to_list = 0
 
-# Her definerer du adressen der skal s&aelig;ttes i Reply-To: feltet
-# n&aring;r indstillingen reply_goes_to_list er sat til Egendefineret
-# adresse.
-# 
-# Der findes mange grunde til at ikke indf&oslash;re eller erstatte
-# Reply-To: felter. En grund kan v&aelig;re at nogen af dem der sender
-# e-mail til listen er afh&aelig;ngige af selv at kunne s&aelig;tte
-# Reply-To: adressen. En anden grund er at modificering af Reply-To:
-# adressen g&oslash;r det vanskeligere at sende svar kun til afsender.
-# Se 'Reply-To' Munging Considered Harmful for en diskussion omkring
-# temaet. Se Reply-To Munging Considered Useful for modsatte meninger.
-# 
-# Nogle maillister har begr&aelig;nset adgang, med en egen parallel
-# liste beregnet for diskussioner. Eksempler p&aring; dette er 'patches'
-# eller 'checkin' lister, som system for revisionskontrol sender
-# &aelig;ndringer i programmet til, mens diskussioner omkring udvikling
-# af programmet sendes til udviklernes egen mailliste. For at
-# underst&oslash;tte s&aring;danne maillister, kan du definere Reply-To:
-# adressen her, og vælge Egendefineret adresse i indstillingen
-# reply_goes_to_list.
-# 
-# Bem&aelig;rk at hvis den oprindelige meddelelse indeholder et
-# Reply-To: felt, vil det ikke &aelig;ndres.
+# This is the address set in the Reply-To: header when the <a
+# href="?VARHELP=general/reply_goes_to_list">reply_goes_to_list option
+# is set to Explicit address.
+# 
+# There are many reasons not to introduce or override the Reply-To:
+# header.  One is that some posters depend on their own Reply-To:
+# settings to convey their valid return address.  Another is that
+# modifying Reply-To: makes it much more difficult to send private
+# replies.  See <a
+# href="http://www.unicom.com/pw/reply-to-harmful.html">`Reply-To'
+# Munging Considered Harmful for a general discussion of this issue.
+# See <a
+# href="http://www.metasystema.net/essays/reply-to.mhtml">Reply-To
+# Munging Considered Useful for a dissenting opinion.
+# 
+# Some mailing lists have restricted posting privileges, with a parallel
+# list devoted to discussions.  Examples are `patches' or `checkin'
+# lists, where software changes are posted by a revision control system,
+# but discussion about the changes occurs on a developers mailing list.
+# To support these types of mailing lists, specify the explicit
+# Reply-To: address here.  You must also specify Explicit address in the
+# reply_goes_to_list variable.
+# 
+# Note that if the original message contains a Reply-To: header, it will
+# not be changed.
 reply_to_address = ''
 
-# V&aelig;lg kun 'ja' her, hvis listen skal bruges som  "paraply" for
-# andre lister. Hvis 'ja' er valgt, vil bekr&aelig;ftelser og
-# meddelelser med adgangskode blive sendt til en adresse som konstrueres
-# ud fra medlemmets e-mailadresse - v&aelig;rdien af indstillingen
-# "umbrella_member_suffix" tilf&oslash;jes medlemmets kontonavn (det som
-# st&aring;r f&oslash;r @-tegnet).
+# Set this to yes when this list is intended to cascade only to other
+# mailing lists.  When set, meta notices like confirmations and password
+# reminders will be directed to an address derived from the member's
+# address - it will have the value of "umbrella_member_suffix" appended
+# to the member's account name.
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 umbrella_list = 0
 
-# N&aring;r "umbrella_list" indikerer at denne liste har andre
-# maillister som medlemmer, skal administrative meddelelser som f.eks.
-# bekr&aelig;ftelser og p&aring;mindelser om adgangskode ikke sendes til
-# selve listen, men snarere til administrator for listen. V&aelig;rdien
-# af denne indstilling bestemmer, hvilken adresse administrative
-# meddelelser skal sendes til. '-owner' er et almindeligt valg for denne
-# indstilling. Denne indstilling har ingen effekt n&aring;r
-# "umbrella_list" er sat til "Nej".
+# When "umbrella_list" is set to indicate that this list has other
+# mailing lists as members, then administrative notices like
+# confirmations and password reminders need to not be sent to the member
+# list addresses, but rather to the owner of those member lists.  In
+# that case, the value of this setting is appended to the member's
+# account name for such notices.  `-owner' is the typical choice.  This
+# setting has no effect when "umbrella_list" is "No".
 umbrella_member_suffix = '-owner'
 
-# Aktiver denne, hvis der skal sendes en p&aring;mindelse om adgangskode
-# til medlemmerne en gang hver m&aring;ned. Husk at medlemmerne
-# ogs&aring; selv kan frav&aelig;lge dette.
+# Turn this on if you want password reminders to be sent once per month
+# to your members.  Note that members may disable their own individual
+# password reminders.
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 send_reminders = 0
 
-# Tekst du skriver her vil blive tilf&oslash;jet &oslash;verst i
-# velkomsthilsenen der sendes til nye medlemmer. Velkomshilsenen
-# indeholder i forvejen vigtige adresser og URLer knyttet til
-# maillisten, s&aring; den slags information er det ikke
-# n&oslash;dvendigt at inkludere her. Her kan du tilf&oslash;je f.eks.
-# oplysning om etikette eller regler for brug af listen, o.l.
-# 
-# Bem&aelig;rk: Linierne i denne tekst vil brydes efter f&oslash;lgende
-# regler:
+# This value, if any, will be added to the front of the new-subscriber
+# welcome message.  The rest of the welcome message already describes
+# the important addresses and URLs for the mailing list, so you don't
+# need to include any of that kind of stuff here.  This should just
+# contain mission-specific kinds of things, like etiquette policies or
+# team orientation, or that kind of thing.
 # 
-# Hvert afsnit udfyldes s&aringdan at ingen linie er l&aelig;ngere en 70
-# tegn. Enhver linie der begynder med tomme tegn udfyldes ikke. Tomme
-# linier adskiller afsnit.
+# Note that this text will be wrapped, according to the following rules:
+# Each paragraph is filled so that no line is longer than 70 characters.
+# Any line that begins with whitespace is not filled. A blank line
+# separates paragraphs.
 # 
 welcome_msg = """Once upon a time I started spreading newsletters to people I thought would be happy to know about my thoughts, work and sparetime.
 
 Now I have put it into a regular maling list server, giving you the option *not* to receive these mails - or how and when..."""
 
-# S&aelig;t kun denne til 'Nej' hvis du skal tilf&oslash;je nye
-# medlemmer manuelt, og ikke vil have at de f&aring;r det at vide. Dette
-# er meget nyttigt n&aring;r man g&aring;r fra et andet mallistesystem
-# og til Mailman, og vil have at overgangen skal v&aelig;re s&aring;
-# lidt m&aelig;rkbar som muligt.
+# Turn this off only if you plan on subscribing people manually and
+# don't want them to know that you did so.  This option is most useful
+# for transparently migrating lists from some other mailing list manager
+# to Mailman.
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 send_welcome_msg = 1
 
-# Tekst der sendes til medlemmer der framelder sig listen. Hvis feltet
-# er tomt, tilf&oslash;jes der ikke nogen speciel tekst til
-# frameldingen.
+# Text sent to people leaving the list.  If empty, no special text will
+# be added to the unsubscribe message.
 goodbye_msg = ''
 
-# Send afskedshilsen til medlemmer n&aring;r de frameldes?
+# Send goodbye message to members when they are unsubscribed?
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 send_goodbye_msg = 1
 
-# Der udsendes en p&aring;mindelse til listemoderator (og
-# listeadministrator) dagligt om anmodninger der af en eller anden grund
-# venter p&aring; behandling. V&aelig;lger du "Ja", vil
-# listeadminstrator ogs&aring; modtage en meddelelse s&aring; snart en
-# anmodning ankommer.
+# List moderators (and list administrators) are sent daily reminders of
+# requests pending approval, like subscriptions to a moderated list, or
+# postings that are being held for one reason or another.  Setting this
+# option causes notices to be sent immediately on the arrival of new
+# requests as well.
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 admin_immed_notify = 1
 
-# Skal listeadministrator modtage meddelelse om tilmeldinger og
-# afmeldinger?
+# Should administrator get notices of subscribes and unsubscribes?
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 admin_notify_mchanges = 1
 
-# Approval notices are sent when mail triggers certain of the limits
-# except routine list moderation and spam filters, for which notices are
-# not sent.  This option overrides ever sending the notice.
+# Send mail to poster when their posting is held for approval?
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 respond_to_post_requests = 1
 
-# Når dette valg er aktiveret, vil al e-mail til listen blive modereret.
-# Dette valg kan være nyttigt når din mailliste f.eks. har en såkaldt
-# "flamewar", altså en "krig" hvor medlemmer kun skælder ud på hinanden.
-# En "nød-moderering" kan da hjælpe dig at fjerne usaglige meddelelser
-# til listen, og på den måde dysse en ophedet diskussion ned.
+# When this option is enabled, all list traffic is emergency moderated,
+# i.e. held for moderation.  Turn this option on when your list is
+# experiencing a flamewar and you want a cooling off period.
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 emergency = 0
 
-# Når et nyt medlem tilmeldes listen, bliver medlemmets indstillinger
-# taget herfra.
+# When a new member is subscribed to this list, their initial set of
+# options is taken from the this variable's setting.
 new_member_options = 256
 
-# Filter for administrative meddelelser vil unders&oslash;ge om
-# meddelelsen egentligt er ment som en administrativ anmodning (f.eks.
-# tilmelding, framelding, o.l.), og i s&aring; fald sende meddelelsen
-# til listeadministrator i stedet for.
+# Administrivia tests will check postings to see whether it's really
+# meant as an administrative request (like subscribe, unsubscribe, etc),
+# and will add it to the the administrative requests queue, notifying
+# the administrator of the new request, in the process.
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 administrivia = 1
 
-# Maximum st&oslash;rrelse i kilobytes (KB) for indholdet i e-mail der
-# sendes til listen. Brug v&aelig;rdien '0' for ikke at have nogen
-# begr&aelig;nsning.
+# Maximum length in kilobytes (KB) of a message body.  Use 0 for no
+# limit.
 max_message_size = 40
 
-# "Maskinnavnet" er det navn som skal benyttes for e-mailadresser
-# relateret til Mailman p&aring; denne maskine, og er normalt navnet der
-# er forbundet med e-mail-servicen p&aring; maskinen. Denne indstilling
-# kan v&aelig;re nyttig hvis maskinen har flere navne.
+# The "host_name" is the preferred name for email to mailman-related
+# addresses on this host, and generally should be the mail host's
+# exchanger address, if any.  This setting can be useful for selecting
+# among alternative names of a host that has multiple addresses.
 host_name = 'jones.dk'
 
-# I RFC 2369 defineres en r&aelig;kke List-* felter i brevhovedet, der
-# normalt tilf&oslash;jes enhver meddelelse der sendes ud via listen.
-# Disse felter er til stor gavn for brugere , som benytter et
-# e-mailprogram der f&oslash;lger standarden. Disse felter b&oslash;r
-# derfor altid v&aelig;re med.
-# 
-# Ikke alle e-mailprogrammer f&oslash;lger denne standard. Hvis der er
-# mange medlemmer p&aring; listen, der benytter e-mailprogrammer, der
-# ikke kan h&aring;ndtere disse felter i brevhovedet, kan du v&aelig;lge
-# at udelade dem. Men du b&oslash;r f&oslash;rst fors&oslash;ge at
-# l&aelig;re og forklare medlemmerne hvad hensigten med s&aring;danne
-# felter er, og hvordan de kan skjule dem i deres e-mailprogram. Som en
-# sidste udvej kan du udelade felterne, men det anbefales ikke (og denne
-# mulighed kan faktisk ogs&aring; blive fjernet i senere versioner af
-# Mailman).
-#
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# RFC 2369 defines a set of List-* headers that are normally added to
+# every message sent to the list membership. These greatly aid end-users
+# who are using standards compliant mail readers.  They should normally
+# always be enabled.
+# 
+# However, not all mail readers are standards compliant yet, and if you
+# have a large number of members who are using non-compliant mail
+# readers, they may be annoyed at these headers.  You should first try
+# to educate your members as to why these headers exist, and how to hide
+# them in their mail clients.  As a last resort you can disable these
+# headers, but this is not recommended (and in fact, your ability to
+# disable these headers may eventually go away).
+#
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 include_rfc2369_headers = 1
 
-# List-Post: feltet er et af felterne anbefalet i RFC 2369. P&aring;
-# nogle e-maillister (som f.eks. kun bruges til
-# offentligg&oslash;relser), er det kun bestemte personer der har lov
-# til at poste til listen. Almindelige medlemmer af listen har normalt
-# ikke lov til at poste til listen. For den slags lister, er List-Post:
-# feltet misvisende. S&aelig;t denne indstilling til Nej, for at
-# undg&aring; at feltet tilf&oslash;jes. (Dette p&aring;virker ikke
-# andre List-*: felter.)
-#
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# The List-Post: header is one of the headers recommended by RFC 2369.
+# However for some announce-only mailing lists, only a very select group
+# of people are allowed to post to the list; the general membership is
+# usually not allowed to post.  For lists of this nature, the List-Post:
+# header is misleading. Select No to disable the inclusion of this
+# header. (This does not affect the inclusion of the other List-*:
+# headers.)
+#
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 include_list_post_header = 1
 
+# Discard held messages older than this number of days. Use 0 for no
+# automatic discarding.
+max_days_to_hold = 0
+
 ## Language options
 #
-# Underst&oslash;ttelse af flere sprog. (Internationalisering)
-
-# Dette er standardsproget som benyttes for denne mailliste. Hvis flere
-# end et sprog/ underst&oslash;ttes, vil medlemmer af listen selv kunne
-# v&aelig;lge hvilket sprog der skal benyttes n&aring;r de g&aring;r ind
-# p&aring; deres personlige webside, og n&aring;r meddelelser fra
-# systemet sendes til dem. Hvis medlemmerne ikke &aelig;ndrer noget
-# selv, vil dette standardsprog blive benyttet. Dette g&aelig;lder
-# b&aring;de web-baserede og e-mail-baserede meddelelser, men ikke
-# meddelelser sendt af listens medlemmer.
+# Natural language (internationalization) options.
+
+# This is the default natural language for this mailing list. If more
+# than one language is supported then users will be able to select their
+# own preferences for when they interact with the list.  All other
+# interactions will be conducted in the default language.  This applies
+# to both web-based and email-based messages, but not to email posted by
+# list members.
 preferred_language = 'en'
 
-# Her er alle sprog, som denne liste har underst&oslash;ttelse for.
-# Bem&aelig;rk at standardsproget skal v&aelig;re med.
+# These are all the natural languages supported by this list. Note that
+# the default language must be included.
 available_languages = ['da', 'en']
 
-# Hvis standardsproget for din mailliste benytter et andet tegns&aelig;t
-# end ASCII og Emne prefixet for listen indeholder tegn som ikke findes
-# i ASCII-tegns&aelig;ttet, vil prefixet altid blive kodet i henhold til
-# den relevante standard. Hvis Emne prefixet kun indeholder ASCII tegn,
-# ønsker du måske at vælge Aldrig for at undgå kodning. Dette kan gøre
-# emnet lidt mere læseligt for brugere med e-mailprogrammer der ikke kan
-# håndtere andre tegnsæt end ASCII.
-# 
-# Bemærk imidlertid, at hvis din mailliste modtager både kodede og
-# ukodede emnefelter , kan det være bedst at vælge Efter behov. Med
-# denne indstilling vil Mailman ikke kode ASCII prefixer hvis resten af
-# titelfeltet kun indeholder ASCII tegn, men vil kode prefixet hvis det
-# indeholder tegn som ikke er ASCII tegn. På denne måde undgås en
-# tvetydighed i standarderne, som forårsager at visse e-mailprogrammer
-# vil vise ekstra eller manglende mellemrum imellem emne prefixet og det
-# oprindelige emne.
-#
-# gyldige værdier:
-#    0 = "Aldrig"
-#    1 = "Altid"
-#    2 = "Efter behov"
+# If your mailing list's default language uses a non-ASCII character set
+# and the prefix contains non-ASCII characters, the prefix will always
+# be encoded according to the relevant standards.  However, if your
+# prefix contains only ASCII characters, you may want to set this option
+# to Never to disable prefix encoding.  This can make the subject
+# headers slightly more readable for users with mail readers that don't
+# properly handle non-ASCII encodings.
+# 
+# Note however, that if your mailing list receives both encoded and
+# unencoded subject headers, you might want to choose As needed.  Using
+# this setting, Mailman will not encode ASCII prefixes when the rest of
+# the header contains only ASCII characters, but if the original header
+# contains non-ASCII characters, it will encode the prefix.  This avoids
+# an ambiguity in the standards which could cause some mail readers to
+# display extra, or missing spaces between the prefix and the original
+# header.
+#
+# legal values are:
+#    0 = "Never"
+#    1 = "Always"
+#    2 = "As needed"
 encode_ascii_prefixes = 0
 
 ## Nondigest options
 #
-# Regler for levering i normal-modus.
+# Policies concerning immediately delivered list traffic.
 
-# Kan medlemmer vælge normal-modus?
+# Can subscribers choose to receive mail immediately, rather than in
+# batched digests?
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 nondigestable = 1
 
-# Tekst der tilføjes &oslash;verst i e-mail der sendes til listens
-# medlemmer. This text can include Python format strings which are
-# resolved against list attributes.  The list of substitutions allowed
-# are:
+# Text prepended to the top of every immediately-delivery message. This
+# text can include Python format strings which are resolved against list
+# attributes.  The list of substitutions allowed are:
 # 
 # 
 # real_name - The "pretty" name of the list; usually the list name with
@@ -405,10 +392,9 @@ nondigestable = 1
 # 
 msg_header = ''
 
-# Tekst som tilf&oslash;jes nederst i e-mail der sendes til listens
-# medlemmer. This text can include Python format strings which are
-# resolved against list attributes.  The list of substitutions allowed
-# are:
+# Text appended to the bottom of every immediately-delivery message.
+# This text can include Python format strings which are resolved against
+# list attributes.  The list of substitutions allowed are:
 # 
 # 
 # real_name - The "pretty" name of the list; usually the list name with
@@ -435,45 +421,54 @@ msg_footer = """_______________________________________________
 %(real_name)s maillist  -  %(real_name)s@%(host_name)s
 %(web_page_url)slistinfo/%(_internal_name)s"""
 
+# When you scrub attachments, they are stored in archive area and links
+# are made in the message so that the member can access via web browser.
+# If you want the attachments totally disappear, you can use content
+# filter options.
+#
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
+scrub_nondigest = False
+
 ## Digest options
 #
-# Opsætning af sammendrag-modus.
+# Batched-delivery digest characteristics.
 
-# Kan medlemmer af listen vælge sammendrag-modus?
+# Can list members choose to receive list traffic bunched in digests?
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 digestable = 1
 
-# Hvilken modus er standard for nye brugere?
+# Which delivery mode is the default for new users?
 #
-# gyldige værdier:
-#    0 = "Normal"
-#    1 = "Sammendrag"
+# legal values are:
+#    0 = "Regular"
+#    1 = "Digest"
 digest_is_default = 0
 
-# Hvilket format skal benyttes som standard for samle-email?
+# When receiving digests, which format is default?
 #
-# gyldige værdier:
-#    0 = "Ren tekst"
+# legal values are:
+#    0 = "Plain"
 #    1 = "MIME"
 mime_is_default_digest = 0
 
-# Hvor stor (i KB) m&aring; en samle-email h&oslash;jst v&aelig;re
-# f&oslash;r den udsendes?
+# How big in Kb should a digest be before it gets sent out?
 digest_size_threshhold = 30
 
-# Skal der sendes en samle-email dagligt, selv om st&oslash;rrelsen ikke
-# er opn&aring;et?
+# Should a digest be dispatched daily when the size threshold isn't
+# reached?
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 digest_send_periodic = 1
 
-# Tekst som tilf&oslash;jes &oslash;verst i samle-emailen, f&oslash;r
-# indholdsfortegnelsen.This text can include Python format strings which
+# Text attached (as an initial message, before the table of contents) to
+# the top of digests. This text can include Python format strings which
 # are resolved against list attributes.  The list of substitutions
 # allowed are:
 # 
@@ -500,10 +495,9 @@ digest_send_periodic = 1
 # 
 digest_header = ''
 
-# Tekst der tilføjes nederst i hver samle-email, som sidste
-# information.This text can include Python format strings which are
-# resolved against list attributes.  The list of substitutions allowed
-# are:
+# Text attached (as a final message) to the bottom of digests. This text
+# can include Python format strings which are resolved against list
+# attributes.  The list of substitutions allowed are:
 # 
 # 
 # real_name - The "pretty" name of the list; usually the list name with
@@ -530,277 +524,279 @@ digest_footer = """_______________________________________________
 %(real_name)s maillist  -  %(real_name)s@%(host_name)s
 %(web_page_url)slistinfo/%(_internal_name)s"""
 
-# N&aring;r et nyt volume startes, &oslash;ges volume nummeret, og
-# udgavenummeret s&aelig;ttes til 1.
+# When a new digest volume is started, the volume number is incremented
+# and the issue number is reset to 1.
 #
-# gyldige værdier:
-#    0 = "&Aring;rlig"
-#    1 = "M&aring;nedlig"
-#    2 = "Kvartalsvis"
-#    3 = "Ugentlig"
-#    4 = "Daglig"
+# legal values are:
+#    0 = "Yearly"
+#    1 = "Monthly"
+#    2 = "Quarterly"
+#    3 = "Weekly"
+#    4 = "Daily"
 digest_volume_frequency = 1
 
 ## Privacy options
 #
-# Her kan du bestemme hvad der kr&aelig;ves for at tilmelde sig til
-# maillisten, og bl.a. bestemme om maillisten skal v&aelig;re skjult
-# eller ikke. Se ogs&aring; <a
-# href="http://mail.jones.dk/cgi-bin/mailman/admin/friends/archive">Indstillinger 
-# for arkivering</a> for egne indstillinger, n&aring;r det g&aelig;lder
-# arkivet og arkivering.
+# This section allows you to configure subscription and membership
+# exposure policy.  You can also control whether this list is public or
+# not.  See also the <a
+# href="http://mail.jones.dk/cgi-bin/mailman/admin/friends/archive">Archival 
+# Options</a> section for separate archive-related privacy settings.
 
-# Vis denne mailliste n&aring;r nogen beder om at se en oversigt over
-# maillister p&aring; denne maskine?
+# Advertise this list when people ask what lists are on this machine?
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 advertised = 1
 
-# bekræftelse(*) - bekr&aelig;ftelse via e-mail er n&oslash;dvendig
-# godkendelse - anmodning om medlemskab skal godkendes af
-# listeadministrator (eller evt. listemoderator) bekr&aelig;ftelse +
-# godkendelse - b&aring;de bekr&aelig;ftelse via e-mail og godkendelse
-# fra listeadministrator (evt. listemoderator) er n&oslash;dvendig
-# 
-# (*) n&aring;r nogen vil tilmelde sig en liste, sender Mailman en
-# meddelelse med en unik identifikator som skal angives for at
-# bekr&aelig;fte tilmeldingen. P&aring; den m&aring;de vil det ikke
-# v&aelig;re muligt at tilmelde nogen imod deres vilje.
-#
-# gyldige værdier:
-#    1 = "Bekr&aelig;ftelse"
-#    2 = "Godkendelse"
-#    3 = "Bekr&aelig;ftelse og godkendelse"
+# Confirm (*) - email confirmation required Require approval - require
+# list administrator approval for subscriptions Confirm and approve -
+# both confirm and approve
+# 
+# (*) when someone requests a subscription, Mailman sends them a notice
+# with a unique subscription request number that they must reply to in
+# order to subscribe. This prevents mischievous (or malicious) people
+# from creating subscriptions for others without their consent.
+#
+# legal values are:
+#    1 = "Confirm"
+#    2 = "Require approval"
+#    3 = "Confirm and approve"
 subscribe_policy = 1
 
-# N&aring;r medlemmer &oslash;nsker at forlade en mailliste, sender de
-# en anmodning om framelding, enten via web, eller via e-mail. Normalt
-# er det bedst at disse anmodninger automatisk godkendes, s&aring;
-# medlemmer kan afmelde sig n&aring;r de &oslash;nsker det (mange
-# &oslash;nsker selv at kunne administrere en framelding). For nogle
-# f&aring; maillister kan det alligevel v&aelig;re aktuelt at have
-# kontrol over om medlemmer kan afmelde sig selv eller ej. En liste som
-# alle ansatte i et firma SKAL v&aelig;re medlem af, er et eksempel
-# p&aring; en s&aring;dan liste.
-#
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# When members want to leave a list, they will make an unsubscription
+# request, either via the web or via email. Normally it is best for you
+# to allow open unsubscriptions so that users can easily remove
+# themselves from mailing lists (they get really upset if they can't get
+# off lists!).
+# 
+# For some lists though, you may want to impose moderator approval
+# before an unsubscription request is processed.  Examples of such lists
+# include a corporate mailing list that all employees are required to be
+# members of.
+#
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 unsubscribe_policy = 0
 
-# Alle e-mailadresser som angives her vil blive udelukket fra listen, og
-# kan ikke tilmelde sig. Indtast e-mailadresser, en pr. linie, start
-# linien med tegnet ^ for at angive et regexp-udtryk der skal stemme
-# overens med afsenderadressen.
+# Addresses in this list are banned outright from subscribing to this
+# mailing list, with no further moderation required.  Add addresses one
+# per line; start the line with a ^ character to designate a regular
+# expression match.
 ban_list = []
 
-# Hvis denne indstilling ikke er sat til 'Alle', vil medlemslisten blive
-# beskyttet af medlemmernes eller administrators adgangskode.
+# When set, the list of subscribers is protected by member or admin
+# password authentication.
 #
-# gyldige værdier:
-#    0 = "Alle"
-#    1 = "Kun medlemmer af listen"
-#    2 = "Kun listeadministrator"
+# legal values are:
+#    0 = "Anyone"
+#    1 = "List members"
+#    2 = "List admin only"
 private_roster = 1
 
-# V&aelig;lger du 'Ja' her, vil medlemmers e-mailadresser blive
-# omskrevet n&aring;r de vises i en oversigt p&aring; websiderne
-# (b&aring;de som tekst og som links), s&aring; de ikke er nemme at
-# tolke som e-mailadresser. Formålet er at undg&aring; at medlemmernes
-# mailadresser bliver opsamlet af e-mailsniffere som skanner websider
-# for e-mailadresser (og derefter bruger dem til at udsende spam/junk
-# mail).
-#
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# Setting this option causes member email addresses to be transformed
+# when they are presented on list web pages (both in text and as links),
+# so they're not trivially recognizable as email addresses.  The
+# intention is to prevent the addresses from being snarfed up by
+# automated web scanners for use by spammers.
+#
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 obscure_addresses = 1
 
 ## Privacy options
 #
-# N&aring;r en meddelelse sendes til maillisten, g&aring;r den igennem
-# nogle trin for at afg&oslash;re om moderator skal godkende meddelelsen
-# eller ikke. Her finder du indstillinger til at kontrollere moderation
-# af e-mail fra b&aring;de medlemmer og ikke-medlemmer.
-# 
-# <p>E-mail fra medlemmer holdes tilbage for godkendelse hvis deres
-# <b>moderationsflag</b> er sat. Du kan bestemme om e-mail fra medlemmer
-# normalt skal vurderes eller ikke f&oslash;r den sendes til listen.
-# 
-# <p>E-mail som ikke er sendt af medlemmer af listen, kan automatisk
-# blive <a
-# href="?VARHELP=privacy/sender/accept_these_nonmembers">godkendt</a>,
-# <a href="?VARHELP=privacy/sender/hold_these_nonmembers">holdt tilbage
-# for godkendelse</a>, <a
-# href="?VARHELP=privacy/sender/reject_these_nonmembers">afvist (sendt
-# retur)</a>, eller <a
-# href="?VARHELP=privacy/sender/discard_these_nonmembers">slettet</a>,
-# enten enkeltvis eller som en gruppe. Al e-mail fra ikke-medlemmer, som
-# ikke specifikt bliver godkendt, sendt retur eller slettet, vil blive
-# behandlet alt efter hvad <a
-# href="?VARHELP=privacy/sender/generic_nonmember_action">generelle
-# regler for ikke-medlemmer</a> viser.
-# 
-# <p>I tekstboksene nedenfor kan du tilf&oslash;je en e-mailadresse pr.
-# linie. Du kan ogs&aring; tilf&oslash;je  <a
-# href="http://www.python.org/doc/current/lib/module-re.html">Python
-# regexp-udtryk</a>. Begynd i s&aring; fald linien med tegnet ^ for at
-# markere at det er et s&aring;dant udtryk. N&aring;r du benytter
-# backslash, skriv da lige som i rene strings (Python raw strings)
-# (normalt kun &eacute;n backslash ad gangen).
-# 
-# <p>Bem&aelig;rk: sammenligning med normale e-mailadresser
-# udf&oslash;res f&oslash;rst, regexp-udtryk vil derfor blive behandlet
-# sidst.
-
-# Hvert medlem af listen har et moderationsflag som fort&aelig;ller om
-# e-mails fra medlemmet kan sendes direkte til e-maillisten, eller om de
-# f&oslash;rst skal godkendes af listemoderator. N&aring;r
-# moderationsflaget er sat til, skal e-mails fra medlemmet godkendes af
-# listemoderator f&oslash;r de udsendes til alle p&aring; listen. Som
-# listeadministrator kan du for hvert enkelt medlem bestemme om
-# medlemmets e-mail skal modereres eller ikke. N&aring;r et nyt medlem
-# tilmeldes listen, s&aelig;ttes moderationsflaget til den indstilling
-# du v&aelig;lger her. S&aelig;t den til 'Nej' hvis du &oslash;nsker at
-# e-mail fra medlemmer normalt skal g&aring; lige til listen. S&aelig;t
-# den til 'Ja' hvis du &oslash;nsker at e-mail fra nye medlemmer skal
-# godkendes f&oslash;r de udsendes til hele listen. Du kan altid
-# s&aelig;tte moderationsflaget for hvert enkelt medlem fra
-# Administration af medlemmer siden.
-#
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# When a message is posted to the list, a series of moderation steps are
+# take to decide whether the a moderator must first approve the message
+# or not.  This section contains the controls for moderation of both
+# member and non-member postings.
+# 
+# <p>Member postings are held for moderation if their <b>moderation
+# flag</b> is turned on.  You can control whether member postings are
+# moderated by default or not.
+# 
+# <p>Non-member postings can be automatically <a
+# href="?VARHELP=privacy/sender/accept_these_nonmembers" >accepted</a>,
+# <a href="?VARHELP=privacy/sender/hold_these_nonmembers">held for
+# moderation</a>, <a
+# href="?VARHELP=privacy/sender/reject_these_nonmembers" >rejected</a>
+# (bounced), or <a
+# href="?VARHELP=privacy/sender/discard_these_nonmembers"
+# >discarded</a>, either individually or as a group.  Any posting from a
+# non-member who is not explicitly accepted, rejected, or discarded,
+# will have their posting filtered by the <a
+# href="?VARHELP=privacy/sender/generic_nonmember_action">general
+# non-member rules</a>.
+# 
+# <p>In the text boxes below, add one address per line; start the line
+# with a ^ character to designate a <a href=
+# "http://www.python.org/doc/current/lib/module-re.html" >Python regular
+# expression</a>.  When entering backslashes, do so as if you were using
+# Python raw strings (i.e. you generally just use a single backslash).
+# 
+# <p>Note that non-regexp matches are always done first.
+
+# Each list member has a moderation flag which says whether messages
+# from the list member can be posted directly to the list, or must first
+# be approved by the list moderator.  When the moderation flag is turned
+# on, list member postings must be approved first.  You, the list
+# administrator can decide whether a specific individual's postings will
+# be moderated or not.
+# 
+# When a new member is subscribed, their initial moderation flag takes
+# its value from this option.  Turn this option off to accept member
+# postings by default.  Turn this option on to, by default, moderate
+# member postings first.  You can always manually set an individual
+# member's moderation bit by using the membership management screens.
+#
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 default_member_moderation = 1
 
+# Hold -- this holds the message for approval by the list moderators.
 # 
-# Hold tilbage -- meddelelsen holdes tilbage for godkendelse af
-# listemoderator(er). Afvis -- meddelelsen sendes automatisk retur til
-# afsender. Begrundelsen der sendes kan du skrive selv Slet --
-# meddelelsen bliver fjernet uden at give besked om dette til afsender.
+# Reject -- this automatically rejects the message by sending a bounce
+# notice to the post's author.  The text of the bounce notice can be <a
+# href="?VARHELP=privacy/sender/member_moderation_notice" >configured by
+# you.
+# 
+# Discard -- this simply discards the message, with no notice sent to
+# the post's author.
 # 
 #
-# gyldige værdier:
-#    0 = "Hold&nbsp;tilbage"
-#    1 = "Afvis"
-#    2 = "Slet"
+# legal values are:
+#    0 = "Hold"
+#    1 = "Reject"
+#    2 = "Discard"
 member_moderation_action = 0
 
-# Tekst som skal sendes med meddelelsen om afvisning som sendes til
-# modererede medlemmer af listen.
+# Text to include in any <a
+# href="?VARHELP/privacy/sender/member_moderation_action" >rejection
+# notice to be sent to moderated members who post to this list.
 member_moderation_notice = ''
 
-# E-mail fra disse ikke-medlemmer vil automatisk blive godkendt.
-# Tilf&oslash;j e-mailadresser, en pr. linie. Start linien med tegnet ^
-# for at angive et regexp-udtryk som skal stemme overens med
-# afsenderadressen.
+# Postings from any of these non-members will be automatically accepted
+# with no further moderation applied.  Add member addresses one per
+# line; start the line with a ^ character to designate a regular
+# expression match.
 accept_these_nonmembers = ['dr@jones.dk', 'dr.jones@pobox.com']
 
-# e-mail fra disse ikke-medlemmer vil automatisk blive holdt tilbage for
-# vurdering af listemoderator. Afsenderen vil modtage en meddelelse om
-# dette, med bl.a. instruktioner om hvordan han/hun kan
-# tilbagetr&aelig;kke sin e-mail. Indtast e-mailadresser, en pr. linie.
-# Start linien med tegnet ^ for at angive et regexp-udtryk som skal
-# stemme overens med afsenderadressen.
+# Postings from any of these non-members will be immediately and
+# automatically held for moderation by the list moderators. The sender
+# will receive a notification message which will allow them to cancel
+# their held message.  Add member addresses one per line; start the line
+# with a ^ character to designate a regular expression match.
 hold_these_nonmembers = []
 
-# E-mail fra disse ikke-medlemmer vil automatisk blive afvist. De vil
-# f&aring; mailen retur, med en meddelelse om at den blev automatisk
-# afvist. Dette valg b&oslash;r ikke benyttes for kendte spammere, de
-# b&oslash;r automatisk slettes. Indtast e-mailadresser, en pr. linie.
-# Start linien med tegnet ^ for at angive et regexp-udtryk som skal
-# stemme overens med afsenderadressen.
+# Postings from any of these non-members will be automatically rejected.
+# In other words, their messages will be bounced back to the sender with
+# a notification of automatic rejection.  This option is not appropriate
+# for known spam senders; their messages should be <a
+# href="?VARHELP=privacy/sender/discard_these_nonmembers" >automatically
+# discarded.
+# 
+# Add member addresses one per line; start the line with a ^ character
+# to designate a regular expression match.
 reject_these_nonmembers = []
 
-# E-mail fra disse ikke-medlemmer vil automatisk blive slettet. Det vil
-# sige at meddelelsen afvises uden nogen form for tilbagemelding, men
-# listemoderator kan (om &oslash;nsket) modtage en kopi af den afviste
-# e-mail. Tilf&oslash;j e-mailadresser, en pr. linie, start linien med
-# tegnet ^ for at angive et regexp-udtryk der skal stemme overens med
-# afsenderadressen.
+# Postings from any of these non-members will be automatically
+# discarded.  That is, the message will be thrown away with no further
+# processing or notification.  The sender will not receive a
+# notification or a bounce, however the list moderators can optionally
+# <a href="?VARHELP=privacy/sender/forward_auto_discards" >receive
+# copies of auto-discarded messages..
+# 
+# Add member addresses one per line; start the line with a ^ character
+# to designate a regular expression match.
 discard_these_nonmembers = []
 
-# N&aring;r en e-mail fra et ikke-medlem bliver modtaget, sammenlignes
-# e-mailens afsender med listen over e-mailadresser der skal godkendes,
-# holdes tilbage, <a
-# href="?VARHELP=privacy/sender/reject_these_nonmembers" >afvises
-# (sendes retur), eller slettes. Hvis afsenderadressen ikke stemmer
-# overens med en adresse der findes i listerne, bliver f&oslash;lgende
-# afg&oslash;relse truffet.
-#
-# gyldige værdier:
-#    0 = "Godkend"
-#    1 = "Hold&nbsp;tilbage"
-#    2 = "Afvis"
-#    3 = "Slet"
+# When a post from a non-member is received, the message's sender is
+# matched against the list of explicitly <a
+# href="?VARHELP=privacy/sender/accept_these_nonmembers" >accepted,
+# held, <a href="?VARHELP=privacy/sender/reject_these_nonmembers"
+# >rejected (bounced), and <a
+# href="?VARHELP=privacy/sender/discard_these_nonmembers" >discarded
+# addresses.  If no match is found, then this action is taken.
+#
+# legal values are:
+#    0 = "Accept"
+#    1 = "Hold"
+#    2 = "Reject"
+#    3 = "Discard"
 generic_nonmember_action = 1
 
-# Skal meddelelser fra ikke-medlemmer, hvis mail automatisk slettes,
-# videresendes til listemoderator?
+# Should messages from non-members, which are automatically discarded,
+# be forwarded to the list moderator?
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 forward_auto_discards = 1
 
+# Text to include in any rejection notice to be sent to non-members who
+# post to this list. This notice can include the list's owner address by
+# %(listowner)s and replaces the internally crafted default message.
+nonmember_rejection_notice = ''
+
 ## Privacy options
 #
-# Her kan du ops&aelig;tte filtrering baseret på modtageren af
-# meddelelsen.
+# This section allows you to configure various filters based on the
+# recipient of the message.
 
-# Meget (faktisk det meste) spam/junk mail har ikke de endelige
-# modtagere i modtagerfelterne. Faktisk indeholder felterne To: og/eller
-# Cc: oftest en helt ugyldig adresse. Begr&aelig;nsningen du
-# s&aelig;tter her har kun indvirkning p&aring; det som st&aring;r
-# f&oslash;r '@' tegnet i adressen, men filtret vil alligevel opfange og
-# blokere det meste spam/junk mail.
+# Many (in fact, most) spams do not explicitly name their myriad
+# destinations in the explicit destination addresses - in fact often the
+# To: field has a totally bogus address for obfuscation.  The constraint
+# applies only to the stuff in the address before the '@' sign, but
+# still catches all such spams.
+# 
+# The cost is that the list will not accept unhindered any postings
+# relayed from other addresses, unless
+# 
 # 
-# Prisen for dette er, at listen ikke uhindret vil kunne modtage e-mail
-# videresendt via andre e-mailadresser, med mindre
+# The relaying address has the same name, or
 # 
+# The relaying address name is included on the options that specifies
+# acceptable aliases for the list.
 # 
-# Adressen der videresendes fra hedder det samme, eller Adressen der
-# videresendes fra inkluderes i indstillingen som bestemmer gyldige
-# aliaser for listen.
 # 
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 require_explicit_destination = 1
 
-# Alternative e-mailadresser som godtages n&aring;r
-# 'require_explicit_destination' er sat til. Som v&aelig;rdi for denne
-# indstilling skal du angive regexp-udtryk ("regular expressions"), et
-# udtryk pr. linie, der sammenlignes med hver modtageradresse i
-# meddelelsen. Sammenligningen udf&oslash;res med Pythons re.match()
-# funktion, som betyder at de kun g&aelig;lder for begyndelsen af
-# strengen.
-# 
-# For bagudkompatibilitet med Mailman 1.1, hvis regexp-udtryk ikke
-# indeholder en '@', sammenlignes udtrykket kun med den f&oslash;rste
-# del (det som st&aring;r f&oslash;r '@') i modtageradressen. Hvis
-# sammenligningen ikke lykkes, eller hvis udtrykket ikke indholder en
-# '@', sammenlignes udtrykket med hele modtageradressen.
-# 
-# Sammenligning med kun den f&oslash;rste del af en modtageradresse
-# underst&oslash;ttes ikke l&aelig;ngere. I fremtidige versioner af
-# Mailman vil kun sammenligning med hele modtageradresser blive
-# underst&oslash;ttet.
+# Alternate addresses that are acceptable when
+# `require_explicit_destination' is enabled.  This option takes a list
+# of regular expressions, one per line, which is matched against every
+# recipient address in the message.  The matching is performed with
+# Python's re.match() function, meaning they are anchored to the start
+# of the string.
+# 
+# For backwards compatibility with Mailman 1.1, if the regexp does not
+# contain an `@', then the pattern is matched against just the local
+# part of the recipient address.  If that match fails, or if the pattern
+# does contain an `@', then the pattern is matched against the entire
+# recipient address.
+# 
+# Matching against the local part is deprecated; in a future release,
+# the pattern will always be matched against the entire recipient
+# address.
 acceptable_aliases = ''
 
-# Hvis en mail der er sendt til listen indeholder s&aring; mange som
-# eller flere modtagere end denne v&aelig;rdi, holdes mailen tilbage,
-# s&aring; listeadministrator eventuelt kan godkende den. Brug
-# v&aelig;rdien 0 for ingen begr&aelig;nsning.
+# If a posting has this number, or more, of recipients, it is held for
+# admin approval.  Use 0 for no ceiling.
 max_num_recipients = 10
 
 ## Privacy options
 #
-# Her kan du opsætte forskellige anti-spam filtre, som kan bidrage til
-# at reducere mængden af spam der distribueres via e-maillisten.
+# This section allows you to configure various anti-spam filters posting
+# filters, which can help reduce the amount of spam your list members
+# end up receiving.
+# 
 
 # Each header filter rule has two parts, a list of regular expressions,
 # one per line, and an action to take.  Mailman matches the message's
@@ -811,22 +807,23 @@ max_num_recipients = 10
 # You can have more than one filter rule for your list.  In that case,
 # each rule is matched in turn, with processing stopped after the first
 # match.
+# 
+# Note that headers are collected from all the attachments (except for
+# the mailman administrivia message) and matched against the regular
+# expressions. With this feature, you can effectively sort out messages
+# with dangerous file types or file name extensions.
 header_filter_rules = []
 
-# Brug denne indstilling til at bortfiltrere mail til listen, baseret
-# p&aring; indholdet af et eller flere felter i brevhovedet. Her skal du
-# skrive regexp-udtryk (regular expressions), et pr. linie, som
-# sammenlignes med det aktuelle felt. Sammenligningen skelner ikke
-# imellem store og sm&aring; bogstaver. Linier der begynder med '#'
-# sammenlignes ikke.
+# Use this option to prohibit posts according to specific header values.
+# The target value is a regular-expression for matching against the
+# specified header.  The match is done disregarding letter case.  Lines
+# beginning with '#' are ignored as comments.
 # 
-# For eksempel: udtrykket to: .*@public.com fort&aelig;ller at al mail
-# som indeholder '@public.com' i To: feltet, skal holdes tilbage for
-# godkendelse.
+# For example:to: .*@public.com  says to hold all postings with a To:
+# mail header containing '@public.com' anywhere among the addresses.
 # 
-# Bem&aelig;rk: tomme tegn i starten af regexp-udtrykket fjernes. Dette
-# kan omg&aring;s p&aring; flere m&aring;der, f.eks. ved at bruge
-# escape-tegn eller parenteser.
+# Note that leading whitespace is trimmed from the regexp.  This can be
+# circumvented in a number of ways, e.g. by escaping or bracketing it.
 bounce_matching_headers = """# Lines that *start* with a '#' are comments.
 to: friend@public.com
 message-id: relay.comanche.denmark.eu
@@ -835,415 +832,439 @@ from: .*@uplinkpro.com"""
 
 ## Bounce options
 #
-# Disse regler bestemmer hvordan automatisk behandling af returmails
-# skal foreg&aring;. Her er en oversigt over hvordan det virker.
-# 
-# <p>N&aring;r Mailman modtager en returmail, bliver to ting
-# fors&oslash;gt tolket. Den ene er e-mailadressen for medlemmet som
-# egentlig skulle modtage e-mailen, og den anden er &aring;rsagen til
-# problemet. &Aring;rsagen tolkes til at v&aelig;re <em>alvorlig</em>
-# eller <em>harml&oslash;s</em> alt efter om &aring;rsagen er af kritisk
-# eller af mindre alvorlig art. Hvis der er tvivl, tolkes &aring;rsagen
-# som alvorlig.
-# 
-# <p>Hvis ingen e-mailadresse kan hentes ud af meddelelsen, bliver den
-# normalt afvist. Ellers vil medlemmet som har e-mailadressen f&aring;
-# tildelt et <em>returtal</em>, og hver gang der kommer en
-# returmeddelelse vil tallet &oslash;ges. Alvorlige &aring;rsager
-# f&oslash;rer til at tallet &oslash;ges med 1, harml&oslash;se
-# &aring;rsager f&oslash;rer til at det &oslash;ges med 0.5. Dette sker
-# kun &eacute;n gang pr. dag, s&aring; selv om der kommer 10 alvorlige
-# returmails fra et medlem p&aring; &eacute;n dag, vil tallet kun
-# &oslash;ges med 1.
-# 
-# <p>N&aring;r returtallet for et medlem n&aring;r en vis <a
-# href="?VARHELP=bounce/bounce_score_threshold">gr&aelig;nse</a>,
-# stoppes levering til medlemmet. Dermed vil medlemmet ikke modtage
-# e-mail fra listen f&oslash;r levering s&aelig;ttes til igen. Medlemmet
-# vil med j&aelig;vne mellemrum modtage meddelelse om at dette er sket,
-# og hvad han/hun skal g&oslash;re for at f&aring; e-mail fra listen
-# igen.
-# 
-# <p>Du kan bestemme <a
-# href="?VARHELP=bounce/bounce_you_are_disabled_warnings">hvor mange
-# advarsler</a> medlemmet skal have og <a
-# href="?VARHELP=bounce/bounce_you_are_disabled_warnings_interval">hvor
-# ofte</a> han/hun skal modtage s&aring;danne advarsler.
-# 
-# <p>Der er en vigtig indstilling mere: efter en vis tid -- hvor ingen
-# returmeddelelser dukker op -- regnes returinformation for at
-# v&aelig;re <a
-# href="?VARHELP=bounce/bounce_info_stale_after">for&aelig;ldet</a> og
-# stoppes. Ved at justere denne v&aelig;rdi, og s&aelig;tte en
-# gr&aelig;nse for returantallet, kan du bestemme hvor lang tid der skal
-# g&aring; f&oslash;r levering til et medlem stoppes. Begge disse
-# v&aelig;rdier b&oslash;r tilpasses efter hvor ofte og hvor meget
-# e-mail der sendes til din liste.
-
-# Ved at sætte denne værdi til Nej, slår du al automatisk tolkning af
-# returmeddelelser for denne liste fra. Bemærk at hvis meddelelser
-# afvises vil listeadministratoren ikke blive forstyrret med dem.
-#
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# These policies control the automatic bounce processing system in
+# Mailman.  Here's an overview of how it works.
+# 
+# <p>When a bounce is received, Mailman tries to extract two pieces of
+# information from the message: the address of the member the message
+# was intended for, and the severity of the problem causing the bounce.
+# The severity can be either <em>hard</em> or <em>soft</em> meaning
+# either a fatal error occurred, or a transient error occurred.  When in
+# doubt, a hard severity is used.
+# 
+# <p>If no member address can be extracted from the bounce, then the
+# bounce is usually discarded.  Otherwise, each member is assigned a
+# <em>bounce score</em> and every time we encounter a bounce from this
+# member we increment the score.  Hard bounces increment by 1 while soft
+# bounces increment by 0.5.  We only increment the bounce score once per
+# day, so even if we receive ten hard bounces from a member per day,
+# their score will increase by only 1 for that day.
+# 
+# <p>When a member's bounce score is greater than the <a
+# href="?VARHELP=bounce/bounce_score_threshold">bounce score
+# threshold</a>, the subscription is disabled.  Once disabled, the
+# member will not receive any postings from the list until their
+# membership is explicitly re-enabled (either by the list administrator
+# or the user).  However, they will receive occasional reminders that
+# their membership has been disabled, and these reminders will include
+# information about how to re-enable their membership.
+# 
+# <p>You can control both the <a
+# href="?VARHELP=bounce/bounce_you_are_disabled_warnings">number of
+# reminders</a> the member will receive and the <a
+# href="?VARHELP=bounce/bounce_you_are_disabled_warnings_interval"
+# >frequency</a> with which these reminders are sent.
+# 
+# <p>There is one other important configuration variable; after a
+# certain period of time -- during which no bounces from the member are
+# received -- the bounce information is <a
+# href="?VARHELP=bounce/bounce_info_stale_after">considered stale</a>
+# and discarded.  Thus by adjusting this value, and the score threshold,
+# you can control how quickly bouncing members are disabled.  You should
+# tune both of these to the frequency and traffic volume of your list.
+
+# By setting this value to No, you disable all automatic bounce
+# processing for this list, however bounce messages will still be
+# discarded so that the list administrator isn't inundated with them.
+#
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 bounce_processing = 1
 
-# Hvert medlem tildeles et returtal, og hver gang der kommer en
-# returmeddelelse vil dette tal &oslash;ges.  Alvorlige (&aring;rsager
-# f&oslash;rer til at det &oslash;ges med 1, mens harml&oslash;se
-# &aring;rsager f&oslash;rer til at det &oslash;ges med 0.5. Dette sker
-# kun &eacute;n gang pr. dag, s&aring; selv om der kommer 10 alvorlige
-# returmails fra et medlem p&aring; &eacute;n dag, vil tallet kun
-# &oslash;ges med 1.
-# 
-# Her s&aelig;ttes den &oslash;vre gr&aelig;nse for medlemmets returtal
-# Overskrides denne gr&aelig;nse stoppes levering automatisk, men
-# medlemmet bliver ikke fjernet fra listen.
+# Each subscriber is assigned a bounce score, as a floating point
+# number.  Whenever Mailman receives a bounce from a list member, that
+# member's score is incremented.  Hard bounces (fatal errors) increase
+# the score by 1, while soft bounces (temporary errors) increase the
+# score by 0.5.  Only one bounce per day counts against a member's
+# score, so even if 10 bounces are received for a member on the same
+# day, their score will increase by just 1.
+# 
+# This variable describes the upper limit for a member's bounce score,
+# above which they are automatically disabled, but not removed from the
+# mailing list.
 bounce_score_threshold = 5.0
 
-# Antal dage f&oslash;r returinformation stoppes hvis der ikke dukker
-# flere returmails op. Dette tal skal v&aelig;re et heltal.
+# The number of days after which a member's bounce information is
+# discarded, if no new bounces have been received in the interim.  This
+# value must be an integer.
 bounce_info_stale_after = 7
 
-# Hvor mange Levering til dig er stoppet advarsler der skal sendes til
-# et medlem f&oslash;r medlemmet frameldes listen. S&aelig;t denne værdi
-# til 0 for at fjerne et medlem fra listen straks, hvis der kommer
-# returmails fra medlemmets e-mailadresse. Dette tal skal være et
-# heltal.
+# How many Your Membership Is Disabled warnings a disabled member should
+# get before their address is removed from the mailing list.  Set to 0
+# to immediately remove an address from the list once their bounce score
+# exceeds the threshold.  This value must be an integer.
 bounce_you_are_disabled_warnings = 3
 
-# Antal dage imellem hver gang en Levering til dig er stoppet advarsel
-# skal sendes ud. Dette tal skal være et heltal.
+# The number of days between sending the Your Membership Is Disabled
+# warnings.  This value must be an integer.
 bounce_you_are_disabled_warnings_interval = 7
 
-# Mailmans automatiske returmailh&aring;ndtering er meget robust, men
-# det er alligevel umuligt at genkende alle typer returmails der kommer.
-# Du b&oslash;r v&aelig;lge Ja her, af to grunde: 1) Hvis det virkelig
-# er en permanent returmail fra et medlem af listen, b&oslash;r du
-# antagelig manuelt afmelde medlemmet fra listen, og 2) du vil
-# m&aring;ske sende en meddelelse til udviklerne af Mailman s&aring;dan
-# at returmails automatisk genkendes af Mailman i senere versioner. Hvis
-# du ikke vil g&oslash;re nogen af delene, s&aelig;ttes denne
-# indstilling til Nej. S&aring; vil alle returmails afvises automatisk
-# uden videre behandling. Bem&aelig;rk: Denne indstilling vil ogs&aring;
-# indvirke p&aring; al e-mail der sendes til listens -admin adresse. Den
-# adresse er for&aelig;ldet og udg&aring;et, men måske vil nogen
-# alligevel fortsat sende e-mail til den. Hvis nogen g&oslash;r det, og
-# du har sat denne indstilling til Nej, vil disse mails ogs&aring; blive
-# afvist. M&aring;ske vil du ogs&aring; ops&aelig;tte et automatisk svar
-# p&aring; e-mail sendt til -owner og -admin adresserne.
-#
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# While Mailman's bounce detector is fairly robust, it's impossible to
+# detect every bounce format in the world.  You should keep this
+# variable set to Yes for two reasons: 1) If this really is a permanent
+# bounce from one of your members, you should probably manually remove
+# them from your list, and 2) you might want to send the message on to
+# the Mailman developers so that this new format can be added to its
+# known set.
+# 
+# If you really can't be bothered, then set this variable to No and all
+# non-detected bounces will be discarded without further processing.
+# 
+# Note: This setting will also affect all messages sent to your list's
+# -admin address.  This address is deprecated and should never be used,
+# but some people may still send mail to this address.  If this happens,
+# and this variable is set to No those messages too will get discarded.
+# You may want to set up an autoresponse message for email to the -owner
+# and -admin address.
+#
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 bounce_unrecognized_goes_to_list_owner = 1
 
-# Ved at sætte denne til Nej, fravælges beskeden der normalt sendes til
-# ejer(e) af listen, når levering af e-mail til et medlem stoppes på
-# grund af for mange returmails. Der vil til gengæld altid blive forsøgt
-# afsendt en e-mail med besked til medlemmet.
+# By setting this value to No, you turn off notification messages that
+# are normally sent to the list owners when a member's delivery is
+# disabled due to excessive bounces. An attempt to notify the member
+# will always be made.
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 bounce_notify_owner_on_disable = 1
 
-# Ved at sætte denne til Nej, fravælges beskeden der normalt sendes til
-# ejer(e) af listen, når et medlem frameldes listen på grund af for
-# mange returmails. Der vil til gengæld altid blive forsøgt afsendt en
-# e-mail med besked til medlemmet.
+# By setting this value to No, you turn off notification messages that
+# are normally sent to the list owners when a member is unsubscribed due
+# to excessive bounces.  An attempt to notify the member will always be
+# made.
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 bounce_notify_owner_on_removal = 1
 
 ## Archive options
 #
-# Regler for arkivering
+# List traffic archival policies.
 
-# Arkiver e-mail i et arkiv?
+# Archive messages?
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 archive = 1
 
-# Skal arkivet v&aelig;re offentligt eller privat?
+# Is archive file source for public or private archival?
 #
-# gyldige værdier:
-#    0 = "Offentligt"
-#    1 = "Privat"
+# legal values are:
+#    0 = "public"
+#    1 = "private"
 archive_private = 0
 
-# Hvor ofte skal arkivet deles op?
+# How often should a new archive volume be started?
 #
-# gyldige værdier:
-#    0 = "&Aring;rlig"
-#    1 = "M&aring;nedlig"
-#    2 = "Kvartalsvis"
-#    3 = "Ugentlig"
-#    4 = "Daglig"
+# legal values are:
+#    0 = "Yearly"
+#    1 = "Monthly"
+#    2 = "Quarterly"
+#    3 = "Weekly"
+#    4 = "Daily"
 archive_volume_frequency = 0
 
 ## Gateway options
 #
-# E-mail-Til-Nyhedsgruppe og Nyhedsgruppe-Til-E-mail tjeneste.
+# Mail-to-News and News-to-Mail gateway services.
 
-# Nyhedsgruppe-tjeneste er ikke en del af Mailman. Du skal have adgang
-# til en eksisterende NNTP tjeneste, og maskinen som denne mailliste
-# k&oslash;rer p&aring; skal have adgang til at hente og afsende
-# meddelelser til NNTP tjenesten.
+# This value may be either the name of your news server, or optionally
+# of the format name:port, where port is a port number.
+# 
+# The news server is not part of Mailman proper.  You have to already
+# have access to an NNTP server, and that NNTP server must recognize the
+# machine this mailing list runs on as a machine capable of reading and
+# posting news.
 nntp_host = ''
 
-# Navn p&aring; nyhedsgruppe der skal sendes til og/eller fra.
+# The name of the Usenet group to gateway to and/or from.
 linked_newsgroup = ''
 
-# Skal nye meddelelser til denne liste sendes til nyhedsgruppen?
+# Should new posts to the mailing list be sent to the newsgroup?
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 gateway_to_news = 0
 
-# Skal nye meddelelser til nyhedsgruppen sendes til denne mailliste?
+# Should new posts to the newsgroup be sent to the mailing list?
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 gateway_to_mail = 0
 
-# Denne indstilling fort&aelig;ller Mailman hvilken slags
-# moderationsregler nyhedsgruppen har og hvordan de koordineres med
-# maillistens moderationsregler. Dette g&aelig;lder kun nyhedgrupper du
-# overfører meddelelser til, s&aring; hvis du kun overf&oslash;rer fra
-# en nyhedsgruppe, eller nyhedsgruppen du overf&oslash;rer til ikke er
-# modereret, s&aelig;ttes indstillingen til Ingen.
-# 
-# Hvis nyhedsgruppen er modereret, kan du s&aelig;tte maillisten til at
-# v&aelig;re moderationsadressen for nyhedsgruppen. Ved at vælge
-# Modereret, vil en ekstra meddelelse holdes tilbage i
-# godkendelsesprocessen. Al mail sendt til maillisten skal godkendes
-# f&oslash;r den sendes til nyhedsgruppen, eller til medlemmerne af
-# listen.
-# 
-# Vær opm&aelig;rksom p&aring; at hvis brevhovedet i mailen har et
-# Approved: felt med listens administrative adgangskode, vil denne regel
-# ikke blive benyttet. På den m&aring;de kan priviligerede afsendere
-# sende mail direkte til listen og nyhedsgruppen.
-# 
-# Hvis nyhedsgruppen er modereret, men du alligevel vil have en
-# &aring;ben liste, b&oslash;r du vælge Åben liste, modereret
-# nyhedsgruppe. S&aring; vil de s&aelig;dvanlige mekanismer for
-# moderation blive benyttet i Mailman, men alle meddelelser der sendes
-# til Usenet vil f&aring; et Approved felt i brevhovedet.
-#
-# gyldige værdier:
-#    0 = "Ingen"
-#    1 = "Åben liste, modereret nyhedsgruppe"
-#    2 = "Modereret"
+# This setting determines the moderation policy of the newsgroup and its
+# interaction with the moderation policy of the mailing list.  This only
+# applies to the newsgroup that you are gatewaying to, so if you are
+# only gatewaying from Usenet, or the newsgroup you are gatewaying to is
+# not moderated, set this option to None.
+# 
+# If the newsgroup is moderated, you can set this mailing list up to be
+# the moderation address for the newsgroup.  By selecting Moderated, an
+# additional posting hold will be placed in the approval process.  All
+# messages posted to the mailing list will have to be approved before
+# being sent on to the newsgroup, or to the mailing list membership.
+# 
+# Note that if the message has an Approved header with the list's
+# administrative password in it, this hold test will be bypassed,
+# allowing privileged posters to send messages directly to the list and
+# the newsgroup.
+# 
+# Finally, if the newsgroup is moderated, but you want to have an open
+# posting policy anyway, you should select Open list, moderated group.
+# The effect of this is to use the normal Mailman moderation facilities,
+# but to add an Approved header to all messages that are gatewayed to
+# Usenet.
+#
+# legal values are:
+#    0 = "None"
+#    1 = "Open list, moderated group"
+#    2 = "Moderated"
 news_moderation = 0
 
-# Mailman tilføjer normalt en tekst du selv kan tilrette (emne prefix)
-# foran emnefeltet i mail som sendes til listen, og normalt sker dette
-# også for mail som sendes videre til Usenet. Du kan sætte denne
-# indstilling til Nej hvis du ikke ønsker emne prefix tilføjet til mail
-# som sendes til Usenet. Sættes emne prefix for listen til off, vil
-# videresendte meddelelser heller ikke få prefix tilføjet.
+# Mailman prefixes Subject: headers with text you can customize and
+# normally, this prefix shows up in messages gatewayed to Usenet.  You
+# can set this option to No to disable the prefix on gated messages.  Of
+# course, if you turn off normal Subject: prefixes, they won't be
+# prefixed for gated messages either.
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 news_prefix_subject_too = 1
 
 ## Autoreply options
 #
-# Indstillinger for automatiske svar.<p>
+# Auto-responder characteristics.<p>
 # 
-# I tekstboksene nedenfor kan du bruge følgende variabler: (skriv:
-# %(&lt;variabelnavn&gt;)s ) for at indsætte ønsket information: <p><ul>
-# <li><b>listname</b> - <em>navnet p&aring; listen</em>
-# <li><b>listurl</b> - <em>URL til listens webside</em>
-# <li><b>requestemail</b> - <em>listens -request e-mailadresse</em>
-# <li><b>owneremail</b> - <em>listens -owner e-mailadresse</em> </ul>
+# In the text fields below, string interpolation is performed with the
+# following key/value substitutions: <p><ul> <li><b>listname</b> -
+# <em>gets the name of the mailing list</em> <li><b>listurl</b> -
+# <em>gets the list's listinfo URL</em> <li><b>requestemail</b> -
+# <em>gets the list's -request address</em> <li><b>owneremail</b> -
+# <em>gets the list's -owner address</em> </ul>
 # 
-# <p>Du kan enten skrive teksten direkte i tekstboksene, eller du kan
-# angive navnet p&aring; en fil som indeholder teksten. Denne fil vil
-# s&aring; blive indl&aelig;st i tekstboksen, fra dit lokale filsystem.
+# <p>For each text field, you can either enter the text directly into
+# the text box, or you can specify a file on your local system to upload
+# as the text.
 
-# Skal Mailman sende et automatisk svar til dem der sender e-mail til
-# listen?
+# Should Mailman send an auto-response to mailing list posters?
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 autorespond_postings = 0
 
-# Automatisk svar der skal sendes.
+# Auto-response text to send to mailing list posters.
 autoresponse_postings_text = ''
 
-# Skal Mailman sende et automatisk svar p&aring; e-mail der sendes til
-# -owner adressen?
+# Should Mailman send an auto-response to emails sent to the -owner
+# address?
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 autorespond_admin = 0
 
-# Automatisk svar p&aring; e-mail til -owner adressen.
+# Auto-response text to send to -owner emails.
 autoresponse_admin_text = ''
 
-# Skal Mailman sende et automatisk svar p&aring; e-mail der sendes til
-# -request adressen? Hvis du v&aelig;lger ja, kan du ogs&aring;
-# v&aelig;lge om e-mailen der blev sendt til -request adressen skal
-# medtages i det automatiske svar.
+# Should Mailman send an auto-response to emails sent to the -request
+# address?  If you choose yes, decide whether you want Mailman to
+# discard the original email, or forward it on to the system as a normal
+# mail command.
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja, men uden den originale e-mail"
-#    2 = "Ja, og medtag den originale e-mail"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes, w/discard"
+#    2 = "Yes, w/forward"
 autorespond_requests = 0
 
-# Automatisk svar p&aring; e-mail til -request adressen.
+# Auto-response text to send to -request emails.
 autoresponse_request_text = ''
 
-# Antal dage imellem automatisk svar p&aring; e-mail, fra samme
-# afsender, til listen eller til -request/-owner adresserne. S&aelig;t
-# denne v&aelig;rdi til 0 (eller et negativt tal) for at sende
-# automatisk svar hver gang.
+# Number of days between auto-responses to either the mailing list or
+# -request/-owner address from the same poster.  Set to zero (or
+# negative) for no grace period (i.e. auto-respond to every message).
 autoresponse_graceperiod = 90
 
 ## Contentfilter options
 #
-# Regler for indhold i e-mail sendt til listen.
-# 
-# <p>Filtrering af indhold fungerer således: når listen modtager en
-# e-mail og du har beskyttelse med filtrering af indhold aktiveret,
-# sammenlignes først eventuelle vedh&aelig;ftninger med <a
-# href="?VARHELP=contentfilter/filter_mime_types">MIME filtrene</a>.
-# Hvis en vedh&aelig;ftning passer med et af disse filtre, bliver
-# vedh&aelig;ftningen fjernet.
-# 
-# <p>Derefter sammenlignes eventuelle vedh&aelig;ftninger med <a
-# href="?VARHELP=contentfilter/pass_mime_types">gyldige MIME typer</a>,
-# hvis nogen er defineret. Alle vedh&aelig;ftninger som ikke stemmer
-# overens med de angivne MIME typer, bliver fjernet.
-# 
-# <p>Efter filtreringen vil alle tomme <tt>multipart</tt>
-# vedh&aelig;ftninger v&aelig;re fjernet. Hvis selve meddelelsen er helt
-# tom efter denne filtrering, vil meddelelsen blive afvist. Derefter vil
-# enhver <tt>multipart/alternative</tt> vedh&aelig;ftning blive
-# erstattet af den første alternative som ikke er tom.
-# 
-# <p>Til sidst vil alle <tt>text/html</tt> vedh&aelig;ftninger som måtte
-# v&aelig;re tilbage i meddelelsen blive konverteret til
-# <tt>text/plain</tt> hvis <a
-# href="?VARHELP=contentfilter/convert_html_to_plaintext">konverter til
-# ren tekst</a> er sat til og serveren er konfigureret til at tillade
-# sådanne konverteringer.
-
-# Skal Mailman filtrere indhold i e-mail sendt til listen som angivet
-# nedenfor?
-#
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# Policies concerning the content of list traffic.
+# 
+# <p>Content filtering works like this: when a message is received by
+# the list and you have enabled content filtering, the individual
+# attachments are first compared to the <a
+# href="?VARHELP=contentfilter/filter_mime_types">filter types</a>.  If
+# the attachment type matches an entry in the filter types, it is
+# discarded.
+# 
+# <p>Then, if there are <a
+# href="?VARHELP=contentfilter/pass_mime_types">pass types</a> defined,
+# any attachment type that does <em>not</em> match a pass type is also
+# discarded.  If there are no pass types defined, this check is skipped.
+# 
+# <p>After this initial filtering, any <tt>multipart</tt> attachments
+# that are empty are removed.  If the outer message is left empty after
+# this filtering, then the whole message is discarded.
+# 
+# <p> Then, each <tt>multipart/alternative</tt> section will be replaced
+# by just the first alternative that is non-empty after filtering if <a
+# href="?VARHELP=contentfilter/collapse_alternatives"
+# >collapse_alternatives</a> is enabled.
+# 
+# <p>Finally, any <tt>text/html</tt> parts that are left in the message
+# may be converted to <tt>text/plain</tt> if <a
+# href="?VARHELP=contentfilter/convert_html_to_plaintext"
+# >convert_html_to_plaintext</a> is enabled and the site is configured
+# to allow these conversions.
+
+# Should Mailman filter the content of list traffic according to the
+# settings below?
+#
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 filter_content = 0
 
-# Brug denne indstilling til at fjerne vedh&aelig;ftninger der passer
-# til MIME typer. Hver linie skal her indeholde navnet på en MIME
-# type/subtype, f.eks. image/gif. Hvis du ønsker at fjerne alle
-# vedh&aelig;ftninger som har en given hoved MIME type, kan du undlade
-# at angive subtype, f.eks. image.
+# Use this option to remove each message attachment that matches one of
+# these content types.  Each line should contain a string naming a MIME
+# type/subtype, e.g. image/gif.  Leave off the subtype to remove all
+# parts with a matching major content type, e.g. image.
 # 
-# Tomme linier medtages ikke.
+# Blank lines are ignored.
 # 
-# Se også gyldige MIME typer for whitelist af MIME typer.
+# See also <a href="?VARHELP=contentfilter/pass_mime_types"
+# >pass_mime_types for a content type whitelist.
 filter_mime_types = ''
 
-# Brug denne indstilling for at definere hvilke MIME typer der skal være
-# tilladt. Krav og format for filtrering er identisk med MIME filtre.
+# Use this option to remove each message attachment that does not have a
+# matching content type.  Requirements and formats are exactly like <a
+# href="?VARHELP=contentfilter/filter_mime_types" >filter_mime_types.
 # 
-# Bem&aelig;rk: hvis du lægger noget ind her, men ikke angiver
-# multipart, vil ingen e-mail med vedh&aelig;ftninger blive medtaget.
+# Note: if you add entries to this list but don't add multipart to this
+# list, any messages with attachments will be rejected by the pass
+# filter.
 pass_mime_types = """multipart/mixed
 multipart/alternative
 text/plain"""
 
-# Skal Mailman konvertere text/html dele til ren tekst? Denne
-# konvertering vil finde sted efter at MIME filteret har fjernet de
-# uønskede dele.
+# Remove message attachments that have a matching filename extension.
+filter_filename_extensions = """exe
+bat
+cmd
+com
+pif
+scr
+vbs
+cpl"""
+
+# Remove message attachments that don't have a matching filename
+# extension.  Leave this field blank to skip this filter test.
+pass_filename_extensions = ''
+
+# Should Mailman collapse multipart/alternative to its first part
+# content?
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
+collapse_alternatives = True
+
+# Should Mailman convert text/html parts to plain text?  This conversion
+# happens after MIME attachments have been stripped.
+#
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 convert_html_to_plaintext = 1
 
-# Her bestemmer du hvad der skal ske, når en meddelelse filtreres fra af
-# et filter, altså hvis vedh&aelig;ftningen filtreres fra af MIME
-# filteret, eller en vedh&aelig;ftning ikke har en af de gyldige MIME
-# typer, eller meddelelsen ender med at være tom efter filtrering.
-# 
-# Bemærk at det du vælger her ikke vil ske hvis en meddelelse stadig
-# indeholder noget efter filtrering. Så vil meddelelsen altid blive
-# sendt videre til listen.
-# 
-# Når meddelelsen afvises, skrives Message-ID for den afviste meddelelse
-# til loggen. Når meddelelsen sendes retur eller videresendes til
-# listens ejer, vil en begrundelse altid blive inkluderet i den
-# returmail der sendes til afsenderen. Når meddelelserne skal bevares,
-# gemmes de i et specielt køkatalog på disken, sådan at
-# serveradministrator kan se (og måske gøre noget med) dem, men bliver
-# ellers fjernet. Dette sidste valg er kun tilgængeligt hvis
-# serveradministrator har tilladt det.
-#
-# gyldige værdier:
-#    0 = "Slet"
-#    1 = "Afvis"
-#    2 = "Videresend til Listens Ejer"
-#    3 = "Bevar"
+# One of these actions is taken when the message matches one of the
+# content filtering rules, meaning, the top-level content type matches
+# one of the <a href="?VARHELP=contentfilter/filter_mime_types"
+# >filter_mime_types, or the top-level content type does not match one
+# of the <a href="?VARHELP=contentfilter/pass_mime_types"
+# >pass_mime_types, or if after filtering the subparts of the message,
+# the message ends up empty.
+# 
+# Note this action is not taken if after filtering the message still
+# contains content.  In that case the message is always forwarded on to
+# the list membership.
+# 
+# When messages are discarded, a log entry is written containing the
+# Message-ID of the discarded message.  When messages are rejected or
+# forwarded to the list owner, a reason for the rejection is included in
+# the bounce message to the original author.  When messages are
+# preserved, they are saved in a special queue directory on disk for the
+# site administrator to view (and possibly rescue) but otherwise
+# discarded.  This last option is only available if enabled by the site
+# administrator.
+#
+# legal values are:
+#    0 = "Discard"
+#    1 = "Reject"
+#    2 = "Forward to List Owner"
+#    3 = "Preserve"
 filter_action = 0
 
 ## Topics options
 #
-# Emneord for listen
-
-# Emnefilteret kategoriserer hver e-mail som kommer til listen, efter de
-# regexp-udtryk du skriver nedenfor. Hvis felterne Subject: eller
-# Keywords: i brevhovedet i en mail stemmer overens med et af disse
-# udtryk, bliver mailen placeret under det p&aring;g&aelig;ldende emne.
-# Hvert medlem af listen kan vælge kun at modtage mail der passer til de
-# &oslash;nskede emner. E-mail som ikke h&oslash;rer under noget emne,
-# bliver ikke leveret.
-# 
-# Bem&aeligrk: Dette fungerer kun i normal-modus, ikke i
-# sammendrag-modus.
-# 
-# Indholdet i meddelelsen kan ogs&aring; unders&oslash;ges for Subject:
-# og Keyword: felter, alt efter hvad indstillingen
-# topics_bodylines_limit er sat til.
+# List topic keywords
+
+# The topic filter categorizes each incoming email message according to
+# <a href="http://www.python.org/doc/current/lib/module-re.html">regular
+# expression filters you specify below.  If the message's Subject: or
+# Keywords: header contains a match against a topic filter, the message
+# is logically placed into a topic bucket.  Each user can then choose to
+# only receive messages from the mailing list for a particular topic
+# bucket (or buckets).  Any message not categorized in a topic bucket
+# registered with the user is not delivered to the list.
+# 
+# Note that this feature only works with regular delivery, not digest
+# delivery.
+# 
+# The body of the message can also be optionally scanned for Subject:
+# and Keywords: headers, as specified by the <a
+# href="?VARHELP=topics/topics_bodylines_limit">topics_bodylines_limit
+# configuration variable.
 #
-# gyldige værdier:
-#    0 = "Ikke tilgængeligt"
-#    1 = "Tilgængeligt"
+# legal values are:
+#    0 = "Disabled"
+#    1 = "Enabled"
 topics_enabled = 0
 
-# Her angiver du hvor mange linier af mailens indhold emnefilteret skal
-# gennems&oslash;ge. En s&oslash;gning stopper n&aring;r det antal
-# linier er gennems&oslash;gt, eller n&aring;r den m&oslash;der en linie
-# som ikke ligner et brevhoved-felt. S&aelig;ttes denne v&aelig;rdi til
-# nul (0), vil ingen linier i indholdet blive unders&oslash;gt (dvs. kun
-# Keywords: og Subject: i brevhovedet unders&oslash;ges). S&aelig;ttes
-# denne v&aelig;rdi til et negativt tal, vil alle linier blive
-# unders&oslash;gt frem til den f&oslash;rste linie som ikke ligner et
-# brevhoved-felt.
+# The topic matcher will scan this many lines of the message body
+# looking for topic keyword matches.  Body scanning stops when either
+# this many lines have been looked at, or a non-header-like body line is
+# encountered.  By setting this value to zero, no body lines will be
+# scanned (i.e. only the Keywords: and Subject: headers will be
+# scanned).  By setting this value to a negative number, then all body
+# lines will be scanned until a non-header-like line is encountered.
+# 
 topics_bodylines_limit = 5
 
-# Hvert emneord er faktisk et regexp-udtryk, der sammenlignes med dele
-# af mailen, nemlig felterne Keywords: og Subject: i brevhovedet.
-# Bem&aelig;rk at de f&oslash;rste linier i mailens indhold ogs&aring;
-# kan best&aring; af s&aring;danne "felter", og de kan dermed ogs&aring;
-# blive unders&oslash;gt.
+# Each topic keyword is actually a regular expression, which is matched
+# against certain parts of a mail message, specifically the Keywords:
+# and Subject: message headers. Note that the first few lines of the
+# body of the message can also contain a Keywords: and Subject: "header"
+# on which matching is also performed.
 topics = []
 
diff --git a/mailman/mailman.py b/mailman/mailman.py
index 8fb26d5..b6c18f8 100644
--- a/mailman/mailman.py
+++ b/mailman/mailman.py
@@ -1,382 +1,369 @@
-## Indstillinger for maillisten "mailman"  -*- python -*-
-## Dato: Sun Dec 11 16:36:00 2005
+# -*- python -*-
+# -*- coding: us-ascii -*-
+## "mailman" mailing list configuration settings
+## captured on Tue Mar 20 08:52:22 2007
 
 ## General options
 #
-# Grundlæggende egenskaber for listen, herunder en beskrivelse af
-# listen. 
-
-# Du kan f.eks. stave navnet med stort forbogstav eller ændre andre
-# bogstaver til store, s&aring; navnet bliver udtalt rigtigt eller at
-# forkortelser fremhæves. Bemærk at dette navn bruges i e-maillistens
-# adresse (f.eks. i bekræftelser ved tilmeldinger), s&aring; navnet kan
-# ikke ændres p&aring; nogen anden m&aring;de. (e-mailadresser er ikke
-# f&oslash;lsomme for store eller sm&aring; bogstaver, men de er
-# f&oslash;lsomme for n&aelig;sten alt andet :-)
+# Fundamental list characteristics, including descriptive info and basic
+# behaviors.
+
+# The capitalization of this name can be changed to make it presentable
+# in polite company as a proper noun, or to make an acronym part all
+# upper case, etc.  However, the name will be advertised as the email
+# address (e.g., in subscribe confirmation notices), so it should not be
+# otherwise altered.  (Email addresses are not case sensitive, but they
+# are sensitive to almost everything else :-)
 real_name = 'Mailman'
 
-# Der er to roller forbundet med hver mailliste. Listeadministratorerne
-# er dem der som sidste instans har kontrol over alle indstillingerne
-# for maillisten. De kan &aelig;ndre alle indstillinger der er
-# tilg&aelig;ngelige via disse administrative websider.
-# 
-# Listemoderatorerne har begrænset adgang; de kan ikke ændre
-# indstillinger for e-maillisten, men de kan tage sig af anmodninger i
-# forbindelse med listen, f.eks. anmodning om medlemskab, eller
-# godkende/afvise meddelelser der skal godkendes for at kunne udsendes
-# til listen. Listeadministratorerne kan ogs&aring; udf&oslash;re disse
-# opgaver.
-# 
-# For at aktivere muligheden for at have listemoderatorer, og p&aring;
-# den m&aring;de fordele arbejdsopgaverne i forbindelse med listen, skal
-# du anf&oslash;re din egen moderatoradgangskode, og angive
-# e-mailadresser for den/dem som skal v&aelig;re listemoderator(er).
-# Bemærk at i tekstboksene nedenfor skal du skrive e-mailadresser for
-# listeadministratorer.
+# There are two ownership roles associated with each mailing list.  The
+# list administrators are the people who have ultimate control over all
+# parameters of this mailing list.  They are able to change any list
+# configuration variable available through these administration web
+# pages.
+# 
+# The list moderators have more limited permissions; they are not able
+# to change any list configuration variable, but they are allowed to
+# tend to pending administration requests, including approving or
+# rejecting held subscription requests, and disposing of held postings.
+# Of course, the list administrators can also tend to pending requests.
+# 
+# In order to split the list ownership duties into administrators and
+# moderators, you must set a separate moderator password, and also
+# provide the email addresses of the list moderators.  Note that the
+# field you are changing here specifies the list administrators.
 owner = ['postmaster@jones.dk']
 
-# Der er to ejer-roller forbundet med hver mailliste.
-# Listeadministratorerne er dem der har den endelige kontrol over alle
-# indstillingerne for e-mallisten. De kan &aelig;ndre alle indstillinger
-# der er tilgængelige via disse administrative websider.
-# 
-# Listemoderatorerne har begr&aelig;nset adgang; de kan ikke &aelig;ndre
-# indstillinger for e-maillisten, men de kan tage sig af anmodninger
-# ang&aring;ende listen, f.eks. anmodning om medlemskab, eller
-# godkende/afvise meddelelser der skal godkendes for at kunne udsendes
-# p&aring; listen. Listeadministratorerne kan selvsagt ogs&aring;
-# udf&oslash;re disse opgaver.
-# 
-# For at aktivere muligheden for at have listemoderatorer, og p&aring;
-# den m&aring;de fordele arbejdsopgaverne i forbindelse med listen, skal
-# du anf&oslash;re din egen moderatoradgangskode, og indtaste
-# e-mailadresser for den/dem der skal v&aelig;re listemoderatore(r).
-# Bemærk, at i tekstboksene nedenfor skal du skrive listemoderator
-# e-mailadresse(r).
+# There are two ownership roles associated with each mailing list.  The
+# list administrators are the people who have ultimate control over all
+# parameters of this mailing list.  They are able to change any list
+# configuration variable available through these administration web
+# pages.
+# 
+# The list moderators have more limited permissions; they are not able
+# to change any list configuration variable, but they are allowed to
+# tend to pending administration requests, including approving or
+# rejecting held subscription requests, and disposing of held postings.
+# Of course, the list administrators can also tend to pending requests.
+# 
+# In order to split the list ownership duties into administrators and
+# moderators, you must set a separate moderator password, and also
+# provide the email addresses of the list moderators in this section.
+# Note that the field you are changing here specifies the list
+# moderators.
 moderator = []
 
-# Denne beskrivelse benyttes n&aring;r denne malliste listes op sammen
-# med andre maillister, i toptekster, osv. Den b&oslash;r v&aelig;re
-# s&aring; kort som overhovedet mulig, uden at det bliver uklart hvad
-# meningen med maillisten er eller hvad den skal bruges til.
+# This description is used when the mailing list is listed with other
+# mailing lists, or in headers, and so forth.  It should be as succinct
+# as you can get it, while still identifying what the list is.
 description = ''
 
-# Teksten tolkes som html bortset fra linieskift, der vil blive
-# &aelig;ndret til html-tag'et '<br>', sådan at du kan benytte links,
-# forh&aring;ndsformateret tekst, osv. Men brug alts&aring; kun
-# linieskift der hvor du vil have et nyt afsnit. V&aelig;r meget
-# omhyggelig, hvis du benytter html-kode. Fejl (f.eks. manglende
-# slut-tag's) kan f&oslash;re til at listens informationsside ikke
-# bliver vist s&aring;dan som den skal.
+# The text will be treated as html except that newlines will be
+# translated to <br> - so you can use links, preformatted text, etc, but
+# don't put in carriage returns except where you mean to separate
+# paragraphs.  And review your changes - bad html (like some
+# unterminated HTML constructs) can prevent display of the entire
+# listinfo page.
 info = ''
 
 # This text will be prepended to subject lines of messages posted to the
-# list, to distinguish mailing list messages in in mailbox summaries.
+# list, to distinguish mailing list messages in mailbox summaries.
 # Brevity is premium here, it's ok to shorten long mailing list names to
 # something more concise, as long as it still identifies the mailing
-# list.
+# list. You can also add a sequential number by %d substitution
+# directive. eg.; [listname %d] -> [listname 123] (listname %05d) ->
+# (listname 00123)
+# 
 subject_prefix = '[Mailman] '
 
-# Skjul afsenderen af meddelelser, ved at erstatte den med e-maillistens
-# adresse (Dette medfører at alle From:, Sender, og Reply-To: felter
-# fjernes)
+# Hide the sender of a message, replacing it with the list address
+# (Removes From, Sender and Reply-To fields)
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 anonymous_list = 0
 
-# Skal eksisterende Reply-To: felt i brevhovedet fjernes? Hvis ja, vil
-# dette blive gjort uanset om Mailman tilføjer et Reply-To: felt eller
-# ikke.
+# Should any existing Reply-To: header found in the original message be
+# stripped?  If so, this will be done regardless of whether an explict
+# Reply-To: header is added by Mailman or not.
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 first_strip_reply_to = 0
 
-# Denne indstillling fort&aelig;ller hvad Mailman skal g&oslash;re med
-# Reply-To: feltet i brevhovedet p&aring; e-mail der sendes til listen.
-# Hvis den er sat til Afsender, vil Mailman ikke tilf&oslash;je noget
-# Reply-To: felt, men findes et s&aring;dant felt allerede, vil det ikke
-# blive fjernet. S&aelig;ttes indstillingen til enten e-maillistens
-# adresse eller Egendefineret adresse, vil Mailman tilf&oslash;je, evt.
-# erstatte, et Reply-To: felt. (Egendefineret adresse inds&aelig;tter
-# v&aelig;rdien af indstillingen reply_to_address).
-# 
-# Der er flere grunde til ikke at indf&oslash;re eller erstatte
-# Reply-To: felter. En grund kan v&aelig;re at nogen af dem der sender
-# mail til listen er afh&aelig;ngige af selv at kunne s&aelig;tte
-# Reply-To: adressen. En anden grund er at modifikation af Reply-To:
-# adressen g&oslash;r det vanskeligere kun at sende svar til afsender.
-# Se 'Reply-To' Munging Considered Harmful for en diskussion omkring
-# emnet. Se Reply-To Munging Considered Useful for modsatte meninger.
-# 
-# Nogle maillister har begr&aelig;nset adgang, med en parallel liste
-# beregnet til diskussioner. Eksempler p&aring; dette er 'patches' eller
-# 'checkin' lister, som system for revisionskontrol sender
-# &aelig;ndringer i programmet til, men diskussioner omkring udvikling
-# af programmet sendes til udviklernes egen mailliste. For at
-# underst&oslash;tte lignende e-maillister, v&aelig;lg Egendefineret
-# adresse og s&aelig;t Reply-To: adressen i indstillingen
-# reply_to_address til at pege på den parallelle diskussionsliste.
-#
-# gyldige værdier:
-#    0 = "Afsender"
-#    1 = "mail listens adresse"
-#    2 = "Egendefineret adresse"
+# This option controls what Mailman does to the Reply-To: header in
+# messages flowing through this mailing list.  When set to Poster, no
+# Reply-To: header is added by Mailman, although if one is present in
+# the original message, it is not stripped.  Setting this value to
+# either This list or Explicit address causes Mailman to insert a
+# specific Reply-To: header in all messages, overriding the header in
+# the original message if necessary (Explicit address inserts the value
+# of <a href="?VARHELP=general/reply_to_address">reply_to_address).
+# 
+# There are many reasons not to introduce or override the Reply-To:
+# header.  One is that some posters depend on their own Reply-To:
+# settings to convey their valid return address.  Another is that
+# modifying Reply-To: makes it much more difficult to send private
+# replies.  See <a
+# href="http://www.unicom.com/pw/reply-to-harmful.html">`Reply-To'
+# Munging Considered Harmful for a general discussion of this issue.
+# See <a
+# href="http://www.metasystema.net/essays/reply-to.mhtml">Reply-To
+# Munging Considered Useful for a dissenting opinion.
+# 
+# Some mailing lists have restricted posting privileges, with a parallel
+# list devoted to discussions.  Examples are `patches' or `checkin'
+# lists, where software changes are posted by a revision control system,
+# but discussion about the changes occurs on a developers mailing list.
+# To support these types of mailing lists, select Explicit address and
+# set the Reply-To: address below to point to the parallel list.
+#
+# legal values are:
+#    0 = "Poster"
+#    1 = "This list"
+#    2 = "Explicit address"
 reply_goes_to_list = 0
 
-# Her definerer du adressen der skal s&aelig;ttes i Reply-To: feltet
-# n&aring;r indstillingen reply_goes_to_list er sat til Egendefineret
-# adresse.
-# 
-# Der findes mange grunde til at ikke indf&oslash;re eller erstatte
-# Reply-To: felter. En grund kan v&aelig;re at nogen af dem der sender
-# e-mail til listen er afh&aelig;ngige af selv at kunne s&aelig;tte
-# Reply-To: adressen. En anden grund er at modificering af Reply-To:
-# adressen g&oslash;r det vanskeligere at sende svar kun til afsender.
-# Se 'Reply-To' Munging Considered Harmful for en diskussion omkring
-# temaet. Se Reply-To Munging Considered Useful for modsatte meninger.
-# 
-# Nogle maillister har begr&aelig;nset adgang, med en egen parallel
-# liste beregnet for diskussioner. Eksempler p&aring; dette er 'patches'
-# eller 'checkin' lister, som system for revisionskontrol sender
-# &aelig;ndringer i programmet til, mens diskussioner omkring udvikling
-# af programmet sendes til udviklernes egen mailliste. For at
-# underst&oslash;tte s&aring;danne maillister, kan du definere Reply-To:
-# adressen her, og vælge Egendefineret adresse i indstillingen
-# reply_goes_to_list.
-# 
-# Bem&aelig;rk at hvis den oprindelige meddelelse indeholder et
-# Reply-To: felt, vil det ikke &aelig;ndres.
+# This is the address set in the Reply-To: header when the <a
+# href="?VARHELP=general/reply_goes_to_list">reply_goes_to_list option
+# is set to Explicit address.
+# 
+# There are many reasons not to introduce or override the Reply-To:
+# header.  One is that some posters depend on their own Reply-To:
+# settings to convey their valid return address.  Another is that
+# modifying Reply-To: makes it much more difficult to send private
+# replies.  See <a
+# href="http://www.unicom.com/pw/reply-to-harmful.html">`Reply-To'
+# Munging Considered Harmful for a general discussion of this issue.
+# See <a
+# href="http://www.metasystema.net/essays/reply-to.mhtml">Reply-To
+# Munging Considered Useful for a dissenting opinion.
+# 
+# Some mailing lists have restricted posting privileges, with a parallel
+# list devoted to discussions.  Examples are `patches' or `checkin'
+# lists, where software changes are posted by a revision control system,
+# but discussion about the changes occurs on a developers mailing list.
+# To support these types of mailing lists, specify the explicit
+# Reply-To: address here.  You must also specify Explicit address in the
+# reply_goes_to_list variable.
+# 
+# Note that if the original message contains a Reply-To: header, it will
+# not be changed.
 reply_to_address = ''
 
-# V&aelig;lg kun 'ja' her, hvis listen skal bruges som  "paraply" for
-# andre lister. Hvis 'ja' er valgt, vil bekr&aelig;ftelser og
-# meddelelser med adgangskode blive sendt til en adresse som konstrueres
-# ud fra medlemmets e-mailadresse - v&aelig;rdien af indstillingen
-# "umbrella_member_suffix" tilf&oslash;jes medlemmets kontonavn (det som
-# st&aring;r f&oslash;r @-tegnet).
+# Set this to yes when this list is intended to cascade only to other
+# mailing lists.  When set, meta notices like confirmations and password
+# reminders will be directed to an address derived from the member's
+# address - it will have the value of "umbrella_member_suffix" appended
+# to the member's account name.
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 umbrella_list = 0
 
-# N&aring;r "umbrella_list" indikerer at denne liste har andre
-# maillister som medlemmer, skal administrative meddelelser som f.eks.
-# bekr&aelig;ftelser og p&aring;mindelser om adgangskode ikke sendes til
-# selve listen, men snarere til administrator for listen. V&aelig;rdien
-# af denne indstilling bestemmer, hvilken adresse administrative
-# meddelelser skal sendes til. '-owner' er et almindeligt valg for denne
-# indstilling. Denne indstilling har ingen effekt n&aring;r
-# "umbrella_list" er sat til "Nej".
+# When "umbrella_list" is set to indicate that this list has other
+# mailing lists as members, then administrative notices like
+# confirmations and password reminders need to not be sent to the member
+# list addresses, but rather to the owner of those member lists.  In
+# that case, the value of this setting is appended to the member's
+# account name for such notices.  `-owner' is the typical choice.  This
+# setting has no effect when "umbrella_list" is "No".
 umbrella_member_suffix = '-owner'
 
-# Aktiver denne, hvis der skal sendes en p&aring;mindelse om adgangskode
-# til medlemmerne en gang hver m&aring;ned. Husk at medlemmerne
-# ogs&aring; selv kan frav&aelig;lge dette.
+# Turn this on if you want password reminders to be sent once per month
+# to your members.  Note that members may disable their own individual
+# password reminders.
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 send_reminders = 0
 
-# Tekst du skriver her vil blive tilf&oslash;jet &oslash;verst i
-# velkomsthilsenen der sendes til nye medlemmer. Velkomshilsenen
-# indeholder i forvejen vigtige adresser og URLer knyttet til
-# maillisten, s&aring; den slags information er det ikke
-# n&oslash;dvendigt at inkludere her. Her kan du tilf&oslash;je f.eks.
-# oplysning om etikette eller regler for brug af listen, o.l.
-# 
-# Bem&aelig;rk: Linierne i denne tekst vil brydes efter f&oslash;lgende
-# regler:
+# This value, if any, will be added to the front of the new-subscriber
+# welcome message.  The rest of the welcome message already describes
+# the important addresses and URLs for the mailing list, so you don't
+# need to include any of that kind of stuff here.  This should just
+# contain mission-specific kinds of things, like etiquette policies or
+# team orientation, or that kind of thing.
 # 
-# Hvert afsnit udfyldes s&aringdan at ingen linie er l&aelig;ngere en 70
-# tegn. Enhver linie der begynder med tomme tegn udfyldes ikke. Tomme
-# linier adskiller afsnit.
+# Note that this text will be wrapped, according to the following rules:
+# Each paragraph is filled so that no line is longer than 70 characters.
+# Any line that begins with whitespace is not filled. A blank line
+# separates paragraphs.
 # 
 welcome_msg = ''
 
-# S&aelig;t kun denne til 'Nej' hvis du skal tilf&oslash;je nye
-# medlemmer manuelt, og ikke vil have at de f&aring;r det at vide. Dette
-# er meget nyttigt n&aring;r man g&aring;r fra et andet mallistesystem
-# og til Mailman, og vil have at overgangen skal v&aelig;re s&aring;
-# lidt m&aelig;rkbar som muligt.
+# Turn this off only if you plan on subscribing people manually and
+# don't want them to know that you did so.  This option is most useful
+# for transparently migrating lists from some other mailing list manager
+# to Mailman.
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 send_welcome_msg = 1
 
-# Tekst der sendes til medlemmer der framelder sig listen. Hvis feltet
-# er tomt, tilf&oslash;jes der ikke nogen speciel tekst til
-# frameldingen.
+# Text sent to people leaving the list.  If empty, no special text will
+# be added to the unsubscribe message.
 goodbye_msg = ''
 
-# Send afskedshilsen til medlemmer n&aring;r de frameldes?
+# Send goodbye message to members when they are unsubscribed?
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 send_goodbye_msg = 1
 
-# Der udsendes en p&aring;mindelse til listemoderator (og
-# listeadministrator) dagligt om anmodninger der af en eller anden grund
-# venter p&aring; behandling. V&aelig;lger du "Ja", vil
-# listeadminstrator ogs&aring; modtage en meddelelse s&aring; snart en
-# anmodning ankommer.
+# List moderators (and list administrators) are sent daily reminders of
+# requests pending approval, like subscriptions to a moderated list, or
+# postings that are being held for one reason or another.  Setting this
+# option causes notices to be sent immediately on the arrival of new
+# requests as well.
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 admin_immed_notify = 1
 
-# Skal listeadministrator modtage meddelelse om tilmeldinger og
-# afmeldinger?
+# Should administrator get notices of subscribes and unsubscribes?
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 admin_notify_mchanges = 0
 
-# Approval notices are sent when mail triggers certain of the limits
-# except routine list moderation and spam filters, for which notices are
-# not sent.  This option overrides ever sending the notice.
+# Send mail to poster when their posting is held for approval?
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 respond_to_post_requests = 1
 
-# Når dette valg er aktiveret, vil al e-mail til listen blive modereret.
-# Dette valg kan være nyttigt når din mailliste f.eks. har en såkaldt
-# "flamewar", altså en "krig" hvor medlemmer kun skælder ud på hinanden.
-# En "nød-moderering" kan da hjælpe dig at fjerne usaglige meddelelser
-# til listen, og på den måde dysse en ophedet diskussion ned.
+# When this option is enabled, all list traffic is emergency moderated,
+# i.e. held for moderation.  Turn this option on when your list is
+# experiencing a flamewar and you want a cooling off period.
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 emergency = 0
 
-# Når et nyt medlem tilmeldes listen, bliver medlemmets indstillinger
-# taget herfra.
+# When a new member is subscribed to this list, their initial set of
+# options is taken from the this variable's setting.
 new_member_options = 256
 
-# Filter for administrative meddelelser vil unders&oslash;ge om
-# meddelelsen egentligt er ment som en administrativ anmodning (f.eks.
-# tilmelding, framelding, o.l.), og i s&aring; fald sende meddelelsen
-# til listeadministrator i stedet for.
+# Administrivia tests will check postings to see whether it's really
+# meant as an administrative request (like subscribe, unsubscribe, etc),
+# and will add it to the the administrative requests queue, notifying
+# the administrator of the new request, in the process.
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 administrivia = 1
 
-# Maximum st&oslash;rrelse i kilobytes (KB) for indholdet i e-mail der
-# sendes til listen. Brug v&aelig;rdien '0' for ikke at have nogen
-# begr&aelig;nsning.
+# Maximum length in kilobytes (KB) of a message body.  Use 0 for no
+# limit.
 max_message_size = 40
 
-# "Maskinnavnet" er det navn som skal benyttes for e-mailadresser
-# relateret til Mailman p&aring; denne maskine, og er normalt navnet der
-# er forbundet med e-mail-servicen p&aring; maskinen. Denne indstilling
-# kan v&aelig;re nyttig hvis maskinen har flere navne.
+# The "host_name" is the preferred name for email to mailman-related
+# addresses on this host, and generally should be the mail host's
+# exchanger address, if any.  This setting can be useful for selecting
+# among alternative names of a host that has multiple addresses.
 host_name = 'jones.dk'
 
-# I RFC 2369 defineres en r&aelig;kke List-* felter i brevhovedet, der
-# normalt tilf&oslash;jes enhver meddelelse der sendes ud via listen.
-# Disse felter er til stor gavn for brugere , som benytter et
-# e-mailprogram der f&oslash;lger standarden. Disse felter b&oslash;r
-# derfor altid v&aelig;re med.
-# 
-# Ikke alle e-mailprogrammer f&oslash;lger denne standard. Hvis der er
-# mange medlemmer p&aring; listen, der benytter e-mailprogrammer, der
-# ikke kan h&aring;ndtere disse felter i brevhovedet, kan du v&aelig;lge
-# at udelade dem. Men du b&oslash;r f&oslash;rst fors&oslash;ge at
-# l&aelig;re og forklare medlemmerne hvad hensigten med s&aring;danne
-# felter er, og hvordan de kan skjule dem i deres e-mailprogram. Som en
-# sidste udvej kan du udelade felterne, men det anbefales ikke (og denne
-# mulighed kan faktisk ogs&aring; blive fjernet i senere versioner af
-# Mailman).
-#
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# RFC 2369 defines a set of List-* headers that are normally added to
+# every message sent to the list membership. These greatly aid end-users
+# who are using standards compliant mail readers.  They should normally
+# always be enabled.
+# 
+# However, not all mail readers are standards compliant yet, and if you
+# have a large number of members who are using non-compliant mail
+# readers, they may be annoyed at these headers.  You should first try
+# to educate your members as to why these headers exist, and how to hide
+# them in their mail clients.  As a last resort you can disable these
+# headers, but this is not recommended (and in fact, your ability to
+# disable these headers may eventually go away).
+#
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 include_rfc2369_headers = 1
 
-# List-Post: feltet er et af felterne anbefalet i RFC 2369. P&aring;
-# nogle e-maillister (som f.eks. kun bruges til
-# offentligg&oslash;relser), er det kun bestemte personer der har lov
-# til at poste til listen. Almindelige medlemmer af listen har normalt
-# ikke lov til at poste til listen. For den slags lister, er List-Post:
-# feltet misvisende. S&aelig;t denne indstilling til Nej, for at
-# undg&aring; at feltet tilf&oslash;jes. (Dette p&aring;virker ikke
-# andre List-*: felter.)
-#
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# The List-Post: header is one of the headers recommended by RFC 2369.
+# However for some announce-only mailing lists, only a very select group
+# of people are allowed to post to the list; the general membership is
+# usually not allowed to post.  For lists of this nature, the List-Post:
+# header is misleading. Select No to disable the inclusion of this
+# header. (This does not affect the inclusion of the other List-*:
+# headers.)
+#
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 include_list_post_header = 1
 
+# Discard held messages older than this number of days. Use 0 for no
+# automatic discarding.
+max_days_to_hold = 0
+
 ## Language options
 #
-# Underst&oslash;ttelse af flere sprog. (Internationalisering)
-
-# Dette er standardsproget som benyttes for denne mailliste. Hvis flere
-# end et sprog/ underst&oslash;ttes, vil medlemmer af listen selv kunne
-# v&aelig;lge hvilket sprog der skal benyttes n&aring;r de g&aring;r ind
-# p&aring; deres personlige webside, og n&aring;r meddelelser fra
-# systemet sendes til dem. Hvis medlemmerne ikke &aelig;ndrer noget
-# selv, vil dette standardsprog blive benyttet. Dette g&aelig;lder
-# b&aring;de web-baserede og e-mail-baserede meddelelser, men ikke
-# meddelelser sendt af listens medlemmer.
+# Natural language (internationalization) options.
+
+# This is the default natural language for this mailing list. If more
+# than one language is supported then users will be able to select their
+# own preferences for when they interact with the list.  All other
+# interactions will be conducted in the default language.  This applies
+# to both web-based and email-based messages, but not to email posted by
+# list members.
 preferred_language = 'en'
 
-# Her er alle sprog, som denne liste har underst&oslash;ttelse for.
-# Bem&aelig;rk at standardsproget skal v&aelig;re med.
+# These are all the natural languages supported by this list. Note that
+# the default language must be included.
 available_languages = ['en', 'da']
 
-# Hvis standardsproget for din mailliste benytter et andet tegns&aelig;t
-# end ASCII og Emne prefixet for listen indeholder tegn som ikke findes
-# i ASCII-tegns&aelig;ttet, vil prefixet altid blive kodet i henhold til
-# den relevante standard. Hvis Emne prefixet kun indeholder ASCII tegn,
-# ønsker du måske at vælge Aldrig for at undgå kodning. Dette kan gøre
-# emnet lidt mere læseligt for brugere med e-mailprogrammer der ikke kan
-# håndtere andre tegnsæt end ASCII.
-# 
-# Bemærk imidlertid, at hvis din mailliste modtager både kodede og
-# ukodede emnefelter , kan det være bedst at vælge Efter behov. Med
-# denne indstilling vil Mailman ikke kode ASCII prefixer hvis resten af
-# titelfeltet kun indeholder ASCII tegn, men vil kode prefixet hvis det
-# indeholder tegn som ikke er ASCII tegn. På denne måde undgås en
-# tvetydighed i standarderne, som forårsager at visse e-mailprogrammer
-# vil vise ekstra eller manglende mellemrum imellem emne prefixet og det
-# oprindelige emne.
-#
-# gyldige værdier:
-#    0 = "Aldrig"
-#    1 = "Altid"
-#    2 = "Efter behov"
+# If your mailing list's default language uses a non-ASCII character set
+# and the prefix contains non-ASCII characters, the prefix will always
+# be encoded according to the relevant standards.  However, if your
+# prefix contains only ASCII characters, you may want to set this option
+# to Never to disable prefix encoding.  This can make the subject
+# headers slightly more readable for users with mail readers that don't
+# properly handle non-ASCII encodings.
+# 
+# Note however, that if your mailing list receives both encoded and
+# unencoded subject headers, you might want to choose As needed.  Using
+# this setting, Mailman will not encode ASCII prefixes when the rest of
+# the header contains only ASCII characters, but if the original header
+# contains non-ASCII characters, it will encode the prefix.  This avoids
+# an ambiguity in the standards which could cause some mail readers to
+# display extra, or missing spaces between the prefix and the original
+# header.
+#
+# legal values are:
+#    0 = "Never"
+#    1 = "Always"
+#    2 = "As needed"
 encode_ascii_prefixes = 0
 
 ## Nondigest options
 #
-# Regler for levering i normal-modus.
+# Policies concerning immediately delivered list traffic.
 
-# Kan medlemmer vælge normal-modus?
+# Can subscribers choose to receive mail immediately, rather than in
+# batched digests?
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 nondigestable = 1
 
-# Tekst der tilføjes &oslash;verst i e-mail der sendes til listens
-# medlemmer. This text can include Python format strings which are
-# resolved against list attributes.  The list of substitutions allowed
-# are:
+# Text prepended to the top of every immediately-delivery message. This
+# text can include Python format strings which are resolved against list
+# attributes.  The list of substitutions allowed are:
 # 
 # 
 # real_name - The "pretty" name of the list; usually the list name with
@@ -401,10 +388,9 @@ nondigestable = 1
 # 
 msg_header = ''
 
-# Tekst som tilf&oslash;jes nederst i e-mail der sendes til listens
-# medlemmer. This text can include Python format strings which are
-# resolved against list attributes.  The list of substitutions allowed
-# are:
+# Text appended to the bottom of every immediately-delivery message.
+# This text can include Python format strings which are resolved against
+# list attributes.  The list of substitutions allowed are:
 # 
 # 
 # real_name - The "pretty" name of the list; usually the list name with
@@ -432,45 +418,54 @@ msg_footer = """_______________________________________________
 %(real_name)s@%(host_name)s
 %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s"""
 
+# When you scrub attachments, they are stored in archive area and links
+# are made in the message so that the member can access via web browser.
+# If you want the attachments totally disappear, you can use content
+# filter options.
+#
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
+scrub_nondigest = False
+
 ## Digest options
 #
-# Opsætning af sammendrag-modus.
+# Batched-delivery digest characteristics.
 
-# Kan medlemmer af listen vælge sammendrag-modus?
+# Can list members choose to receive list traffic bunched in digests?
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 digestable = 1
 
-# Hvilken modus er standard for nye brugere?
+# Which delivery mode is the default for new users?
 #
-# gyldige værdier:
-#    0 = "Normal"
-#    1 = "Sammendrag"
+# legal values are:
+#    0 = "Regular"
+#    1 = "Digest"
 digest_is_default = 0
 
-# Hvilket format skal benyttes som standard for samle-email?
+# When receiving digests, which format is default?
 #
-# gyldige værdier:
-#    0 = "Ren tekst"
+# legal values are:
+#    0 = "Plain"
 #    1 = "MIME"
 mime_is_default_digest = 0
 
-# Hvor stor (i KB) m&aring; en samle-email h&oslash;jst v&aelig;re
-# f&oslash;r den udsendes?
+# How big in Kb should a digest be before it gets sent out?
 digest_size_threshhold = 30
 
-# Skal der sendes en samle-email dagligt, selv om st&oslash;rrelsen ikke
-# er opn&aring;et?
+# Should a digest be dispatched daily when the size threshold isn't
+# reached?
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 digest_send_periodic = 1
 
-# Tekst som tilf&oslash;jes &oslash;verst i samle-emailen, f&oslash;r
-# indholdsfortegnelsen.This text can include Python format strings which
+# Text attached (as an initial message, before the table of contents) to
+# the top of digests. This text can include Python format strings which
 # are resolved against list attributes.  The list of substitutions
 # allowed are:
 # 
@@ -497,10 +492,9 @@ digest_send_periodic = 1
 # 
 digest_header = ''
 
-# Tekst der tilføjes nederst i hver samle-email, som sidste
-# information.This text can include Python format strings which are
-# resolved against list attributes.  The list of substitutions allowed
-# are:
+# Text attached (as a final message) to the bottom of digests. This text
+# can include Python format strings which are resolved against list
+# attributes.  The list of substitutions allowed are:
 # 
 # 
 # real_name - The "pretty" name of the list; usually the list name with
@@ -528,277 +522,279 @@ digest_footer = """_______________________________________________
 %(real_name)s@%(host_name)s
 %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s"""
 
-# N&aring;r et nyt volume startes, &oslash;ges volume nummeret, og
-# udgavenummeret s&aelig;ttes til 1.
+# When a new digest volume is started, the volume number is incremented
+# and the issue number is reset to 1.
 #
-# gyldige værdier:
-#    0 = "&Aring;rlig"
-#    1 = "M&aring;nedlig"
-#    2 = "Kvartalsvis"
-#    3 = "Ugentlig"
-#    4 = "Daglig"
+# legal values are:
+#    0 = "Yearly"
+#    1 = "Monthly"
+#    2 = "Quarterly"
+#    3 = "Weekly"
+#    4 = "Daily"
 digest_volume_frequency = 1
 
 ## Privacy options
 #
-# Her kan du bestemme hvad der kr&aelig;ves for at tilmelde sig til
-# maillisten, og bl.a. bestemme om maillisten skal v&aelig;re skjult
-# eller ikke. Se ogs&aring; <a
-# href="http://mail.jones.dk/cgi-bin/mailman/admin/mailman/archive">Indstillinger 
-# for arkivering</a> for egne indstillinger, n&aring;r det g&aelig;lder
-# arkivet og arkivering.
-
-# Vis denne mailliste n&aring;r nogen beder om at se en oversigt over
-# maillister p&aring; denne maskine?
-#
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
-advertised = 1
-
-# bekræftelse(*) - bekr&aelig;ftelse via e-mail er n&oslash;dvendig
-# godkendelse - anmodning om medlemskab skal godkendes af
-# listeadministrator (eller evt. listemoderator) bekr&aelig;ftelse +
-# godkendelse - b&aring;de bekr&aelig;ftelse via e-mail og godkendelse
-# fra listeadministrator (evt. listemoderator) er n&oslash;dvendig
-# 
-# (*) n&aring;r nogen vil tilmelde sig en liste, sender Mailman en
-# meddelelse med en unik identifikator som skal angives for at
-# bekr&aelig;fte tilmeldingen. P&aring; den m&aring;de vil det ikke
-# v&aelig;re muligt at tilmelde nogen imod deres vilje.
-#
-# gyldige værdier:
-#    1 = "Bekr&aelig;ftelse"
-#    2 = "Godkendelse"
-#    3 = "Bekr&aelig;ftelse og godkendelse"
+# This section allows you to configure subscription and membership
+# exposure policy.  You can also control whether this list is public or
+# not.  See also the <a
+# href="http://mail.jones.dk/cgi-bin/mailman/admin/mailman/archive">Archival 
+# Options</a> section for separate archive-related privacy settings.
+
+# Advertise this list when people ask what lists are on this machine?
+#
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
+advertised = 0
+
+# Confirm (*) - email confirmation required Require approval - require
+# list administrator approval for subscriptions Confirm and approve -
+# both confirm and approve
+# 
+# (*) when someone requests a subscription, Mailman sends them a notice
+# with a unique subscription request number that they must reply to in
+# order to subscribe. This prevents mischievous (or malicious) people
+# from creating subscriptions for others without their consent.
+#
+# legal values are:
+#    1 = "Confirm"
+#    2 = "Require approval"
+#    3 = "Confirm and approve"
 subscribe_policy = 1
 
-# N&aring;r medlemmer &oslash;nsker at forlade en mailliste, sender de
-# en anmodning om framelding, enten via web, eller via e-mail. Normalt
-# er det bedst at disse anmodninger automatisk godkendes, s&aring;
-# medlemmer kan afmelde sig n&aring;r de &oslash;nsker det (mange
-# &oslash;nsker selv at kunne administrere en framelding). For nogle
-# f&aring; maillister kan det alligevel v&aelig;re aktuelt at have
-# kontrol over om medlemmer kan afmelde sig selv eller ej. En liste som
-# alle ansatte i et firma SKAL v&aelig;re medlem af, er et eksempel
-# p&aring; en s&aring;dan liste.
-#
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# When members want to leave a list, they will make an unsubscription
+# request, either via the web or via email. Normally it is best for you
+# to allow open unsubscriptions so that users can easily remove
+# themselves from mailing lists (they get really upset if they can't get
+# off lists!).
+# 
+# For some lists though, you may want to impose moderator approval
+# before an unsubscription request is processed.  Examples of such lists
+# include a corporate mailing list that all employees are required to be
+# members of.
+#
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 unsubscribe_policy = 0
 
-# Alle e-mailadresser som angives her vil blive udelukket fra listen, og
-# kan ikke tilmelde sig. Indtast e-mailadresser, en pr. linie, start
-# linien med tegnet ^ for at angive et regexp-udtryk der skal stemme
-# overens med afsenderadressen.
+# Addresses in this list are banned outright from subscribing to this
+# mailing list, with no further moderation required.  Add addresses one
+# per line; start the line with a ^ character to designate a regular
+# expression match.
 ban_list = ['walters@yahoo.com', 'carson@yahoo.com', 'gill@yahoo.com', 'kramer@yahoo.com', 'mccormick@yahoo.com', 'wolfowitz@yahoo.com', 'partnerrewards@yahoo.com', 'glover@yahoo.com', 'zakmomoh@netscape.net', 'malone@yahoo.com', 'becker@yahoo.com', 'moreno@yahoo.com', 'warburg@yahoo.com', 'newsletter@premiumreifen.de', 'goodwin@yahoo.com', 'hampton@yahoo.com', 'martinszee32@yahoo.fr', 'alexander@aheadhost.co.uk', 'buber@yahoo.com', 'lazard@yahoo.com', 'sembler@yahoo.com', 'reich@yahoo.com', 'kim@yahoo.com', 'odetts@yahoo.com', 'owens@yahoo.com']
 
-# Hvis denne indstilling ikke er sat til 'Alle', vil medlemslisten blive
-# beskyttet af medlemmernes eller administrators adgangskode.
+# When set, the list of subscribers is protected by member or admin
+# password authentication.
 #
-# gyldige værdier:
-#    0 = "Alle"
-#    1 = "Kun medlemmer af listen"
-#    2 = "Kun listeadministrator"
+# legal values are:
+#    0 = "Anyone"
+#    1 = "List members"
+#    2 = "List admin only"
 private_roster = 1
 
-# V&aelig;lger du 'Ja' her, vil medlemmers e-mailadresser blive
-# omskrevet n&aring;r de vises i en oversigt p&aring; websiderne
-# (b&aring;de som tekst og som links), s&aring; de ikke er nemme at
-# tolke som e-mailadresser. Formålet er at undg&aring; at medlemmernes
-# mailadresser bliver opsamlet af e-mailsniffere som skanner websider
-# for e-mailadresser (og derefter bruger dem til at udsende spam/junk
-# mail).
-#
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# Setting this option causes member email addresses to be transformed
+# when they are presented on list web pages (both in text and as links),
+# so they're not trivially recognizable as email addresses.  The
+# intention is to prevent the addresses from being snarfed up by
+# automated web scanners for use by spammers.
+#
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 obscure_addresses = 1
 
 ## Privacy options
 #
-# N&aring;r en meddelelse sendes til maillisten, g&aring;r den igennem
-# nogle trin for at afg&oslash;re om moderator skal godkende meddelelsen
-# eller ikke. Her finder du indstillinger til at kontrollere moderation
-# af e-mail fra b&aring;de medlemmer og ikke-medlemmer.
-# 
-# <p>E-mail fra medlemmer holdes tilbage for godkendelse hvis deres
-# <b>moderationsflag</b> er sat. Du kan bestemme om e-mail fra medlemmer
-# normalt skal vurderes eller ikke f&oslash;r den sendes til listen.
-# 
-# <p>E-mail som ikke er sendt af medlemmer af listen, kan automatisk
-# blive <a
-# href="?VARHELP=privacy/sender/accept_these_nonmembers">godkendt</a>,
-# <a href="?VARHELP=privacy/sender/hold_these_nonmembers">holdt tilbage
-# for godkendelse</a>, <a
-# href="?VARHELP=privacy/sender/reject_these_nonmembers">afvist (sendt
-# retur)</a>, eller <a
-# href="?VARHELP=privacy/sender/discard_these_nonmembers">slettet</a>,
-# enten enkeltvis eller som en gruppe. Al e-mail fra ikke-medlemmer, som
-# ikke specifikt bliver godkendt, sendt retur eller slettet, vil blive
-# behandlet alt efter hvad <a
-# href="?VARHELP=privacy/sender/generic_nonmember_action">generelle
-# regler for ikke-medlemmer</a> viser.
-# 
-# <p>I tekstboksene nedenfor kan du tilf&oslash;je en e-mailadresse pr.
-# linie. Du kan ogs&aring; tilf&oslash;je  <a
-# href="http://www.python.org/doc/current/lib/module-re.html">Python
-# regexp-udtryk</a>. Begynd i s&aring; fald linien med tegnet ^ for at
-# markere at det er et s&aring;dant udtryk. N&aring;r du benytter
-# backslash, skriv da lige som i rene strings (Python raw strings)
-# (normalt kun &eacute;n backslash ad gangen).
-# 
-# <p>Bem&aelig;rk: sammenligning med normale e-mailadresser
-# udf&oslash;res f&oslash;rst, regexp-udtryk vil derfor blive behandlet
-# sidst.
-
-# Hvert medlem af listen har et moderationsflag som fort&aelig;ller om
-# e-mails fra medlemmet kan sendes direkte til e-maillisten, eller om de
-# f&oslash;rst skal godkendes af listemoderator. N&aring;r
-# moderationsflaget er sat til, skal e-mails fra medlemmet godkendes af
-# listemoderator f&oslash;r de udsendes til alle p&aring; listen. Som
-# listeadministrator kan du for hvert enkelt medlem bestemme om
-# medlemmets e-mail skal modereres eller ikke. N&aring;r et nyt medlem
-# tilmeldes listen, s&aelig;ttes moderationsflaget til den indstilling
-# du v&aelig;lger her. S&aelig;t den til 'Nej' hvis du &oslash;nsker at
-# e-mail fra medlemmer normalt skal g&aring; lige til listen. S&aelig;t
-# den til 'Ja' hvis du &oslash;nsker at e-mail fra nye medlemmer skal
-# godkendes f&oslash;r de udsendes til hele listen. Du kan altid
-# s&aelig;tte moderationsflaget for hvert enkelt medlem fra
-# Administration af medlemmer siden.
-#
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# When a message is posted to the list, a series of moderation steps are
+# take to decide whether the a moderator must first approve the message
+# or not.  This section contains the controls for moderation of both
+# member and non-member postings.
+# 
+# <p>Member postings are held for moderation if their <b>moderation
+# flag</b> is turned on.  You can control whether member postings are
+# moderated by default or not.
+# 
+# <p>Non-member postings can be automatically <a
+# href="?VARHELP=privacy/sender/accept_these_nonmembers" >accepted</a>,
+# <a href="?VARHELP=privacy/sender/hold_these_nonmembers">held for
+# moderation</a>, <a
+# href="?VARHELP=privacy/sender/reject_these_nonmembers" >rejected</a>
+# (bounced), or <a
+# href="?VARHELP=privacy/sender/discard_these_nonmembers"
+# >discarded</a>, either individually or as a group.  Any posting from a
+# non-member who is not explicitly accepted, rejected, or discarded,
+# will have their posting filtered by the <a
+# href="?VARHELP=privacy/sender/generic_nonmember_action">general
+# non-member rules</a>.
+# 
+# <p>In the text boxes below, add one address per line; start the line
+# with a ^ character to designate a <a href=
+# "http://www.python.org/doc/current/lib/module-re.html" >Python regular
+# expression</a>.  When entering backslashes, do so as if you were using
+# Python raw strings (i.e. you generally just use a single backslash).
+# 
+# <p>Note that non-regexp matches are always done first.
+
+# Each list member has a moderation flag which says whether messages
+# from the list member can be posted directly to the list, or must first
+# be approved by the list moderator.  When the moderation flag is turned
+# on, list member postings must be approved first.  You, the list
+# administrator can decide whether a specific individual's postings will
+# be moderated or not.
+# 
+# When a new member is subscribed, their initial moderation flag takes
+# its value from this option.  Turn this option off to accept member
+# postings by default.  Turn this option on to, by default, moderate
+# member postings first.  You can always manually set an individual
+# member's moderation bit by using the membership management screens.
+#
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 default_member_moderation = 0
 
+# Hold -- this holds the message for approval by the list moderators.
+# 
+# Reject -- this automatically rejects the message by sending a bounce
+# notice to the post's author.  The text of the bounce notice can be <a
+# href="?VARHELP=privacy/sender/member_moderation_notice" >configured by
+# you.
 # 
-# Hold tilbage -- meddelelsen holdes tilbage for godkendelse af
-# listemoderator(er). Afvis -- meddelelsen sendes automatisk retur til
-# afsender. Begrundelsen der sendes kan du skrive selv Slet --
-# meddelelsen bliver fjernet uden at give besked om dette til afsender.
+# Discard -- this simply discards the message, with no notice sent to
+# the post's author.
 # 
 #
-# gyldige værdier:
-#    0 = "Hold&nbsp;tilbage"
-#    1 = "Afvis"
-#    2 = "Slet"
+# legal values are:
+#    0 = "Hold"
+#    1 = "Reject"
+#    2 = "Discard"
 member_moderation_action = 0
 
-# Tekst som skal sendes med meddelelsen om afvisning som sendes til
-# modererede medlemmer af listen.
+# Text to include in any <a
+# href="?VARHELP/privacy/sender/member_moderation_action" >rejection
+# notice to be sent to moderated members who post to this list.
 member_moderation_notice = ''
 
-# E-mail fra disse ikke-medlemmer vil automatisk blive godkendt.
-# Tilf&oslash;j e-mailadresser, en pr. linie. Start linien med tegnet ^
-# for at angive et regexp-udtryk som skal stemme overens med
-# afsenderadressen.
+# Postings from any of these non-members will be automatically accepted
+# with no further moderation applied.  Add member addresses one per
+# line; start the line with a ^ character to designate a regular
+# expression match.
 accept_these_nonmembers = []
 
-# e-mail fra disse ikke-medlemmer vil automatisk blive holdt tilbage for
-# vurdering af listemoderator. Afsenderen vil modtage en meddelelse om
-# dette, med bl.a. instruktioner om hvordan han/hun kan
-# tilbagetr&aelig;kke sin e-mail. Indtast e-mailadresser, en pr. linie.
-# Start linien med tegnet ^ for at angive et regexp-udtryk som skal
-# stemme overens med afsenderadressen.
+# Postings from any of these non-members will be immediately and
+# automatically held for moderation by the list moderators. The sender
+# will receive a notification message which will allow them to cancel
+# their held message.  Add member addresses one per line; start the line
+# with a ^ character to designate a regular expression match.
 hold_these_nonmembers = []
 
-# E-mail fra disse ikke-medlemmer vil automatisk blive afvist. De vil
-# f&aring; mailen retur, med en meddelelse om at den blev automatisk
-# afvist. Dette valg b&oslash;r ikke benyttes for kendte spammere, de
-# b&oslash;r automatisk slettes. Indtast e-mailadresser, en pr. linie.
-# Start linien med tegnet ^ for at angive et regexp-udtryk som skal
-# stemme overens med afsenderadressen.
+# Postings from any of these non-members will be automatically rejected.
+# In other words, their messages will be bounced back to the sender with
+# a notification of automatic rejection.  This option is not appropriate
+# for known spam senders; their messages should be <a
+# href="?VARHELP=privacy/sender/discard_these_nonmembers" >automatically
+# discarded.
+# 
+# Add member addresses one per line; start the line with a ^ character
+# to designate a regular expression match.
 reject_these_nonmembers = []
 
-# E-mail fra disse ikke-medlemmer vil automatisk blive slettet. Det vil
-# sige at meddelelsen afvises uden nogen form for tilbagemelding, men
-# listemoderator kan (om &oslash;nsket) modtage en kopi af den afviste
-# e-mail. Tilf&oslash;j e-mailadresser, en pr. linie, start linien med
-# tegnet ^ for at angive et regexp-udtryk der skal stemme overens med
-# afsenderadressen.
+# Postings from any of these non-members will be automatically
+# discarded.  That is, the message will be thrown away with no further
+# processing or notification.  The sender will not receive a
+# notification or a bounce, however the list moderators can optionally
+# <a href="?VARHELP=privacy/sender/forward_auto_discards" >receive
+# copies of auto-discarded messages..
+# 
+# Add member addresses one per line; start the line with a ^ character
+# to designate a regular expression match.
 discard_these_nonmembers = ['bounce@gaintrafficfast.com', 'loteria_espana@zwallet.com', 'nijie101@fsmail.net', 'douglascole@telstra.com', 'bush.e@telstra.com', 'erjam_james@telstra.com', 'gracestaylor1@netscape.net', 'walters@yahoo.com', 'carson@yahoo.com', 'gill@yahoo.com', 'kramer@yahoo.com', 'mccormick@yahoo.com', 'wolfowitz@yahoo.com', 'partnerrewards@yahoo.com', 'glover@yahoo.com', 'zakmomoh@netscape.net', 'malone@yahoo.com', 'becker@yahoo.com', 'moreno@yahoo.com', 'warburg@yahoo.com', 'newsletter@premiumreifen.de', 'goodwin@yahoo.com', 'hampton@yahoo.com', 'martinszee32@yahoo.fr', 'alexander@aheadhost.co.uk', 'buber@yahoo.com', 'lazard@yahoo.com', 'sembler@yahoo.com', 'reich@yahoo.com', 'kim@yahoo.com', 'odetts@yahoo.com', 'owens@yahoo.com']
 
-# N&aring;r en e-mail fra et ikke-medlem bliver modtaget, sammenlignes
-# e-mailens afsender med listen over e-mailadresser der skal godkendes,
-# holdes tilbage, <a
-# href="?VARHELP=privacy/sender/reject_these_nonmembers" >afvises
-# (sendes retur), eller slettes. Hvis afsenderadressen ikke stemmer
-# overens med en adresse der findes i listerne, bliver f&oslash;lgende
-# afg&oslash;relse truffet.
-#
-# gyldige værdier:
-#    0 = "Godkend"
-#    1 = "Hold&nbsp;tilbage"
-#    2 = "Afvis"
-#    3 = "Slet"
+# When a post from a non-member is received, the message's sender is
+# matched against the list of explicitly <a
+# href="?VARHELP=privacy/sender/accept_these_nonmembers" >accepted,
+# held, <a href="?VARHELP=privacy/sender/reject_these_nonmembers"
+# >rejected (bounced), and <a
+# href="?VARHELP=privacy/sender/discard_these_nonmembers" >discarded
+# addresses.  If no match is found, then this action is taken.
+#
+# legal values are:
+#    0 = "Accept"
+#    1 = "Hold"
+#    2 = "Reject"
+#    3 = "Discard"
 generic_nonmember_action = 1
 
-# Skal meddelelser fra ikke-medlemmer, hvis mail automatisk slettes,
-# videresendes til listemoderator?
+# Should messages from non-members, which are automatically discarded,
+# be forwarded to the list moderator?
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 forward_auto_discards = 1
 
+# Text to include in any rejection notice to be sent to non-members who
+# post to this list. This notice can include the list's owner address by
+# %(listowner)s and replaces the internally crafted default message.
+nonmember_rejection_notice = ''
+
 ## Privacy options
 #
-# Her kan du ops&aelig;tte filtrering baseret på modtageren af
-# meddelelsen.
+# This section allows you to configure various filters based on the
+# recipient of the message.
 
-# Meget (faktisk det meste) spam/junk mail har ikke de endelige
-# modtagere i modtagerfelterne. Faktisk indeholder felterne To: og/eller
-# Cc: oftest en helt ugyldig adresse. Begr&aelig;nsningen du
-# s&aelig;tter her har kun indvirkning p&aring; det som st&aring;r
-# f&oslash;r '@' tegnet i adressen, men filtret vil alligevel opfange og
-# blokere det meste spam/junk mail.
+# Many (in fact, most) spams do not explicitly name their myriad
+# destinations in the explicit destination addresses - in fact often the
+# To: field has a totally bogus address for obfuscation.  The constraint
+# applies only to the stuff in the address before the '@' sign, but
+# still catches all such spams.
+# 
+# The cost is that the list will not accept unhindered any postings
+# relayed from other addresses, unless
 # 
-# Prisen for dette er, at listen ikke uhindret vil kunne modtage e-mail
-# videresendt via andre e-mailadresser, med mindre
 # 
+# The relaying address has the same name, or
+# 
+# The relaying address name is included on the options that specifies
+# acceptable aliases for the list.
 # 
-# Adressen der videresendes fra hedder det samme, eller Adressen der
-# videresendes fra inkluderes i indstillingen som bestemmer gyldige
-# aliaser for listen.
 # 
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 require_explicit_destination = 1
 
-# Alternative e-mailadresser som godtages n&aring;r
-# 'require_explicit_destination' er sat til. Som v&aelig;rdi for denne
-# indstilling skal du angive regexp-udtryk ("regular expressions"), et
-# udtryk pr. linie, der sammenlignes med hver modtageradresse i
-# meddelelsen. Sammenligningen udf&oslash;res med Pythons re.match()
-# funktion, som betyder at de kun g&aelig;lder for begyndelsen af
-# strengen.
-# 
-# For bagudkompatibilitet med Mailman 1.1, hvis regexp-udtryk ikke
-# indeholder en '@', sammenlignes udtrykket kun med den f&oslash;rste
-# del (det som st&aring;r f&oslash;r '@') i modtageradressen. Hvis
-# sammenligningen ikke lykkes, eller hvis udtrykket ikke indholder en
-# '@', sammenlignes udtrykket med hele modtageradressen.
-# 
-# Sammenligning med kun den f&oslash;rste del af en modtageradresse
-# underst&oslash;ttes ikke l&aelig;ngere. I fremtidige versioner af
-# Mailman vil kun sammenligning med hele modtageradresser blive
-# underst&oslash;ttet.
+# Alternate addresses that are acceptable when
+# `require_explicit_destination' is enabled.  This option takes a list
+# of regular expressions, one per line, which is matched against every
+# recipient address in the message.  The matching is performed with
+# Python's re.match() function, meaning they are anchored to the start
+# of the string.
+# 
+# For backwards compatibility with Mailman 1.1, if the regexp does not
+# contain an `@', then the pattern is matched against just the local
+# part of the recipient address.  If that match fails, or if the pattern
+# does contain an `@', then the pattern is matched against the entire
+# recipient address.
+# 
+# Matching against the local part is deprecated; in a future release,
+# the pattern will always be matched against the entire recipient
+# address.
 acceptable_aliases = ''
 
-# Hvis en mail der er sendt til listen indeholder s&aring; mange som
-# eller flere modtagere end denne v&aelig;rdi, holdes mailen tilbage,
-# s&aring; listeadministrator eventuelt kan godkende den. Brug
-# v&aelig;rdien 0 for ingen begr&aelig;nsning.
+# If a posting has this number, or more, of recipients, it is held for
+# admin approval.  Use 0 for no ceiling.
 max_num_recipients = 10
 
 ## Privacy options
 #
-# Her kan du opsætte forskellige anti-spam filtre, som kan bidrage til
-# at reducere mængden af spam der distribueres via e-maillisten.
+# This section allows you to configure various anti-spam filters posting
+# filters, which can help reduce the amount of spam your list members
+# end up receiving.
+# 
 
 # Each header filter rule has two parts, a list of regular expressions,
 # one per line, and an action to take.  Mailman matches the message's
@@ -809,22 +805,23 @@ max_num_recipients = 10
 # You can have more than one filter rule for your list.  In that case,
 # each rule is matched in turn, with processing stopped after the first
 # match.
+# 
+# Note that headers are collected from all the attachments (except for
+# the mailman administrivia message) and matched against the regular
+# expressions. With this feature, you can effectively sort out messages
+# with dangerous file types or file name extensions.
 header_filter_rules = []
 
-# Brug denne indstilling til at bortfiltrere mail til listen, baseret
-# p&aring; indholdet af et eller flere felter i brevhovedet. Her skal du
-# skrive regexp-udtryk (regular expressions), et pr. linie, som
-# sammenlignes med det aktuelle felt. Sammenligningen skelner ikke
-# imellem store og sm&aring; bogstaver. Linier der begynder med '#'
-# sammenlignes ikke.
+# Use this option to prohibit posts according to specific header values.
+# The target value is a regular-expression for matching against the
+# specified header.  The match is done disregarding letter case.  Lines
+# beginning with '#' are ignored as comments.
 # 
-# For eksempel: udtrykket to: .*@public.com fort&aelig;ller at al mail
-# som indeholder '@public.com' i To: feltet, skal holdes tilbage for
-# godkendelse.
+# For example:to: .*@public.com  says to hold all postings with a To:
+# mail header containing '@public.com' anywhere among the addresses.
 # 
-# Bem&aelig;rk: tomme tegn i starten af regexp-udtrykket fjernes. Dette
-# kan omg&aring;s p&aring; flere m&aring;der, f.eks. ved at bruge
-# escape-tegn eller parenteser.
+# Note that leading whitespace is trimmed from the regexp.  This can be
+# circumvented in a number of ways, e.g. by escaping or bracketing it.
 bounce_matching_headers = """
 # Lines that *start* with a '#' are comments.
 to: friend@public.com
@@ -834,415 +831,439 @@ from: .*@uplinkpro.com"""
 
 ## Bounce options
 #
-# Disse regler bestemmer hvordan automatisk behandling af returmails
-# skal foreg&aring;. Her er en oversigt over hvordan det virker.
-# 
-# <p>N&aring;r Mailman modtager en returmail, bliver to ting
-# fors&oslash;gt tolket. Den ene er e-mailadressen for medlemmet som
-# egentlig skulle modtage e-mailen, og den anden er &aring;rsagen til
-# problemet. &Aring;rsagen tolkes til at v&aelig;re <em>alvorlig</em>
-# eller <em>harml&oslash;s</em> alt efter om &aring;rsagen er af kritisk
-# eller af mindre alvorlig art. Hvis der er tvivl, tolkes &aring;rsagen
-# som alvorlig.
-# 
-# <p>Hvis ingen e-mailadresse kan hentes ud af meddelelsen, bliver den
-# normalt afvist. Ellers vil medlemmet som har e-mailadressen f&aring;
-# tildelt et <em>returtal</em>, og hver gang der kommer en
-# returmeddelelse vil tallet &oslash;ges. Alvorlige &aring;rsager
-# f&oslash;rer til at tallet &oslash;ges med 1, harml&oslash;se
-# &aring;rsager f&oslash;rer til at det &oslash;ges med 0.5. Dette sker
-# kun &eacute;n gang pr. dag, s&aring; selv om der kommer 10 alvorlige
-# returmails fra et medlem p&aring; &eacute;n dag, vil tallet kun
-# &oslash;ges med 1.
-# 
-# <p>N&aring;r returtallet for et medlem n&aring;r en vis <a
-# href="?VARHELP=bounce/bounce_score_threshold">gr&aelig;nse</a>,
-# stoppes levering til medlemmet. Dermed vil medlemmet ikke modtage
-# e-mail fra listen f&oslash;r levering s&aelig;ttes til igen. Medlemmet
-# vil med j&aelig;vne mellemrum modtage meddelelse om at dette er sket,
-# og hvad han/hun skal g&oslash;re for at f&aring; e-mail fra listen
-# igen.
-# 
-# <p>Du kan bestemme <a
-# href="?VARHELP=bounce/bounce_you_are_disabled_warnings">hvor mange
-# advarsler</a> medlemmet skal have og <a
-# href="?VARHELP=bounce/bounce_you_are_disabled_warnings_interval">hvor
-# ofte</a> han/hun skal modtage s&aring;danne advarsler.
-# 
-# <p>Der er en vigtig indstilling mere: efter en vis tid -- hvor ingen
-# returmeddelelser dukker op -- regnes returinformation for at
-# v&aelig;re <a
-# href="?VARHELP=bounce/bounce_info_stale_after">for&aelig;ldet</a> og
-# stoppes. Ved at justere denne v&aelig;rdi, og s&aelig;tte en
-# gr&aelig;nse for returantallet, kan du bestemme hvor lang tid der skal
-# g&aring; f&oslash;r levering til et medlem stoppes. Begge disse
-# v&aelig;rdier b&oslash;r tilpasses efter hvor ofte og hvor meget
-# e-mail der sendes til din liste.
-
-# Ved at sætte denne værdi til Nej, slår du al automatisk tolkning af
-# returmeddelelser for denne liste fra. Bemærk at hvis meddelelser
-# afvises vil listeadministratoren ikke blive forstyrret med dem.
-#
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# These policies control the automatic bounce processing system in
+# Mailman.  Here's an overview of how it works.
+# 
+# <p>When a bounce is received, Mailman tries to extract two pieces of
+# information from the message: the address of the member the message
+# was intended for, and the severity of the problem causing the bounce.
+# The severity can be either <em>hard</em> or <em>soft</em> meaning
+# either a fatal error occurred, or a transient error occurred.  When in
+# doubt, a hard severity is used.
+# 
+# <p>If no member address can be extracted from the bounce, then the
+# bounce is usually discarded.  Otherwise, each member is assigned a
+# <em>bounce score</em> and every time we encounter a bounce from this
+# member we increment the score.  Hard bounces increment by 1 while soft
+# bounces increment by 0.5.  We only increment the bounce score once per
+# day, so even if we receive ten hard bounces from a member per day,
+# their score will increase by only 1 for that day.
+# 
+# <p>When a member's bounce score is greater than the <a
+# href="?VARHELP=bounce/bounce_score_threshold">bounce score
+# threshold</a>, the subscription is disabled.  Once disabled, the
+# member will not receive any postings from the list until their
+# membership is explicitly re-enabled (either by the list administrator
+# or the user).  However, they will receive occasional reminders that
+# their membership has been disabled, and these reminders will include
+# information about how to re-enable their membership.
+# 
+# <p>You can control both the <a
+# href="?VARHELP=bounce/bounce_you_are_disabled_warnings">number of
+# reminders</a> the member will receive and the <a
+# href="?VARHELP=bounce/bounce_you_are_disabled_warnings_interval"
+# >frequency</a> with which these reminders are sent.
+# 
+# <p>There is one other important configuration variable; after a
+# certain period of time -- during which no bounces from the member are
+# received -- the bounce information is <a
+# href="?VARHELP=bounce/bounce_info_stale_after">considered stale</a>
+# and discarded.  Thus by adjusting this value, and the score threshold,
+# you can control how quickly bouncing members are disabled.  You should
+# tune both of these to the frequency and traffic volume of your list.
+
+# By setting this value to No, you disable all automatic bounce
+# processing for this list, however bounce messages will still be
+# discarded so that the list administrator isn't inundated with them.
+#
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 bounce_processing = 1
 
-# Hvert medlem tildeles et returtal, og hver gang der kommer en
-# returmeddelelse vil dette tal &oslash;ges.  Alvorlige (&aring;rsager
-# f&oslash;rer til at det &oslash;ges med 1, mens harml&oslash;se
-# &aring;rsager f&oslash;rer til at det &oslash;ges med 0.5. Dette sker
-# kun &eacute;n gang pr. dag, s&aring; selv om der kommer 10 alvorlige
-# returmails fra et medlem p&aring; &eacute;n dag, vil tallet kun
-# &oslash;ges med 1.
-# 
-# Her s&aelig;ttes den &oslash;vre gr&aelig;nse for medlemmets returtal
-# Overskrides denne gr&aelig;nse stoppes levering automatisk, men
-# medlemmet bliver ikke fjernet fra listen.
+# Each subscriber is assigned a bounce score, as a floating point
+# number.  Whenever Mailman receives a bounce from a list member, that
+# member's score is incremented.  Hard bounces (fatal errors) increase
+# the score by 1, while soft bounces (temporary errors) increase the
+# score by 0.5.  Only one bounce per day counts against a member's
+# score, so even if 10 bounces are received for a member on the same
+# day, their score will increase by just 1.
+# 
+# This variable describes the upper limit for a member's bounce score,
+# above which they are automatically disabled, but not removed from the
+# mailing list.
 bounce_score_threshold = 5.0
 
-# Antal dage f&oslash;r returinformation stoppes hvis der ikke dukker
-# flere returmails op. Dette tal skal v&aelig;re et heltal.
+# The number of days after which a member's bounce information is
+# discarded, if no new bounces have been received in the interim.  This
+# value must be an integer.
 bounce_info_stale_after = 7
 
-# Hvor mange Levering til dig er stoppet advarsler der skal sendes til
-# et medlem f&oslash;r medlemmet frameldes listen. S&aelig;t denne værdi
-# til 0 for at fjerne et medlem fra listen straks, hvis der kommer
-# returmails fra medlemmets e-mailadresse. Dette tal skal være et
-# heltal.
+# How many Your Membership Is Disabled warnings a disabled member should
+# get before their address is removed from the mailing list.  Set to 0
+# to immediately remove an address from the list once their bounce score
+# exceeds the threshold.  This value must be an integer.
 bounce_you_are_disabled_warnings = 3
 
-# Antal dage imellem hver gang en Levering til dig er stoppet advarsel
-# skal sendes ud. Dette tal skal være et heltal.
+# The number of days between sending the Your Membership Is Disabled
+# warnings.  This value must be an integer.
 bounce_you_are_disabled_warnings_interval = 7
 
-# Mailmans automatiske returmailh&aring;ndtering er meget robust, men
-# det er alligevel umuligt at genkende alle typer returmails der kommer.
-# Du b&oslash;r v&aelig;lge Ja her, af to grunde: 1) Hvis det virkelig
-# er en permanent returmail fra et medlem af listen, b&oslash;r du
-# antagelig manuelt afmelde medlemmet fra listen, og 2) du vil
-# m&aring;ske sende en meddelelse til udviklerne af Mailman s&aring;dan
-# at returmails automatisk genkendes af Mailman i senere versioner. Hvis
-# du ikke vil g&oslash;re nogen af delene, s&aelig;ttes denne
-# indstilling til Nej. S&aring; vil alle returmails afvises automatisk
-# uden videre behandling. Bem&aelig;rk: Denne indstilling vil ogs&aring;
-# indvirke p&aring; al e-mail der sendes til listens -admin adresse. Den
-# adresse er for&aelig;ldet og udg&aring;et, men måske vil nogen
-# alligevel fortsat sende e-mail til den. Hvis nogen g&oslash;r det, og
-# du har sat denne indstilling til Nej, vil disse mails ogs&aring; blive
-# afvist. M&aring;ske vil du ogs&aring; ops&aelig;tte et automatisk svar
-# p&aring; e-mail sendt til -owner og -admin adresserne.
-#
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# While Mailman's bounce detector is fairly robust, it's impossible to
+# detect every bounce format in the world.  You should keep this
+# variable set to Yes for two reasons: 1) If this really is a permanent
+# bounce from one of your members, you should probably manually remove
+# them from your list, and 2) you might want to send the message on to
+# the Mailman developers so that this new format can be added to its
+# known set.
+# 
+# If you really can't be bothered, then set this variable to No and all
+# non-detected bounces will be discarded without further processing.
+# 
+# Note: This setting will also affect all messages sent to your list's
+# -admin address.  This address is deprecated and should never be used,
+# but some people may still send mail to this address.  If this happens,
+# and this variable is set to No those messages too will get discarded.
+# You may want to set up an autoresponse message for email to the -owner
+# and -admin address.
+#
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 bounce_unrecognized_goes_to_list_owner = 1
 
-# Ved at sætte denne til Nej, fravælges beskeden der normalt sendes til
-# ejer(e) af listen, når levering af e-mail til et medlem stoppes på
-# grund af for mange returmails. Der vil til gengæld altid blive forsøgt
-# afsendt en e-mail med besked til medlemmet.
+# By setting this value to No, you turn off notification messages that
+# are normally sent to the list owners when a member's delivery is
+# disabled due to excessive bounces. An attempt to notify the member
+# will always be made.
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 bounce_notify_owner_on_disable = 1
 
-# Ved at sætte denne til Nej, fravælges beskeden der normalt sendes til
-# ejer(e) af listen, når et medlem frameldes listen på grund af for
-# mange returmails. Der vil til gengæld altid blive forsøgt afsendt en
-# e-mail med besked til medlemmet.
+# By setting this value to No, you turn off notification messages that
+# are normally sent to the list owners when a member is unsubscribed due
+# to excessive bounces.  An attempt to notify the member will always be
+# made.
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 bounce_notify_owner_on_removal = 1
 
 ## Archive options
 #
-# Regler for arkivering
+# List traffic archival policies.
 
-# Arkiver e-mail i et arkiv?
+# Archive messages?
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 archive = 1
 
-# Skal arkivet v&aelig;re offentligt eller privat?
+# Is archive file source for public or private archival?
 #
-# gyldige værdier:
-#    0 = "Offentligt"
-#    1 = "Privat"
+# legal values are:
+#    0 = "public"
+#    1 = "private"
 archive_private = 0
 
-# Hvor ofte skal arkivet deles op?
+# How often should a new archive volume be started?
 #
-# gyldige værdier:
-#    0 = "&Aring;rlig"
-#    1 = "M&aring;nedlig"
-#    2 = "Kvartalsvis"
-#    3 = "Ugentlig"
-#    4 = "Daglig"
+# legal values are:
+#    0 = "Yearly"
+#    1 = "Monthly"
+#    2 = "Quarterly"
+#    3 = "Weekly"
+#    4 = "Daily"
 archive_volume_frequency = 1
 
 ## Gateway options
 #
-# E-mail-Til-Nyhedsgruppe og Nyhedsgruppe-Til-E-mail tjeneste.
+# Mail-to-News and News-to-Mail gateway services.
 
-# Nyhedsgruppe-tjeneste er ikke en del af Mailman. Du skal have adgang
-# til en eksisterende NNTP tjeneste, og maskinen som denne mailliste
-# k&oslash;rer p&aring; skal have adgang til at hente og afsende
-# meddelelser til NNTP tjenesten.
+# This value may be either the name of your news server, or optionally
+# of the format name:port, where port is a port number.
+# 
+# The news server is not part of Mailman proper.  You have to already
+# have access to an NNTP server, and that NNTP server must recognize the
+# machine this mailing list runs on as a machine capable of reading and
+# posting news.
 nntp_host = ''
 
-# Navn p&aring; nyhedsgruppe der skal sendes til og/eller fra.
+# The name of the Usenet group to gateway to and/or from.
 linked_newsgroup = ''
 
-# Skal nye meddelelser til denne liste sendes til nyhedsgruppen?
+# Should new posts to the mailing list be sent to the newsgroup?
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 gateway_to_news = 0
 
-# Skal nye meddelelser til nyhedsgruppen sendes til denne mailliste?
+# Should new posts to the newsgroup be sent to the mailing list?
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 gateway_to_mail = 0
 
-# Denne indstilling fort&aelig;ller Mailman hvilken slags
-# moderationsregler nyhedsgruppen har og hvordan de koordineres med
-# maillistens moderationsregler. Dette g&aelig;lder kun nyhedgrupper du
-# overfører meddelelser til, s&aring; hvis du kun overf&oslash;rer fra
-# en nyhedsgruppe, eller nyhedsgruppen du overf&oslash;rer til ikke er
-# modereret, s&aelig;ttes indstillingen til Ingen.
-# 
-# Hvis nyhedsgruppen er modereret, kan du s&aelig;tte maillisten til at
-# v&aelig;re moderationsadressen for nyhedsgruppen. Ved at vælge
-# Modereret, vil en ekstra meddelelse holdes tilbage i
-# godkendelsesprocessen. Al mail sendt til maillisten skal godkendes
-# f&oslash;r den sendes til nyhedsgruppen, eller til medlemmerne af
-# listen.
-# 
-# Vær opm&aelig;rksom p&aring; at hvis brevhovedet i mailen har et
-# Approved: felt med listens administrative adgangskode, vil denne regel
-# ikke blive benyttet. På den m&aring;de kan priviligerede afsendere
-# sende mail direkte til listen og nyhedsgruppen.
-# 
-# Hvis nyhedsgruppen er modereret, men du alligevel vil have en
-# &aring;ben liste, b&oslash;r du vælge Åben liste, modereret
-# nyhedsgruppe. S&aring; vil de s&aelig;dvanlige mekanismer for
-# moderation blive benyttet i Mailman, men alle meddelelser der sendes
-# til Usenet vil f&aring; et Approved felt i brevhovedet.
-#
-# gyldige værdier:
-#    0 = "Ingen"
-#    1 = "Åben liste, modereret nyhedsgruppe"
-#    2 = "Modereret"
+# This setting determines the moderation policy of the newsgroup and its
+# interaction with the moderation policy of the mailing list.  This only
+# applies to the newsgroup that you are gatewaying to, so if you are
+# only gatewaying from Usenet, or the newsgroup you are gatewaying to is
+# not moderated, set this option to None.
+# 
+# If the newsgroup is moderated, you can set this mailing list up to be
+# the moderation address for the newsgroup.  By selecting Moderated, an
+# additional posting hold will be placed in the approval process.  All
+# messages posted to the mailing list will have to be approved before
+# being sent on to the newsgroup, or to the mailing list membership.
+# 
+# Note that if the message has an Approved header with the list's
+# administrative password in it, this hold test will be bypassed,
+# allowing privileged posters to send messages directly to the list and
+# the newsgroup.
+# 
+# Finally, if the newsgroup is moderated, but you want to have an open
+# posting policy anyway, you should select Open list, moderated group.
+# The effect of this is to use the normal Mailman moderation facilities,
+# but to add an Approved header to all messages that are gatewayed to
+# Usenet.
+#
+# legal values are:
+#    0 = "None"
+#    1 = "Open list, moderated group"
+#    2 = "Moderated"
 news_moderation = 0
 
-# Mailman tilføjer normalt en tekst du selv kan tilrette (emne prefix)
-# foran emnefeltet i mail som sendes til listen, og normalt sker dette
-# også for mail som sendes videre til Usenet. Du kan sætte denne
-# indstilling til Nej hvis du ikke ønsker emne prefix tilføjet til mail
-# som sendes til Usenet. Sættes emne prefix for listen til off, vil
-# videresendte meddelelser heller ikke få prefix tilføjet.
+# Mailman prefixes Subject: headers with text you can customize and
+# normally, this prefix shows up in messages gatewayed to Usenet.  You
+# can set this option to No to disable the prefix on gated messages.  Of
+# course, if you turn off normal Subject: prefixes, they won't be
+# prefixed for gated messages either.
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 news_prefix_subject_too = 1
 
 ## Autoreply options
 #
-# Indstillinger for automatiske svar.<p>
+# Auto-responder characteristics.<p>
 # 
-# I tekstboksene nedenfor kan du bruge følgende variabler: (skriv:
-# %(&lt;variabelnavn&gt;)s ) for at indsætte ønsket information: <p><ul>
-# <li><b>listname</b> - <em>navnet p&aring; listen</em>
-# <li><b>listurl</b> - <em>URL til listens webside</em>
-# <li><b>requestemail</b> - <em>listens -request e-mailadresse</em>
-# <li><b>owneremail</b> - <em>listens -owner e-mailadresse</em> </ul>
+# In the text fields below, string interpolation is performed with the
+# following key/value substitutions: <p><ul> <li><b>listname</b> -
+# <em>gets the name of the mailing list</em> <li><b>listurl</b> -
+# <em>gets the list's listinfo URL</em> <li><b>requestemail</b> -
+# <em>gets the list's -request address</em> <li><b>owneremail</b> -
+# <em>gets the list's -owner address</em> </ul>
 # 
-# <p>Du kan enten skrive teksten direkte i tekstboksene, eller du kan
-# angive navnet p&aring; en fil som indeholder teksten. Denne fil vil
-# s&aring; blive indl&aelig;st i tekstboksen, fra dit lokale filsystem.
+# <p>For each text field, you can either enter the text directly into
+# the text box, or you can specify a file on your local system to upload
+# as the text.
 
-# Skal Mailman sende et automatisk svar til dem der sender e-mail til
-# listen?
+# Should Mailman send an auto-response to mailing list posters?
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 autorespond_postings = 0
 
-# Automatisk svar der skal sendes.
+# Auto-response text to send to mailing list posters.
 autoresponse_postings_text = ''
 
-# Skal Mailman sende et automatisk svar p&aring; e-mail der sendes til
-# -owner adressen?
+# Should Mailman send an auto-response to emails sent to the -owner
+# address?
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 autorespond_admin = 0
 
-# Automatisk svar p&aring; e-mail til -owner adressen.
+# Auto-response text to send to -owner emails.
 autoresponse_admin_text = ''
 
-# Skal Mailman sende et automatisk svar p&aring; e-mail der sendes til
-# -request adressen? Hvis du v&aelig;lger ja, kan du ogs&aring;
-# v&aelig;lge om e-mailen der blev sendt til -request adressen skal
-# medtages i det automatiske svar.
+# Should Mailman send an auto-response to emails sent to the -request
+# address?  If you choose yes, decide whether you want Mailman to
+# discard the original email, or forward it on to the system as a normal
+# mail command.
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja, men uden den originale e-mail"
-#    2 = "Ja, og medtag den originale e-mail"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes, w/discard"
+#    2 = "Yes, w/forward"
 autorespond_requests = 0
 
-# Automatisk svar p&aring; e-mail til -request adressen.
+# Auto-response text to send to -request emails.
 autoresponse_request_text = ''
 
-# Antal dage imellem automatisk svar p&aring; e-mail, fra samme
-# afsender, til listen eller til -request/-owner adresserne. S&aelig;t
-# denne v&aelig;rdi til 0 (eller et negativt tal) for at sende
-# automatisk svar hver gang.
+# Number of days between auto-responses to either the mailing list or
+# -request/-owner address from the same poster.  Set to zero (or
+# negative) for no grace period (i.e. auto-respond to every message).
 autoresponse_graceperiod = 90
 
 ## Contentfilter options
 #
-# Regler for indhold i e-mail sendt til listen.
-# 
-# <p>Filtrering af indhold fungerer således: når listen modtager en
-# e-mail og du har beskyttelse med filtrering af indhold aktiveret,
-# sammenlignes først eventuelle vedh&aelig;ftninger med <a
-# href="?VARHELP=contentfilter/filter_mime_types">MIME filtrene</a>.
-# Hvis en vedh&aelig;ftning passer med et af disse filtre, bliver
-# vedh&aelig;ftningen fjernet.
-# 
-# <p>Derefter sammenlignes eventuelle vedh&aelig;ftninger med <a
-# href="?VARHELP=contentfilter/pass_mime_types">gyldige MIME typer</a>,
-# hvis nogen er defineret. Alle vedh&aelig;ftninger som ikke stemmer
-# overens med de angivne MIME typer, bliver fjernet.
-# 
-# <p>Efter filtreringen vil alle tomme <tt>multipart</tt>
-# vedh&aelig;ftninger v&aelig;re fjernet. Hvis selve meddelelsen er helt
-# tom efter denne filtrering, vil meddelelsen blive afvist. Derefter vil
-# enhver <tt>multipart/alternative</tt> vedh&aelig;ftning blive
-# erstattet af den første alternative som ikke er tom.
-# 
-# <p>Til sidst vil alle <tt>text/html</tt> vedh&aelig;ftninger som måtte
-# v&aelig;re tilbage i meddelelsen blive konverteret til
-# <tt>text/plain</tt> hvis <a
-# href="?VARHELP=contentfilter/convert_html_to_plaintext">konverter til
-# ren tekst</a> er sat til og serveren er konfigureret til at tillade
-# sådanne konverteringer.
-
-# Skal Mailman filtrere indhold i e-mail sendt til listen som angivet
-# nedenfor?
-#
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# Policies concerning the content of list traffic.
+# 
+# <p>Content filtering works like this: when a message is received by
+# the list and you have enabled content filtering, the individual
+# attachments are first compared to the <a
+# href="?VARHELP=contentfilter/filter_mime_types">filter types</a>.  If
+# the attachment type matches an entry in the filter types, it is
+# discarded.
+# 
+# <p>Then, if there are <a
+# href="?VARHELP=contentfilter/pass_mime_types">pass types</a> defined,
+# any attachment type that does <em>not</em> match a pass type is also
+# discarded.  If there are no pass types defined, this check is skipped.
+# 
+# <p>After this initial filtering, any <tt>multipart</tt> attachments
+# that are empty are removed.  If the outer message is left empty after
+# this filtering, then the whole message is discarded.
+# 
+# <p> Then, each <tt>multipart/alternative</tt> section will be replaced
+# by just the first alternative that is non-empty after filtering if <a
+# href="?VARHELP=contentfilter/collapse_alternatives"
+# >collapse_alternatives</a> is enabled.
+# 
+# <p>Finally, any <tt>text/html</tt> parts that are left in the message
+# may be converted to <tt>text/plain</tt> if <a
+# href="?VARHELP=contentfilter/convert_html_to_plaintext"
+# >convert_html_to_plaintext</a> is enabled and the site is configured
+# to allow these conversions.
+
+# Should Mailman filter the content of list traffic according to the
+# settings below?
+#
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 filter_content = 0
 
-# Brug denne indstilling til at fjerne vedh&aelig;ftninger der passer
-# til MIME typer. Hver linie skal her indeholde navnet på en MIME
-# type/subtype, f.eks. image/gif. Hvis du ønsker at fjerne alle
-# vedh&aelig;ftninger som har en given hoved MIME type, kan du undlade
-# at angive subtype, f.eks. image.
+# Use this option to remove each message attachment that matches one of
+# these content types.  Each line should contain a string naming a MIME
+# type/subtype, e.g. image/gif.  Leave off the subtype to remove all
+# parts with a matching major content type, e.g. image.
 # 
-# Tomme linier medtages ikke.
+# Blank lines are ignored.
 # 
-# Se også gyldige MIME typer for whitelist af MIME typer.
+# See also <a href="?VARHELP=contentfilter/pass_mime_types"
+# >pass_mime_types for a content type whitelist.
 filter_mime_types = ''
 
-# Brug denne indstilling for at definere hvilke MIME typer der skal være
-# tilladt. Krav og format for filtrering er identisk med MIME filtre.
+# Use this option to remove each message attachment that does not have a
+# matching content type.  Requirements and formats are exactly like <a
+# href="?VARHELP=contentfilter/filter_mime_types" >filter_mime_types.
 # 
-# Bem&aelig;rk: hvis du lægger noget ind her, men ikke angiver
-# multipart, vil ingen e-mail med vedh&aelig;ftninger blive medtaget.
+# Note: if you add entries to this list but don't add multipart to this
+# list, any messages with attachments will be rejected by the pass
+# filter.
 pass_mime_types = """multipart/mixed
 multipart/alternative
 text/plain"""
 
-# Skal Mailman konvertere text/html dele til ren tekst? Denne
-# konvertering vil finde sted efter at MIME filteret har fjernet de
-# uønskede dele.
+# Remove message attachments that have a matching filename extension.
+filter_filename_extensions = """exe
+bat
+cmd
+com
+pif
+scr
+vbs
+cpl"""
+
+# Remove message attachments that don't have a matching filename
+# extension.  Leave this field blank to skip this filter test.
+pass_filename_extensions = ''
+
+# Should Mailman collapse multipart/alternative to its first part
+# content?
+#
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
+collapse_alternatives = True
+
+# Should Mailman convert text/html parts to plain text?  This conversion
+# happens after MIME attachments have been stripped.
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 convert_html_to_plaintext = 1
 
-# Her bestemmer du hvad der skal ske, når en meddelelse filtreres fra af
-# et filter, altså hvis vedh&aelig;ftningen filtreres fra af MIME
-# filteret, eller en vedh&aelig;ftning ikke har en af de gyldige MIME
-# typer, eller meddelelsen ender med at være tom efter filtrering.
-# 
-# Bemærk at det du vælger her ikke vil ske hvis en meddelelse stadig
-# indeholder noget efter filtrering. Så vil meddelelsen altid blive
-# sendt videre til listen.
-# 
-# Når meddelelsen afvises, skrives Message-ID for den afviste meddelelse
-# til loggen. Når meddelelsen sendes retur eller videresendes til
-# listens ejer, vil en begrundelse altid blive inkluderet i den
-# returmail der sendes til afsenderen. Når meddelelserne skal bevares,
-# gemmes de i et specielt køkatalog på disken, sådan at
-# serveradministrator kan se (og måske gøre noget med) dem, men bliver
-# ellers fjernet. Dette sidste valg er kun tilgængeligt hvis
-# serveradministrator har tilladt det.
-#
-# gyldige værdier:
-#    0 = "Slet"
-#    1 = "Afvis"
-#    2 = "Videresend til Listens Ejer"
-#    3 = "Bevar"
+# One of these actions is taken when the message matches one of the
+# content filtering rules, meaning, the top-level content type matches
+# one of the <a href="?VARHELP=contentfilter/filter_mime_types"
+# >filter_mime_types, or the top-level content type does not match one
+# of the <a href="?VARHELP=contentfilter/pass_mime_types"
+# >pass_mime_types, or if after filtering the subparts of the message,
+# the message ends up empty.
+# 
+# Note this action is not taken if after filtering the message still
+# contains content.  In that case the message is always forwarded on to
+# the list membership.
+# 
+# When messages are discarded, a log entry is written containing the
+# Message-ID of the discarded message.  When messages are rejected or
+# forwarded to the list owner, a reason for the rejection is included in
+# the bounce message to the original author.  When messages are
+# preserved, they are saved in a special queue directory on disk for the
+# site administrator to view (and possibly rescue) but otherwise
+# discarded.  This last option is only available if enabled by the site
+# administrator.
+#
+# legal values are:
+#    0 = "Discard"
+#    1 = "Reject"
+#    2 = "Forward to List Owner"
+#    3 = "Preserve"
 filter_action = 0
 
 ## Topics options
 #
-# Emneord for listen
-
-# Emnefilteret kategoriserer hver e-mail som kommer til listen, efter de
-# regexp-udtryk du skriver nedenfor. Hvis felterne Subject: eller
-# Keywords: i brevhovedet i en mail stemmer overens med et af disse
-# udtryk, bliver mailen placeret under det p&aring;g&aelig;ldende emne.
-# Hvert medlem af listen kan vælge kun at modtage mail der passer til de
-# &oslash;nskede emner. E-mail som ikke h&oslash;rer under noget emne,
-# bliver ikke leveret.
-# 
-# Bem&aeligrk: Dette fungerer kun i normal-modus, ikke i
-# sammendrag-modus.
-# 
-# Indholdet i meddelelsen kan ogs&aring; unders&oslash;ges for Subject:
-# og Keyword: felter, alt efter hvad indstillingen
-# topics_bodylines_limit er sat til.
+# List topic keywords
+
+# The topic filter categorizes each incoming email message according to
+# <a href="http://www.python.org/doc/current/lib/module-re.html">regular
+# expression filters you specify below.  If the message's Subject: or
+# Keywords: header contains a match against a topic filter, the message
+# is logically placed into a topic bucket.  Each user can then choose to
+# only receive messages from the mailing list for a particular topic
+# bucket (or buckets).  Any message not categorized in a topic bucket
+# registered with the user is not delivered to the list.
+# 
+# Note that this feature only works with regular delivery, not digest
+# delivery.
+# 
+# The body of the message can also be optionally scanned for Subject:
+# and Keywords: headers, as specified by the <a
+# href="?VARHELP=topics/topics_bodylines_limit">topics_bodylines_limit
+# configuration variable.
 #
-# gyldige værdier:
-#    0 = "Ikke tilgængeligt"
-#    1 = "Tilgængeligt"
+# legal values are:
+#    0 = "Disabled"
+#    1 = "Enabled"
 topics_enabled = 0
 
-# Her angiver du hvor mange linier af mailens indhold emnefilteret skal
-# gennems&oslash;ge. En s&oslash;gning stopper n&aring;r det antal
-# linier er gennems&oslash;gt, eller n&aring;r den m&oslash;der en linie
-# som ikke ligner et brevhoved-felt. S&aelig;ttes denne v&aelig;rdi til
-# nul (0), vil ingen linier i indholdet blive unders&oslash;gt (dvs. kun
-# Keywords: og Subject: i brevhovedet unders&oslash;ges). S&aelig;ttes
-# denne v&aelig;rdi til et negativt tal, vil alle linier blive
-# unders&oslash;gt frem til den f&oslash;rste linie som ikke ligner et
-# brevhoved-felt.
+# The topic matcher will scan this many lines of the message body
+# looking for topic keyword matches.  Body scanning stops when either
+# this many lines have been looked at, or a non-header-like body line is
+# encountered.  By setting this value to zero, no body lines will be
+# scanned (i.e. only the Keywords: and Subject: headers will be
+# scanned).  By setting this value to a negative number, then all body
+# lines will be scanned until a non-header-like line is encountered.
+# 
 topics_bodylines_limit = 5
 
-# Hvert emneord er faktisk et regexp-udtryk, der sammenlignes med dele
-# af mailen, nemlig felterne Keywords: og Subject: i brevhovedet.
-# Bem&aelig;rk at de f&oslash;rste linier i mailens indhold ogs&aring;
-# kan best&aring; af s&aring;danne "felter", og de kan dermed ogs&aring;
-# blive unders&oslash;gt.
+# Each topic keyword is actually a regular expression, which is matched
+# against certain parts of a mail message, specifically the Keywords:
+# and Subject: message headers. Note that the first few lines of the
+# body of the message can also contain a Keywords: and Subject: "header"
+# on which matching is also performed.
 topics = []
 
diff --git a/mailman/nilsstaerk.members b/mailman/nilsstaerk.members
index b50f4a4..c3f040b 100644
--- a/mailman/nilsstaerk.members
+++ b/mailman/nilsstaerk.members
@@ -1,5 +1,3 @@
-071@4131.org
-6x112467@tiscali.dk
 Ajimenez58@cantv.net
 Alexander.Hattwig@netcologne.de
 Anne.Winton@royalacademy.org.uk
@@ -7,6 +5,7 @@ Bazagramox@hotmail.com
 CRUZMUR@terra.es
 Christiane_Paul@whitney.org
 Clausbjerre@sol.dk
+Dagfinn@dudyginaart.net
 Detroitmona@aol.com
 Diana_Pulling@moma.org
 Dr.Reinhold.Nagel.Praxis@telemed.de
@@ -18,11 +17,14 @@ Heike.Suetter@t-online.de
 Holckworld@get2net.dk
 Houhrparis@aol.com
 Infor@ingerlam.dk
+JUMO@dr.dk
 Jeanette@ag925.se
 Jensina@mpiri.org
 JerrySaltz@aol.com
+Kaare.Lenbroch@pfizer.com
 Kim@baldessari.org
 Koplevb@tiscali.dk
+Lotte.Andersen@steenstrom.com
 Luis_Perez_Oramas@moma.org
 MArzak@guggenheim-bilbao.es
 Mail@peterfunch.com
@@ -30,6 +32,7 @@ Manuel.E.Gonzalez@chase.com
 Marc@dhoye.com
 Maria_Montalva@moma.org
 MarieIrmgard@hotmail.com
+MariesMail@msn.com
 Martina.Weinhart@schirn.de
 Michael_hall@gmx.net
 Michel.ricard@culture.gouv.fr
@@ -43,30 +46,34 @@ Priamo@prodigy.net.mx
 Rathj9@hotmail.com
 RosenblumRb@netscape.net
 Sabine.oelze@onlinehome.de
+SerineMila@hotmail.com
 Stilling@generaldanmark.dk
 Thomas.Knaack@enskilda.dk
 Timhinman@hotmail.com
 Zdenka.Badovinac@mg-lj.si
 aa0email@yahoo.com
+aarestrup@mail.dk
 aaronlevinelaw@aol.com
 abbeloos11@hotmail.com
 abildgaard@dca-cdb.dk
+aboysen@gmail.com
 acolvin2@earthlink.net
 adamjavlatham@hotmail.com
 adammcarr@hotmail.com
 ads2@nyu.edu
-aegidius@dk.ibm.com
-aellegood@nortonfamilyoffice.com
+agosto_leduc@hotmail.com
 ahmedfancy@yahoo.com
 aissadione@arc.sn
 ajimenez@cisneros.com
 akm@herningkunstmuseum.dk
 akr@tdcadsl.dk
+alan_malligsen@hotmail.com
 albergariagabrie@hotmail.com
 alberto03@eresmas.com
 alef@get2net.dk
 alexander_natas@c.dk
 alicegkrok@yahoo.se
+almudenagv@hotmail.com
 alposo@cantv.net
 alvalca@telefonica.net
 alvall@jazfree.com
@@ -86,6 +93,7 @@ andrea@jespersen.co.uk
 andrea@karberg.dk
 andrea@mfs.museum.no
 andrea@mso13.com
+andreas.ligaard@dk.abnamro.com
 andrew@andrewmummery.com
 andrewkreps@rcn.com
 anette.wingaard@skolekom.dk
@@ -97,9 +105,13 @@ anna.holmbom@malmo.se
 anna.maria.lund@get2net.dk
 anna@this.is
 annahermansson@hotmail.com
+anne.karin.jonssen@skat.dk
 anne.kielgast@mail.dk
 anne@senstad.com
+anne@yellowpencil.dk
+anne_oetbygaard@yahoo.com
 annebirte@artlink.no
+annesofie@wonderland-mag.dk
 annickb@altern.org
 annlumbye@mail.dk
 annuke@m3.stud.ku.dk
@@ -113,10 +125,13 @@ art.stpdal@mail.tele.dk
 art@artpublic.ch
 art@birgittelund.com
 artbox@hol.gr
+artcarproject06@yahoo.co.uk
+artcarproject@yahoo.co.uk
 artiskok@webspeed.dk
 artluv6@aol.com
 artopia_net@yahoo.com
 artpublic@hotmail.com
+artqueendk@hotmail.com
 asa.nacking@rooseum.se
 asa.nacking@swipnet.se
 asc@bruun-rasmussen.dk
@@ -136,17 +151,27 @@ batkin@bard.edu
 baungaard@mail.dk
 bcn2022@hotmail.com
 bcr2022@hotmail.com
+bejerholm.madsen@yahoo.dk
 bellet@lemonde.fr
+bendixen@contemporary-art.dk
 benmonga@yahoo.fr
 benteelisabeth@private.dk
 berlin@nordenhake.com
 bert@transit.be
 berta.sichel@cars.mcu.es
 betbang@tele2adsl.dk
+betinastrange@hotmail.com
 bgrenvil@vanartgallery.bc.ca
+bholmand@yahoo.no
+bhu@horsenshs.dk
 birgittalund@get2net.dk
 birgitteanderberg@mail.tele.dk
+birte@dobag.dk
 bitsch@tdcadsl.dk
+bj@byraadgivning.dk
+bjarnesorensen@mail.dk
+bkoelle@freenet.de
+bmdepero@hotmail.com
 bob@bobvanorsouw.ch
 bobokrabbe@hotmail.com
 bodild@dragoer.dk
@@ -158,8 +183,8 @@ brammer@os.dk
 bryggebladet@mail.dk
 bs@najalauf.dk
 bs@najaluf.dk
+bs@opiumome.com
 bt@danx.dk
-c.asprey1@ntlworld.com
 c.elgiz@tnn.net
 c_taplin@bellsouth.net
 cabs@dr.dk
@@ -171,10 +196,13 @@ camouflage@skynet.be
 can@kb.dk
 capsengirl@hotmail.com
 carinajohnsen@hotmail.com
+carla@dbmail.dk
 carlazaccagnini@yahoo.com.br
 carlchristian@jacc.dk
 carlesguerra@hotmail.com
 carlsonsarah81@hotmail.com
+carolinejepsen@mail.dk
+carolk@slam.org
 carstenhall@go.com
 cascino6@hotmail.com
 catertoart@aol.com
@@ -182,6 +210,7 @@ cb@nordeuropa.nu
 cba@vestkunst.dk
 cbasualdo@aol.com
 cbecker@artic.edu
+cc@carlachristine.com
 ceamon@frequencylabs.com
 cecid@bway.net
 cecilia.pereira.marimon@xunta.es
@@ -190,13 +219,15 @@ cemetiah@indosat.net.id
 ceo@thymann.com
 cffm@novonordisk.com
 cgarrido.fundacio@lacaixa.es
+chah@ke.dk
 charlotte.o@wanadoo.dk
 charlotte.s@smk.dk
 charlotte.smidt@bane.dk
-charlotte.sprogoe@mail.dk
+charlotte.sprogoe@gmail.com
 charlotte.thiis.evensen@nrk.no
 charlotte@charlottenborg-art.dk
 charlotte@fjeldal.dk
+charlotte@trippetti.dk
 charlotteboudon@hotmail.com
 charlottekrenk@hotmail.com
 charlottmarkus@mail.com
@@ -206,14 +237,17 @@ christa@charlottenborg-art.dk
 christel_tillisch@tdcadsl.dk
 christian.damgaard@gmail.com
 christian@farmfreshfilms.com
+christian@goecker.dk
 christian@skovbjerg.com
 christina@helvad.dk
 christine.maes@gent.be
 christine@etnahem.com
 christineclemmesen@hotmail.com
 christoph.ruys@belgacom.net
+chus@fkv.de
 cjalving@hum.ku.dk
 cjennow@hotmail.com
+ck@kirk-ejendomme.dk
 clairecanning@tankmagazine.com
 clau0111@hotmail.com
 claus.carstensen@pc.dk
@@ -224,6 +258,7 @@ cmedin@yahoo.com
 columnadearena@hotmail.com
 comp@dr.dk
 contact@meyerkainer.at
+contact@npgallery.com
 contact@paulknight.com.au
 contact@photography-now.com
 cooperhall@aol.com
@@ -243,6 +278,7 @@ dangermouse1@earthlink.net
 danpty@fastwebnet.it
 daross222@earthlink.net
 david@dlg-gallery.com
+david_grimberg@hotmail.com
 davisof@get2net.dk
 db@damonbrandt.com
 db@dorisbloom.dk
@@ -268,8 +304,10 @@ dmc@scanvaegt.dk
 dogenhaus@aol.com
 donrubell@rubellhotels.com
 doritma@t0.or.at
+dorte.mosbaek@bobedre.dk
 dorte@nilsstaerk.dk
 dortehb@yahoo.dk
+dorthe.abildgaard@andelsmail.dk
 dotkorn@gone.dk
 dplaton@brandeis.edu
 dr_ravn@hotmail.com
@@ -277,6 +315,7 @@ duncann44@hotmail.com
 dv@tdc.dk
 dvir_g@inter.net.il
 e-post@wanas.se
+e.ralickas@parachute.ca
 e@katyasander.net
 eafrandsen@os.dk
 earmstrong@ocma.net
@@ -285,6 +324,7 @@ ebbe_stub@hotmail.com
 edegnemark@hotmail.com
 edicionesplanb@prodigy.net.mx
 edith@lacoleccionjumex.org
+editor@artknowledgenews.com
 editor@indexmagazine.com
 eduardoabrantes@gmail.com
 ef@djh.dk
@@ -306,9 +346,11 @@ elbab@retemail.es
 eleni.x@eudoramail.com
 elf.langsted@get2net.dk
 elg@mail.tele.dk
+elg@v1gallery.com
 elisabeth.byre@chello.no
 elisabeth.harmitt@oamp.fr
 els@hanappe.com
+elsa@ennemm.is
 email@stereobar.dk
 emif@micronet.it
 emma.lequeux@free.fr
@@ -332,6 +374,7 @@ ferariarte@tin.it
 ferdinand@muter.dk
 fff@fotogalleriet.no
 fietanderup@hotmail.com
+finin@finin.dk
 finn.agger@private.dk
 finnbogi@finnbogi.com
 finnbrod@khio.no
@@ -383,10 +426,13 @@ giannimercurio@libero.it
 gimm@gimm-eis.com
 ginatornatore@btinternet.com
 gitte.tjellesen@skolekom.dk
+gittemads@hotmail.com
 gitteoglars@get2net.dk
 gkridisser@animabrasiliae.com
 glinder@tiscali.net
+gmc682002@yahoo.com.mx
 gny@dav.egmont.com
+goran.aldvik@sas.se
 gorm@mbox301.get2net.dk
 goski@sol.dk
 gr@postmedia.net
@@ -409,6 +455,7 @@ hanuta77@hotmail.com
 hb@emerge.dk
 heide.kramer@basis-wien.at
 heike.munder@mgb.ch
+helena_skau@yahoo.com
 helene.mustad@artlink.no
 helga-marie@nordby.to
 helle-peter@get2net.dk
@@ -419,7 +466,9 @@ henar@helgadealvear.net
 henbie@hotmail.com
 hennadeluxe@cool.dk
 henningschultz@hotmail.com
+henrik@nordenlund.dk
 henrik@norholt.dk
+henrikeiben@hotmail.com
 henrikorlanielsen@yahoo.dk
 hh@brandeddesign.dk
 hhf@city.dk
@@ -430,18 +479,24 @@ hlaura@hum.ku.dk
 hnr@codan.dk
 hoffmann@sophie-gips.de
 holgerf@dk.ibm.com
+holzherr@magnumphotos.fr
+honkyparker@earthlink.net
 honor@gagosian.com
 horst.koehn@wienkav.at
 hotlot1@hotmail.com
+hpo@bredalsparken.dk
+hst@plesner.com
 hughiebb@aol.com
 ibp@berlingske.dk
 idak@fotogalleriet.no
+idasuhr@hotmail.com
 idaunsgaard@hotmail.com
 ihansen@ingridhansengallery.com
 ij@dlf.org
 info@annetgelink.com
 info@apexart.org
 info@arsfutura.com
+info@art-review.co.uk
 info@artagents.de
 info@artecontexto.com
 info@cca-glasgow.com
@@ -453,9 +508,11 @@ info@galleriafrancescakaufmann.com
 info@galleriasogospatty.com
 info@gallericharlottelund.com
 info@galleriflach.com
+info@gertgermeraad.nl
 info@giomarconi.com
 info@hammersidi.com
 info@i8.is
+info@isabelcarafi.it
 info@kug.dk
 info@kulstrunk.ch
 info@marcovigo.com
@@ -465,6 +522,7 @@ info@mobilehomegallery.com
 info@modernartinc.com
 info@nicolafornello.com
 info@outlook.gr
+info@pashaparts.dk
 info@patrickseguin.com
 info@rubin-stuk.dk
 info@soniarosso.com
@@ -472,10 +530,12 @@ info@suite106.com
 info@thetownhousegallery.com
 info@trondhugo.no
 info@uks.no
+info@wdw.nl
 infocav@cav.net4b.pt
 infos@jousse-enterprise.com
 ingeborg@shinegallery.co.uk
 irinairina@hotmail.com
+ivarivar@internet.is
 izumi@yahoo.it
 j.skjoldborg@mail.dk
 jacobfabricius@wanadoo.dk
@@ -488,6 +548,7 @@ jakob_witt@hotmail.com
 jakobjakobsen@adr.dk
 jakobjensen@gmx.net
 jalvaer@yahoo.com
+jan.petter.allan@nordea.com
 jan_b_christensen@yahoo.com
 jandol@get2net.dk
 jane.burton@tate.org.uk
@@ -508,6 +569,7 @@ jeppehein@web.de
 jer@kb.dk
 jesper@artaround.com
 jesper@nilsstaerk.dk
+jesperlindhardt@hotmail.com
 jf@spacepoetry.dk
 jfdr@eresmas.net
 jhanhardt@earthlink.net
@@ -518,17 +580,21 @@ jlindegaard1@hotmail.com
 jlmoraza@arrakis.es
 jlomax@ocma.net
 jlouey@mac.com
+jm@copearch.com
+jm@skibsted.net
 jmanuel.bonet@cars.mcu.es
-jnj@tdc.dk
 joachim@kattrup.com
+joakim.borda-p@brfcirkeln.se
 jock@san.rr.com
 joel@interimart.net
 johann@circleculture.com
 john@baldessari.org
+jonatanbakkelund@hotmail.com
 jone@kvie.nu
 jonekvie@telia.com
 jonfp@mail1.stofanet.dk
 jose@kurzimanzutto.com
+josephine.ernst@nerv.dk
 jphol@hotmail.com
 jputnam@british-museum.ac.uk
 jrocaaco@banrep.gov.co
@@ -539,20 +605,25 @@ juanmartinprada@w3art.es
 judelson@i-20.com
 judith.quentel@fracdespaysdelaloie.com
 julie.damgaard@tdcadsl.dk
+julie@artpartner.se
 julielb@mac.com
 julieta68@bellsouth.net
 julieta68@yahoo.com
+junedi@m4.stud.ku.dk
 just@planet-save.com
 jvaliaga@hotmail.com
 jw@cphid.dk
 k.bjerrekaer@oncable.dk
+kaholo@web.de
 kaj.nyborg.isoplant@teliamail.dk
 kaldender@kopenhagen.dk
 kantorart@earthlink.net
 karaoke@karaoke.dk
 karen.lohrmann@berlin.de
+karla-andersen@jubii.dk
 karro_p@hotmail.com
 kasparoppen@yahoo.com
+kasper@kaspersonne.com
 kasper@pp.dk
 katalog@brandts.dk
 katerinagregos@hotmail.com
@@ -561,43 +632,49 @@ katie.boucher@chisenhale.org.uk
 katja@casa.as
 katja@it-c.dk
 katja@pp.dk
-kayxmellish@yahoo.com
+katrinostlundh@hotmail.com
 kb@dynaudio.dk
 kea@post5.tele.dk
+keikocakemaker@hotmail.com
 keli.esja@wanadoo.nl
+kelly@contemporary-art.dk
 kellykyst@hotmail.com
 kerstin.knepper@tate.org.uk
 kf@kunstforeningen.dk
-kim@hueg.dk
 kim@kbvin.com
 kim@ndreasen.private.as
 kipo@kipo.dk
 kirse.junge-stevnsborg@helsingborg.se
 kirsi.vakiparta@av-arkki.fi
 kirsten.mathiesen@jp.dk
+kissutaffere@gmail.com
 kjelman@online.no
 kkanatani@guggenheim.org
 kkern@worldonline.dk
 kkr@codan.dk
 kkuramitsu@nortonfamilyoffice.com
+kobenhavn@avisen.dk
 koenig@museum-ludwig.de
 kokkin@kpa.no
 kolovskaya@proarte.ru
 konjitseyoum@hotmail.com
 konstpap@hol.gr
 kopenhagen@kopenhagen.dk
+kp@colliers.dk
 krag_egemose@email.dk
+krge@nykredit.dk
 krisni77@hotmail.com
 kristian@online.no
 kristinask@gmx.net
+kristinesundahl@gmail.com
 kristoferpaetau@web.de
 krueger@rpi.edu
 ks@kunststyrelsen.dk
 kthejll@image.dk
+kub@cfmoller.com
 kultur@dr.dk
 kunst.kultur@borsen.dk
-kunst@listserv.hum.ku.dk
-kystol@hotmail.com
+kunst@citadellet.dk
 l.jakob@mail.dk
 la@livingarch.com
 laneeley@adelphia.net
@@ -605,6 +682,8 @@ laneeley@mac.com
 lar@ntadvokater.dk
 lars.nilsson@khm.lu.se
 lars@textkontor.dk
+larsbanglarsen@yahoo.com
+laura@laurastamer.dk
 lauraskoler@aol.com
 le@erhvervsraadet.dk
 leeagibstein@yahoo.com
@@ -615,22 +694,29 @@ leif_M_Tangen@yahoo.no
 lemans@vmw.nl
 lemmerz@wake.dk
 lenbroch@12move.dk
+lenbroch@kruhoeffer.dk
 lengel@ifi.ku.dk
 leopar@tin.it
+letters@art-review.co.uk
 lh@fs.dk
 li@pol.dk
 liamgillick@compuserve.com
 lieberaxel@telia.com
+liekewijnia@hotmail.com
 liliana@swipnet.se
 line.jannik@elvis.dk
 line.rosenvinge@mail.dk
 line.voutsinos@privat.dk
 linetindkristensen@hotmail.com
 linus.voncastelmur@cop.rep.admin.ch
+lis@aarestrup-vind.dk
 lis@kunde.dk
+lisa@hollybushgardens.co.uk
 lisa_flood_@hotmail.com
 lisbet.berg@hotmail.com
+lise.garsdal@pol.dk
 liseharlev@gmx.net
+liseskou@tele2adsl.dk
 lisette_ve@hotmail.com
 lisjan@webspeed.dk
 listen@listen.no
@@ -640,6 +726,7 @@ liz@pennymccallfoundation.org
 llagnado@nw.com.br
 lmiller@fluentcollab.org
 lone@jones.dk
+lone@nilsstaerk.dk
 lonedan@centrum.dk
 lorena110577@yahoo.es
 lose@postman.dk
@@ -647,7 +734,6 @@ lotte.n@dgmedia.dk
 lottenburger@worldonline.dk
 lottepe@m3.stud.ku.dk
 lphillips@newmuseum.org
-lst@arkmail.dk
 luchal@iol.it
 luisa@franconoero.com
 luisahedo@telefonica.net
@@ -655,11 +741,14 @@ lutzachill@gmx.de
 lwaters@berkeleyrep.org
 lzippay@eai.org
 m.gestsson@ntlworld.com
+m.grive@00tal.com
 m.kataoka@mori.art.museum
 m.knop@mail.dk
 m.m.basilio@att.net
 maaretta.jaukkuri@kit.ntnu.no
+madeleine.malmsten@lund.se
 madista@mail.dk
+mads.eskesen@gmail.com
 mads@dadlnet.dk
 madsen@where2go.dk
 magdacurator@yahoo.com
@@ -680,7 +769,9 @@ mail@themoderninstitute.com
 mail@thomasandersen.dk
 mailkim@kimsmai.com
 maillistetest@nilsstaerk.dk
+mailme@timmimensah.com
 maj.allin@austrade.gov.au
+majaschou@yahoo.com
 majbritt.loeland@privat.dk
 malene.landgreen@get2net.dk
 malene.severinsen@borsen.dk
@@ -691,6 +782,8 @@ mancus@volny.cz
 mangerman@hotmail.com
 manucerda@hotmail.com
 map@pls.dk
+marc-olivier.wahler@palaisdetokyo.com
+margrit.brehm@gmx.net
 margrit.brehm@museumdermoderne.at
 mari.s@online.no
 mari.shaw@obermayer.com
@@ -706,9 +799,11 @@ mark.oedum@tietoenator.com
 marlene-ninabeth-skouboe@mail.dk
 martin.schwander@bluewin.ch
 martin@drdante.dk
+martinmalte.blumenthal@axa-art.de
 maryann@insite2000.org
 marywafer@postmaster.co.uk
 matcook@matcook.homechoice.co.uk
+matf@nykredit.dk
 mathias_seeberg@hotmail.com
 mats.eriksson@brevet.nu
 matthew@frieze.com
@@ -722,10 +817,13 @@ meraso@kultura.gipuzkoa.net
 mestrom@mindspring.com
 mette@aok.dk
 mette@skjoedt.com
+mfa@georgjensen.com
 mfm@berlingske.dk
 mia@fryland.org
+mia@schoneck.dk
 michaelbach@wanadoo.es
 michaelrooks@earthlink.net
+michele@contemporary-magazine.com
 mikael.petersen@barclayscapital.com
 mikeskovgaard@hotmail.com
 milovanfarronato@hotmail.com
@@ -740,11 +838,11 @@ mollefc@hotmail.com
 monica@gjesdal.larsen.ms
 morelllars@hotmail.com
 morten.boye@get2net.dk
+morten@straede.net
 mortenkirk9@hotmail.com
 mortenvammen@gmail.com
 mosholt@mail.dk
 mosvold@kool.no
-mow@swissinstitute.net
 mponsa.fundacio@lacaixa.es
 mrooks@tcmhi.org
 mrush@palmbeachica.org
@@ -756,10 +854,12 @@ nadja@reflexioner.org
 napoleo@iname.com
 nathalie.oliveira@culture.gouv.fr
 nce@concorde-us.com
+news@flashartonline.com
 nextsaturday@yahoo.com
 nicmed@yahoo.com
 niels@kantorfeuer.com
 niklas@vonbartha.com
+nilausen@image.dk
 nils@drylab.no
 nils@nilsfriedman.com
 nils@nilsstaerk.dk
@@ -775,9 +875,11 @@ nourbakhsch@t-online.de
 nsc@ddc.dk
 nstrands@online.no
 nw@nicolaiwallner.com
+obr@pro-ventilation.dk
 ockenholt@wanadoo.dk
 ofa@3falke.dk
 office@brandstromstene.se
+office@galeriemichaeljanssen.de
 office@klosterfelde.de
 office@nu-e.nu
 office@schipper-krome.com
@@ -786,6 +888,7 @@ ohs@mail.dk
 oldorp@xs4all.nl
 oldspice90@hotmail.com
 ole_bundgaard@ofir.dk
+ondfod@hotmail.com
 orandi@skill.com.br
 orkr@dr.dk
 orod1313@hotmail.com
@@ -818,6 +921,7 @@ pernillegrane@aol.com
 peter.friis@mercuriurval.com
 peter.rohleder@lavandoo.com
 peter@alpgallery.com
+peter@fario.dk
 peter@lind-damkjaer.dk
 petercallesen@yahoo.com
 peterdoroshenko@mac.com
@@ -834,6 +938,7 @@ philip.nelson@galerie-nelson.com
 photo@artists.fi
 pia.kristoffersson@chello.se
 piras.michelle@libero.it
+pivedyr@hotmail.com
 pjs1001@cam.ac.uk
 pk2073@columbia.edu
 pl@grey.dk
@@ -842,27 +947,34 @@ plh@framfab.dk
 pm154@columbia.edu
 pmacalau@harbourfront.on.ca
 pmartin@lacoleccionjumex.org
+pmeyer69@bluewin.ch
 polydoros@artrace.com
 pontus.kyander@svt.se
 pontusky@yahoo.se
 post@byogbolig.com
 post@ffkd.dk
+post@fkv.de
 post@larsmonradvaage.com
 pr@rosendahls.dk
 pr@silkeborg-gym.dk
 prcact@hol.gr
 press@outlook.gr
+presse@kultunaut.dk
 pressrelease@undo.net
 prh6@neosoft.com
 pri@svane.com
+prinz@vitaminb.de
 programme@balticmill.com
 ps@kunstforeningen.dk
 pschou@post7.tele.dk
 pst@eb.dk
+pt@annahelwinggallery.com
 ptsh@dadlnet.dk
 ptst@dadlnet.dk
 pwamby@yahoo.dk
+r-dahl@post.tele.dk
 r01sbp@af-dk.dk
+raaa@stofanet.dk
 ramon.esparza@euskalnet.net
 ratio3@mac.com
 raucciesantamaria@interfree.it
@@ -870,11 +982,14 @@ raymoon@niew.nl
 rbasha@tfaa.org
 rcembalest@artnewsonline.com
 rebeca@noguerasblanchard.com
+rebeccawilson@art-review.co.uk
 redaktion@bryggebladet.dk
 redaktion@lettre.dk
 redaktion@oxygenavis.dk
+redaktor@paletten.tk
 reginebasha@hotmail.com
 regkunst@uol.com.br
+renee@varaart.com
 reviews@frieze.com
 reyna@mail.utexas.edu
 rhill@guggenheim.org
@@ -907,6 +1022,7 @@ rperea@ipn.mx
 rromero@cisneros.com
 rspeyer@tishmanspeyer.com
 rthorisson@yahoo.com
+ruchill@ima-art.org
 rui@ard-system.com
 rwasko@muzart.infocentrum.com
 s.win@tdcadsl.dk
@@ -923,6 +1039,7 @@ schachter@mindspring.com
 schivara@mcachicago.org
 scuesta@w3art.es
 scully@scully.dk
+sec@surfmail.dk
 sedrul@grn.es
 seeart@pacbell.net
 sehsan@web.de
@@ -932,6 +1049,7 @@ sevgiz@ttnet.net.tr
 sfk.sebastian.deisen@t-online.de
 shannon.fitzgerald@contemporarystl.org
 shirley_suki_1981@yahoo.com.hk
+siesbye@cirque.dk
 signal.galleri@swipnet.se
 signe@storstein.dk
 signen@tiscali.dk
@@ -950,8 +1068,10 @@ smarchan@fsof.uned.es
 snozke@hotmail.com
 snutarm@hotmail.com
 soerensiggaard@yahoo.dk
+sofia-l@algonet.se
 sofiethorsen@web.de
 sonia@colors.it
+sonia@flashartonline.com
 sophienholm@sophienholm.dk
 sophiepucill@hotmail.com
 soren@hjerrildnielsen.dk
@@ -967,18 +1087,22 @@ stellasig70@hotmail.com
 sten.faerch.jensen@bryggemail.dk
 stenka@fald.dk
 stephan.granhaug@schibsted.no
-steve.wilson@chevrontexaco.com
 stf913@hotmail.com
 stmiller@hiwaay.net
 straede@vip.cybercity.dk
 strousa@yahoo.com
 studio@realitymodels.org
+sub@in2media.dk
+submit@linkup-cph.dk
+surely2986@nilsstaerk.dk
 sus.petersen@oncable.dk
+susan@eyemazing.com
 susgre@sol.dk
 sylvie_betard@hotmail.com
 sylviebetard@noos.fr
 t.gammelgaard@mail.dk
 t.nagano@mori.art.museum
+taxholm@lite.dk
 tb@eventforce.dk
 tbeck@mobilixnet.dk
 tbrugera@cubarte.cult.cu
@@ -986,6 +1110,7 @@ tbruguera@aol.com
 tchiarelli@uol.com.br
 tdy@novo.dk
 tellmemore@theshowroom.org
+teocohen@yahoo.com.mx
 teraqueiroz@hotmail.com
 terje@sandengen.dk
 theiscapion@yahoo.com
@@ -993,6 +1118,7 @@ therese12@hotmail.com
 thomas.locher@t-online.de
 thomas.miessgang@kunsthallewien.at
 thomas@ovlisen.com
+thomas_ogard@yahoo.com
 thyrahilden@hotmail.com
 tiloschulz@hotmail.com
 tim@voldsted.dk
@@ -1002,9 +1128,12 @@ tmch@mail.dk
 tmh@psglaw.dk
 toni@bigmagazine.com
 toqster@excite.com
+tor@radioman.se
 tore-bahnson@mobilixnet.dk
+torpjens@mail.dk
 torrente63@telefonica.net
 tow@berlingske.dk
+toy@homebase.dk
 tra@budweg.com
 trine@isness.org
 trine@paintbox.dk
@@ -1016,6 +1145,7 @@ truls@diplomatique.net
 tsn@le34.dk
 tsultan@uh.edu
 tyapelli@mail.sdsu.edu
+tyler.coburn@gmail.com
 u@thomsen.mail.dk
 u_fredriksson@hotmail.com
 ube@neg-micon.dk
@@ -1034,6 +1164,7 @@ vesna@arts.ucla.edu
 vibweb@yahoo.no
 vicmir@dircon.co.uk
 victor@re-public.com
+victorstilling@gmail.com
 viero@muvi.dk
 vitaminabc@mail.com
 vnoorthoorn@hotmail.com
@@ -1047,7 +1178,6 @@ wlam@cubarte.cult.cu
 wstover@newmuseum.org
 wwoon@mcachicago.org
 wyckhuys@hotmail.com
-xmel@xmel.com
 yamatomichael@earthlink.net
 ysg@nyc.rr.com
 zach@kantorfeuer.com
diff --git a/mailman/nilsstaerk.py b/mailman/nilsstaerk.py
index 56016b9..c958d1b 100644
--- a/mailman/nilsstaerk.py
+++ b/mailman/nilsstaerk.py
@@ -1,382 +1,369 @@
-## Indstillinger for maillisten "nilsstaerk"  -*- python -*-
-## Dato: Sun Dec 11 16:36:03 2005
+# -*- python -*-
+# -*- coding: us-ascii -*-
+## "nilsstaerk" mailing list configuration settings
+## captured on Tue Dec  5 15:21:15 2006
 
 ## General options
 #
-# Grundlæggende egenskaber for listen, herunder en beskrivelse af
-# listen. 
-
-# Du kan f.eks. stave navnet med stort forbogstav eller ændre andre
-# bogstaver til store, s&aring; navnet bliver udtalt rigtigt eller at
-# forkortelser fremhæves. Bemærk at dette navn bruges i e-maillistens
-# adresse (f.eks. i bekræftelser ved tilmeldinger), s&aring; navnet kan
-# ikke ændres p&aring; nogen anden m&aring;de. (e-mailadresser er ikke
-# f&oslash;lsomme for store eller sm&aring; bogstaver, men de er
-# f&oslash;lsomme for n&aelig;sten alt andet :-)
+# Fundamental list characteristics, including descriptive info and basic
+# behaviors.
+
+# The capitalization of this name can be changed to make it presentable
+# in polite company as a proper noun, or to make an acronym part all
+# upper case, etc.  However, the name will be advertised as the email
+# address (e.g., in subscribe confirmation notices), so it should not be
+# otherwise altered.  (Email addresses are not case sensitive, but they
+# are sensitive to almost everything else :-)
 real_name = 'NilsStaerk'
 
-# Der er to roller forbundet med hver mailliste. Listeadministratorerne
-# er dem der som sidste instans har kontrol over alle indstillingerne
-# for maillisten. De kan &aelig;ndre alle indstillinger der er
-# tilg&aelig;ngelige via disse administrative websider.
-# 
-# Listemoderatorerne har begrænset adgang; de kan ikke ændre
-# indstillinger for e-maillisten, men de kan tage sig af anmodninger i
-# forbindelse med listen, f.eks. anmodning om medlemskab, eller
-# godkende/afvise meddelelser der skal godkendes for at kunne udsendes
-# til listen. Listeadministratorerne kan ogs&aring; udf&oslash;re disse
-# opgaver.
-# 
-# For at aktivere muligheden for at have listemoderatorer, og p&aring;
-# den m&aring;de fordele arbejdsopgaverne i forbindelse med listen, skal
-# du anf&oslash;re din egen moderatoradgangskode, og angive
-# e-mailadresser for den/dem som skal v&aelig;re listemoderator(er).
-# Bemærk at i tekstboksene nedenfor skal du skrive e-mailadresser for
-# listeadministratorer.
+# There are two ownership roles associated with each mailing list.  The
+# list administrators are the people who have ultimate control over all
+# parameters of this mailing list.  They are able to change any list
+# configuration variable available through these administration web
+# pages.
+# 
+# The list moderators have more limited permissions; they are not able
+# to change any list configuration variable, but they are allowed to
+# tend to pending administration requests, including approving or
+# rejecting held subscription requests, and disposing of held postings.
+# Of course, the list administrators can also tend to pending requests.
+# 
+# In order to split the list ownership duties into administrators and
+# moderators, you must set a separate moderator password, and also
+# provide the email addresses of the list moderators.  Note that the
+# field you are changing here specifies the list administrators.
 owner = ['nils@nilsstaerk.dk']
 
-# Der er to ejer-roller forbundet med hver mailliste.
-# Listeadministratorerne er dem der har den endelige kontrol over alle
-# indstillingerne for e-mallisten. De kan &aelig;ndre alle indstillinger
-# der er tilgængelige via disse administrative websider.
-# 
-# Listemoderatorerne har begr&aelig;nset adgang; de kan ikke &aelig;ndre
-# indstillinger for e-maillisten, men de kan tage sig af anmodninger
-# ang&aring;ende listen, f.eks. anmodning om medlemskab, eller
-# godkende/afvise meddelelser der skal godkendes for at kunne udsendes
-# p&aring; listen. Listeadministratorerne kan selvsagt ogs&aring;
-# udf&oslash;re disse opgaver.
-# 
-# For at aktivere muligheden for at have listemoderatorer, og p&aring;
-# den m&aring;de fordele arbejdsopgaverne i forbindelse med listen, skal
-# du anf&oslash;re din egen moderatoradgangskode, og indtaste
-# e-mailadresser for den/dem der skal v&aelig;re listemoderatore(r).
-# Bemærk, at i tekstboksene nedenfor skal du skrive listemoderator
-# e-mailadresse(r).
+# There are two ownership roles associated with each mailing list.  The
+# list administrators are the people who have ultimate control over all
+# parameters of this mailing list.  They are able to change any list
+# configuration variable available through these administration web
+# pages.
+# 
+# The list moderators have more limited permissions; they are not able
+# to change any list configuration variable, but they are allowed to
+# tend to pending administration requests, including approving or
+# rejecting held subscription requests, and disposing of held postings.
+# Of course, the list administrators can also tend to pending requests.
+# 
+# In order to split the list ownership duties into administrators and
+# moderators, you must set a separate moderator password, and also
+# provide the email addresses of the list moderators in this section.
+# Note that the field you are changing here specifies the list
+# moderators.
 moderator = []
 
-# Denne beskrivelse benyttes n&aring;r denne malliste listes op sammen
-# med andre maillister, i toptekster, osv. Den b&oslash;r v&aelig;re
-# s&aring; kort som overhovedet mulig, uden at det bliver uklart hvad
-# meningen med maillisten er eller hvad den skal bruges til.
+# This description is used when the mailing list is listed with other
+# mailing lists, or in headers, and so forth.  It should be as succinct
+# as you can get it, while still identifying what the list is.
 description = 'Info regarding Nils Staerk'
 
-# Teksten tolkes som html bortset fra linieskift, der vil blive
-# &aelig;ndret til html-tag'et '<br>', sådan at du kan benytte links,
-# forh&aring;ndsformateret tekst, osv. Men brug alts&aring; kun
-# linieskift der hvor du vil have et nyt afsnit. V&aelig;r meget
-# omhyggelig, hvis du benytter html-kode. Fejl (f.eks. manglende
-# slut-tag's) kan f&oslash;re til at listens informationsside ikke
-# bliver vist s&aring;dan som den skal.
+# The text will be treated as html except that newlines will be
+# translated to <br> - so you can use links, preformatted text, etc, but
+# don't put in carriage returns except where you mean to separate
+# paragraphs.  And review your changes - bad html (like some
+# unterminated HTML constructs) can prevent display of the entire
+# listinfo page.
 info = ''
 
 # This text will be prepended to subject lines of messages posted to the
-# list, to distinguish mailing list messages in in mailbox summaries.
+# list, to distinguish mailing list messages in mailbox summaries.
 # Brevity is premium here, it's ok to shorten long mailing list names to
 # something more concise, as long as it still identifies the mailing
-# list.
+# list. You can also add a sequential number by %d substitution
+# directive. eg.; [listname %d] -> [listname 123] (listname %05d) ->
+# (listname 00123)
+# 
 subject_prefix = '[Nilsstaerk] '
 
-# Skjul afsenderen af meddelelser, ved at erstatte den med e-maillistens
-# adresse (Dette medfører at alle From:, Sender, og Reply-To: felter
-# fjernes)
+# Hide the sender of a message, replacing it with the list address
+# (Removes From, Sender and Reply-To fields)
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 anonymous_list = 0
 
-# Skal eksisterende Reply-To: felt i brevhovedet fjernes? Hvis ja, vil
-# dette blive gjort uanset om Mailman tilføjer et Reply-To: felt eller
-# ikke.
+# Should any existing Reply-To: header found in the original message be
+# stripped?  If so, this will be done regardless of whether an explict
+# Reply-To: header is added by Mailman or not.
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 first_strip_reply_to = 0
 
-# Denne indstillling fort&aelig;ller hvad Mailman skal g&oslash;re med
-# Reply-To: feltet i brevhovedet p&aring; e-mail der sendes til listen.
-# Hvis den er sat til Afsender, vil Mailman ikke tilf&oslash;je noget
-# Reply-To: felt, men findes et s&aring;dant felt allerede, vil det ikke
-# blive fjernet. S&aelig;ttes indstillingen til enten e-maillistens
-# adresse eller Egendefineret adresse, vil Mailman tilf&oslash;je, evt.
-# erstatte, et Reply-To: felt. (Egendefineret adresse inds&aelig;tter
-# v&aelig;rdien af indstillingen reply_to_address).
-# 
-# Der er flere grunde til ikke at indf&oslash;re eller erstatte
-# Reply-To: felter. En grund kan v&aelig;re at nogen af dem der sender
-# mail til listen er afh&aelig;ngige af selv at kunne s&aelig;tte
-# Reply-To: adressen. En anden grund er at modifikation af Reply-To:
-# adressen g&oslash;r det vanskeligere kun at sende svar til afsender.
-# Se 'Reply-To' Munging Considered Harmful for en diskussion omkring
-# emnet. Se Reply-To Munging Considered Useful for modsatte meninger.
-# 
-# Nogle maillister har begr&aelig;nset adgang, med en parallel liste
-# beregnet til diskussioner. Eksempler p&aring; dette er 'patches' eller
-# 'checkin' lister, som system for revisionskontrol sender
-# &aelig;ndringer i programmet til, men diskussioner omkring udvikling
-# af programmet sendes til udviklernes egen mailliste. For at
-# underst&oslash;tte lignende e-maillister, v&aelig;lg Egendefineret
-# adresse og s&aelig;t Reply-To: adressen i indstillingen
-# reply_to_address til at pege på den parallelle diskussionsliste.
-#
-# gyldige værdier:
-#    0 = "Afsender"
-#    1 = "mail listens adresse"
-#    2 = "Egendefineret adresse"
+# This option controls what Mailman does to the Reply-To: header in
+# messages flowing through this mailing list.  When set to Poster, no
+# Reply-To: header is added by Mailman, although if one is present in
+# the original message, it is not stripped.  Setting this value to
+# either This list or Explicit address causes Mailman to insert a
+# specific Reply-To: header in all messages, overriding the header in
+# the original message if necessary (Explicit address inserts the value
+# of <a href="?VARHELP=general/reply_to_address">reply_to_address).
+# 
+# There are many reasons not to introduce or override the Reply-To:
+# header.  One is that some posters depend on their own Reply-To:
+# settings to convey their valid return address.  Another is that
+# modifying Reply-To: makes it much more difficult to send private
+# replies.  See <a
+# href="http://www.unicom.com/pw/reply-to-harmful.html">`Reply-To'
+# Munging Considered Harmful for a general discussion of this issue.
+# See <a
+# href="http://www.metasystema.net/essays/reply-to.mhtml">Reply-To
+# Munging Considered Useful for a dissenting opinion.
+# 
+# Some mailing lists have restricted posting privileges, with a parallel
+# list devoted to discussions.  Examples are `patches' or `checkin'
+# lists, where software changes are posted by a revision control system,
+# but discussion about the changes occurs on a developers mailing list.
+# To support these types of mailing lists, select Explicit address and
+# set the Reply-To: address below to point to the parallel list.
+#
+# legal values are:
+#    0 = "Poster"
+#    1 = "This list"
+#    2 = "Explicit address"
 reply_goes_to_list = 0
 
-# Her definerer du adressen der skal s&aelig;ttes i Reply-To: feltet
-# n&aring;r indstillingen reply_goes_to_list er sat til Egendefineret
-# adresse.
-# 
-# Der findes mange grunde til at ikke indf&oslash;re eller erstatte
-# Reply-To: felter. En grund kan v&aelig;re at nogen af dem der sender
-# e-mail til listen er afh&aelig;ngige af selv at kunne s&aelig;tte
-# Reply-To: adressen. En anden grund er at modificering af Reply-To:
-# adressen g&oslash;r det vanskeligere at sende svar kun til afsender.
-# Se 'Reply-To' Munging Considered Harmful for en diskussion omkring
-# temaet. Se Reply-To Munging Considered Useful for modsatte meninger.
-# 
-# Nogle maillister har begr&aelig;nset adgang, med en egen parallel
-# liste beregnet for diskussioner. Eksempler p&aring; dette er 'patches'
-# eller 'checkin' lister, som system for revisionskontrol sender
-# &aelig;ndringer i programmet til, mens diskussioner omkring udvikling
-# af programmet sendes til udviklernes egen mailliste. For at
-# underst&oslash;tte s&aring;danne maillister, kan du definere Reply-To:
-# adressen her, og vælge Egendefineret adresse i indstillingen
-# reply_goes_to_list.
-# 
-# Bem&aelig;rk at hvis den oprindelige meddelelse indeholder et
-# Reply-To: felt, vil det ikke &aelig;ndres.
+# This is the address set in the Reply-To: header when the <a
+# href="?VARHELP=general/reply_goes_to_list">reply_goes_to_list option
+# is set to Explicit address.
+# 
+# There are many reasons not to introduce or override the Reply-To:
+# header.  One is that some posters depend on their own Reply-To:
+# settings to convey their valid return address.  Another is that
+# modifying Reply-To: makes it much more difficult to send private
+# replies.  See <a
+# href="http://www.unicom.com/pw/reply-to-harmful.html">`Reply-To'
+# Munging Considered Harmful for a general discussion of this issue.
+# See <a
+# href="http://www.metasystema.net/essays/reply-to.mhtml">Reply-To
+# Munging Considered Useful for a dissenting opinion.
+# 
+# Some mailing lists have restricted posting privileges, with a parallel
+# list devoted to discussions.  Examples are `patches' or `checkin'
+# lists, where software changes are posted by a revision control system,
+# but discussion about the changes occurs on a developers mailing list.
+# To support these types of mailing lists, specify the explicit
+# Reply-To: address here.  You must also specify Explicit address in the
+# reply_goes_to_list variable.
+# 
+# Note that if the original message contains a Reply-To: header, it will
+# not be changed.
 reply_to_address = ''
 
-# V&aelig;lg kun 'ja' her, hvis listen skal bruges som  "paraply" for
-# andre lister. Hvis 'ja' er valgt, vil bekr&aelig;ftelser og
-# meddelelser med adgangskode blive sendt til en adresse som konstrueres
-# ud fra medlemmets e-mailadresse - v&aelig;rdien af indstillingen
-# "umbrella_member_suffix" tilf&oslash;jes medlemmets kontonavn (det som
-# st&aring;r f&oslash;r @-tegnet).
+# Set this to yes when this list is intended to cascade only to other
+# mailing lists.  When set, meta notices like confirmations and password
+# reminders will be directed to an address derived from the member's
+# address - it will have the value of "umbrella_member_suffix" appended
+# to the member's account name.
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 umbrella_list = 0
 
-# N&aring;r "umbrella_list" indikerer at denne liste har andre
-# maillister som medlemmer, skal administrative meddelelser som f.eks.
-# bekr&aelig;ftelser og p&aring;mindelser om adgangskode ikke sendes til
-# selve listen, men snarere til administrator for listen. V&aelig;rdien
-# af denne indstilling bestemmer, hvilken adresse administrative
-# meddelelser skal sendes til. '-owner' er et almindeligt valg for denne
-# indstilling. Denne indstilling har ingen effekt n&aring;r
-# "umbrella_list" er sat til "Nej".
+# When "umbrella_list" is set to indicate that this list has other
+# mailing lists as members, then administrative notices like
+# confirmations and password reminders need to not be sent to the member
+# list addresses, but rather to the owner of those member lists.  In
+# that case, the value of this setting is appended to the member's
+# account name for such notices.  `-owner' is the typical choice.  This
+# setting has no effect when "umbrella_list" is "No".
 umbrella_member_suffix = '-owner'
 
-# Aktiver denne, hvis der skal sendes en p&aring;mindelse om adgangskode
-# til medlemmerne en gang hver m&aring;ned. Husk at medlemmerne
-# ogs&aring; selv kan frav&aelig;lge dette.
+# Turn this on if you want password reminders to be sent once per month
+# to your members.  Note that members may disable their own individual
+# password reminders.
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 send_reminders = 0
 
-# Tekst du skriver her vil blive tilf&oslash;jet &oslash;verst i
-# velkomsthilsenen der sendes til nye medlemmer. Velkomshilsenen
-# indeholder i forvejen vigtige adresser og URLer knyttet til
-# maillisten, s&aring; den slags information er det ikke
-# n&oslash;dvendigt at inkludere her. Her kan du tilf&oslash;je f.eks.
-# oplysning om etikette eller regler for brug af listen, o.l.
-# 
-# Bem&aelig;rk: Linierne i denne tekst vil brydes efter f&oslash;lgende
-# regler:
+# This value, if any, will be added to the front of the new-subscriber
+# welcome message.  The rest of the welcome message already describes
+# the important addresses and URLs for the mailing list, so you don't
+# need to include any of that kind of stuff here.  This should just
+# contain mission-specific kinds of things, like etiquette policies or
+# team orientation, or that kind of thing.
 # 
-# Hvert afsnit udfyldes s&aringdan at ingen linie er l&aelig;ngere en 70
-# tegn. Enhver linie der begynder med tomme tegn udfyldes ikke. Tomme
-# linier adskiller afsnit.
+# Note that this text will be wrapped, according to the following rules:
+# Each paragraph is filled so that no line is longer than 70 characters.
+# Any line that begins with whitespace is not filled. A blank line
+# separates paragraphs.
 # 
 welcome_msg = ''
 
-# S&aelig;t kun denne til 'Nej' hvis du skal tilf&oslash;je nye
-# medlemmer manuelt, og ikke vil have at de f&aring;r det at vide. Dette
-# er meget nyttigt n&aring;r man g&aring;r fra et andet mallistesystem
-# og til Mailman, og vil have at overgangen skal v&aelig;re s&aring;
-# lidt m&aelig;rkbar som muligt.
+# Turn this off only if you plan on subscribing people manually and
+# don't want them to know that you did so.  This option is most useful
+# for transparently migrating lists from some other mailing list manager
+# to Mailman.
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 send_welcome_msg = 0
 
-# Tekst der sendes til medlemmer der framelder sig listen. Hvis feltet
-# er tomt, tilf&oslash;jes der ikke nogen speciel tekst til
-# frameldingen.
+# Text sent to people leaving the list.  If empty, no special text will
+# be added to the unsubscribe message.
 goodbye_msg = ''
 
-# Send afskedshilsen til medlemmer n&aring;r de frameldes?
+# Send goodbye message to members when they are unsubscribed?
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 send_goodbye_msg = 1
 
-# Der udsendes en p&aring;mindelse til listemoderator (og
-# listeadministrator) dagligt om anmodninger der af en eller anden grund
-# venter p&aring; behandling. V&aelig;lger du "Ja", vil
-# listeadminstrator ogs&aring; modtage en meddelelse s&aring; snart en
-# anmodning ankommer.
+# List moderators (and list administrators) are sent daily reminders of
+# requests pending approval, like subscriptions to a moderated list, or
+# postings that are being held for one reason or another.  Setting this
+# option causes notices to be sent immediately on the arrival of new
+# requests as well.
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 admin_immed_notify = 1
 
-# Skal listeadministrator modtage meddelelse om tilmeldinger og
-# afmeldinger?
+# Should administrator get notices of subscribes and unsubscribes?
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 admin_notify_mchanges = 1
 
-# Approval notices are sent when mail triggers certain of the limits
-# except routine list moderation and spam filters, for which notices are
-# not sent.  This option overrides ever sending the notice.
+# Send mail to poster when their posting is held for approval?
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 respond_to_post_requests = 1
 
-# Når dette valg er aktiveret, vil al e-mail til listen blive modereret.
-# Dette valg kan være nyttigt når din mailliste f.eks. har en såkaldt
-# "flamewar", altså en "krig" hvor medlemmer kun skælder ud på hinanden.
-# En "nød-moderering" kan da hjælpe dig at fjerne usaglige meddelelser
-# til listen, og på den måde dysse en ophedet diskussion ned.
+# When this option is enabled, all list traffic is emergency moderated,
+# i.e. held for moderation.  Turn this option on when your list is
+# experiencing a flamewar and you want a cooling off period.
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 emergency = 0
 
-# Når et nyt medlem tilmeldes listen, bliver medlemmets indstillinger
-# taget herfra.
+# When a new member is subscribed to this list, their initial set of
+# options is taken from the this variable's setting.
 new_member_options = 256
 
-# Filter for administrative meddelelser vil unders&oslash;ge om
-# meddelelsen egentligt er ment som en administrativ anmodning (f.eks.
-# tilmelding, framelding, o.l.), og i s&aring; fald sende meddelelsen
-# til listeadministrator i stedet for.
+# Administrivia tests will check postings to see whether it's really
+# meant as an administrative request (like subscribe, unsubscribe, etc),
+# and will add it to the the administrative requests queue, notifying
+# the administrator of the new request, in the process.
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 administrivia = 1
 
-# Maximum st&oslash;rrelse i kilobytes (KB) for indholdet i e-mail der
-# sendes til listen. Brug v&aelig;rdien '0' for ikke at have nogen
-# begr&aelig;nsning.
+# Maximum length in kilobytes (KB) of a message body.  Use 0 for no
+# limit.
 max_message_size = 40
 
-# "Maskinnavnet" er det navn som skal benyttes for e-mailadresser
-# relateret til Mailman p&aring; denne maskine, og er normalt navnet der
-# er forbundet med e-mail-servicen p&aring; maskinen. Denne indstilling
-# kan v&aelig;re nyttig hvis maskinen har flere navne.
+# The "host_name" is the preferred name for email to mailman-related
+# addresses on this host, and generally should be the mail host's
+# exchanger address, if any.  This setting can be useful for selecting
+# among alternative names of a host that has multiple addresses.
 host_name = 'www.nilsstaerk.dk'
 
-# I RFC 2369 defineres en r&aelig;kke List-* felter i brevhovedet, der
-# normalt tilf&oslash;jes enhver meddelelse der sendes ud via listen.
-# Disse felter er til stor gavn for brugere , som benytter et
-# e-mailprogram der f&oslash;lger standarden. Disse felter b&oslash;r
-# derfor altid v&aelig;re med.
-# 
-# Ikke alle e-mailprogrammer f&oslash;lger denne standard. Hvis der er
-# mange medlemmer p&aring; listen, der benytter e-mailprogrammer, der
-# ikke kan h&aring;ndtere disse felter i brevhovedet, kan du v&aelig;lge
-# at udelade dem. Men du b&oslash;r f&oslash;rst fors&oslash;ge at
-# l&aelig;re og forklare medlemmerne hvad hensigten med s&aring;danne
-# felter er, og hvordan de kan skjule dem i deres e-mailprogram. Som en
-# sidste udvej kan du udelade felterne, men det anbefales ikke (og denne
-# mulighed kan faktisk ogs&aring; blive fjernet i senere versioner af
-# Mailman).
-#
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# RFC 2369 defines a set of List-* headers that are normally added to
+# every message sent to the list membership. These greatly aid end-users
+# who are using standards compliant mail readers.  They should normally
+# always be enabled.
+# 
+# However, not all mail readers are standards compliant yet, and if you
+# have a large number of members who are using non-compliant mail
+# readers, they may be annoyed at these headers.  You should first try
+# to educate your members as to why these headers exist, and how to hide
+# them in their mail clients.  As a last resort you can disable these
+# headers, but this is not recommended (and in fact, your ability to
+# disable these headers may eventually go away).
+#
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 include_rfc2369_headers = 1
 
-# List-Post: feltet er et af felterne anbefalet i RFC 2369. P&aring;
-# nogle e-maillister (som f.eks. kun bruges til
-# offentligg&oslash;relser), er det kun bestemte personer der har lov
-# til at poste til listen. Almindelige medlemmer af listen har normalt
-# ikke lov til at poste til listen. For den slags lister, er List-Post:
-# feltet misvisende. S&aelig;t denne indstilling til Nej, for at
-# undg&aring; at feltet tilf&oslash;jes. (Dette p&aring;virker ikke
-# andre List-*: felter.)
-#
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# The List-Post: header is one of the headers recommended by RFC 2369.
+# However for some announce-only mailing lists, only a very select group
+# of people are allowed to post to the list; the general membership is
+# usually not allowed to post.  For lists of this nature, the List-Post:
+# header is misleading. Select No to disable the inclusion of this
+# header. (This does not affect the inclusion of the other List-*:
+# headers.)
+#
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 include_list_post_header = 1
 
+# Discard held messages older than this number of days. Use 0 for no
+# automatic discarding.
+max_days_to_hold = 0
+
 ## Language options
 #
-# Underst&oslash;ttelse af flere sprog. (Internationalisering)
-
-# Dette er standardsproget som benyttes for denne mailliste. Hvis flere
-# end et sprog/ underst&oslash;ttes, vil medlemmer af listen selv kunne
-# v&aelig;lge hvilket sprog der skal benyttes n&aring;r de g&aring;r ind
-# p&aring; deres personlige webside, og n&aring;r meddelelser fra
-# systemet sendes til dem. Hvis medlemmerne ikke &aelig;ndrer noget
-# selv, vil dette standardsprog blive benyttet. Dette g&aelig;lder
-# b&aring;de web-baserede og e-mail-baserede meddelelser, men ikke
-# meddelelser sendt af listens medlemmer.
+# Natural language (internationalization) options.
+
+# This is the default natural language for this mailing list. If more
+# than one language is supported then users will be able to select their
+# own preferences for when they interact with the list.  All other
+# interactions will be conducted in the default language.  This applies
+# to both web-based and email-based messages, but not to email posted by
+# list members.
 preferred_language = 'en'
 
-# Her er alle sprog, som denne liste har underst&oslash;ttelse for.
-# Bem&aelig;rk at standardsproget skal v&aelig;re med.
+# These are all the natural languages supported by this list. Note that
+# the default language must be included.
 available_languages = ['en', 'da']
 
-# Hvis standardsproget for din mailliste benytter et andet tegns&aelig;t
-# end ASCII og Emne prefixet for listen indeholder tegn som ikke findes
-# i ASCII-tegns&aelig;ttet, vil prefixet altid blive kodet i henhold til
-# den relevante standard. Hvis Emne prefixet kun indeholder ASCII tegn,
-# ønsker du måske at vælge Aldrig for at undgå kodning. Dette kan gøre
-# emnet lidt mere læseligt for brugere med e-mailprogrammer der ikke kan
-# håndtere andre tegnsæt end ASCII.
-# 
-# Bemærk imidlertid, at hvis din mailliste modtager både kodede og
-# ukodede emnefelter , kan det være bedst at vælge Efter behov. Med
-# denne indstilling vil Mailman ikke kode ASCII prefixer hvis resten af
-# titelfeltet kun indeholder ASCII tegn, men vil kode prefixet hvis det
-# indeholder tegn som ikke er ASCII tegn. På denne måde undgås en
-# tvetydighed i standarderne, som forårsager at visse e-mailprogrammer
-# vil vise ekstra eller manglende mellemrum imellem emne prefixet og det
-# oprindelige emne.
-#
-# gyldige værdier:
-#    0 = "Aldrig"
-#    1 = "Altid"
-#    2 = "Efter behov"
+# If your mailing list's default language uses a non-ASCII character set
+# and the prefix contains non-ASCII characters, the prefix will always
+# be encoded according to the relevant standards.  However, if your
+# prefix contains only ASCII characters, you may want to set this option
+# to Never to disable prefix encoding.  This can make the subject
+# headers slightly more readable for users with mail readers that don't
+# properly handle non-ASCII encodings.
+# 
+# Note however, that if your mailing list receives both encoded and
+# unencoded subject headers, you might want to choose As needed.  Using
+# this setting, Mailman will not encode ASCII prefixes when the rest of
+# the header contains only ASCII characters, but if the original header
+# contains non-ASCII characters, it will encode the prefix.  This avoids
+# an ambiguity in the standards which could cause some mail readers to
+# display extra, or missing spaces between the prefix and the original
+# header.
+#
+# legal values are:
+#    0 = "Never"
+#    1 = "Always"
+#    2 = "As needed"
 encode_ascii_prefixes = 0
 
 ## Nondigest options
 #
-# Regler for levering i normal-modus.
+# Policies concerning immediately delivered list traffic.
 
-# Kan medlemmer vælge normal-modus?
+# Can subscribers choose to receive mail immediately, rather than in
+# batched digests?
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 nondigestable = 1
 
-# Tekst der tilføjes &oslash;verst i e-mail der sendes til listens
-# medlemmer. This text can include Python format strings which are
-# resolved against list attributes.  The list of substitutions allowed
-# are:
+# Text prepended to the top of every immediately-delivery message. This
+# text can include Python format strings which are resolved against list
+# attributes.  The list of substitutions allowed are:
 # 
 # 
 # real_name - The "pretty" name of the list; usually the list name with
@@ -401,10 +388,9 @@ nondigestable = 1
 # 
 msg_header = ''
 
-# Tekst som tilf&oslash;jes nederst i e-mail der sendes til listens
-# medlemmer. This text can include Python format strings which are
-# resolved against list attributes.  The list of substitutions allowed
-# are:
+# Text appended to the bottom of every immediately-delivery message.
+# This text can include Python format strings which are resolved against
+# list attributes.  The list of substitutions allowed are:
 # 
 # 
 # real_name - The "pretty" name of the list; usually the list name with
@@ -432,45 +418,54 @@ msg_footer = """_______________________________________________
 %(real_name)s@%(host_name)s
 %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s"""
 
+# When you scrub attachments, they are stored in archive area and links
+# are made in the message so that the member can access via web browser.
+# If you want the attachments totally disappear, you can use content
+# filter options.
+#
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
+scrub_nondigest = False
+
 ## Digest options
 #
-# Opsætning af sammendrag-modus.
+# Batched-delivery digest characteristics.
 
-# Kan medlemmer af listen vælge sammendrag-modus?
+# Can list members choose to receive list traffic bunched in digests?
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 digestable = 1
 
-# Hvilken modus er standard for nye brugere?
+# Which delivery mode is the default for new users?
 #
-# gyldige værdier:
-#    0 = "Normal"
-#    1 = "Sammendrag"
+# legal values are:
+#    0 = "Regular"
+#    1 = "Digest"
 digest_is_default = 0
 
-# Hvilket format skal benyttes som standard for samle-email?
+# When receiving digests, which format is default?
 #
-# gyldige værdier:
-#    0 = "Ren tekst"
+# legal values are:
+#    0 = "Plain"
 #    1 = "MIME"
 mime_is_default_digest = 0
 
-# Hvor stor (i KB) m&aring; en samle-email h&oslash;jst v&aelig;re
-# f&oslash;r den udsendes?
+# How big in Kb should a digest be before it gets sent out?
 digest_size_threshhold = 30
 
-# Skal der sendes en samle-email dagligt, selv om st&oslash;rrelsen ikke
-# er opn&aring;et?
+# Should a digest be dispatched daily when the size threshold isn't
+# reached?
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 digest_send_periodic = 1
 
-# Tekst som tilf&oslash;jes &oslash;verst i samle-emailen, f&oslash;r
-# indholdsfortegnelsen.This text can include Python format strings which
+# Text attached (as an initial message, before the table of contents) to
+# the top of digests. This text can include Python format strings which
 # are resolved against list attributes.  The list of substitutions
 # allowed are:
 # 
@@ -497,10 +492,9 @@ digest_send_periodic = 1
 # 
 digest_header = ''
 
-# Tekst der tilføjes nederst i hver samle-email, som sidste
-# information.This text can include Python format strings which are
-# resolved against list attributes.  The list of substitutions allowed
-# are:
+# Text attached (as a final message) to the bottom of digests. This text
+# can include Python format strings which are resolved against list
+# attributes.  The list of substitutions allowed are:
 # 
 # 
 # real_name - The "pretty" name of the list; usually the list name with
@@ -528,277 +522,279 @@ digest_footer = """_______________________________________________
 %(real_name)s@%(host_name)s
 %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s"""
 
-# N&aring;r et nyt volume startes, &oslash;ges volume nummeret, og
-# udgavenummeret s&aelig;ttes til 1.
+# When a new digest volume is started, the volume number is incremented
+# and the issue number is reset to 1.
 #
-# gyldige værdier:
-#    0 = "&Aring;rlig"
-#    1 = "M&aring;nedlig"
-#    2 = "Kvartalsvis"
-#    3 = "Ugentlig"
-#    4 = "Daglig"
+# legal values are:
+#    0 = "Yearly"
+#    1 = "Monthly"
+#    2 = "Quarterly"
+#    3 = "Weekly"
+#    4 = "Daily"
 digest_volume_frequency = 1
 
 ## Privacy options
 #
-# Her kan du bestemme hvad der kr&aelig;ves for at tilmelde sig til
-# maillisten, og bl.a. bestemme om maillisten skal v&aelig;re skjult
-# eller ikke. Se ogs&aring; <a
-# href="http://www.nilsstaerk.dk/mailman/admin/nilsstaerk/archive">Indstillinger 
-# for arkivering</a> for egne indstillinger, n&aring;r det g&aelig;lder
-# arkivet og arkivering.
+# This section allows you to configure subscription and membership
+# exposure policy.  You can also control whether this list is public or
+# not.  See also the <a
+# href="http://www.nilsstaerk.dk/mailman/admin/nilsstaerk/archive">Archival 
+# Options</a> section for separate archive-related privacy settings.
 
-# Vis denne mailliste n&aring;r nogen beder om at se en oversigt over
-# maillister p&aring; denne maskine?
+# Advertise this list when people ask what lists are on this machine?
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 advertised = 1
 
-# bekræftelse(*) - bekr&aelig;ftelse via e-mail er n&oslash;dvendig
-# godkendelse - anmodning om medlemskab skal godkendes af
-# listeadministrator (eller evt. listemoderator) bekr&aelig;ftelse +
-# godkendelse - b&aring;de bekr&aelig;ftelse via e-mail og godkendelse
-# fra listeadministrator (evt. listemoderator) er n&oslash;dvendig
-# 
-# (*) n&aring;r nogen vil tilmelde sig en liste, sender Mailman en
-# meddelelse med en unik identifikator som skal angives for at
-# bekr&aelig;fte tilmeldingen. P&aring; den m&aring;de vil det ikke
-# v&aelig;re muligt at tilmelde nogen imod deres vilje.
-#
-# gyldige værdier:
-#    1 = "Bekr&aelig;ftelse"
-#    2 = "Godkendelse"
-#    3 = "Bekr&aelig;ftelse og godkendelse"
+# Confirm (*) - email confirmation required Require approval - require
+# list administrator approval for subscriptions Confirm and approve -
+# both confirm and approve
+# 
+# (*) when someone requests a subscription, Mailman sends them a notice
+# with a unique subscription request number that they must reply to in
+# order to subscribe. This prevents mischievous (or malicious) people
+# from creating subscriptions for others without their consent.
+#
+# legal values are:
+#    1 = "Confirm"
+#    2 = "Require approval"
+#    3 = "Confirm and approve"
 subscribe_policy = 2
 
-# N&aring;r medlemmer &oslash;nsker at forlade en mailliste, sender de
-# en anmodning om framelding, enten via web, eller via e-mail. Normalt
-# er det bedst at disse anmodninger automatisk godkendes, s&aring;
-# medlemmer kan afmelde sig n&aring;r de &oslash;nsker det (mange
-# &oslash;nsker selv at kunne administrere en framelding). For nogle
-# f&aring; maillister kan det alligevel v&aelig;re aktuelt at have
-# kontrol over om medlemmer kan afmelde sig selv eller ej. En liste som
-# alle ansatte i et firma SKAL v&aelig;re medlem af, er et eksempel
-# p&aring; en s&aring;dan liste.
-#
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# When members want to leave a list, they will make an unsubscription
+# request, either via the web or via email. Normally it is best for you
+# to allow open unsubscriptions so that users can easily remove
+# themselves from mailing lists (they get really upset if they can't get
+# off lists!).
+# 
+# For some lists though, you may want to impose moderator approval
+# before an unsubscription request is processed.  Examples of such lists
+# include a corporate mailing list that all employees are required to be
+# members of.
+#
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 unsubscribe_policy = 0
 
-# Alle e-mailadresser som angives her vil blive udelukket fra listen, og
-# kan ikke tilmelde sig. Indtast e-mailadresser, en pr. linie, start
-# linien med tegnet ^ for at angive et regexp-udtryk der skal stemme
-# overens med afsenderadressen.
-ban_list = ['ivan@divus.cz', 'arlene@divus.cz', 'news@divus.cz', 'postmaster@spamninja11.data393.net', 'postmaster@ideo.com', 'artes.plasticas@casamerica.es', 'mailer-daemon@yahoo.com', 'boxoffice@newschool.edu', 'symantec_antivirus_for_smtp_gateways@newschool.edu', 'exhibition@giger.cz', '138chriss@accesswave.com', '9gareth@accinternet.com', '6cassie@acadia.net', 'gpjth@hotmail.com', 'mqkiivztsa@yahoo.com', 'givyikheq@hotmail.com', 'kfrhrhny@hotmail.com', 'igcfeqxehzcz@hotmail.com', 'xqbjvh@hotmail.com', 'jmzccgrswwth@hotmail.com', 'marietta@access-one.com', 'divus@divus.cz', 'xmmsaaxt@yahoo.com', 'mailer-daemon@user2.cybercity.dk', 'baldip@yahoo.com', 'info@er-var.co.uk', 'nilsstaerk-request@jones.dk', 'xuzoerdcikv@yahoo.com', 'chester@about.com', 'lrejjuwf@hotmail.com', 'jjcvmqzdrco@oficinadecorreo.com', 'fkvxvudo@lmgpc.com', 'mailer-daemon@user3.cybercity.dk', '7janel@1st.net', 'info@sometimewaiting.co.uk', 'ugsjrq@calvarynaperville.org', 'vbusk@thesignshop.com', 'ejiyrhuvs@useglass.com', 'support@webworx.net.au', '29broderick@acadia.net', 'comunicacion@intereconomia.com', 'ehejcm@seethetrainer.com']
+# Addresses in this list are banned outright from subscribing to this
+# mailing list, with no further moderation required.  Add addresses one
+# per line; start the line with a ^ character to designate a regular
+# expression match.
+ban_list = ['ivan@divus.cz', 'arlene@divus.cz', 'news@divus.cz', 'postmaster@spamninja11.data393.net', 'postmaster@ideo.com', 'artes.plasticas@casamerica.es', 'mailer-daemon@yahoo.com', 'boxoffice@newschool.edu', 'symantec_antivirus_for_smtp_gateways@newschool.edu', 'exhibition@giger.cz', '138chriss@accesswave.com', '9gareth@accinternet.com', '6cassie@acadia.net', 'gpjth@hotmail.com', 'mqkiivztsa@yahoo.com', 'givyikheq@hotmail.com', 'kfrhrhny@hotmail.com', 'igcfeqxehzcz@hotmail.com', 'xqbjvh@hotmail.com', 'jmzccgrswwth@hotmail.com', 'marietta@access-one.com', 'divus@divus.cz', 'xmmsaaxt@yahoo.com', 'mailer-daemon@user2.cybercity.dk', 'baldip@yahoo.com', 'info@er-var.co.uk', 'nilsstaerk-request@jones.dk', 'xuzoerdcikv@yahoo.com', 'chester@about.com', 'lrejjuwf@hotmail.com', 'jjcvmqzdrco@oficinadecorreo.com', 'fkvxvudo@lmgpc.com', 'mailer-daemon@user3.cybercity.dk', '7janel@1st.net', 'info@sometimewaiting.co.uk', 'ugsjrq@calvarynaperville.org', 'vbusk@thesignshop.com', 'ejiyrhuvs@useglass.com', 'support@webworx.net.au', '29broderick@acadia.net', 'comunicacion@intereconomia.com', 'ehejcm@seethetrainer.com', 'yhkexjdnz@hotmail.com', 'info@tartsf.com', '34haskel@aaii.com', 'postmaster@roskilde-festival.dk', 'gftaezueajkzo@yahoo.com', 'ipyua@hotmail.com', 'nciwnuessqalw@yahoo.com', 'cfewpuhno@davidmbailey.com', '04freddie@abpn.com', '88arbenz@access-one.com', 'uqbsadon@todays.co.ke', '83hyman@acninc.net', 'ykiotnqx@msn.com', 'iebpbxrcwwg@slipfree.com', 'rdnkrvthhxr@hotmail.com', 'txidtnsrp@puebla.com', 'dvegxrizdpg@psiconsult.com', 'obrizuyranrhn@rootinstitute.com', 'socorro.mcintosh@earthlink.net', 'roslynaaas@archaeologist.com', 'quinnstarks@accountant.com', 'alfredoheath@publicist.com', 'dennyrowland@soon.com', 'margieknowles2p@rome.com', 'isabelleinman@soon.com', 'tknor@intelliteach.com', 'tl-sss@tl-sss.com', 'dhdgaywcirfd@moorekelly.freeserve.co.uk', 'issacmcintyre@iname.com', 'tknowlesdd@wrgb.com', 'tkwithecalhoun@billminder.com', 'augustaoakley@legislator.com', 'bmwoztx@lisecarabians.com', 'bennetthuerta@optician.com', 'donovanvelez@cliffhanger.com', 'destructadventure@popstar.com', 'melisajustice@hot-shot.com', 'billowbrownie@musician.org', 'vdlxbgy@ashoka.org', 'dieldrinbarium@adexec.com', 'srdgpooepm@bekkis.com', 'fnjaskracxizzt@navajoco.com', 'benblackberry@dr.com', 'lefvmkzn@ashlandhome.net', 'codetermineappertain@musician.org', 'dvorh@carfang.com', 'upcowdj@crfoods.com', 'borneasilomar@teacher.com', 'yfduyuy@butterworth.net', 'censorialcyrillic@earthling.net', 'wocecfar@concordances.com', 'copyrightbarberry@loveable.com', 'hbaaazhmlyk@ccsi-texas.com', 'hmpbiacund@christianaindustries.com', 'gxtfcsi@cbltech.com', 'bftkshsqb@f-i-s.com', 'brethrenbonfire@rouchotagreektranslations.nildram.co.uk', 'pwoairufn@earth.sunlink.net', 'aqu@fc.uhaul.com', 'n9tsprinkle@fortvicrv.com', 'catfishbirdie@earthlink.net', 'conjurecesium@rpdata.se', 'anthologyadmiration@rossword.org', 'cockeyeconcurrent@earthlink.net', 'gcmiedlcdu@flagworks.com', 'ralphmelisand@fichten.com', 'childlikebruce@royston.ie', 'mkybzwqziezbp@charlottecityclub.com', 'wlxryus@ceosuccess.com', 'livy@afol.com', 'daigle@karproducts.com', 'eugmosq@duesouth.net', 'cadfaelpurser@hnoc.org', 'compensableangelina@rpeer.com', 'diedeguo@icpusa.com', 'cineramaabysmal@earthlink.net', 'crematorychloroform@rotadasterras.com', 'mickukasand@azettler.com', 'tyripoc@cauzway.net', 'mzdndudepxgdnwuj@futbolsoccer.com', 'donataaborquez@homesoc.com', 'mill@esc9.net', 'hajnallack@ambenv.com', 'cameronbludgeon@earthlink.net', 'dnitfalna@tpnet.pl', 'andromac@arnett.com', 'deon@dragontek.com', 'hernu@atlantabev.com', 'tadeo@ariesgroupinc.com', 'xuekmv@drschore.com', 'nkrayfuwg@dulcinea.com', 'kelyesen@corcoran.com', 'chartcalibrate@earthlink.net', 'deoarahim@calvaryspringfield.org', 'koesitapiwa@fogelman-properties.com', 'gillesichab@centurian-surplus.com', 'alireacarlen@advancedrelocation.com', 'dudaucormac@alliedwelding.net', 'mxbrvrccf@schneis.de', 'decreasediameter@earthlink.net', 'fleshman@finaltouchvideo.com', 'znjuy@gaoland.net', 'true@dancehallminded.com', 'maspeacoc@hallmarkhomes-sav.com', 'brier@corpcomm.net', 'heffer@allprimeproducts.com', 'hdrumxynd@rr.com', 'rwlrtitc@iplannetworks.net', 'lizu@bma.com', 'jpfeguqnb@tpnet.pl', 'verrierykud@bcm.com', 'srakw@wanadoo.fr', 'clemilo@bonitabaygroup.com', 'roxann@kdix.com', 'swishera@changeconsultants.com', 'calumnyband@round-house.org', 'dravenrigg@adventis.com', 'ayzhfczpn@cdonline.dk', 'ymclapboard@carcumb.com', 'yfillegible@aron01.jany.gs.com', 'kisha@antaresiti.com', 'nievypohlm@covance.com', 'tiphavillica@gourmetconnection.com', 'belfuvolkan@d2bt01.jda002.net', 'qlfpjnpb@diversityinc.com', 'muirhet@housemancc.com', 'careful.congenital@rothauge.com', 'leporemisi@allured.com', 'lldepth@boxofficereport.com', 'bonaventurecerulean@rpm4parts.com', 'yaludurkee@groppelong.com', 'virabunt@cafe-express.com', 'iucomposition@briangrossfineart.com', 'jenae@chyron.com', 'lalage@abounding.org', 'reganai@harveststates.com', 'vconsort1@baiworld.com', 'bootstrapdeltoid@royalgreenjackets.co.uk', 'apdlnct@e-sonic.com', 'tuomo@hsca.com', 'colbo@fppp.org', 'valladistefan@advanced-driving.net', 'zslyhmbo@engpwr.com', 'koldobi@alloysystems.com', 'cemarinade@eventrentals.com', 'hanes@kitchenaid.com', 'nearyavrah@albany.com', 'gascay@advrenaltech.com', 'mccmorris@allamericanshops.com', 'nxwqrc@fieldingconstruction.com', 'roushinand@innisbrook.com', 'qwdarm@peer.pl', 'prakashugant@gasmark.com', 'alanag3lusk@townhall.com', 'blsnar@tpnet.pl', 'holsey@hadenstanziale.com', 'jhansen@scc.net', 'bovinebookcase@royalguardfence.com', 'lightaavram@commeng.com', 'marleneichurt@tropos.com', 'classarchfool@rowan.pl', 'repassguido@hawkeyesecurity-ins.com', 'whdsz@tpnet.pl', 'brakemanambuscade@rowebots.com', 'tabeamcclusky@eurekanet.com', 'mckeever@ownlife.com', 'skye@adcc.com', 'sparksuhiltrud@hammersplastic.com', 'shaeukova@eastbrookhomes.com', 'georginab3fournier@bartleby.com', 'algolaviatrix@rouwen.de', 'disccurvilinear@rpsb.net', 'allant@fuse.net', 'mcchesu@aimt.com', 'decy@bullseye-glass.com', 'eloisefrmesser@inflammationresearch.org', 'braggingbrigadier@royalsantaana.com', 'corneliatceddy@kidshealth.org', 'fbrmemsct@tie.cl', 'jsqrkrh@comcast.net', 'aeronwenakur@fnbada.com', 'ututfaobt@tiscali.fr', 'pthpnmyb@comcast.net', 'ilhixryr@estec.com', 'nvyfm@pgsm.hu', 'ashmenbarkeep@rotail.com', 'ramon@fspnet.com', 'bushwhackaficionado@rovaldi.com', 'xtwnjx@eos.esg.eng.sun.com', 'ydvwl@dumeco.com', 'nadja@cme.com', 'xjtnexgiox@taberindustries.com', 'giannayosmun@flexhaul.com', 'thomassonabeni@antec.com', 'lnanimosity@abmt.com', 'dcttabd@stwconn.com', 'aloysiussultan@breitdrescherbreit.com', 'lauracolucci@breoconsulting.com', 'fabian@fnol.net', 'fsolely@bergpipe.com', 'lsbegrh@rima-tde.net', 'haymiflavio@eaw.com', 'pirittay@kalkustom.com', 'cos@cookie.com', 'bypathcotta@earthlink.net', 'jsdqduznys@commsysinc.com', 'brae@doall.com', 'zqcuxknb@mindspring.com', 'farringt@asus.com', 'klyazdkmy@divo.net', 'lippoldtemp@agla.com', 'ldcalculator@asbloan.com', 'kylealcon@bipsnm.com', 'aregular@magnis.net', 'lvwxydwmi@fbrnet.com', 'kezvmcn@abecohen.com', 'van@childrensinstitute.org', 'moxkwzjmofl@rinet.ru', 'gwnwomohd@datachem.com', 'congruentback@royalterracehotel.co.uk', 'jolliff@atsalaska.com', 'kiranaplum@fcfinsurance.com', 'kesvanc@adjmail.com', 'morgancon@csw.net', 'swnntts@d-e-m-o.com', 'dorianbrunel@kbl.pactec.net', 'pap@baillie.com', 'dawooda@asde.net', 'keltner@amtechmicro.com', 'iacchu@lksamm.com', 'mayhall@cardsource.com', 'kittye@joplinglobe.com', 'chaseu@lonabaugh.com', 'harpermarylee@anaconda.com.au', 'bkechsibida@embarqhsd.net', 'laram2granger@tenthdimension.com', 'barnetabide@royalbank.co.zw', 'bonniem@avm.de', 'ufragile@maallen.com', 'zvjaihejxpf@usis.net', 'mull@burke.org', 'chartiera@healthwisdom.com', 'crailway@lstreb.com', 'aeibmjt@syscon-intl.com', 'bhymkzpym@xtria.com', 'ptbsrmgh@withatwist.com', 'aeneasdelphinus@rovaria.com', 'abstinentallegheny@rpscomm.com', 'carperi@corrcomm.net', 'ctracy@linkny.com', 'beneficecottonseed@royalinvestments.com', 'stultz@adventureunlimited.com', 'taukabbf@vhv.com', 'dana_54@loa.com', 'ulyssestheresa@wikipedia.org', 'stultzi@banknorth.com', 'binderybellyfullc@jewelmusic.com', 'crossroadbarometer@rowneyconsulting.com', 'rjzkvitev@wemsdiet.com', 'jehoiau@aek.com', 'darnalvarez@rr.collumbus.com', 'mpknltsee@templealiyah.com', 'boredomcalypso@roughgroove.com', 'lxfogto@smt.net', 'iwhtccks@therural.net', 'swenjwoffy@upromise.com', 'ozltkruc@visitedmondok.com', 'nfikbpr@somero.com', 'usaubozty@westquality.com', 'info@chromos.de', 'yphijdqwq@solutionsie.com', 'ambercranium@roullier.com.uy', 'aaugust@ncfbins.com', 'asinineanthem@rppeo.org', 'bibbso@lexgen.com', 'associablealameda@roxcar.com.br', 'arubachauncey@rquode.com', 'assumeaden@rotterdams-handelshuis.nl', 'acknowledgeblazon@royallender.com', 'blomqmichel@iqmail.net', 'bitwisebernardino@rqka1.mp', 'bbbbbadgcffdgc@caringforyou.uk.com', 'amau@ipsww.com', 'accrualbismuth@roussinwaechter.com', 'anticcranelike@royutah.com', 'arskimqwbm@britishwatchcompany.com', 'beanea@bentonandassoc.com', 'bhggpmdtm@photo-sciences.com', 'bivalveadjoin@route24.de', 'alexislmorn@uvhippo.com', 'anarchdefensive@royramm.no', 'bgefcgcfca@cassavarecords.com', 'begffafc@careercommandpost.com', 'besottedchristendom@routestolearning.ca']
 
-# Hvis denne indstilling ikke er sat til 'Alle', vil medlemslisten blive
-# beskyttet af medlemmernes eller administrators adgangskode.
+# When set, the list of subscribers is protected by member or admin
+# password authentication.
 #
-# gyldige værdier:
-#    0 = "Alle"
-#    1 = "Kun medlemmer af listen"
-#    2 = "Kun listeadministrator"
+# legal values are:
+#    0 = "Anyone"
+#    1 = "List members"
+#    2 = "List admin only"
 private_roster = 2
 
-# V&aelig;lger du 'Ja' her, vil medlemmers e-mailadresser blive
-# omskrevet n&aring;r de vises i en oversigt p&aring; websiderne
-# (b&aring;de som tekst og som links), s&aring; de ikke er nemme at
-# tolke som e-mailadresser. Formålet er at undg&aring; at medlemmernes
-# mailadresser bliver opsamlet af e-mailsniffere som skanner websider
-# for e-mailadresser (og derefter bruger dem til at udsende spam/junk
-# mail).
-#
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# Setting this option causes member email addresses to be transformed
+# when they are presented on list web pages (both in text and as links),
+# so they're not trivially recognizable as email addresses.  The
+# intention is to prevent the addresses from being snarfed up by
+# automated web scanners for use by spammers.
+#
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 obscure_addresses = 0
 
 ## Privacy options
 #
-# N&aring;r en meddelelse sendes til maillisten, g&aring;r den igennem
-# nogle trin for at afg&oslash;re om moderator skal godkende meddelelsen
-# eller ikke. Her finder du indstillinger til at kontrollere moderation
-# af e-mail fra b&aring;de medlemmer og ikke-medlemmer.
-# 
-# <p>E-mail fra medlemmer holdes tilbage for godkendelse hvis deres
-# <b>moderationsflag</b> er sat. Du kan bestemme om e-mail fra medlemmer
-# normalt skal vurderes eller ikke f&oslash;r den sendes til listen.
-# 
-# <p>E-mail som ikke er sendt af medlemmer af listen, kan automatisk
-# blive <a
-# href="?VARHELP=privacy/sender/accept_these_nonmembers">godkendt</a>,
-# <a href="?VARHELP=privacy/sender/hold_these_nonmembers">holdt tilbage
-# for godkendelse</a>, <a
-# href="?VARHELP=privacy/sender/reject_these_nonmembers">afvist (sendt
-# retur)</a>, eller <a
-# href="?VARHELP=privacy/sender/discard_these_nonmembers">slettet</a>,
-# enten enkeltvis eller som en gruppe. Al e-mail fra ikke-medlemmer, som
-# ikke specifikt bliver godkendt, sendt retur eller slettet, vil blive
-# behandlet alt efter hvad <a
-# href="?VARHELP=privacy/sender/generic_nonmember_action">generelle
-# regler for ikke-medlemmer</a> viser.
-# 
-# <p>I tekstboksene nedenfor kan du tilf&oslash;je en e-mailadresse pr.
-# linie. Du kan ogs&aring; tilf&oslash;je  <a
-# href="http://www.python.org/doc/current/lib/module-re.html">Python
-# regexp-udtryk</a>. Begynd i s&aring; fald linien med tegnet ^ for at
-# markere at det er et s&aring;dant udtryk. N&aring;r du benytter
-# backslash, skriv da lige som i rene strings (Python raw strings)
-# (normalt kun &eacute;n backslash ad gangen).
-# 
-# <p>Bem&aelig;rk: sammenligning med normale e-mailadresser
-# udf&oslash;res f&oslash;rst, regexp-udtryk vil derfor blive behandlet
-# sidst.
-
-# Hvert medlem af listen har et moderationsflag som fort&aelig;ller om
-# e-mails fra medlemmet kan sendes direkte til e-maillisten, eller om de
-# f&oslash;rst skal godkendes af listemoderator. N&aring;r
-# moderationsflaget er sat til, skal e-mails fra medlemmet godkendes af
-# listemoderator f&oslash;r de udsendes til alle p&aring; listen. Som
-# listeadministrator kan du for hvert enkelt medlem bestemme om
-# medlemmets e-mail skal modereres eller ikke. N&aring;r et nyt medlem
-# tilmeldes listen, s&aelig;ttes moderationsflaget til den indstilling
-# du v&aelig;lger her. S&aelig;t den til 'Nej' hvis du &oslash;nsker at
-# e-mail fra medlemmer normalt skal g&aring; lige til listen. S&aelig;t
-# den til 'Ja' hvis du &oslash;nsker at e-mail fra nye medlemmer skal
-# godkendes f&oslash;r de udsendes til hele listen. Du kan altid
-# s&aelig;tte moderationsflaget for hvert enkelt medlem fra
-# Administration af medlemmer siden.
-#
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# When a message is posted to the list, a series of moderation steps are
+# take to decide whether the a moderator must first approve the message
+# or not.  This section contains the controls for moderation of both
+# member and non-member postings.
+# 
+# <p>Member postings are held for moderation if their <b>moderation
+# flag</b> is turned on.  You can control whether member postings are
+# moderated by default or not.
+# 
+# <p>Non-member postings can be automatically <a
+# href="?VARHELP=privacy/sender/accept_these_nonmembers" >accepted</a>,
+# <a href="?VARHELP=privacy/sender/hold_these_nonmembers">held for
+# moderation</a>, <a
+# href="?VARHELP=privacy/sender/reject_these_nonmembers" >rejected</a>
+# (bounced), or <a
+# href="?VARHELP=privacy/sender/discard_these_nonmembers"
+# >discarded</a>, either individually or as a group.  Any posting from a
+# non-member who is not explicitly accepted, rejected, or discarded,
+# will have their posting filtered by the <a
+# href="?VARHELP=privacy/sender/generic_nonmember_action">general
+# non-member rules</a>.
+# 
+# <p>In the text boxes below, add one address per line; start the line
+# with a ^ character to designate a <a href=
+# "http://www.python.org/doc/current/lib/module-re.html" >Python regular
+# expression</a>.  When entering backslashes, do so as if you were using
+# Python raw strings (i.e. you generally just use a single backslash).
+# 
+# <p>Note that non-regexp matches are always done first.
+
+# Each list member has a moderation flag which says whether messages
+# from the list member can be posted directly to the list, or must first
+# be approved by the list moderator.  When the moderation flag is turned
+# on, list member postings must be approved first.  You, the list
+# administrator can decide whether a specific individual's postings will
+# be moderated or not.
+# 
+# When a new member is subscribed, their initial moderation flag takes
+# its value from this option.  Turn this option off to accept member
+# postings by default.  Turn this option on to, by default, moderate
+# member postings first.  You can always manually set an individual
+# member's moderation bit by using the membership management screens.
+#
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 default_member_moderation = 1
 
+# Hold -- this holds the message for approval by the list moderators.
+# 
+# Reject -- this automatically rejects the message by sending a bounce
+# notice to the post's author.  The text of the bounce notice can be <a
+# href="?VARHELP=privacy/sender/member_moderation_notice" >configured by
+# you.
 # 
-# Hold tilbage -- meddelelsen holdes tilbage for godkendelse af
-# listemoderator(er). Afvis -- meddelelsen sendes automatisk retur til
-# afsender. Begrundelsen der sendes kan du skrive selv Slet --
-# meddelelsen bliver fjernet uden at give besked om dette til afsender.
+# Discard -- this simply discards the message, with no notice sent to
+# the post's author.
 # 
 #
-# gyldige værdier:
-#    0 = "Hold&nbsp;tilbage"
-#    1 = "Afvis"
-#    2 = "Slet"
+# legal values are:
+#    0 = "Hold"
+#    1 = "Reject"
+#    2 = "Discard"
 member_moderation_action = 0
 
-# Tekst som skal sendes med meddelelsen om afvisning som sendes til
-# modererede medlemmer af listen.
+# Text to include in any <a
+# href="?VARHELP/privacy/sender/member_moderation_action" >rejection
+# notice to be sent to moderated members who post to this list.
 member_moderation_notice = ''
 
-# E-mail fra disse ikke-medlemmer vil automatisk blive godkendt.
-# Tilf&oslash;j e-mailadresser, en pr. linie. Start linien med tegnet ^
-# for at angive et regexp-udtryk som skal stemme overens med
-# afsenderadressen.
+# Postings from any of these non-members will be automatically accepted
+# with no further moderation applied.  Add member addresses one per
+# line; start the line with a ^ character to designate a regular
+# expression match.
 accept_these_nonmembers = []
 
-# e-mail fra disse ikke-medlemmer vil automatisk blive holdt tilbage for
-# vurdering af listemoderator. Afsenderen vil modtage en meddelelse om
-# dette, med bl.a. instruktioner om hvordan han/hun kan
-# tilbagetr&aelig;kke sin e-mail. Indtast e-mailadresser, en pr. linie.
-# Start linien med tegnet ^ for at angive et regexp-udtryk som skal
-# stemme overens med afsenderadressen.
+# Postings from any of these non-members will be immediately and
+# automatically held for moderation by the list moderators. The sender
+# will receive a notification message which will allow them to cancel
+# their held message.  Add member addresses one per line; start the line
+# with a ^ character to designate a regular expression match.
 hold_these_nonmembers = []
 
-# E-mail fra disse ikke-medlemmer vil automatisk blive afvist. De vil
-# f&aring; mailen retur, med en meddelelse om at den blev automatisk
-# afvist. Dette valg b&oslash;r ikke benyttes for kendte spammere, de
-# b&oslash;r automatisk slettes. Indtast e-mailadresser, en pr. linie.
-# Start linien med tegnet ^ for at angive et regexp-udtryk som skal
-# stemme overens med afsenderadressen.
-reject_these_nonmembers = ['news@divus.cz', 'artes.plasticas@casamerica.es', 'mailer-daemon@yahoo.com', 'boxoffice@newschool.edu', 'symantec_antivirus_for_smtp_gateways@newschool.edu', 'exhibition@giger.cz', '138chriss@accesswave.com', '9gareth@accinternet.com', 'ivan@divus.cz', '6cassie@acadia.net', 'gpjth@hotmail.com', 'mqkiivztsa@yahoo.com', 'givyikheq@hotmail.com', 'mqkiivztsa@yahoo.com', 'givyikheq@hotmail.com', 'kfrhrhny@hotmail.com', 'igcfeqxehzcz@hotmail.com', 'xqbjvh@hotmail.com', 'jmzccgrswwth@hotmail.com', 'marietta@access-one.com', 'divus@divus.cz', 'xmmsaaxt@yahoo.com', 'mailer-daemon@user2.cybercity.dk', 'baldip@yahoo.com', 'info@er-var.co.uk', 'nilsstaerk-request@jones.dk', 'xuzoerdcikv@yahoo.com', 'chester@about.com', 'lrejjuwf@hotmail.com', 'jjcvmqzdrco@oficinadecorreo.com', 'fkvxvudo@lmgpc.com', 'mailer-daemon@user3.cybercity.dk', '7janel@1st.net', 'info@sometimewaiting.co.uk', 'ugsjrq@calvarynaperville.org', 'vbusk@thesignshop.com', 'ejiyrhuvs@useglass.com', 'support@webworx.net.au', '29broderick@acadia.net', 'comunicacion@intereconomia.com', 'ehejcm@seethetrainer.com']
-
-# E-mail fra disse ikke-medlemmer vil automatisk blive slettet. Det vil
-# sige at meddelelsen afvises uden nogen form for tilbagemelding, men
-# listemoderator kan (om &oslash;nsket) modtage en kopi af den afviste
-# e-mail. Tilf&oslash;j e-mailadresser, en pr. linie, start linien med
-# tegnet ^ for at angive et regexp-udtryk der skal stemme overens med
-# afsenderadressen.
-discard_these_nonmembers = []
-
-# N&aring;r en e-mail fra et ikke-medlem bliver modtaget, sammenlignes
-# e-mailens afsender med listen over e-mailadresser der skal godkendes,
-# holdes tilbage, <a
-# href="?VARHELP=privacy/sender/reject_these_nonmembers" >afvises
-# (sendes retur), eller slettes. Hvis afsenderadressen ikke stemmer
-# overens med en adresse der findes i listerne, bliver f&oslash;lgende
-# afg&oslash;relse truffet.
-#
-# gyldige værdier:
-#    0 = "Godkend"
-#    1 = "Hold&nbsp;tilbage"
-#    2 = "Afvis"
-#    3 = "Slet"
+# Postings from any of these non-members will be automatically rejected.
+# In other words, their messages will be bounced back to the sender with
+# a notification of automatic rejection.  This option is not appropriate
+# for known spam senders; their messages should be <a
+# href="?VARHELP=privacy/sender/discard_these_nonmembers" >automatically
+# discarded.
+# 
+# Add member addresses one per line; start the line with a ^ character
+# to designate a regular expression match.
+reject_these_nonmembers = ['news@divus.cz', 'artes.plasticas@casamerica.es', 'mailer-daemon@yahoo.com', 'boxoffice@newschool.edu', 'symantec_antivirus_for_smtp_gateways@newschool.edu', 'exhibition@giger.cz', '138chriss@accesswave.com', '9gareth@accinternet.com', 'ivan@divus.cz', '6cassie@acadia.net', 'gpjth@hotmail.com', 'mqkiivztsa@yahoo.com', 'givyikheq@hotmail.com', 'mqkiivztsa@yahoo.com', 'givyikheq@hotmail.com', 'kfrhrhny@hotmail.com', 'igcfeqxehzcz@hotmail.com', 'xqbjvh@hotmail.com', 'jmzccgrswwth@hotmail.com', 'marietta@access-one.com', 'divus@divus.cz', 'xmmsaaxt@yahoo.com', 'mailer-daemon@user2.cybercity.dk', 'baldip@yahoo.com', 'info@er-var.co.uk', 'nilsstaerk-request@jones.dk', 'xuzoerdcikv@yahoo.com', 'chester@about.com', 'lrejjuwf@hotmail.com', 'jjcvmqzdrco@oficinadecorreo.com', 'fkvxvudo@lmgpc.com', 'mailer-daemon@user3.cybercity.dk', '7janel@1st.net', 'info@sometimewaiting.co.uk', 'ugsjrq@calvarynaperville.org', 'vbusk@thesignshop.com', 'ejiyrhuvs@useglass.com', 'support@webworx.net.au', '29broderick@acadia.net', 'comunicacion@intereconomia.com', 'ehejcm@seethetrainer.com', 'eyrjoje@tofi.de', 'yhkexjdnz@hotmail.com', 'info@tartsf.com', 'postmaster@roskilde-festival.dk', 'gftaezueajkzo@yahoo.com', 'ipyua@hotmail.com', 'nciwnuessqalw@yahoo.com', 'cfewpuhno@davidmbailey.com', '04freddie@abpn.com', '88arbenz@access-one.com', 'uqbsadon@todays.co.ke', '83hyman@acninc.net', 'iebpbxrcwwg@slipfree.com', 'rdnkrvthhxr@hotmail.com', 'txidtnsrp@puebla.com', 'dvegxrizdpg@psiconsult.com', 'obrizuyranrhn@rootinstitute.com', 'socorro.mcintosh@earthlink.net', 'roslynaaas@archaeologist.com', 'quinnstarks@accountant.com', 'alfredoheath@publicist.com', 'dennyrowland@soon.com', 'margieknowles2p@rome.com', 'isabelleinman@soon.com', 'tknor@intelliteach.com', 'tl-sss@tl-sss.com', 'dhdgaywcirfd@moorekelly.freeserve.co.uk', 'issacmcintyre@iname.com', 'tknowlesdd@wrgb.com', 'tkwithecalhoun@billminder.com', 'augustaoakley@legislator.com', 'bmwoztx@lisecarabians.com', 'bennetthuerta@optician.com', 'donovanvelez@cliffhanger.com', 'destructadventure@popstar.com', 'melisajustice@hot-shot.com', 'vdlxbgy@ashoka.org', 'dieldrinbarium@adexec.com', 'srdgpooepm@bekkis.com', 'fnjaskracxizzt@navajoco.com', 'benblackberry@dr.com', 'lefvmkzn@ashlandhome.net', 'codetermineappertain@musician.org', 'dvorh@carfang.com', 'upcowdj@crfoods.com', 'borneasilomar@teacher.com', 'yfduyuy@butterworth.net', 'censorialcyrillic@earthling.net', 'wocecfar@concordances.com', 'copyrightbarberry@loveable.com', 'hbaaazhmlyk@ccsi-texas.com', 'hmpbiacund@christianaindustries.com', 'gxtfcsi@cbltech.com', 'bftkshsqb@f-i-s.com', 'brethrenbonfire@rouchotagreektranslations.nildram.co.uk', 'pwoairufn@earth.sunlink.net', 'aqu@fc.uhaul.com', 'n9tsprinkle@fortvicrv.com', 'catfishbirdie@earthlink.net', 'conjurecesium@rpdata.se', 'anthologyadmiration@rossword.org', 'cockeyeconcurrent@earthlink.net', 'gcmiedlcdu@flagworks.com', 'ralphmelisand@fichten.com', 'childlikebruce@royston.ie', 'mkybzwqziezbp@charlottecityclub.com', 'wlxryus@ceosuccess.com', 'livy@afol.com', 'daigle@karproducts.com', 'eugmosq@duesouth.net', 'cadfaelpurser@hnoc.org', 'compensableangelina@rpeer.com', 'diedeguo@icpusa.com', 'cineramaabysmal@earthlink.net', 'crematorychloroform@rotadasterras.com', 'mickukasand@azettler.com', 'tyripoc@cauzway.net', 'mzdndudepxgdnwuj@futbolsoccer.com', 'donataaborquez@homesoc.com', 'mill@esc9.net', 'hajnallack@ambenv.com', 'cameronbludgeon@earthlink.net', 'dnitfalna@tpnet.pl', 'andromac@arnett.com', 'deon@dragontek.com', 'hernu@atlantabev.com', 'tadeo@ariesgroupinc.com', 'xuekmv@drschore.com', 'nkrayfuwg@dulcinea.com', 'kelyesen@corcoran.com', 'chartcalibrate@earthlink.net', 'deoarahim@calvaryspringfield.org', 'koesitapiwa@fogelman-properties.com', 'gillesichab@centurian-surplus.com', 'alireacarlen@advancedrelocation.com', 'dudaucormac@alliedwelding.net', 'mxbrvrccf@schneis.de', 'decreasediameter@earthlink.net', 'fleshman@finaltouchvideo.com', 'znjuy@gaoland.net', 'true@dancehallminded.com', 'maspeacoc@hallmarkhomes-sav.com', 'brier@corpcomm.net', 'heffer@allprimeproducts.com', 'hdrumxynd@rr.com', 'rwlrtitc@iplannetworks.net', 'lizu@bma.com', 'jpfeguqnb@tpnet.pl', 'verrierykud@bcm.com', 'srakw@wanadoo.fr', 'clemilo@bonitabaygroup.com', 'roxann@kdix.com', 'swishera@changeconsultants.com', 'calumnyband@round-house.org', 'dravenrigg@adventis.com', 'ayzhfczpn@cdonline.dk', 'ymclapboard@carcumb.com', 'yfillegible@aron01.jany.gs.com', 'kisha@antaresiti.com', 'nievypohlm@covance.com', 'tiphavillica@gourmetconnection.com', 'belfuvolkan@d2bt01.jda002.net', 'qlfpjnpb@diversityinc.com', 'muirhet@housemancc.com', 'careful.congenital@rothauge.com', 'leporemisi@allured.com', 'lldepth@boxofficereport.com', 'bonaventurecerulean@rpm4parts.com', 'yaludurkee@groppelong.com', 'virabunt@cafe-express.com', 'jenae@chyron.com', 'lalage@abounding.org', 'reganai@harveststates.com', 'vconsort1@baiworld.com', 'bootstrapdeltoid@royalgreenjackets.co.uk', 'apdlnct@e-sonic.com', 'tuomo@hsca.com', 'colbo@fppp.org', 'valladistefan@advanced-driving.net', 'zslyhmbo@engpwr.com', 'koldobi@alloysystems.com', 'cemarinade@eventrentals.com', 'hanes@kitchenaid.com', 'nearyavrah@albany.com', 'gascay@advrenaltech.com', 'mccmorris@allamericanshops.com', 'nxwqrc@fieldingconstruction.com', 'roushinand@innisbrook.com', 'qwdarm@peer.pl', 'prakashugant@gasmark.com', 'alanag3lusk@townhall.com', 'blsnar@tpnet.pl', 'holsey@hadenstanziale.com', 'jhansen@scc.net', 'bovinebookcase@royalguardfence.com', 'ogricn@eletronet.com', 'lightaavram@commeng.com', 'marleneichurt@tropos.com', 'classarchfool@rowan.pl', 'repassguido@hawkeyesecurity-ins.com', 'whdsz@tpnet.pl', 'brakemanambuscade@rowebots.com', 'tabeamcclusky@eurekanet.com', 'mckeever@ownlife.com', 'skye@adcc.com', 'sparksuhiltrud@hammersplastic.com', 'shaeukova@eastbrookhomes.com', 'georginab3fournier@bartleby.com', 'algolaviatrix@rouwen.de', 'disccurvilinear@rpsb.net', 'allant@fuse.net', 'lewinosatterlee@isea.org', 'mcchesu@aimt.com', 'decy@bullseye-glass.com', 'eloisefrmesser@inflammationresearch.org', 'braggingbrigadier@royalsantaana.com', 'corneliatceddy@kidshealth.org', 'fbrmemsct@tie.cl', 'jsqrkrh@comcast.net', 'aeronwenakur@fnbada.com', 'ututfaobt@tiscali.fr', 'pthpnmyb@comcast.net', 'ilhixryr@estec.com', 'nvyfm@pgsm.hu', 'ashmenbarkeep@rotail.com', 'ramon@fspnet.com', 'bushwhackaficionado@rovaldi.com', 'xtwnjx@eos.esg.eng.sun.com', 'ydvwl@dumeco.com', 'nadja@cme.com', 'xjtnexgiox@taberindustries.com', 'giannayosmun@flexhaul.com', 'thomassonabeni@antec.com', 'lnanimosity@abmt.com', 'dcttabd@stwconn.com', 'aloysiussultan@breitdrescherbreit.com', 'lauracolucci@breoconsulting.com', 'fabian@fnol.net', 'fsolely@bergpipe.com', 'lsbegrh@rima-tde.net', 'haymiflavio@eaw.com', 'pirittay@kalkustom.com', 'pearcujoden@agg.com', 'cos@cookie.com', 'bypathcotta@earthlink.net', 'jsdqduznys@commsysinc.com', 'brae@doall.com', 'zqcuxknb@mindspring.com', 'farringt@asus.com', 'klyazdkmy@divo.net', 'lippoldtemp@agla.com', 'ldcalculator@asbloan.com', 'kylealcon@bipsnm.com', 'aregular@magnis.net', 'kezvmcn@abecohen.com', 'van@childrensinstitute.org', 'sselb@bwoodtx.com', 'moxkwzjmofl@rinet.ru', 'gwnwomohd@datachem.com', 'congruentback@royalterracehotel.co.uk', 'jolliff@atsalaska.com', 'kiranaplum@fcfinsurance.com', 'kesvanc@adjmail.com', 'morgancon@csw.net', 'swnntts@d-e-m-o.com', 'dorianbrunel@kbl.pactec.net', 'pap@baillie.com', 'dawooda@asde.net', 'keltner@amtechmicro.com', 'iacchu@lksamm.com', 'mayhall@cardsource.com', 'kittye@joplinglobe.com', 'chaseu@lonabaugh.com', 'harpermarylee@anaconda.com.au', 'bkechsibida@embarqhsd.net', 'laram2granger@tenthdimension.com', 'barnetabide@royalbank.co.zw', 'gascay@advrenaltech.com', 'mccmorris@allamericanshops.com', 'nxwqrc@fieldingconstruction.com', 'roushinand@innisbrook.com', 'qwdarm@peer.pl', 'prakashugant@gasmark.com', 'alanag3lusk@townhall.com', 'blsnar@tpnet.pl', 'holsey@hadenstanziale.com', 'jhansen@scc.net', 'bovinebookcase@royalguardfence.com', 'ogricn@eletronet.com', 'lightaavram@commeng.com', 'marleneichurt@tropos.com', 'classarchfool@rowan.pl', 'repassguido@hawkeyesecurity-ins.com', 'whdsz@tpnet.pl', 'brakemanambuscade@rowebots.com', 'tabeamcclusky@eurekanet.com', 'mckeever@ownlife.com', 'skye@adcc.com', 'sparksuhiltrud@hammersplastic.com', 'shaeukova@eastbrookhomes.com', 'georginab3fournier@bartleby.com', 'algolaviatrix@rouwen.de', 'disccurvilinear@rpsb.net', 'allant@fuse.net', 'lewinosatterlee@isea.org', 'mcchesu@aimt.com', 'decy@bullseye-glass.com', 'eloisefrmesser@inflammationresearch.org', 'braggingbrigadier@royalsantaana.com', 'corneliatceddy@kidshealth.org', 'fbrmemsct@tie.cl', 'jsqrkrh@comcast.net', 'aeronwenakur@fnbada.com', 'ututfaobt@tiscali.fr', 'pthpnmyb@comcast.net', 'ilhixryr@estec.com', 'nvyfm@pgsm.hu', 'ashmenbarkeep@rotail.com', 'ramon@fspnet.com', 'bushwhackaficionado@rovaldi.com', 'xtwnjx@eos.esg.eng.sun.com', 'ydvwl@dumeco.com', 'nadja@cme.com', 'xjtnexgiox@taberindustries.com', 'giannayosmun@flexhaul.com', 'thomassonabeni@antec.com', 'lnanimosity@abmt.com', 'dcttabd@stwconn.com', 'aloysiussultan@breitdrescherbreit.com', 'lauracolucci@breoconsulting.com', 'fabian@fnol.net', 'fsolely@bergpipe.com', 'lsbegrh@rima-tde.net', 'haymiflavio@eaw.com', 'pirittay@kalkustom.com', 'pearcujoden@agg.com', 'cos@cookie.com', 'bypathcotta@earthlink.net', 'jsdqduznys@commsysinc.com', 'brae@doall.com', 'zqcuxknb@mindspring.com', 'farringt@asus.com', 'klyazdkmy@divo.net', 'lippoldtemp@agla.com', 'ldcalculator@asbloan.com', 'kylealcon@bipsnm.com', 'aregular@magnis.net', 'kezvmcn@abecohen.com', 'van@childrensinstitute.org', 'sselb@bwoodtx.com', 'moxkwzjmofl@rinet.ru', 'gwnwomohd@datachem.com', 'congruentback@royalterracehotel.co.uk', 'jolliff@atsalaska.com', 'kiranaplum@fcfinsurance.com', 'kesvanc@adjmail.com', 'morgancon@csw.net', 'swnntts@d-e-m-o.com', 'dorianbrunel@kbl.pactec.net', 'pap@baillie.com', 'dawooda@asde.net', 'keltner@amtechmicro.com', 'iacchu@lksamm.com', 'mayhall@cardsource.com', 'kittye@joplinglobe.com', 'chaseu@lonabaugh.com', 'harpermarylee@anaconda.com.au', 'bkechsibida@embarqhsd.net', 'laram2granger@tenthdimension.com', 'barnetabide@royalbank.co.zw', 'bonniem@avm.de', 'ufragile@maallen.com', 'zvjaihejxpf@usis.net', 'mull@burke.org', 'chartiera@healthwisdom.com', 'crailway@lstreb.com', 'aeibmjt@syscon-intl.com', 'bhymkzpym@xtria.com', 'ptbsrmgh@withatwist.com', 'aeneasdelphinus@rovaria.com', 'abstinentallegheny@rpscomm.com', 'carperi@corrcomm.net', 'ctracy@linkny.com', 'beneficecottonseed@royalinvestments.com', 'stultz@adventureunlimited.com', 'taukabbf@vhv.com', 'dana_54@loa.com', 'ulyssestheresa@wikipedia.org', 'stultzi@banknorth.com', 'binderybellyfullc@jewelmusic.com', 'crossroadbarometer@rowneyconsulting.com', 'rjzkvitev@wemsdiet.com', 'gqmevwqcjja@verizon.com', 'jehoiau@aek.com', 'darnalvarez@rr.collumbus.com', 'mpknltsee@templealiyah.com', 'hedinychiz@dp-center.com', 'boredomcalypso@roughgroove.com', 'lxfogto@smt.net', 'iwhtccks@therural.net', 'ozltkruc@visitedmondok.com', 'nfikbpr@somero.com', 'peebrraqgnf@telecen.net', 'usaubozty@westquality.com', 'info@chromos.de', 'swenjwoffy@upromise.com', 'yphijdqwq@solutionsie.com', 'ambercranium@roullier.com.uy', 'asinineanthem@rppeo.org', 'bibbso@lexgen.com', 'associablealameda@roxcar.com.br', 'arubachauncey@rquode.com', 'assumeaden@rotterdams-handelshuis.nl', 'acknowledgeblazon@royallender.com', 'blomqmichel@iqmail.net', 'bitwisebernardino@rqka1.mp', 'bbbbbadgcffdgc@caringforyou.uk.com', 'amau@ipsww.com', 'accrualbismuth@roussinwaechter.com', 'anticcranelike@royutah.com', 'arskimqwbm@britishwatchcompany.com', 'beanea@bentonandassoc.com', 'bhggpmdtm@photo-sciences.com', 'bivalveadjoin@route24.de', 'alexislmorn@uvhippo.com', 'anarchdefensive@royramm.no', 'bgefcgcfca@cassavarecords.com', 'begffafc@careercommandpost.com', 'besottedchristendom@routestolearning.ca']
+
+# Postings from any of these non-members will be automatically
+# discarded.  That is, the message will be thrown away with no further
+# processing or notification.  The sender will not receive a
+# notification or a bounce, however the list moderators can optionally
+# <a href="?VARHELP=privacy/sender/forward_auto_discards" >receive
+# copies of auto-discarded messages..
+# 
+# Add member addresses one per line; start the line with a ^ character
+# to designate a regular expression match.
+discard_these_nonmembers = ['lvwxydwmi@fbrnet.com', 'lvwxydwmi@fbrnet.com', 'aaugust@ncfbins.com']
+
+# When a post from a non-member is received, the message's sender is
+# matched against the list of explicitly <a
+# href="?VARHELP=privacy/sender/accept_these_nonmembers" >accepted,
+# held, <a href="?VARHELP=privacy/sender/reject_these_nonmembers"
+# >rejected (bounced), and <a
+# href="?VARHELP=privacy/sender/discard_these_nonmembers" >discarded
+# addresses.  If no match is found, then this action is taken.
+#
+# legal values are:
+#    0 = "Accept"
+#    1 = "Hold"
+#    2 = "Reject"
+#    3 = "Discard"
 generic_nonmember_action = 1
 
-# Skal meddelelser fra ikke-medlemmer, hvis mail automatisk slettes,
-# videresendes til listemoderator?
+# Should messages from non-members, which are automatically discarded,
+# be forwarded to the list moderator?
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 forward_auto_discards = 1
 
+# Text to include in any rejection notice to be sent to non-members who
+# post to this list. This notice can include the list's owner address by
+# %(listowner)s and replaces the internally crafted default message.
+nonmember_rejection_notice = ''
+
 ## Privacy options
 #
-# Her kan du ops&aelig;tte filtrering baseret på modtageren af
-# meddelelsen.
+# This section allows you to configure various filters based on the
+# recipient of the message.
 
-# Meget (faktisk det meste) spam/junk mail har ikke de endelige
-# modtagere i modtagerfelterne. Faktisk indeholder felterne To: og/eller
-# Cc: oftest en helt ugyldig adresse. Begr&aelig;nsningen du
-# s&aelig;tter her har kun indvirkning p&aring; det som st&aring;r
-# f&oslash;r '@' tegnet i adressen, men filtret vil alligevel opfange og
-# blokere det meste spam/junk mail.
+# Many (in fact, most) spams do not explicitly name their myriad
+# destinations in the explicit destination addresses - in fact often the
+# To: field has a totally bogus address for obfuscation.  The constraint
+# applies only to the stuff in the address before the '@' sign, but
+# still catches all such spams.
+# 
+# The cost is that the list will not accept unhindered any postings
+# relayed from other addresses, unless
 # 
-# Prisen for dette er, at listen ikke uhindret vil kunne modtage e-mail
-# videresendt via andre e-mailadresser, med mindre
 # 
+# The relaying address has the same name, or
+# 
+# The relaying address name is included on the options that specifies
+# acceptable aliases for the list.
 # 
-# Adressen der videresendes fra hedder det samme, eller Adressen der
-# videresendes fra inkluderes i indstillingen som bestemmer gyldige
-# aliaser for listen.
 # 
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 require_explicit_destination = 1
 
-# Alternative e-mailadresser som godtages n&aring;r
-# 'require_explicit_destination' er sat til. Som v&aelig;rdi for denne
-# indstilling skal du angive regexp-udtryk ("regular expressions"), et
-# udtryk pr. linie, der sammenlignes med hver modtageradresse i
-# meddelelsen. Sammenligningen udf&oslash;res med Pythons re.match()
-# funktion, som betyder at de kun g&aelig;lder for begyndelsen af
-# strengen.
-# 
-# For bagudkompatibilitet med Mailman 1.1, hvis regexp-udtryk ikke
-# indeholder en '@', sammenlignes udtrykket kun med den f&oslash;rste
-# del (det som st&aring;r f&oslash;r '@') i modtageradressen. Hvis
-# sammenligningen ikke lykkes, eller hvis udtrykket ikke indholder en
-# '@', sammenlignes udtrykket med hele modtageradressen.
-# 
-# Sammenligning med kun den f&oslash;rste del af en modtageradresse
-# underst&oslash;ttes ikke l&aelig;ngere. I fremtidige versioner af
-# Mailman vil kun sammenligning med hele modtageradresser blive
-# underst&oslash;ttet.
+# Alternate addresses that are acceptable when
+# `require_explicit_destination' is enabled.  This option takes a list
+# of regular expressions, one per line, which is matched against every
+# recipient address in the message.  The matching is performed with
+# Python's re.match() function, meaning they are anchored to the start
+# of the string.
+# 
+# For backwards compatibility with Mailman 1.1, if the regexp does not
+# contain an `@', then the pattern is matched against just the local
+# part of the recipient address.  If that match fails, or if the pattern
+# does contain an `@', then the pattern is matched against the entire
+# recipient address.
+# 
+# Matching against the local part is deprecated; in a future release,
+# the pattern will always be matched against the entire recipient
+# address.
 acceptable_aliases = ''
 
-# Hvis en mail der er sendt til listen indeholder s&aring; mange som
-# eller flere modtagere end denne v&aelig;rdi, holdes mailen tilbage,
-# s&aring; listeadministrator eventuelt kan godkende den. Brug
-# v&aelig;rdien 0 for ingen begr&aelig;nsning.
+# If a posting has this number, or more, of recipients, it is held for
+# admin approval.  Use 0 for no ceiling.
 max_num_recipients = 10
 
 ## Privacy options
 #
-# Her kan du opsætte forskellige anti-spam filtre, som kan bidrage til
-# at reducere mængden af spam der distribueres via e-maillisten.
+# This section allows you to configure various anti-spam filters posting
+# filters, which can help reduce the amount of spam your list members
+# end up receiving.
+# 
 
 # Each header filter rule has two parts, a list of regular expressions,
 # one per line, and an action to take.  Mailman matches the message's
@@ -809,22 +805,23 @@ max_num_recipients = 10
 # You can have more than one filter rule for your list.  In that case,
 # each rule is matched in turn, with processing stopped after the first
 # match.
+# 
+# Note that headers are collected from all the attachments (except for
+# the mailman administrivia message) and matched against the regular
+# expressions. With this feature, you can effectively sort out messages
+# with dangerous file types or file name extensions.
 header_filter_rules = []
 
-# Brug denne indstilling til at bortfiltrere mail til listen, baseret
-# p&aring; indholdet af et eller flere felter i brevhovedet. Her skal du
-# skrive regexp-udtryk (regular expressions), et pr. linie, som
-# sammenlignes med det aktuelle felt. Sammenligningen skelner ikke
-# imellem store og sm&aring; bogstaver. Linier der begynder med '#'
-# sammenlignes ikke.
+# Use this option to prohibit posts according to specific header values.
+# The target value is a regular-expression for matching against the
+# specified header.  The match is done disregarding letter case.  Lines
+# beginning with '#' are ignored as comments.
 # 
-# For eksempel: udtrykket to: .*@public.com fort&aelig;ller at al mail
-# som indeholder '@public.com' i To: feltet, skal holdes tilbage for
-# godkendelse.
+# For example:to: .*@public.com  says to hold all postings with a To:
+# mail header containing '@public.com' anywhere among the addresses.
 # 
-# Bem&aelig;rk: tomme tegn i starten af regexp-udtrykket fjernes. Dette
-# kan omg&aring;s p&aring; flere m&aring;der, f.eks. ved at bruge
-# escape-tegn eller parenteser.
+# Note that leading whitespace is trimmed from the regexp.  This can be
+# circumvented in a number of ways, e.g. by escaping or bracketing it.
 bounce_matching_headers = """# Lines that *start* with a '#' are comments.
 to: friend@public.com
 message-id: relay.comanche.denmark.eu
@@ -833,415 +830,439 @@ from: .*@uplinkpro.com"""
 
 ## Bounce options
 #
-# Disse regler bestemmer hvordan automatisk behandling af returmails
-# skal foreg&aring;. Her er en oversigt over hvordan det virker.
-# 
-# <p>N&aring;r Mailman modtager en returmail, bliver to ting
-# fors&oslash;gt tolket. Den ene er e-mailadressen for medlemmet som
-# egentlig skulle modtage e-mailen, og den anden er &aring;rsagen til
-# problemet. &Aring;rsagen tolkes til at v&aelig;re <em>alvorlig</em>
-# eller <em>harml&oslash;s</em> alt efter om &aring;rsagen er af kritisk
-# eller af mindre alvorlig art. Hvis der er tvivl, tolkes &aring;rsagen
-# som alvorlig.
-# 
-# <p>Hvis ingen e-mailadresse kan hentes ud af meddelelsen, bliver den
-# normalt afvist. Ellers vil medlemmet som har e-mailadressen f&aring;
-# tildelt et <em>returtal</em>, og hver gang der kommer en
-# returmeddelelse vil tallet &oslash;ges. Alvorlige &aring;rsager
-# f&oslash;rer til at tallet &oslash;ges med 1, harml&oslash;se
-# &aring;rsager f&oslash;rer til at det &oslash;ges med 0.5. Dette sker
-# kun &eacute;n gang pr. dag, s&aring; selv om der kommer 10 alvorlige
-# returmails fra et medlem p&aring; &eacute;n dag, vil tallet kun
-# &oslash;ges med 1.
-# 
-# <p>N&aring;r returtallet for et medlem n&aring;r en vis <a
-# href="?VARHELP=bounce/bounce_score_threshold">gr&aelig;nse</a>,
-# stoppes levering til medlemmet. Dermed vil medlemmet ikke modtage
-# e-mail fra listen f&oslash;r levering s&aelig;ttes til igen. Medlemmet
-# vil med j&aelig;vne mellemrum modtage meddelelse om at dette er sket,
-# og hvad han/hun skal g&oslash;re for at f&aring; e-mail fra listen
-# igen.
-# 
-# <p>Du kan bestemme <a
-# href="?VARHELP=bounce/bounce_you_are_disabled_warnings">hvor mange
-# advarsler</a> medlemmet skal have og <a
-# href="?VARHELP=bounce/bounce_you_are_disabled_warnings_interval">hvor
-# ofte</a> han/hun skal modtage s&aring;danne advarsler.
-# 
-# <p>Der er en vigtig indstilling mere: efter en vis tid -- hvor ingen
-# returmeddelelser dukker op -- regnes returinformation for at
-# v&aelig;re <a
-# href="?VARHELP=bounce/bounce_info_stale_after">for&aelig;ldet</a> og
-# stoppes. Ved at justere denne v&aelig;rdi, og s&aelig;tte en
-# gr&aelig;nse for returantallet, kan du bestemme hvor lang tid der skal
-# g&aring; f&oslash;r levering til et medlem stoppes. Begge disse
-# v&aelig;rdier b&oslash;r tilpasses efter hvor ofte og hvor meget
-# e-mail der sendes til din liste.
-
-# Ved at sætte denne værdi til Nej, slår du al automatisk tolkning af
-# returmeddelelser for denne liste fra. Bemærk at hvis meddelelser
-# afvises vil listeadministratoren ikke blive forstyrret med dem.
-#
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# These policies control the automatic bounce processing system in
+# Mailman.  Here's an overview of how it works.
+# 
+# <p>When a bounce is received, Mailman tries to extract two pieces of
+# information from the message: the address of the member the message
+# was intended for, and the severity of the problem causing the bounce.
+# The severity can be either <em>hard</em> or <em>soft</em> meaning
+# either a fatal error occurred, or a transient error occurred.  When in
+# doubt, a hard severity is used.
+# 
+# <p>If no member address can be extracted from the bounce, then the
+# bounce is usually discarded.  Otherwise, each member is assigned a
+# <em>bounce score</em> and every time we encounter a bounce from this
+# member we increment the score.  Hard bounces increment by 1 while soft
+# bounces increment by 0.5.  We only increment the bounce score once per
+# day, so even if we receive ten hard bounces from a member per day,
+# their score will increase by only 1 for that day.
+# 
+# <p>When a member's bounce score is greater than the <a
+# href="?VARHELP=bounce/bounce_score_threshold">bounce score
+# threshold</a>, the subscription is disabled.  Once disabled, the
+# member will not receive any postings from the list until their
+# membership is explicitly re-enabled (either by the list administrator
+# or the user).  However, they will receive occasional reminders that
+# their membership has been disabled, and these reminders will include
+# information about how to re-enable their membership.
+# 
+# <p>You can control both the <a
+# href="?VARHELP=bounce/bounce_you_are_disabled_warnings">number of
+# reminders</a> the member will receive and the <a
+# href="?VARHELP=bounce/bounce_you_are_disabled_warnings_interval"
+# >frequency</a> with which these reminders are sent.
+# 
+# <p>There is one other important configuration variable; after a
+# certain period of time -- during which no bounces from the member are
+# received -- the bounce information is <a
+# href="?VARHELP=bounce/bounce_info_stale_after">considered stale</a>
+# and discarded.  Thus by adjusting this value, and the score threshold,
+# you can control how quickly bouncing members are disabled.  You should
+# tune both of these to the frequency and traffic volume of your list.
+
+# By setting this value to No, you disable all automatic bounce
+# processing for this list, however bounce messages will still be
+# discarded so that the list administrator isn't inundated with them.
+#
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 bounce_processing = 1
 
-# Hvert medlem tildeles et returtal, og hver gang der kommer en
-# returmeddelelse vil dette tal &oslash;ges.  Alvorlige (&aring;rsager
-# f&oslash;rer til at det &oslash;ges med 1, mens harml&oslash;se
-# &aring;rsager f&oslash;rer til at det &oslash;ges med 0.5. Dette sker
-# kun &eacute;n gang pr. dag, s&aring; selv om der kommer 10 alvorlige
-# returmails fra et medlem p&aring; &eacute;n dag, vil tallet kun
-# &oslash;ges med 1.
-# 
-# Her s&aelig;ttes den &oslash;vre gr&aelig;nse for medlemmets returtal
-# Overskrides denne gr&aelig;nse stoppes levering automatisk, men
-# medlemmet bliver ikke fjernet fra listen.
+# Each subscriber is assigned a bounce score, as a floating point
+# number.  Whenever Mailman receives a bounce from a list member, that
+# member's score is incremented.  Hard bounces (fatal errors) increase
+# the score by 1, while soft bounces (temporary errors) increase the
+# score by 0.5.  Only one bounce per day counts against a member's
+# score, so even if 10 bounces are received for a member on the same
+# day, their score will increase by just 1.
+# 
+# This variable describes the upper limit for a member's bounce score,
+# above which they are automatically disabled, but not removed from the
+# mailing list.
 bounce_score_threshold = 5.0
 
-# Antal dage f&oslash;r returinformation stoppes hvis der ikke dukker
-# flere returmails op. Dette tal skal v&aelig;re et heltal.
+# The number of days after which a member's bounce information is
+# discarded, if no new bounces have been received in the interim.  This
+# value must be an integer.
 bounce_info_stale_after = 7
 
-# Hvor mange Levering til dig er stoppet advarsler der skal sendes til
-# et medlem f&oslash;r medlemmet frameldes listen. S&aelig;t denne værdi
-# til 0 for at fjerne et medlem fra listen straks, hvis der kommer
-# returmails fra medlemmets e-mailadresse. Dette tal skal være et
-# heltal.
+# How many Your Membership Is Disabled warnings a disabled member should
+# get before their address is removed from the mailing list.  Set to 0
+# to immediately remove an address from the list once their bounce score
+# exceeds the threshold.  This value must be an integer.
 bounce_you_are_disabled_warnings = 3
 
-# Antal dage imellem hver gang en Levering til dig er stoppet advarsel
-# skal sendes ud. Dette tal skal være et heltal.
+# The number of days between sending the Your Membership Is Disabled
+# warnings.  This value must be an integer.
 bounce_you_are_disabled_warnings_interval = 7
 
-# Mailmans automatiske returmailh&aring;ndtering er meget robust, men
-# det er alligevel umuligt at genkende alle typer returmails der kommer.
-# Du b&oslash;r v&aelig;lge Ja her, af to grunde: 1) Hvis det virkelig
-# er en permanent returmail fra et medlem af listen, b&oslash;r du
-# antagelig manuelt afmelde medlemmet fra listen, og 2) du vil
-# m&aring;ske sende en meddelelse til udviklerne af Mailman s&aring;dan
-# at returmails automatisk genkendes af Mailman i senere versioner. Hvis
-# du ikke vil g&oslash;re nogen af delene, s&aelig;ttes denne
-# indstilling til Nej. S&aring; vil alle returmails afvises automatisk
-# uden videre behandling. Bem&aelig;rk: Denne indstilling vil ogs&aring;
-# indvirke p&aring; al e-mail der sendes til listens -admin adresse. Den
-# adresse er for&aelig;ldet og udg&aring;et, men måske vil nogen
-# alligevel fortsat sende e-mail til den. Hvis nogen g&oslash;r det, og
-# du har sat denne indstilling til Nej, vil disse mails ogs&aring; blive
-# afvist. M&aring;ske vil du ogs&aring; ops&aelig;tte et automatisk svar
-# p&aring; e-mail sendt til -owner og -admin adresserne.
-#
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# While Mailman's bounce detector is fairly robust, it's impossible to
+# detect every bounce format in the world.  You should keep this
+# variable set to Yes for two reasons: 1) If this really is a permanent
+# bounce from one of your members, you should probably manually remove
+# them from your list, and 2) you might want to send the message on to
+# the Mailman developers so that this new format can be added to its
+# known set.
+# 
+# If you really can't be bothered, then set this variable to No and all
+# non-detected bounces will be discarded without further processing.
+# 
+# Note: This setting will also affect all messages sent to your list's
+# -admin address.  This address is deprecated and should never be used,
+# but some people may still send mail to this address.  If this happens,
+# and this variable is set to No those messages too will get discarded.
+# You may want to set up an autoresponse message for email to the -owner
+# and -admin address.
+#
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 bounce_unrecognized_goes_to_list_owner = 1
 
-# Ved at sætte denne til Nej, fravælges beskeden der normalt sendes til
-# ejer(e) af listen, når levering af e-mail til et medlem stoppes på
-# grund af for mange returmails. Der vil til gengæld altid blive forsøgt
-# afsendt en e-mail med besked til medlemmet.
+# By setting this value to No, you turn off notification messages that
+# are normally sent to the list owners when a member's delivery is
+# disabled due to excessive bounces. An attempt to notify the member
+# will always be made.
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 bounce_notify_owner_on_disable = 1
 
-# Ved at sætte denne til Nej, fravælges beskeden der normalt sendes til
-# ejer(e) af listen, når et medlem frameldes listen på grund af for
-# mange returmails. Der vil til gengæld altid blive forsøgt afsendt en
-# e-mail med besked til medlemmet.
+# By setting this value to No, you turn off notification messages that
+# are normally sent to the list owners when a member is unsubscribed due
+# to excessive bounces.  An attempt to notify the member will always be
+# made.
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 bounce_notify_owner_on_removal = 1
 
 ## Archive options
 #
-# Regler for arkivering
+# List traffic archival policies.
 
-# Arkiver e-mail i et arkiv?
+# Archive messages?
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 archive = 0
 
-# Skal arkivet v&aelig;re offentligt eller privat?
+# Is archive file source for public or private archival?
 #
-# gyldige værdier:
-#    0 = "Offentligt"
-#    1 = "Privat"
+# legal values are:
+#    0 = "public"
+#    1 = "private"
 archive_private = 0
 
-# Hvor ofte skal arkivet deles op?
+# How often should a new archive volume be started?
 #
-# gyldige værdier:
-#    0 = "&Aring;rlig"
-#    1 = "M&aring;nedlig"
-#    2 = "Kvartalsvis"
-#    3 = "Ugentlig"
-#    4 = "Daglig"
+# legal values are:
+#    0 = "Yearly"
+#    1 = "Monthly"
+#    2 = "Quarterly"
+#    3 = "Weekly"
+#    4 = "Daily"
 archive_volume_frequency = 2
 
 ## Gateway options
 #
-# E-mail-Til-Nyhedsgruppe og Nyhedsgruppe-Til-E-mail tjeneste.
+# Mail-to-News and News-to-Mail gateway services.
 
-# Nyhedsgruppe-tjeneste er ikke en del af Mailman. Du skal have adgang
-# til en eksisterende NNTP tjeneste, og maskinen som denne mailliste
-# k&oslash;rer p&aring; skal have adgang til at hente og afsende
-# meddelelser til NNTP tjenesten.
+# This value may be either the name of your news server, or optionally
+# of the format name:port, where port is a port number.
+# 
+# The news server is not part of Mailman proper.  You have to already
+# have access to an NNTP server, and that NNTP server must recognize the
+# machine this mailing list runs on as a machine capable of reading and
+# posting news.
 nntp_host = ''
 
-# Navn p&aring; nyhedsgruppe der skal sendes til og/eller fra.
+# The name of the Usenet group to gateway to and/or from.
 linked_newsgroup = ''
 
-# Skal nye meddelelser til denne liste sendes til nyhedsgruppen?
+# Should new posts to the mailing list be sent to the newsgroup?
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 gateway_to_news = 0
 
-# Skal nye meddelelser til nyhedsgruppen sendes til denne mailliste?
+# Should new posts to the newsgroup be sent to the mailing list?
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 gateway_to_mail = 0
 
-# Denne indstilling fort&aelig;ller Mailman hvilken slags
-# moderationsregler nyhedsgruppen har og hvordan de koordineres med
-# maillistens moderationsregler. Dette g&aelig;lder kun nyhedgrupper du
-# overfører meddelelser til, s&aring; hvis du kun overf&oslash;rer fra
-# en nyhedsgruppe, eller nyhedsgruppen du overf&oslash;rer til ikke er
-# modereret, s&aelig;ttes indstillingen til Ingen.
-# 
-# Hvis nyhedsgruppen er modereret, kan du s&aelig;tte maillisten til at
-# v&aelig;re moderationsadressen for nyhedsgruppen. Ved at vælge
-# Modereret, vil en ekstra meddelelse holdes tilbage i
-# godkendelsesprocessen. Al mail sendt til maillisten skal godkendes
-# f&oslash;r den sendes til nyhedsgruppen, eller til medlemmerne af
-# listen.
-# 
-# Vær opm&aelig;rksom p&aring; at hvis brevhovedet i mailen har et
-# Approved: felt med listens administrative adgangskode, vil denne regel
-# ikke blive benyttet. På den m&aring;de kan priviligerede afsendere
-# sende mail direkte til listen og nyhedsgruppen.
-# 
-# Hvis nyhedsgruppen er modereret, men du alligevel vil have en
-# &aring;ben liste, b&oslash;r du vælge Åben liste, modereret
-# nyhedsgruppe. S&aring; vil de s&aelig;dvanlige mekanismer for
-# moderation blive benyttet i Mailman, men alle meddelelser der sendes
-# til Usenet vil f&aring; et Approved felt i brevhovedet.
-#
-# gyldige værdier:
-#    0 = "Ingen"
-#    1 = "Åben liste, modereret nyhedsgruppe"
-#    2 = "Modereret"
+# This setting determines the moderation policy of the newsgroup and its
+# interaction with the moderation policy of the mailing list.  This only
+# applies to the newsgroup that you are gatewaying to, so if you are
+# only gatewaying from Usenet, or the newsgroup you are gatewaying to is
+# not moderated, set this option to None.
+# 
+# If the newsgroup is moderated, you can set this mailing list up to be
+# the moderation address for the newsgroup.  By selecting Moderated, an
+# additional posting hold will be placed in the approval process.  All
+# messages posted to the mailing list will have to be approved before
+# being sent on to the newsgroup, or to the mailing list membership.
+# 
+# Note that if the message has an Approved header with the list's
+# administrative password in it, this hold test will be bypassed,
+# allowing privileged posters to send messages directly to the list and
+# the newsgroup.
+# 
+# Finally, if the newsgroup is moderated, but you want to have an open
+# posting policy anyway, you should select Open list, moderated group.
+# The effect of this is to use the normal Mailman moderation facilities,
+# but to add an Approved header to all messages that are gatewayed to
+# Usenet.
+#
+# legal values are:
+#    0 = "None"
+#    1 = "Open list, moderated group"
+#    2 = "Moderated"
 news_moderation = 0
 
-# Mailman tilføjer normalt en tekst du selv kan tilrette (emne prefix)
-# foran emnefeltet i mail som sendes til listen, og normalt sker dette
-# også for mail som sendes videre til Usenet. Du kan sætte denne
-# indstilling til Nej hvis du ikke ønsker emne prefix tilføjet til mail
-# som sendes til Usenet. Sættes emne prefix for listen til off, vil
-# videresendte meddelelser heller ikke få prefix tilføjet.
+# Mailman prefixes Subject: headers with text you can customize and
+# normally, this prefix shows up in messages gatewayed to Usenet.  You
+# can set this option to No to disable the prefix on gated messages.  Of
+# course, if you turn off normal Subject: prefixes, they won't be
+# prefixed for gated messages either.
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 news_prefix_subject_too = 1
 
 ## Autoreply options
 #
-# Indstillinger for automatiske svar.<p>
+# Auto-responder characteristics.<p>
 # 
-# I tekstboksene nedenfor kan du bruge følgende variabler: (skriv:
-# %(&lt;variabelnavn&gt;)s ) for at indsætte ønsket information: <p><ul>
-# <li><b>listname</b> - <em>navnet p&aring; listen</em>
-# <li><b>listurl</b> - <em>URL til listens webside</em>
-# <li><b>requestemail</b> - <em>listens -request e-mailadresse</em>
-# <li><b>owneremail</b> - <em>listens -owner e-mailadresse</em> </ul>
+# In the text fields below, string interpolation is performed with the
+# following key/value substitutions: <p><ul> <li><b>listname</b> -
+# <em>gets the name of the mailing list</em> <li><b>listurl</b> -
+# <em>gets the list's listinfo URL</em> <li><b>requestemail</b> -
+# <em>gets the list's -request address</em> <li><b>owneremail</b> -
+# <em>gets the list's -owner address</em> </ul>
 # 
-# <p>Du kan enten skrive teksten direkte i tekstboksene, eller du kan
-# angive navnet p&aring; en fil som indeholder teksten. Denne fil vil
-# s&aring; blive indl&aelig;st i tekstboksen, fra dit lokale filsystem.
+# <p>For each text field, you can either enter the text directly into
+# the text box, or you can specify a file on your local system to upload
+# as the text.
 
-# Skal Mailman sende et automatisk svar til dem der sender e-mail til
-# listen?
+# Should Mailman send an auto-response to mailing list posters?
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 autorespond_postings = 0
 
-# Automatisk svar der skal sendes.
+# Auto-response text to send to mailing list posters.
 autoresponse_postings_text = ''
 
-# Skal Mailman sende et automatisk svar p&aring; e-mail der sendes til
-# -owner adressen?
+# Should Mailman send an auto-response to emails sent to the -owner
+# address?
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 autorespond_admin = 0
 
-# Automatisk svar p&aring; e-mail til -owner adressen.
+# Auto-response text to send to -owner emails.
 autoresponse_admin_text = ''
 
-# Skal Mailman sende et automatisk svar p&aring; e-mail der sendes til
-# -request adressen? Hvis du v&aelig;lger ja, kan du ogs&aring;
-# v&aelig;lge om e-mailen der blev sendt til -request adressen skal
-# medtages i det automatiske svar.
+# Should Mailman send an auto-response to emails sent to the -request
+# address?  If you choose yes, decide whether you want Mailman to
+# discard the original email, or forward it on to the system as a normal
+# mail command.
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja, men uden den originale e-mail"
-#    2 = "Ja, og medtag den originale e-mail"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes, w/discard"
+#    2 = "Yes, w/forward"
 autorespond_requests = 0
 
-# Automatisk svar p&aring; e-mail til -request adressen.
+# Auto-response text to send to -request emails.
 autoresponse_request_text = ''
 
-# Antal dage imellem automatisk svar p&aring; e-mail, fra samme
-# afsender, til listen eller til -request/-owner adresserne. S&aelig;t
-# denne v&aelig;rdi til 0 (eller et negativt tal) for at sende
-# automatisk svar hver gang.
+# Number of days between auto-responses to either the mailing list or
+# -request/-owner address from the same poster.  Set to zero (or
+# negative) for no grace period (i.e. auto-respond to every message).
 autoresponse_graceperiod = 90
 
 ## Contentfilter options
 #
-# Regler for indhold i e-mail sendt til listen.
-# 
-# <p>Filtrering af indhold fungerer således: når listen modtager en
-# e-mail og du har beskyttelse med filtrering af indhold aktiveret,
-# sammenlignes først eventuelle vedh&aelig;ftninger med <a
-# href="?VARHELP=contentfilter/filter_mime_types">MIME filtrene</a>.
-# Hvis en vedh&aelig;ftning passer med et af disse filtre, bliver
-# vedh&aelig;ftningen fjernet.
-# 
-# <p>Derefter sammenlignes eventuelle vedh&aelig;ftninger med <a
-# href="?VARHELP=contentfilter/pass_mime_types">gyldige MIME typer</a>,
-# hvis nogen er defineret. Alle vedh&aelig;ftninger som ikke stemmer
-# overens med de angivne MIME typer, bliver fjernet.
-# 
-# <p>Efter filtreringen vil alle tomme <tt>multipart</tt>
-# vedh&aelig;ftninger v&aelig;re fjernet. Hvis selve meddelelsen er helt
-# tom efter denne filtrering, vil meddelelsen blive afvist. Derefter vil
-# enhver <tt>multipart/alternative</tt> vedh&aelig;ftning blive
-# erstattet af den første alternative som ikke er tom.
-# 
-# <p>Til sidst vil alle <tt>text/html</tt> vedh&aelig;ftninger som måtte
-# v&aelig;re tilbage i meddelelsen blive konverteret til
-# <tt>text/plain</tt> hvis <a
-# href="?VARHELP=contentfilter/convert_html_to_plaintext">konverter til
-# ren tekst</a> er sat til og serveren er konfigureret til at tillade
-# sådanne konverteringer.
-
-# Skal Mailman filtrere indhold i e-mail sendt til listen som angivet
-# nedenfor?
-#
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# Policies concerning the content of list traffic.
+# 
+# <p>Content filtering works like this: when a message is received by
+# the list and you have enabled content filtering, the individual
+# attachments are first compared to the <a
+# href="?VARHELP=contentfilter/filter_mime_types">filter types</a>.  If
+# the attachment type matches an entry in the filter types, it is
+# discarded.
+# 
+# <p>Then, if there are <a
+# href="?VARHELP=contentfilter/pass_mime_types">pass types</a> defined,
+# any attachment type that does <em>not</em> match a pass type is also
+# discarded.  If there are no pass types defined, this check is skipped.
+# 
+# <p>After this initial filtering, any <tt>multipart</tt> attachments
+# that are empty are removed.  If the outer message is left empty after
+# this filtering, then the whole message is discarded.
+# 
+# <p> Then, each <tt>multipart/alternative</tt> section will be replaced
+# by just the first alternative that is non-empty after filtering if <a
+# href="?VARHELP=contentfilter/collapse_alternatives"
+# >collapse_alternatives</a> is enabled.
+# 
+# <p>Finally, any <tt>text/html</tt> parts that are left in the message
+# may be converted to <tt>text/plain</tt> if <a
+# href="?VARHELP=contentfilter/convert_html_to_plaintext"
+# >convert_html_to_plaintext</a> is enabled and the site is configured
+# to allow these conversions.
+
+# Should Mailman filter the content of list traffic according to the
+# settings below?
+#
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 filter_content = 0
 
-# Brug denne indstilling til at fjerne vedh&aelig;ftninger der passer
-# til MIME typer. Hver linie skal her indeholde navnet på en MIME
-# type/subtype, f.eks. image/gif. Hvis du ønsker at fjerne alle
-# vedh&aelig;ftninger som har en given hoved MIME type, kan du undlade
-# at angive subtype, f.eks. image.
+# Use this option to remove each message attachment that matches one of
+# these content types.  Each line should contain a string naming a MIME
+# type/subtype, e.g. image/gif.  Leave off the subtype to remove all
+# parts with a matching major content type, e.g. image.
 # 
-# Tomme linier medtages ikke.
+# Blank lines are ignored.
 # 
-# Se også gyldige MIME typer for whitelist af MIME typer.
+# See also <a href="?VARHELP=contentfilter/pass_mime_types"
+# >pass_mime_types for a content type whitelist.
 filter_mime_types = ''
 
-# Brug denne indstilling for at definere hvilke MIME typer der skal være
-# tilladt. Krav og format for filtrering er identisk med MIME filtre.
+# Use this option to remove each message attachment that does not have a
+# matching content type.  Requirements and formats are exactly like <a
+# href="?VARHELP=contentfilter/filter_mime_types" >filter_mime_types.
 # 
-# Bem&aelig;rk: hvis du lægger noget ind her, men ikke angiver
-# multipart, vil ingen e-mail med vedh&aelig;ftninger blive medtaget.
+# Note: if you add entries to this list but don't add multipart to this
+# list, any messages with attachments will be rejected by the pass
+# filter.
 pass_mime_types = """multipart/mixed
 multipart/alternative
 text/plain"""
 
-# Skal Mailman konvertere text/html dele til ren tekst? Denne
-# konvertering vil finde sted efter at MIME filteret har fjernet de
-# uønskede dele.
+# Remove message attachments that have a matching filename extension.
+filter_filename_extensions = """exe
+bat
+cmd
+com
+pif
+scr
+vbs
+cpl"""
+
+# Remove message attachments that don't have a matching filename
+# extension.  Leave this field blank to skip this filter test.
+pass_filename_extensions = ''
+
+# Should Mailman collapse multipart/alternative to its first part
+# content?
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
+collapse_alternatives = True
+
+# Should Mailman convert text/html parts to plain text?  This conversion
+# happens after MIME attachments have been stripped.
+#
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 convert_html_to_plaintext = 1
 
-# Her bestemmer du hvad der skal ske, når en meddelelse filtreres fra af
-# et filter, altså hvis vedh&aelig;ftningen filtreres fra af MIME
-# filteret, eller en vedh&aelig;ftning ikke har en af de gyldige MIME
-# typer, eller meddelelsen ender med at være tom efter filtrering.
-# 
-# Bemærk at det du vælger her ikke vil ske hvis en meddelelse stadig
-# indeholder noget efter filtrering. Så vil meddelelsen altid blive
-# sendt videre til listen.
-# 
-# Når meddelelsen afvises, skrives Message-ID for den afviste meddelelse
-# til loggen. Når meddelelsen sendes retur eller videresendes til
-# listens ejer, vil en begrundelse altid blive inkluderet i den
-# returmail der sendes til afsenderen. Når meddelelserne skal bevares,
-# gemmes de i et specielt køkatalog på disken, sådan at
-# serveradministrator kan se (og måske gøre noget med) dem, men bliver
-# ellers fjernet. Dette sidste valg er kun tilgængeligt hvis
-# serveradministrator har tilladt det.
-#
-# gyldige værdier:
-#    0 = "Slet"
-#    1 = "Afvis"
-#    2 = "Videresend til Listens Ejer"
-#    3 = "Bevar"
+# One of these actions is taken when the message matches one of the
+# content filtering rules, meaning, the top-level content type matches
+# one of the <a href="?VARHELP=contentfilter/filter_mime_types"
+# >filter_mime_types, or the top-level content type does not match one
+# of the <a href="?VARHELP=contentfilter/pass_mime_types"
+# >pass_mime_types, or if after filtering the subparts of the message,
+# the message ends up empty.
+# 
+# Note this action is not taken if after filtering the message still
+# contains content.  In that case the message is always forwarded on to
+# the list membership.
+# 
+# When messages are discarded, a log entry is written containing the
+# Message-ID of the discarded message.  When messages are rejected or
+# forwarded to the list owner, a reason for the rejection is included in
+# the bounce message to the original author.  When messages are
+# preserved, they are saved in a special queue directory on disk for the
+# site administrator to view (and possibly rescue) but otherwise
+# discarded.  This last option is only available if enabled by the site
+# administrator.
+#
+# legal values are:
+#    0 = "Discard"
+#    1 = "Reject"
+#    2 = "Forward to List Owner"
+#    3 = "Preserve"
 filter_action = 0
 
 ## Topics options
 #
-# Emneord for listen
-
-# Emnefilteret kategoriserer hver e-mail som kommer til listen, efter de
-# regexp-udtryk du skriver nedenfor. Hvis felterne Subject: eller
-# Keywords: i brevhovedet i en mail stemmer overens med et af disse
-# udtryk, bliver mailen placeret under det p&aring;g&aelig;ldende emne.
-# Hvert medlem af listen kan vælge kun at modtage mail der passer til de
-# &oslash;nskede emner. E-mail som ikke h&oslash;rer under noget emne,
-# bliver ikke leveret.
-# 
-# Bem&aeligrk: Dette fungerer kun i normal-modus, ikke i
-# sammendrag-modus.
-# 
-# Indholdet i meddelelsen kan ogs&aring; unders&oslash;ges for Subject:
-# og Keyword: felter, alt efter hvad indstillingen
-# topics_bodylines_limit er sat til.
+# List topic keywords
+
+# The topic filter categorizes each incoming email message according to
+# <a href="http://www.python.org/doc/current/lib/module-re.html">regular
+# expression filters you specify below.  If the message's Subject: or
+# Keywords: header contains a match against a topic filter, the message
+# is logically placed into a topic bucket.  Each user can then choose to
+# only receive messages from the mailing list for a particular topic
+# bucket (or buckets).  Any message not categorized in a topic bucket
+# registered with the user is not delivered to the list.
+# 
+# Note that this feature only works with regular delivery, not digest
+# delivery.
+# 
+# The body of the message can also be optionally scanned for Subject:
+# and Keywords: headers, as specified by the <a
+# href="?VARHELP=topics/topics_bodylines_limit">topics_bodylines_limit
+# configuration variable.
 #
-# gyldige værdier:
-#    0 = "Ikke tilgængeligt"
-#    1 = "Tilgængeligt"
+# legal values are:
+#    0 = "Disabled"
+#    1 = "Enabled"
 topics_enabled = 0
 
-# Her angiver du hvor mange linier af mailens indhold emnefilteret skal
-# gennems&oslash;ge. En s&oslash;gning stopper n&aring;r det antal
-# linier er gennems&oslash;gt, eller n&aring;r den m&oslash;der en linie
-# som ikke ligner et brevhoved-felt. S&aelig;ttes denne v&aelig;rdi til
-# nul (0), vil ingen linier i indholdet blive unders&oslash;gt (dvs. kun
-# Keywords: og Subject: i brevhovedet unders&oslash;ges). S&aelig;ttes
-# denne v&aelig;rdi til et negativt tal, vil alle linier blive
-# unders&oslash;gt frem til den f&oslash;rste linie som ikke ligner et
-# brevhoved-felt.
+# The topic matcher will scan this many lines of the message body
+# looking for topic keyword matches.  Body scanning stops when either
+# this many lines have been looked at, or a non-header-like body line is
+# encountered.  By setting this value to zero, no body lines will be
+# scanned (i.e. only the Keywords: and Subject: headers will be
+# scanned).  By setting this value to a negative number, then all body
+# lines will be scanned until a non-header-like line is encountered.
+# 
 topics_bodylines_limit = 5
 
-# Hvert emneord er faktisk et regexp-udtryk, der sammenlignes med dele
-# af mailen, nemlig felterne Keywords: og Subject: i brevhovedet.
-# Bem&aelig;rk at de f&oslash;rste linier i mailens indhold ogs&aring;
-# kan best&aring; af s&aring;danne "felter", og de kan dermed ogs&aring;
-# blive unders&oslash;gt.
+# Each topic keyword is actually a regular expression, which is matched
+# against certain parts of a mail message, specifically the Keywords:
+# and Subject: message headers. Note that the first few lines of the
+# body of the message can also contain a Keywords: and Subject: "header"
+# on which matching is also performed.
 topics = []
 
diff --git a/mailman/nyheder.members b/mailman/nyheder.members
index f4bd303..4479bf5 100644
--- a/mailman/nyheder.members
+++ b/mailman/nyheder.members
@@ -14,7 +14,6 @@ Brian Pedersen <brianpadk@yahoo.com>
 Chris Larsen <chris_larsen@hotmail.com>
 Laila Mortensen <clc@oncable.dk>
 Clara Okoy <cno@deutero.dk>
-Jonas Smedegaard <dr@jones.dk>
 Ivan Dybvad <dybvad@post9.tele.dk>
 Flemming Moelgaard <flemming.moelgaard@dgi.dk>
 Henriette Bjerrum <henriette.bjerrum@dgi.dk>
diff --git a/mailman/nyheder.py b/mailman/nyheder.py
index 2815dec..f47d25a 100644
--- a/mailman/nyheder.py
+++ b/mailman/nyheder.py
@@ -1,384 +1,371 @@
-## Indstillinger for maillisten "nyheder"  -*- python -*-
-## Dato: Sun Dec 11 16:36:05 2005
+# -*- python -*-
+# -*- coding: us-ascii -*-
+## "nyheder" mailing list configuration settings
+## captured on Tue Mar 20 08:52:27 2007
 
 ## General options
 #
-# Grundlæggende egenskaber for listen, herunder en beskrivelse af
-# listen. 
-
-# Du kan f.eks. stave navnet med stort forbogstav eller ændre andre
-# bogstaver til store, s&aring; navnet bliver udtalt rigtigt eller at
-# forkortelser fremhæves. Bemærk at dette navn bruges i e-maillistens
-# adresse (f.eks. i bekræftelser ved tilmeldinger), s&aring; navnet kan
-# ikke ændres p&aring; nogen anden m&aring;de. (e-mailadresser er ikke
-# f&oslash;lsomme for store eller sm&aring; bogstaver, men de er
-# f&oslash;lsomme for n&aelig;sten alt andet :-)
+# Fundamental list characteristics, including descriptive info and basic
+# behaviors.
+
+# The capitalization of this name can be changed to make it presentable
+# in polite company as a proper noun, or to make an acronym part all
+# upper case, etc.  However, the name will be advertised as the email
+# address (e.g., in subscribe confirmation notices), so it should not be
+# otherwise altered.  (Email addresses are not case sensitive, but they
+# are sensitive to almost everything else :-)
 real_name = 'Nyheder'
 
-# Der er to roller forbundet med hver mailliste. Listeadministratorerne
-# er dem der som sidste instans har kontrol over alle indstillingerne
-# for maillisten. De kan &aelig;ndre alle indstillinger der er
-# tilg&aelig;ngelige via disse administrative websider.
-# 
-# Listemoderatorerne har begrænset adgang; de kan ikke ændre
-# indstillinger for e-maillisten, men de kan tage sig af anmodninger i
-# forbindelse med listen, f.eks. anmodning om medlemskab, eller
-# godkende/afvise meddelelser der skal godkendes for at kunne udsendes
-# til listen. Listeadministratorerne kan ogs&aring; udf&oslash;re disse
-# opgaver.
-# 
-# For at aktivere muligheden for at have listemoderatorer, og p&aring;
-# den m&aring;de fordele arbejdsopgaverne i forbindelse med listen, skal
-# du anf&oslash;re din egen moderatoradgangskode, og angive
-# e-mailadresser for den/dem som skal v&aelig;re listemoderator(er).
-# Bemærk at i tekstboksene nedenfor skal du skrive e-mailadresser for
-# listeadministratorer.
+# There are two ownership roles associated with each mailing list.  The
+# list administrators are the people who have ultimate control over all
+# parameters of this mailing list.  They are able to change any list
+# configuration variable available through these administration web
+# pages.
+# 
+# The list moderators have more limited permissions; they are not able
+# to change any list configuration variable, but they are allowed to
+# tend to pending administration requests, including approving or
+# rejecting held subscription requests, and disposing of held postings.
+# Of course, the list administrators can also tend to pending requests.
+# 
+# In order to split the list ownership duties into administrators and
+# moderators, you must set a separate moderator password, and also
+# provide the email addresses of the list moderators.  Note that the
+# field you are changing here specifies the list administrators.
 owner = ['dr@jones.dk']
 
-# Der er to ejer-roller forbundet med hver mailliste.
-# Listeadministratorerne er dem der har den endelige kontrol over alle
-# indstillingerne for e-mallisten. De kan &aelig;ndre alle indstillinger
-# der er tilgængelige via disse administrative websider.
-# 
-# Listemoderatorerne har begr&aelig;nset adgang; de kan ikke &aelig;ndre
-# indstillinger for e-maillisten, men de kan tage sig af anmodninger
-# ang&aring;ende listen, f.eks. anmodning om medlemskab, eller
-# godkende/afvise meddelelser der skal godkendes for at kunne udsendes
-# p&aring; listen. Listeadministratorerne kan selvsagt ogs&aring;
-# udf&oslash;re disse opgaver.
-# 
-# For at aktivere muligheden for at have listemoderatorer, og p&aring;
-# den m&aring;de fordele arbejdsopgaverne i forbindelse med listen, skal
-# du anf&oslash;re din egen moderatoradgangskode, og indtaste
-# e-mailadresser for den/dem der skal v&aelig;re listemoderatore(r).
-# Bemærk, at i tekstboksene nedenfor skal du skrive listemoderator
-# e-mailadresse(r).
+# There are two ownership roles associated with each mailing list.  The
+# list administrators are the people who have ultimate control over all
+# parameters of this mailing list.  They are able to change any list
+# configuration variable available through these administration web
+# pages.
+# 
+# The list moderators have more limited permissions; they are not able
+# to change any list configuration variable, but they are allowed to
+# tend to pending administration requests, including approving or
+# rejecting held subscription requests, and disposing of held postings.
+# Of course, the list administrators can also tend to pending requests.
+# 
+# In order to split the list ownership duties into administrators and
+# moderators, you must set a separate moderator password, and also
+# provide the email addresses of the list moderators in this section.
+# Note that the field you are changing here specifies the list
+# moderators.
 moderator = ['sf@dgi-huset.dk', 'tk@dgi-huset.dk']
 
-# Denne beskrivelse benyttes n&aring;r denne malliste listes op sammen
-# med andre maillister, i toptekster, osv. Den b&oslash;r v&aelig;re
-# s&aring; kort som overhovedet mulig, uden at det bliver uklart hvad
-# meningen med maillisten er eller hvad den skal bruges til.
+# This description is used when the mailing list is listed with other
+# mailing lists, or in headers, and so forth.  It should be as succinct
+# as you can get it, while still identifying what the list is.
 description = 'Nyheder om DGI-huset i &#197;rhus'
 
-# Teksten tolkes som html bortset fra linieskift, der vil blive
-# &aelig;ndret til html-tag'et '<br>', sådan at du kan benytte links,
-# forh&aring;ndsformateret tekst, osv. Men brug alts&aring; kun
-# linieskift der hvor du vil have et nyt afsnit. V&aelig;r meget
-# omhyggelig, hvis du benytter html-kode. Fejl (f.eks. manglende
-# slut-tag's) kan f&oslash;re til at listens informationsside ikke
-# bliver vist s&aring;dan som den skal.
+# The text will be treated as html except that newlines will be
+# translated to <br> - so you can use links, preformatted text, etc, but
+# don't put in carriage returns except where you mean to separate
+# paragraphs.  And review your changes - bad html (like some
+# unterminated HTML constructs) can prevent display of the entire
+# listinfo page.
 info = """Nyheder om DGI-huset i &#197;rhus.
 
 &#197;ben for tilmelding. Offentligt tilg&#230;ngeligt arkiv. Kun DGI-huset kan sende til listen."""
 
 # This text will be prepended to subject lines of messages posted to the
-# list, to distinguish mailing list messages in in mailbox summaries.
+# list, to distinguish mailing list messages in mailbox summaries.
 # Brevity is premium here, it's ok to shorten long mailing list names to
 # something more concise, as long as it still identifies the mailing
-# list.
+# list. You can also add a sequential number by %d substitution
+# directive. eg.; [listname %d] -> [listname 123] (listname %05d) ->
+# (listname 00123)
+# 
 subject_prefix = '[Nyheder] '
 
-# Skjul afsenderen af meddelelser, ved at erstatte den med e-maillistens
-# adresse (Dette medfører at alle From:, Sender, og Reply-To: felter
-# fjernes)
+# Hide the sender of a message, replacing it with the list address
+# (Removes From, Sender and Reply-To fields)
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 anonymous_list = 1
 
-# Skal eksisterende Reply-To: felt i brevhovedet fjernes? Hvis ja, vil
-# dette blive gjort uanset om Mailman tilføjer et Reply-To: felt eller
-# ikke.
+# Should any existing Reply-To: header found in the original message be
+# stripped?  If so, this will be done regardless of whether an explict
+# Reply-To: header is added by Mailman or not.
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 first_strip_reply_to = 1
 
-# Denne indstillling fort&aelig;ller hvad Mailman skal g&oslash;re med
-# Reply-To: feltet i brevhovedet p&aring; e-mail der sendes til listen.
-# Hvis den er sat til Afsender, vil Mailman ikke tilf&oslash;je noget
-# Reply-To: felt, men findes et s&aring;dant felt allerede, vil det ikke
-# blive fjernet. S&aelig;ttes indstillingen til enten e-maillistens
-# adresse eller Egendefineret adresse, vil Mailman tilf&oslash;je, evt.
-# erstatte, et Reply-To: felt. (Egendefineret adresse inds&aelig;tter
-# v&aelig;rdien af indstillingen reply_to_address).
-# 
-# Der er flere grunde til ikke at indf&oslash;re eller erstatte
-# Reply-To: felter. En grund kan v&aelig;re at nogen af dem der sender
-# mail til listen er afh&aelig;ngige af selv at kunne s&aelig;tte
-# Reply-To: adressen. En anden grund er at modifikation af Reply-To:
-# adressen g&oslash;r det vanskeligere kun at sende svar til afsender.
-# Se 'Reply-To' Munging Considered Harmful for en diskussion omkring
-# emnet. Se Reply-To Munging Considered Useful for modsatte meninger.
-# 
-# Nogle maillister har begr&aelig;nset adgang, med en parallel liste
-# beregnet til diskussioner. Eksempler p&aring; dette er 'patches' eller
-# 'checkin' lister, som system for revisionskontrol sender
-# &aelig;ndringer i programmet til, men diskussioner omkring udvikling
-# af programmet sendes til udviklernes egen mailliste. For at
-# underst&oslash;tte lignende e-maillister, v&aelig;lg Egendefineret
-# adresse og s&aelig;t Reply-To: adressen i indstillingen
-# reply_to_address til at pege på den parallelle diskussionsliste.
-#
-# gyldige værdier:
-#    0 = "Afsender"
-#    1 = "mail listens adresse"
-#    2 = "Egendefineret adresse"
+# This option controls what Mailman does to the Reply-To: header in
+# messages flowing through this mailing list.  When set to Poster, no
+# Reply-To: header is added by Mailman, although if one is present in
+# the original message, it is not stripped.  Setting this value to
+# either This list or Explicit address causes Mailman to insert a
+# specific Reply-To: header in all messages, overriding the header in
+# the original message if necessary (Explicit address inserts the value
+# of <a href="?VARHELP=general/reply_to_address">reply_to_address).
+# 
+# There are many reasons not to introduce or override the Reply-To:
+# header.  One is that some posters depend on their own Reply-To:
+# settings to convey their valid return address.  Another is that
+# modifying Reply-To: makes it much more difficult to send private
+# replies.  See <a
+# href="http://www.unicom.com/pw/reply-to-harmful.html">`Reply-To'
+# Munging Considered Harmful for a general discussion of this issue.
+# See <a
+# href="http://www.metasystema.net/essays/reply-to.mhtml">Reply-To
+# Munging Considered Useful for a dissenting opinion.
+# 
+# Some mailing lists have restricted posting privileges, with a parallel
+# list devoted to discussions.  Examples are `patches' or `checkin'
+# lists, where software changes are posted by a revision control system,
+# but discussion about the changes occurs on a developers mailing list.
+# To support these types of mailing lists, select Explicit address and
+# set the Reply-To: address below to point to the parallel list.
+#
+# legal values are:
+#    0 = "Poster"
+#    1 = "This list"
+#    2 = "Explicit address"
 reply_goes_to_list = 2
 
-# Her definerer du adressen der skal s&aelig;ttes i Reply-To: feltet
-# n&aring;r indstillingen reply_goes_to_list er sat til Egendefineret
-# adresse.
-# 
-# Der findes mange grunde til at ikke indf&oslash;re eller erstatte
-# Reply-To: felter. En grund kan v&aelig;re at nogen af dem der sender
-# e-mail til listen er afh&aelig;ngige af selv at kunne s&aelig;tte
-# Reply-To: adressen. En anden grund er at modificering af Reply-To:
-# adressen g&oslash;r det vanskeligere at sende svar kun til afsender.
-# Se 'Reply-To' Munging Considered Harmful for en diskussion omkring
-# temaet. Se Reply-To Munging Considered Useful for modsatte meninger.
-# 
-# Nogle maillister har begr&aelig;nset adgang, med en egen parallel
-# liste beregnet for diskussioner. Eksempler p&aring; dette er 'patches'
-# eller 'checkin' lister, som system for revisionskontrol sender
-# &aelig;ndringer i programmet til, mens diskussioner omkring udvikling
-# af programmet sendes til udviklernes egen mailliste. For at
-# underst&oslash;tte s&aring;danne maillister, kan du definere Reply-To:
-# adressen her, og vælge Egendefineret adresse i indstillingen
-# reply_goes_to_list.
-# 
-# Bem&aelig;rk at hvis den oprindelige meddelelse indeholder et
-# Reply-To: felt, vil det ikke &aelig;ndres.
+# This is the address set in the Reply-To: header when the <a
+# href="?VARHELP=general/reply_goes_to_list">reply_goes_to_list option
+# is set to Explicit address.
+# 
+# There are many reasons not to introduce or override the Reply-To:
+# header.  One is that some posters depend on their own Reply-To:
+# settings to convey their valid return address.  Another is that
+# modifying Reply-To: makes it much more difficult to send private
+# replies.  See <a
+# href="http://www.unicom.com/pw/reply-to-harmful.html">`Reply-To'
+# Munging Considered Harmful for a general discussion of this issue.
+# See <a
+# href="http://www.metasystema.net/essays/reply-to.mhtml">Reply-To
+# Munging Considered Useful for a dissenting opinion.
+# 
+# Some mailing lists have restricted posting privileges, with a parallel
+# list devoted to discussions.  Examples are `patches' or `checkin'
+# lists, where software changes are posted by a revision control system,
+# but discussion about the changes occurs on a developers mailing list.
+# To support these types of mailing lists, specify the explicit
+# Reply-To: address here.  You must also specify Explicit address in the
+# reply_goes_to_list variable.
+# 
+# Note that if the original message contains a Reply-To: header, it will
+# not be changed.
 reply_to_address = 'info@dgi-huset.dk'
 
-# V&aelig;lg kun 'ja' her, hvis listen skal bruges som  "paraply" for
-# andre lister. Hvis 'ja' er valgt, vil bekr&aelig;ftelser og
-# meddelelser med adgangskode blive sendt til en adresse som konstrueres
-# ud fra medlemmets e-mailadresse - v&aelig;rdien af indstillingen
-# "umbrella_member_suffix" tilf&oslash;jes medlemmets kontonavn (det som
-# st&aring;r f&oslash;r @-tegnet).
+# Set this to yes when this list is intended to cascade only to other
+# mailing lists.  When set, meta notices like confirmations and password
+# reminders will be directed to an address derived from the member's
+# address - it will have the value of "umbrella_member_suffix" appended
+# to the member's account name.
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 umbrella_list = 0
 
-# N&aring;r "umbrella_list" indikerer at denne liste har andre
-# maillister som medlemmer, skal administrative meddelelser som f.eks.
-# bekr&aelig;ftelser og p&aring;mindelser om adgangskode ikke sendes til
-# selve listen, men snarere til administrator for listen. V&aelig;rdien
-# af denne indstilling bestemmer, hvilken adresse administrative
-# meddelelser skal sendes til. '-owner' er et almindeligt valg for denne
-# indstilling. Denne indstilling har ingen effekt n&aring;r
-# "umbrella_list" er sat til "Nej".
+# When "umbrella_list" is set to indicate that this list has other
+# mailing lists as members, then administrative notices like
+# confirmations and password reminders need to not be sent to the member
+# list addresses, but rather to the owner of those member lists.  In
+# that case, the value of this setting is appended to the member's
+# account name for such notices.  `-owner' is the typical choice.  This
+# setting has no effect when "umbrella_list" is "No".
 umbrella_member_suffix = '-owner'
 
-# Aktiver denne, hvis der skal sendes en p&aring;mindelse om adgangskode
-# til medlemmerne en gang hver m&aring;ned. Husk at medlemmerne
-# ogs&aring; selv kan frav&aelig;lge dette.
+# Turn this on if you want password reminders to be sent once per month
+# to your members.  Note that members may disable their own individual
+# password reminders.
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 send_reminders = 0
 
-# Tekst du skriver her vil blive tilf&oslash;jet &oslash;verst i
-# velkomsthilsenen der sendes til nye medlemmer. Velkomshilsenen
-# indeholder i forvejen vigtige adresser og URLer knyttet til
-# maillisten, s&aring; den slags information er det ikke
-# n&oslash;dvendigt at inkludere her. Her kan du tilf&oslash;je f.eks.
-# oplysning om etikette eller regler for brug af listen, o.l.
-# 
-# Bem&aelig;rk: Linierne i denne tekst vil brydes efter f&oslash;lgende
-# regler:
+# This value, if any, will be added to the front of the new-subscriber
+# welcome message.  The rest of the welcome message already describes
+# the important addresses and URLs for the mailing list, so you don't
+# need to include any of that kind of stuff here.  This should just
+# contain mission-specific kinds of things, like etiquette policies or
+# team orientation, or that kind of thing.
 # 
-# Hvert afsnit udfyldes s&aringdan at ingen linie er l&aelig;ngere en 70
-# tegn. Enhver linie der begynder med tomme tegn udfyldes ikke. Tomme
-# linier adskiller afsnit.
+# Note that this text will be wrapped, according to the following rules:
+# Each paragraph is filled so that no line is longer than 70 characters.
+# Any line that begins with whitespace is not filled. A blank line
+# separates paragraphs.
 # 
 welcome_msg = ''
 
-# S&aelig;t kun denne til 'Nej' hvis du skal tilf&oslash;je nye
-# medlemmer manuelt, og ikke vil have at de f&aring;r det at vide. Dette
-# er meget nyttigt n&aring;r man g&aring;r fra et andet mallistesystem
-# og til Mailman, og vil have at overgangen skal v&aelig;re s&aring;
-# lidt m&aelig;rkbar som muligt.
+# Turn this off only if you plan on subscribing people manually and
+# don't want them to know that you did so.  This option is most useful
+# for transparently migrating lists from some other mailing list manager
+# to Mailman.
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 send_welcome_msg = 1
 
-# Tekst der sendes til medlemmer der framelder sig listen. Hvis feltet
-# er tomt, tilf&oslash;jes der ikke nogen speciel tekst til
-# frameldingen.
+# Text sent to people leaving the list.  If empty, no special text will
+# be added to the unsubscribe message.
 goodbye_msg = ''
 
-# Send afskedshilsen til medlemmer n&aring;r de frameldes?
+# Send goodbye message to members when they are unsubscribed?
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 send_goodbye_msg = 1
 
-# Der udsendes en p&aring;mindelse til listemoderator (og
-# listeadministrator) dagligt om anmodninger der af en eller anden grund
-# venter p&aring; behandling. V&aelig;lger du "Ja", vil
-# listeadminstrator ogs&aring; modtage en meddelelse s&aring; snart en
-# anmodning ankommer.
+# List moderators (and list administrators) are sent daily reminders of
+# requests pending approval, like subscriptions to a moderated list, or
+# postings that are being held for one reason or another.  Setting this
+# option causes notices to be sent immediately on the arrival of new
+# requests as well.
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 admin_immed_notify = 1
 
-# Skal listeadministrator modtage meddelelse om tilmeldinger og
-# afmeldinger?
+# Should administrator get notices of subscribes and unsubscribes?
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 admin_notify_mchanges = 1
 
-# Approval notices are sent when mail triggers certain of the limits
-# except routine list moderation and spam filters, for which notices are
-# not sent.  This option overrides ever sending the notice.
+# Send mail to poster when their posting is held for approval?
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 respond_to_post_requests = 1
 
-# Når dette valg er aktiveret, vil al e-mail til listen blive modereret.
-# Dette valg kan være nyttigt når din mailliste f.eks. har en såkaldt
-# "flamewar", altså en "krig" hvor medlemmer kun skælder ud på hinanden.
-# En "nød-moderering" kan da hjælpe dig at fjerne usaglige meddelelser
-# til listen, og på den måde dysse en ophedet diskussion ned.
+# When this option is enabled, all list traffic is emergency moderated,
+# i.e. held for moderation.  Turn this option on when your list is
+# experiencing a flamewar and you want a cooling off period.
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 emergency = 0
 
-# Når et nyt medlem tilmeldes listen, bliver medlemmets indstillinger
-# taget herfra.
+# When a new member is subscribed to this list, their initial set of
+# options is taken from the this variable's setting.
 new_member_options = 260
 
-# Filter for administrative meddelelser vil unders&oslash;ge om
-# meddelelsen egentligt er ment som en administrativ anmodning (f.eks.
-# tilmelding, framelding, o.l.), og i s&aring; fald sende meddelelsen
-# til listeadministrator i stedet for.
+# Administrivia tests will check postings to see whether it's really
+# meant as an administrative request (like subscribe, unsubscribe, etc),
+# and will add it to the the administrative requests queue, notifying
+# the administrator of the new request, in the process.
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 administrivia = 0
 
-# Maximum st&oslash;rrelse i kilobytes (KB) for indholdet i e-mail der
-# sendes til listen. Brug v&aelig;rdien '0' for ikke at have nogen
-# begr&aelig;nsning.
+# Maximum length in kilobytes (KB) of a message body.  Use 0 for no
+# limit.
 max_message_size = 0
 
-# "Maskinnavnet" er det navn som skal benyttes for e-mailadresser
-# relateret til Mailman p&aring; denne maskine, og er normalt navnet der
-# er forbundet med e-mail-servicen p&aring; maskinen. Denne indstilling
-# kan v&aelig;re nyttig hvis maskinen har flere navne.
+# The "host_name" is the preferred name for email to mailman-related
+# addresses on this host, and generally should be the mail host's
+# exchanger address, if any.  This setting can be useful for selecting
+# among alternative names of a host that has multiple addresses.
 host_name = 'dgi-huset.dk'
 
-# I RFC 2369 defineres en r&aelig;kke List-* felter i brevhovedet, der
-# normalt tilf&oslash;jes enhver meddelelse der sendes ud via listen.
-# Disse felter er til stor gavn for brugere , som benytter et
-# e-mailprogram der f&oslash;lger standarden. Disse felter b&oslash;r
-# derfor altid v&aelig;re med.
-# 
-# Ikke alle e-mailprogrammer f&oslash;lger denne standard. Hvis der er
-# mange medlemmer p&aring; listen, der benytter e-mailprogrammer, der
-# ikke kan h&aring;ndtere disse felter i brevhovedet, kan du v&aelig;lge
-# at udelade dem. Men du b&oslash;r f&oslash;rst fors&oslash;ge at
-# l&aelig;re og forklare medlemmerne hvad hensigten med s&aring;danne
-# felter er, og hvordan de kan skjule dem i deres e-mailprogram. Som en
-# sidste udvej kan du udelade felterne, men det anbefales ikke (og denne
-# mulighed kan faktisk ogs&aring; blive fjernet i senere versioner af
-# Mailman).
-#
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# RFC 2369 defines a set of List-* headers that are normally added to
+# every message sent to the list membership. These greatly aid end-users
+# who are using standards compliant mail readers.  They should normally
+# always be enabled.
+# 
+# However, not all mail readers are standards compliant yet, and if you
+# have a large number of members who are using non-compliant mail
+# readers, they may be annoyed at these headers.  You should first try
+# to educate your members as to why these headers exist, and how to hide
+# them in their mail clients.  As a last resort you can disable these
+# headers, but this is not recommended (and in fact, your ability to
+# disable these headers may eventually go away).
+#
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 include_rfc2369_headers = 1
 
-# List-Post: feltet er et af felterne anbefalet i RFC 2369. P&aring;
-# nogle e-maillister (som f.eks. kun bruges til
-# offentligg&oslash;relser), er det kun bestemte personer der har lov
-# til at poste til listen. Almindelige medlemmer af listen har normalt
-# ikke lov til at poste til listen. For den slags lister, er List-Post:
-# feltet misvisende. S&aelig;t denne indstilling til Nej, for at
-# undg&aring; at feltet tilf&oslash;jes. (Dette p&aring;virker ikke
-# andre List-*: felter.)
-#
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# The List-Post: header is one of the headers recommended by RFC 2369.
+# However for some announce-only mailing lists, only a very select group
+# of people are allowed to post to the list; the general membership is
+# usually not allowed to post.  For lists of this nature, the List-Post:
+# header is misleading. Select No to disable the inclusion of this
+# header. (This does not affect the inclusion of the other List-*:
+# headers.)
+#
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 include_list_post_header = 1
 
+# Discard held messages older than this number of days. Use 0 for no
+# automatic discarding.
+max_days_to_hold = 0
+
 ## Language options
 #
-# Underst&oslash;ttelse af flere sprog. (Internationalisering)
-
-# Dette er standardsproget som benyttes for denne mailliste. Hvis flere
-# end et sprog/ underst&oslash;ttes, vil medlemmer af listen selv kunne
-# v&aelig;lge hvilket sprog der skal benyttes n&aring;r de g&aring;r ind
-# p&aring; deres personlige webside, og n&aring;r meddelelser fra
-# systemet sendes til dem. Hvis medlemmerne ikke &aelig;ndrer noget
-# selv, vil dette standardsprog blive benyttet. Dette g&aelig;lder
-# b&aring;de web-baserede og e-mail-baserede meddelelser, men ikke
-# meddelelser sendt af listens medlemmer.
+# Natural language (internationalization) options.
+
+# This is the default natural language for this mailing list. If more
+# than one language is supported then users will be able to select their
+# own preferences for when they interact with the list.  All other
+# interactions will be conducted in the default language.  This applies
+# to both web-based and email-based messages, but not to email posted by
+# list members.
 preferred_language = 'en'
 
-# Her er alle sprog, som denne liste har underst&oslash;ttelse for.
-# Bem&aelig;rk at standardsproget skal v&aelig;re med.
+# These are all the natural languages supported by this list. Note that
+# the default language must be included.
 available_languages = ['en', 'da']
 
-# Hvis standardsproget for din mailliste benytter et andet tegns&aelig;t
-# end ASCII og Emne prefixet for listen indeholder tegn som ikke findes
-# i ASCII-tegns&aelig;ttet, vil prefixet altid blive kodet i henhold til
-# den relevante standard. Hvis Emne prefixet kun indeholder ASCII tegn,
-# ønsker du måske at vælge Aldrig for at undgå kodning. Dette kan gøre
-# emnet lidt mere læseligt for brugere med e-mailprogrammer der ikke kan
-# håndtere andre tegnsæt end ASCII.
-# 
-# Bemærk imidlertid, at hvis din mailliste modtager både kodede og
-# ukodede emnefelter , kan det være bedst at vælge Efter behov. Med
-# denne indstilling vil Mailman ikke kode ASCII prefixer hvis resten af
-# titelfeltet kun indeholder ASCII tegn, men vil kode prefixet hvis det
-# indeholder tegn som ikke er ASCII tegn. På denne måde undgås en
-# tvetydighed i standarderne, som forårsager at visse e-mailprogrammer
-# vil vise ekstra eller manglende mellemrum imellem emne prefixet og det
-# oprindelige emne.
-#
-# gyldige værdier:
-#    0 = "Aldrig"
-#    1 = "Altid"
-#    2 = "Efter behov"
+# If your mailing list's default language uses a non-ASCII character set
+# and the prefix contains non-ASCII characters, the prefix will always
+# be encoded according to the relevant standards.  However, if your
+# prefix contains only ASCII characters, you may want to set this option
+# to Never to disable prefix encoding.  This can make the subject
+# headers slightly more readable for users with mail readers that don't
+# properly handle non-ASCII encodings.
+# 
+# Note however, that if your mailing list receives both encoded and
+# unencoded subject headers, you might want to choose As needed.  Using
+# this setting, Mailman will not encode ASCII prefixes when the rest of
+# the header contains only ASCII characters, but if the original header
+# contains non-ASCII characters, it will encode the prefix.  This avoids
+# an ambiguity in the standards which could cause some mail readers to
+# display extra, or missing spaces between the prefix and the original
+# header.
+#
+# legal values are:
+#    0 = "Never"
+#    1 = "Always"
+#    2 = "As needed"
 encode_ascii_prefixes = 0
 
 ## Nondigest options
 #
-# Regler for levering i normal-modus.
+# Policies concerning immediately delivered list traffic.
 
-# Kan medlemmer vælge normal-modus?
+# Can subscribers choose to receive mail immediately, rather than in
+# batched digests?
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 nondigestable = 1
 
-# Tekst der tilføjes &oslash;verst i e-mail der sendes til listens
-# medlemmer. This text can include Python format strings which are
-# resolved against list attributes.  The list of substitutions allowed
-# are:
+# Text prepended to the top of every immediately-delivery message. This
+# text can include Python format strings which are resolved against list
+# attributes.  The list of substitutions allowed are:
 # 
 # 
 # real_name - The "pretty" name of the list; usually the list name with
@@ -403,10 +390,9 @@ nondigestable = 1
 # 
 msg_header = ''
 
-# Tekst som tilf&oslash;jes nederst i e-mail der sendes til listens
-# medlemmer. This text can include Python format strings which are
-# resolved against list attributes.  The list of substitutions allowed
-# are:
+# Text appended to the bottom of every immediately-delivery message.
+# This text can include Python format strings which are resolved against
+# list attributes.  The list of substitutions allowed are:
 # 
 # 
 # real_name - The "pretty" name of the list; usually the list name with
@@ -434,45 +420,54 @@ msg_footer = """_______________________________________________
 %(real_name)s@%(host_name)s
 %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s"""
 
+# When you scrub attachments, they are stored in archive area and links
+# are made in the message so that the member can access via web browser.
+# If you want the attachments totally disappear, you can use content
+# filter options.
+#
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
+scrub_nondigest = False
+
 ## Digest options
 #
-# Opsætning af sammendrag-modus.
+# Batched-delivery digest characteristics.
 
-# Kan medlemmer af listen vælge sammendrag-modus?
+# Can list members choose to receive list traffic bunched in digests?
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 digestable = 1
 
-# Hvilken modus er standard for nye brugere?
+# Which delivery mode is the default for new users?
 #
-# gyldige værdier:
-#    0 = "Normal"
-#    1 = "Sammendrag"
+# legal values are:
+#    0 = "Regular"
+#    1 = "Digest"
 digest_is_default = 0
 
-# Hvilket format skal benyttes som standard for samle-email?
+# When receiving digests, which format is default?
 #
-# gyldige værdier:
-#    0 = "Ren tekst"
+# legal values are:
+#    0 = "Plain"
 #    1 = "MIME"
 mime_is_default_digest = 0
 
-# Hvor stor (i KB) m&aring; en samle-email h&oslash;jst v&aelig;re
-# f&oslash;r den udsendes?
+# How big in Kb should a digest be before it gets sent out?
 digest_size_threshhold = 30
 
-# Skal der sendes en samle-email dagligt, selv om st&oslash;rrelsen ikke
-# er opn&aring;et?
+# Should a digest be dispatched daily when the size threshold isn't
+# reached?
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 digest_send_periodic = 1
 
-# Tekst som tilf&oslash;jes &oslash;verst i samle-emailen, f&oslash;r
-# indholdsfortegnelsen.This text can include Python format strings which
+# Text attached (as an initial message, before the table of contents) to
+# the top of digests. This text can include Python format strings which
 # are resolved against list attributes.  The list of substitutions
 # allowed are:
 # 
@@ -499,10 +494,9 @@ digest_send_periodic = 1
 # 
 digest_header = ''
 
-# Tekst der tilføjes nederst i hver samle-email, som sidste
-# information.This text can include Python format strings which are
-# resolved against list attributes.  The list of substitutions allowed
-# are:
+# Text attached (as a final message) to the bottom of digests. This text
+# can include Python format strings which are resolved against list
+# attributes.  The list of substitutions allowed are:
 # 
 # 
 # real_name - The "pretty" name of the list; usually the list name with
@@ -530,281 +524,283 @@ digest_footer = """_______________________________________________
 %(real_name)s@%(host_name)s
 %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s"""
 
-# N&aring;r et nyt volume startes, &oslash;ges volume nummeret, og
-# udgavenummeret s&aelig;ttes til 1.
+# When a new digest volume is started, the volume number is incremented
+# and the issue number is reset to 1.
 #
-# gyldige værdier:
-#    0 = "&Aring;rlig"
-#    1 = "M&aring;nedlig"
-#    2 = "Kvartalsvis"
-#    3 = "Ugentlig"
-#    4 = "Daglig"
+# legal values are:
+#    0 = "Yearly"
+#    1 = "Monthly"
+#    2 = "Quarterly"
+#    3 = "Weekly"
+#    4 = "Daily"
 digest_volume_frequency = 1
 
 ## Privacy options
 #
-# Her kan du bestemme hvad der kr&aelig;ves for at tilmelde sig til
-# maillisten, og bl.a. bestemme om maillisten skal v&aelig;re skjult
-# eller ikke. Se ogs&aring; <a
-# href="http://dgi-huset.dk/cgi-bin/mailman/admin/nyheder/archive">Indstillinger 
-# for arkivering</a> for egne indstillinger, n&aring;r det g&aelig;lder
-# arkivet og arkivering.
+# This section allows you to configure subscription and membership
+# exposure policy.  You can also control whether this list is public or
+# not.  See also the <a
+# href="http://dgi-huset.dk/cgi-bin/mailman/admin/nyheder/archive">Archival 
+# Options</a> section for separate archive-related privacy settings.
 
-# Vis denne mailliste n&aring;r nogen beder om at se en oversigt over
-# maillister p&aring; denne maskine?
+# Advertise this list when people ask what lists are on this machine?
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 advertised = 1
 
-# bekræftelse(*) - bekr&aelig;ftelse via e-mail er n&oslash;dvendig
-# godkendelse - anmodning om medlemskab skal godkendes af
-# listeadministrator (eller evt. listemoderator) bekr&aelig;ftelse +
-# godkendelse - b&aring;de bekr&aelig;ftelse via e-mail og godkendelse
-# fra listeadministrator (evt. listemoderator) er n&oslash;dvendig
-# 
-# (*) n&aring;r nogen vil tilmelde sig en liste, sender Mailman en
-# meddelelse med en unik identifikator som skal angives for at
-# bekr&aelig;fte tilmeldingen. P&aring; den m&aring;de vil det ikke
-# v&aelig;re muligt at tilmelde nogen imod deres vilje.
-#
-# gyldige værdier:
-#    1 = "Bekr&aelig;ftelse"
-#    2 = "Godkendelse"
-#    3 = "Bekr&aelig;ftelse og godkendelse"
+# Confirm (*) - email confirmation required Require approval - require
+# list administrator approval for subscriptions Confirm and approve -
+# both confirm and approve
+# 
+# (*) when someone requests a subscription, Mailman sends them a notice
+# with a unique subscription request number that they must reply to in
+# order to subscribe. This prevents mischievous (or malicious) people
+# from creating subscriptions for others without their consent.
+#
+# legal values are:
+#    1 = "Confirm"
+#    2 = "Require approval"
+#    3 = "Confirm and approve"
 subscribe_policy = 1
 
-# N&aring;r medlemmer &oslash;nsker at forlade en mailliste, sender de
-# en anmodning om framelding, enten via web, eller via e-mail. Normalt
-# er det bedst at disse anmodninger automatisk godkendes, s&aring;
-# medlemmer kan afmelde sig n&aring;r de &oslash;nsker det (mange
-# &oslash;nsker selv at kunne administrere en framelding). For nogle
-# f&aring; maillister kan det alligevel v&aelig;re aktuelt at have
-# kontrol over om medlemmer kan afmelde sig selv eller ej. En liste som
-# alle ansatte i et firma SKAL v&aelig;re medlem af, er et eksempel
-# p&aring; en s&aring;dan liste.
-#
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# When members want to leave a list, they will make an unsubscription
+# request, either via the web or via email. Normally it is best for you
+# to allow open unsubscriptions so that users can easily remove
+# themselves from mailing lists (they get really upset if they can't get
+# off lists!).
+# 
+# For some lists though, you may want to impose moderator approval
+# before an unsubscription request is processed.  Examples of such lists
+# include a corporate mailing list that all employees are required to be
+# members of.
+#
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 unsubscribe_policy = 0
 
-# Alle e-mailadresser som angives her vil blive udelukket fra listen, og
-# kan ikke tilmelde sig. Indtast e-mailadresser, en pr. linie, start
-# linien med tegnet ^ for at angive et regexp-udtryk der skal stemme
-# overens med afsenderadressen.
+# Addresses in this list are banned outright from subscribing to this
+# mailing list, with no further moderation required.  Add addresses one
+# per line; start the line with a ^ character to designate a regular
+# expression match.
 ban_list = []
 
-# Hvis denne indstilling ikke er sat til 'Alle', vil medlemslisten blive
-# beskyttet af medlemmernes eller administrators adgangskode.
+# When set, the list of subscribers is protected by member or admin
+# password authentication.
 #
-# gyldige værdier:
-#    0 = "Alle"
-#    1 = "Kun medlemmer af listen"
-#    2 = "Kun listeadministrator"
+# legal values are:
+#    0 = "Anyone"
+#    1 = "List members"
+#    2 = "List admin only"
 private_roster = 2
 
-# V&aelig;lger du 'Ja' her, vil medlemmers e-mailadresser blive
-# omskrevet n&aring;r de vises i en oversigt p&aring; websiderne
-# (b&aring;de som tekst og som links), s&aring; de ikke er nemme at
-# tolke som e-mailadresser. Formålet er at undg&aring; at medlemmernes
-# mailadresser bliver opsamlet af e-mailsniffere som skanner websider
-# for e-mailadresser (og derefter bruger dem til at udsende spam/junk
-# mail).
-#
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# Setting this option causes member email addresses to be transformed
+# when they are presented on list web pages (both in text and as links),
+# so they're not trivially recognizable as email addresses.  The
+# intention is to prevent the addresses from being snarfed up by
+# automated web scanners for use by spammers.
+#
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 obscure_addresses = 1
 
 ## Privacy options
 #
-# N&aring;r en meddelelse sendes til maillisten, g&aring;r den igennem
-# nogle trin for at afg&oslash;re om moderator skal godkende meddelelsen
-# eller ikke. Her finder du indstillinger til at kontrollere moderation
-# af e-mail fra b&aring;de medlemmer og ikke-medlemmer.
-# 
-# <p>E-mail fra medlemmer holdes tilbage for godkendelse hvis deres
-# <b>moderationsflag</b> er sat. Du kan bestemme om e-mail fra medlemmer
-# normalt skal vurderes eller ikke f&oslash;r den sendes til listen.
-# 
-# <p>E-mail som ikke er sendt af medlemmer af listen, kan automatisk
-# blive <a
-# href="?VARHELP=privacy/sender/accept_these_nonmembers">godkendt</a>,
-# <a href="?VARHELP=privacy/sender/hold_these_nonmembers">holdt tilbage
-# for godkendelse</a>, <a
-# href="?VARHELP=privacy/sender/reject_these_nonmembers">afvist (sendt
-# retur)</a>, eller <a
-# href="?VARHELP=privacy/sender/discard_these_nonmembers">slettet</a>,
-# enten enkeltvis eller som en gruppe. Al e-mail fra ikke-medlemmer, som
-# ikke specifikt bliver godkendt, sendt retur eller slettet, vil blive
-# behandlet alt efter hvad <a
-# href="?VARHELP=privacy/sender/generic_nonmember_action">generelle
-# regler for ikke-medlemmer</a> viser.
-# 
-# <p>I tekstboksene nedenfor kan du tilf&oslash;je en e-mailadresse pr.
-# linie. Du kan ogs&aring; tilf&oslash;je  <a
-# href="http://www.python.org/doc/current/lib/module-re.html">Python
-# regexp-udtryk</a>. Begynd i s&aring; fald linien med tegnet ^ for at
-# markere at det er et s&aring;dant udtryk. N&aring;r du benytter
-# backslash, skriv da lige som i rene strings (Python raw strings)
-# (normalt kun &eacute;n backslash ad gangen).
-# 
-# <p>Bem&aelig;rk: sammenligning med normale e-mailadresser
-# udf&oslash;res f&oslash;rst, regexp-udtryk vil derfor blive behandlet
-# sidst.
-
-# Hvert medlem af listen har et moderationsflag som fort&aelig;ller om
-# e-mails fra medlemmet kan sendes direkte til e-maillisten, eller om de
-# f&oslash;rst skal godkendes af listemoderator. N&aring;r
-# moderationsflaget er sat til, skal e-mails fra medlemmet godkendes af
-# listemoderator f&oslash;r de udsendes til alle p&aring; listen. Som
-# listeadministrator kan du for hvert enkelt medlem bestemme om
-# medlemmets e-mail skal modereres eller ikke. N&aring;r et nyt medlem
-# tilmeldes listen, s&aelig;ttes moderationsflaget til den indstilling
-# du v&aelig;lger her. S&aelig;t den til 'Nej' hvis du &oslash;nsker at
-# e-mail fra medlemmer normalt skal g&aring; lige til listen. S&aelig;t
-# den til 'Ja' hvis du &oslash;nsker at e-mail fra nye medlemmer skal
-# godkendes f&oslash;r de udsendes til hele listen. Du kan altid
-# s&aelig;tte moderationsflaget for hvert enkelt medlem fra
-# Administration af medlemmer siden.
-#
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# When a message is posted to the list, a series of moderation steps are
+# take to decide whether the a moderator must first approve the message
+# or not.  This section contains the controls for moderation of both
+# member and non-member postings.
+# 
+# <p>Member postings are held for moderation if their <b>moderation
+# flag</b> is turned on.  You can control whether member postings are
+# moderated by default or not.
+# 
+# <p>Non-member postings can be automatically <a
+# href="?VARHELP=privacy/sender/accept_these_nonmembers" >accepted</a>,
+# <a href="?VARHELP=privacy/sender/hold_these_nonmembers">held for
+# moderation</a>, <a
+# href="?VARHELP=privacy/sender/reject_these_nonmembers" >rejected</a>
+# (bounced), or <a
+# href="?VARHELP=privacy/sender/discard_these_nonmembers"
+# >discarded</a>, either individually or as a group.  Any posting from a
+# non-member who is not explicitly accepted, rejected, or discarded,
+# will have their posting filtered by the <a
+# href="?VARHELP=privacy/sender/generic_nonmember_action">general
+# non-member rules</a>.
+# 
+# <p>In the text boxes below, add one address per line; start the line
+# with a ^ character to designate a <a href=
+# "http://www.python.org/doc/current/lib/module-re.html" >Python regular
+# expression</a>.  When entering backslashes, do so as if you were using
+# Python raw strings (i.e. you generally just use a single backslash).
+# 
+# <p>Note that non-regexp matches are always done first.
+
+# Each list member has a moderation flag which says whether messages
+# from the list member can be posted directly to the list, or must first
+# be approved by the list moderator.  When the moderation flag is turned
+# on, list member postings must be approved first.  You, the list
+# administrator can decide whether a specific individual's postings will
+# be moderated or not.
+# 
+# When a new member is subscribed, their initial moderation flag takes
+# its value from this option.  Turn this option off to accept member
+# postings by default.  Turn this option on to, by default, moderate
+# member postings first.  You can always manually set an individual
+# member's moderation bit by using the membership management screens.
+#
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 default_member_moderation = 1
 
+# Hold -- this holds the message for approval by the list moderators.
 # 
-# Hold tilbage -- meddelelsen holdes tilbage for godkendelse af
-# listemoderator(er). Afvis -- meddelelsen sendes automatisk retur til
-# afsender. Begrundelsen der sendes kan du skrive selv Slet --
-# meddelelsen bliver fjernet uden at give besked om dette til afsender.
+# Reject -- this automatically rejects the message by sending a bounce
+# notice to the post's author.  The text of the bounce notice can be <a
+# href="?VARHELP=privacy/sender/member_moderation_notice" >configured by
+# you.
+# 
+# Discard -- this simply discards the message, with no notice sent to
+# the post's author.
 # 
 #
-# gyldige værdier:
-#    0 = "Hold&nbsp;tilbage"
-#    1 = "Afvis"
-#    2 = "Slet"
+# legal values are:
+#    0 = "Hold"
+#    1 = "Reject"
+#    2 = "Discard"
 member_moderation_action = 0
 
-# Tekst som skal sendes med meddelelsen om afvisning som sendes til
-# modererede medlemmer af listen.
+# Text to include in any <a
+# href="?VARHELP/privacy/sender/member_moderation_action" >rejection
+# notice to be sent to moderated members who post to this list.
 member_moderation_notice = """Email-adressen nyheder@dgi-huset ender blindt.
 
 Brug istedet web-adressen http://www.dgi-huset.dk/ eller email-adressen info@dgi-huset.dk .
 
 Velig hilsen DGI-huset."""
 
-# E-mail fra disse ikke-medlemmer vil automatisk blive godkendt.
-# Tilf&oslash;j e-mailadresser, en pr. linie. Start linien med tegnet ^
-# for at angive et regexp-udtryk som skal stemme overens med
-# afsenderadressen.
+# Postings from any of these non-members will be automatically accepted
+# with no further moderation applied.  Add member addresses one per
+# line; start the line with a ^ character to designate a regular
+# expression match.
 accept_these_nonmembers = []
 
-# e-mail fra disse ikke-medlemmer vil automatisk blive holdt tilbage for
-# vurdering af listemoderator. Afsenderen vil modtage en meddelelse om
-# dette, med bl.a. instruktioner om hvordan han/hun kan
-# tilbagetr&aelig;kke sin e-mail. Indtast e-mailadresser, en pr. linie.
-# Start linien med tegnet ^ for at angive et regexp-udtryk som skal
-# stemme overens med afsenderadressen.
+# Postings from any of these non-members will be immediately and
+# automatically held for moderation by the list moderators. The sender
+# will receive a notification message which will allow them to cancel
+# their held message.  Add member addresses one per line; start the line
+# with a ^ character to designate a regular expression match.
 hold_these_nonmembers = ['^.*@dgi-huset.dk']
 
-# E-mail fra disse ikke-medlemmer vil automatisk blive afvist. De vil
-# f&aring; mailen retur, med en meddelelse om at den blev automatisk
-# afvist. Dette valg b&oslash;r ikke benyttes for kendte spammere, de
-# b&oslash;r automatisk slettes. Indtast e-mailadresser, en pr. linie.
-# Start linien med tegnet ^ for at angive et regexp-udtryk som skal
-# stemme overens med afsenderadressen.
+# Postings from any of these non-members will be automatically rejected.
+# In other words, their messages will be bounced back to the sender with
+# a notification of automatic rejection.  This option is not appropriate
+# for known spam senders; their messages should be <a
+# href="?VARHELP=privacy/sender/discard_these_nonmembers" >automatically
+# discarded.
+# 
+# Add member addresses one per line; start the line with a ^ character
+# to designate a regular expression match.
 reject_these_nonmembers = []
 
-# E-mail fra disse ikke-medlemmer vil automatisk blive slettet. Det vil
-# sige at meddelelsen afvises uden nogen form for tilbagemelding, men
-# listemoderator kan (om &oslash;nsket) modtage en kopi af den afviste
-# e-mail. Tilf&oslash;j e-mailadresser, en pr. linie, start linien med
-# tegnet ^ for at angive et regexp-udtryk der skal stemme overens med
-# afsenderadressen.
+# Postings from any of these non-members will be automatically
+# discarded.  That is, the message will be thrown away with no further
+# processing or notification.  The sender will not receive a
+# notification or a bounce, however the list moderators can optionally
+# <a href="?VARHELP=privacy/sender/forward_auto_discards" >receive
+# copies of auto-discarded messages..
+# 
+# Add member addresses one per line; start the line with a ^ character
+# to designate a regular expression match.
 discard_these_nonmembers = []
 
-# N&aring;r en e-mail fra et ikke-medlem bliver modtaget, sammenlignes
-# e-mailens afsender med listen over e-mailadresser der skal godkendes,
-# holdes tilbage, <a
-# href="?VARHELP=privacy/sender/reject_these_nonmembers" >afvises
-# (sendes retur), eller slettes. Hvis afsenderadressen ikke stemmer
-# overens med en adresse der findes i listerne, bliver f&oslash;lgende
-# afg&oslash;relse truffet.
-#
-# gyldige værdier:
-#    0 = "Godkend"
-#    1 = "Hold&nbsp;tilbage"
-#    2 = "Afvis"
-#    3 = "Slet"
+# When a post from a non-member is received, the message's sender is
+# matched against the list of explicitly <a
+# href="?VARHELP=privacy/sender/accept_these_nonmembers" >accepted,
+# held, <a href="?VARHELP=privacy/sender/reject_these_nonmembers"
+# >rejected (bounced), and <a
+# href="?VARHELP=privacy/sender/discard_these_nonmembers" >discarded
+# addresses.  If no match is found, then this action is taken.
+#
+# legal values are:
+#    0 = "Accept"
+#    1 = "Hold"
+#    2 = "Reject"
+#    3 = "Discard"
 generic_nonmember_action = 1
 
-# Skal meddelelser fra ikke-medlemmer, hvis mail automatisk slettes,
-# videresendes til listemoderator?
+# Should messages from non-members, which are automatically discarded,
+# be forwarded to the list moderator?
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 forward_auto_discards = 1
 
+# Text to include in any rejection notice to be sent to non-members who
+# post to this list. This notice can include the list's owner address by
+# %(listowner)s and replaces the internally crafted default message.
+nonmember_rejection_notice = ''
+
 ## Privacy options
 #
-# Her kan du ops&aelig;tte filtrering baseret på modtageren af
-# meddelelsen.
+# This section allows you to configure various filters based on the
+# recipient of the message.
 
-# Meget (faktisk det meste) spam/junk mail har ikke de endelige
-# modtagere i modtagerfelterne. Faktisk indeholder felterne To: og/eller
-# Cc: oftest en helt ugyldig adresse. Begr&aelig;nsningen du
-# s&aelig;tter her har kun indvirkning p&aring; det som st&aring;r
-# f&oslash;r '@' tegnet i adressen, men filtret vil alligevel opfange og
-# blokere det meste spam/junk mail.
+# Many (in fact, most) spams do not explicitly name their myriad
+# destinations in the explicit destination addresses - in fact often the
+# To: field has a totally bogus address for obfuscation.  The constraint
+# applies only to the stuff in the address before the '@' sign, but
+# still catches all such spams.
+# 
+# The cost is that the list will not accept unhindered any postings
+# relayed from other addresses, unless
+# 
 # 
-# Prisen for dette er, at listen ikke uhindret vil kunne modtage e-mail
-# videresendt via andre e-mailadresser, med mindre
+# The relaying address has the same name, or
 # 
+# The relaying address name is included on the options that specifies
+# acceptable aliases for the list.
 # 
-# Adressen der videresendes fra hedder det samme, eller Adressen der
-# videresendes fra inkluderes i indstillingen som bestemmer gyldige
-# aliaser for listen.
 # 
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 require_explicit_destination = 1
 
-# Alternative e-mailadresser som godtages n&aring;r
-# 'require_explicit_destination' er sat til. Som v&aelig;rdi for denne
-# indstilling skal du angive regexp-udtryk ("regular expressions"), et
-# udtryk pr. linie, der sammenlignes med hver modtageradresse i
-# meddelelsen. Sammenligningen udf&oslash;res med Pythons re.match()
-# funktion, som betyder at de kun g&aelig;lder for begyndelsen af
-# strengen.
-# 
-# For bagudkompatibilitet med Mailman 1.1, hvis regexp-udtryk ikke
-# indeholder en '@', sammenlignes udtrykket kun med den f&oslash;rste
-# del (det som st&aring;r f&oslash;r '@') i modtageradressen. Hvis
-# sammenligningen ikke lykkes, eller hvis udtrykket ikke indholder en
-# '@', sammenlignes udtrykket med hele modtageradressen.
-# 
-# Sammenligning med kun den f&oslash;rste del af en modtageradresse
-# underst&oslash;ttes ikke l&aelig;ngere. I fremtidige versioner af
-# Mailman vil kun sammenligning med hele modtageradresser blive
-# underst&oslash;ttet.
+# Alternate addresses that are acceptable when
+# `require_explicit_destination' is enabled.  This option takes a list
+# of regular expressions, one per line, which is matched against every
+# recipient address in the message.  The matching is performed with
+# Python's re.match() function, meaning they are anchored to the start
+# of the string.
+# 
+# For backwards compatibility with Mailman 1.1, if the regexp does not
+# contain an `@', then the pattern is matched against just the local
+# part of the recipient address.  If that match fails, or if the pattern
+# does contain an `@', then the pattern is matched against the entire
+# recipient address.
+# 
+# Matching against the local part is deprecated; in a future release,
+# the pattern will always be matched against the entire recipient
+# address.
 acceptable_aliases = ''
 
-# Hvis en mail der er sendt til listen indeholder s&aring; mange som
-# eller flere modtagere end denne v&aelig;rdi, holdes mailen tilbage,
-# s&aring; listeadministrator eventuelt kan godkende den. Brug
-# v&aelig;rdien 0 for ingen begr&aelig;nsning.
+# If a posting has this number, or more, of recipients, it is held for
+# admin approval.  Use 0 for no ceiling.
 max_num_recipients = 10
 
 ## Privacy options
 #
-# Her kan du opsætte forskellige anti-spam filtre, som kan bidrage til
-# at reducere mængden af spam der distribueres via e-maillisten.
+# This section allows you to configure various anti-spam filters posting
+# filters, which can help reduce the amount of spam your list members
+# end up receiving.
+# 
 
 # Each header filter rule has two parts, a list of regular expressions,
 # one per line, and an action to take.  Mailman matches the message's
@@ -815,22 +811,23 @@ max_num_recipients = 10
 # You can have more than one filter rule for your list.  In that case,
 # each rule is matched in turn, with processing stopped after the first
 # match.
+# 
+# Note that headers are collected from all the attachments (except for
+# the mailman administrivia message) and matched against the regular
+# expressions. With this feature, you can effectively sort out messages
+# with dangerous file types or file name extensions.
 header_filter_rules = []
 
-# Brug denne indstilling til at bortfiltrere mail til listen, baseret
-# p&aring; indholdet af et eller flere felter i brevhovedet. Her skal du
-# skrive regexp-udtryk (regular expressions), et pr. linie, som
-# sammenlignes med det aktuelle felt. Sammenligningen skelner ikke
-# imellem store og sm&aring; bogstaver. Linier der begynder med '#'
-# sammenlignes ikke.
+# Use this option to prohibit posts according to specific header values.
+# The target value is a regular-expression for matching against the
+# specified header.  The match is done disregarding letter case.  Lines
+# beginning with '#' are ignored as comments.
 # 
-# For eksempel: udtrykket to: .*@public.com fort&aelig;ller at al mail
-# som indeholder '@public.com' i To: feltet, skal holdes tilbage for
-# godkendelse.
+# For example:to: .*@public.com  says to hold all postings with a To:
+# mail header containing '@public.com' anywhere among the addresses.
 # 
-# Bem&aelig;rk: tomme tegn i starten af regexp-udtrykket fjernes. Dette
-# kan omg&aring;s p&aring; flere m&aring;der, f.eks. ved at bruge
-# escape-tegn eller parenteser.
+# Note that leading whitespace is trimmed from the regexp.  This can be
+# circumvented in a number of ways, e.g. by escaping or bracketing it.
 bounce_matching_headers = """
 # Lines that *start* with a '#' are comments.
 to: friend@public.com
@@ -840,415 +837,439 @@ from: .*@uplinkpro.com"""
 
 ## Bounce options
 #
-# Disse regler bestemmer hvordan automatisk behandling af returmails
-# skal foreg&aring;. Her er en oversigt over hvordan det virker.
-# 
-# <p>N&aring;r Mailman modtager en returmail, bliver to ting
-# fors&oslash;gt tolket. Den ene er e-mailadressen for medlemmet som
-# egentlig skulle modtage e-mailen, og den anden er &aring;rsagen til
-# problemet. &Aring;rsagen tolkes til at v&aelig;re <em>alvorlig</em>
-# eller <em>harml&oslash;s</em> alt efter om &aring;rsagen er af kritisk
-# eller af mindre alvorlig art. Hvis der er tvivl, tolkes &aring;rsagen
-# som alvorlig.
-# 
-# <p>Hvis ingen e-mailadresse kan hentes ud af meddelelsen, bliver den
-# normalt afvist. Ellers vil medlemmet som har e-mailadressen f&aring;
-# tildelt et <em>returtal</em>, og hver gang der kommer en
-# returmeddelelse vil tallet &oslash;ges. Alvorlige &aring;rsager
-# f&oslash;rer til at tallet &oslash;ges med 1, harml&oslash;se
-# &aring;rsager f&oslash;rer til at det &oslash;ges med 0.5. Dette sker
-# kun &eacute;n gang pr. dag, s&aring; selv om der kommer 10 alvorlige
-# returmails fra et medlem p&aring; &eacute;n dag, vil tallet kun
-# &oslash;ges med 1.
-# 
-# <p>N&aring;r returtallet for et medlem n&aring;r en vis <a
-# href="?VARHELP=bounce/bounce_score_threshold">gr&aelig;nse</a>,
-# stoppes levering til medlemmet. Dermed vil medlemmet ikke modtage
-# e-mail fra listen f&oslash;r levering s&aelig;ttes til igen. Medlemmet
-# vil med j&aelig;vne mellemrum modtage meddelelse om at dette er sket,
-# og hvad han/hun skal g&oslash;re for at f&aring; e-mail fra listen
-# igen.
-# 
-# <p>Du kan bestemme <a
-# href="?VARHELP=bounce/bounce_you_are_disabled_warnings">hvor mange
-# advarsler</a> medlemmet skal have og <a
-# href="?VARHELP=bounce/bounce_you_are_disabled_warnings_interval">hvor
-# ofte</a> han/hun skal modtage s&aring;danne advarsler.
-# 
-# <p>Der er en vigtig indstilling mere: efter en vis tid -- hvor ingen
-# returmeddelelser dukker op -- regnes returinformation for at
-# v&aelig;re <a
-# href="?VARHELP=bounce/bounce_info_stale_after">for&aelig;ldet</a> og
-# stoppes. Ved at justere denne v&aelig;rdi, og s&aelig;tte en
-# gr&aelig;nse for returantallet, kan du bestemme hvor lang tid der skal
-# g&aring; f&oslash;r levering til et medlem stoppes. Begge disse
-# v&aelig;rdier b&oslash;r tilpasses efter hvor ofte og hvor meget
-# e-mail der sendes til din liste.
-
-# Ved at sætte denne værdi til Nej, slår du al automatisk tolkning af
-# returmeddelelser for denne liste fra. Bemærk at hvis meddelelser
-# afvises vil listeadministratoren ikke blive forstyrret med dem.
-#
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# These policies control the automatic bounce processing system in
+# Mailman.  Here's an overview of how it works.
+# 
+# <p>When a bounce is received, Mailman tries to extract two pieces of
+# information from the message: the address of the member the message
+# was intended for, and the severity of the problem causing the bounce.
+# The severity can be either <em>hard</em> or <em>soft</em> meaning
+# either a fatal error occurred, or a transient error occurred.  When in
+# doubt, a hard severity is used.
+# 
+# <p>If no member address can be extracted from the bounce, then the
+# bounce is usually discarded.  Otherwise, each member is assigned a
+# <em>bounce score</em> and every time we encounter a bounce from this
+# member we increment the score.  Hard bounces increment by 1 while soft
+# bounces increment by 0.5.  We only increment the bounce score once per
+# day, so even if we receive ten hard bounces from a member per day,
+# their score will increase by only 1 for that day.
+# 
+# <p>When a member's bounce score is greater than the <a
+# href="?VARHELP=bounce/bounce_score_threshold">bounce score
+# threshold</a>, the subscription is disabled.  Once disabled, the
+# member will not receive any postings from the list until their
+# membership is explicitly re-enabled (either by the list administrator
+# or the user).  However, they will receive occasional reminders that
+# their membership has been disabled, and these reminders will include
+# information about how to re-enable their membership.
+# 
+# <p>You can control both the <a
+# href="?VARHELP=bounce/bounce_you_are_disabled_warnings">number of
+# reminders</a> the member will receive and the <a
+# href="?VARHELP=bounce/bounce_you_are_disabled_warnings_interval"
+# >frequency</a> with which these reminders are sent.
+# 
+# <p>There is one other important configuration variable; after a
+# certain period of time -- during which no bounces from the member are
+# received -- the bounce information is <a
+# href="?VARHELP=bounce/bounce_info_stale_after">considered stale</a>
+# and discarded.  Thus by adjusting this value, and the score threshold,
+# you can control how quickly bouncing members are disabled.  You should
+# tune both of these to the frequency and traffic volume of your list.
+
+# By setting this value to No, you disable all automatic bounce
+# processing for this list, however bounce messages will still be
+# discarded so that the list administrator isn't inundated with them.
+#
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 bounce_processing = 1
 
-# Hvert medlem tildeles et returtal, og hver gang der kommer en
-# returmeddelelse vil dette tal &oslash;ges.  Alvorlige (&aring;rsager
-# f&oslash;rer til at det &oslash;ges med 1, mens harml&oslash;se
-# &aring;rsager f&oslash;rer til at det &oslash;ges med 0.5. Dette sker
-# kun &eacute;n gang pr. dag, s&aring; selv om der kommer 10 alvorlige
-# returmails fra et medlem p&aring; &eacute;n dag, vil tallet kun
-# &oslash;ges med 1.
-# 
-# Her s&aelig;ttes den &oslash;vre gr&aelig;nse for medlemmets returtal
-# Overskrides denne gr&aelig;nse stoppes levering automatisk, men
-# medlemmet bliver ikke fjernet fra listen.
+# Each subscriber is assigned a bounce score, as a floating point
+# number.  Whenever Mailman receives a bounce from a list member, that
+# member's score is incremented.  Hard bounces (fatal errors) increase
+# the score by 1, while soft bounces (temporary errors) increase the
+# score by 0.5.  Only one bounce per day counts against a member's
+# score, so even if 10 bounces are received for a member on the same
+# day, their score will increase by just 1.
+# 
+# This variable describes the upper limit for a member's bounce score,
+# above which they are automatically disabled, but not removed from the
+# mailing list.
 bounce_score_threshold = 5.0
 
-# Antal dage f&oslash;r returinformation stoppes hvis der ikke dukker
-# flere returmails op. Dette tal skal v&aelig;re et heltal.
+# The number of days after which a member's bounce information is
+# discarded, if no new bounces have been received in the interim.  This
+# value must be an integer.
 bounce_info_stale_after = 7
 
-# Hvor mange Levering til dig er stoppet advarsler der skal sendes til
-# et medlem f&oslash;r medlemmet frameldes listen. S&aelig;t denne værdi
-# til 0 for at fjerne et medlem fra listen straks, hvis der kommer
-# returmails fra medlemmets e-mailadresse. Dette tal skal være et
-# heltal.
+# How many Your Membership Is Disabled warnings a disabled member should
+# get before their address is removed from the mailing list.  Set to 0
+# to immediately remove an address from the list once their bounce score
+# exceeds the threshold.  This value must be an integer.
 bounce_you_are_disabled_warnings = 3
 
-# Antal dage imellem hver gang en Levering til dig er stoppet advarsel
-# skal sendes ud. Dette tal skal være et heltal.
+# The number of days between sending the Your Membership Is Disabled
+# warnings.  This value must be an integer.
 bounce_you_are_disabled_warnings_interval = 7
 
-# Mailmans automatiske returmailh&aring;ndtering er meget robust, men
-# det er alligevel umuligt at genkende alle typer returmails der kommer.
-# Du b&oslash;r v&aelig;lge Ja her, af to grunde: 1) Hvis det virkelig
-# er en permanent returmail fra et medlem af listen, b&oslash;r du
-# antagelig manuelt afmelde medlemmet fra listen, og 2) du vil
-# m&aring;ske sende en meddelelse til udviklerne af Mailman s&aring;dan
-# at returmails automatisk genkendes af Mailman i senere versioner. Hvis
-# du ikke vil g&oslash;re nogen af delene, s&aelig;ttes denne
-# indstilling til Nej. S&aring; vil alle returmails afvises automatisk
-# uden videre behandling. Bem&aelig;rk: Denne indstilling vil ogs&aring;
-# indvirke p&aring; al e-mail der sendes til listens -admin adresse. Den
-# adresse er for&aelig;ldet og udg&aring;et, men måske vil nogen
-# alligevel fortsat sende e-mail til den. Hvis nogen g&oslash;r det, og
-# du har sat denne indstilling til Nej, vil disse mails ogs&aring; blive
-# afvist. M&aring;ske vil du ogs&aring; ops&aelig;tte et automatisk svar
-# p&aring; e-mail sendt til -owner og -admin adresserne.
-#
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# While Mailman's bounce detector is fairly robust, it's impossible to
+# detect every bounce format in the world.  You should keep this
+# variable set to Yes for two reasons: 1) If this really is a permanent
+# bounce from one of your members, you should probably manually remove
+# them from your list, and 2) you might want to send the message on to
+# the Mailman developers so that this new format can be added to its
+# known set.
+# 
+# If you really can't be bothered, then set this variable to No and all
+# non-detected bounces will be discarded without further processing.
+# 
+# Note: This setting will also affect all messages sent to your list's
+# -admin address.  This address is deprecated and should never be used,
+# but some people may still send mail to this address.  If this happens,
+# and this variable is set to No those messages too will get discarded.
+# You may want to set up an autoresponse message for email to the -owner
+# and -admin address.
+#
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 bounce_unrecognized_goes_to_list_owner = 1
 
-# Ved at sætte denne til Nej, fravælges beskeden der normalt sendes til
-# ejer(e) af listen, når levering af e-mail til et medlem stoppes på
-# grund af for mange returmails. Der vil til gengæld altid blive forsøgt
-# afsendt en e-mail med besked til medlemmet.
+# By setting this value to No, you turn off notification messages that
+# are normally sent to the list owners when a member's delivery is
+# disabled due to excessive bounces. An attempt to notify the member
+# will always be made.
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 bounce_notify_owner_on_disable = 1
 
-# Ved at sætte denne til Nej, fravælges beskeden der normalt sendes til
-# ejer(e) af listen, når et medlem frameldes listen på grund af for
-# mange returmails. Der vil til gengæld altid blive forsøgt afsendt en
-# e-mail med besked til medlemmet.
+# By setting this value to No, you turn off notification messages that
+# are normally sent to the list owners when a member is unsubscribed due
+# to excessive bounces.  An attempt to notify the member will always be
+# made.
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 bounce_notify_owner_on_removal = 1
 
 ## Archive options
 #
-# Regler for arkivering
+# List traffic archival policies.
 
-# Arkiver e-mail i et arkiv?
+# Archive messages?
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 archive = 1
 
-# Skal arkivet v&aelig;re offentligt eller privat?
+# Is archive file source for public or private archival?
 #
-# gyldige værdier:
-#    0 = "Offentligt"
-#    1 = "Privat"
+# legal values are:
+#    0 = "public"
+#    1 = "private"
 archive_private = 0
 
-# Hvor ofte skal arkivet deles op?
+# How often should a new archive volume be started?
 #
-# gyldige værdier:
-#    0 = "&Aring;rlig"
-#    1 = "M&aring;nedlig"
-#    2 = "Kvartalsvis"
-#    3 = "Ugentlig"
-#    4 = "Daglig"
+# legal values are:
+#    0 = "Yearly"
+#    1 = "Monthly"
+#    2 = "Quarterly"
+#    3 = "Weekly"
+#    4 = "Daily"
 archive_volume_frequency = 1
 
 ## Gateway options
 #
-# E-mail-Til-Nyhedsgruppe og Nyhedsgruppe-Til-E-mail tjeneste.
+# Mail-to-News and News-to-Mail gateway services.
 
-# Nyhedsgruppe-tjeneste er ikke en del af Mailman. Du skal have adgang
-# til en eksisterende NNTP tjeneste, og maskinen som denne mailliste
-# k&oslash;rer p&aring; skal have adgang til at hente og afsende
-# meddelelser til NNTP tjenesten.
+# This value may be either the name of your news server, or optionally
+# of the format name:port, where port is a port number.
+# 
+# The news server is not part of Mailman proper.  You have to already
+# have access to an NNTP server, and that NNTP server must recognize the
+# machine this mailing list runs on as a machine capable of reading and
+# posting news.
 nntp_host = ''
 
-# Navn p&aring; nyhedsgruppe der skal sendes til og/eller fra.
+# The name of the Usenet group to gateway to and/or from.
 linked_newsgroup = ''
 
-# Skal nye meddelelser til denne liste sendes til nyhedsgruppen?
+# Should new posts to the mailing list be sent to the newsgroup?
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 gateway_to_news = 0
 
-# Skal nye meddelelser til nyhedsgruppen sendes til denne mailliste?
+# Should new posts to the newsgroup be sent to the mailing list?
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 gateway_to_mail = 0
 
-# Denne indstilling fort&aelig;ller Mailman hvilken slags
-# moderationsregler nyhedsgruppen har og hvordan de koordineres med
-# maillistens moderationsregler. Dette g&aelig;lder kun nyhedgrupper du
-# overfører meddelelser til, s&aring; hvis du kun overf&oslash;rer fra
-# en nyhedsgruppe, eller nyhedsgruppen du overf&oslash;rer til ikke er
-# modereret, s&aelig;ttes indstillingen til Ingen.
-# 
-# Hvis nyhedsgruppen er modereret, kan du s&aelig;tte maillisten til at
-# v&aelig;re moderationsadressen for nyhedsgruppen. Ved at vælge
-# Modereret, vil en ekstra meddelelse holdes tilbage i
-# godkendelsesprocessen. Al mail sendt til maillisten skal godkendes
-# f&oslash;r den sendes til nyhedsgruppen, eller til medlemmerne af
-# listen.
-# 
-# Vær opm&aelig;rksom p&aring; at hvis brevhovedet i mailen har et
-# Approved: felt med listens administrative adgangskode, vil denne regel
-# ikke blive benyttet. På den m&aring;de kan priviligerede afsendere
-# sende mail direkte til listen og nyhedsgruppen.
-# 
-# Hvis nyhedsgruppen er modereret, men du alligevel vil have en
-# &aring;ben liste, b&oslash;r du vælge Åben liste, modereret
-# nyhedsgruppe. S&aring; vil de s&aelig;dvanlige mekanismer for
-# moderation blive benyttet i Mailman, men alle meddelelser der sendes
-# til Usenet vil f&aring; et Approved felt i brevhovedet.
-#
-# gyldige værdier:
-#    0 = "Ingen"
-#    1 = "Åben liste, modereret nyhedsgruppe"
-#    2 = "Modereret"
+# This setting determines the moderation policy of the newsgroup and its
+# interaction with the moderation policy of the mailing list.  This only
+# applies to the newsgroup that you are gatewaying to, so if you are
+# only gatewaying from Usenet, or the newsgroup you are gatewaying to is
+# not moderated, set this option to None.
+# 
+# If the newsgroup is moderated, you can set this mailing list up to be
+# the moderation address for the newsgroup.  By selecting Moderated, an
+# additional posting hold will be placed in the approval process.  All
+# messages posted to the mailing list will have to be approved before
+# being sent on to the newsgroup, or to the mailing list membership.
+# 
+# Note that if the message has an Approved header with the list's
+# administrative password in it, this hold test will be bypassed,
+# allowing privileged posters to send messages directly to the list and
+# the newsgroup.
+# 
+# Finally, if the newsgroup is moderated, but you want to have an open
+# posting policy anyway, you should select Open list, moderated group.
+# The effect of this is to use the normal Mailman moderation facilities,
+# but to add an Approved header to all messages that are gatewayed to
+# Usenet.
+#
+# legal values are:
+#    0 = "None"
+#    1 = "Open list, moderated group"
+#    2 = "Moderated"
 news_moderation = 0
 
-# Mailman tilføjer normalt en tekst du selv kan tilrette (emne prefix)
-# foran emnefeltet i mail som sendes til listen, og normalt sker dette
-# også for mail som sendes videre til Usenet. Du kan sætte denne
-# indstilling til Nej hvis du ikke ønsker emne prefix tilføjet til mail
-# som sendes til Usenet. Sættes emne prefix for listen til off, vil
-# videresendte meddelelser heller ikke få prefix tilføjet.
+# Mailman prefixes Subject: headers with text you can customize and
+# normally, this prefix shows up in messages gatewayed to Usenet.  You
+# can set this option to No to disable the prefix on gated messages.  Of
+# course, if you turn off normal Subject: prefixes, they won't be
+# prefixed for gated messages either.
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 news_prefix_subject_too = 1
 
 ## Autoreply options
 #
-# Indstillinger for automatiske svar.<p>
+# Auto-responder characteristics.<p>
 # 
-# I tekstboksene nedenfor kan du bruge følgende variabler: (skriv:
-# %(&lt;variabelnavn&gt;)s ) for at indsætte ønsket information: <p><ul>
-# <li><b>listname</b> - <em>navnet p&aring; listen</em>
-# <li><b>listurl</b> - <em>URL til listens webside</em>
-# <li><b>requestemail</b> - <em>listens -request e-mailadresse</em>
-# <li><b>owneremail</b> - <em>listens -owner e-mailadresse</em> </ul>
+# In the text fields below, string interpolation is performed with the
+# following key/value substitutions: <p><ul> <li><b>listname</b> -
+# <em>gets the name of the mailing list</em> <li><b>listurl</b> -
+# <em>gets the list's listinfo URL</em> <li><b>requestemail</b> -
+# <em>gets the list's -request address</em> <li><b>owneremail</b> -
+# <em>gets the list's -owner address</em> </ul>
 # 
-# <p>Du kan enten skrive teksten direkte i tekstboksene, eller du kan
-# angive navnet p&aring; en fil som indeholder teksten. Denne fil vil
-# s&aring; blive indl&aelig;st i tekstboksen, fra dit lokale filsystem.
+# <p>For each text field, you can either enter the text directly into
+# the text box, or you can specify a file on your local system to upload
+# as the text.
 
-# Skal Mailman sende et automatisk svar til dem der sender e-mail til
-# listen?
+# Should Mailman send an auto-response to mailing list posters?
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 autorespond_postings = 0
 
-# Automatisk svar der skal sendes.
+# Auto-response text to send to mailing list posters.
 autoresponse_postings_text = ''
 
-# Skal Mailman sende et automatisk svar p&aring; e-mail der sendes til
-# -owner adressen?
+# Should Mailman send an auto-response to emails sent to the -owner
+# address?
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 autorespond_admin = 0
 
-# Automatisk svar p&aring; e-mail til -owner adressen.
+# Auto-response text to send to -owner emails.
 autoresponse_admin_text = ''
 
-# Skal Mailman sende et automatisk svar p&aring; e-mail der sendes til
-# -request adressen? Hvis du v&aelig;lger ja, kan du ogs&aring;
-# v&aelig;lge om e-mailen der blev sendt til -request adressen skal
-# medtages i det automatiske svar.
+# Should Mailman send an auto-response to emails sent to the -request
+# address?  If you choose yes, decide whether you want Mailman to
+# discard the original email, or forward it on to the system as a normal
+# mail command.
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja, men uden den originale e-mail"
-#    2 = "Ja, og medtag den originale e-mail"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes, w/discard"
+#    2 = "Yes, w/forward"
 autorespond_requests = 0
 
-# Automatisk svar p&aring; e-mail til -request adressen.
+# Auto-response text to send to -request emails.
 autoresponse_request_text = ''
 
-# Antal dage imellem automatisk svar p&aring; e-mail, fra samme
-# afsender, til listen eller til -request/-owner adresserne. S&aelig;t
-# denne v&aelig;rdi til 0 (eller et negativt tal) for at sende
-# automatisk svar hver gang.
+# Number of days between auto-responses to either the mailing list or
+# -request/-owner address from the same poster.  Set to zero (or
+# negative) for no grace period (i.e. auto-respond to every message).
 autoresponse_graceperiod = 90
 
 ## Contentfilter options
 #
-# Regler for indhold i e-mail sendt til listen.
-# 
-# <p>Filtrering af indhold fungerer således: når listen modtager en
-# e-mail og du har beskyttelse med filtrering af indhold aktiveret,
-# sammenlignes først eventuelle vedh&aelig;ftninger med <a
-# href="?VARHELP=contentfilter/filter_mime_types">MIME filtrene</a>.
-# Hvis en vedh&aelig;ftning passer med et af disse filtre, bliver
-# vedh&aelig;ftningen fjernet.
-# 
-# <p>Derefter sammenlignes eventuelle vedh&aelig;ftninger med <a
-# href="?VARHELP=contentfilter/pass_mime_types">gyldige MIME typer</a>,
-# hvis nogen er defineret. Alle vedh&aelig;ftninger som ikke stemmer
-# overens med de angivne MIME typer, bliver fjernet.
-# 
-# <p>Efter filtreringen vil alle tomme <tt>multipart</tt>
-# vedh&aelig;ftninger v&aelig;re fjernet. Hvis selve meddelelsen er helt
-# tom efter denne filtrering, vil meddelelsen blive afvist. Derefter vil
-# enhver <tt>multipart/alternative</tt> vedh&aelig;ftning blive
-# erstattet af den første alternative som ikke er tom.
-# 
-# <p>Til sidst vil alle <tt>text/html</tt> vedh&aelig;ftninger som måtte
-# v&aelig;re tilbage i meddelelsen blive konverteret til
-# <tt>text/plain</tt> hvis <a
-# href="?VARHELP=contentfilter/convert_html_to_plaintext">konverter til
-# ren tekst</a> er sat til og serveren er konfigureret til at tillade
-# sådanne konverteringer.
-
-# Skal Mailman filtrere indhold i e-mail sendt til listen som angivet
-# nedenfor?
-#
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# Policies concerning the content of list traffic.
+# 
+# <p>Content filtering works like this: when a message is received by
+# the list and you have enabled content filtering, the individual
+# attachments are first compared to the <a
+# href="?VARHELP=contentfilter/filter_mime_types">filter types</a>.  If
+# the attachment type matches an entry in the filter types, it is
+# discarded.
+# 
+# <p>Then, if there are <a
+# href="?VARHELP=contentfilter/pass_mime_types">pass types</a> defined,
+# any attachment type that does <em>not</em> match a pass type is also
+# discarded.  If there are no pass types defined, this check is skipped.
+# 
+# <p>After this initial filtering, any <tt>multipart</tt> attachments
+# that are empty are removed.  If the outer message is left empty after
+# this filtering, then the whole message is discarded.
+# 
+# <p> Then, each <tt>multipart/alternative</tt> section will be replaced
+# by just the first alternative that is non-empty after filtering if <a
+# href="?VARHELP=contentfilter/collapse_alternatives"
+# >collapse_alternatives</a> is enabled.
+# 
+# <p>Finally, any <tt>text/html</tt> parts that are left in the message
+# may be converted to <tt>text/plain</tt> if <a
+# href="?VARHELP=contentfilter/convert_html_to_plaintext"
+# >convert_html_to_plaintext</a> is enabled and the site is configured
+# to allow these conversions.
+
+# Should Mailman filter the content of list traffic according to the
+# settings below?
+#
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 filter_content = 0
 
-# Brug denne indstilling til at fjerne vedh&aelig;ftninger der passer
-# til MIME typer. Hver linie skal her indeholde navnet på en MIME
-# type/subtype, f.eks. image/gif. Hvis du ønsker at fjerne alle
-# vedh&aelig;ftninger som har en given hoved MIME type, kan du undlade
-# at angive subtype, f.eks. image.
+# Use this option to remove each message attachment that matches one of
+# these content types.  Each line should contain a string naming a MIME
+# type/subtype, e.g. image/gif.  Leave off the subtype to remove all
+# parts with a matching major content type, e.g. image.
 # 
-# Tomme linier medtages ikke.
+# Blank lines are ignored.
 # 
-# Se også gyldige MIME typer for whitelist af MIME typer.
+# See also <a href="?VARHELP=contentfilter/pass_mime_types"
+# >pass_mime_types for a content type whitelist.
 filter_mime_types = ''
 
-# Brug denne indstilling for at definere hvilke MIME typer der skal være
-# tilladt. Krav og format for filtrering er identisk med MIME filtre.
+# Use this option to remove each message attachment that does not have a
+# matching content type.  Requirements and formats are exactly like <a
+# href="?VARHELP=contentfilter/filter_mime_types" >filter_mime_types.
 # 
-# Bem&aelig;rk: hvis du lægger noget ind her, men ikke angiver
-# multipart, vil ingen e-mail med vedh&aelig;ftninger blive medtaget.
+# Note: if you add entries to this list but don't add multipart to this
+# list, any messages with attachments will be rejected by the pass
+# filter.
 pass_mime_types = """multipart/mixed
 multipart/alternative
 text/plain"""
 
-# Skal Mailman konvertere text/html dele til ren tekst? Denne
-# konvertering vil finde sted efter at MIME filteret har fjernet de
-# uønskede dele.
+# Remove message attachments that have a matching filename extension.
+filter_filename_extensions = """exe
+bat
+cmd
+com
+pif
+scr
+vbs
+cpl"""
+
+# Remove message attachments that don't have a matching filename
+# extension.  Leave this field blank to skip this filter test.
+pass_filename_extensions = ''
+
+# Should Mailman collapse multipart/alternative to its first part
+# content?
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
+collapse_alternatives = True
+
+# Should Mailman convert text/html parts to plain text?  This conversion
+# happens after MIME attachments have been stripped.
+#
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 convert_html_to_plaintext = 1
 
-# Her bestemmer du hvad der skal ske, når en meddelelse filtreres fra af
-# et filter, altså hvis vedh&aelig;ftningen filtreres fra af MIME
-# filteret, eller en vedh&aelig;ftning ikke har en af de gyldige MIME
-# typer, eller meddelelsen ender med at være tom efter filtrering.
-# 
-# Bemærk at det du vælger her ikke vil ske hvis en meddelelse stadig
-# indeholder noget efter filtrering. Så vil meddelelsen altid blive
-# sendt videre til listen.
-# 
-# Når meddelelsen afvises, skrives Message-ID for den afviste meddelelse
-# til loggen. Når meddelelsen sendes retur eller videresendes til
-# listens ejer, vil en begrundelse altid blive inkluderet i den
-# returmail der sendes til afsenderen. Når meddelelserne skal bevares,
-# gemmes de i et specielt køkatalog på disken, sådan at
-# serveradministrator kan se (og måske gøre noget med) dem, men bliver
-# ellers fjernet. Dette sidste valg er kun tilgængeligt hvis
-# serveradministrator har tilladt det.
-#
-# gyldige værdier:
-#    0 = "Slet"
-#    1 = "Afvis"
-#    2 = "Videresend til Listens Ejer"
-#    3 = "Bevar"
+# One of these actions is taken when the message matches one of the
+# content filtering rules, meaning, the top-level content type matches
+# one of the <a href="?VARHELP=contentfilter/filter_mime_types"
+# >filter_mime_types, or the top-level content type does not match one
+# of the <a href="?VARHELP=contentfilter/pass_mime_types"
+# >pass_mime_types, or if after filtering the subparts of the message,
+# the message ends up empty.
+# 
+# Note this action is not taken if after filtering the message still
+# contains content.  In that case the message is always forwarded on to
+# the list membership.
+# 
+# When messages are discarded, a log entry is written containing the
+# Message-ID of the discarded message.  When messages are rejected or
+# forwarded to the list owner, a reason for the rejection is included in
+# the bounce message to the original author.  When messages are
+# preserved, they are saved in a special queue directory on disk for the
+# site administrator to view (and possibly rescue) but otherwise
+# discarded.  This last option is only available if enabled by the site
+# administrator.
+#
+# legal values are:
+#    0 = "Discard"
+#    1 = "Reject"
+#    2 = "Forward to List Owner"
+#    3 = "Preserve"
 filter_action = 0
 
 ## Topics options
 #
-# Emneord for listen
-
-# Emnefilteret kategoriserer hver e-mail som kommer til listen, efter de
-# regexp-udtryk du skriver nedenfor. Hvis felterne Subject: eller
-# Keywords: i brevhovedet i en mail stemmer overens med et af disse
-# udtryk, bliver mailen placeret under det p&aring;g&aelig;ldende emne.
-# Hvert medlem af listen kan vælge kun at modtage mail der passer til de
-# &oslash;nskede emner. E-mail som ikke h&oslash;rer under noget emne,
-# bliver ikke leveret.
-# 
-# Bem&aeligrk: Dette fungerer kun i normal-modus, ikke i
-# sammendrag-modus.
-# 
-# Indholdet i meddelelsen kan ogs&aring; unders&oslash;ges for Subject:
-# og Keyword: felter, alt efter hvad indstillingen
-# topics_bodylines_limit er sat til.
+# List topic keywords
+
+# The topic filter categorizes each incoming email message according to
+# <a href="http://www.python.org/doc/current/lib/module-re.html">regular
+# expression filters you specify below.  If the message's Subject: or
+# Keywords: header contains a match against a topic filter, the message
+# is logically placed into a topic bucket.  Each user can then choose to
+# only receive messages from the mailing list for a particular topic
+# bucket (or buckets).  Any message not categorized in a topic bucket
+# registered with the user is not delivered to the list.
+# 
+# Note that this feature only works with regular delivery, not digest
+# delivery.
+# 
+# The body of the message can also be optionally scanned for Subject:
+# and Keywords: headers, as specified by the <a
+# href="?VARHELP=topics/topics_bodylines_limit">topics_bodylines_limit
+# configuration variable.
 #
-# gyldige værdier:
-#    0 = "Ikke tilgængeligt"
-#    1 = "Tilgængeligt"
+# legal values are:
+#    0 = "Disabled"
+#    1 = "Enabled"
 topics_enabled = 0
 
-# Her angiver du hvor mange linier af mailens indhold emnefilteret skal
-# gennems&oslash;ge. En s&oslash;gning stopper n&aring;r det antal
-# linier er gennems&oslash;gt, eller n&aring;r den m&oslash;der en linie
-# som ikke ligner et brevhoved-felt. S&aelig;ttes denne v&aelig;rdi til
-# nul (0), vil ingen linier i indholdet blive unders&oslash;gt (dvs. kun
-# Keywords: og Subject: i brevhovedet unders&oslash;ges). S&aelig;ttes
-# denne v&aelig;rdi til et negativt tal, vil alle linier blive
-# unders&oslash;gt frem til den f&oslash;rste linie som ikke ligner et
-# brevhoved-felt.
+# The topic matcher will scan this many lines of the message body
+# looking for topic keyword matches.  Body scanning stops when either
+# this many lines have been looked at, or a non-header-like body line is
+# encountered.  By setting this value to zero, no body lines will be
+# scanned (i.e. only the Keywords: and Subject: headers will be
+# scanned).  By setting this value to a negative number, then all body
+# lines will be scanned until a non-header-like line is encountered.
+# 
 topics_bodylines_limit = 5
 
-# Hvert emneord er faktisk et regexp-udtryk, der sammenlignes med dele
-# af mailen, nemlig felterne Keywords: og Subject: i brevhovedet.
-# Bem&aelig;rk at de f&oslash;rste linier i mailens indhold ogs&aring;
-# kan best&aring; af s&aring;danne "felter", og de kan dermed ogs&aring;
-# blive unders&oslash;gt.
+# Each topic keyword is actually a regular expression, which is matched
+# against certain parts of a mail message, specifically the Keywords:
+# and Subject: message headers. Note that the first few lines of the
+# body of the message can also contain a Keywords: and Subject: "header"
+# on which matching is also performed.
 topics = []
 
diff --git a/mailman/trekroner.members b/mailman/trekroner.members
index f4dc8ee..38ab642 100644
--- a/mailman/trekroner.members
+++ b/mailman/trekroner.members
@@ -1,5 +1,22 @@
+Bjarne Andersen <Bjarne.Andersen@munksoegaard.dk>
+Lene Ejg Jarb?l <Ejg@ritzau.dk>
+Thomas Houkj?r <afrikanus1@hotmail.com>
+Anders Magnusson <am@jones.dk>
+anne.braae.tholstrup@munksoegaard.dk
+Annette Warming <annette_warming@munksoegaard.dk>
+Astrid Dahl <astrid.dahl@munksoegaard.dk>
+Bakmand <bolig34@munksoegaard.dk>
+Britt Karlsen <britt@rumfang.dk>
+cfm@munksoegaard.dk
+Christian Hedeskov <ch77@munksoegaard.dk>
 Eva <evadiekmann@mac.com>
+Jan Peiter <janpeiter@yahoo.dk>
 Jonas Smedegaard <jones@munksoegaard.dk>
+Lene  <lene.okholm@get2net.dk>
 Lene <lenet@munksoegaard.dk>
 Morten <mr8@munksoegaard.dk>
 Rikke Houkj?r <rikke_houkjaer@yahoo.dk>
+Siri Reiter <siri@jones.dk>
+Svanholm <svanholm@mac.com>
+Tomas Breddam <tomas@breddam.dk>
+ulf westergaard <ulfw@privat.dk>
diff --git a/mailman/trekroner.py b/mailman/trekroner.py
index e68ecb9..850eb1c 100644
--- a/mailman/trekroner.py
+++ b/mailman/trekroner.py
@@ -1,5 +1,7 @@
-## Indstillinger for maillisten "trekroner"  -*- python -*-
-## Dato: Sun Dec 11 16:36:07 2005
+# -*- python -*-
+# -*- coding: iso-8859-1 -*-
+## "trekroner" mailing list configuration settings
+## captured on Tue Mar 20 08:52:33 2007
 
 ## General options
 #
@@ -78,13 +80,17 @@ info = """&Aring;ben liste til l&oslash;st og fast om det at bo i Trekroner-omr&
 For at begr&aelig;nse spam genneml&aelig;ses emails fra ikke-medlemmer f&oslash;r de
 publiceres på listen.
 Hvis du er interesseret i at hj&aelig;lpe med at afvise spam men godkende
-*alt* legitimt (ingen smagsdommeri), så kontakt <a href="mailto:listmaster@jones.dk">listmaster@jones.dk</a>."""
+*alt* legitimt (ingen smagsdommeri), så kontakt <a href=\"mailto:listmaster@jones.dk\">listmaster@jones.dk</a>."""
 
-# This text will be prepended to subject lines of messages posted to the
-# list, to distinguish mailing list messages in in mailbox summaries.
-# Brevity is premium here, it's ok to shorten long mailing list names to
-# something more concise, as long as it still identifies the mailing
-# list.
+# Denne tekst vil blive placeret foran emnet i mails sendt til listen
+# for nemmere og kunne skelne mail fra listen i indboksen i
+# postprogrammet. Teksten b&oslash;r holdes kort. Det er iorden og
+# sk&aelig;re et langt listenavn ned til et mere kortfattet navn
+# s&aring;l&aelig;nge det stadig er beskrivende for listen. Du kan
+# ogs&aring; tilf&oslash;je et fortl&oslash;bende nummer ved at bruge %d
+# substitutions direktivet f.eks. [listenavn %d] -> [listenavn 123]
+# (listenavn %05d) -> (listenavn 00123)
+# 
 subject_prefix = '[Trekroner] '
 
 # Skjul afsenderen af meddelelser, ved at erstatte den med e-maillistens
@@ -105,31 +111,32 @@ anonymous_list = False
 #    1 = "Ja"
 first_strip_reply_to = False
 
-# Denne indstillling fort&aelig;ller hvad Mailman skal g&oslash;re med
-# Reply-To: feltet i brevhovedet p&aring; e-mail der sendes til listen.
-# Hvis den er sat til Afsender, vil Mailman ikke tilf&oslash;je noget
-# Reply-To: felt, men findes et s&aring;dant felt allerede, vil det ikke
-# blive fjernet. S&aelig;ttes indstillingen til enten e-maillistens
-# adresse eller Egendefineret adresse, vil Mailman tilf&oslash;je, evt.
-# erstatte, et Reply-To: felt. (Egendefineret adresse inds&aelig;tter
-# v&aelig;rdien af indstillingen reply_to_address).
-# 
-# Der er flere grunde til ikke at indf&oslash;re eller erstatte
-# Reply-To: felter. En grund kan v&aelig;re at nogen af dem der sender
-# mail til listen er afh&aelig;ngige af selv at kunne s&aelig;tte
-# Reply-To: adressen. En anden grund er at modifikation af Reply-To:
-# adressen g&oslash;r det vanskeligere kun at sende svar til afsender.
-# Se 'Reply-To' Munging Considered Harmful for en diskussion omkring
-# emnet. Se Reply-To Munging Considered Useful for modsatte meninger.
-# 
-# Nogle maillister har begr&aelig;nset adgang, med en parallel liste
-# beregnet til diskussioner. Eksempler p&aring; dette er 'patches' eller
-# 'checkin' lister, som system for revisionskontrol sender
-# &aelig;ndringer i programmet til, men diskussioner omkring udvikling
-# af programmet sendes til udviklernes egen mailliste. For at
-# underst&oslash;tte lignende e-maillister, v&aelig;lg Egendefineret
-# adresse og s&aelig;t Reply-To: adressen i indstillingen
-# reply_to_address til at pege på den parallelle diskussionsliste.
+# This option controls what Mailman does to the Reply-To: header in
+# messages flowing through this mailing list.  When set to Poster, no
+# Reply-To: header is added by Mailman, although if one is present in
+# the original message, it is not stripped.  Setting this value to
+# either This list or Explicit address causes Mailman to insert a
+# specific Reply-To: header in all messages, overriding the header in
+# the original message if necessary (Explicit address inserts the value
+# of <a href="?VARHELP=general/reply_to_address">reply_to_address).
+# 
+# There are many reasons not to introduce or override the Reply-To:
+# header.  One is that some posters depend on their own Reply-To:
+# settings to convey their valid return address.  Another is that
+# modifying Reply-To: makes it much more difficult to send private
+# replies.  See <a
+# href="http://www.unicom.com/pw/reply-to-harmful.html">`Reply-To'
+# Munging Considered Harmful for a general discussion of this issue.
+# See <a
+# href="http://www.metasystema.net/essays/reply-to.mhtml">Reply-To
+# Munging Considered Useful for a dissenting opinion.
+# 
+# Some mailing lists have restricted posting privileges, with a parallel
+# list devoted to discussions.  Examples are `patches' or `checkin'
+# lists, where software changes are posted by a revision control system,
+# but discussion about the changes occurs on a developers mailing list.
+# To support these types of mailing lists, select Explicit address and
+# set the Reply-To: address below to point to the parallel list.
 #
 # gyldige værdier:
 #    0 = "Afsender"
@@ -137,29 +144,31 @@ first_strip_reply_to = False
 #    2 = "Egendefineret adresse"
 reply_goes_to_list = 0
 
-# Her definerer du adressen der skal s&aelig;ttes i Reply-To: feltet
-# n&aring;r indstillingen reply_goes_to_list er sat til Egendefineret
-# adresse.
-# 
-# Der findes mange grunde til at ikke indf&oslash;re eller erstatte
-# Reply-To: felter. En grund kan v&aelig;re at nogen af dem der sender
-# e-mail til listen er afh&aelig;ngige af selv at kunne s&aelig;tte
-# Reply-To: adressen. En anden grund er at modificering af Reply-To:
-# adressen g&oslash;r det vanskeligere at sende svar kun til afsender.
-# Se 'Reply-To' Munging Considered Harmful for en diskussion omkring
-# temaet. Se Reply-To Munging Considered Useful for modsatte meninger.
-# 
-# Nogle maillister har begr&aelig;nset adgang, med en egen parallel
-# liste beregnet for diskussioner. Eksempler p&aring; dette er 'patches'
-# eller 'checkin' lister, som system for revisionskontrol sender
-# &aelig;ndringer i programmet til, mens diskussioner omkring udvikling
-# af programmet sendes til udviklernes egen mailliste. For at
-# underst&oslash;tte s&aring;danne maillister, kan du definere Reply-To:
-# adressen her, og vælge Egendefineret adresse i indstillingen
-# reply_goes_to_list.
-# 
-# Bem&aelig;rk at hvis den oprindelige meddelelse indeholder et
-# Reply-To: felt, vil det ikke &aelig;ndres.
+# This is the address set in the Reply-To: header when the <a
+# href="?VARHELP=general/reply_goes_to_list">reply_goes_to_list option
+# is set to Explicit address.
+# 
+# There are many reasons not to introduce or override the Reply-To:
+# header.  One is that some posters depend on their own Reply-To:
+# settings to convey their valid return address.  Another is that
+# modifying Reply-To: makes it much more difficult to send private
+# replies.  See <a
+# href="http://www.unicom.com/pw/reply-to-harmful.html">`Reply-To'
+# Munging Considered Harmful for a general discussion of this issue.
+# See <a
+# href="http://www.metasystema.net/essays/reply-to.mhtml">Reply-To
+# Munging Considered Useful for a dissenting opinion.
+# 
+# Some mailing lists have restricted posting privileges, with a parallel
+# list devoted to discussions.  Examples are `patches' or `checkin'
+# lists, where software changes are posted by a revision control system,
+# but discussion about the changes occurs on a developers mailing list.
+# To support these types of mailing lists, specify the explicit
+# Reply-To: address here.  You must also specify Explicit address in the
+# reply_goes_to_list variable.
+# 
+# Note that if the original message contains a Reply-To: header, it will
+# not be changed.
 reply_to_address = ''
 
 # V&aelig;lg kun 'ja' her, hvis listen skal bruges som  "paraply" for
@@ -259,11 +268,10 @@ admin_immed_notify = True
 # gyldige værdier:
 #    0 = "Nej"
 #    1 = "Ja"
-admin_notify_mchanges = True
+admin_notify_mchanges = 1
 
-# Approval notices are sent when mail triggers certain of the limits
-# except routine list moderation and spam filters, for which notices are
-# not sent.  This option overrides ever sending the notice.
+# Send e-mail til afsendere n&aring;r deres e-mail til listen holdes
+# tilbage for godkendelse?
 #
 # gyldige værdier:
 #    0 = "Nej"
@@ -341,6 +349,10 @@ include_rfc2369_headers = 1
 #    1 = "Ja"
 include_list_post_header = 1
 
+# Slet alle tilbageholdte beskeder der er ældre end dette antal dage.
+# Brug 0 for at slå automatisk sletning fra.
+max_days_to_hold = 0
+
 ## Language options
 #
 # Underst&oslash;ttelse af flere sprog. (Internationalisering)
@@ -394,59 +406,57 @@ encode_ascii_prefixes = 2
 nondigestable = True
 
 # Tekst der tilføjes &oslash;verst i e-mail der sendes til listens
-# medlemmer. Teksten kan inneholde formateringskoder som byttes ut med
-# verdier fra listens oppsett. For detaljer, se Pythons
+# medlemmer. Teksten kan indeholde formateringskoder som udskiftes med
+# v&aelig;rdier fra listens ops&aelig;tning. For detaljer, se Pythons
 # formateringsregler (engelsk). Gyldige koder er:
 # 
 # 
 # real_name - Listens formaterede navn; normalt listenavnet med stort
 # forbogstav eller store bogstaver enkelte steder.
 # 
-# list_name - Listens navn som brugt i URLer, der det har betydning om
+# list_name - Listens navn som brugt i URLer, hvor det har betydning om
 # den staves med store eller sm&aring; bogstaver. (For
 # bagudkompatibilitet, er _internal_name det samme.)
 # 
-# host_name - Internetadressen (fully qulified domain name) til maskinen
-# som listeserveren g&aring;r p&aring;.
+# host_name - Internetadressen (fully qualified domain name) til
+# maskinen som listeserveren k&oslash;rer p&aring;.
 # 
-# web_page_url - Basis URL for Mailman. Denne kan laegges til sammen
-# med, f.eks. listinfo/%(internal_name)s for &aring; danne URLen til en
-# listes infoside.
+# web_page_url - Basis URL for Mailman. Denne kan kombineres med f.eks.
+# listinfo/%(list_name)s for at danne URLen til en listes infoside.
 # 
 # description - En kort beskrivelse af listen.
 # 
-# info - Full beskrivelse af listen.
+# info - Fuld beskrivelse af listen.
 # 
-# cgiext - Tillaeg som laegges til CGI scripts.
+# cgiext - Extension som tilf&oslash;jes CGI scripts.
 # 
 # 
 msg_header = ''
 
 # Tekst som tilf&oslash;jes nederst i e-mail der sendes til listens
-# medlemmer. Teksten kan inneholde formateringskoder som byttes ut med
-# verdier fra listens oppsett. For detaljer, se Pythons
+# medlemmer. Teksten kan indeholde formateringskoder som udskiftes med
+# v&aelig;rdier fra listens ops&aelig;tning. For detaljer, se Pythons
 # formateringsregler (engelsk). Gyldige koder er:
 # 
 # 
 # real_name - Listens formaterede navn; normalt listenavnet med stort
 # forbogstav eller store bogstaver enkelte steder.
 # 
-# list_name - Listens navn som brugt i URLer, der det har betydning om
+# list_name - Listens navn som brugt i URLer, hvor det har betydning om
 # den staves med store eller sm&aring; bogstaver. (For
 # bagudkompatibilitet, er _internal_name det samme.)
 # 
-# host_name - Internetadressen (fully qulified domain name) til maskinen
-# som listeserveren g&aring;r p&aring;.
+# host_name - Internetadressen (fully qualified domain name) til
+# maskinen som listeserveren k&oslash;rer p&aring;.
 # 
-# web_page_url - Basis URL for Mailman. Denne kan laegges til sammen
-# med, f.eks. listinfo/%(internal_name)s for &aring; danne URLen til en
-# listes infoside.
+# web_page_url - Basis URL for Mailman. Denne kan kombineres med f.eks.
+# listinfo/%(list_name)s for at danne URLen til en listes infoside.
 # 
 # description - En kort beskrivelse af listen.
 # 
-# info - Full beskrivelse af listen.
+# info - Fuld beskrivelse af listen.
 # 
-# cgiext - Tillaeg som laegges til CGI scripts.
+# cgiext - Extension som tilf&oslash;jes CGI scripts.
 # 
 # 
 msg_footer = """-- 
@@ -456,6 +466,17 @@ msg_footer = """--
 
 NB! Alle indl&aelig;g er offentligt tilg&aelig;ngelige!"""
 
+# Når du fjerner vedh&aelig;ftninger, gemmes de i et arkiv område og der
+# laves istedet links i e-mailen således at medlemmer kan tilgå
+# vedh&aelig;ftninger via en webbrowser. Hvis du vil have
+# vedh&aelig;ftninger til helt og forsvinde så kan du bruge et
+# indholdsfilter.
+#
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
+scrub_nondigest = False
+
 ## Digest options
 #
 # Opsætning af sammendrag-modus.
@@ -494,59 +515,57 @@ digest_size_threshhold = 300
 digest_send_periodic = True
 
 # Tekst som tilf&oslash;jes &oslash;verst i samle-emailen, f&oslash;r
-# indholdsfortegnelsen.Teksten kan inneholde formateringskoder som
-# byttes ut med verdier fra listens oppsett. For detaljer, se Pythons
-# formateringsregler (engelsk). Gyldige koder er:
+# indholdsfortegnelsen.Teksten kan indeholde formateringskoder som
+# udskiftes med v&aelig;rdier fra listens ops&aelig;tning. For detaljer,
+# se Pythons formateringsregler (engelsk). Gyldige koder er:
 # 
 # 
 # real_name - Listens formaterede navn; normalt listenavnet med stort
 # forbogstav eller store bogstaver enkelte steder.
 # 
-# list_name - Listens navn som brugt i URLer, der det har betydning om
+# list_name - Listens navn som brugt i URLer, hvor det har betydning om
 # den staves med store eller sm&aring; bogstaver. (For
 # bagudkompatibilitet, er _internal_name det samme.)
 # 
-# host_name - Internetadressen (fully qulified domain name) til maskinen
-# som listeserveren g&aring;r p&aring;.
+# host_name - Internetadressen (fully qualified domain name) til
+# maskinen som listeserveren k&oslash;rer p&aring;.
 # 
-# web_page_url - Basis URL for Mailman. Denne kan laegges til sammen
-# med, f.eks. listinfo/%(internal_name)s for &aring; danne URLen til en
-# listes infoside.
+# web_page_url - Basis URL for Mailman. Denne kan kombineres med f.eks.
+# listinfo/%(list_name)s for at danne URLen til en listes infoside.
 # 
 # description - En kort beskrivelse af listen.
 # 
-# info - Full beskrivelse af listen.
+# info - Fuld beskrivelse af listen.
 # 
-# cgiext - Tillaeg som laegges til CGI scripts.
+# cgiext - Extension som tilf&oslash;jes CGI scripts.
 # 
 # 
 digest_header = ''
 
 # Tekst der tilføjes nederst i hver samle-email, som sidste
-# information.Teksten kan inneholde formateringskoder som byttes ut med
-# verdier fra listens oppsett. For detaljer, se Pythons
+# information.Teksten kan indeholde formateringskoder som udskiftes med
+# v&aelig;rdier fra listens ops&aelig;tning. For detaljer, se Pythons
 # formateringsregler (engelsk). Gyldige koder er:
 # 
 # 
 # real_name - Listens formaterede navn; normalt listenavnet med stort
 # forbogstav eller store bogstaver enkelte steder.
 # 
-# list_name - Listens navn som brugt i URLer, der det har betydning om
+# list_name - Listens navn som brugt i URLer, hvor det har betydning om
 # den staves med store eller sm&aring; bogstaver. (For
 # bagudkompatibilitet, er _internal_name det samme.)
 # 
-# host_name - Internetadressen (fully qulified domain name) til maskinen
-# som listeserveren g&aring;r p&aring;.
+# host_name - Internetadressen (fully qualified domain name) til
+# maskinen som listeserveren k&oslash;rer p&aring;.
 # 
-# web_page_url - Basis URL for Mailman. Denne kan laegges til sammen
-# med, f.eks. listinfo/%(internal_name)s for &aring; danne URLen til en
-# listes infoside.
+# web_page_url - Basis URL for Mailman. Denne kan kombineres med f.eks.
+# listinfo/%(list_name)s for at danne URLen til en listes infoside.
 # 
 # description - En kort beskrivelse af listen.
 # 
-# info - Full beskrivelse af listen.
+# info - Fuld beskrivelse af listen.
 # 
-# cgiext - Tillaeg som laegges til CGI scripts.
+# cgiext - Extension som tilf&oslash;jes CGI scripts.
 # 
 # 
 digest_footer = """-- 
@@ -771,6 +790,12 @@ generic_nonmember_action = 1
 #    1 = "Ja"
 forward_auto_discards = 1
 
+# Tekst der skal inkluderes i en meddelelse om afvisning der sendes til
+# ikke-medlemmer der poster til listen. Denne meddelelse kan inkludere
+# listeejerens adresse vha. %(listowner)s og den erstatter den
+# automatisk konstruerede standard meddelelse.
+nonmember_rejection_notice = ''
+
 ## Privacy options
 #
 # Her kan du ops&aelig;tte filtrering baseret på modtageren af
@@ -828,15 +853,22 @@ max_num_recipients = 10
 # Her kan du opsætte forskellige anti-spam filtre, som kan bidrage til
 # at reducere mængden af spam der distribueres via e-maillisten.
 
-# Each header filter rule has two parts, a list of regular expressions,
-# one per line, and an action to take.  Mailman matches the message's
-# headers against every regular expression in the rule and if any match,
-# the message is rejected, held, or discarded based on the action you
-# specify.  Use Defer to temporarily disable a rule.
-# 
-# You can have more than one filter rule for your list.  In that case,
-# each rule is matched in turn, with processing stopped after the first
-# match.
+# Hver filterregel best&aring;r af to dele: en liste med regexp-udtryk,
+# et pr. linie, og en aktion der skal udf&oslash;res. Mailman
+# sammenligner meddelelsens brevhoved med alle regexp-udtryk i reglen,
+# og hvis der er overensstemmelse, vil meddelelsen blive afvist,
+# tilbageholdt eller slettet, afh&aelig;ngigt af hvilken aktion du har
+# angivet her. Brug Afvent for midlertidigt at s&aelig;tte en regel ud
+# af kraft.
+# 
+# Du kan have flere end en regel for din liste.  I s&aring; fald vil
+# hver regel blive anvendt efter tur, og processen stopper f&oslash;rste
+# gang der findes overensstemmelse.
+# 
+# Bemærk at brevhovedlinier indsamles fra alle vedh&aelig;ftninger
+# (undtagen fra mailman administrivia meddelelser) og sammenlignes med
+# regexp-udtrykkene. Ved brug af denne funktionalitet kan du effektivt
+# sortere meddelelser fra med farlige filtyper eller filnavn-endelser.
 header_filter_rules = []
 
 # Brug denne indstilling til at bortfiltrere mail til listen, baseret
@@ -1143,32 +1175,34 @@ autoresponse_graceperiod = 90
 
 ## Contentfilter options
 #
-# Regler for indhold i e-mail sendt til listen.
-# 
-# <p>Filtrering af indhold fungerer således: når listen modtager en
-# e-mail og du har beskyttelse med filtrering af indhold aktiveret,
-# sammenlignes først eventuelle vedh&aelig;ftninger med <a
-# href="?VARHELP=contentfilter/filter_mime_types">MIME filtrene</a>.
-# Hvis en vedh&aelig;ftning passer med et af disse filtre, bliver
-# vedh&aelig;ftningen fjernet.
-# 
-# <p>Derefter sammenlignes eventuelle vedh&aelig;ftninger med <a
-# href="?VARHELP=contentfilter/pass_mime_types">gyldige MIME typer</a>,
-# hvis nogen er defineret. Alle vedh&aelig;ftninger som ikke stemmer
-# overens med de angivne MIME typer, bliver fjernet.
-# 
-# <p>Efter filtreringen vil alle tomme <tt>multipart</tt>
-# vedh&aelig;ftninger v&aelig;re fjernet. Hvis selve meddelelsen er helt
-# tom efter denne filtrering, vil meddelelsen blive afvist. Derefter vil
-# enhver <tt>multipart/alternative</tt> vedh&aelig;ftning blive
-# erstattet af den første alternative som ikke er tom.
-# 
-# <p>Til sidst vil alle <tt>text/html</tt> vedh&aelig;ftninger som måtte
-# v&aelig;re tilbage i meddelelsen blive konverteret til
-# <tt>text/plain</tt> hvis <a
-# href="?VARHELP=contentfilter/convert_html_to_plaintext">konverter til
-# ren tekst</a> er sat til og serveren er konfigureret til at tillade
-# sådanne konverteringer.
+# Policies concerning the content of list traffic.
+# 
+# <p>Content filtering works like this: when a message is received by
+# the list and you have enabled content filtering, the individual
+# attachments are first compared to the <a
+# href="?VARHELP=contentfilter/filter_mime_types">filter types</a>.  If
+# the attachment type matches an entry in the filter types, it is
+# discarded.
+# 
+# <p>Then, if there are <a
+# href="?VARHELP=contentfilter/pass_mime_types">pass types</a> defined,
+# any attachment type that does <em>not</em> match a pass type is also
+# discarded.  If there are no pass types defined, this check is skipped.
+# 
+# <p>After this initial filtering, any <tt>multipart</tt> attachments
+# that are empty are removed.  If the outer message is left empty after
+# this filtering, then the whole message is discarded.
+# 
+# <p> Then, each <tt>multipart/alternative</tt> section will be replaced
+# by just the first alternative that is non-empty after filtering if <a
+# href="?VARHELP=contentfilter/collapse_alternatives"
+# >collapse_alternatives</a> is enabled.
+# 
+# <p>Finally, any <tt>text/html</tt> parts that are left in the message
+# may be converted to <tt>text/plain</tt> if <a
+# href="?VARHELP=contentfilter/convert_html_to_plaintext"
+# >convert_html_to_plaintext</a> is enabled and the site is configured
+# to allow these conversions.
 
 # Skal Mailman filtrere indhold i e-mail sendt til listen som angivet
 # nedenfor?
@@ -1198,6 +1232,28 @@ pass_mime_types = """multipart/mixed
 multipart/alternative
 text/plain"""
 
+# Fjern e-mailvedh&aelig;ftninger med passende filnavn-endelser.
+filter_filename_extensions = """exe
+bat
+cmd
+com
+pif
+scr
+vbs
+cpl"""
+
+# Fjern alle vedh&aelig;ftninger der ikke har en passende
+# filnavn-endelse. Lad dette felt være tomt for at udelade dette filter.
+pass_filename_extensions = ''
+
+# Should Mailman collapse multipart/alternative to its first part
+# content?
+#
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
+collapse_alternatives = True
+
 # Skal Mailman konvertere text/html dele til ren tekst? Denne
 # konvertering vil finde sted efter at MIME filteret har fjernet de
 # uønskede dele.
diff --git a/mailman/uge29.py b/mailman/uge29.py
index 59a59be..86328ce 100644
--- a/mailman/uge29.py
+++ b/mailman/uge29.py
@@ -1,5 +1,7 @@
-## Indstillinger for maillisten "uge29"  -*- python -*-
-## Dato: Sun Dec 11 16:36:09 2005
+# -*- python -*-
+# -*- coding: iso-8859-1 -*-
+## "uge29" mailing list configuration settings
+## captured on Tue Mar 20 08:52:38 2007
 
 ## General options
 #
@@ -59,7 +61,7 @@ moderator = []
 # med andre maillister, i toptekster, osv. Den b&oslash;r v&aelig;re
 # s&aring; kort som overhovedet mulig, uden at det bliver uklart hvad
 # meningen med maillisten er eller hvad den skal bruges til.
-description = 'Deltagere i uge 29 p\xe5 Drej\xf8 \xd8-lejr'
+description = "Deltagere i uge 29 på Drejø Ø-lejr"
 
 # Teksten tolkes som html bortset fra linieskift, der vil blive
 # &aelig;ndret til html-tag'et '<br>', sådan at du kan benytte links,
@@ -79,11 +81,15 @@ Alle kan sende til listen, og tilmelde sig at modtage.
 Der er offentlig adgang til email-arkiv.
 """
 
-# This text will be prepended to subject lines of messages posted to the
-# list, to distinguish mailing list messages in in mailbox summaries.
-# Brevity is premium here, it's ok to shorten long mailing list names to
-# something more concise, as long as it still identifies the mailing
-# list.
+# Denne tekst vil blive placeret foran emnet i mails sendt til listen
+# for nemmere og kunne skelne mail fra listen i indboksen i
+# postprogrammet. Teksten b&oslash;r holdes kort. Det er iorden og
+# sk&aelig;re et langt listenavn ned til et mere kortfattet navn
+# s&aring;l&aelig;nge det stadig er beskrivende for listen. Du kan
+# ogs&aring; tilf&oslash;je et fortl&oslash;bende nummer ved at bruge %d
+# substitutions direktivet f.eks. [listenavn %d] -> [listenavn 123]
+# (listenavn %05d) -> (listenavn 00123)
+# 
 subject_prefix = '[Uge29] '
 
 # Skjul afsenderen af meddelelser, ved at erstatte den med e-maillistens
@@ -104,31 +110,32 @@ anonymous_list = False
 #    1 = "Ja"
 first_strip_reply_to = False
 
-# Denne indstillling fort&aelig;ller hvad Mailman skal g&oslash;re med
-# Reply-To: feltet i brevhovedet p&aring; e-mail der sendes til listen.
-# Hvis den er sat til Afsender, vil Mailman ikke tilf&oslash;je noget
-# Reply-To: felt, men findes et s&aring;dant felt allerede, vil det ikke
-# blive fjernet. S&aelig;ttes indstillingen til enten e-maillistens
-# adresse eller Egendefineret adresse, vil Mailman tilf&oslash;je, evt.
-# erstatte, et Reply-To: felt. (Egendefineret adresse inds&aelig;tter
-# v&aelig;rdien af indstillingen reply_to_address).
-# 
-# Der er flere grunde til ikke at indf&oslash;re eller erstatte
-# Reply-To: felter. En grund kan v&aelig;re at nogen af dem der sender
-# mail til listen er afh&aelig;ngige af selv at kunne s&aelig;tte
-# Reply-To: adressen. En anden grund er at modifikation af Reply-To:
-# adressen g&oslash;r det vanskeligere kun at sende svar til afsender.
-# Se 'Reply-To' Munging Considered Harmful for en diskussion omkring
-# emnet. Se Reply-To Munging Considered Useful for modsatte meninger.
-# 
-# Nogle maillister har begr&aelig;nset adgang, med en parallel liste
-# beregnet til diskussioner. Eksempler p&aring; dette er 'patches' eller
-# 'checkin' lister, som system for revisionskontrol sender
-# &aelig;ndringer i programmet til, men diskussioner omkring udvikling
-# af programmet sendes til udviklernes egen mailliste. For at
-# underst&oslash;tte lignende e-maillister, v&aelig;lg Egendefineret
-# adresse og s&aelig;t Reply-To: adressen i indstillingen
-# reply_to_address til at pege på den parallelle diskussionsliste.
+# This option controls what Mailman does to the Reply-To: header in
+# messages flowing through this mailing list.  When set to Poster, no
+# Reply-To: header is added by Mailman, although if one is present in
+# the original message, it is not stripped.  Setting this value to
+# either This list or Explicit address causes Mailman to insert a
+# specific Reply-To: header in all messages, overriding the header in
+# the original message if necessary (Explicit address inserts the value
+# of <a href="?VARHELP=general/reply_to_address">reply_to_address).
+# 
+# There are many reasons not to introduce or override the Reply-To:
+# header.  One is that some posters depend on their own Reply-To:
+# settings to convey their valid return address.  Another is that
+# modifying Reply-To: makes it much more difficult to send private
+# replies.  See <a
+# href="http://www.unicom.com/pw/reply-to-harmful.html">`Reply-To'
+# Munging Considered Harmful for a general discussion of this issue.
+# See <a
+# href="http://www.metasystema.net/essays/reply-to.mhtml">Reply-To
+# Munging Considered Useful for a dissenting opinion.
+# 
+# Some mailing lists have restricted posting privileges, with a parallel
+# list devoted to discussions.  Examples are `patches' or `checkin'
+# lists, where software changes are posted by a revision control system,
+# but discussion about the changes occurs on a developers mailing list.
+# To support these types of mailing lists, select Explicit address and
+# set the Reply-To: address below to point to the parallel list.
 #
 # gyldige værdier:
 #    0 = "Afsender"
@@ -136,29 +143,31 @@ first_strip_reply_to = False
 #    2 = "Egendefineret adresse"
 reply_goes_to_list = 1
 
-# Her definerer du adressen der skal s&aelig;ttes i Reply-To: feltet
-# n&aring;r indstillingen reply_goes_to_list er sat til Egendefineret
-# adresse.
-# 
-# Der findes mange grunde til at ikke indf&oslash;re eller erstatte
-# Reply-To: felter. En grund kan v&aelig;re at nogen af dem der sender
-# e-mail til listen er afh&aelig;ngige af selv at kunne s&aelig;tte
-# Reply-To: adressen. En anden grund er at modificering af Reply-To:
-# adressen g&oslash;r det vanskeligere at sende svar kun til afsender.
-# Se 'Reply-To' Munging Considered Harmful for en diskussion omkring
-# temaet. Se Reply-To Munging Considered Useful for modsatte meninger.
-# 
-# Nogle maillister har begr&aelig;nset adgang, med en egen parallel
-# liste beregnet for diskussioner. Eksempler p&aring; dette er 'patches'
-# eller 'checkin' lister, som system for revisionskontrol sender
-# &aelig;ndringer i programmet til, mens diskussioner omkring udvikling
-# af programmet sendes til udviklernes egen mailliste. For at
-# underst&oslash;tte s&aring;danne maillister, kan du definere Reply-To:
-# adressen her, og vælge Egendefineret adresse i indstillingen
-# reply_goes_to_list.
-# 
-# Bem&aelig;rk at hvis den oprindelige meddelelse indeholder et
-# Reply-To: felt, vil det ikke &aelig;ndres.
+# This is the address set in the Reply-To: header when the <a
+# href="?VARHELP=general/reply_goes_to_list">reply_goes_to_list option
+# is set to Explicit address.
+# 
+# There are many reasons not to introduce or override the Reply-To:
+# header.  One is that some posters depend on their own Reply-To:
+# settings to convey their valid return address.  Another is that
+# modifying Reply-To: makes it much more difficult to send private
+# replies.  See <a
+# href="http://www.unicom.com/pw/reply-to-harmful.html">`Reply-To'
+# Munging Considered Harmful for a general discussion of this issue.
+# See <a
+# href="http://www.metasystema.net/essays/reply-to.mhtml">Reply-To
+# Munging Considered Useful for a dissenting opinion.
+# 
+# Some mailing lists have restricted posting privileges, with a parallel
+# list devoted to discussions.  Examples are `patches' or `checkin'
+# lists, where software changes are posted by a revision control system,
+# but discussion about the changes occurs on a developers mailing list.
+# To support these types of mailing lists, specify the explicit
+# Reply-To: address here.  You must also specify Explicit address in the
+# reply_goes_to_list variable.
+# 
+# Note that if the original message contains a Reply-To: header, it will
+# not be changed.
 reply_to_address = ''
 
 # V&aelig;lg kun 'ja' her, hvis listen skal bruges som  "paraply" for
@@ -258,9 +267,8 @@ admin_immed_notify = True
 #    1 = "Ja"
 admin_notify_mchanges = False
 
-# Approval notices are sent when mail triggers certain of the limits
-# except routine list moderation and spam filters, for which notices are
-# not sent.  This option overrides ever sending the notice.
+# Send e-mail til afsendere n&aring;r deres e-mail til listen holdes
+# tilbage for godkendelse?
 #
 # gyldige værdier:
 #    0 = "Nej"
@@ -338,6 +346,10 @@ include_rfc2369_headers = 1
 #    1 = "Ja"
 include_list_post_header = 1
 
+# Slet alle tilbageholdte beskeder der er ældre end dette antal dage.
+# Brug 0 for at slå automatisk sletning fra.
+max_days_to_hold = 0
+
 ## Language options
 #
 # Underst&oslash;ttelse af flere sprog. (Internationalisering)
@@ -391,59 +403,57 @@ encode_ascii_prefixes = 2
 nondigestable = True
 
 # Tekst der tilføjes &oslash;verst i e-mail der sendes til listens
-# medlemmer. Teksten kan inneholde formateringskoder som byttes ut med
-# verdier fra listens oppsett. For detaljer, se Pythons
+# medlemmer. Teksten kan indeholde formateringskoder som udskiftes med
+# v&aelig;rdier fra listens ops&aelig;tning. For detaljer, se Pythons
 # formateringsregler (engelsk). Gyldige koder er:
 # 
 # 
 # real_name - Listens formaterede navn; normalt listenavnet med stort
 # forbogstav eller store bogstaver enkelte steder.
 # 
-# list_name - Listens navn som brugt i URLer, der det har betydning om
+# list_name - Listens navn som brugt i URLer, hvor det har betydning om
 # den staves med store eller sm&aring; bogstaver. (For
 # bagudkompatibilitet, er _internal_name det samme.)
 # 
-# host_name - Internetadressen (fully qulified domain name) til maskinen
-# som listeserveren g&aring;r p&aring;.
+# host_name - Internetadressen (fully qualified domain name) til
+# maskinen som listeserveren k&oslash;rer p&aring;.
 # 
-# web_page_url - Basis URL for Mailman. Denne kan laegges til sammen
-# med, f.eks. listinfo/%(internal_name)s for &aring; danne URLen til en
-# listes infoside.
+# web_page_url - Basis URL for Mailman. Denne kan kombineres med f.eks.
+# listinfo/%(list_name)s for at danne URLen til en listes infoside.
 # 
 # description - En kort beskrivelse af listen.
 # 
-# info - Full beskrivelse af listen.
+# info - Fuld beskrivelse af listen.
 # 
-# cgiext - Tillaeg som laegges til CGI scripts.
+# cgiext - Extension som tilf&oslash;jes CGI scripts.
 # 
 # 
 msg_header = ''
 
 # Tekst som tilf&oslash;jes nederst i e-mail der sendes til listens
-# medlemmer. Teksten kan inneholde formateringskoder som byttes ut med
-# verdier fra listens oppsett. For detaljer, se Pythons
+# medlemmer. Teksten kan indeholde formateringskoder som udskiftes med
+# v&aelig;rdier fra listens ops&aelig;tning. For detaljer, se Pythons
 # formateringsregler (engelsk). Gyldige koder er:
 # 
 # 
 # real_name - Listens formaterede navn; normalt listenavnet med stort
 # forbogstav eller store bogstaver enkelte steder.
 # 
-# list_name - Listens navn som brugt i URLer, der det har betydning om
+# list_name - Listens navn som brugt i URLer, hvor det har betydning om
 # den staves med store eller sm&aring; bogstaver. (For
 # bagudkompatibilitet, er _internal_name det samme.)
 # 
-# host_name - Internetadressen (fully qulified domain name) til maskinen
-# som listeserveren g&aring;r p&aring;.
+# host_name - Internetadressen (fully qualified domain name) til
+# maskinen som listeserveren k&oslash;rer p&aring;.
 # 
-# web_page_url - Basis URL for Mailman. Denne kan laegges til sammen
-# med, f.eks. listinfo/%(internal_name)s for &aring; danne URLen til en
-# listes infoside.
+# web_page_url - Basis URL for Mailman. Denne kan kombineres med f.eks.
+# listinfo/%(list_name)s for at danne URLen til en listes infoside.
 # 
 # description - En kort beskrivelse af listen.
 # 
-# info - Full beskrivelse af listen.
+# info - Fuld beskrivelse af listen.
 # 
-# cgiext - Tillaeg som laegges til CGI scripts.
+# cgiext - Extension som tilf&oslash;jes CGI scripts.
 # 
 # 
 msg_footer = """_______________________________________________
@@ -451,6 +461,17 @@ msg_footer = """_______________________________________________
 %(real_name)s@%(host_name)s
 %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s"""
 
+# Når du fjerner vedh&aelig;ftninger, gemmes de i et arkiv område og der
+# laves istedet links i e-mailen således at medlemmer kan tilgå
+# vedh&aelig;ftninger via en webbrowser. Hvis du vil have
+# vedh&aelig;ftninger til helt og forsvinde så kan du bruge et
+# indholdsfilter.
+#
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
+scrub_nondigest = False
+
 ## Digest options
 #
 # Opsætning af sammendrag-modus.
@@ -489,59 +510,57 @@ digest_size_threshhold = 30
 digest_send_periodic = True
 
 # Tekst som tilf&oslash;jes &oslash;verst i samle-emailen, f&oslash;r
-# indholdsfortegnelsen.Teksten kan inneholde formateringskoder som
-# byttes ut med verdier fra listens oppsett. For detaljer, se Pythons
-# formateringsregler (engelsk). Gyldige koder er:
+# indholdsfortegnelsen.Teksten kan indeholde formateringskoder som
+# udskiftes med v&aelig;rdier fra listens ops&aelig;tning. For detaljer,
+# se Pythons formateringsregler (engelsk). Gyldige koder er:
 # 
 # 
 # real_name - Listens formaterede navn; normalt listenavnet med stort
 # forbogstav eller store bogstaver enkelte steder.
 # 
-# list_name - Listens navn som brugt i URLer, der det har betydning om
+# list_name - Listens navn som brugt i URLer, hvor det har betydning om
 # den staves med store eller sm&aring; bogstaver. (For
 # bagudkompatibilitet, er _internal_name det samme.)
 # 
-# host_name - Internetadressen (fully qulified domain name) til maskinen
-# som listeserveren g&aring;r p&aring;.
+# host_name - Internetadressen (fully qualified domain name) til
+# maskinen som listeserveren k&oslash;rer p&aring;.
 # 
-# web_page_url - Basis URL for Mailman. Denne kan laegges til sammen
-# med, f.eks. listinfo/%(internal_name)s for &aring; danne URLen til en
-# listes infoside.
+# web_page_url - Basis URL for Mailman. Denne kan kombineres med f.eks.
+# listinfo/%(list_name)s for at danne URLen til en listes infoside.
 # 
 # description - En kort beskrivelse af listen.
 # 
-# info - Full beskrivelse af listen.
+# info - Fuld beskrivelse af listen.
 # 
-# cgiext - Tillaeg som laegges til CGI scripts.
+# cgiext - Extension som tilf&oslash;jes CGI scripts.
 # 
 # 
 digest_header = ''
 
 # Tekst der tilføjes nederst i hver samle-email, som sidste
-# information.Teksten kan inneholde formateringskoder som byttes ut med
-# verdier fra listens oppsett. For detaljer, se Pythons
+# information.Teksten kan indeholde formateringskoder som udskiftes med
+# v&aelig;rdier fra listens ops&aelig;tning. For detaljer, se Pythons
 # formateringsregler (engelsk). Gyldige koder er:
 # 
 # 
 # real_name - Listens formaterede navn; normalt listenavnet med stort
 # forbogstav eller store bogstaver enkelte steder.
 # 
-# list_name - Listens navn som brugt i URLer, der det har betydning om
+# list_name - Listens navn som brugt i URLer, hvor det har betydning om
 # den staves med store eller sm&aring; bogstaver. (For
 # bagudkompatibilitet, er _internal_name det samme.)
 # 
-# host_name - Internetadressen (fully qulified domain name) til maskinen
-# som listeserveren g&aring;r p&aring;.
+# host_name - Internetadressen (fully qualified domain name) til
+# maskinen som listeserveren k&oslash;rer p&aring;.
 # 
-# web_page_url - Basis URL for Mailman. Denne kan laegges til sammen
-# med, f.eks. listinfo/%(internal_name)s for &aring; danne URLen til en
-# listes infoside.
+# web_page_url - Basis URL for Mailman. Denne kan kombineres med f.eks.
+# listinfo/%(list_name)s for at danne URLen til en listes infoside.
 # 
 # description - En kort beskrivelse af listen.
 # 
-# info - Full beskrivelse af listen.
+# info - Fuld beskrivelse af listen.
 # 
-# cgiext - Tillaeg som laegges til CGI scripts.
+# cgiext - Extension som tilf&oslash;jes CGI scripts.
 # 
 # 
 digest_footer = """_______________________________________________
@@ -613,7 +632,7 @@ unsubscribe_policy = 0
 # kan ikke tilmelde sig. Indtast e-mailadresser, en pr. linie, start
 # linien med tegnet ^ for at angive et regexp-udtryk der skal stemme
 # overens med afsenderadressen.
-ban_list = ['nitaigouranga@aol.com']
+ban_list = ['nitaigouranga@aol.com', 'lottoaward16@msn.com', 'wendysmith06@sympatico.ca', 'shaooogroups@sympatico.ca']
 
 # Hvis denne indstilling ikke er sat til 'Alle', vil medlemslisten blive
 # beskyttet af medlemmernes eller administrators adgangskode.
@@ -739,7 +758,7 @@ reject_these_nonmembers = []
 # e-mail. Tilf&oslash;j e-mailadresser, en pr. linie, start linien med
 # tegnet ^ for at angive et regexp-udtryk der skal stemme overens med
 # afsenderadressen.
-discard_these_nonmembers = ['nitaigouranga@aol.com']
+discard_these_nonmembers = ['nitaigouranga@aol.com', 'lottoaward16@msn.com', 'wendysmith06@sympatico.ca', 'shaooogroups@sympatico.ca']
 
 # N&aring;r en e-mail fra et ikke-medlem bliver modtaget, sammenlignes
 # e-mailens afsender med listen over e-mailadresser der skal godkendes,
@@ -764,6 +783,12 @@ generic_nonmember_action = 1
 #    1 = "Ja"
 forward_auto_discards = True
 
+# Tekst der skal inkluderes i en meddelelse om afvisning der sendes til
+# ikke-medlemmer der poster til listen. Denne meddelelse kan inkludere
+# listeejerens adresse vha. %(listowner)s og den erstatter den
+# automatisk konstruerede standard meddelelse.
+nonmember_rejection_notice = ''
+
 ## Privacy options
 #
 # Her kan du ops&aelig;tte filtrering baseret på modtageren af
@@ -821,15 +846,22 @@ max_num_recipients = 10
 # Her kan du opsætte forskellige anti-spam filtre, som kan bidrage til
 # at reducere mængden af spam der distribueres via e-maillisten.
 
-# Each header filter rule has two parts, a list of regular expressions,
-# one per line, and an action to take.  Mailman matches the message's
-# headers against every regular expression in the rule and if any match,
-# the message is rejected, held, or discarded based on the action you
-# specify.  Use Defer to temporarily disable a rule.
-# 
-# You can have more than one filter rule for your list.  In that case,
-# each rule is matched in turn, with processing stopped after the first
-# match.
+# Hver filterregel best&aring;r af to dele: en liste med regexp-udtryk,
+# et pr. linie, og en aktion der skal udf&oslash;res. Mailman
+# sammenligner meddelelsens brevhoved med alle regexp-udtryk i reglen,
+# og hvis der er overensstemmelse, vil meddelelsen blive afvist,
+# tilbageholdt eller slettet, afh&aelig;ngigt af hvilken aktion du har
+# angivet her. Brug Afvent for midlertidigt at s&aelig;tte en regel ud
+# af kraft.
+# 
+# Du kan have flere end en regel for din liste.  I s&aring; fald vil
+# hver regel blive anvendt efter tur, og processen stopper f&oslash;rste
+# gang der findes overensstemmelse.
+# 
+# Bemærk at brevhovedlinier indsamles fra alle vedh&aelig;ftninger
+# (undtagen fra mailman administrivia meddelelser) og sammenlignes med
+# regexp-udtrykkene. Ved brug af denne funktionalitet kan du effektivt
+# sortere meddelelser fra med farlige filtyper eller filnavn-endelser.
 header_filter_rules = []
 
 # Brug denne indstilling til at bortfiltrere mail til listen, baseret
@@ -1136,32 +1168,34 @@ autoresponse_graceperiod = 90
 
 ## Contentfilter options
 #
-# Regler for indhold i e-mail sendt til listen.
-# 
-# <p>Filtrering af indhold fungerer således: når listen modtager en
-# e-mail og du har beskyttelse med filtrering af indhold aktiveret,
-# sammenlignes først eventuelle vedh&aelig;ftninger med <a
-# href="?VARHELP=contentfilter/filter_mime_types">MIME filtrene</a>.
-# Hvis en vedh&aelig;ftning passer med et af disse filtre, bliver
-# vedh&aelig;ftningen fjernet.
-# 
-# <p>Derefter sammenlignes eventuelle vedh&aelig;ftninger med <a
-# href="?VARHELP=contentfilter/pass_mime_types">gyldige MIME typer</a>,
-# hvis nogen er defineret. Alle vedh&aelig;ftninger som ikke stemmer
-# overens med de angivne MIME typer, bliver fjernet.
-# 
-# <p>Efter filtreringen vil alle tomme <tt>multipart</tt>
-# vedh&aelig;ftninger v&aelig;re fjernet. Hvis selve meddelelsen er helt
-# tom efter denne filtrering, vil meddelelsen blive afvist. Derefter vil
-# enhver <tt>multipart/alternative</tt> vedh&aelig;ftning blive
-# erstattet af den første alternative som ikke er tom.
-# 
-# <p>Til sidst vil alle <tt>text/html</tt> vedh&aelig;ftninger som måtte
-# v&aelig;re tilbage i meddelelsen blive konverteret til
-# <tt>text/plain</tt> hvis <a
-# href="?VARHELP=contentfilter/convert_html_to_plaintext">konverter til
-# ren tekst</a> er sat til og serveren er konfigureret til at tillade
-# sådanne konverteringer.
+# Policies concerning the content of list traffic.
+# 
+# <p>Content filtering works like this: when a message is received by
+# the list and you have enabled content filtering, the individual
+# attachments are first compared to the <a
+# href="?VARHELP=contentfilter/filter_mime_types">filter types</a>.  If
+# the attachment type matches an entry in the filter types, it is
+# discarded.
+# 
+# <p>Then, if there are <a
+# href="?VARHELP=contentfilter/pass_mime_types">pass types</a> defined,
+# any attachment type that does <em>not</em> match a pass type is also
+# discarded.  If there are no pass types defined, this check is skipped.
+# 
+# <p>After this initial filtering, any <tt>multipart</tt> attachments
+# that are empty are removed.  If the outer message is left empty after
+# this filtering, then the whole message is discarded.
+# 
+# <p> Then, each <tt>multipart/alternative</tt> section will be replaced
+# by just the first alternative that is non-empty after filtering if <a
+# href="?VARHELP=contentfilter/collapse_alternatives"
+# >collapse_alternatives</a> is enabled.
+# 
+# <p>Finally, any <tt>text/html</tt> parts that are left in the message
+# may be converted to <tt>text/plain</tt> if <a
+# href="?VARHELP=contentfilter/convert_html_to_plaintext"
+# >convert_html_to_plaintext</a> is enabled and the site is configured
+# to allow these conversions.
 
 # Skal Mailman filtrere indhold i e-mail sendt til listen som angivet
 # nedenfor?
@@ -1191,6 +1225,28 @@ pass_mime_types = """multipart/mixed
 multipart/alternative
 text/plain"""
 
+# Fjern e-mailvedh&aelig;ftninger med passende filnavn-endelser.
+filter_filename_extensions = """exe
+bat
+cmd
+com
+pif
+scr
+vbs
+cpl"""
+
+# Fjern alle vedh&aelig;ftninger der ikke har en passende
+# filnavn-endelse. Lad dette felt være tomt for at udelade dette filter.
+pass_filename_extensions = ''
+
+# Should Mailman collapse multipart/alternative to its first part
+# content?
+#
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
+collapse_alternatives = True
+
 # Skal Mailman konvertere text/html dele til ren tekst? Denne
 # konvertering vil finde sted efter at MIME filteret har fjernet de
 # uønskede dele.
diff --git a/mailman/users.members b/mailman/users.members
index 3f25c58..6f4ce19 100644
--- a/mailman/users.members
+++ b/mailman/users.members
@@ -7,87 +7,42 @@ alsinger@jones.dk
 anders@jones.dk
 anderskr@jones.dk
 ane@jones.dk
-ann@jones.dk
-anne@jones.dk
-anwar@jones.dk
 ascanius@jones.dk
 assenbjerg@jones.dk
-awh@jones.dk
 banana@jones.dk
-benny@jones.dk
-betina@jones.dk
 bettina@jones.dk
-binx@jones.dk
-birgitte@jones.dk
 bolette@jones.dk
 borking@jones.dk
-bsi@jones.dk
-cfo@jones.dk
 chr.h@pobox.com
 chrois@jones.dk
-claude@jones.dk
-cm@jones.dk
 concept@jones.dk
-dewd@jones.dk
-dive@jones.dk
-dolmer@jones.dk
-dorte@jones.dk
-dr@jones.dk
 dreijer@jones.dk
 elizabeth@jones.dk
-emil@jones.dk
 emilie@jones.dk
-emma@jones.dk
 esben@jones.dk
-eva@jones.dk
-evamaria@jones.dk
-exit@jones.dk
-filurlig@jones.dk
-fire@jones.dk
-flip@jones.dk
 foto@jones.dk
-frank@jones.dk
-frederik@jones.dk
-fsl@jones.dk
 gio@jones.dk
-gitte@jones.dk
 global@jones.dk
-go@jones.dk
 grit@jones.dk
-grohmann@jones.dk
-hanne@jones.dk
 harry@jones.dk
-helbak@jones.dk
 helene@jones.dk
-henrik@jones.dk
-hh@jones.dk
 hilde@jones.dk
-hilleroed@jones.dk
 hsv@jones.dk
-hvam@jones.dk
-id@jones.dk
-ida@jones.dk
-idaadm@jones.dk
 inarosing@jones.dk
 ingersme@jones.dk
 inuk@jones.dk
-izi@jones.dk
+jais@jones.dk
 janus@netcetera.dk
-jason@jones.dk
 jasper@jones.dk
-jens@jones.dk
-jesper@jones.dk
-jfe@jones.dk
 jgh@jones.dk
-jnj@jones.dk
 jo@jones.dk
 joachim@jones.dk
 jones@jones.dk
 jorgen@jones.dk
-joy@jones.dk
 juri@jones.dk
 kamilla@jones.dk
 karina@jones.dk
+karineggert@jones.dk
 karl@jones.dk
 kathrine@jones.dk
 katja@jones.dk
@@ -116,7 +71,6 @@ line@jones.dk
 lisa@jones.dk
 lise@jones.dk
 liseharlev@jones.dk
-lone@jones.dk
 lucifer@jones.dk
 maki@jones.dk
 malene@jones.dk
@@ -139,12 +93,9 @@ mogens@jones.dk
 morgan@jones.dk
 morten@jones.dk
 mp@jones.dk
-mr@jones.dk
 nancy@jones.dk
 negon@jones.dk
-nicolai@jones.dk
 niels@jones.dk
-nils@jones.dk
 nina@jones.dk
 nors@jones.dk
 nrl@jones.dk
@@ -167,7 +118,6 @@ reumert@jones.dk
 riccos@jones.dk
 rinchin@jones.dk
 ronald@jones.dk
-ror@jones.dk
 rornaestved@jones.dk
 rosen@jones.dk
 ruggero@jones.dk
@@ -176,7 +126,6 @@ sabine@jones.dk
 sacha@jones.dk
 samuel@jones.dk
 sanna@jones.dk
-saturn@jones.dk
 sebwijk@jones.dk
 sfr@jones.dk
 sg@jones.dk
@@ -185,15 +134,12 @@ siri@jones.dk
 sita@jones.dk
 sj@jones.dk
 skkh@jones.dk
-sm@jones.dk
-soren@jones.dk
 stef@jones.dk
 steinbach@jones.dk
 sthorsson@jones.dk
 stine@jones.dk
 stinemarie@jones.dk
 stinus@jones.dk
-stuff@jones.dk
 synne@jones.dk
 thdreijer@jones.dk
 thomas@jones.dk
diff --git a/mailman/users.py b/mailman/users.py
index 22cd5d6..f112ae4 100644
--- a/mailman/users.py
+++ b/mailman/users.py
@@ -1,73 +1,69 @@
-## Indstillinger for maillisten "users"  -*- python -*-
-## Dato: Sun Dec 11 16:36:11 2005
+# -*- python -*-
+# -*- coding: us-ascii -*-
+## "users" mailing list configuration settings
+## captured on Tue Mar 20 08:52:44 2007
 
 ## General options
 #
-# Grundlæggende egenskaber for listen, herunder en beskrivelse af
-# listen. 
-
-# Du kan f.eks. stave navnet med stort forbogstav eller ændre andre
-# bogstaver til store, s&aring; navnet bliver udtalt rigtigt eller at
-# forkortelser fremhæves. Bemærk at dette navn bruges i e-maillistens
-# adresse (f.eks. i bekræftelser ved tilmeldinger), s&aring; navnet kan
-# ikke ændres p&aring; nogen anden m&aring;de. (e-mailadresser er ikke
-# f&oslash;lsomme for store eller sm&aring; bogstaver, men de er
-# f&oslash;lsomme for n&aelig;sten alt andet :-)
+# Fundamental list characteristics, including descriptive info and basic
+# behaviors.
+
+# The capitalization of this name can be changed to make it presentable
+# in polite company as a proper noun, or to make an acronym part all
+# upper case, etc.  However, the name will be advertised as the email
+# address (e.g., in subscribe confirmation notices), so it should not be
+# otherwise altered.  (Email addresses are not case sensitive, but they
+# are sensitive to almost everything else :-)
 real_name = 'Users'
 
-# Der er to roller forbundet med hver mailliste. Listeadministratorerne
-# er dem der som sidste instans har kontrol over alle indstillingerne
-# for maillisten. De kan &aelig;ndre alle indstillinger der er
-# tilg&aelig;ngelige via disse administrative websider.
-# 
-# Listemoderatorerne har begrænset adgang; de kan ikke ændre
-# indstillinger for e-maillisten, men de kan tage sig af anmodninger i
-# forbindelse med listen, f.eks. anmodning om medlemskab, eller
-# godkende/afvise meddelelser der skal godkendes for at kunne udsendes
-# til listen. Listeadministratorerne kan ogs&aring; udf&oslash;re disse
-# opgaver.
-# 
-# For at aktivere muligheden for at have listemoderatorer, og p&aring;
-# den m&aring;de fordele arbejdsopgaverne i forbindelse med listen, skal
-# du anf&oslash;re din egen moderatoradgangskode, og angive
-# e-mailadresser for den/dem som skal v&aelig;re listemoderator(er).
-# Bemærk at i tekstboksene nedenfor skal du skrive e-mailadresser for
-# listeadministratorer.
+# There are two ownership roles associated with each mailing list.  The
+# list administrators are the people who have ultimate control over all
+# parameters of this mailing list.  They are able to change any list
+# configuration variable available through these administration web
+# pages.
+# 
+# The list moderators have more limited permissions; they are not able
+# to change any list configuration variable, but they are allowed to
+# tend to pending administration requests, including approving or
+# rejecting held subscription requests, and disposing of held postings.
+# Of course, the list administrators can also tend to pending requests.
+# 
+# In order to split the list ownership duties into administrators and
+# moderators, you must set a separate moderator password, and also
+# provide the email addresses of the list moderators.  Note that the
+# field you are changing here specifies the list administrators.
 owner = ['dr.jones@pobox.com']
 
-# Der er to ejer-roller forbundet med hver mailliste.
-# Listeadministratorerne er dem der har den endelige kontrol over alle
-# indstillingerne for e-mallisten. De kan &aelig;ndre alle indstillinger
-# der er tilgængelige via disse administrative websider.
-# 
-# Listemoderatorerne har begr&aelig;nset adgang; de kan ikke &aelig;ndre
-# indstillinger for e-maillisten, men de kan tage sig af anmodninger
-# ang&aring;ende listen, f.eks. anmodning om medlemskab, eller
-# godkende/afvise meddelelser der skal godkendes for at kunne udsendes
-# p&aring; listen. Listeadministratorerne kan selvsagt ogs&aring;
-# udf&oslash;re disse opgaver.
-# 
-# For at aktivere muligheden for at have listemoderatorer, og p&aring;
-# den m&aring;de fordele arbejdsopgaverne i forbindelse med listen, skal
-# du anf&oslash;re din egen moderatoradgangskode, og indtaste
-# e-mailadresser for den/dem der skal v&aelig;re listemoderatore(r).
-# Bemærk, at i tekstboksene nedenfor skal du skrive listemoderator
-# e-mailadresse(r).
+# There are two ownership roles associated with each mailing list.  The
+# list administrators are the people who have ultimate control over all
+# parameters of this mailing list.  They are able to change any list
+# configuration variable available through these administration web
+# pages.
+# 
+# The list moderators have more limited permissions; they are not able
+# to change any list configuration variable, but they are allowed to
+# tend to pending administration requests, including approving or
+# rejecting held subscription requests, and disposing of held postings.
+# Of course, the list administrators can also tend to pending requests.
+# 
+# In order to split the list ownership duties into administrators and
+# moderators, you must set a separate moderator password, and also
+# provide the email addresses of the list moderators in this section.
+# Note that the field you are changing here specifies the list
+# moderators.
 moderator = []
 
-# Denne beskrivelse benyttes n&aring;r denne malliste listes op sammen
-# med andre maillister, i toptekster, osv. Den b&oslash;r v&aelig;re
-# s&aring; kort som overhovedet mulig, uden at det bliver uklart hvad
-# meningen med maillisten er eller hvad den skal bruges til.
+# This description is used when the mailing list is listed with other
+# mailing lists, or in headers, and so forth.  It should be as succinct
+# as you can get it, while still identifying what the list is.
 description = 'Announcements to users at jones.dk'
 
-# Teksten tolkes som html bortset fra linieskift, der vil blive
-# &aelig;ndret til html-tag'et '<br>', sådan at du kan benytte links,
-# forh&aring;ndsformateret tekst, osv. Men brug alts&aring; kun
-# linieskift der hvor du vil have et nyt afsnit. V&aelig;r meget
-# omhyggelig, hvis du benytter html-kode. Fejl (f.eks. manglende
-# slut-tag's) kan f&oslash;re til at listens informationsside ikke
-# bliver vist s&aring;dan som den skal.
+# The text will be treated as html except that newlines will be
+# translated to <br> - so you can use links, preformatted text, etc, but
+# don't put in carriage returns except where you mean to separate
+# paragraphs.  And review your changes - bad html (like some
+# unterminated HTML constructs) can prevent display of the entire
+# listinfo page.
 info = """This is a mailing list reaching all people with an E-mail account at jones.dk.
 I might have some tip or a warning regarding the system.
 
@@ -75,131 +71,132 @@ Kind regards,
 Jonas Smedegaard"""
 
 # This text will be prepended to subject lines of messages posted to the
-# list, to distinguish mailing list messages in in mailbox summaries.
+# list, to distinguish mailing list messages in mailbox summaries.
 # Brevity is premium here, it's ok to shorten long mailing list names to
 # something more concise, as long as it still identifies the mailing
-# list.
+# list. You can also add a sequential number by %d substitution
+# directive. eg.; [listname %d] -> [listname 123] (listname %05d) ->
+# (listname 00123)
+# 
 subject_prefix = '[Users] '
 
-# Skjul afsenderen af meddelelser, ved at erstatte den med e-maillistens
-# adresse (Dette medfører at alle From:, Sender, og Reply-To: felter
-# fjernes)
+# Hide the sender of a message, replacing it with the list address
+# (Removes From, Sender and Reply-To fields)
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 anonymous_list = 0
 
-# Skal eksisterende Reply-To: felt i brevhovedet fjernes? Hvis ja, vil
-# dette blive gjort uanset om Mailman tilføjer et Reply-To: felt eller
-# ikke.
+# Should any existing Reply-To: header found in the original message be
+# stripped?  If so, this will be done regardless of whether an explict
+# Reply-To: header is added by Mailman or not.
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 first_strip_reply_to = 0
 
-# Denne indstillling fort&aelig;ller hvad Mailman skal g&oslash;re med
-# Reply-To: feltet i brevhovedet p&aring; e-mail der sendes til listen.
-# Hvis den er sat til Afsender, vil Mailman ikke tilf&oslash;je noget
-# Reply-To: felt, men findes et s&aring;dant felt allerede, vil det ikke
-# blive fjernet. S&aelig;ttes indstillingen til enten e-maillistens
-# adresse eller Egendefineret adresse, vil Mailman tilf&oslash;je, evt.
-# erstatte, et Reply-To: felt. (Egendefineret adresse inds&aelig;tter
-# v&aelig;rdien af indstillingen reply_to_address).
-# 
-# Der er flere grunde til ikke at indf&oslash;re eller erstatte
-# Reply-To: felter. En grund kan v&aelig;re at nogen af dem der sender
-# mail til listen er afh&aelig;ngige af selv at kunne s&aelig;tte
-# Reply-To: adressen. En anden grund er at modifikation af Reply-To:
-# adressen g&oslash;r det vanskeligere kun at sende svar til afsender.
-# Se 'Reply-To' Munging Considered Harmful for en diskussion omkring
-# emnet. Se Reply-To Munging Considered Useful for modsatte meninger.
-# 
-# Nogle maillister har begr&aelig;nset adgang, med en parallel liste
-# beregnet til diskussioner. Eksempler p&aring; dette er 'patches' eller
-# 'checkin' lister, som system for revisionskontrol sender
-# &aelig;ndringer i programmet til, men diskussioner omkring udvikling
-# af programmet sendes til udviklernes egen mailliste. For at
-# underst&oslash;tte lignende e-maillister, v&aelig;lg Egendefineret
-# adresse og s&aelig;t Reply-To: adressen i indstillingen
-# reply_to_address til at pege på den parallelle diskussionsliste.
-#
-# gyldige værdier:
-#    0 = "Afsender"
-#    1 = "mail listens adresse"
-#    2 = "Egendefineret adresse"
+# This option controls what Mailman does to the Reply-To: header in
+# messages flowing through this mailing list.  When set to Poster, no
+# Reply-To: header is added by Mailman, although if one is present in
+# the original message, it is not stripped.  Setting this value to
+# either This list or Explicit address causes Mailman to insert a
+# specific Reply-To: header in all messages, overriding the header in
+# the original message if necessary (Explicit address inserts the value
+# of <a href="?VARHELP=general/reply_to_address">reply_to_address).
+# 
+# There are many reasons not to introduce or override the Reply-To:
+# header.  One is that some posters depend on their own Reply-To:
+# settings to convey their valid return address.  Another is that
+# modifying Reply-To: makes it much more difficult to send private
+# replies.  See <a
+# href="http://www.unicom.com/pw/reply-to-harmful.html">`Reply-To'
+# Munging Considered Harmful for a general discussion of this issue.
+# See <a
+# href="http://www.metasystema.net/essays/reply-to.mhtml">Reply-To
+# Munging Considered Useful for a dissenting opinion.
+# 
+# Some mailing lists have restricted posting privileges, with a parallel
+# list devoted to discussions.  Examples are `patches' or `checkin'
+# lists, where software changes are posted by a revision control system,
+# but discussion about the changes occurs on a developers mailing list.
+# To support these types of mailing lists, select Explicit address and
+# set the Reply-To: address below to point to the parallel list.
+#
+# legal values are:
+#    0 = "Poster"
+#    1 = "This list"
+#    2 = "Explicit address"
 reply_goes_to_list = 0
 
-# Her definerer du adressen der skal s&aelig;ttes i Reply-To: feltet
-# n&aring;r indstillingen reply_goes_to_list er sat til Egendefineret
-# adresse.
-# 
-# Der findes mange grunde til at ikke indf&oslash;re eller erstatte
-# Reply-To: felter. En grund kan v&aelig;re at nogen af dem der sender
-# e-mail til listen er afh&aelig;ngige af selv at kunne s&aelig;tte
-# Reply-To: adressen. En anden grund er at modificering af Reply-To:
-# adressen g&oslash;r det vanskeligere at sende svar kun til afsender.
-# Se 'Reply-To' Munging Considered Harmful for en diskussion omkring
-# temaet. Se Reply-To Munging Considered Useful for modsatte meninger.
-# 
-# Nogle maillister har begr&aelig;nset adgang, med en egen parallel
-# liste beregnet for diskussioner. Eksempler p&aring; dette er 'patches'
-# eller 'checkin' lister, som system for revisionskontrol sender
-# &aelig;ndringer i programmet til, mens diskussioner omkring udvikling
-# af programmet sendes til udviklernes egen mailliste. For at
-# underst&oslash;tte s&aring;danne maillister, kan du definere Reply-To:
-# adressen her, og vælge Egendefineret adresse i indstillingen
-# reply_goes_to_list.
-# 
-# Bem&aelig;rk at hvis den oprindelige meddelelse indeholder et
-# Reply-To: felt, vil det ikke &aelig;ndres.
+# This is the address set in the Reply-To: header when the <a
+# href="?VARHELP=general/reply_goes_to_list">reply_goes_to_list option
+# is set to Explicit address.
+# 
+# There are many reasons not to introduce or override the Reply-To:
+# header.  One is that some posters depend on their own Reply-To:
+# settings to convey their valid return address.  Another is that
+# modifying Reply-To: makes it much more difficult to send private
+# replies.  See <a
+# href="http://www.unicom.com/pw/reply-to-harmful.html">`Reply-To'
+# Munging Considered Harmful for a general discussion of this issue.
+# See <a
+# href="http://www.metasystema.net/essays/reply-to.mhtml">Reply-To
+# Munging Considered Useful for a dissenting opinion.
+# 
+# Some mailing lists have restricted posting privileges, with a parallel
+# list devoted to discussions.  Examples are `patches' or `checkin'
+# lists, where software changes are posted by a revision control system,
+# but discussion about the changes occurs on a developers mailing list.
+# To support these types of mailing lists, specify the explicit
+# Reply-To: address here.  You must also specify Explicit address in the
+# reply_goes_to_list variable.
+# 
+# Note that if the original message contains a Reply-To: header, it will
+# not be changed.
 reply_to_address = ''
 
-# V&aelig;lg kun 'ja' her, hvis listen skal bruges som  "paraply" for
-# andre lister. Hvis 'ja' er valgt, vil bekr&aelig;ftelser og
-# meddelelser med adgangskode blive sendt til en adresse som konstrueres
-# ud fra medlemmets e-mailadresse - v&aelig;rdien af indstillingen
-# "umbrella_member_suffix" tilf&oslash;jes medlemmets kontonavn (det som
-# st&aring;r f&oslash;r @-tegnet).
+# Set this to yes when this list is intended to cascade only to other
+# mailing lists.  When set, meta notices like confirmations and password
+# reminders will be directed to an address derived from the member's
+# address - it will have the value of "umbrella_member_suffix" appended
+# to the member's account name.
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 umbrella_list = 0
 
-# N&aring;r "umbrella_list" indikerer at denne liste har andre
-# maillister som medlemmer, skal administrative meddelelser som f.eks.
-# bekr&aelig;ftelser og p&aring;mindelser om adgangskode ikke sendes til
-# selve listen, men snarere til administrator for listen. V&aelig;rdien
-# af denne indstilling bestemmer, hvilken adresse administrative
-# meddelelser skal sendes til. '-owner' er et almindeligt valg for denne
-# indstilling. Denne indstilling har ingen effekt n&aring;r
-# "umbrella_list" er sat til "Nej".
+# When "umbrella_list" is set to indicate that this list has other
+# mailing lists as members, then administrative notices like
+# confirmations and password reminders need to not be sent to the member
+# list addresses, but rather to the owner of those member lists.  In
+# that case, the value of this setting is appended to the member's
+# account name for such notices.  `-owner' is the typical choice.  This
+# setting has no effect when "umbrella_list" is "No".
 umbrella_member_suffix = '-owner'
 
-# Aktiver denne, hvis der skal sendes en p&aring;mindelse om adgangskode
-# til medlemmerne en gang hver m&aring;ned. Husk at medlemmerne
-# ogs&aring; selv kan frav&aelig;lge dette.
+# Turn this on if you want password reminders to be sent once per month
+# to your members.  Note that members may disable their own individual
+# password reminders.
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 send_reminders = 0
 
-# Tekst du skriver her vil blive tilf&oslash;jet &oslash;verst i
-# velkomsthilsenen der sendes til nye medlemmer. Velkomshilsenen
-# indeholder i forvejen vigtige adresser og URLer knyttet til
-# maillisten, s&aring; den slags information er det ikke
-# n&oslash;dvendigt at inkludere her. Her kan du tilf&oslash;je f.eks.
-# oplysning om etikette eller regler for brug af listen, o.l.
-# 
-# Bem&aelig;rk: Linierne i denne tekst vil brydes efter f&oslash;lgende
-# regler:
+# This value, if any, will be added to the front of the new-subscriber
+# welcome message.  The rest of the welcome message already describes
+# the important addresses and URLs for the mailing list, so you don't
+# need to include any of that kind of stuff here.  This should just
+# contain mission-specific kinds of things, like etiquette policies or
+# team orientation, or that kind of thing.
 # 
-# Hvert afsnit udfyldes s&aringdan at ingen linie er l&aelig;ngere en 70
-# tegn. Enhver linie der begynder med tomme tegn udfyldes ikke. Tomme
-# linier adskiller afsnit.
+# Note that this text will be wrapped, according to the following rules:
+# Each paragraph is filled so that no line is longer than 70 characters.
+# Any line that begins with whitespace is not filled. A blank line
+# separates paragraphs.
 # 
 welcome_msg = """This is a mailing list for people with an E-mail account at jones.dk
 
@@ -214,185 +211,175 @@ Kind regards,
 
 Jonas Smedegaard"""
 
-# S&aelig;t kun denne til 'Nej' hvis du skal tilf&oslash;je nye
-# medlemmer manuelt, og ikke vil have at de f&aring;r det at vide. Dette
-# er meget nyttigt n&aring;r man g&aring;r fra et andet mallistesystem
-# og til Mailman, og vil have at overgangen skal v&aelig;re s&aring;
-# lidt m&aelig;rkbar som muligt.
+# Turn this off only if you plan on subscribing people manually and
+# don't want them to know that you did so.  This option is most useful
+# for transparently migrating lists from some other mailing list manager
+# to Mailman.
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 send_welcome_msg = 1
 
-# Tekst der sendes til medlemmer der framelder sig listen. Hvis feltet
-# er tomt, tilf&oslash;jes der ikke nogen speciel tekst til
-# frameldingen.
+# Text sent to people leaving the list.  If empty, no special text will
+# be added to the unsubscribe message.
 goodbye_msg = """Hmmm
 Are you sure that was a very smart move?"""
 
-# Send afskedshilsen til medlemmer n&aring;r de frameldes?
+# Send goodbye message to members when they are unsubscribed?
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 send_goodbye_msg = 1
 
-# Der udsendes en p&aring;mindelse til listemoderator (og
-# listeadministrator) dagligt om anmodninger der af en eller anden grund
-# venter p&aring; behandling. V&aelig;lger du "Ja", vil
-# listeadminstrator ogs&aring; modtage en meddelelse s&aring; snart en
-# anmodning ankommer.
+# List moderators (and list administrators) are sent daily reminders of
+# requests pending approval, like subscriptions to a moderated list, or
+# postings that are being held for one reason or another.  Setting this
+# option causes notices to be sent immediately on the arrival of new
+# requests as well.
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 admin_immed_notify = 1
 
-# Skal listeadministrator modtage meddelelse om tilmeldinger og
-# afmeldinger?
+# Should administrator get notices of subscribes and unsubscribes?
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 admin_notify_mchanges = 0
 
-# Approval notices are sent when mail triggers certain of the limits
-# except routine list moderation and spam filters, for which notices are
-# not sent.  This option overrides ever sending the notice.
+# Send mail to poster when their posting is held for approval?
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 respond_to_post_requests = 1
 
-# Når dette valg er aktiveret, vil al e-mail til listen blive modereret.
-# Dette valg kan være nyttigt når din mailliste f.eks. har en såkaldt
-# "flamewar", altså en "krig" hvor medlemmer kun skælder ud på hinanden.
-# En "nød-moderering" kan da hjælpe dig at fjerne usaglige meddelelser
-# til listen, og på den måde dysse en ophedet diskussion ned.
+# When this option is enabled, all list traffic is emergency moderated,
+# i.e. held for moderation.  Turn this option on when your list is
+# experiencing a flamewar and you want a cooling off period.
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 emergency = 0
 
-# Når et nyt medlem tilmeldes listen, bliver medlemmets indstillinger
-# taget herfra.
+# When a new member is subscribed to this list, their initial set of
+# options is taken from the this variable's setting.
 new_member_options = 256
 
-# Filter for administrative meddelelser vil unders&oslash;ge om
-# meddelelsen egentligt er ment som en administrativ anmodning (f.eks.
-# tilmelding, framelding, o.l.), og i s&aring; fald sende meddelelsen
-# til listeadministrator i stedet for.
+# Administrivia tests will check postings to see whether it's really
+# meant as an administrative request (like subscribe, unsubscribe, etc),
+# and will add it to the the administrative requests queue, notifying
+# the administrator of the new request, in the process.
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 administrivia = 1
 
-# Maximum st&oslash;rrelse i kilobytes (KB) for indholdet i e-mail der
-# sendes til listen. Brug v&aelig;rdien '0' for ikke at have nogen
-# begr&aelig;nsning.
+# Maximum length in kilobytes (KB) of a message body.  Use 0 for no
+# limit.
 max_message_size = 40
 
-# "Maskinnavnet" er det navn som skal benyttes for e-mailadresser
-# relateret til Mailman p&aring; denne maskine, og er normalt navnet der
-# er forbundet med e-mail-servicen p&aring; maskinen. Denne indstilling
-# kan v&aelig;re nyttig hvis maskinen har flere navne.
+# The "host_name" is the preferred name for email to mailman-related
+# addresses on this host, and generally should be the mail host's
+# exchanger address, if any.  This setting can be useful for selecting
+# among alternative names of a host that has multiple addresses.
 host_name = 'jones.dk'
 
-# I RFC 2369 defineres en r&aelig;kke List-* felter i brevhovedet, der
-# normalt tilf&oslash;jes enhver meddelelse der sendes ud via listen.
-# Disse felter er til stor gavn for brugere , som benytter et
-# e-mailprogram der f&oslash;lger standarden. Disse felter b&oslash;r
-# derfor altid v&aelig;re med.
-# 
-# Ikke alle e-mailprogrammer f&oslash;lger denne standard. Hvis der er
-# mange medlemmer p&aring; listen, der benytter e-mailprogrammer, der
-# ikke kan h&aring;ndtere disse felter i brevhovedet, kan du v&aelig;lge
-# at udelade dem. Men du b&oslash;r f&oslash;rst fors&oslash;ge at
-# l&aelig;re og forklare medlemmerne hvad hensigten med s&aring;danne
-# felter er, og hvordan de kan skjule dem i deres e-mailprogram. Som en
-# sidste udvej kan du udelade felterne, men det anbefales ikke (og denne
-# mulighed kan faktisk ogs&aring; blive fjernet i senere versioner af
-# Mailman).
-#
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# RFC 2369 defines a set of List-* headers that are normally added to
+# every message sent to the list membership. These greatly aid end-users
+# who are using standards compliant mail readers.  They should normally
+# always be enabled.
+# 
+# However, not all mail readers are standards compliant yet, and if you
+# have a large number of members who are using non-compliant mail
+# readers, they may be annoyed at these headers.  You should first try
+# to educate your members as to why these headers exist, and how to hide
+# them in their mail clients.  As a last resort you can disable these
+# headers, but this is not recommended (and in fact, your ability to
+# disable these headers may eventually go away).
+#
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 include_rfc2369_headers = 1
 
-# List-Post: feltet er et af felterne anbefalet i RFC 2369. P&aring;
-# nogle e-maillister (som f.eks. kun bruges til
-# offentligg&oslash;relser), er det kun bestemte personer der har lov
-# til at poste til listen. Almindelige medlemmer af listen har normalt
-# ikke lov til at poste til listen. For den slags lister, er List-Post:
-# feltet misvisende. S&aelig;t denne indstilling til Nej, for at
-# undg&aring; at feltet tilf&oslash;jes. (Dette p&aring;virker ikke
-# andre List-*: felter.)
-#
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# The List-Post: header is one of the headers recommended by RFC 2369.
+# However for some announce-only mailing lists, only a very select group
+# of people are allowed to post to the list; the general membership is
+# usually not allowed to post.  For lists of this nature, the List-Post:
+# header is misleading. Select No to disable the inclusion of this
+# header. (This does not affect the inclusion of the other List-*:
+# headers.)
+#
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 include_list_post_header = 1
 
+# Discard held messages older than this number of days. Use 0 for no
+# automatic discarding.
+max_days_to_hold = 0
+
 ## Language options
 #
-# Underst&oslash;ttelse af flere sprog. (Internationalisering)
-
-# Dette er standardsproget som benyttes for denne mailliste. Hvis flere
-# end et sprog/ underst&oslash;ttes, vil medlemmer af listen selv kunne
-# v&aelig;lge hvilket sprog der skal benyttes n&aring;r de g&aring;r ind
-# p&aring; deres personlige webside, og n&aring;r meddelelser fra
-# systemet sendes til dem. Hvis medlemmerne ikke &aelig;ndrer noget
-# selv, vil dette standardsprog blive benyttet. Dette g&aelig;lder
-# b&aring;de web-baserede og e-mail-baserede meddelelser, men ikke
-# meddelelser sendt af listens medlemmer.
+# Natural language (internationalization) options.
+
+# This is the default natural language for this mailing list. If more
+# than one language is supported then users will be able to select their
+# own preferences for when they interact with the list.  All other
+# interactions will be conducted in the default language.  This applies
+# to both web-based and email-based messages, but not to email posted by
+# list members.
 preferred_language = 'en'
 
-# Her er alle sprog, som denne liste har underst&oslash;ttelse for.
-# Bem&aelig;rk at standardsproget skal v&aelig;re med.
+# These are all the natural languages supported by this list. Note that
+# the default language must be included.
 available_languages = ['da', 'de', 'en', 'no', 'sv']
 
-# Hvis standardsproget for din mailliste benytter et andet tegns&aelig;t
-# end ASCII og Emne prefixet for listen indeholder tegn som ikke findes
-# i ASCII-tegns&aelig;ttet, vil prefixet altid blive kodet i henhold til
-# den relevante standard. Hvis Emne prefixet kun indeholder ASCII tegn,
-# ønsker du måske at vælge Aldrig for at undgå kodning. Dette kan gøre
-# emnet lidt mere læseligt for brugere med e-mailprogrammer der ikke kan
-# håndtere andre tegnsæt end ASCII.
-# 
-# Bemærk imidlertid, at hvis din mailliste modtager både kodede og
-# ukodede emnefelter , kan det være bedst at vælge Efter behov. Med
-# denne indstilling vil Mailman ikke kode ASCII prefixer hvis resten af
-# titelfeltet kun indeholder ASCII tegn, men vil kode prefixet hvis det
-# indeholder tegn som ikke er ASCII tegn. På denne måde undgås en
-# tvetydighed i standarderne, som forårsager at visse e-mailprogrammer
-# vil vise ekstra eller manglende mellemrum imellem emne prefixet og det
-# oprindelige emne.
-#
-# gyldige værdier:
-#    0 = "Aldrig"
-#    1 = "Altid"
-#    2 = "Efter behov"
+# If your mailing list's default language uses a non-ASCII character set
+# and the prefix contains non-ASCII characters, the prefix will always
+# be encoded according to the relevant standards.  However, if your
+# prefix contains only ASCII characters, you may want to set this option
+# to Never to disable prefix encoding.  This can make the subject
+# headers slightly more readable for users with mail readers that don't
+# properly handle non-ASCII encodings.
+# 
+# Note however, that if your mailing list receives both encoded and
+# unencoded subject headers, you might want to choose As needed.  Using
+# this setting, Mailman will not encode ASCII prefixes when the rest of
+# the header contains only ASCII characters, but if the original header
+# contains non-ASCII characters, it will encode the prefix.  This avoids
+# an ambiguity in the standards which could cause some mail readers to
+# display extra, or missing spaces between the prefix and the original
+# header.
+#
+# legal values are:
+#    0 = "Never"
+#    1 = "Always"
+#    2 = "As needed"
 encode_ascii_prefixes = 0
 
 ## Nondigest options
 #
-# Regler for levering i normal-modus.
+# Policies concerning immediately delivered list traffic.
 
-# Kan medlemmer vælge normal-modus?
+# Can subscribers choose to receive mail immediately, rather than in
+# batched digests?
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 nondigestable = 1
 
-# Tekst der tilføjes &oslash;verst i e-mail der sendes til listens
-# medlemmer. This text can include Python format strings which are
-# resolved against list attributes.  The list of substitutions allowed
-# are:
+# Text prepended to the top of every immediately-delivery message. This
+# text can include Python format strings which are resolved against list
+# attributes.  The list of substitutions allowed are:
 # 
 # 
 # real_name - The "pretty" name of the list; usually the list name with
@@ -417,10 +404,9 @@ nondigestable = 1
 # 
 msg_header = ''
 
-# Tekst som tilf&oslash;jes nederst i e-mail der sendes til listens
-# medlemmer. This text can include Python format strings which are
-# resolved against list attributes.  The list of substitutions allowed
-# are:
+# Text appended to the bottom of every immediately-delivery message.
+# This text can include Python format strings which are resolved against
+# list attributes.  The list of substitutions allowed are:
 # 
 # 
 # real_name - The "pretty" name of the list; usually the list name with
@@ -447,45 +433,54 @@ msg_footer = """_______________________________________________
 %(real_name)s maillist  -  %(real_name)s@%(host_name)s
 %(web_page_url)slistinfo/%(_internal_name)s"""
 
+# When you scrub attachments, they are stored in archive area and links
+# are made in the message so that the member can access via web browser.
+# If you want the attachments totally disappear, you can use content
+# filter options.
+#
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
+scrub_nondigest = False
+
 ## Digest options
 #
-# Opsætning af sammendrag-modus.
+# Batched-delivery digest characteristics.
 
-# Kan medlemmer af listen vælge sammendrag-modus?
+# Can list members choose to receive list traffic bunched in digests?
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 digestable = 1
 
-# Hvilken modus er standard for nye brugere?
+# Which delivery mode is the default for new users?
 #
-# gyldige værdier:
-#    0 = "Normal"
-#    1 = "Sammendrag"
+# legal values are:
+#    0 = "Regular"
+#    1 = "Digest"
 digest_is_default = 0
 
-# Hvilket format skal benyttes som standard for samle-email?
+# When receiving digests, which format is default?
 #
-# gyldige værdier:
-#    0 = "Ren tekst"
+# legal values are:
+#    0 = "Plain"
 #    1 = "MIME"
 mime_is_default_digest = 0
 
-# Hvor stor (i KB) m&aring; en samle-email h&oslash;jst v&aelig;re
-# f&oslash;r den udsendes?
+# How big in Kb should a digest be before it gets sent out?
 digest_size_threshhold = 30
 
-# Skal der sendes en samle-email dagligt, selv om st&oslash;rrelsen ikke
-# er opn&aring;et?
+# Should a digest be dispatched daily when the size threshold isn't
+# reached?
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 digest_send_periodic = 1
 
-# Tekst som tilf&oslash;jes &oslash;verst i samle-emailen, f&oslash;r
-# indholdsfortegnelsen.This text can include Python format strings which
+# Text attached (as an initial message, before the table of contents) to
+# the top of digests. This text can include Python format strings which
 # are resolved against list attributes.  The list of substitutions
 # allowed are:
 # 
@@ -512,10 +507,9 @@ digest_send_periodic = 1
 # 
 digest_header = ''
 
-# Tekst der tilføjes nederst i hver samle-email, som sidste
-# information.This text can include Python format strings which are
-# resolved against list attributes.  The list of substitutions allowed
-# are:
+# Text attached (as a final message) to the bottom of digests. This text
+# can include Python format strings which are resolved against list
+# attributes.  The list of substitutions allowed are:
 # 
 # 
 # real_name - The "pretty" name of the list; usually the list name with
@@ -542,277 +536,279 @@ digest_footer = """_______________________________________________
 %(real_name)s maillist  -  %(real_name)s@%(host_name)s
 %(web_page_url)slistinfo/%(_internal_name)s"""
 
-# N&aring;r et nyt volume startes, &oslash;ges volume nummeret, og
-# udgavenummeret s&aelig;ttes til 1.
+# When a new digest volume is started, the volume number is incremented
+# and the issue number is reset to 1.
 #
-# gyldige værdier:
-#    0 = "&Aring;rlig"
-#    1 = "M&aring;nedlig"
-#    2 = "Kvartalsvis"
-#    3 = "Ugentlig"
-#    4 = "Daglig"
+# legal values are:
+#    0 = "Yearly"
+#    1 = "Monthly"
+#    2 = "Quarterly"
+#    3 = "Weekly"
+#    4 = "Daily"
 digest_volume_frequency = 1
 
 ## Privacy options
 #
-# Her kan du bestemme hvad der kr&aelig;ves for at tilmelde sig til
-# maillisten, og bl.a. bestemme om maillisten skal v&aelig;re skjult
-# eller ikke. Se ogs&aring; <a
-# href="http://mail.jones.dk/cgi-bin/mailman/admin/users/archive">Indstillinger 
-# for arkivering</a> for egne indstillinger, n&aring;r det g&aelig;lder
-# arkivet og arkivering.
+# This section allows you to configure subscription and membership
+# exposure policy.  You can also control whether this list is public or
+# not.  See also the <a
+# href="http://mail.jones.dk/cgi-bin/mailman/admin/users/archive">Archival 
+# Options</a> section for separate archive-related privacy settings.
 
-# Vis denne mailliste n&aring;r nogen beder om at se en oversigt over
-# maillister p&aring; denne maskine?
+# Advertise this list when people ask what lists are on this machine?
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 advertised = 1
 
-# bekræftelse(*) - bekr&aelig;ftelse via e-mail er n&oslash;dvendig
-# godkendelse - anmodning om medlemskab skal godkendes af
-# listeadministrator (eller evt. listemoderator) bekr&aelig;ftelse +
-# godkendelse - b&aring;de bekr&aelig;ftelse via e-mail og godkendelse
-# fra listeadministrator (evt. listemoderator) er n&oslash;dvendig
-# 
-# (*) n&aring;r nogen vil tilmelde sig en liste, sender Mailman en
-# meddelelse med en unik identifikator som skal angives for at
-# bekr&aelig;fte tilmeldingen. P&aring; den m&aring;de vil det ikke
-# v&aelig;re muligt at tilmelde nogen imod deres vilje.
-#
-# gyldige værdier:
-#    1 = "Bekr&aelig;ftelse"
-#    2 = "Godkendelse"
-#    3 = "Bekr&aelig;ftelse og godkendelse"
+# Confirm (*) - email confirmation required Require approval - require
+# list administrator approval for subscriptions Confirm and approve -
+# both confirm and approve
+# 
+# (*) when someone requests a subscription, Mailman sends them a notice
+# with a unique subscription request number that they must reply to in
+# order to subscribe. This prevents mischievous (or malicious) people
+# from creating subscriptions for others without their consent.
+#
+# legal values are:
+#    1 = "Confirm"
+#    2 = "Require approval"
+#    3 = "Confirm and approve"
 subscribe_policy = 2
 
-# N&aring;r medlemmer &oslash;nsker at forlade en mailliste, sender de
-# en anmodning om framelding, enten via web, eller via e-mail. Normalt
-# er det bedst at disse anmodninger automatisk godkendes, s&aring;
-# medlemmer kan afmelde sig n&aring;r de &oslash;nsker det (mange
-# &oslash;nsker selv at kunne administrere en framelding). For nogle
-# f&aring; maillister kan det alligevel v&aelig;re aktuelt at have
-# kontrol over om medlemmer kan afmelde sig selv eller ej. En liste som
-# alle ansatte i et firma SKAL v&aelig;re medlem af, er et eksempel
-# p&aring; en s&aring;dan liste.
-#
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# When members want to leave a list, they will make an unsubscription
+# request, either via the web or via email. Normally it is best for you
+# to allow open unsubscriptions so that users can easily remove
+# themselves from mailing lists (they get really upset if they can't get
+# off lists!).
+# 
+# For some lists though, you may want to impose moderator approval
+# before an unsubscription request is processed.  Examples of such lists
+# include a corporate mailing list that all employees are required to be
+# members of.
+#
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 unsubscribe_policy = 0
 
-# Alle e-mailadresser som angives her vil blive udelukket fra listen, og
-# kan ikke tilmelde sig. Indtast e-mailadresser, en pr. linie, start
-# linien med tegnet ^ for at angive et regexp-udtryk der skal stemme
-# overens med afsenderadressen.
+# Addresses in this list are banned outright from subscribing to this
+# mailing list, with no further moderation required.  Add addresses one
+# per line; start the line with a ^ character to designate a regular
+# expression match.
 ban_list = []
 
-# Hvis denne indstilling ikke er sat til 'Alle', vil medlemslisten blive
-# beskyttet af medlemmernes eller administrators adgangskode.
+# When set, the list of subscribers is protected by member or admin
+# password authentication.
 #
-# gyldige værdier:
-#    0 = "Alle"
-#    1 = "Kun medlemmer af listen"
-#    2 = "Kun listeadministrator"
+# legal values are:
+#    0 = "Anyone"
+#    1 = "List members"
+#    2 = "List admin only"
 private_roster = 2
 
-# V&aelig;lger du 'Ja' her, vil medlemmers e-mailadresser blive
-# omskrevet n&aring;r de vises i en oversigt p&aring; websiderne
-# (b&aring;de som tekst og som links), s&aring; de ikke er nemme at
-# tolke som e-mailadresser. Formålet er at undg&aring; at medlemmernes
-# mailadresser bliver opsamlet af e-mailsniffere som skanner websider
-# for e-mailadresser (og derefter bruger dem til at udsende spam/junk
-# mail).
-#
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# Setting this option causes member email addresses to be transformed
+# when they are presented on list web pages (both in text and as links),
+# so they're not trivially recognizable as email addresses.  The
+# intention is to prevent the addresses from being snarfed up by
+# automated web scanners for use by spammers.
+#
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 obscure_addresses = 1
 
 ## Privacy options
 #
-# N&aring;r en meddelelse sendes til maillisten, g&aring;r den igennem
-# nogle trin for at afg&oslash;re om moderator skal godkende meddelelsen
-# eller ikke. Her finder du indstillinger til at kontrollere moderation
-# af e-mail fra b&aring;de medlemmer og ikke-medlemmer.
-# 
-# <p>E-mail fra medlemmer holdes tilbage for godkendelse hvis deres
-# <b>moderationsflag</b> er sat. Du kan bestemme om e-mail fra medlemmer
-# normalt skal vurderes eller ikke f&oslash;r den sendes til listen.
-# 
-# <p>E-mail som ikke er sendt af medlemmer af listen, kan automatisk
-# blive <a
-# href="?VARHELP=privacy/sender/accept_these_nonmembers">godkendt</a>,
-# <a href="?VARHELP=privacy/sender/hold_these_nonmembers">holdt tilbage
-# for godkendelse</a>, <a
-# href="?VARHELP=privacy/sender/reject_these_nonmembers">afvist (sendt
-# retur)</a>, eller <a
-# href="?VARHELP=privacy/sender/discard_these_nonmembers">slettet</a>,
-# enten enkeltvis eller som en gruppe. Al e-mail fra ikke-medlemmer, som
-# ikke specifikt bliver godkendt, sendt retur eller slettet, vil blive
-# behandlet alt efter hvad <a
-# href="?VARHELP=privacy/sender/generic_nonmember_action">generelle
-# regler for ikke-medlemmer</a> viser.
-# 
-# <p>I tekstboksene nedenfor kan du tilf&oslash;je en e-mailadresse pr.
-# linie. Du kan ogs&aring; tilf&oslash;je  <a
-# href="http://www.python.org/doc/current/lib/module-re.html">Python
-# regexp-udtryk</a>. Begynd i s&aring; fald linien med tegnet ^ for at
-# markere at det er et s&aring;dant udtryk. N&aring;r du benytter
-# backslash, skriv da lige som i rene strings (Python raw strings)
-# (normalt kun &eacute;n backslash ad gangen).
-# 
-# <p>Bem&aelig;rk: sammenligning med normale e-mailadresser
-# udf&oslash;res f&oslash;rst, regexp-udtryk vil derfor blive behandlet
-# sidst.
-
-# Hvert medlem af listen har et moderationsflag som fort&aelig;ller om
-# e-mails fra medlemmet kan sendes direkte til e-maillisten, eller om de
-# f&oslash;rst skal godkendes af listemoderator. N&aring;r
-# moderationsflaget er sat til, skal e-mails fra medlemmet godkendes af
-# listemoderator f&oslash;r de udsendes til alle p&aring; listen. Som
-# listeadministrator kan du for hvert enkelt medlem bestemme om
-# medlemmets e-mail skal modereres eller ikke. N&aring;r et nyt medlem
-# tilmeldes listen, s&aelig;ttes moderationsflaget til den indstilling
-# du v&aelig;lger her. S&aelig;t den til 'Nej' hvis du &oslash;nsker at
-# e-mail fra medlemmer normalt skal g&aring; lige til listen. S&aelig;t
-# den til 'Ja' hvis du &oslash;nsker at e-mail fra nye medlemmer skal
-# godkendes f&oslash;r de udsendes til hele listen. Du kan altid
-# s&aelig;tte moderationsflaget for hvert enkelt medlem fra
-# Administration af medlemmer siden.
-#
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# When a message is posted to the list, a series of moderation steps are
+# take to decide whether the a moderator must first approve the message
+# or not.  This section contains the controls for moderation of both
+# member and non-member postings.
+# 
+# <p>Member postings are held for moderation if their <b>moderation
+# flag</b> is turned on.  You can control whether member postings are
+# moderated by default or not.
+# 
+# <p>Non-member postings can be automatically <a
+# href="?VARHELP=privacy/sender/accept_these_nonmembers" >accepted</a>,
+# <a href="?VARHELP=privacy/sender/hold_these_nonmembers">held for
+# moderation</a>, <a
+# href="?VARHELP=privacy/sender/reject_these_nonmembers" >rejected</a>
+# (bounced), or <a
+# href="?VARHELP=privacy/sender/discard_these_nonmembers"
+# >discarded</a>, either individually or as a group.  Any posting from a
+# non-member who is not explicitly accepted, rejected, or discarded,
+# will have their posting filtered by the <a
+# href="?VARHELP=privacy/sender/generic_nonmember_action">general
+# non-member rules</a>.
+# 
+# <p>In the text boxes below, add one address per line; start the line
+# with a ^ character to designate a <a href=
+# "http://www.python.org/doc/current/lib/module-re.html" >Python regular
+# expression</a>.  When entering backslashes, do so as if you were using
+# Python raw strings (i.e. you generally just use a single backslash).
+# 
+# <p>Note that non-regexp matches are always done first.
+
+# Each list member has a moderation flag which says whether messages
+# from the list member can be posted directly to the list, or must first
+# be approved by the list moderator.  When the moderation flag is turned
+# on, list member postings must be approved first.  You, the list
+# administrator can decide whether a specific individual's postings will
+# be moderated or not.
+# 
+# When a new member is subscribed, their initial moderation flag takes
+# its value from this option.  Turn this option off to accept member
+# postings by default.  Turn this option on to, by default, moderate
+# member postings first.  You can always manually set an individual
+# member's moderation bit by using the membership management screens.
+#
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 default_member_moderation = 1
 
+# Hold -- this holds the message for approval by the list moderators.
 # 
-# Hold tilbage -- meddelelsen holdes tilbage for godkendelse af
-# listemoderator(er). Afvis -- meddelelsen sendes automatisk retur til
-# afsender. Begrundelsen der sendes kan du skrive selv Slet --
-# meddelelsen bliver fjernet uden at give besked om dette til afsender.
+# Reject -- this automatically rejects the message by sending a bounce
+# notice to the post's author.  The text of the bounce notice can be <a
+# href="?VARHELP=privacy/sender/member_moderation_notice" >configured by
+# you.
+# 
+# Discard -- this simply discards the message, with no notice sent to
+# the post's author.
 # 
 #
-# gyldige værdier:
-#    0 = "Hold&nbsp;tilbage"
-#    1 = "Afvis"
-#    2 = "Slet"
+# legal values are:
+#    0 = "Hold"
+#    1 = "Reject"
+#    2 = "Discard"
 member_moderation_action = 0
 
-# Tekst som skal sendes med meddelelsen om afvisning som sendes til
-# modererede medlemmer af listen.
+# Text to include in any <a
+# href="?VARHELP/privacy/sender/member_moderation_action" >rejection
+# notice to be sent to moderated members who post to this list.
 member_moderation_notice = ''
 
-# E-mail fra disse ikke-medlemmer vil automatisk blive godkendt.
-# Tilf&oslash;j e-mailadresser, en pr. linie. Start linien med tegnet ^
-# for at angive et regexp-udtryk som skal stemme overens med
-# afsenderadressen.
+# Postings from any of these non-members will be automatically accepted
+# with no further moderation applied.  Add member addresses one per
+# line; start the line with a ^ character to designate a regular
+# expression match.
 accept_these_nonmembers = ['jonas@jones.dk']
 
-# e-mail fra disse ikke-medlemmer vil automatisk blive holdt tilbage for
-# vurdering af listemoderator. Afsenderen vil modtage en meddelelse om
-# dette, med bl.a. instruktioner om hvordan han/hun kan
-# tilbagetr&aelig;kke sin e-mail. Indtast e-mailadresser, en pr. linie.
-# Start linien med tegnet ^ for at angive et regexp-udtryk som skal
-# stemme overens med afsenderadressen.
+# Postings from any of these non-members will be immediately and
+# automatically held for moderation by the list moderators. The sender
+# will receive a notification message which will allow them to cancel
+# their held message.  Add member addresses one per line; start the line
+# with a ^ character to designate a regular expression match.
 hold_these_nonmembers = []
 
-# E-mail fra disse ikke-medlemmer vil automatisk blive afvist. De vil
-# f&aring; mailen retur, med en meddelelse om at den blev automatisk
-# afvist. Dette valg b&oslash;r ikke benyttes for kendte spammere, de
-# b&oslash;r automatisk slettes. Indtast e-mailadresser, en pr. linie.
-# Start linien med tegnet ^ for at angive et regexp-udtryk som skal
-# stemme overens med afsenderadressen.
+# Postings from any of these non-members will be automatically rejected.
+# In other words, their messages will be bounced back to the sender with
+# a notification of automatic rejection.  This option is not appropriate
+# for known spam senders; their messages should be <a
+# href="?VARHELP=privacy/sender/discard_these_nonmembers" >automatically
+# discarded.
+# 
+# Add member addresses one per line; start the line with a ^ character
+# to designate a regular expression match.
 reject_these_nonmembers = []
 
-# E-mail fra disse ikke-medlemmer vil automatisk blive slettet. Det vil
-# sige at meddelelsen afvises uden nogen form for tilbagemelding, men
-# listemoderator kan (om &oslash;nsket) modtage en kopi af den afviste
-# e-mail. Tilf&oslash;j e-mailadresser, en pr. linie, start linien med
-# tegnet ^ for at angive et regexp-udtryk der skal stemme overens med
-# afsenderadressen.
+# Postings from any of these non-members will be automatically
+# discarded.  That is, the message will be thrown away with no further
+# processing or notification.  The sender will not receive a
+# notification or a bounce, however the list moderators can optionally
+# <a href="?VARHELP=privacy/sender/forward_auto_discards" >receive
+# copies of auto-discarded messages..
+# 
+# Add member addresses one per line; start the line with a ^ character
+# to designate a regular expression match.
 discard_these_nonmembers = []
 
-# N&aring;r en e-mail fra et ikke-medlem bliver modtaget, sammenlignes
-# e-mailens afsender med listen over e-mailadresser der skal godkendes,
-# holdes tilbage, <a
-# href="?VARHELP=privacy/sender/reject_these_nonmembers" >afvises
-# (sendes retur), eller slettes. Hvis afsenderadressen ikke stemmer
-# overens med en adresse der findes i listerne, bliver f&oslash;lgende
-# afg&oslash;relse truffet.
-#
-# gyldige værdier:
-#    0 = "Godkend"
-#    1 = "Hold&nbsp;tilbage"
-#    2 = "Afvis"
-#    3 = "Slet"
+# When a post from a non-member is received, the message's sender is
+# matched against the list of explicitly <a
+# href="?VARHELP=privacy/sender/accept_these_nonmembers" >accepted,
+# held, <a href="?VARHELP=privacy/sender/reject_these_nonmembers"
+# >rejected (bounced), and <a
+# href="?VARHELP=privacy/sender/discard_these_nonmembers" >discarded
+# addresses.  If no match is found, then this action is taken.
+#
+# legal values are:
+#    0 = "Accept"
+#    1 = "Hold"
+#    2 = "Reject"
+#    3 = "Discard"
 generic_nonmember_action = 3
 
-# Skal meddelelser fra ikke-medlemmer, hvis mail automatisk slettes,
-# videresendes til listemoderator?
+# Should messages from non-members, which are automatically discarded,
+# be forwarded to the list moderator?
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 forward_auto_discards = 1
 
+# Text to include in any rejection notice to be sent to non-members who
+# post to this list. This notice can include the list's owner address by
+# %(listowner)s and replaces the internally crafted default message.
+nonmember_rejection_notice = ''
+
 ## Privacy options
 #
-# Her kan du ops&aelig;tte filtrering baseret på modtageren af
-# meddelelsen.
+# This section allows you to configure various filters based on the
+# recipient of the message.
 
-# Meget (faktisk det meste) spam/junk mail har ikke de endelige
-# modtagere i modtagerfelterne. Faktisk indeholder felterne To: og/eller
-# Cc: oftest en helt ugyldig adresse. Begr&aelig;nsningen du
-# s&aelig;tter her har kun indvirkning p&aring; det som st&aring;r
-# f&oslash;r '@' tegnet i adressen, men filtret vil alligevel opfange og
-# blokere det meste spam/junk mail.
+# Many (in fact, most) spams do not explicitly name their myriad
+# destinations in the explicit destination addresses - in fact often the
+# To: field has a totally bogus address for obfuscation.  The constraint
+# applies only to the stuff in the address before the '@' sign, but
+# still catches all such spams.
+# 
+# The cost is that the list will not accept unhindered any postings
+# relayed from other addresses, unless
+# 
 # 
-# Prisen for dette er, at listen ikke uhindret vil kunne modtage e-mail
-# videresendt via andre e-mailadresser, med mindre
+# The relaying address has the same name, or
 # 
+# The relaying address name is included on the options that specifies
+# acceptable aliases for the list.
 # 
-# Adressen der videresendes fra hedder det samme, eller Adressen der
-# videresendes fra inkluderes i indstillingen som bestemmer gyldige
-# aliaser for listen.
 # 
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 require_explicit_destination = 1
 
-# Alternative e-mailadresser som godtages n&aring;r
-# 'require_explicit_destination' er sat til. Som v&aelig;rdi for denne
-# indstilling skal du angive regexp-udtryk ("regular expressions"), et
-# udtryk pr. linie, der sammenlignes med hver modtageradresse i
-# meddelelsen. Sammenligningen udf&oslash;res med Pythons re.match()
-# funktion, som betyder at de kun g&aelig;lder for begyndelsen af
-# strengen.
-# 
-# For bagudkompatibilitet med Mailman 1.1, hvis regexp-udtryk ikke
-# indeholder en '@', sammenlignes udtrykket kun med den f&oslash;rste
-# del (det som st&aring;r f&oslash;r '@') i modtageradressen. Hvis
-# sammenligningen ikke lykkes, eller hvis udtrykket ikke indholder en
-# '@', sammenlignes udtrykket med hele modtageradressen.
-# 
-# Sammenligning med kun den f&oslash;rste del af en modtageradresse
-# underst&oslash;ttes ikke l&aelig;ngere. I fremtidige versioner af
-# Mailman vil kun sammenligning med hele modtageradresser blive
-# underst&oslash;ttet.
+# Alternate addresses that are acceptable when
+# `require_explicit_destination' is enabled.  This option takes a list
+# of regular expressions, one per line, which is matched against every
+# recipient address in the message.  The matching is performed with
+# Python's re.match() function, meaning they are anchored to the start
+# of the string.
+# 
+# For backwards compatibility with Mailman 1.1, if the regexp does not
+# contain an `@', then the pattern is matched against just the local
+# part of the recipient address.  If that match fails, or if the pattern
+# does contain an `@', then the pattern is matched against the entire
+# recipient address.
+# 
+# Matching against the local part is deprecated; in a future release,
+# the pattern will always be matched against the entire recipient
+# address.
 acceptable_aliases = ''
 
-# Hvis en mail der er sendt til listen indeholder s&aring; mange som
-# eller flere modtagere end denne v&aelig;rdi, holdes mailen tilbage,
-# s&aring; listeadministrator eventuelt kan godkende den. Brug
-# v&aelig;rdien 0 for ingen begr&aelig;nsning.
+# If a posting has this number, or more, of recipients, it is held for
+# admin approval.  Use 0 for no ceiling.
 max_num_recipients = 10
 
 ## Privacy options
 #
-# Her kan du opsætte forskellige anti-spam filtre, som kan bidrage til
-# at reducere mængden af spam der distribueres via e-maillisten.
+# This section allows you to configure various anti-spam filters posting
+# filters, which can help reduce the amount of spam your list members
+# end up receiving.
+# 
 
 # Each header filter rule has two parts, a list of regular expressions,
 # one per line, and an action to take.  Mailman matches the message's
@@ -823,22 +819,23 @@ max_num_recipients = 10
 # You can have more than one filter rule for your list.  In that case,
 # each rule is matched in turn, with processing stopped after the first
 # match.
+# 
+# Note that headers are collected from all the attachments (except for
+# the mailman administrivia message) and matched against the regular
+# expressions. With this feature, you can effectively sort out messages
+# with dangerous file types or file name extensions.
 header_filter_rules = []
 
-# Brug denne indstilling til at bortfiltrere mail til listen, baseret
-# p&aring; indholdet af et eller flere felter i brevhovedet. Her skal du
-# skrive regexp-udtryk (regular expressions), et pr. linie, som
-# sammenlignes med det aktuelle felt. Sammenligningen skelner ikke
-# imellem store og sm&aring; bogstaver. Linier der begynder med '#'
-# sammenlignes ikke.
+# Use this option to prohibit posts according to specific header values.
+# The target value is a regular-expression for matching against the
+# specified header.  The match is done disregarding letter case.  Lines
+# beginning with '#' are ignored as comments.
 # 
-# For eksempel: udtrykket to: .*@public.com fort&aelig;ller at al mail
-# som indeholder '@public.com' i To: feltet, skal holdes tilbage for
-# godkendelse.
+# For example:to: .*@public.com  says to hold all postings with a To:
+# mail header containing '@public.com' anywhere among the addresses.
 # 
-# Bem&aelig;rk: tomme tegn i starten af regexp-udtrykket fjernes. Dette
-# kan omg&aring;s p&aring; flere m&aring;der, f.eks. ved at bruge
-# escape-tegn eller parenteser.
+# Note that leading whitespace is trimmed from the regexp.  This can be
+# circumvented in a number of ways, e.g. by escaping or bracketing it.
 bounce_matching_headers = """# Lines that *start* with a '#' are comments.
 to: friend@public.com
 message-id: relay.comanche.denmark.eu
@@ -847,415 +844,439 @@ from: .*@uplinkpro.com"""
 
 ## Bounce options
 #
-# Disse regler bestemmer hvordan automatisk behandling af returmails
-# skal foreg&aring;. Her er en oversigt over hvordan det virker.
-# 
-# <p>N&aring;r Mailman modtager en returmail, bliver to ting
-# fors&oslash;gt tolket. Den ene er e-mailadressen for medlemmet som
-# egentlig skulle modtage e-mailen, og den anden er &aring;rsagen til
-# problemet. &Aring;rsagen tolkes til at v&aelig;re <em>alvorlig</em>
-# eller <em>harml&oslash;s</em> alt efter om &aring;rsagen er af kritisk
-# eller af mindre alvorlig art. Hvis der er tvivl, tolkes &aring;rsagen
-# som alvorlig.
-# 
-# <p>Hvis ingen e-mailadresse kan hentes ud af meddelelsen, bliver den
-# normalt afvist. Ellers vil medlemmet som har e-mailadressen f&aring;
-# tildelt et <em>returtal</em>, og hver gang der kommer en
-# returmeddelelse vil tallet &oslash;ges. Alvorlige &aring;rsager
-# f&oslash;rer til at tallet &oslash;ges med 1, harml&oslash;se
-# &aring;rsager f&oslash;rer til at det &oslash;ges med 0.5. Dette sker
-# kun &eacute;n gang pr. dag, s&aring; selv om der kommer 10 alvorlige
-# returmails fra et medlem p&aring; &eacute;n dag, vil tallet kun
-# &oslash;ges med 1.
-# 
-# <p>N&aring;r returtallet for et medlem n&aring;r en vis <a
-# href="?VARHELP=bounce/bounce_score_threshold">gr&aelig;nse</a>,
-# stoppes levering til medlemmet. Dermed vil medlemmet ikke modtage
-# e-mail fra listen f&oslash;r levering s&aelig;ttes til igen. Medlemmet
-# vil med j&aelig;vne mellemrum modtage meddelelse om at dette er sket,
-# og hvad han/hun skal g&oslash;re for at f&aring; e-mail fra listen
-# igen.
-# 
-# <p>Du kan bestemme <a
-# href="?VARHELP=bounce/bounce_you_are_disabled_warnings">hvor mange
-# advarsler</a> medlemmet skal have og <a
-# href="?VARHELP=bounce/bounce_you_are_disabled_warnings_interval">hvor
-# ofte</a> han/hun skal modtage s&aring;danne advarsler.
-# 
-# <p>Der er en vigtig indstilling mere: efter en vis tid -- hvor ingen
-# returmeddelelser dukker op -- regnes returinformation for at
-# v&aelig;re <a
-# href="?VARHELP=bounce/bounce_info_stale_after">for&aelig;ldet</a> og
-# stoppes. Ved at justere denne v&aelig;rdi, og s&aelig;tte en
-# gr&aelig;nse for returantallet, kan du bestemme hvor lang tid der skal
-# g&aring; f&oslash;r levering til et medlem stoppes. Begge disse
-# v&aelig;rdier b&oslash;r tilpasses efter hvor ofte og hvor meget
-# e-mail der sendes til din liste.
-
-# Ved at sætte denne værdi til Nej, slår du al automatisk tolkning af
-# returmeddelelser for denne liste fra. Bemærk at hvis meddelelser
-# afvises vil listeadministratoren ikke blive forstyrret med dem.
-#
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# These policies control the automatic bounce processing system in
+# Mailman.  Here's an overview of how it works.
+# 
+# <p>When a bounce is received, Mailman tries to extract two pieces of
+# information from the message: the address of the member the message
+# was intended for, and the severity of the problem causing the bounce.
+# The severity can be either <em>hard</em> or <em>soft</em> meaning
+# either a fatal error occurred, or a transient error occurred.  When in
+# doubt, a hard severity is used.
+# 
+# <p>If no member address can be extracted from the bounce, then the
+# bounce is usually discarded.  Otherwise, each member is assigned a
+# <em>bounce score</em> and every time we encounter a bounce from this
+# member we increment the score.  Hard bounces increment by 1 while soft
+# bounces increment by 0.5.  We only increment the bounce score once per
+# day, so even if we receive ten hard bounces from a member per day,
+# their score will increase by only 1 for that day.
+# 
+# <p>When a member's bounce score is greater than the <a
+# href="?VARHELP=bounce/bounce_score_threshold">bounce score
+# threshold</a>, the subscription is disabled.  Once disabled, the
+# member will not receive any postings from the list until their
+# membership is explicitly re-enabled (either by the list administrator
+# or the user).  However, they will receive occasional reminders that
+# their membership has been disabled, and these reminders will include
+# information about how to re-enable their membership.
+# 
+# <p>You can control both the <a
+# href="?VARHELP=bounce/bounce_you_are_disabled_warnings">number of
+# reminders</a> the member will receive and the <a
+# href="?VARHELP=bounce/bounce_you_are_disabled_warnings_interval"
+# >frequency</a> with which these reminders are sent.
+# 
+# <p>There is one other important configuration variable; after a
+# certain period of time -- during which no bounces from the member are
+# received -- the bounce information is <a
+# href="?VARHELP=bounce/bounce_info_stale_after">considered stale</a>
+# and discarded.  Thus by adjusting this value, and the score threshold,
+# you can control how quickly bouncing members are disabled.  You should
+# tune both of these to the frequency and traffic volume of your list.
+
+# By setting this value to No, you disable all automatic bounce
+# processing for this list, however bounce messages will still be
+# discarded so that the list administrator isn't inundated with them.
+#
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 bounce_processing = 1
 
-# Hvert medlem tildeles et returtal, og hver gang der kommer en
-# returmeddelelse vil dette tal &oslash;ges.  Alvorlige (&aring;rsager
-# f&oslash;rer til at det &oslash;ges med 1, mens harml&oslash;se
-# &aring;rsager f&oslash;rer til at det &oslash;ges med 0.5. Dette sker
-# kun &eacute;n gang pr. dag, s&aring; selv om der kommer 10 alvorlige
-# returmails fra et medlem p&aring; &eacute;n dag, vil tallet kun
-# &oslash;ges med 1.
-# 
-# Her s&aelig;ttes den &oslash;vre gr&aelig;nse for medlemmets returtal
-# Overskrides denne gr&aelig;nse stoppes levering automatisk, men
-# medlemmet bliver ikke fjernet fra listen.
+# Each subscriber is assigned a bounce score, as a floating point
+# number.  Whenever Mailman receives a bounce from a list member, that
+# member's score is incremented.  Hard bounces (fatal errors) increase
+# the score by 1, while soft bounces (temporary errors) increase the
+# score by 0.5.  Only one bounce per day counts against a member's
+# score, so even if 10 bounces are received for a member on the same
+# day, their score will increase by just 1.
+# 
+# This variable describes the upper limit for a member's bounce score,
+# above which they are automatically disabled, but not removed from the
+# mailing list.
 bounce_score_threshold = 5.0
 
-# Antal dage f&oslash;r returinformation stoppes hvis der ikke dukker
-# flere returmails op. Dette tal skal v&aelig;re et heltal.
+# The number of days after which a member's bounce information is
+# discarded, if no new bounces have been received in the interim.  This
+# value must be an integer.
 bounce_info_stale_after = 7
 
-# Hvor mange Levering til dig er stoppet advarsler der skal sendes til
-# et medlem f&oslash;r medlemmet frameldes listen. S&aelig;t denne værdi
-# til 0 for at fjerne et medlem fra listen straks, hvis der kommer
-# returmails fra medlemmets e-mailadresse. Dette tal skal være et
-# heltal.
+# How many Your Membership Is Disabled warnings a disabled member should
+# get before their address is removed from the mailing list.  Set to 0
+# to immediately remove an address from the list once their bounce score
+# exceeds the threshold.  This value must be an integer.
 bounce_you_are_disabled_warnings = 3
 
-# Antal dage imellem hver gang en Levering til dig er stoppet advarsel
-# skal sendes ud. Dette tal skal være et heltal.
+# The number of days between sending the Your Membership Is Disabled
+# warnings.  This value must be an integer.
 bounce_you_are_disabled_warnings_interval = 7
 
-# Mailmans automatiske returmailh&aring;ndtering er meget robust, men
-# det er alligevel umuligt at genkende alle typer returmails der kommer.
-# Du b&oslash;r v&aelig;lge Ja her, af to grunde: 1) Hvis det virkelig
-# er en permanent returmail fra et medlem af listen, b&oslash;r du
-# antagelig manuelt afmelde medlemmet fra listen, og 2) du vil
-# m&aring;ske sende en meddelelse til udviklerne af Mailman s&aring;dan
-# at returmails automatisk genkendes af Mailman i senere versioner. Hvis
-# du ikke vil g&oslash;re nogen af delene, s&aelig;ttes denne
-# indstilling til Nej. S&aring; vil alle returmails afvises automatisk
-# uden videre behandling. Bem&aelig;rk: Denne indstilling vil ogs&aring;
-# indvirke p&aring; al e-mail der sendes til listens -admin adresse. Den
-# adresse er for&aelig;ldet og udg&aring;et, men måske vil nogen
-# alligevel fortsat sende e-mail til den. Hvis nogen g&oslash;r det, og
-# du har sat denne indstilling til Nej, vil disse mails ogs&aring; blive
-# afvist. M&aring;ske vil du ogs&aring; ops&aelig;tte et automatisk svar
-# p&aring; e-mail sendt til -owner og -admin adresserne.
-#
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# While Mailman's bounce detector is fairly robust, it's impossible to
+# detect every bounce format in the world.  You should keep this
+# variable set to Yes for two reasons: 1) If this really is a permanent
+# bounce from one of your members, you should probably manually remove
+# them from your list, and 2) you might want to send the message on to
+# the Mailman developers so that this new format can be added to its
+# known set.
+# 
+# If you really can't be bothered, then set this variable to No and all
+# non-detected bounces will be discarded without further processing.
+# 
+# Note: This setting will also affect all messages sent to your list's
+# -admin address.  This address is deprecated and should never be used,
+# but some people may still send mail to this address.  If this happens,
+# and this variable is set to No those messages too will get discarded.
+# You may want to set up an autoresponse message for email to the -owner
+# and -admin address.
+#
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 bounce_unrecognized_goes_to_list_owner = 1
 
-# Ved at sætte denne til Nej, fravælges beskeden der normalt sendes til
-# ejer(e) af listen, når levering af e-mail til et medlem stoppes på
-# grund af for mange returmails. Der vil til gengæld altid blive forsøgt
-# afsendt en e-mail med besked til medlemmet.
+# By setting this value to No, you turn off notification messages that
+# are normally sent to the list owners when a member's delivery is
+# disabled due to excessive bounces. An attempt to notify the member
+# will always be made.
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 bounce_notify_owner_on_disable = 1
 
-# Ved at sætte denne til Nej, fravælges beskeden der normalt sendes til
-# ejer(e) af listen, når et medlem frameldes listen på grund af for
-# mange returmails. Der vil til gengæld altid blive forsøgt afsendt en
-# e-mail med besked til medlemmet.
+# By setting this value to No, you turn off notification messages that
+# are normally sent to the list owners when a member is unsubscribed due
+# to excessive bounces.  An attempt to notify the member will always be
+# made.
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 bounce_notify_owner_on_removal = 1
 
 ## Archive options
 #
-# Regler for arkivering
+# List traffic archival policies.
 
-# Arkiver e-mail i et arkiv?
+# Archive messages?
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 archive = 1
 
-# Skal arkivet v&aelig;re offentligt eller privat?
+# Is archive file source for public or private archival?
 #
-# gyldige værdier:
-#    0 = "Offentligt"
-#    1 = "Privat"
+# legal values are:
+#    0 = "public"
+#    1 = "private"
 archive_private = 0
 
-# Hvor ofte skal arkivet deles op?
+# How often should a new archive volume be started?
 #
-# gyldige værdier:
-#    0 = "&Aring;rlig"
-#    1 = "M&aring;nedlig"
-#    2 = "Kvartalsvis"
-#    3 = "Ugentlig"
-#    4 = "Daglig"
+# legal values are:
+#    0 = "Yearly"
+#    1 = "Monthly"
+#    2 = "Quarterly"
+#    3 = "Weekly"
+#    4 = "Daily"
 archive_volume_frequency = 2
 
 ## Gateway options
 #
-# E-mail-Til-Nyhedsgruppe og Nyhedsgruppe-Til-E-mail tjeneste.
+# Mail-to-News and News-to-Mail gateway services.
 
-# Nyhedsgruppe-tjeneste er ikke en del af Mailman. Du skal have adgang
-# til en eksisterende NNTP tjeneste, og maskinen som denne mailliste
-# k&oslash;rer p&aring; skal have adgang til at hente og afsende
-# meddelelser til NNTP tjenesten.
+# This value may be either the name of your news server, or optionally
+# of the format name:port, where port is a port number.
+# 
+# The news server is not part of Mailman proper.  You have to already
+# have access to an NNTP server, and that NNTP server must recognize the
+# machine this mailing list runs on as a machine capable of reading and
+# posting news.
 nntp_host = ''
 
-# Navn p&aring; nyhedsgruppe der skal sendes til og/eller fra.
+# The name of the Usenet group to gateway to and/or from.
 linked_newsgroup = ''
 
-# Skal nye meddelelser til denne liste sendes til nyhedsgruppen?
+# Should new posts to the mailing list be sent to the newsgroup?
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 gateway_to_news = 0
 
-# Skal nye meddelelser til nyhedsgruppen sendes til denne mailliste?
+# Should new posts to the newsgroup be sent to the mailing list?
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 gateway_to_mail = 0
 
-# Denne indstilling fort&aelig;ller Mailman hvilken slags
-# moderationsregler nyhedsgruppen har og hvordan de koordineres med
-# maillistens moderationsregler. Dette g&aelig;lder kun nyhedgrupper du
-# overfører meddelelser til, s&aring; hvis du kun overf&oslash;rer fra
-# en nyhedsgruppe, eller nyhedsgruppen du overf&oslash;rer til ikke er
-# modereret, s&aelig;ttes indstillingen til Ingen.
-# 
-# Hvis nyhedsgruppen er modereret, kan du s&aelig;tte maillisten til at
-# v&aelig;re moderationsadressen for nyhedsgruppen. Ved at vælge
-# Modereret, vil en ekstra meddelelse holdes tilbage i
-# godkendelsesprocessen. Al mail sendt til maillisten skal godkendes
-# f&oslash;r den sendes til nyhedsgruppen, eller til medlemmerne af
-# listen.
-# 
-# Vær opm&aelig;rksom p&aring; at hvis brevhovedet i mailen har et
-# Approved: felt med listens administrative adgangskode, vil denne regel
-# ikke blive benyttet. På den m&aring;de kan priviligerede afsendere
-# sende mail direkte til listen og nyhedsgruppen.
-# 
-# Hvis nyhedsgruppen er modereret, men du alligevel vil have en
-# &aring;ben liste, b&oslash;r du vælge Åben liste, modereret
-# nyhedsgruppe. S&aring; vil de s&aelig;dvanlige mekanismer for
-# moderation blive benyttet i Mailman, men alle meddelelser der sendes
-# til Usenet vil f&aring; et Approved felt i brevhovedet.
-#
-# gyldige værdier:
-#    0 = "Ingen"
-#    1 = "Åben liste, modereret nyhedsgruppe"
-#    2 = "Modereret"
+# This setting determines the moderation policy of the newsgroup and its
+# interaction with the moderation policy of the mailing list.  This only
+# applies to the newsgroup that you are gatewaying to, so if you are
+# only gatewaying from Usenet, or the newsgroup you are gatewaying to is
+# not moderated, set this option to None.
+# 
+# If the newsgroup is moderated, you can set this mailing list up to be
+# the moderation address for the newsgroup.  By selecting Moderated, an
+# additional posting hold will be placed in the approval process.  All
+# messages posted to the mailing list will have to be approved before
+# being sent on to the newsgroup, or to the mailing list membership.
+# 
+# Note that if the message has an Approved header with the list's
+# administrative password in it, this hold test will be bypassed,
+# allowing privileged posters to send messages directly to the list and
+# the newsgroup.
+# 
+# Finally, if the newsgroup is moderated, but you want to have an open
+# posting policy anyway, you should select Open list, moderated group.
+# The effect of this is to use the normal Mailman moderation facilities,
+# but to add an Approved header to all messages that are gatewayed to
+# Usenet.
+#
+# legal values are:
+#    0 = "None"
+#    1 = "Open list, moderated group"
+#    2 = "Moderated"
 news_moderation = 0
 
-# Mailman tilføjer normalt en tekst du selv kan tilrette (emne prefix)
-# foran emnefeltet i mail som sendes til listen, og normalt sker dette
-# også for mail som sendes videre til Usenet. Du kan sætte denne
-# indstilling til Nej hvis du ikke ønsker emne prefix tilføjet til mail
-# som sendes til Usenet. Sættes emne prefix for listen til off, vil
-# videresendte meddelelser heller ikke få prefix tilføjet.
+# Mailman prefixes Subject: headers with text you can customize and
+# normally, this prefix shows up in messages gatewayed to Usenet.  You
+# can set this option to No to disable the prefix on gated messages.  Of
+# course, if you turn off normal Subject: prefixes, they won't be
+# prefixed for gated messages either.
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 news_prefix_subject_too = 1
 
 ## Autoreply options
 #
-# Indstillinger for automatiske svar.<p>
+# Auto-responder characteristics.<p>
 # 
-# I tekstboksene nedenfor kan du bruge følgende variabler: (skriv:
-# %(&lt;variabelnavn&gt;)s ) for at indsætte ønsket information: <p><ul>
-# <li><b>listname</b> - <em>navnet p&aring; listen</em>
-# <li><b>listurl</b> - <em>URL til listens webside</em>
-# <li><b>requestemail</b> - <em>listens -request e-mailadresse</em>
-# <li><b>owneremail</b> - <em>listens -owner e-mailadresse</em> </ul>
+# In the text fields below, string interpolation is performed with the
+# following key/value substitutions: <p><ul> <li><b>listname</b> -
+# <em>gets the name of the mailing list</em> <li><b>listurl</b> -
+# <em>gets the list's listinfo URL</em> <li><b>requestemail</b> -
+# <em>gets the list's -request address</em> <li><b>owneremail</b> -
+# <em>gets the list's -owner address</em> </ul>
 # 
-# <p>Du kan enten skrive teksten direkte i tekstboksene, eller du kan
-# angive navnet p&aring; en fil som indeholder teksten. Denne fil vil
-# s&aring; blive indl&aelig;st i tekstboksen, fra dit lokale filsystem.
+# <p>For each text field, you can either enter the text directly into
+# the text box, or you can specify a file on your local system to upload
+# as the text.
 
-# Skal Mailman sende et automatisk svar til dem der sender e-mail til
-# listen?
+# Should Mailman send an auto-response to mailing list posters?
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 autorespond_postings = 0
 
-# Automatisk svar der skal sendes.
+# Auto-response text to send to mailing list posters.
 autoresponse_postings_text = ''
 
-# Skal Mailman sende et automatisk svar p&aring; e-mail der sendes til
-# -owner adressen?
+# Should Mailman send an auto-response to emails sent to the -owner
+# address?
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 autorespond_admin = 0
 
-# Automatisk svar p&aring; e-mail til -owner adressen.
+# Auto-response text to send to -owner emails.
 autoresponse_admin_text = ''
 
-# Skal Mailman sende et automatisk svar p&aring; e-mail der sendes til
-# -request adressen? Hvis du v&aelig;lger ja, kan du ogs&aring;
-# v&aelig;lge om e-mailen der blev sendt til -request adressen skal
-# medtages i det automatiske svar.
+# Should Mailman send an auto-response to emails sent to the -request
+# address?  If you choose yes, decide whether you want Mailman to
+# discard the original email, or forward it on to the system as a normal
+# mail command.
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja, men uden den originale e-mail"
-#    2 = "Ja, og medtag den originale e-mail"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes, w/discard"
+#    2 = "Yes, w/forward"
 autorespond_requests = 0
 
-# Automatisk svar p&aring; e-mail til -request adressen.
+# Auto-response text to send to -request emails.
 autoresponse_request_text = ''
 
-# Antal dage imellem automatisk svar p&aring; e-mail, fra samme
-# afsender, til listen eller til -request/-owner adresserne. S&aelig;t
-# denne v&aelig;rdi til 0 (eller et negativt tal) for at sende
-# automatisk svar hver gang.
+# Number of days between auto-responses to either the mailing list or
+# -request/-owner address from the same poster.  Set to zero (or
+# negative) for no grace period (i.e. auto-respond to every message).
 autoresponse_graceperiod = 90
 
 ## Contentfilter options
 #
-# Regler for indhold i e-mail sendt til listen.
-# 
-# <p>Filtrering af indhold fungerer således: når listen modtager en
-# e-mail og du har beskyttelse med filtrering af indhold aktiveret,
-# sammenlignes først eventuelle vedh&aelig;ftninger med <a
-# href="?VARHELP=contentfilter/filter_mime_types">MIME filtrene</a>.
-# Hvis en vedh&aelig;ftning passer med et af disse filtre, bliver
-# vedh&aelig;ftningen fjernet.
-# 
-# <p>Derefter sammenlignes eventuelle vedh&aelig;ftninger med <a
-# href="?VARHELP=contentfilter/pass_mime_types">gyldige MIME typer</a>,
-# hvis nogen er defineret. Alle vedh&aelig;ftninger som ikke stemmer
-# overens med de angivne MIME typer, bliver fjernet.
-# 
-# <p>Efter filtreringen vil alle tomme <tt>multipart</tt>
-# vedh&aelig;ftninger v&aelig;re fjernet. Hvis selve meddelelsen er helt
-# tom efter denne filtrering, vil meddelelsen blive afvist. Derefter vil
-# enhver <tt>multipart/alternative</tt> vedh&aelig;ftning blive
-# erstattet af den første alternative som ikke er tom.
-# 
-# <p>Til sidst vil alle <tt>text/html</tt> vedh&aelig;ftninger som måtte
-# v&aelig;re tilbage i meddelelsen blive konverteret til
-# <tt>text/plain</tt> hvis <a
-# href="?VARHELP=contentfilter/convert_html_to_plaintext">konverter til
-# ren tekst</a> er sat til og serveren er konfigureret til at tillade
-# sådanne konverteringer.
-
-# Skal Mailman filtrere indhold i e-mail sendt til listen som angivet
-# nedenfor?
-#
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# Policies concerning the content of list traffic.
+# 
+# <p>Content filtering works like this: when a message is received by
+# the list and you have enabled content filtering, the individual
+# attachments are first compared to the <a
+# href="?VARHELP=contentfilter/filter_mime_types">filter types</a>.  If
+# the attachment type matches an entry in the filter types, it is
+# discarded.
+# 
+# <p>Then, if there are <a
+# href="?VARHELP=contentfilter/pass_mime_types">pass types</a> defined,
+# any attachment type that does <em>not</em> match a pass type is also
+# discarded.  If there are no pass types defined, this check is skipped.
+# 
+# <p>After this initial filtering, any <tt>multipart</tt> attachments
+# that are empty are removed.  If the outer message is left empty after
+# this filtering, then the whole message is discarded.
+# 
+# <p> Then, each <tt>multipart/alternative</tt> section will be replaced
+# by just the first alternative that is non-empty after filtering if <a
+# href="?VARHELP=contentfilter/collapse_alternatives"
+# >collapse_alternatives</a> is enabled.
+# 
+# <p>Finally, any <tt>text/html</tt> parts that are left in the message
+# may be converted to <tt>text/plain</tt> if <a
+# href="?VARHELP=contentfilter/convert_html_to_plaintext"
+# >convert_html_to_plaintext</a> is enabled and the site is configured
+# to allow these conversions.
+
+# Should Mailman filter the content of list traffic according to the
+# settings below?
+#
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 filter_content = 0
 
-# Brug denne indstilling til at fjerne vedh&aelig;ftninger der passer
-# til MIME typer. Hver linie skal her indeholde navnet på en MIME
-# type/subtype, f.eks. image/gif. Hvis du ønsker at fjerne alle
-# vedh&aelig;ftninger som har en given hoved MIME type, kan du undlade
-# at angive subtype, f.eks. image.
+# Use this option to remove each message attachment that matches one of
+# these content types.  Each line should contain a string naming a MIME
+# type/subtype, e.g. image/gif.  Leave off the subtype to remove all
+# parts with a matching major content type, e.g. image.
 # 
-# Tomme linier medtages ikke.
+# Blank lines are ignored.
 # 
-# Se også gyldige MIME typer for whitelist af MIME typer.
+# See also <a href="?VARHELP=contentfilter/pass_mime_types"
+# >pass_mime_types for a content type whitelist.
 filter_mime_types = ''
 
-# Brug denne indstilling for at definere hvilke MIME typer der skal være
-# tilladt. Krav og format for filtrering er identisk med MIME filtre.
+# Use this option to remove each message attachment that does not have a
+# matching content type.  Requirements and formats are exactly like <a
+# href="?VARHELP=contentfilter/filter_mime_types" >filter_mime_types.
 # 
-# Bem&aelig;rk: hvis du lægger noget ind her, men ikke angiver
-# multipart, vil ingen e-mail med vedh&aelig;ftninger blive medtaget.
+# Note: if you add entries to this list but don't add multipart to this
+# list, any messages with attachments will be rejected by the pass
+# filter.
 pass_mime_types = """multipart/mixed
 multipart/alternative
 text/plain"""
 
-# Skal Mailman konvertere text/html dele til ren tekst? Denne
-# konvertering vil finde sted efter at MIME filteret har fjernet de
-# uønskede dele.
+# Remove message attachments that have a matching filename extension.
+filter_filename_extensions = """exe
+bat
+cmd
+com
+pif
+scr
+vbs
+cpl"""
+
+# Remove message attachments that don't have a matching filename
+# extension.  Leave this field blank to skip this filter test.
+pass_filename_extensions = ''
+
+# Should Mailman collapse multipart/alternative to its first part
+# content?
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
+collapse_alternatives = True
+
+# Should Mailman convert text/html parts to plain text?  This conversion
+# happens after MIME attachments have been stripped.
+#
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 convert_html_to_plaintext = 1
 
-# Her bestemmer du hvad der skal ske, når en meddelelse filtreres fra af
-# et filter, altså hvis vedh&aelig;ftningen filtreres fra af MIME
-# filteret, eller en vedh&aelig;ftning ikke har en af de gyldige MIME
-# typer, eller meddelelsen ender med at være tom efter filtrering.
-# 
-# Bemærk at det du vælger her ikke vil ske hvis en meddelelse stadig
-# indeholder noget efter filtrering. Så vil meddelelsen altid blive
-# sendt videre til listen.
-# 
-# Når meddelelsen afvises, skrives Message-ID for den afviste meddelelse
-# til loggen. Når meddelelsen sendes retur eller videresendes til
-# listens ejer, vil en begrundelse altid blive inkluderet i den
-# returmail der sendes til afsenderen. Når meddelelserne skal bevares,
-# gemmes de i et specielt køkatalog på disken, sådan at
-# serveradministrator kan se (og måske gøre noget med) dem, men bliver
-# ellers fjernet. Dette sidste valg er kun tilgængeligt hvis
-# serveradministrator har tilladt det.
-#
-# gyldige værdier:
-#    0 = "Slet"
-#    1 = "Afvis"
-#    2 = "Videresend til Listens Ejer"
-#    3 = "Bevar"
+# One of these actions is taken when the message matches one of the
+# content filtering rules, meaning, the top-level content type matches
+# one of the <a href="?VARHELP=contentfilter/filter_mime_types"
+# >filter_mime_types, or the top-level content type does not match one
+# of the <a href="?VARHELP=contentfilter/pass_mime_types"
+# >pass_mime_types, or if after filtering the subparts of the message,
+# the message ends up empty.
+# 
+# Note this action is not taken if after filtering the message still
+# contains content.  In that case the message is always forwarded on to
+# the list membership.
+# 
+# When messages are discarded, a log entry is written containing the
+# Message-ID of the discarded message.  When messages are rejected or
+# forwarded to the list owner, a reason for the rejection is included in
+# the bounce message to the original author.  When messages are
+# preserved, they are saved in a special queue directory on disk for the
+# site administrator to view (and possibly rescue) but otherwise
+# discarded.  This last option is only available if enabled by the site
+# administrator.
+#
+# legal values are:
+#    0 = "Discard"
+#    1 = "Reject"
+#    2 = "Forward to List Owner"
+#    3 = "Preserve"
 filter_action = 0
 
 ## Topics options
 #
-# Emneord for listen
-
-# Emnefilteret kategoriserer hver e-mail som kommer til listen, efter de
-# regexp-udtryk du skriver nedenfor. Hvis felterne Subject: eller
-# Keywords: i brevhovedet i en mail stemmer overens med et af disse
-# udtryk, bliver mailen placeret under det p&aring;g&aelig;ldende emne.
-# Hvert medlem af listen kan vælge kun at modtage mail der passer til de
-# &oslash;nskede emner. E-mail som ikke h&oslash;rer under noget emne,
-# bliver ikke leveret.
-# 
-# Bem&aeligrk: Dette fungerer kun i normal-modus, ikke i
-# sammendrag-modus.
-# 
-# Indholdet i meddelelsen kan ogs&aring; unders&oslash;ges for Subject:
-# og Keyword: felter, alt efter hvad indstillingen
-# topics_bodylines_limit er sat til.
+# List topic keywords
+
+# The topic filter categorizes each incoming email message according to
+# <a href="http://www.python.org/doc/current/lib/module-re.html">regular
+# expression filters you specify below.  If the message's Subject: or
+# Keywords: header contains a match against a topic filter, the message
+# is logically placed into a topic bucket.  Each user can then choose to
+# only receive messages from the mailing list for a particular topic
+# bucket (or buckets).  Any message not categorized in a topic bucket
+# registered with the user is not delivered to the list.
+# 
+# Note that this feature only works with regular delivery, not digest
+# delivery.
+# 
+# The body of the message can also be optionally scanned for Subject:
+# and Keywords: headers, as specified by the <a
+# href="?VARHELP=topics/topics_bodylines_limit">topics_bodylines_limit
+# configuration variable.
 #
-# gyldige værdier:
-#    0 = "Ikke tilgængeligt"
-#    1 = "Tilgængeligt"
+# legal values are:
+#    0 = "Disabled"
+#    1 = "Enabled"
 topics_enabled = 0
 
-# Her angiver du hvor mange linier af mailens indhold emnefilteret skal
-# gennems&oslash;ge. En s&oslash;gning stopper n&aring;r det antal
-# linier er gennems&oslash;gt, eller n&aring;r den m&oslash;der en linie
-# som ikke ligner et brevhoved-felt. S&aelig;ttes denne v&aelig;rdi til
-# nul (0), vil ingen linier i indholdet blive unders&oslash;gt (dvs. kun
-# Keywords: og Subject: i brevhovedet unders&oslash;ges). S&aelig;ttes
-# denne v&aelig;rdi til et negativt tal, vil alle linier blive
-# unders&oslash;gt frem til den f&oslash;rste linie som ikke ligner et
-# brevhoved-felt.
+# The topic matcher will scan this many lines of the message body
+# looking for topic keyword matches.  Body scanning stops when either
+# this many lines have been looked at, or a non-header-like body line is
+# encountered.  By setting this value to zero, no body lines will be
+# scanned (i.e. only the Keywords: and Subject: headers will be
+# scanned).  By setting this value to a negative number, then all body
+# lines will be scanned until a non-header-like line is encountered.
+# 
 topics_bodylines_limit = 5
 
-# Hvert emneord er faktisk et regexp-udtryk, der sammenlignes med dele
-# af mailen, nemlig felterne Keywords: og Subject: i brevhovedet.
-# Bem&aelig;rk at de f&oslash;rste linier i mailens indhold ogs&aring;
-# kan best&aring; af s&aring;danne "felter", og de kan dermed ogs&aring;
-# blive unders&oslash;gt.
+# Each topic keyword is actually a regular expression, which is matched
+# against certain parts of a mail message, specifically the Keywords:
+# and Subject: message headers. Note that the first few lines of the
+# body of the message can also contain a Keywords: and Subject: "header"
+# on which matching is also performed.
 topics = []
 
diff --git a/mailman/vigtigt.members b/mailman/vigtigt.members
index 79d4203..f191210 100644
--- a/mailman/vigtigt.members
+++ b/mailman/vigtigt.members
@@ -6,3 +6,4 @@ Niels Th?gersen <niels.thoegersen@munksoegaard.dk>
 Per Helmer Roos <per_roos@munksoegaard.dk>
 Siri Reiter <siri_snell_reiter@munksoegaard.dk>
 S?ren Magnusson <soeren_magnusson@munksoegaard.dk>
+S?ren Magnusson <soren@magnussons.dk>
diff --git a/mailman/vigtigt.py b/mailman/vigtigt.py
index d6e36d3..73f0792 100644
--- a/mailman/vigtigt.py
+++ b/mailman/vigtigt.py
@@ -1,5 +1,7 @@
-## Indstillinger for maillisten "vigtigt"  -*- python -*-
-## Dato: Sun Dec 11 16:36:13 2005
+# -*- python -*-
+# -*- coding: iso-8859-1 -*-
+## "vigtigt" mailing list configuration settings
+## captured on Tue Mar 20 08:52:48 2007
 
 ## General options
 #
@@ -76,11 +78,15 @@ info = """&Aring;ben liste til vigtige informationer om Olinesgaard.
  * Alle kan tilmelde sig listen.
  * Medlemmer af Olineg&aring;rdforeningen tilmeldes som standard."""
 
-# This text will be prepended to subject lines of messages posted to the
-# list, to distinguish mailing list messages in in mailbox summaries.
-# Brevity is premium here, it's ok to shorten long mailing list names to
-# something more concise, as long as it still identifies the mailing
-# list.
+# Denne tekst vil blive placeret foran emnet i mails sendt til listen
+# for nemmere og kunne skelne mail fra listen i indboksen i
+# postprogrammet. Teksten b&oslash;r holdes kort. Det er iorden og
+# sk&aelig;re et langt listenavn ned til et mere kortfattet navn
+# s&aring;l&aelig;nge det stadig er beskrivende for listen. Du kan
+# ogs&aring; tilf&oslash;je et fortl&oslash;bende nummer ved at bruge %d
+# substitutions direktivet f.eks. [listenavn %d] -> [listenavn 123]
+# (listenavn %05d) -> (listenavn 00123)
+# 
 subject_prefix = '[Oline vigtigt] '
 
 # Skjul afsenderen af meddelelser, ved at erstatte den med e-maillistens
@@ -101,31 +107,32 @@ anonymous_list = False
 #    1 = "Ja"
 first_strip_reply_to = False
 
-# Denne indstillling fort&aelig;ller hvad Mailman skal g&oslash;re med
-# Reply-To: feltet i brevhovedet p&aring; e-mail der sendes til listen.
-# Hvis den er sat til Afsender, vil Mailman ikke tilf&oslash;je noget
-# Reply-To: felt, men findes et s&aring;dant felt allerede, vil det ikke
-# blive fjernet. S&aelig;ttes indstillingen til enten e-maillistens
-# adresse eller Egendefineret adresse, vil Mailman tilf&oslash;je, evt.
-# erstatte, et Reply-To: felt. (Egendefineret adresse inds&aelig;tter
-# v&aelig;rdien af indstillingen reply_to_address).
-# 
-# Der er flere grunde til ikke at indf&oslash;re eller erstatte
-# Reply-To: felter. En grund kan v&aelig;re at nogen af dem der sender
-# mail til listen er afh&aelig;ngige af selv at kunne s&aelig;tte
-# Reply-To: adressen. En anden grund er at modifikation af Reply-To:
-# adressen g&oslash;r det vanskeligere kun at sende svar til afsender.
-# Se 'Reply-To' Munging Considered Harmful for en diskussion omkring
-# emnet. Se Reply-To Munging Considered Useful for modsatte meninger.
-# 
-# Nogle maillister har begr&aelig;nset adgang, med en parallel liste
-# beregnet til diskussioner. Eksempler p&aring; dette er 'patches' eller
-# 'checkin' lister, som system for revisionskontrol sender
-# &aelig;ndringer i programmet til, men diskussioner omkring udvikling
-# af programmet sendes til udviklernes egen mailliste. For at
-# underst&oslash;tte lignende e-maillister, v&aelig;lg Egendefineret
-# adresse og s&aelig;t Reply-To: adressen i indstillingen
-# reply_to_address til at pege på den parallelle diskussionsliste.
+# This option controls what Mailman does to the Reply-To: header in
+# messages flowing through this mailing list.  When set to Poster, no
+# Reply-To: header is added by Mailman, although if one is present in
+# the original message, it is not stripped.  Setting this value to
+# either This list or Explicit address causes Mailman to insert a
+# specific Reply-To: header in all messages, overriding the header in
+# the original message if necessary (Explicit address inserts the value
+# of <a href="?VARHELP=general/reply_to_address">reply_to_address).
+# 
+# There are many reasons not to introduce or override the Reply-To:
+# header.  One is that some posters depend on their own Reply-To:
+# settings to convey their valid return address.  Another is that
+# modifying Reply-To: makes it much more difficult to send private
+# replies.  See <a
+# href="http://www.unicom.com/pw/reply-to-harmful.html">`Reply-To'
+# Munging Considered Harmful for a general discussion of this issue.
+# See <a
+# href="http://www.metasystema.net/essays/reply-to.mhtml">Reply-To
+# Munging Considered Useful for a dissenting opinion.
+# 
+# Some mailing lists have restricted posting privileges, with a parallel
+# list devoted to discussions.  Examples are `patches' or `checkin'
+# lists, where software changes are posted by a revision control system,
+# but discussion about the changes occurs on a developers mailing list.
+# To support these types of mailing lists, select Explicit address and
+# set the Reply-To: address below to point to the parallel list.
 #
 # gyldige værdier:
 #    0 = "Afsender"
@@ -133,29 +140,31 @@ first_strip_reply_to = False
 #    2 = "Egendefineret adresse"
 reply_goes_to_list = 0
 
-# Her definerer du adressen der skal s&aelig;ttes i Reply-To: feltet
-# n&aring;r indstillingen reply_goes_to_list er sat til Egendefineret
-# adresse.
-# 
-# Der findes mange grunde til at ikke indf&oslash;re eller erstatte
-# Reply-To: felter. En grund kan v&aelig;re at nogen af dem der sender
-# e-mail til listen er afh&aelig;ngige af selv at kunne s&aelig;tte
-# Reply-To: adressen. En anden grund er at modificering af Reply-To:
-# adressen g&oslash;r det vanskeligere at sende svar kun til afsender.
-# Se 'Reply-To' Munging Considered Harmful for en diskussion omkring
-# temaet. Se Reply-To Munging Considered Useful for modsatte meninger.
-# 
-# Nogle maillister har begr&aelig;nset adgang, med en egen parallel
-# liste beregnet for diskussioner. Eksempler p&aring; dette er 'patches'
-# eller 'checkin' lister, som system for revisionskontrol sender
-# &aelig;ndringer i programmet til, mens diskussioner omkring udvikling
-# af programmet sendes til udviklernes egen mailliste. For at
-# underst&oslash;tte s&aring;danne maillister, kan du definere Reply-To:
-# adressen her, og vælge Egendefineret adresse i indstillingen
-# reply_goes_to_list.
-# 
-# Bem&aelig;rk at hvis den oprindelige meddelelse indeholder et
-# Reply-To: felt, vil det ikke &aelig;ndres.
+# This is the address set in the Reply-To: header when the <a
+# href="?VARHELP=general/reply_goes_to_list">reply_goes_to_list option
+# is set to Explicit address.
+# 
+# There are many reasons not to introduce or override the Reply-To:
+# header.  One is that some posters depend on their own Reply-To:
+# settings to convey their valid return address.  Another is that
+# modifying Reply-To: makes it much more difficult to send private
+# replies.  See <a
+# href="http://www.unicom.com/pw/reply-to-harmful.html">`Reply-To'
+# Munging Considered Harmful for a general discussion of this issue.
+# See <a
+# href="http://www.metasystema.net/essays/reply-to.mhtml">Reply-To
+# Munging Considered Useful for a dissenting opinion.
+# 
+# Some mailing lists have restricted posting privileges, with a parallel
+# list devoted to discussions.  Examples are `patches' or `checkin'
+# lists, where software changes are posted by a revision control system,
+# but discussion about the changes occurs on a developers mailing list.
+# To support these types of mailing lists, specify the explicit
+# Reply-To: address here.  You must also specify Explicit address in the
+# reply_goes_to_list variable.
+# 
+# Note that if the original message contains a Reply-To: header, it will
+# not be changed.
 reply_to_address = ''
 
 # V&aelig;lg kun 'ja' her, hvis listen skal bruges som  "paraply" for
@@ -253,9 +262,8 @@ admin_immed_notify = True
 #    1 = "Ja"
 admin_notify_mchanges = False
 
-# Approval notices are sent when mail triggers certain of the limits
-# except routine list moderation and spam filters, for which notices are
-# not sent.  This option overrides ever sending the notice.
+# Send e-mail til afsendere n&aring;r deres e-mail til listen holdes
+# tilbage for godkendelse?
 #
 # gyldige værdier:
 #    0 = "Nej"
@@ -333,6 +341,10 @@ include_rfc2369_headers = 1
 #    1 = "Ja"
 include_list_post_header = 1
 
+# Slet alle tilbageholdte beskeder der er ældre end dette antal dage.
+# Brug 0 for at slå automatisk sletning fra.
+max_days_to_hold = 0
+
 ## Language options
 #
 # Underst&oslash;ttelse af flere sprog. (Internationalisering)
@@ -386,59 +398,57 @@ encode_ascii_prefixes = 2
 nondigestable = True
 
 # Tekst der tilføjes &oslash;verst i e-mail der sendes til listens
-# medlemmer. Teksten kan inneholde formateringskoder som byttes ut med
-# verdier fra listens oppsett. For detaljer, se Pythons
+# medlemmer. Teksten kan indeholde formateringskoder som udskiftes med
+# v&aelig;rdier fra listens ops&aelig;tning. For detaljer, se Pythons
 # formateringsregler (engelsk). Gyldige koder er:
 # 
 # 
 # real_name - Listens formaterede navn; normalt listenavnet med stort
 # forbogstav eller store bogstaver enkelte steder.
 # 
-# list_name - Listens navn som brugt i URLer, der det har betydning om
+# list_name - Listens navn som brugt i URLer, hvor det har betydning om
 # den staves med store eller sm&aring; bogstaver. (For
 # bagudkompatibilitet, er _internal_name det samme.)
 # 
-# host_name - Internetadressen (fully qulified domain name) til maskinen
-# som listeserveren g&aring;r p&aring;.
+# host_name - Internetadressen (fully qualified domain name) til
+# maskinen som listeserveren k&oslash;rer p&aring;.
 # 
-# web_page_url - Basis URL for Mailman. Denne kan laegges til sammen
-# med, f.eks. listinfo/%(internal_name)s for &aring; danne URLen til en
-# listes infoside.
+# web_page_url - Basis URL for Mailman. Denne kan kombineres med f.eks.
+# listinfo/%(list_name)s for at danne URLen til en listes infoside.
 # 
 # description - En kort beskrivelse af listen.
 # 
-# info - Full beskrivelse af listen.
+# info - Fuld beskrivelse af listen.
 # 
-# cgiext - Tillaeg som laegges til CGI scripts.
+# cgiext - Extension som tilf&oslash;jes CGI scripts.
 # 
 # 
 msg_header = ''
 
 # Tekst som tilf&oslash;jes nederst i e-mail der sendes til listens
-# medlemmer. Teksten kan inneholde formateringskoder som byttes ut med
-# verdier fra listens oppsett. For detaljer, se Pythons
+# medlemmer. Teksten kan indeholde formateringskoder som udskiftes med
+# v&aelig;rdier fra listens ops&aelig;tning. For detaljer, se Pythons
 # formateringsregler (engelsk). Gyldige koder er:
 # 
 # 
 # real_name - Listens formaterede navn; normalt listenavnet med stort
 # forbogstav eller store bogstaver enkelte steder.
 # 
-# list_name - Listens navn som brugt i URLer, der det har betydning om
+# list_name - Listens navn som brugt i URLer, hvor det har betydning om
 # den staves med store eller sm&aring; bogstaver. (For
 # bagudkompatibilitet, er _internal_name det samme.)
 # 
-# host_name - Internetadressen (fully qulified domain name) til maskinen
-# som listeserveren g&aring;r p&aring;.
+# host_name - Internetadressen (fully qualified domain name) til
+# maskinen som listeserveren k&oslash;rer p&aring;.
 # 
-# web_page_url - Basis URL for Mailman. Denne kan laegges til sammen
-# med, f.eks. listinfo/%(internal_name)s for &aring; danne URLen til en
-# listes infoside.
+# web_page_url - Basis URL for Mailman. Denne kan kombineres med f.eks.
+# listinfo/%(list_name)s for at danne URLen til en listes infoside.
 # 
 # description - En kort beskrivelse af listen.
 # 
-# info - Full beskrivelse af listen.
+# info - Fuld beskrivelse af listen.
 # 
-# cgiext - Tillaeg som laegges til CGI scripts.
+# cgiext - Extension som tilf&oslash;jes CGI scripts.
 # 
 # 
 msg_footer = """-- 
@@ -446,6 +456,17 @@ msg_footer = """--
 %(real_name)s@%(host_name)s
 %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s"""
 
+# Når du fjerner vedh&aelig;ftninger, gemmes de i et arkiv område og der
+# laves istedet links i e-mailen således at medlemmer kan tilgå
+# vedh&aelig;ftninger via en webbrowser. Hvis du vil have
+# vedh&aelig;ftninger til helt og forsvinde så kan du bruge et
+# indholdsfilter.
+#
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
+scrub_nondigest = False
+
 ## Digest options
 #
 # Opsætning af sammendrag-modus.
@@ -484,59 +505,57 @@ digest_size_threshhold = 300
 digest_send_periodic = True
 
 # Tekst som tilf&oslash;jes &oslash;verst i samle-emailen, f&oslash;r
-# indholdsfortegnelsen.Teksten kan inneholde formateringskoder som
-# byttes ut med verdier fra listens oppsett. For detaljer, se Pythons
-# formateringsregler (engelsk). Gyldige koder er:
+# indholdsfortegnelsen.Teksten kan indeholde formateringskoder som
+# udskiftes med v&aelig;rdier fra listens ops&aelig;tning. For detaljer,
+# se Pythons formateringsregler (engelsk). Gyldige koder er:
 # 
 # 
 # real_name - Listens formaterede navn; normalt listenavnet med stort
 # forbogstav eller store bogstaver enkelte steder.
 # 
-# list_name - Listens navn som brugt i URLer, der det har betydning om
+# list_name - Listens navn som brugt i URLer, hvor det har betydning om
 # den staves med store eller sm&aring; bogstaver. (For
 # bagudkompatibilitet, er _internal_name det samme.)
 # 
-# host_name - Internetadressen (fully qulified domain name) til maskinen
-# som listeserveren g&aring;r p&aring;.
+# host_name - Internetadressen (fully qualified domain name) til
+# maskinen som listeserveren k&oslash;rer p&aring;.
 # 
-# web_page_url - Basis URL for Mailman. Denne kan laegges til sammen
-# med, f.eks. listinfo/%(internal_name)s for &aring; danne URLen til en
-# listes infoside.
+# web_page_url - Basis URL for Mailman. Denne kan kombineres med f.eks.
+# listinfo/%(list_name)s for at danne URLen til en listes infoside.
 # 
 # description - En kort beskrivelse af listen.
 # 
-# info - Full beskrivelse af listen.
+# info - Fuld beskrivelse af listen.
 # 
-# cgiext - Tillaeg som laegges til CGI scripts.
+# cgiext - Extension som tilf&oslash;jes CGI scripts.
 # 
 # 
 digest_header = ''
 
 # Tekst der tilføjes nederst i hver samle-email, som sidste
-# information.Teksten kan inneholde formateringskoder som byttes ut med
-# verdier fra listens oppsett. For detaljer, se Pythons
+# information.Teksten kan indeholde formateringskoder som udskiftes med
+# v&aelig;rdier fra listens ops&aelig;tning. For detaljer, se Pythons
 # formateringsregler (engelsk). Gyldige koder er:
 # 
 # 
 # real_name - Listens formaterede navn; normalt listenavnet med stort
 # forbogstav eller store bogstaver enkelte steder.
 # 
-# list_name - Listens navn som brugt i URLer, der det har betydning om
+# list_name - Listens navn som brugt i URLer, hvor det har betydning om
 # den staves med store eller sm&aring; bogstaver. (For
 # bagudkompatibilitet, er _internal_name det samme.)
 # 
-# host_name - Internetadressen (fully qulified domain name) til maskinen
-# som listeserveren g&aring;r p&aring;.
+# host_name - Internetadressen (fully qualified domain name) til
+# maskinen som listeserveren k&oslash;rer p&aring;.
 # 
-# web_page_url - Basis URL for Mailman. Denne kan laegges til sammen
-# med, f.eks. listinfo/%(internal_name)s for &aring; danne URLen til en
-# listes infoside.
+# web_page_url - Basis URL for Mailman. Denne kan kombineres med f.eks.
+# listinfo/%(list_name)s for at danne URLen til en listes infoside.
 # 
 # description - En kort beskrivelse af listen.
 # 
-# info - Full beskrivelse af listen.
+# info - Fuld beskrivelse af listen.
 # 
-# cgiext - Tillaeg som laegges til CGI scripts.
+# cgiext - Extension som tilf&oslash;jes CGI scripts.
 # 
 # 
 digest_footer = """-- 
@@ -759,6 +778,12 @@ generic_nonmember_action = 0
 #    1 = "Ja"
 forward_auto_discards = 1
 
+# Tekst der skal inkluderes i en meddelelse om afvisning der sendes til
+# ikke-medlemmer der poster til listen. Denne meddelelse kan inkludere
+# listeejerens adresse vha. %(listowner)s og den erstatter den
+# automatisk konstruerede standard meddelelse.
+nonmember_rejection_notice = ''
+
 ## Privacy options
 #
 # Her kan du ops&aelig;tte filtrering baseret på modtageren af
@@ -816,15 +841,22 @@ max_num_recipients = 10
 # Her kan du opsætte forskellige anti-spam filtre, som kan bidrage til
 # at reducere mængden af spam der distribueres via e-maillisten.
 
-# Each header filter rule has two parts, a list of regular expressions,
-# one per line, and an action to take.  Mailman matches the message's
-# headers against every regular expression in the rule and if any match,
-# the message is rejected, held, or discarded based on the action you
-# specify.  Use Defer to temporarily disable a rule.
-# 
-# You can have more than one filter rule for your list.  In that case,
-# each rule is matched in turn, with processing stopped after the first
-# match.
+# Hver filterregel best&aring;r af to dele: en liste med regexp-udtryk,
+# et pr. linie, og en aktion der skal udf&oslash;res. Mailman
+# sammenligner meddelelsens brevhoved med alle regexp-udtryk i reglen,
+# og hvis der er overensstemmelse, vil meddelelsen blive afvist,
+# tilbageholdt eller slettet, afh&aelig;ngigt af hvilken aktion du har
+# angivet her. Brug Afvent for midlertidigt at s&aelig;tte en regel ud
+# af kraft.
+# 
+# Du kan have flere end en regel for din liste.  I s&aring; fald vil
+# hver regel blive anvendt efter tur, og processen stopper f&oslash;rste
+# gang der findes overensstemmelse.
+# 
+# Bemærk at brevhovedlinier indsamles fra alle vedh&aelig;ftninger
+# (undtagen fra mailman administrivia meddelelser) og sammenlignes med
+# regexp-udtrykkene. Ved brug af denne funktionalitet kan du effektivt
+# sortere meddelelser fra med farlige filtyper eller filnavn-endelser.
 header_filter_rules = []
 
 # Brug denne indstilling til at bortfiltrere mail til listen, baseret
@@ -1131,32 +1163,34 @@ autoresponse_graceperiod = 90
 
 ## Contentfilter options
 #
-# Regler for indhold i e-mail sendt til listen.
-# 
-# <p>Filtrering af indhold fungerer således: når listen modtager en
-# e-mail og du har beskyttelse med filtrering af indhold aktiveret,
-# sammenlignes først eventuelle vedh&aelig;ftninger med <a
-# href="?VARHELP=contentfilter/filter_mime_types">MIME filtrene</a>.
-# Hvis en vedh&aelig;ftning passer med et af disse filtre, bliver
-# vedh&aelig;ftningen fjernet.
-# 
-# <p>Derefter sammenlignes eventuelle vedh&aelig;ftninger med <a
-# href="?VARHELP=contentfilter/pass_mime_types">gyldige MIME typer</a>,
-# hvis nogen er defineret. Alle vedh&aelig;ftninger som ikke stemmer
-# overens med de angivne MIME typer, bliver fjernet.
-# 
-# <p>Efter filtreringen vil alle tomme <tt>multipart</tt>
-# vedh&aelig;ftninger v&aelig;re fjernet. Hvis selve meddelelsen er helt
-# tom efter denne filtrering, vil meddelelsen blive afvist. Derefter vil
-# enhver <tt>multipart/alternative</tt> vedh&aelig;ftning blive
-# erstattet af den første alternative som ikke er tom.
-# 
-# <p>Til sidst vil alle <tt>text/html</tt> vedh&aelig;ftninger som måtte
-# v&aelig;re tilbage i meddelelsen blive konverteret til
-# <tt>text/plain</tt> hvis <a
-# href="?VARHELP=contentfilter/convert_html_to_plaintext">konverter til
-# ren tekst</a> er sat til og serveren er konfigureret til at tillade
-# sådanne konverteringer.
+# Policies concerning the content of list traffic.
+# 
+# <p>Content filtering works like this: when a message is received by
+# the list and you have enabled content filtering, the individual
+# attachments are first compared to the <a
+# href="?VARHELP=contentfilter/filter_mime_types">filter types</a>.  If
+# the attachment type matches an entry in the filter types, it is
+# discarded.
+# 
+# <p>Then, if there are <a
+# href="?VARHELP=contentfilter/pass_mime_types">pass types</a> defined,
+# any attachment type that does <em>not</em> match a pass type is also
+# discarded.  If there are no pass types defined, this check is skipped.
+# 
+# <p>After this initial filtering, any <tt>multipart</tt> attachments
+# that are empty are removed.  If the outer message is left empty after
+# this filtering, then the whole message is discarded.
+# 
+# <p> Then, each <tt>multipart/alternative</tt> section will be replaced
+# by just the first alternative that is non-empty after filtering if <a
+# href="?VARHELP=contentfilter/collapse_alternatives"
+# >collapse_alternatives</a> is enabled.
+# 
+# <p>Finally, any <tt>text/html</tt> parts that are left in the message
+# may be converted to <tt>text/plain</tt> if <a
+# href="?VARHELP=contentfilter/convert_html_to_plaintext"
+# >convert_html_to_plaintext</a> is enabled and the site is configured
+# to allow these conversions.
 
 # Skal Mailman filtrere indhold i e-mail sendt til listen som angivet
 # nedenfor?
@@ -1186,6 +1220,28 @@ pass_mime_types = """multipart/mixed
 multipart/alternative
 text/plain"""
 
+# Fjern e-mailvedh&aelig;ftninger med passende filnavn-endelser.
+filter_filename_extensions = """exe
+bat
+cmd
+com
+pif
+scr
+vbs
+cpl"""
+
+# Fjern alle vedh&aelig;ftninger der ikke har en passende
+# filnavn-endelse. Lad dette felt være tomt for at udelade dette filter.
+pass_filename_extensions = ''
+
+# Should Mailman collapse multipart/alternative to its first part
+# content?
+#
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
+collapse_alternatives = True
+
 # Skal Mailman konvertere text/html dele til ren tekst? Denne
 # konvertering vil finde sted efter at MIME filteret har fjernet de
 # uønskede dele.
diff --git a/mailman/wikifans.members b/mailman/wikifans.members
index 82d118a..45d47b6 100644
--- a/mailman/wikifans.members
+++ b/mailman/wikifans.members
@@ -1,7 +1,6 @@
 a-tange@ofir.dk
 Anders Enslev Jensen <anders.enslev.jensen@skolekom.dk>
 Charlotte Drud <cdrud@wanadoo.dk>
-Jonas Smedegaard <dr@jones.dk>
 Chris Druid <druid@kth.se>
 Espen Sivertsen <espen@kaospilot.dk>
 Finn <finowitz@mail.dk>
diff --git a/mailman/wikifans.py b/mailman/wikifans.py
index ffbe804..e34ccf8 100644
--- a/mailman/wikifans.py
+++ b/mailman/wikifans.py
@@ -1,73 +1,69 @@
-## Indstillinger for maillisten "wikifans"  -*- python -*-
-## Dato: Sun Dec 11 16:36:15 2005
+# -*- python -*-
+# -*- coding: us-ascii -*-
+## "wikifans" mailing list configuration settings
+## captured on Tue Mar 20 08:52:53 2007
 
 ## General options
 #
-# Grundlæggende egenskaber for listen, herunder en beskrivelse af
-# listen. 
-
-# Du kan f.eks. stave navnet med stort forbogstav eller ændre andre
-# bogstaver til store, s&aring; navnet bliver udtalt rigtigt eller at
-# forkortelser fremhæves. Bemærk at dette navn bruges i e-maillistens
-# adresse (f.eks. i bekræftelser ved tilmeldinger), s&aring; navnet kan
-# ikke ændres p&aring; nogen anden m&aring;de. (e-mailadresser er ikke
-# f&oslash;lsomme for store eller sm&aring; bogstaver, men de er
-# f&oslash;lsomme for n&aelig;sten alt andet :-)
+# Fundamental list characteristics, including descriptive info and basic
+# behaviors.
+
+# The capitalization of this name can be changed to make it presentable
+# in polite company as a proper noun, or to make an acronym part all
+# upper case, etc.  However, the name will be advertised as the email
+# address (e.g., in subscribe confirmation notices), so it should not be
+# otherwise altered.  (Email addresses are not case sensitive, but they
+# are sensitive to almost everything else :-)
 real_name = 'WikiFans'
 
-# Der er to roller forbundet med hver mailliste. Listeadministratorerne
-# er dem der som sidste instans har kontrol over alle indstillingerne
-# for maillisten. De kan &aelig;ndre alle indstillinger der er
-# tilg&aelig;ngelige via disse administrative websider.
-# 
-# Listemoderatorerne har begrænset adgang; de kan ikke ændre
-# indstillinger for e-maillisten, men de kan tage sig af anmodninger i
-# forbindelse med listen, f.eks. anmodning om medlemskab, eller
-# godkende/afvise meddelelser der skal godkendes for at kunne udsendes
-# til listen. Listeadministratorerne kan ogs&aring; udf&oslash;re disse
-# opgaver.
-# 
-# For at aktivere muligheden for at have listemoderatorer, og p&aring;
-# den m&aring;de fordele arbejdsopgaverne i forbindelse med listen, skal
-# du anf&oslash;re din egen moderatoradgangskode, og angive
-# e-mailadresser for den/dem som skal v&aelig;re listemoderator(er).
-# Bemærk at i tekstboksene nedenfor skal du skrive e-mailadresser for
-# listeadministratorer.
+# There are two ownership roles associated with each mailing list.  The
+# list administrators are the people who have ultimate control over all
+# parameters of this mailing list.  They are able to change any list
+# configuration variable available through these administration web
+# pages.
+# 
+# The list moderators have more limited permissions; they are not able
+# to change any list configuration variable, but they are allowed to
+# tend to pending administration requests, including approving or
+# rejecting held subscription requests, and disposing of held postings.
+# Of course, the list administrators can also tend to pending requests.
+# 
+# In order to split the list ownership duties into administrators and
+# moderators, you must set a separate moderator password, and also
+# provide the email addresses of the list moderators.  Note that the
+# field you are changing here specifies the list administrators.
 owner = ['listmaster@jones.dk']
 
-# Der er to ejer-roller forbundet med hver mailliste.
-# Listeadministratorerne er dem der har den endelige kontrol over alle
-# indstillingerne for e-mallisten. De kan &aelig;ndre alle indstillinger
-# der er tilgængelige via disse administrative websider.
-# 
-# Listemoderatorerne har begr&aelig;nset adgang; de kan ikke &aelig;ndre
-# indstillinger for e-maillisten, men de kan tage sig af anmodninger
-# ang&aring;ende listen, f.eks. anmodning om medlemskab, eller
-# godkende/afvise meddelelser der skal godkendes for at kunne udsendes
-# p&aring; listen. Listeadministratorerne kan selvsagt ogs&aring;
-# udf&oslash;re disse opgaver.
-# 
-# For at aktivere muligheden for at have listemoderatorer, og p&aring;
-# den m&aring;de fordele arbejdsopgaverne i forbindelse med listen, skal
-# du anf&oslash;re din egen moderatoradgangskode, og indtaste
-# e-mailadresser for den/dem der skal v&aelig;re listemoderatore(r).
-# Bemærk, at i tekstboksene nedenfor skal du skrive listemoderator
-# e-mailadresse(r).
+# There are two ownership roles associated with each mailing list.  The
+# list administrators are the people who have ultimate control over all
+# parameters of this mailing list.  They are able to change any list
+# configuration variable available through these administration web
+# pages.
+# 
+# The list moderators have more limited permissions; they are not able
+# to change any list configuration variable, but they are allowed to
+# tend to pending administration requests, including approving or
+# rejecting held subscription requests, and disposing of held postings.
+# Of course, the list administrators can also tend to pending requests.
+# 
+# In order to split the list ownership duties into administrators and
+# moderators, you must set a separate moderator password, and also
+# provide the email addresses of the list moderators in this section.
+# Note that the field you are changing here specifies the list
+# moderators.
 moderator = []
 
-# Denne beskrivelse benyttes n&aring;r denne malliste listes op sammen
-# med andre maillister, i toptekster, osv. Den b&oslash;r v&aelig;re
-# s&aring; kort som overhovedet mulig, uden at det bliver uklart hvad
-# meningen med maillisten er eller hvad den skal bruges til.
+# This description is used when the mailing list is listed with other
+# mailing lists, or in headers, and so forth.  It should be as succinct
+# as you can get it, while still identifying what the list is.
 description = 'WikiFans'
 
-# Teksten tolkes som html bortset fra linieskift, der vil blive
-# &aelig;ndret til html-tag'et '<br>', sådan at du kan benytte links,
-# forh&aring;ndsformateret tekst, osv. Men brug alts&aring; kun
-# linieskift der hvor du vil have et nyt afsnit. V&aelig;r meget
-# omhyggelig, hvis du benytter html-kode. Fejl (f.eks. manglende
-# slut-tag's) kan f&oslash;re til at listens informationsside ikke
-# bliver vist s&aring;dan som den skal.
+# The text will be treated as html except that newlines will be
+# translated to <br> - so you can use links, preformatted text, etc, but
+# don't put in carriage returns except where you mean to separate
+# paragraphs.  And review your changes - bad html (like some
+# unterminated HTML constructs) can prevent display of the entire
+# listinfo page.
 info = """Open list for users of wikis hosted by JonasSmedegaard.
 
  * Everyone can send to the list (max. 40KiB).
@@ -77,131 +73,132 @@ info = """Open list for users of wikis hosted by JonasSmedegaard.
  * Everyone kan subscribe to the list."""
 
 # This text will be prepended to subject lines of messages posted to the
-# list, to distinguish mailing list messages in in mailbox summaries.
+# list, to distinguish mailing list messages in mailbox summaries.
 # Brevity is premium here, it's ok to shorten long mailing list names to
 # something more concise, as long as it still identifies the mailing
-# list.
+# list. You can also add a sequential number by %d substitution
+# directive. eg.; [listname %d] -> [listname 123] (listname %05d) ->
+# (listname 00123)
+# 
 subject_prefix = '[WikiFans] '
 
-# Skjul afsenderen af meddelelser, ved at erstatte den med e-maillistens
-# adresse (Dette medfører at alle From:, Sender, og Reply-To: felter
-# fjernes)
+# Hide the sender of a message, replacing it with the list address
+# (Removes From, Sender and Reply-To fields)
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 anonymous_list = False
 
-# Skal eksisterende Reply-To: felt i brevhovedet fjernes? Hvis ja, vil
-# dette blive gjort uanset om Mailman tilføjer et Reply-To: felt eller
-# ikke.
+# Should any existing Reply-To: header found in the original message be
+# stripped?  If so, this will be done regardless of whether an explict
+# Reply-To: header is added by Mailman or not.
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 first_strip_reply_to = False
 
-# Denne indstillling fort&aelig;ller hvad Mailman skal g&oslash;re med
-# Reply-To: feltet i brevhovedet p&aring; e-mail der sendes til listen.
-# Hvis den er sat til Afsender, vil Mailman ikke tilf&oslash;je noget
-# Reply-To: felt, men findes et s&aring;dant felt allerede, vil det ikke
-# blive fjernet. S&aelig;ttes indstillingen til enten e-maillistens
-# adresse eller Egendefineret adresse, vil Mailman tilf&oslash;je, evt.
-# erstatte, et Reply-To: felt. (Egendefineret adresse inds&aelig;tter
-# v&aelig;rdien af indstillingen reply_to_address).
-# 
-# Der er flere grunde til ikke at indf&oslash;re eller erstatte
-# Reply-To: felter. En grund kan v&aelig;re at nogen af dem der sender
-# mail til listen er afh&aelig;ngige af selv at kunne s&aelig;tte
-# Reply-To: adressen. En anden grund er at modifikation af Reply-To:
-# adressen g&oslash;r det vanskeligere kun at sende svar til afsender.
-# Se 'Reply-To' Munging Considered Harmful for en diskussion omkring
-# emnet. Se Reply-To Munging Considered Useful for modsatte meninger.
-# 
-# Nogle maillister har begr&aelig;nset adgang, med en parallel liste
-# beregnet til diskussioner. Eksempler p&aring; dette er 'patches' eller
-# 'checkin' lister, som system for revisionskontrol sender
-# &aelig;ndringer i programmet til, men diskussioner omkring udvikling
-# af programmet sendes til udviklernes egen mailliste. For at
-# underst&oslash;tte lignende e-maillister, v&aelig;lg Egendefineret
-# adresse og s&aelig;t Reply-To: adressen i indstillingen
-# reply_to_address til at pege på den parallelle diskussionsliste.
-#
-# gyldige værdier:
-#    0 = "Afsender"
-#    1 = "mail listens adresse"
-#    2 = "Egendefineret adresse"
+# This option controls what Mailman does to the Reply-To: header in
+# messages flowing through this mailing list.  When set to Poster, no
+# Reply-To: header is added by Mailman, although if one is present in
+# the original message, it is not stripped.  Setting this value to
+# either This list or Explicit address causes Mailman to insert a
+# specific Reply-To: header in all messages, overriding the header in
+# the original message if necessary (Explicit address inserts the value
+# of <a href="?VARHELP=general/reply_to_address">reply_to_address).
+# 
+# There are many reasons not to introduce or override the Reply-To:
+# header.  One is that some posters depend on their own Reply-To:
+# settings to convey their valid return address.  Another is that
+# modifying Reply-To: makes it much more difficult to send private
+# replies.  See <a
+# href="http://www.unicom.com/pw/reply-to-harmful.html">`Reply-To'
+# Munging Considered Harmful for a general discussion of this issue.
+# See <a
+# href="http://www.metasystema.net/essays/reply-to.mhtml">Reply-To
+# Munging Considered Useful for a dissenting opinion.
+# 
+# Some mailing lists have restricted posting privileges, with a parallel
+# list devoted to discussions.  Examples are `patches' or `checkin'
+# lists, where software changes are posted by a revision control system,
+# but discussion about the changes occurs on a developers mailing list.
+# To support these types of mailing lists, select Explicit address and
+# set the Reply-To: address below to point to the parallel list.
+#
+# legal values are:
+#    0 = "Poster"
+#    1 = "This list"
+#    2 = "Explicit address"
 reply_goes_to_list = 0
 
-# Her definerer du adressen der skal s&aelig;ttes i Reply-To: feltet
-# n&aring;r indstillingen reply_goes_to_list er sat til Egendefineret
-# adresse.
-# 
-# Der findes mange grunde til at ikke indf&oslash;re eller erstatte
-# Reply-To: felter. En grund kan v&aelig;re at nogen af dem der sender
-# e-mail til listen er afh&aelig;ngige af selv at kunne s&aelig;tte
-# Reply-To: adressen. En anden grund er at modificering af Reply-To:
-# adressen g&oslash;r det vanskeligere at sende svar kun til afsender.
-# Se 'Reply-To' Munging Considered Harmful for en diskussion omkring
-# temaet. Se Reply-To Munging Considered Useful for modsatte meninger.
-# 
-# Nogle maillister har begr&aelig;nset adgang, med en egen parallel
-# liste beregnet for diskussioner. Eksempler p&aring; dette er 'patches'
-# eller 'checkin' lister, som system for revisionskontrol sender
-# &aelig;ndringer i programmet til, mens diskussioner omkring udvikling
-# af programmet sendes til udviklernes egen mailliste. For at
-# underst&oslash;tte s&aring;danne maillister, kan du definere Reply-To:
-# adressen her, og vælge Egendefineret adresse i indstillingen
-# reply_goes_to_list.
-# 
-# Bem&aelig;rk at hvis den oprindelige meddelelse indeholder et
-# Reply-To: felt, vil det ikke &aelig;ndres.
+# This is the address set in the Reply-To: header when the <a
+# href="?VARHELP=general/reply_goes_to_list">reply_goes_to_list option
+# is set to Explicit address.
+# 
+# There are many reasons not to introduce or override the Reply-To:
+# header.  One is that some posters depend on their own Reply-To:
+# settings to convey their valid return address.  Another is that
+# modifying Reply-To: makes it much more difficult to send private
+# replies.  See <a
+# href="http://www.unicom.com/pw/reply-to-harmful.html">`Reply-To'
+# Munging Considered Harmful for a general discussion of this issue.
+# See <a
+# href="http://www.metasystema.net/essays/reply-to.mhtml">Reply-To
+# Munging Considered Useful for a dissenting opinion.
+# 
+# Some mailing lists have restricted posting privileges, with a parallel
+# list devoted to discussions.  Examples are `patches' or `checkin'
+# lists, where software changes are posted by a revision control system,
+# but discussion about the changes occurs on a developers mailing list.
+# To support these types of mailing lists, specify the explicit
+# Reply-To: address here.  You must also specify Explicit address in the
+# reply_goes_to_list variable.
+# 
+# Note that if the original message contains a Reply-To: header, it will
+# not be changed.
 reply_to_address = ''
 
-# V&aelig;lg kun 'ja' her, hvis listen skal bruges som  "paraply" for
-# andre lister. Hvis 'ja' er valgt, vil bekr&aelig;ftelser og
-# meddelelser med adgangskode blive sendt til en adresse som konstrueres
-# ud fra medlemmets e-mailadresse - v&aelig;rdien af indstillingen
-# "umbrella_member_suffix" tilf&oslash;jes medlemmets kontonavn (det som
-# st&aring;r f&oslash;r @-tegnet).
+# Set this to yes when this list is intended to cascade only to other
+# mailing lists.  When set, meta notices like confirmations and password
+# reminders will be directed to an address derived from the member's
+# address - it will have the value of "umbrella_member_suffix" appended
+# to the member's account name.
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 umbrella_list = False
 
-# N&aring;r "umbrella_list" indikerer at denne liste har andre
-# maillister som medlemmer, skal administrative meddelelser som f.eks.
-# bekr&aelig;ftelser og p&aring;mindelser om adgangskode ikke sendes til
-# selve listen, men snarere til administrator for listen. V&aelig;rdien
-# af denne indstilling bestemmer, hvilken adresse administrative
-# meddelelser skal sendes til. '-owner' er et almindeligt valg for denne
-# indstilling. Denne indstilling har ingen effekt n&aring;r
-# "umbrella_list" er sat til "Nej".
+# When "umbrella_list" is set to indicate that this list has other
+# mailing lists as members, then administrative notices like
+# confirmations and password reminders need to not be sent to the member
+# list addresses, but rather to the owner of those member lists.  In
+# that case, the value of this setting is appended to the member's
+# account name for such notices.  `-owner' is the typical choice.  This
+# setting has no effect when "umbrella_list" is "No".
 umbrella_member_suffix = '-owner'
 
-# Aktiver denne, hvis der skal sendes en p&aring;mindelse om adgangskode
-# til medlemmerne en gang hver m&aring;ned. Husk at medlemmerne
-# ogs&aring; selv kan frav&aelig;lge dette.
+# Turn this on if you want password reminders to be sent once per month
+# to your members.  Note that members may disable their own individual
+# password reminders.
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 send_reminders = 0
 
-# Tekst du skriver her vil blive tilf&oslash;jet &oslash;verst i
-# velkomsthilsenen der sendes til nye medlemmer. Velkomshilsenen
-# indeholder i forvejen vigtige adresser og URLer knyttet til
-# maillisten, s&aring; den slags information er det ikke
-# n&oslash;dvendigt at inkludere her. Her kan du tilf&oslash;je f.eks.
-# oplysning om etikette eller regler for brug af listen, o.l.
-# 
-# Bem&aelig;rk: Linierne i denne tekst vil brydes efter f&oslash;lgende
-# regler:
+# This value, if any, will be added to the front of the new-subscriber
+# welcome message.  The rest of the welcome message already describes
+# the important addresses and URLs for the mailing list, so you don't
+# need to include any of that kind of stuff here.  This should just
+# contain mission-specific kinds of things, like etiquette policies or
+# team orientation, or that kind of thing.
 # 
-# Hvert afsnit udfyldes s&aringdan at ingen linie er l&aelig;ngere en 70
-# tegn. Enhver linie der begynder med tomme tegn udfyldes ikke. Tomme
-# linier adskiller afsnit.
+# Note that this text will be wrapped, according to the following rules:
+# Each paragraph is filled so that no line is longer than 70 characters.
+# Any line that begins with whitespace is not filled. A blank line
+# separates paragraphs.
 # 
 welcome_msg = """This is an open list for users of wikis hosted by JonasSmedegaard.
 
@@ -211,184 +208,174 @@ welcome_msg = """This is an open list for users of wikis hosted by JonasSmedegaa
  * Emails are archived. The archive is public accessible.
  * Everyone kan subscribe to the list."""
 
-# S&aelig;t kun denne til 'Nej' hvis du skal tilf&oslash;je nye
-# medlemmer manuelt, og ikke vil have at de f&aring;r det at vide. Dette
-# er meget nyttigt n&aring;r man g&aring;r fra et andet mallistesystem
-# og til Mailman, og vil have at overgangen skal v&aelig;re s&aring;
-# lidt m&aelig;rkbar som muligt.
+# Turn this off only if you plan on subscribing people manually and
+# don't want them to know that you did so.  This option is most useful
+# for transparently migrating lists from some other mailing list manager
+# to Mailman.
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 send_welcome_msg = True
 
-# Tekst der sendes til medlemmer der framelder sig listen. Hvis feltet
-# er tomt, tilf&oslash;jes der ikke nogen speciel tekst til
-# frameldingen.
+# Text sent to people leaving the list.  If empty, no special text will
+# be added to the unsubscribe message.
 goodbye_msg = ''
 
-# Send afskedshilsen til medlemmer n&aring;r de frameldes?
+# Send goodbye message to members when they are unsubscribed?
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 send_goodbye_msg = True
 
-# Der udsendes en p&aring;mindelse til listemoderator (og
-# listeadministrator) dagligt om anmodninger der af en eller anden grund
-# venter p&aring; behandling. V&aelig;lger du "Ja", vil
-# listeadminstrator ogs&aring; modtage en meddelelse s&aring; snart en
-# anmodning ankommer.
+# List moderators (and list administrators) are sent daily reminders of
+# requests pending approval, like subscriptions to a moderated list, or
+# postings that are being held for one reason or another.  Setting this
+# option causes notices to be sent immediately on the arrival of new
+# requests as well.
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 admin_immed_notify = True
 
-# Skal listeadministrator modtage meddelelse om tilmeldinger og
-# afmeldinger?
+# Should administrator get notices of subscribes and unsubscribes?
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 admin_notify_mchanges = False
 
-# Approval notices are sent when mail triggers certain of the limits
-# except routine list moderation and spam filters, for which notices are
-# not sent.  This option overrides ever sending the notice.
+# Send mail to poster when their posting is held for approval?
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 respond_to_post_requests = 1
 
-# Når dette valg er aktiveret, vil al e-mail til listen blive modereret.
-# Dette valg kan være nyttigt når din mailliste f.eks. har en såkaldt
-# "flamewar", altså en "krig" hvor medlemmer kun skælder ud på hinanden.
-# En "nød-moderering" kan da hjælpe dig at fjerne usaglige meddelelser
-# til listen, og på den måde dysse en ophedet diskussion ned.
+# When this option is enabled, all list traffic is emergency moderated,
+# i.e. held for moderation.  Turn this option on when your list is
+# experiencing a flamewar and you want a cooling off period.
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 emergency = 0
 
-# Når et nyt medlem tilmeldes listen, bliver medlemmets indstillinger
-# taget herfra.
+# When a new member is subscribed to this list, their initial set of
+# options is taken from the this variable's setting.
 new_member_options = 256
 
-# Filter for administrative meddelelser vil unders&oslash;ge om
-# meddelelsen egentligt er ment som en administrativ anmodning (f.eks.
-# tilmelding, framelding, o.l.), og i s&aring; fald sende meddelelsen
-# til listeadministrator i stedet for.
+# Administrivia tests will check postings to see whether it's really
+# meant as an administrative request (like subscribe, unsubscribe, etc),
+# and will add it to the the administrative requests queue, notifying
+# the administrator of the new request, in the process.
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 administrivia = True
 
-# Maximum st&oslash;rrelse i kilobytes (KB) for indholdet i e-mail der
-# sendes til listen. Brug v&aelig;rdien '0' for ikke at have nogen
-# begr&aelig;nsning.
+# Maximum length in kilobytes (KB) of a message body.  Use 0 for no
+# limit.
 max_message_size = 40
 
-# "Maskinnavnet" er det navn som skal benyttes for e-mailadresser
-# relateret til Mailman p&aring; denne maskine, og er normalt navnet der
-# er forbundet med e-mail-servicen p&aring; maskinen. Denne indstilling
-# kan v&aelig;re nyttig hvis maskinen har flere navne.
+# The "host_name" is the preferred name for email to mailman-related
+# addresses on this host, and generally should be the mail host's
+# exchanger address, if any.  This setting can be useful for selecting
+# among alternative names of a host that has multiple addresses.
 host_name = 'jones.dk'
 
-# I RFC 2369 defineres en r&aelig;kke List-* felter i brevhovedet, der
-# normalt tilf&oslash;jes enhver meddelelse der sendes ud via listen.
-# Disse felter er til stor gavn for brugere , som benytter et
-# e-mailprogram der f&oslash;lger standarden. Disse felter b&oslash;r
-# derfor altid v&aelig;re med.
-# 
-# Ikke alle e-mailprogrammer f&oslash;lger denne standard. Hvis der er
-# mange medlemmer p&aring; listen, der benytter e-mailprogrammer, der
-# ikke kan h&aring;ndtere disse felter i brevhovedet, kan du v&aelig;lge
-# at udelade dem. Men du b&oslash;r f&oslash;rst fors&oslash;ge at
-# l&aelig;re og forklare medlemmerne hvad hensigten med s&aring;danne
-# felter er, og hvordan de kan skjule dem i deres e-mailprogram. Som en
-# sidste udvej kan du udelade felterne, men det anbefales ikke (og denne
-# mulighed kan faktisk ogs&aring; blive fjernet i senere versioner af
-# Mailman).
-#
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# RFC 2369 defines a set of List-* headers that are normally added to
+# every message sent to the list membership. These greatly aid end-users
+# who are using standards compliant mail readers.  They should normally
+# always be enabled.
+# 
+# However, not all mail readers are standards compliant yet, and if you
+# have a large number of members who are using non-compliant mail
+# readers, they may be annoyed at these headers.  You should first try
+# to educate your members as to why these headers exist, and how to hide
+# them in their mail clients.  As a last resort you can disable these
+# headers, but this is not recommended (and in fact, your ability to
+# disable these headers may eventually go away).
+#
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 include_rfc2369_headers = 1
 
-# List-Post: feltet er et af felterne anbefalet i RFC 2369. P&aring;
-# nogle e-maillister (som f.eks. kun bruges til
-# offentligg&oslash;relser), er det kun bestemte personer der har lov
-# til at poste til listen. Almindelige medlemmer af listen har normalt
-# ikke lov til at poste til listen. For den slags lister, er List-Post:
-# feltet misvisende. S&aelig;t denne indstilling til Nej, for at
-# undg&aring; at feltet tilf&oslash;jes. (Dette p&aring;virker ikke
-# andre List-*: felter.)
-#
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# The List-Post: header is one of the headers recommended by RFC 2369.
+# However for some announce-only mailing lists, only a very select group
+# of people are allowed to post to the list; the general membership is
+# usually not allowed to post.  For lists of this nature, the List-Post:
+# header is misleading. Select No to disable the inclusion of this
+# header. (This does not affect the inclusion of the other List-*:
+# headers.)
+#
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 include_list_post_header = 1
 
+# Discard held messages older than this number of days. Use 0 for no
+# automatic discarding.
+max_days_to_hold = 0
+
 ## Language options
 #
-# Underst&oslash;ttelse af flere sprog. (Internationalisering)
-
-# Dette er standardsproget som benyttes for denne mailliste. Hvis flere
-# end et sprog/ underst&oslash;ttes, vil medlemmer af listen selv kunne
-# v&aelig;lge hvilket sprog der skal benyttes n&aring;r de g&aring;r ind
-# p&aring; deres personlige webside, og n&aring;r meddelelser fra
-# systemet sendes til dem. Hvis medlemmerne ikke &aelig;ndrer noget
-# selv, vil dette standardsprog blive benyttet. Dette g&aelig;lder
-# b&aring;de web-baserede og e-mail-baserede meddelelser, men ikke
-# meddelelser sendt af listens medlemmer.
+# Natural language (internationalization) options.
+
+# This is the default natural language for this mailing list. If more
+# than one language is supported then users will be able to select their
+# own preferences for when they interact with the list.  All other
+# interactions will be conducted in the default language.  This applies
+# to both web-based and email-based messages, but not to email posted by
+# list members.
 preferred_language = 'en'
 
-# Her er alle sprog, som denne liste har underst&oslash;ttelse for.
-# Bem&aelig;rk at standardsproget skal v&aelig;re med.
+# These are all the natural languages supported by this list. Note that
+# the default language must be included.
 available_languages = ['en', 'da']
 
-# Hvis standardsproget for din mailliste benytter et andet tegns&aelig;t
-# end ASCII og Emne prefixet for listen indeholder tegn som ikke findes
-# i ASCII-tegns&aelig;ttet, vil prefixet altid blive kodet i henhold til
-# den relevante standard. Hvis Emne prefixet kun indeholder ASCII tegn,
-# ønsker du måske at vælge Aldrig for at undgå kodning. Dette kan gøre
-# emnet lidt mere læseligt for brugere med e-mailprogrammer der ikke kan
-# håndtere andre tegnsæt end ASCII.
-# 
-# Bemærk imidlertid, at hvis din mailliste modtager både kodede og
-# ukodede emnefelter , kan det være bedst at vælge Efter behov. Med
-# denne indstilling vil Mailman ikke kode ASCII prefixer hvis resten af
-# titelfeltet kun indeholder ASCII tegn, men vil kode prefixet hvis det
-# indeholder tegn som ikke er ASCII tegn. På denne måde undgås en
-# tvetydighed i standarderne, som forårsager at visse e-mailprogrammer
-# vil vise ekstra eller manglende mellemrum imellem emne prefixet og det
-# oprindelige emne.
-#
-# gyldige værdier:
-#    0 = "Aldrig"
-#    1 = "Altid"
-#    2 = "Efter behov"
+# If your mailing list's default language uses a non-ASCII character set
+# and the prefix contains non-ASCII characters, the prefix will always
+# be encoded according to the relevant standards.  However, if your
+# prefix contains only ASCII characters, you may want to set this option
+# to Never to disable prefix encoding.  This can make the subject
+# headers slightly more readable for users with mail readers that don't
+# properly handle non-ASCII encodings.
+# 
+# Note however, that if your mailing list receives both encoded and
+# unencoded subject headers, you might want to choose As needed.  Using
+# this setting, Mailman will not encode ASCII prefixes when the rest of
+# the header contains only ASCII characters, but if the original header
+# contains non-ASCII characters, it will encode the prefix.  This avoids
+# an ambiguity in the standards which could cause some mail readers to
+# display extra, or missing spaces between the prefix and the original
+# header.
+#
+# legal values are:
+#    0 = "Never"
+#    1 = "Always"
+#    2 = "As needed"
 encode_ascii_prefixes = 2
 
 ## Nondigest options
 #
-# Regler for levering i normal-modus.
+# Policies concerning immediately delivered list traffic.
 
-# Kan medlemmer vælge normal-modus?
+# Can subscribers choose to receive mail immediately, rather than in
+# batched digests?
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 nondigestable = True
 
-# Tekst der tilføjes &oslash;verst i e-mail der sendes til listens
-# medlemmer. This text can include Python format strings which are
-# resolved against list attributes.  The list of substitutions allowed
-# are:
+# Text prepended to the top of every immediately-delivery message. This
+# text can include Python format strings which are resolved against list
+# attributes.  The list of substitutions allowed are:
 # 
 # 
 # real_name - The "pretty" name of the list; usually the list name with
@@ -413,10 +400,9 @@ nondigestable = True
 # 
 msg_header = ''
 
-# Tekst som tilf&oslash;jes nederst i e-mail der sendes til listens
-# medlemmer. This text can include Python format strings which are
-# resolved against list attributes.  The list of substitutions allowed
-# are:
+# Text appended to the bottom of every immediately-delivery message.
+# This text can include Python format strings which are resolved against
+# list attributes.  The list of substitutions allowed are:
 # 
 # 
 # real_name - The "pretty" name of the list; usually the list name with
@@ -444,45 +430,54 @@ msg_footer = """--
 %(real_name)s@%(host_name)s
 %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s"""
 
+# When you scrub attachments, they are stored in archive area and links
+# are made in the message so that the member can access via web browser.
+# If you want the attachments totally disappear, you can use content
+# filter options.
+#
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
+scrub_nondigest = False
+
 ## Digest options
 #
-# Opsætning af sammendrag-modus.
+# Batched-delivery digest characteristics.
 
-# Kan medlemmer af listen vælge sammendrag-modus?
+# Can list members choose to receive list traffic bunched in digests?
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 digestable = True
 
-# Hvilken modus er standard for nye brugere?
+# Which delivery mode is the default for new users?
 #
-# gyldige værdier:
-#    0 = "Normal"
-#    1 = "Sammendrag"
+# legal values are:
+#    0 = "Regular"
+#    1 = "Digest"
 digest_is_default = False
 
-# Hvilket format skal benyttes som standard for samle-email?
+# When receiving digests, which format is default?
 #
-# gyldige værdier:
-#    0 = "Ren tekst"
+# legal values are:
+#    0 = "Plain"
 #    1 = "MIME"
 mime_is_default_digest = False
 
-# Hvor stor (i KB) m&aring; en samle-email h&oslash;jst v&aelig;re
-# f&oslash;r den udsendes?
+# How big in Kb should a digest be before it gets sent out?
 digest_size_threshhold = 30
 
-# Skal der sendes en samle-email dagligt, selv om st&oslash;rrelsen ikke
-# er opn&aring;et?
+# Should a digest be dispatched daily when the size threshold isn't
+# reached?
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 digest_send_periodic = True
 
-# Tekst som tilf&oslash;jes &oslash;verst i samle-emailen, f&oslash;r
-# indholdsfortegnelsen.This text can include Python format strings which
+# Text attached (as an initial message, before the table of contents) to
+# the top of digests. This text can include Python format strings which
 # are resolved against list attributes.  The list of substitutions
 # allowed are:
 # 
@@ -509,10 +504,9 @@ digest_send_periodic = True
 # 
 digest_header = ''
 
-# Tekst der tilføjes nederst i hver samle-email, som sidste
-# information.This text can include Python format strings which are
-# resolved against list attributes.  The list of substitutions allowed
-# are:
+# Text attached (as a final message) to the bottom of digests. This text
+# can include Python format strings which are resolved against list
+# attributes.  The list of substitutions allowed are:
 # 
 # 
 # real_name - The "pretty" name of the list; usually the list name with
@@ -540,277 +534,279 @@ digest_footer = """--
 %(real_name)s@%(host_name)s
 %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s"""
 
-# N&aring;r et nyt volume startes, &oslash;ges volume nummeret, og
-# udgavenummeret s&aelig;ttes til 1.
+# When a new digest volume is started, the volume number is incremented
+# and the issue number is reset to 1.
 #
-# gyldige værdier:
-#    0 = "&Aring;rlig"
-#    1 = "M&aring;nedlig"
-#    2 = "Kvartalsvis"
-#    3 = "Ugentlig"
-#    4 = "Daglig"
+# legal values are:
+#    0 = "Yearly"
+#    1 = "Monthly"
+#    2 = "Quarterly"
+#    3 = "Weekly"
+#    4 = "Daily"
 digest_volume_frequency = 3
 
 ## Privacy options
 #
-# Her kan du bestemme hvad der kr&aelig;ves for at tilmelde sig til
-# maillisten, og bl.a. bestemme om maillisten skal v&aelig;re skjult
-# eller ikke. Se ogs&aring; <a
-# href="http://mail.jones.dk/mailman/admin/wikifans/archive">Indstillinger 
-# for arkivering</a> for egne indstillinger, n&aring;r det g&aelig;lder
-# arkivet og arkivering.
+# This section allows you to configure subscription and membership
+# exposure policy.  You can also control whether this list is public or
+# not.  See also the <a
+# href="http://mail.jones.dk/mailman/admin/wikifans/archive">Archival
+# Options</a> section for separate archive-related privacy settings.
 
-# Vis denne mailliste n&aring;r nogen beder om at se en oversigt over
-# maillister p&aring; denne maskine?
+# Advertise this list when people ask what lists are on this machine?
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 advertised = 1
 
-# bekræftelse(*) - bekr&aelig;ftelse via e-mail er n&oslash;dvendig
-# godkendelse - anmodning om medlemskab skal godkendes af
-# listeadministrator (eller evt. listemoderator) bekr&aelig;ftelse +
-# godkendelse - b&aring;de bekr&aelig;ftelse via e-mail og godkendelse
-# fra listeadministrator (evt. listemoderator) er n&oslash;dvendig
-# 
-# (*) n&aring;r nogen vil tilmelde sig en liste, sender Mailman en
-# meddelelse med en unik identifikator som skal angives for at
-# bekr&aelig;fte tilmeldingen. P&aring; den m&aring;de vil det ikke
-# v&aelig;re muligt at tilmelde nogen imod deres vilje.
-#
-# gyldige værdier:
-#    1 = "Bekr&aelig;ftelse"
-#    2 = "Godkendelse"
-#    3 = "Bekr&aelig;ftelse og godkendelse"
+# Confirm (*) - email confirmation required Require approval - require
+# list administrator approval for subscriptions Confirm and approve -
+# both confirm and approve
+# 
+# (*) when someone requests a subscription, Mailman sends them a notice
+# with a unique subscription request number that they must reply to in
+# order to subscribe. This prevents mischievous (or malicious) people
+# from creating subscriptions for others without their consent.
+#
+# legal values are:
+#    1 = "Confirm"
+#    2 = "Require approval"
+#    3 = "Confirm and approve"
 subscribe_policy = 1
 
-# N&aring;r medlemmer &oslash;nsker at forlade en mailliste, sender de
-# en anmodning om framelding, enten via web, eller via e-mail. Normalt
-# er det bedst at disse anmodninger automatisk godkendes, s&aring;
-# medlemmer kan afmelde sig n&aring;r de &oslash;nsker det (mange
-# &oslash;nsker selv at kunne administrere en framelding). For nogle
-# f&aring; maillister kan det alligevel v&aelig;re aktuelt at have
-# kontrol over om medlemmer kan afmelde sig selv eller ej. En liste som
-# alle ansatte i et firma SKAL v&aelig;re medlem af, er et eksempel
-# p&aring; en s&aring;dan liste.
-#
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# When members want to leave a list, they will make an unsubscription
+# request, either via the web or via email. Normally it is best for you
+# to allow open unsubscriptions so that users can easily remove
+# themselves from mailing lists (they get really upset if they can't get
+# off lists!).
+# 
+# For some lists though, you may want to impose moderator approval
+# before an unsubscription request is processed.  Examples of such lists
+# include a corporate mailing list that all employees are required to be
+# members of.
+#
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 unsubscribe_policy = 0
 
-# Alle e-mailadresser som angives her vil blive udelukket fra listen, og
-# kan ikke tilmelde sig. Indtast e-mailadresser, en pr. linie, start
-# linien med tegnet ^ for at angive et regexp-udtryk der skal stemme
-# overens med afsenderadressen.
+# Addresses in this list are banned outright from subscribing to this
+# mailing list, with no further moderation required.  Add addresses one
+# per line; start the line with a ^ character to designate a regular
+# expression match.
 ban_list = []
 
-# Hvis denne indstilling ikke er sat til 'Alle', vil medlemslisten blive
-# beskyttet af medlemmernes eller administrators adgangskode.
+# When set, the list of subscribers is protected by member or admin
+# password authentication.
 #
-# gyldige værdier:
-#    0 = "Alle"
-#    1 = "Kun medlemmer af listen"
-#    2 = "Kun listeadministrator"
+# legal values are:
+#    0 = "Anyone"
+#    1 = "List members"
+#    2 = "List admin only"
 private_roster = 1
 
-# V&aelig;lger du 'Ja' her, vil medlemmers e-mailadresser blive
-# omskrevet n&aring;r de vises i en oversigt p&aring; websiderne
-# (b&aring;de som tekst og som links), s&aring; de ikke er nemme at
-# tolke som e-mailadresser. Formålet er at undg&aring; at medlemmernes
-# mailadresser bliver opsamlet af e-mailsniffere som skanner websider
-# for e-mailadresser (og derefter bruger dem til at udsende spam/junk
-# mail).
-#
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# Setting this option causes member email addresses to be transformed
+# when they are presented on list web pages (both in text and as links),
+# so they're not trivially recognizable as email addresses.  The
+# intention is to prevent the addresses from being snarfed up by
+# automated web scanners for use by spammers.
+#
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 obscure_addresses = 1
 
 ## Privacy options
 #
-# N&aring;r en meddelelse sendes til maillisten, g&aring;r den igennem
-# nogle trin for at afg&oslash;re om moderator skal godkende meddelelsen
-# eller ikke. Her finder du indstillinger til at kontrollere moderation
-# af e-mail fra b&aring;de medlemmer og ikke-medlemmer.
-# 
-# <p>E-mail fra medlemmer holdes tilbage for godkendelse hvis deres
-# <b>moderationsflag</b> er sat. Du kan bestemme om e-mail fra medlemmer
-# normalt skal vurderes eller ikke f&oslash;r den sendes til listen.
-# 
-# <p>E-mail som ikke er sendt af medlemmer af listen, kan automatisk
-# blive <a
-# href="?VARHELP=privacy/sender/accept_these_nonmembers">godkendt</a>,
-# <a href="?VARHELP=privacy/sender/hold_these_nonmembers">holdt tilbage
-# for godkendelse</a>, <a
-# href="?VARHELP=privacy/sender/reject_these_nonmembers">afvist (sendt
-# retur)</a>, eller <a
-# href="?VARHELP=privacy/sender/discard_these_nonmembers">slettet</a>,
-# enten enkeltvis eller som en gruppe. Al e-mail fra ikke-medlemmer, som
-# ikke specifikt bliver godkendt, sendt retur eller slettet, vil blive
-# behandlet alt efter hvad <a
-# href="?VARHELP=privacy/sender/generic_nonmember_action">generelle
-# regler for ikke-medlemmer</a> viser.
-# 
-# <p>I tekstboksene nedenfor kan du tilf&oslash;je en e-mailadresse pr.
-# linie. Du kan ogs&aring; tilf&oslash;je  <a
-# href="http://www.python.org/doc/current/lib/module-re.html">Python
-# regexp-udtryk</a>. Begynd i s&aring; fald linien med tegnet ^ for at
-# markere at det er et s&aring;dant udtryk. N&aring;r du benytter
-# backslash, skriv da lige som i rene strings (Python raw strings)
-# (normalt kun &eacute;n backslash ad gangen).
-# 
-# <p>Bem&aelig;rk: sammenligning med normale e-mailadresser
-# udf&oslash;res f&oslash;rst, regexp-udtryk vil derfor blive behandlet
-# sidst.
-
-# Hvert medlem af listen har et moderationsflag som fort&aelig;ller om
-# e-mails fra medlemmet kan sendes direkte til e-maillisten, eller om de
-# f&oslash;rst skal godkendes af listemoderator. N&aring;r
-# moderationsflaget er sat til, skal e-mails fra medlemmet godkendes af
-# listemoderator f&oslash;r de udsendes til alle p&aring; listen. Som
-# listeadministrator kan du for hvert enkelt medlem bestemme om
-# medlemmets e-mail skal modereres eller ikke. N&aring;r et nyt medlem
-# tilmeldes listen, s&aelig;ttes moderationsflaget til den indstilling
-# du v&aelig;lger her. S&aelig;t den til 'Nej' hvis du &oslash;nsker at
-# e-mail fra medlemmer normalt skal g&aring; lige til listen. S&aelig;t
-# den til 'Ja' hvis du &oslash;nsker at e-mail fra nye medlemmer skal
-# godkendes f&oslash;r de udsendes til hele listen. Du kan altid
-# s&aelig;tte moderationsflaget for hvert enkelt medlem fra
-# Administration af medlemmer siden.
-#
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# When a message is posted to the list, a series of moderation steps are
+# take to decide whether the a moderator must first approve the message
+# or not.  This section contains the controls for moderation of both
+# member and non-member postings.
+# 
+# <p>Member postings are held for moderation if their <b>moderation
+# flag</b> is turned on.  You can control whether member postings are
+# moderated by default or not.
+# 
+# <p>Non-member postings can be automatically <a
+# href="?VARHELP=privacy/sender/accept_these_nonmembers" >accepted</a>,
+# <a href="?VARHELP=privacy/sender/hold_these_nonmembers">held for
+# moderation</a>, <a
+# href="?VARHELP=privacy/sender/reject_these_nonmembers" >rejected</a>
+# (bounced), or <a
+# href="?VARHELP=privacy/sender/discard_these_nonmembers"
+# >discarded</a>, either individually or as a group.  Any posting from a
+# non-member who is not explicitly accepted, rejected, or discarded,
+# will have their posting filtered by the <a
+# href="?VARHELP=privacy/sender/generic_nonmember_action">general
+# non-member rules</a>.
+# 
+# <p>In the text boxes below, add one address per line; start the line
+# with a ^ character to designate a <a href=
+# "http://www.python.org/doc/current/lib/module-re.html" >Python regular
+# expression</a>.  When entering backslashes, do so as if you were using
+# Python raw strings (i.e. you generally just use a single backslash).
+# 
+# <p>Note that non-regexp matches are always done first.
+
+# Each list member has a moderation flag which says whether messages
+# from the list member can be posted directly to the list, or must first
+# be approved by the list moderator.  When the moderation flag is turned
+# on, list member postings must be approved first.  You, the list
+# administrator can decide whether a specific individual's postings will
+# be moderated or not.
+# 
+# When a new member is subscribed, their initial moderation flag takes
+# its value from this option.  Turn this option off to accept member
+# postings by default.  Turn this option on to, by default, moderate
+# member postings first.  You can always manually set an individual
+# member's moderation bit by using the membership management screens.
+#
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 default_member_moderation = 0
 
+# Hold -- this holds the message for approval by the list moderators.
 # 
-# Hold tilbage -- meddelelsen holdes tilbage for godkendelse af
-# listemoderator(er). Afvis -- meddelelsen sendes automatisk retur til
-# afsender. Begrundelsen der sendes kan du skrive selv Slet --
-# meddelelsen bliver fjernet uden at give besked om dette til afsender.
+# Reject -- this automatically rejects the message by sending a bounce
+# notice to the post's author.  The text of the bounce notice can be <a
+# href="?VARHELP=privacy/sender/member_moderation_notice" >configured by
+# you.
+# 
+# Discard -- this simply discards the message, with no notice sent to
+# the post's author.
 # 
 #
-# gyldige værdier:
-#    0 = "Hold&nbsp;tilbage"
-#    1 = "Afvis"
-#    2 = "Slet"
+# legal values are:
+#    0 = "Hold"
+#    1 = "Reject"
+#    2 = "Discard"
 member_moderation_action = 0
 
-# Tekst som skal sendes med meddelelsen om afvisning som sendes til
-# modererede medlemmer af listen.
+# Text to include in any <a
+# href="?VARHELP/privacy/sender/member_moderation_action" >rejection
+# notice to be sent to moderated members who post to this list.
 member_moderation_notice = ''
 
-# E-mail fra disse ikke-medlemmer vil automatisk blive godkendt.
-# Tilf&oslash;j e-mailadresser, en pr. linie. Start linien med tegnet ^
-# for at angive et regexp-udtryk som skal stemme overens med
-# afsenderadressen.
+# Postings from any of these non-members will be automatically accepted
+# with no further moderation applied.  Add member addresses one per
+# line; start the line with a ^ character to designate a regular
+# expression match.
 accept_these_nonmembers = []
 
-# e-mail fra disse ikke-medlemmer vil automatisk blive holdt tilbage for
-# vurdering af listemoderator. Afsenderen vil modtage en meddelelse om
-# dette, med bl.a. instruktioner om hvordan han/hun kan
-# tilbagetr&aelig;kke sin e-mail. Indtast e-mailadresser, en pr. linie.
-# Start linien med tegnet ^ for at angive et regexp-udtryk som skal
-# stemme overens med afsenderadressen.
+# Postings from any of these non-members will be immediately and
+# automatically held for moderation by the list moderators. The sender
+# will receive a notification message which will allow them to cancel
+# their held message.  Add member addresses one per line; start the line
+# with a ^ character to designate a regular expression match.
 hold_these_nonmembers = []
 
-# E-mail fra disse ikke-medlemmer vil automatisk blive afvist. De vil
-# f&aring; mailen retur, med en meddelelse om at den blev automatisk
-# afvist. Dette valg b&oslash;r ikke benyttes for kendte spammere, de
-# b&oslash;r automatisk slettes. Indtast e-mailadresser, en pr. linie.
-# Start linien med tegnet ^ for at angive et regexp-udtryk som skal
-# stemme overens med afsenderadressen.
+# Postings from any of these non-members will be automatically rejected.
+# In other words, their messages will be bounced back to the sender with
+# a notification of automatic rejection.  This option is not appropriate
+# for known spam senders; their messages should be <a
+# href="?VARHELP=privacy/sender/discard_these_nonmembers" >automatically
+# discarded.
+# 
+# Add member addresses one per line; start the line with a ^ character
+# to designate a regular expression match.
 reject_these_nonmembers = []
 
-# E-mail fra disse ikke-medlemmer vil automatisk blive slettet. Det vil
-# sige at meddelelsen afvises uden nogen form for tilbagemelding, men
-# listemoderator kan (om &oslash;nsket) modtage en kopi af den afviste
-# e-mail. Tilf&oslash;j e-mailadresser, en pr. linie, start linien med
-# tegnet ^ for at angive et regexp-udtryk der skal stemme overens med
-# afsenderadressen.
+# Postings from any of these non-members will be automatically
+# discarded.  That is, the message will be thrown away with no further
+# processing or notification.  The sender will not receive a
+# notification or a bounce, however the list moderators can optionally
+# <a href="?VARHELP=privacy/sender/forward_auto_discards" >receive
+# copies of auto-discarded messages..
+# 
+# Add member addresses one per line; start the line with a ^ character
+# to designate a regular expression match.
 discard_these_nonmembers = []
 
-# N&aring;r en e-mail fra et ikke-medlem bliver modtaget, sammenlignes
-# e-mailens afsender med listen over e-mailadresser der skal godkendes,
-# holdes tilbage, <a
-# href="?VARHELP=privacy/sender/reject_these_nonmembers" >afvises
-# (sendes retur), eller slettes. Hvis afsenderadressen ikke stemmer
-# overens med en adresse der findes i listerne, bliver f&oslash;lgende
-# afg&oslash;relse truffet.
-#
-# gyldige værdier:
-#    0 = "Godkend"
-#    1 = "Hold&nbsp;tilbage"
-#    2 = "Afvis"
-#    3 = "Slet"
+# When a post from a non-member is received, the message's sender is
+# matched against the list of explicitly <a
+# href="?VARHELP=privacy/sender/accept_these_nonmembers" >accepted,
+# held, <a href="?VARHELP=privacy/sender/reject_these_nonmembers"
+# >rejected (bounced), and <a
+# href="?VARHELP=privacy/sender/discard_these_nonmembers" >discarded
+# addresses.  If no match is found, then this action is taken.
+#
+# legal values are:
+#    0 = "Accept"
+#    1 = "Hold"
+#    2 = "Reject"
+#    3 = "Discard"
 generic_nonmember_action = 1
 
-# Skal meddelelser fra ikke-medlemmer, hvis mail automatisk slettes,
-# videresendes til listemoderator?
+# Should messages from non-members, which are automatically discarded,
+# be forwarded to the list moderator?
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 forward_auto_discards = 1
 
+# Text to include in any rejection notice to be sent to non-members who
+# post to this list. This notice can include the list's owner address by
+# %(listowner)s and replaces the internally crafted default message.
+nonmember_rejection_notice = ''
+
 ## Privacy options
 #
-# Her kan du ops&aelig;tte filtrering baseret på modtageren af
-# meddelelsen.
+# This section allows you to configure various filters based on the
+# recipient of the message.
 
-# Meget (faktisk det meste) spam/junk mail har ikke de endelige
-# modtagere i modtagerfelterne. Faktisk indeholder felterne To: og/eller
-# Cc: oftest en helt ugyldig adresse. Begr&aelig;nsningen du
-# s&aelig;tter her har kun indvirkning p&aring; det som st&aring;r
-# f&oslash;r '@' tegnet i adressen, men filtret vil alligevel opfange og
-# blokere det meste spam/junk mail.
+# Many (in fact, most) spams do not explicitly name their myriad
+# destinations in the explicit destination addresses - in fact often the
+# To: field has a totally bogus address for obfuscation.  The constraint
+# applies only to the stuff in the address before the '@' sign, but
+# still catches all such spams.
+# 
+# The cost is that the list will not accept unhindered any postings
+# relayed from other addresses, unless
+# 
 # 
-# Prisen for dette er, at listen ikke uhindret vil kunne modtage e-mail
-# videresendt via andre e-mailadresser, med mindre
+# The relaying address has the same name, or
 # 
+# The relaying address name is included on the options that specifies
+# acceptable aliases for the list.
 # 
-# Adressen der videresendes fra hedder det samme, eller Adressen der
-# videresendes fra inkluderes i indstillingen som bestemmer gyldige
-# aliaser for listen.
 # 
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 require_explicit_destination = 1
 
-# Alternative e-mailadresser som godtages n&aring;r
-# 'require_explicit_destination' er sat til. Som v&aelig;rdi for denne
-# indstilling skal du angive regexp-udtryk ("regular expressions"), et
-# udtryk pr. linie, der sammenlignes med hver modtageradresse i
-# meddelelsen. Sammenligningen udf&oslash;res med Pythons re.match()
-# funktion, som betyder at de kun g&aelig;lder for begyndelsen af
-# strengen.
-# 
-# For bagudkompatibilitet med Mailman 1.1, hvis regexp-udtryk ikke
-# indeholder en '@', sammenlignes udtrykket kun med den f&oslash;rste
-# del (det som st&aring;r f&oslash;r '@') i modtageradressen. Hvis
-# sammenligningen ikke lykkes, eller hvis udtrykket ikke indholder en
-# '@', sammenlignes udtrykket med hele modtageradressen.
-# 
-# Sammenligning med kun den f&oslash;rste del af en modtageradresse
-# underst&oslash;ttes ikke l&aelig;ngere. I fremtidige versioner af
-# Mailman vil kun sammenligning med hele modtageradresser blive
-# underst&oslash;ttet.
+# Alternate addresses that are acceptable when
+# `require_explicit_destination' is enabled.  This option takes a list
+# of regular expressions, one per line, which is matched against every
+# recipient address in the message.  The matching is performed with
+# Python's re.match() function, meaning they are anchored to the start
+# of the string.
+# 
+# For backwards compatibility with Mailman 1.1, if the regexp does not
+# contain an `@', then the pattern is matched against just the local
+# part of the recipient address.  If that match fails, or if the pattern
+# does contain an `@', then the pattern is matched against the entire
+# recipient address.
+# 
+# Matching against the local part is deprecated; in a future release,
+# the pattern will always be matched against the entire recipient
+# address.
 acceptable_aliases = ''
 
-# Hvis en mail der er sendt til listen indeholder s&aring; mange som
-# eller flere modtagere end denne v&aelig;rdi, holdes mailen tilbage,
-# s&aring; listeadministrator eventuelt kan godkende den. Brug
-# v&aelig;rdien 0 for ingen begr&aelig;nsning.
+# If a posting has this number, or more, of recipients, it is held for
+# admin approval.  Use 0 for no ceiling.
 max_num_recipients = 10
 
 ## Privacy options
 #
-# Her kan du opsætte forskellige anti-spam filtre, som kan bidrage til
-# at reducere mængden af spam der distribueres via e-maillisten.
+# This section allows you to configure various anti-spam filters posting
+# filters, which can help reduce the amount of spam your list members
+# end up receiving.
+# 
 
 # Each header filter rule has two parts, a list of regular expressions,
 # one per line, and an action to take.  Mailman matches the message's
@@ -821,22 +817,23 @@ max_num_recipients = 10
 # You can have more than one filter rule for your list.  In that case,
 # each rule is matched in turn, with processing stopped after the first
 # match.
+# 
+# Note that headers are collected from all the attachments (except for
+# the mailman administrivia message) and matched against the regular
+# expressions. With this feature, you can effectively sort out messages
+# with dangerous file types or file name extensions.
 header_filter_rules = []
 
-# Brug denne indstilling til at bortfiltrere mail til listen, baseret
-# p&aring; indholdet af et eller flere felter i brevhovedet. Her skal du
-# skrive regexp-udtryk (regular expressions), et pr. linie, som
-# sammenlignes med det aktuelle felt. Sammenligningen skelner ikke
-# imellem store og sm&aring; bogstaver. Linier der begynder med '#'
-# sammenlignes ikke.
+# Use this option to prohibit posts according to specific header values.
+# The target value is a regular-expression for matching against the
+# specified header.  The match is done disregarding letter case.  Lines
+# beginning with '#' are ignored as comments.
 # 
-# For eksempel: udtrykket to: .*@public.com fort&aelig;ller at al mail
-# som indeholder '@public.com' i To: feltet, skal holdes tilbage for
-# godkendelse.
+# For example:to: .*@public.com  says to hold all postings with a To:
+# mail header containing '@public.com' anywhere among the addresses.
 # 
-# Bem&aelig;rk: tomme tegn i starten af regexp-udtrykket fjernes. Dette
-# kan omg&aring;s p&aring; flere m&aring;der, f.eks. ved at bruge
-# escape-tegn eller parenteser.
+# Note that leading whitespace is trimmed from the regexp.  This can be
+# circumvented in a number of ways, e.g. by escaping or bracketing it.
 bounce_matching_headers = """
 # Lines that *start* with a '#' are comments.
 to: friend@public.com
@@ -846,415 +843,439 @@ from: .*@uplinkpro.com"""
 
 ## Bounce options
 #
-# Disse regler bestemmer hvordan automatisk behandling af returmails
-# skal foreg&aring;. Her er en oversigt over hvordan det virker.
-# 
-# <p>N&aring;r Mailman modtager en returmail, bliver to ting
-# fors&oslash;gt tolket. Den ene er e-mailadressen for medlemmet som
-# egentlig skulle modtage e-mailen, og den anden er &aring;rsagen til
-# problemet. &Aring;rsagen tolkes til at v&aelig;re <em>alvorlig</em>
-# eller <em>harml&oslash;s</em> alt efter om &aring;rsagen er af kritisk
-# eller af mindre alvorlig art. Hvis der er tvivl, tolkes &aring;rsagen
-# som alvorlig.
-# 
-# <p>Hvis ingen e-mailadresse kan hentes ud af meddelelsen, bliver den
-# normalt afvist. Ellers vil medlemmet som har e-mailadressen f&aring;
-# tildelt et <em>returtal</em>, og hver gang der kommer en
-# returmeddelelse vil tallet &oslash;ges. Alvorlige &aring;rsager
-# f&oslash;rer til at tallet &oslash;ges med 1, harml&oslash;se
-# &aring;rsager f&oslash;rer til at det &oslash;ges med 0.5. Dette sker
-# kun &eacute;n gang pr. dag, s&aring; selv om der kommer 10 alvorlige
-# returmails fra et medlem p&aring; &eacute;n dag, vil tallet kun
-# &oslash;ges med 1.
-# 
-# <p>N&aring;r returtallet for et medlem n&aring;r en vis <a
-# href="?VARHELP=bounce/bounce_score_threshold">gr&aelig;nse</a>,
-# stoppes levering til medlemmet. Dermed vil medlemmet ikke modtage
-# e-mail fra listen f&oslash;r levering s&aelig;ttes til igen. Medlemmet
-# vil med j&aelig;vne mellemrum modtage meddelelse om at dette er sket,
-# og hvad han/hun skal g&oslash;re for at f&aring; e-mail fra listen
-# igen.
-# 
-# <p>Du kan bestemme <a
-# href="?VARHELP=bounce/bounce_you_are_disabled_warnings">hvor mange
-# advarsler</a> medlemmet skal have og <a
-# href="?VARHELP=bounce/bounce_you_are_disabled_warnings_interval">hvor
-# ofte</a> han/hun skal modtage s&aring;danne advarsler.
-# 
-# <p>Der er en vigtig indstilling mere: efter en vis tid -- hvor ingen
-# returmeddelelser dukker op -- regnes returinformation for at
-# v&aelig;re <a
-# href="?VARHELP=bounce/bounce_info_stale_after">for&aelig;ldet</a> og
-# stoppes. Ved at justere denne v&aelig;rdi, og s&aelig;tte en
-# gr&aelig;nse for returantallet, kan du bestemme hvor lang tid der skal
-# g&aring; f&oslash;r levering til et medlem stoppes. Begge disse
-# v&aelig;rdier b&oslash;r tilpasses efter hvor ofte og hvor meget
-# e-mail der sendes til din liste.
-
-# Ved at sætte denne værdi til Nej, slår du al automatisk tolkning af
-# returmeddelelser for denne liste fra. Bemærk at hvis meddelelser
-# afvises vil listeadministratoren ikke blive forstyrret med dem.
-#
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# These policies control the automatic bounce processing system in
+# Mailman.  Here's an overview of how it works.
+# 
+# <p>When a bounce is received, Mailman tries to extract two pieces of
+# information from the message: the address of the member the message
+# was intended for, and the severity of the problem causing the bounce.
+# The severity can be either <em>hard</em> or <em>soft</em> meaning
+# either a fatal error occurred, or a transient error occurred.  When in
+# doubt, a hard severity is used.
+# 
+# <p>If no member address can be extracted from the bounce, then the
+# bounce is usually discarded.  Otherwise, each member is assigned a
+# <em>bounce score</em> and every time we encounter a bounce from this
+# member we increment the score.  Hard bounces increment by 1 while soft
+# bounces increment by 0.5.  We only increment the bounce score once per
+# day, so even if we receive ten hard bounces from a member per day,
+# their score will increase by only 1 for that day.
+# 
+# <p>When a member's bounce score is greater than the <a
+# href="?VARHELP=bounce/bounce_score_threshold">bounce score
+# threshold</a>, the subscription is disabled.  Once disabled, the
+# member will not receive any postings from the list until their
+# membership is explicitly re-enabled (either by the list administrator
+# or the user).  However, they will receive occasional reminders that
+# their membership has been disabled, and these reminders will include
+# information about how to re-enable their membership.
+# 
+# <p>You can control both the <a
+# href="?VARHELP=bounce/bounce_you_are_disabled_warnings">number of
+# reminders</a> the member will receive and the <a
+# href="?VARHELP=bounce/bounce_you_are_disabled_warnings_interval"
+# >frequency</a> with which these reminders are sent.
+# 
+# <p>There is one other important configuration variable; after a
+# certain period of time -- during which no bounces from the member are
+# received -- the bounce information is <a
+# href="?VARHELP=bounce/bounce_info_stale_after">considered stale</a>
+# and discarded.  Thus by adjusting this value, and the score threshold,
+# you can control how quickly bouncing members are disabled.  You should
+# tune both of these to the frequency and traffic volume of your list.
+
+# By setting this value to No, you disable all automatic bounce
+# processing for this list, however bounce messages will still be
+# discarded so that the list administrator isn't inundated with them.
+#
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 bounce_processing = True
 
-# Hvert medlem tildeles et returtal, og hver gang der kommer en
-# returmeddelelse vil dette tal &oslash;ges.  Alvorlige (&aring;rsager
-# f&oslash;rer til at det &oslash;ges med 1, mens harml&oslash;se
-# &aring;rsager f&oslash;rer til at det &oslash;ges med 0.5. Dette sker
-# kun &eacute;n gang pr. dag, s&aring; selv om der kommer 10 alvorlige
-# returmails fra et medlem p&aring; &eacute;n dag, vil tallet kun
-# &oslash;ges med 1.
-# 
-# Her s&aelig;ttes den &oslash;vre gr&aelig;nse for medlemmets returtal
-# Overskrides denne gr&aelig;nse stoppes levering automatisk, men
-# medlemmet bliver ikke fjernet fra listen.
+# Each subscriber is assigned a bounce score, as a floating point
+# number.  Whenever Mailman receives a bounce from a list member, that
+# member's score is incremented.  Hard bounces (fatal errors) increase
+# the score by 1, while soft bounces (temporary errors) increase the
+# score by 0.5.  Only one bounce per day counts against a member's
+# score, so even if 10 bounces are received for a member on the same
+# day, their score will increase by just 1.
+# 
+# This variable describes the upper limit for a member's bounce score,
+# above which they are automatically disabled, but not removed from the
+# mailing list.
 bounce_score_threshold = 5.0
 
-# Antal dage f&oslash;r returinformation stoppes hvis der ikke dukker
-# flere returmails op. Dette tal skal v&aelig;re et heltal.
+# The number of days after which a member's bounce information is
+# discarded, if no new bounces have been received in the interim.  This
+# value must be an integer.
 bounce_info_stale_after = 7
 
-# Hvor mange Levering til dig er stoppet advarsler der skal sendes til
-# et medlem f&oslash;r medlemmet frameldes listen. S&aelig;t denne værdi
-# til 0 for at fjerne et medlem fra listen straks, hvis der kommer
-# returmails fra medlemmets e-mailadresse. Dette tal skal være et
-# heltal.
+# How many Your Membership Is Disabled warnings a disabled member should
+# get before their address is removed from the mailing list.  Set to 0
+# to immediately remove an address from the list once their bounce score
+# exceeds the threshold.  This value must be an integer.
 bounce_you_are_disabled_warnings = 3
 
-# Antal dage imellem hver gang en Levering til dig er stoppet advarsel
-# skal sendes ud. Dette tal skal være et heltal.
+# The number of days between sending the Your Membership Is Disabled
+# warnings.  This value must be an integer.
 bounce_you_are_disabled_warnings_interval = 7
 
-# Mailmans automatiske returmailh&aring;ndtering er meget robust, men
-# det er alligevel umuligt at genkende alle typer returmails der kommer.
-# Du b&oslash;r v&aelig;lge Ja her, af to grunde: 1) Hvis det virkelig
-# er en permanent returmail fra et medlem af listen, b&oslash;r du
-# antagelig manuelt afmelde medlemmet fra listen, og 2) du vil
-# m&aring;ske sende en meddelelse til udviklerne af Mailman s&aring;dan
-# at returmails automatisk genkendes af Mailman i senere versioner. Hvis
-# du ikke vil g&oslash;re nogen af delene, s&aelig;ttes denne
-# indstilling til Nej. S&aring; vil alle returmails afvises automatisk
-# uden videre behandling. Bem&aelig;rk: Denne indstilling vil ogs&aring;
-# indvirke p&aring; al e-mail der sendes til listens -admin adresse. Den
-# adresse er for&aelig;ldet og udg&aring;et, men måske vil nogen
-# alligevel fortsat sende e-mail til den. Hvis nogen g&oslash;r det, og
-# du har sat denne indstilling til Nej, vil disse mails ogs&aring; blive
-# afvist. M&aring;ske vil du ogs&aring; ops&aelig;tte et automatisk svar
-# p&aring; e-mail sendt til -owner og -admin adresserne.
-#
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# While Mailman's bounce detector is fairly robust, it's impossible to
+# detect every bounce format in the world.  You should keep this
+# variable set to Yes for two reasons: 1) If this really is a permanent
+# bounce from one of your members, you should probably manually remove
+# them from your list, and 2) you might want to send the message on to
+# the Mailman developers so that this new format can be added to its
+# known set.
+# 
+# If you really can't be bothered, then set this variable to No and all
+# non-detected bounces will be discarded without further processing.
+# 
+# Note: This setting will also affect all messages sent to your list's
+# -admin address.  This address is deprecated and should never be used,
+# but some people may still send mail to this address.  If this happens,
+# and this variable is set to No those messages too will get discarded.
+# You may want to set up an autoresponse message for email to the -owner
+# and -admin address.
+#
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 bounce_unrecognized_goes_to_list_owner = True
 
-# Ved at sætte denne til Nej, fravælges beskeden der normalt sendes til
-# ejer(e) af listen, når levering af e-mail til et medlem stoppes på
-# grund af for mange returmails. Der vil til gengæld altid blive forsøgt
-# afsendt en e-mail med besked til medlemmet.
+# By setting this value to No, you turn off notification messages that
+# are normally sent to the list owners when a member's delivery is
+# disabled due to excessive bounces. An attempt to notify the member
+# will always be made.
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 bounce_notify_owner_on_disable = True
 
-# Ved at sætte denne til Nej, fravælges beskeden der normalt sendes til
-# ejer(e) af listen, når et medlem frameldes listen på grund af for
-# mange returmails. Der vil til gengæld altid blive forsøgt afsendt en
-# e-mail med besked til medlemmet.
+# By setting this value to No, you turn off notification messages that
+# are normally sent to the list owners when a member is unsubscribed due
+# to excessive bounces.  An attempt to notify the member will always be
+# made.
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 bounce_notify_owner_on_removal = True
 
 ## Archive options
 #
-# Regler for arkivering
+# List traffic archival policies.
 
-# Arkiver e-mail i et arkiv?
+# Archive messages?
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 archive = True
 
-# Skal arkivet v&aelig;re offentligt eller privat?
+# Is archive file source for public or private archival?
 #
-# gyldige værdier:
-#    0 = "Offentligt"
-#    1 = "Privat"
+# legal values are:
+#    0 = "public"
+#    1 = "private"
 archive_private = 0
 
-# Hvor ofte skal arkivet deles op?
+# How often should a new archive volume be started?
 #
-# gyldige værdier:
-#    0 = "&Aring;rlig"
-#    1 = "M&aring;nedlig"
-#    2 = "Kvartalsvis"
-#    3 = "Ugentlig"
-#    4 = "Daglig"
+# legal values are:
+#    0 = "Yearly"
+#    1 = "Monthly"
+#    2 = "Quarterly"
+#    3 = "Weekly"
+#    4 = "Daily"
 archive_volume_frequency = 1
 
 ## Gateway options
 #
-# E-mail-Til-Nyhedsgruppe og Nyhedsgruppe-Til-E-mail tjeneste.
+# Mail-to-News and News-to-Mail gateway services.
 
-# Nyhedsgruppe-tjeneste er ikke en del af Mailman. Du skal have adgang
-# til en eksisterende NNTP tjeneste, og maskinen som denne mailliste
-# k&oslash;rer p&aring; skal have adgang til at hente og afsende
-# meddelelser til NNTP tjenesten.
+# This value may be either the name of your news server, or optionally
+# of the format name:port, where port is a port number.
+# 
+# The news server is not part of Mailman proper.  You have to already
+# have access to an NNTP server, and that NNTP server must recognize the
+# machine this mailing list runs on as a machine capable of reading and
+# posting news.
 nntp_host = ''
 
-# Navn p&aring; nyhedsgruppe der skal sendes til og/eller fra.
+# The name of the Usenet group to gateway to and/or from.
 linked_newsgroup = ''
 
-# Skal nye meddelelser til denne liste sendes til nyhedsgruppen?
+# Should new posts to the mailing list be sent to the newsgroup?
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 gateway_to_news = 0
 
-# Skal nye meddelelser til nyhedsgruppen sendes til denne mailliste?
+# Should new posts to the newsgroup be sent to the mailing list?
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 gateway_to_mail = 0
 
-# Denne indstilling fort&aelig;ller Mailman hvilken slags
-# moderationsregler nyhedsgruppen har og hvordan de koordineres med
-# maillistens moderationsregler. Dette g&aelig;lder kun nyhedgrupper du
-# overfører meddelelser til, s&aring; hvis du kun overf&oslash;rer fra
-# en nyhedsgruppe, eller nyhedsgruppen du overf&oslash;rer til ikke er
-# modereret, s&aelig;ttes indstillingen til Ingen.
-# 
-# Hvis nyhedsgruppen er modereret, kan du s&aelig;tte maillisten til at
-# v&aelig;re moderationsadressen for nyhedsgruppen. Ved at vælge
-# Modereret, vil en ekstra meddelelse holdes tilbage i
-# godkendelsesprocessen. Al mail sendt til maillisten skal godkendes
-# f&oslash;r den sendes til nyhedsgruppen, eller til medlemmerne af
-# listen.
-# 
-# Vær opm&aelig;rksom p&aring; at hvis brevhovedet i mailen har et
-# Approved: felt med listens administrative adgangskode, vil denne regel
-# ikke blive benyttet. På den m&aring;de kan priviligerede afsendere
-# sende mail direkte til listen og nyhedsgruppen.
-# 
-# Hvis nyhedsgruppen er modereret, men du alligevel vil have en
-# &aring;ben liste, b&oslash;r du vælge Åben liste, modereret
-# nyhedsgruppe. S&aring; vil de s&aelig;dvanlige mekanismer for
-# moderation blive benyttet i Mailman, men alle meddelelser der sendes
-# til Usenet vil f&aring; et Approved felt i brevhovedet.
-#
-# gyldige værdier:
-#    0 = "Ingen"
-#    1 = "Åben liste, modereret nyhedsgruppe"
-#    2 = "Modereret"
+# This setting determines the moderation policy of the newsgroup and its
+# interaction with the moderation policy of the mailing list.  This only
+# applies to the newsgroup that you are gatewaying to, so if you are
+# only gatewaying from Usenet, or the newsgroup you are gatewaying to is
+# not moderated, set this option to None.
+# 
+# If the newsgroup is moderated, you can set this mailing list up to be
+# the moderation address for the newsgroup.  By selecting Moderated, an
+# additional posting hold will be placed in the approval process.  All
+# messages posted to the mailing list will have to be approved before
+# being sent on to the newsgroup, or to the mailing list membership.
+# 
+# Note that if the message has an Approved header with the list's
+# administrative password in it, this hold test will be bypassed,
+# allowing privileged posters to send messages directly to the list and
+# the newsgroup.
+# 
+# Finally, if the newsgroup is moderated, but you want to have an open
+# posting policy anyway, you should select Open list, moderated group.
+# The effect of this is to use the normal Mailman moderation facilities,
+# but to add an Approved header to all messages that are gatewayed to
+# Usenet.
+#
+# legal values are:
+#    0 = "None"
+#    1 = "Open list, moderated group"
+#    2 = "Moderated"
 news_moderation = 0
 
-# Mailman tilføjer normalt en tekst du selv kan tilrette (emne prefix)
-# foran emnefeltet i mail som sendes til listen, og normalt sker dette
-# også for mail som sendes videre til Usenet. Du kan sætte denne
-# indstilling til Nej hvis du ikke ønsker emne prefix tilføjet til mail
-# som sendes til Usenet. Sættes emne prefix for listen til off, vil
-# videresendte meddelelser heller ikke få prefix tilføjet.
+# Mailman prefixes Subject: headers with text you can customize and
+# normally, this prefix shows up in messages gatewayed to Usenet.  You
+# can set this option to No to disable the prefix on gated messages.  Of
+# course, if you turn off normal Subject: prefixes, they won't be
+# prefixed for gated messages either.
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 news_prefix_subject_too = 1
 
 ## Autoreply options
 #
-# Indstillinger for automatiske svar.<p>
+# Auto-responder characteristics.<p>
 # 
-# I tekstboksene nedenfor kan du bruge følgende variabler: (skriv:
-# %(&lt;variabelnavn&gt;)s ) for at indsætte ønsket information: <p><ul>
-# <li><b>listname</b> - <em>navnet p&aring; listen</em>
-# <li><b>listurl</b> - <em>URL til listens webside</em>
-# <li><b>requestemail</b> - <em>listens -request e-mailadresse</em>
-# <li><b>owneremail</b> - <em>listens -owner e-mailadresse</em> </ul>
+# In the text fields below, string interpolation is performed with the
+# following key/value substitutions: <p><ul> <li><b>listname</b> -
+# <em>gets the name of the mailing list</em> <li><b>listurl</b> -
+# <em>gets the list's listinfo URL</em> <li><b>requestemail</b> -
+# <em>gets the list's -request address</em> <li><b>owneremail</b> -
+# <em>gets the list's -owner address</em> </ul>
 # 
-# <p>Du kan enten skrive teksten direkte i tekstboksene, eller du kan
-# angive navnet p&aring; en fil som indeholder teksten. Denne fil vil
-# s&aring; blive indl&aelig;st i tekstboksen, fra dit lokale filsystem.
+# <p>For each text field, you can either enter the text directly into
+# the text box, or you can specify a file on your local system to upload
+# as the text.
 
-# Skal Mailman sende et automatisk svar til dem der sender e-mail til
-# listen?
+# Should Mailman send an auto-response to mailing list posters?
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 autorespond_postings = 0
 
-# Automatisk svar der skal sendes.
+# Auto-response text to send to mailing list posters.
 autoresponse_postings_text = ''
 
-# Skal Mailman sende et automatisk svar p&aring; e-mail der sendes til
-# -owner adressen?
+# Should Mailman send an auto-response to emails sent to the -owner
+# address?
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 autorespond_admin = 0
 
-# Automatisk svar p&aring; e-mail til -owner adressen.
+# Auto-response text to send to -owner emails.
 autoresponse_admin_text = ''
 
-# Skal Mailman sende et automatisk svar p&aring; e-mail der sendes til
-# -request adressen? Hvis du v&aelig;lger ja, kan du ogs&aring;
-# v&aelig;lge om e-mailen der blev sendt til -request adressen skal
-# medtages i det automatiske svar.
+# Should Mailman send an auto-response to emails sent to the -request
+# address?  If you choose yes, decide whether you want Mailman to
+# discard the original email, or forward it on to the system as a normal
+# mail command.
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja, men uden den originale e-mail"
-#    2 = "Ja, og medtag den originale e-mail"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes, w/discard"
+#    2 = "Yes, w/forward"
 autorespond_requests = 0
 
-# Automatisk svar p&aring; e-mail til -request adressen.
+# Auto-response text to send to -request emails.
 autoresponse_request_text = ''
 
-# Antal dage imellem automatisk svar p&aring; e-mail, fra samme
-# afsender, til listen eller til -request/-owner adresserne. S&aelig;t
-# denne v&aelig;rdi til 0 (eller et negativt tal) for at sende
-# automatisk svar hver gang.
+# Number of days between auto-responses to either the mailing list or
+# -request/-owner address from the same poster.  Set to zero (or
+# negative) for no grace period (i.e. auto-respond to every message).
 autoresponse_graceperiod = 90
 
 ## Contentfilter options
 #
-# Regler for indhold i e-mail sendt til listen.
-# 
-# <p>Filtrering af indhold fungerer således: når listen modtager en
-# e-mail og du har beskyttelse med filtrering af indhold aktiveret,
-# sammenlignes først eventuelle vedh&aelig;ftninger med <a
-# href="?VARHELP=contentfilter/filter_mime_types">MIME filtrene</a>.
-# Hvis en vedh&aelig;ftning passer med et af disse filtre, bliver
-# vedh&aelig;ftningen fjernet.
-# 
-# <p>Derefter sammenlignes eventuelle vedh&aelig;ftninger med <a
-# href="?VARHELP=contentfilter/pass_mime_types">gyldige MIME typer</a>,
-# hvis nogen er defineret. Alle vedh&aelig;ftninger som ikke stemmer
-# overens med de angivne MIME typer, bliver fjernet.
-# 
-# <p>Efter filtreringen vil alle tomme <tt>multipart</tt>
-# vedh&aelig;ftninger v&aelig;re fjernet. Hvis selve meddelelsen er helt
-# tom efter denne filtrering, vil meddelelsen blive afvist. Derefter vil
-# enhver <tt>multipart/alternative</tt> vedh&aelig;ftning blive
-# erstattet af den første alternative som ikke er tom.
-# 
-# <p>Til sidst vil alle <tt>text/html</tt> vedh&aelig;ftninger som måtte
-# v&aelig;re tilbage i meddelelsen blive konverteret til
-# <tt>text/plain</tt> hvis <a
-# href="?VARHELP=contentfilter/convert_html_to_plaintext">konverter til
-# ren tekst</a> er sat til og serveren er konfigureret til at tillade
-# sådanne konverteringer.
-
-# Skal Mailman filtrere indhold i e-mail sendt til listen som angivet
-# nedenfor?
-#
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# Policies concerning the content of list traffic.
+# 
+# <p>Content filtering works like this: when a message is received by
+# the list and you have enabled content filtering, the individual
+# attachments are first compared to the <a
+# href="?VARHELP=contentfilter/filter_mime_types">filter types</a>.  If
+# the attachment type matches an entry in the filter types, it is
+# discarded.
+# 
+# <p>Then, if there are <a
+# href="?VARHELP=contentfilter/pass_mime_types">pass types</a> defined,
+# any attachment type that does <em>not</em> match a pass type is also
+# discarded.  If there are no pass types defined, this check is skipped.
+# 
+# <p>After this initial filtering, any <tt>multipart</tt> attachments
+# that are empty are removed.  If the outer message is left empty after
+# this filtering, then the whole message is discarded.
+# 
+# <p> Then, each <tt>multipart/alternative</tt> section will be replaced
+# by just the first alternative that is non-empty after filtering if <a
+# href="?VARHELP=contentfilter/collapse_alternatives"
+# >collapse_alternatives</a> is enabled.
+# 
+# <p>Finally, any <tt>text/html</tt> parts that are left in the message
+# may be converted to <tt>text/plain</tt> if <a
+# href="?VARHELP=contentfilter/convert_html_to_plaintext"
+# >convert_html_to_plaintext</a> is enabled and the site is configured
+# to allow these conversions.
+
+# Should Mailman filter the content of list traffic according to the
+# settings below?
+#
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 filter_content = False
 
-# Brug denne indstilling til at fjerne vedh&aelig;ftninger der passer
-# til MIME typer. Hver linie skal her indeholde navnet på en MIME
-# type/subtype, f.eks. image/gif. Hvis du ønsker at fjerne alle
-# vedh&aelig;ftninger som har en given hoved MIME type, kan du undlade
-# at angive subtype, f.eks. image.
+# Use this option to remove each message attachment that matches one of
+# these content types.  Each line should contain a string naming a MIME
+# type/subtype, e.g. image/gif.  Leave off the subtype to remove all
+# parts with a matching major content type, e.g. image.
 # 
-# Tomme linier medtages ikke.
+# Blank lines are ignored.
 # 
-# Se også gyldige MIME typer for whitelist af MIME typer.
+# See also <a href="?VARHELP=contentfilter/pass_mime_types"
+# >pass_mime_types for a content type whitelist.
 filter_mime_types = ''
 
-# Brug denne indstilling for at definere hvilke MIME typer der skal være
-# tilladt. Krav og format for filtrering er identisk med MIME filtre.
+# Use this option to remove each message attachment that does not have a
+# matching content type.  Requirements and formats are exactly like <a
+# href="?VARHELP=contentfilter/filter_mime_types" >filter_mime_types.
 # 
-# Bem&aelig;rk: hvis du lægger noget ind her, men ikke angiver
-# multipart, vil ingen e-mail med vedh&aelig;ftninger blive medtaget.
+# Note: if you add entries to this list but don't add multipart to this
+# list, any messages with attachments will be rejected by the pass
+# filter.
 pass_mime_types = """multipart/mixed
 multipart/alternative
 text/plain"""
 
-# Skal Mailman konvertere text/html dele til ren tekst? Denne
-# konvertering vil finde sted efter at MIME filteret har fjernet de
-# uønskede dele.
+# Remove message attachments that have a matching filename extension.
+filter_filename_extensions = """exe
+bat
+cmd
+com
+pif
+scr
+vbs
+cpl"""
+
+# Remove message attachments that don't have a matching filename
+# extension.  Leave this field blank to skip this filter test.
+pass_filename_extensions = ''
+
+# Should Mailman collapse multipart/alternative to its first part
+# content?
 #
-# gyldige værdier:
-#    0 = "Nej"
-#    1 = "Ja"
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
+collapse_alternatives = True
+
+# Should Mailman convert text/html parts to plain text?  This conversion
+# happens after MIME attachments have been stripped.
+#
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
 convert_html_to_plaintext = True
 
-# Her bestemmer du hvad der skal ske, når en meddelelse filtreres fra af
-# et filter, altså hvis vedh&aelig;ftningen filtreres fra af MIME
-# filteret, eller en vedh&aelig;ftning ikke har en af de gyldige MIME
-# typer, eller meddelelsen ender med at være tom efter filtrering.
-# 
-# Bemærk at det du vælger her ikke vil ske hvis en meddelelse stadig
-# indeholder noget efter filtrering. Så vil meddelelsen altid blive
-# sendt videre til listen.
-# 
-# Når meddelelsen afvises, skrives Message-ID for den afviste meddelelse
-# til loggen. Når meddelelsen sendes retur eller videresendes til
-# listens ejer, vil en begrundelse altid blive inkluderet i den
-# returmail der sendes til afsenderen. Når meddelelserne skal bevares,
-# gemmes de i et specielt køkatalog på disken, sådan at
-# serveradministrator kan se (og måske gøre noget med) dem, men bliver
-# ellers fjernet. Dette sidste valg er kun tilgængeligt hvis
-# serveradministrator har tilladt det.
-#
-# gyldige værdier:
-#    0 = "Slet"
-#    1 = "Afvis"
-#    2 = "Videresend til Listens Ejer"
-#    3 = "Bevar"
+# One of these actions is taken when the message matches one of the
+# content filtering rules, meaning, the top-level content type matches
+# one of the <a href="?VARHELP=contentfilter/filter_mime_types"
+# >filter_mime_types, or the top-level content type does not match one
+# of the <a href="?VARHELP=contentfilter/pass_mime_types"
+# >pass_mime_types, or if after filtering the subparts of the message,
+# the message ends up empty.
+# 
+# Note this action is not taken if after filtering the message still
+# contains content.  In that case the message is always forwarded on to
+# the list membership.
+# 
+# When messages are discarded, a log entry is written containing the
+# Message-ID of the discarded message.  When messages are rejected or
+# forwarded to the list owner, a reason for the rejection is included in
+# the bounce message to the original author.  When messages are
+# preserved, they are saved in a special queue directory on disk for the
+# site administrator to view (and possibly rescue) but otherwise
+# discarded.  This last option is only available if enabled by the site
+# administrator.
+#
+# legal values are:
+#    0 = "Discard"
+#    1 = "Reject"
+#    2 = "Forward to List Owner"
+#    3 = "Preserve"
 filter_action = 0
 
 ## Topics options
 #
-# Emneord for listen
-
-# Emnefilteret kategoriserer hver e-mail som kommer til listen, efter de
-# regexp-udtryk du skriver nedenfor. Hvis felterne Subject: eller
-# Keywords: i brevhovedet i en mail stemmer overens med et af disse
-# udtryk, bliver mailen placeret under det p&aring;g&aelig;ldende emne.
-# Hvert medlem af listen kan vælge kun at modtage mail der passer til de
-# &oslash;nskede emner. E-mail som ikke h&oslash;rer under noget emne,
-# bliver ikke leveret.
-# 
-# Bem&aeligrk: Dette fungerer kun i normal-modus, ikke i
-# sammendrag-modus.
-# 
-# Indholdet i meddelelsen kan ogs&aring; unders&oslash;ges for Subject:
-# og Keyword: felter, alt efter hvad indstillingen
-# topics_bodylines_limit er sat til.
+# List topic keywords
+
+# The topic filter categorizes each incoming email message according to
+# <a href="http://www.python.org/doc/current/lib/module-re.html">regular
+# expression filters you specify below.  If the message's Subject: or
+# Keywords: header contains a match against a topic filter, the message
+# is logically placed into a topic bucket.  Each user can then choose to
+# only receive messages from the mailing list for a particular topic
+# bucket (or buckets).  Any message not categorized in a topic bucket
+# registered with the user is not delivered to the list.
+# 
+# Note that this feature only works with regular delivery, not digest
+# delivery.
+# 
+# The body of the message can also be optionally scanned for Subject:
+# and Keywords: headers, as specified by the <a
+# href="?VARHELP=topics/topics_bodylines_limit">topics_bodylines_limit
+# configuration variable.
 #
-# gyldige værdier:
-#    0 = "Ikke tilgængeligt"
-#    1 = "Tilgængeligt"
+# legal values are:
+#    0 = "Disabled"
+#    1 = "Enabled"
 topics_enabled = 0
 
-# Her angiver du hvor mange linier af mailens indhold emnefilteret skal
-# gennems&oslash;ge. En s&oslash;gning stopper n&aring;r det antal
-# linier er gennems&oslash;gt, eller n&aring;r den m&oslash;der en linie
-# som ikke ligner et brevhoved-felt. S&aelig;ttes denne v&aelig;rdi til
-# nul (0), vil ingen linier i indholdet blive unders&oslash;gt (dvs. kun
-# Keywords: og Subject: i brevhovedet unders&oslash;ges). S&aelig;ttes
-# denne v&aelig;rdi til et negativt tal, vil alle linier blive
-# unders&oslash;gt frem til den f&oslash;rste linie som ikke ligner et
-# brevhoved-felt.
+# The topic matcher will scan this many lines of the message body
+# looking for topic keyword matches.  Body scanning stops when either
+# this many lines have been looked at, or a non-header-like body line is
+# encountered.  By setting this value to zero, no body lines will be
+# scanned (i.e. only the Keywords: and Subject: headers will be
+# scanned).  By setting this value to a negative number, then all body
+# lines will be scanned until a non-header-like line is encountered.
+# 
 topics_bodylines_limit = 5
 
-# Hvert emneord er faktisk et regexp-udtryk, der sammenlignes med dele
-# af mailen, nemlig felterne Keywords: og Subject: i brevhovedet.
-# Bem&aelig;rk at de f&oslash;rste linier i mailens indhold ogs&aring;
-# kan best&aring; af s&aring;danne "felter", og de kan dermed ogs&aring;
-# blive unders&oslash;gt.
+# Each topic keyword is actually a regular expression, which is matched
+# against certain parts of a mail message, specifically the Keywords:
+# and Subject: message headers. Note that the first few lines of the
+# body of the message can also contain a Keywords: and Subject: "header"
+# on which matching is also performed.
 topics = []