Comments changed to danish.

14 files changed, 8440 insertions, 9344 deletions

diff --git a/mailman/absynthe.py b/mailman/absynthe.py
index 4d4d2e7..73c0b95 100644
--- a/mailman/absynthe.py
+++ b/mailman/absynthe.py
@@ -1,362 +1,386 @@
-## "absynthe" mailing list configuration settings -*- python -*-
-## captured on Wed Mar 16 02:40:55 2005
+## Indstillinger for maillisten "absynthe"  -*- python -*-
+## Dato: Thu May  5 09:52:35 2005
 
 ## General options
 #
-# 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 :-)
+# Grundlæggende egenskaber for listen, blant andet en beskrivelse af
+# listen, og hvordan den opfører sig.
+
+# Her kan du f.eks. stave navnet med stort forbogstav, eller ændre visse
+# bogstaver til store sådan at navnet kan udtales på en rigtig
+# måde eller at forkortelser fremhæves. Bemærk at dette navn
+# bruges i e-maillistens adresse (f.eks. i bekræftigelser ved
+# tilmeldinger), så der 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 :-)
 real_name = 'Absynthe'
 
-# 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.
+# Der er to roller forbundet med hver mailliste. Listeadministratorene
+# 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.
+# 
+# Listemoderatorene har begrænset adgang; de kan ikke ændre
+# indstillinger for e-maillisten, men de kan tage sig af
+# forespørgsler i forbindlse med listen, f.eks. ansøgning
+# om medlemskab, eller godkende/afvise meddelelser der skal godkendes
+# for at kunne udsendes til listen. Listeadministratorene kan også
+# udføre disse opgaver.
+# 
+# For at aktivere muligheden for at have listemoderatorer, og på
+# den måde opdele arbejdsopgaverne forbundet med listen, skal du
+# sætte dit eget moderatorpassword, og angive din
+# e-mailadressen(e) til den/de som skal være listemoderator(er).
+# Bemærk at i tekstboksene nedenfor skal du skrive e-mailadressen(e) til
+# listeadministratoren(e).
 owner = ['go@jones.dk']
 
-# 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.
+# Det er to ejerskab forbundet med hver mailliste. Listeadministratorene
+# er dem der har den endelige kontrol over alle indstillingerne for
+# e-mallisten. De kan ændre alle indstillinger der er tilgengelige
+# via disse administrative websider.
+# 
+# Listemoderatorene har begrænset adgang; de kan ikke ændre
+# indstillinger for e-maillisten, men de kan tage sig af
+# forespørgsler angående listen, f.eks. ansøgning om
+# medlemskab, eller godkende/afvise meddelelser der skal godkendes for
+# at kunne udsendes på listen. Listeadministratorene kan selvsagt
+# også udføre disse opgaver.
+# 
+# For at aktivere muligheten for at have listemoderatorer, og på
+# den måden opdele arbejdsopgaverne der er forbundet med listen,
+# skal du sætte dit eget moderatorpassword, og indtaste din
+# e-mailadresse(r) til den/de der skal være listemoderator(er).
+# Bemærk at i tekstboksene nedenfor skal du skrive e-mailadressen(e) til
+# listemoderatoren(e).
 moderator = []
 
-# 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.
+# Denne beskrivelsen 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 gjøre det uklart
+# hvad meningen med maillisten er eller hvad den skal bruges til.
 description = ''
 
-# 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.
+# Teksten tolkes som html bortset fra linieskift, der vil blive
+# &aelig;ndret til html-tag'en '<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. Benytter du html-kode,
+# husk da at gennemse meget grundigt, for fejl (f.eks. manglende
+# slutt-tag's) kan f&oslash;re til at listens informationsside ikke vil
+# vises s&aring;dan som den skal.
 info = ''
 
-# 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 er sat ind foran emne-/tittelfeltet i e-mail der sendes
+# til listen, for at skille e-mailliste-meddelelser i e-mailboksen fra
+# dem der er medlem af listen. Denne tekst b&oslash;r holdes p&aring; et
+# absolut minimum, benytter du f.eks. listens navn og navnet er langt,
+# b&oslash;r du stave det endnu kortere her. Men den b&oslash;r fremover
+# v&aelig;re beskrivende for listen.
 subject_prefix = '[Absynthe] '
 
-# Hide the sender of a message, replacing it with the list address
-# (Removes From, Sender and Reply-To fields)
+# Skjule afsenderen af meddelser, ved at erstatte den med e-maillistens
+# adresse (Dette medfører at alle From:, Sender, og Reply-To: felter
+# fjernes)
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 anonymous_list = 0
 
-# 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.
+# Skal eksisterende Reply-To: felt i meddelelseshovedet fjernes? Hvis ja
+# vil dette blive gjort uanset om Mailman tlføjer et Reply-To: felt
+# eller ikke.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 first_strip_reply_to = 0
 
-# 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.org/essays/reply-to-useful.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.
+# Denne indstillling fort&aelig;ller hvad Mailman skal gj&oslash;re med
+# Reply-To: feltet i meddelelseshovedet 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;dan 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 diskusion omkring
+# emnet. Se Reply-To Munging Considered Useful for modsatte meninger.
+# 
+# Nogle maillister har begr&aelig;nset adgang, med en egen parallell
+# liste beregnet til diskutioner. Eksempler p&aring; dette er 'patches'
+# eller 'checkin' lister, som system for revisionskontrol sender
+# &aelig;ndringer i programmet til, men diskusioner omkring udvikling af
+# programmet sendes til udviklerenes 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 diskusionsliste.
 #
-# legal values are:
-#    0 = "Poster"
-#    1 = "This list"
-#    2 = "Explicit address"
+# gyldige værdier:
+#    0 = "Afsender"
+#    1 = "mail listens adresse"
+#    2 = "Egendefineret adresse"
 reply_goes_to_list = 1
 
-# 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.org/essays/reply-to-useful.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.
+# 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 modifikasion af Reply-To:
+# adressen g&oslash;r det vanskeligere at sende svar kun til afsender.
+# Se 'Reply-To' Munging Considered Harmful for en diskusion omkring
+# temaet. Se Reply-To Munging Considered Useful for modsatte meninger.
+# 
+# Nogen maillister har begr&aelig;nset adgang, med en egen parallell
+# liste beregnet for diskusioner. Eksempler p&aring; dette er 'patches'
+# eller 'checkin' lister, som system for revisionskontrol sender
+# &aelig;ndringer til i programmet, men diskusioner rundt udvikling af
+# programmet sendes til udviklerenes egen mailliste. For at
+# st&oslash;tte s&aring;danne maillister, definer Reply-To: adressen
+# her, og vælg Egendefineret adresse i indstillingen reply_goes_to_list.
+# 
+# Bem&aelig;rk at hvis den oprindelige meddelse indeholder et Reply-To:
+# felt, vil det ikke &aelig;ndres.
 reply_to_address = ''
 
-# 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.
+# S&aelig;t denne til 'ja' hvis listen skal bruges som en "paraply" for
+# flere andre lister. N&aring;r denne er sat, vil bekr&aelig;ftigelser
+# og meddelelser med password blive sendt til en egen adresse som
+# beregnes ud fra e-mailadressen som er tilmeldt listen - v&aelig;rdien
+# af indstillingen "umbrella_member_suffix" bruges til dette. Denne
+# v&aelig;rdi tilf&oslash;jes til medlemmets kontonavn (det som
+# st&aring;r f&oslash;r @-tegnet).
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 umbrella_list = 0
 
-# 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".
+# N&aring;r "umbrella_list" indikerer at denne liste har andre
+# maillister som medlemmer, er det som regel &oslash;nskelig at
+# administrative meddelelser som f.eks. bekr&aelig;ftigelser og password
+# reminders ikke sendes til selve listen som er medlem, men til
+# administratoren for listen. Hvis dette er tilf&aelig;ldet, bruges
+# v&aelig;rdien af denne indstilling til at bestemme adressen sådan at
+# 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".
 umbrella_member_suffix = '-owner'
 
-# 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.
+# S&aelig;tt denne til hvis du vil have at password reminder skal sendes
+# til medlemmene en gang hver m&aring;ned. Husk at medlemmene kan
+# ogs&aring; selv frav&aelig;lge dette.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 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.
+# Tekst du skriver her vil blive tilf&oslash;jet &oslash;verst i
+# velkomsthilsenen der sendes til nye medlemmer. Velkomshilsenen
+# indeholder allerede viktige adresser og URLer knyttet til maillisten,
+# s&aring; sådan information er det ikke n&oslash;dvendig at inkludere
+# her. Her kan du indl&oslash;gge f.eks. oplysning om etikette eller
+# regler for brug af listen, o.l.
+# 
+# Bem&oslash;rk: Liniene i denne tekst vil brydes efter f&oslash;lgende
+# regler:
 # 
-# 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.
+# Hvert afsnit udfyldes s&aringdan at ingen linie er lenger en 70 tegn.
+# Enhver linie der begynder med blanke tegn udfyldes ikke. Blanke linier
+# adskiller afsnitt.
 # 
 welcome_msg = ''
 
-# 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.
+# S&aelig;t kun denne til 'Nej' hvis du skal il&aelig;gge nye medlemmer
+# manuelt, og ikke vil have de skal f&aring; dette 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.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 send_welcome_msg = 1
 
-# Text sent to people leaving the list.  If empty, no special text will
-# be added to the unsubscribe message.
+# Tekst der sendes til medlemmer der framelder sig fra listen. Hvis
+# denne er tom, l&aelig;gges det ikke noget tekst til frameldelsen.
 goodbye_msg = ''
 
-# Send goodbye message to members when they are unsubscribed?
+# Sende afskedshilsen til medlemmer n&aring;r de frameldes?
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 send_goodbye_msg = 1
 
-# 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.
+# Der udsendes en reminder til listemoderatoren(e) (og
+# listeadministratoren(e)) dagligt om foresp&oslash;rsler der af en
+# eller anden grund venter p&aring; behandling. V&aelig;lger du "Ja",
+# vil listeadminstratoren ogs&aring; motdtage en meddelelse s&aring;
+# snart en foresp&oslash;rsel kommer ind.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 admin_immed_notify = 1
 
-# Should administrator get notices of subscribes and unsubscribes?
+# Skal listeadministratoren(e) ogs&aring; modtage meddelelse om nye
+# medlemmer der tilmelder sig og gamle medlemmer som framelder sig?
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 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.
+# Besked om at en meddelelse skal godkendes sendes ud til afsenderen
+# s&aring;fremt meddelelsen stoppes pga. noget andet end listemoderation
+# eller spam filtre. S&aelig;ttes denne indstilling til 'Nej', vil
+# afsender overhovedet ikke modtage denne besked.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 respond_to_post_requests = 1
 
-# 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.
+# Når dette valg er aktiveret, vil alt e-mail til listen blive moderert.
+# 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-moderasjon" kan da hjælpe dig at fjerne usaglige meddelelser
+# til listen, og på den måden dysse en ophedet diskusion ned.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 emergency = 0
 
-# When a new member is subscribed to this list, their initial set of
-# options is taken from the this variable's setting.
+# Når et nyt medlem tilmeldes listen, blir medlemmets indstillinger
+# taget herfra.
 new_member_options = 256
 
-# 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.
+# Filter for administrative meddelelser vil unders&oslash;ge om
+# meddelelsen egentligt er ment som en administrativ foresp&oslash;rgsel
+# (f.eks. tilmelding, framelding, o.l.), og is&aring;fald sende
+# meddelelsen til administratoren i stedet.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 administrivia = 1
 
-# Maximum length in kilobytes (KB) of a message body.  Use 0 for no
-# limit.
+# Maximum st&oslash;rrelse i kilobytes (KB) for indholdet i e-mail der
+# sendes til listen. Brug verdien '0' for ikke at have en
+# begr&aelig;nsning.
 max_message_size = 40
 
-# 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.
+# "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; denne maskinen. Denne
+# indstillingen kan v&aelig;re nyttig hvis maskinen har flere navne.
 host_name = 'jones.dk'
 
-# 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).
+# I RFC 2369 defineres en r&aelig;kke List-* felter i
+# meddelelseshovedet, der normalt tilf&oslash;jes hver meddelelse der
+# sendes ud via listen. Disse felter kan hj&aelig;lpe de brugere af
+# listen der benytter et e-mailprogram som f&oslash;lger denne standard.
+# Disse felter b&oslash;r derfor altid v&aelig;re med.
+# 
+# Ikke alle e-mailprogrammer f&oslash;lger denne standard. Er det mange
+# af medlemmene p&aring; listen der benytter s&aring;danne
+# e-mailprogrammer, der ikke kan h&aring;ndtere disse felter i
+# meddelelseshovedet, kan det v&aelig;re du vil v&aelig;lge at udelade
+# dem. Men du b&oslash;r f&oslash;rst fors&oslash;ge at l&aelig;re og
+# forklare medlemmene 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 disse felter, men dette anbefales ikke (denne
+# muligheten kan faktisk ogs&aring; blive fjernet i senere versioner).
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 include_rfc2369_headers = 1
 
-# 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.)
+# List-Post: feltet er et af felterne anbefalet i RFC 2369. Visse
+# e-maillister (som f.eks. kun bruges til offentligørelser), er det kun
+# visse personer der har lov til at sende til; de som er medlem af
+# listen har generelt ikke lov til at sende til listen. For disse
+# lister, er List-Post: feltet forvirrende. I visse tilf&aelig;lde kan
+# det være forvirrende at s&aelig;tte denne indstilling til Nej,
+# s&aring; feltet ikke tilføjes. (Dette påvirker ikke andre List-*:
+# felter.)
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 include_list_post_header = 1
 
 ## Language options
 #
-# 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.
+# Underst&oslash;ttelse for flere sprog. (Internationalisering)
+
+# Dette er standardsproget som benyttes for denne mailliste. Hvis mer
+# 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.
 preferred_language = 'en'
 
-# These are all the natural languages supported by this list. Note that
-# the default language must be included.
+# Her er alle spr&aring;gene denne listen har underst&oslash;ttelse for.
+# Bem&aelig;rk at standardsproget skal v&aelig;re med.
 available_languages = ['en', 'da']
 
-# 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.
+# Hvis standardsproget for din mailliste benytter et andet tegns&aelig;t
+# end ASCII og tittel prefixet for listen indeholder tegn som ikke
+# findes i ASCII-tegns&aelig;ttet, vil prefixet alltid blive kodet i
+# henhold til den relevante standard. Hvis tittel prefixet kun
+# indeholder ASCII tegn, kan det imidlertid ske at du ønsker at sætte
+# dette valg til Aldrig for at undgå koding. Dette kan gøre titlen lidt
+# mere læselig for brugere med e-mailprogrammer der ikke takler andre
+# tegnsæt end ASCII på en rigtig måde.
+# 
+# Bemærk imidlertid at hvis din mailliste modtager både kodede og
+# ukodede tittel felt, kan det være bedst at vælge Efter behov. Med
+# denne indstilling vil Mailman ikke kode ASCII prefixer hvis resten af
+# tittelfeltet kun indeholder ASCII tegn, men vil kode prefixet hvis det
+# indeholder tegn som ikke er ASCII tegn. På denne måde undgås en [...]
+# i standarderne, som forårsager at visse e-mailprogrammer vil vise
+# ekstra eller manglende mellemrum imellom tittel prefixet og det
+# oprindelige tittelfelt.
 #
-# legal values are:
-#    0 = "Never"
-#    1 = "Always"
-#    2 = "As needed"
+# gyldige værdier:
+#    0 = "Aldrig"
+#    1 = "Altid"
+#    2 = "Efter behov"
 encode_ascii_prefixes = 0
 
 ## Nondigest options
 #
-# Policies concerning immediately delivered list traffic.
+# Regler for levering i normal-modus.
 
-# Can subscribers choose to receive mail immediately, rather than in
-# batched digests?
+# Kan medlemmer vælge normal-modus?
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 nondigestable = 1
 
-# 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:
+# 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:
 # 
 # 
 # real_name - The "pretty" name of the list; usually the list name with
@@ -381,9 +405,10 @@ nondigestable = 1
 # 
 msg_header = ''
 
-# 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:
+# Tekst som tilf&aelig;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:
 # 
 # 
 # real_name - The "pretty" name of the list; usually the list name with
@@ -413,42 +438,44 @@ msg_footer = """_______________________________________________
 
 ## Digest options
 #
-# Batched-delivery digest characteristics.
+# Opsætning af sammendrag-modus.
 
-# Can list members choose to receive list traffic bunched in digests?
+# Kan medlemmer af listen vælge at f&aring; tilsendt sammendrag i stedet
+# for?
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 digestable = 1
 
-# Which delivery mode is the default for new users?
+# Hvilken modus er standard for nye brugere?
 #
-# legal values are:
-#    0 = "Regular"
-#    1 = "Digest"
+# gyldige værdier:
+#    0 = "Normal"
+#    1 = "Sammendrag"
 digest_is_default = 0
 
-# When receiving digests, which format is default?
+# Hvilket format skal benyttes som standard for samle-email?
 #
-# legal values are:
-#    0 = "Plain"
+# gyldige værdier:
+#    0 = "Ren tekst"
 #    1 = "MIME"
 mime_is_default_digest = 0
 
-# How big in Kb should a digest be before it gets sent out?
+# Hvor stor (i Kb) m&aring; en samle-email h&oslash;jst v&aelig;re
+# f&oslash;r den udsendes?
 digest_size_threshhold = 30
 
-# Should a digest be dispatched daily when the size threshold isn't
-# reached?
+# Skal der sendes en samle-email dagligt, selv om st&oslash;rrelsen ikke
+# er opn&aring;et?
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 digest_send_periodic = 1
 
-# Text attached (as an initial message, before the table of contents) to
-# the top of digests. This text can include Python format strings which
+# Tekst som l&aelig;gges til &oslash;verst i samle-emailen, f&oslash;r
+# indholdsfortegnelsen.This text can include Python format strings which
 # are resolved against list attributes.  The list of substitutions
 # allowed are:
 # 
@@ -475,9 +502,10 @@ digest_send_periodic = 1
 # 
 digest_header = ''
 
-# 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:
+# Tekst der tilføjes nederst i hver samle-e-mail, som sidste
+# information.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
@@ -505,274 +533,277 @@ digest_footer = """_______________________________________________
 %(real_name)s@%(host_name)s
 %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s"""
 
-# When a new digest volume is started, the volume number is incremented
-# and the issue number is reset to 1.
+# N&aring;r et nyt volume startes, &oslash;ges volume nummeret, og
+# udgavenummeret s&aelig;ttes til 1.
 #
-# legal values are:
-#    0 = "Yearly"
-#    1 = "Monthly"
-#    2 = "Quarterly"
-#    3 = "Weekly"
-#    4 = "Daily"
+# gyldige værdier:
+#    0 = "&Aring;rlig"
+#    1 = "M&aring;nedlig"
+#    2 = "Kvartalsvis"
+#    3 = "Ugentlig"
+#    4 = "Daglig"
 digest_volume_frequency = 1
 
 ## Privacy options
 #
-# 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.
-
-# Advertise this list when people ask what lists are on this machine?
+# Her kan du bestemme hvad der kr&oslash;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&oslash;lder
+# arkivet og arkivering.
+
+# Vise denne mailliste n&aring;r nogn beder om at se en oversigt over
+# maillister p&aring; denne maskine?
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 advertised = 1
 
-# 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.
+# bek&aelig;ftigelse(*) - bekr&aelig;ftigelse af e-mail er
+# n&oslash;dvendig godkendelse - ans&oslash;gkning om medlemskabp skal
+# godkendes af listeadministrator (eller evt. listemoderator)
+# bekr&aelig;ftigelse+godkendelse - b&aring;de bekr&aelig;ftelse
+# p&aring; e-mail og godkendelse af listeadministrator (evt.
+# listemoderator) er nun&oslash;dvendig
+# 
+# (*) n&aring;r nogen vil tilmelde sig en liste, sender Mailman en
+# meddelelse med et uniktidentifikator som de skal opgive for at
+# bekr&oslash;fte tilmeldingen. P&aring; denne m&aring;den vil det da
+# ikke v&aelig;re muligt at tilmelde nogen til listen imod deres vilje.
 #
-# legal values are:
-#    1 = "Confirm"
-#    2 = "Require approval"
-#    3 = "Confirm and approve"
+# gyldige værdier:
+#    1 = "Bekr&aelig;ftigelse"
+#    2 = "Godkendelse"
+#    3 = "Bekr&aelig;ftigelse og godkendelse"
 subscribe_policy = 1
 
-# 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.
+# N&aring;r medlemmer &oslash;nsker at forlade en mailliste, sender de
+# en ans&oslash;gning om framelding, enten via web, eller via e-mail.
+# Normalt er det best at disse ans&oslash;gninger automatisk godkendes,
+# s&aring; meldemmer kan udmelde sig n&aring;r de &oslash;nsker det
+# (mange &oslash;nsker selv at kunne administrere en frameldelse. For
+# nogen f&aring; maillister kan det aligevel v&aelig;re aktuelt at have
+# kontrol over om medlemmer kan melde sig selv ud eller ikke. En liste
+# som alle ansatte i et firma M&Aring; v&aelig;re medlem af, er et
+# eksempel p&aring; en s&aring;dan liste.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 unsubscribe_policy = 0
 
-# 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.
+# Alle e-mailadresser som angives her vil blive udelukket fra listen, og
+# kan ikke tilmelde sig. Indtast e-mailadresser, en per linie, start
+# linien med tegnet ^ for at angive et regexp-udtryk der skal passe med
+# afsenderadressen.
 ban_list = []
 
-# When set, the list of subscribers is protected by member or admin
-# password authentication.
+# Hvis denne indstilling er sat til, vil listen over medlemmer af
+# e-maillisten blive beskyttet af medlemmenes eller adminstratorens
+# password.
 #
-# legal values are:
-#    0 = "Anyone"
-#    1 = "List members"
-#    2 = "List admin only"
+# gyldige værdier:
+#    0 = "Alle"
+#    1 = "Kun medlemmer af listen"
+#    2 = "Kun listeadministrator"
 private_roster = 0
 
-# 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.
+# V&aelig;lger du 'Ja' her, vil medlemmers e-mailadresse omskrives
+# n&aring;r de vises i en oversigt p&aring; websidene (b&aring;de som
+# tekst og i linker), s&aring; de ikke er nemme at tolke som
+# e-mailadresser. Meningen med dette er at undg&aring; at e-mailsniffere
+# der gennemg&aring;r websider for at finde e-mailadresser (og derefter
+# bruge dem til at udsende spam/junk mail) til ikke at opsamle
+# medlemmenes e-mailadresser.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 obscure_addresses = 1
 
 ## Privacy options
 #
-# 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.
+# N&aring;r en meddelelse sendes til maillisten, g&aring;r den igennem
+# en r&aelig;kke trin for at afg&oslash;re om moderatoren m&aring;
+# godkende meddelelsen eller ikke. Her finder du indstillinger for 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 de sendes til listen.
+# 
+# <p>e-mail som ikke er sendt af medlemmer af listen, kan automatisk bli
+# <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">sendt
+# retur</a>, eller <a
+# href="?VARHELP=privacy/sender/discard_these_nonmembers">afvist</a>,
+# enten individuelt eller som en gruppe. All e-mail fra ikke-medlemmer,
+# som ikke specifikt bliver godkent, sendes retur, eller afvist, 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 il&aelig;gger du en e-mailadresse per
+# linie. Du kan ogs&aring; il&aelig;gge  <a
+# href="http://www.python.org/doc/current/lib/module-re.html">Python
+# regexp-uttrykk</a>. Begynd is&aring;fald linien med tegnet ^ for at
+# markere at det er et s&aring;dan udtryk. N&aring;r du benytter
+# backslash, skriv da lige som i rene strings (Python raw strings)
+# (normalt kun &eacute;n backslash af gangen).
+# 
+# <p>Bem&aelig;rk: match p&aring; 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-mail fra medlemmet kan sendes direkte til e-maillisten, eller om de
+# f&oslash;rst skal godkendes af listemoderatoren. N&aring;r
+# moderationsflaget er sat til, skal e-mail fra medlemmet godkendes af
+# listemoderatoren f&oslash;r det udsendes til alle p&aring; listen. Som
+# listeadminsitrator kan du for hvert enkelt medlem bestemme om
+# medlemmets e-mail skal modereres eller ikke. N&aring;r et nyt medlem
+# tilmeldes til 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
+# Administrere medlemmer siden.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 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.
 # 
-# Discard -- this simply discards the message, with no notice sent to
-# the post's author.
+# Holde tilbage -- meldingen holdes tilbage for godkendelse af
+# listemoderatoren(e). Afslå -- meldingen sendes automatisk retur til
+# afsender. Begrundelsen der sendes kan du skrive selv Slette --
+# meddelelsen blir afvist uden at give besked om dette til afsender.
 # 
 #
-# legal values are:
-#    0 = "Hold"
-#    1 = "Reject"
-#    2 = "Discard"
+# gyldige værdier:
+#    0 = "Holde&nbsp;tilbage"
+#    1 = "Afvis"
+#    2 = "Kassere"
 member_moderation_action = 0
 
-# 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.
+# Tekst som skal sendes med meldingen om retur som sendes til modereede
+# medlemmer af listen.
 member_moderation_notice = ''
 
-# 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.
+# e-mail fra disse ikke-medlemmer vil automatisk blive godkendt.
+# Il&aelig;g e-mailadresser, en per linie, start linien med tegnet ^ for
+# at angive et regexp-uttryk som skal passe med afsenderadressen.
 accept_these_nonmembers = []
 
-# 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.
+# e-mail fra disse ikke-medlemmer vil automatisk blive holdt tilbage for
+# vurdering af listemoderatorene. Afsenderen vil modtage en meddelelse
+# om dette, med bl.a. instruktioner om hvordan han/hun kan
+# tilbagetr&aelig;kke sin e-mails. Indtast e-mailadresser, en per linie,
+# start linien med tegnet ^ for at angive et regexp-uttrykk som skal
+# passe med afsenderadressen.
 hold_these_nonmembers = []
 
-# 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.
+# 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 spam-afsendere,
+# de b&oslash;r automatisk afvises. Indtast e-mailadresser, en per
+# linie, start linien med tegnet ^ for &aring; angiv et regexp-uttrykk
+# som skal passe med afsenderadressen.
 reject_these_nonmembers = []
 
-# 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.
+# e-mail fra disse ikke-medlemmer vil automatisk blive afvist. Det vil
+# sige at meddelelsen afvises uden nogen form for tilbagemelding, men
+# listemoderatorene kan (om ønskeligt) modtage en kopi af den afviste
+# e-mail. Tilf&oslash;je e-mailadresser, en per linie, start linien med
+# tegnet ^ for at angive et regexp-uttryk der skal passe med
+# afsenderadressen.
 discard_these_nonmembers = []
 
-# 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.
+# N&aring;r en e-mail fra et ikke-medlem blir modtaget, sammenlignes
+# e-mailens afsender med listen over e-mailadresser der skal godkendes,
+# holdes tilbage, afvises (sendes i retur), og afvises. Hvis
+# afsenderadressen ikke passer med den der er opgivet i listene, blir
+# f&oslash;lgende afg&oslash;relse taget.
 #
-# legal values are:
-#    0 = "Accept"
-#    1 = "Hold"
-#    2 = "Reject"
-#    3 = "Discard"
+# gyldige værdier:
+#    0 = "Godkende"
+#    1 = "Holde&nbsp;tilbage"
+#    2 = "Afvis"
+#    3 = "Kassere"
 generic_nonmember_action = 1
 
-# Should messages from non-members, which are automatically discarded,
-# be forwarded to the list moderator?
+# Skal meddelelser fra ikke-medlemmer, som automatisk afvises, også
+# sendes til listemoderatoren?
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 forward_auto_discards = 1
 
 ## Privacy options
 #
-# This section allows you to configure various filters based on the
-# recipient of the message.
+# Her kan du ops&aelig;tte filtrering baseret på modtaeren af
+# meddelelsen.
 
-# 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.
+# Meget (faktisk det meste af) spam/junk mail har ikke de endelige
+# modtagere i modtagerfelterne. Faktisk s&aring; indeholder felterne To:
+# og/eller Cc: oftest en fuldst&aelig;ndig 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(e), men vil
+# aligevel blive fanget og blokkere det meste af spam/junk mail.
 # 
-# 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 ville 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
+# alias for listen.
 # 
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 require_explicit_destination = 1
 
-# 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.
+# Alternative e-mailadresser som godtages n&aring;r
+# 'require_explicit_destination' er sat til. Som v&aelig;rdi for denne
+# indstilling skal du opgive regexp-uttryk ("regular expressions"), et
+# udtryk per linie, der sammenlignes imod 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 imod den f&oslash;rste
+# del (det som st&aring;r f&oslash;r '@') af modtageradressen. Hvis
+# sammenligningen ikke lykkes, eller hvis udtrykket ikke indholder en
+# '@', sammenlignes udtrykket med hele modtageradressen.
+# 
+# Sammenligning kun imod den f&oslash;rste del af en modtageradresse
+# underst&oslash;ttes ikke i fr&aelig;mtidige udgaver af Mailman, vil
+# kun sammenligning imod hele modtageradresser blive
+# underst&oslash;ttet.
 acceptable_aliases = ''
 
-# If a posting has this number, or more, of recipients, it is held for
-# admin approval.  Use 0 for no ceiling.
+# Hvis en mail der er sendt til listen indeholder s&aring; mange
+# modtagere som, eller flere modtagere end, denne værdi, holdes malen
+# tilbage så listeadministratoren eventuelt kan godkende den. Brug
+# værdien 0 for ingen begrænsning.
 max_num_recipients = 10
 
 ## Privacy options
 #
-# 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.
-# 
+# Her kan du opsætte forskellige anti-spam filtre, som kan være til
+# hjælp for 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
@@ -785,16 +816,20 @@ max_num_recipients = 10
 # match.
 header_filter_rules = []
 
-# 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.
+# Brug denne indstilling til at fra-filtrere mail til listen, baseret
+# p&aring; indholdet af et eller flere felter i mailhovedet. Her skal du
+# skrive regexp-uttryk (regular expressions), et per linie, som
+# sammenlignes mod det aktuelle felt. Sammenligningen sk&aelig;lner ikke
+# imellem store og sm&aring; bogstaver. Linier der begynder med '#'
+# sammenlignes ikke.
 # 
-# For example:to: .*@public.com  says to hold all postings with a To:
-# mail header containing '@public.com' anywhere among the addresses.
+# For eksempel: udtrykket to: .*@public.com fort&aelig;ller at alt mail
+# som indeholder '@public.com' i To: feltet, skal holdes tilbage til
+# godkendelse.
 # 
-# 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.
+# Bem&aelig;rk: blanke tegn i starten af regexp-udtrykket fjernes. Dette
+# kan man undg&aring; p&aring; flere m&aring;ter, f.eks. ved at bruge
+# escape-tegn eller parenteser.
 bounce_matching_headers = """# Lines that *start* with a '#' are comments.
 to: friend@public.com
 message-id: relay.comanche.denmark.eu
@@ -803,54 +838,56 @@ from: .*@uplinkpro.com"""
 
 ## Bounce options
 #
-# 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.
+# Disse regler bestemmer hvordan automatisk behandling af returmails
+# gj&oslash;res. Her er en oversigt over hvordan funktionen er.
+# 
+# <p>N&aring;r Mailman modtager en returmail, blir to ting
+# fors&oslash;kt tolket. Det ene er e-mailadressen til medlemmet som
+# egentlig skulle modtage e-mailen, og det andet er &aring;rsagen til
+# problemet. &Aring;rsagen tolkes til at v&aelig;re <em>alvorlig</em>
+# eller <em>lett</em> alt efter om &aring;rsagen er af kritisk eller af
+# mindre alvorlig art. Såfremt der er tvivl, tolkes &aring;rsaken som
+# alvorlig.
+# 
+# <p>Hvis ingen e-mailadresse kan hentes ud af meddelelsen, blir den
+# normalt afvist. Ellers, vil medlemmet som har e-mailadressen f&aring;
+# en <em>returtal</em>, og hver gang en returmeddelelse kommer vil
+# tallet &oslash;ges. Alvorlige &aring;rsaker f&oslash;rer til at tallet
+# &oslash;ges med 1, lette &aring;rsaker f&oslash;rer til at det
+# &oslash;kes med 0.5. Dette sker kun &eacute;n gang per dag, s&aring;
+# selv om det 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;ttest til igen.
+# Medlemmet vil med j&aelig;vne mellemrum modtage melding 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>Det er en vigtig indstilling til; efter en vis tid -- hvis ingen
+# returmeddelelser dukker op i l&oslash;bet af denne tid -- anses
+# returinformation som <a
+# href="?VARHELP=bounce/bounce_info_stale_after">udg&aring;et</a> og
+# afvises. Ved at justere denne værdi, og sætte en grænse for
+# returantallet, kan du bestemme hvor lang tid der skal gå f&oslash;r
+# levering til et medlem stoppes. Begge disse værdier skal du justere
+# alt efter hvor ofte og hvor meget e-mail der sendes til din liste.
+
+# Ved at sætte denne værdi til Nej, sætter du alt automatisk tolking af
+# returmeddelelser for denne liste fra. Bemærk at såfremt meddelelser
+# afvises vil listeadministratoren ikke blive forstyrret med dem.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 bounce_processing = 1
 
 # Each subscriber is assigned a bounce score, as a floating point
@@ -866,351 +903,345 @@ bounce_processing = 1
 # mailing list.
 bounce_score_threshold = 5.0
 
-# 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.
+# Antal dage f&oslash;r returinformation afvises såfremt der ikke dukker
+# flere returmails op. Dette tal skal v&aelig;re et heltal.
 bounce_info_stale_after = 7
 
-# 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.
+# Hvor mange Levering til dig er stoppet advarsler der skal sendes til
+# et medlem f&oslash;r medlemmet frameldes fra listen. S&aelig;t denne
+# værdi til 0 for at fjerne et medlem fra listen umiddelbart
+# s&aring;fremt der kommer returmails fra medlemmets e-mailadresse.
+# Dette tal skal være et heltal.
 bounce_you_are_disabled_warnings = 3
 
-# The number of days between sending the Your Membership Is Disabled
-# warnings.  This value must be an integer.
+# Antal dage imellem hver gang en Levering til dig er stoppet advarsel
+# skal sendes ud. Dette tal skal være et heltal.
 bounce_you_are_disabled_warnings_interval = 7
 
-# 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.
+# Mailmans automatiske returmailhåndtering er meget robust, men det er
+# aligevel umuligt at genkende alle typer returmails der kommer. Du bør
+# angive Ja her, af to grunde: 1) Hvis det virkelig er en permanent
+# returmail fra et medlem af listen, bør du antageligt manuelt udmelde
+# medlemmet fra listen, og 2) du vil måske sende meddelelse til
+# udviklerne af Mailman sådan at returmails automatisk genkendes af
+# Mailman i senere versioner. Hvis du ikke vil gøre nogen af delene, sæt
+# da denne indstilling til Nej. Så vil alle returmails afvises
+# automatisk uden videre behandling. Bem&aelig;rk: Denne indstilling vil
+# også indvirke på alt e-mail der sendes til listens -admin adresse. Den
+# adresse er gammel og udgået, men det kan være at nogen fortsat vil
+# sende e-mail til den. Hvis nogen gør det, og du har sat denne
+# indstilling til Nej, vil disse mails også blive afvist. Måske vil du
+# også opsætte et automatisk svar på e-mail sendt til -owner og -admin
+# adresserne.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 bounce_unrecognized_goes_to_list_owner = 1
 
-# 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.
+# Ved at sætte denne til Nej, fravælges beskeden der normalt sendes til
+# ejeren(e) af listen, når afsending 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.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 bounce_notify_owner_on_disable = 1
 
-# 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.
+# Ved at sætte denne til Nej, fravælges beskeden der normalt sendes til
+# ejeren(e) af listen, når et medlem frameldes fra listen på grund af
+# for mange returmails. Der vil til gengæld altid blive forsøgt afsendt
+# en e-mail med besked til medlemmet.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 bounce_notify_owner_on_removal = 1
 
 ## Archive options
 #
-# List traffic archival policies.
+# Regler for arkivering
 
-# Archive messages?
+# Arkivere e-mail i et arkiv?
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 archive = 1
 
-# Is archive file source for public or private archival?
+# Skal filen arkiveres i et privat eller i et offentlig arkiv?
 #
-# legal values are:
-#    0 = "public"
-#    1 = "private"
+# gyldige værdier:
+#    0 = "offentlig"
+#    1 = "privat"
 archive_private = 0
 
-# How often should a new archive volume be started?
+# Hvor ofte skal arkivet deles op?
 #
-# legal values are:
-#    0 = "Yearly"
-#    1 = "Monthly"
-#    2 = "Quarterly"
-#    3 = "Weekly"
-#    4 = "Daily"
+# gyldige værdier:
+#    0 = "&Aring;rlig"
+#    1 = "M&aring;nedlig"
+#    2 = "Kvartalsvis"
+#    3 = "Ugentlig"
+#    4 = "Daglig"
 archive_volume_frequency = 0
 
 ## Gateway options
 #
-# Mail-to-News and News-to-Mail gateway services.
+# e-mail-Til-Nyhedsgruppe og Nyhedsgruppe-Til-e-mail tjeneste.
 
-# 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.
+# 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.
 nntp_host = ''
 
-# The name of the Usenet group to gateway to and/or from.
+# Navn p&aring; nyhedsgruppe der skal sendes til og/eller fra.
 linked_newsgroup = ''
 
-# Should new posts to the mailing list be sent to the newsgroup?
+# Skal nye mail til denne liste sendes til nyhedsgruppen?
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 gateway_to_news = 0
 
-# Should new posts to the newsgroup be sent to the mailing list?
+# Skal nye meddelelser til nyhedsgruppen sendes til denne mailliste?
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 gateway_to_mail = 0
 
-# 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.
+# 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&aring;t da 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
+# Moderet, vil en ekstra meddelelse holdes tilbage i
+# godkendelsesprocessen. Alt mail sendt til maillisten skal godkendes
+# f&oslash;r de sendes til nyhedsgruppen, eller til medlemmene af
+# listen.
+# 
+# Vær opm&aelig;rksom p&aring; at hvis mailhovedet i mailen har et
+# Approved: felt med listens administrative password, 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 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 meddelelseshovedet.
 #
-# legal values are:
-#    0 = "None"
-#    1 = "Open list, moderated group"
-#    2 = "Moderated"
+# gyldige værdier:
+#    0 = "Ingen"
+#    1 = "Åben liste, modereret nyhedsgruppe"
+#    2 = "Modereret"
 news_moderation = 0
 
-# 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.
+# Mailman tilføjer normalt en tekst du selv 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 sette denne indstilling
+# til Nej hvis du ikke ønsker emne prefix tilføjet til mail som sendes
+# til Usenet. Sætter du emne prefix for listen til off, vil opsamlet
+# meddelelser heller ikke få præfix tilføjet.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 news_prefix_subject_too = 1
 
 ## Autoreply options
 #
-# Auto-responder characteristics.<p>
+# Indstillinger for automatiske svar.<p>
 # 
-# 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>
+# 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 epostadresse</em>
+# <li><b>owneremail</b> - <em>listens -owner epostadresse</em> </ul>
 # 
-# <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.
+# <p>Du kan enten skrive teksten direkte i tekstboksene, eller du kan
+# angive navnet p&aring; en fil som indeholder teksten. Denne file vil
+# s&aring; blive indl&aelig;st i tekstboksen, fra dit lokale filsystem.
 
-# Should Mailman send an auto-response to mailing list posters?
+# Skal Mailman sende et automatisk svar til dem der sender e-mail til
+# listen?
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 autorespond_postings = 0
 
-# Auto-response text to send to mailing list posters.
+# Automatisk svar der skal sendes.
 autoresponse_postings_text = ''
 
-# Should Mailman send an auto-response to emails sent to the -owner
-# address?
+# Skal Mailman sende et automatisk svar p&aring; e-mail der sendes til
+# -owner adressen?
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 autorespond_admin = 0
 
-# Auto-response text to send to -owner emails.
+# Automatisk svar p&aring; e-mail til -owner adressen.
 autoresponse_admin_text = ''
 
-# 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.
+# 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
+# ogs&aring; skal v&aelig;re med i det automatiske svar.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes, w/discard"
-#    2 = "Yes, w/forward"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja, men uden den originale e-mailn"
+#    2 = "Ja, og medtag den originale e-mail"
 autorespond_requests = 0
 
-# Auto-response text to send to -request emails.
+# Automatisk svar p&aring; e-mail til -request adressen.
 autoresponse_request_text = ''
 
-# 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).
+# Antal dage imellem automatisk svar p&aring; e-mail, fra samme
+# afsender, til listen eller til -request/-owner adressene. S&aelig;t
+# denne v&aelig;rdi til 0 (eller et negativt tal) for at sende
+# automatisk svar hver gang.
 autoresponse_graceperiod = 90
 
 ## Contentfilter options
 #
-# 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.  Then, each
-# <tt>multipart/alternative</tt> section will be replaced by just the
-# first alternative that is non-empty after filtering.
-# 
-# <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?
+# Regler for indhold i e-mail sendt til listen.
+# 
+# <p>Filtrering af indhold fungerer således: når listen modtger en
+# e-mail og du har beskyttelse med filtrering af indhold, sammenlignes
+# først eventuelle ved- hæftelser imod <a
+# href="?VARHELP=contentfilter/filter_mime_types">MIME filtre</a>. Hvis
+# en vedhæftelse passer med et af disse filtre, blir vedhæftelsen
+# fjernet.
+# 
+# <p>Derefter sammenlignes eventuelle vedhæftelser imod <a
+# href="?VARHELP=contentfilter/pass_mime_types">gyldige MIME typer</a>,
+# hvis nogen er defineret. Alle vedhæftelser som ikke passer med de
+# angivne MIME typene, blir fjernet.
+# 
+# <p>Efter disse filtre, vil alle tomme <tt>multipart</tt> vedhæftelser
+# blive fjernet. Hvis selve meddelelsen er helt tom efter denne
+# filtrering, vil meddelelsen bli afvist. Derefter vil hvert
+# <tt>multipart/alternative</tt> vedhæftelse blive erstattet af det
+# første alternative som ikke er tomt.
+# 
+# <p>Til slut vil alle <tt>text/html</tt> vedhæftelser som måtte være
+# tilbage i meddelelsen blive konverteret til <tt>text/plain</tt>
+# såfremt <a
+# href="?VARHELP=contentfilter/convert_html_to_plaintext">konvertere til
+# ren tekst</a> er sat til og serveren er konfigurert til at tillade
+# sådanne konverteringer.
+
+# Skal Mailman filtrere indhold i e-mail sendt til listen som angivet
+# nedenfor?
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 filter_content = 0
 
-# 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.
+# Brug denne instilling til at fjerne vedhæftelser der passer til MIME
+# typer. Hver linie skal her indeholde navnet på en MIME type/subtype,
+# f.eks. image/gif. Såfremt du ønsker at fjerne alle vedhæftelser som
+# har en given hoved MIME type, kan du lade være at angive subtype,
+# f.eks. image.
 # 
-# Blank lines are ignored.
+# Blanke linier medtages ikke.
 # 
-# See also <a href="?VARHELP=contentfilter/pass_mime_types"
-# >pass_mime_types for a content type whitelist.
+# Se også gyldige MIME typer for whitelist af MIME typer.
 filter_mime_types = ''
 
-# 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.
+# Brug denne indstilling for at definere hvilke MIME typer der skal være
+# tilladt. Krav og format for filtrering er identisk med MIME filtre.
 # 
-# 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.
+# Bem&aelig;rk: hvis du lægger noget ind her, men ikke angiver
+# multipart, vil al e-mail med vedhæftelser ikke blive medtaget.
 pass_mime_types = """multipart/mixed
 multipart/alternative
 text/plain"""
 
-# Should Mailman convert text/html parts to plain text?  This conversion
-# happens after MIME attachments have been stripped.
+# Skal Mailman konvertere text/html dele til ren tekst? Denne
+# konvertering vil finde sted efter at MIME filteret har fjernet de
+# ønskede dele.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 convert_html_to_plaintext = 1
 
-# One of these actions is take 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.
+# Her bestemmer du hvad der skal ske når en meddelelse filtreres fra af
+# et filter, altså såfremt vedhæftelsen filtreres fra MIME filteret,
+# eller ent vedhæftelse ikke har en af de gyldige MIME typer, eller
+# meddelelsen ender op med at være tom efter filtrering.
+# 
+# Bemærk at det du vælger her ikke vil ske såfremt en meddelelse stadig
+# indeholder noget efter filtrering. Så vil meddelelsen altid sendes
+# videre til listen.
+# 
+# Når meddelelsen afvises, skrives Message-ID'en til den afviste
+# meddelelse til loggen. Når meddelelsen sendes retur eller videresendes
+# til listens ejer, vil en begrundelse altid blive inkluderet i
+# returmail der sendes til afsenderen. Når meddelelserne skal bevares,
+# gemmes de i en specielt køkatalog på disk sådan at
+# serveradministratoren kan se (og måske gøre noget med) meddelelsen,
+# men ellers fjernet. Dette sidste valg er kun tilgængeligt såfremt
+# serveradministratoren har tilladt det.
 #
-# legal values are:
-#    0 = "Discard"
-#    1 = "Reject"
-#    2 = "Forward to List Owner"
-#    3 = "Preserve"
+# gyldige værdier:
+#    0 = "Kassere"
+#    1 = "Afvis"
+#    2 = "Videresend til Listens Ejer"
+#    3 = "Tag hånd om"
 filter_action = 0
 
 ## Topics options
 #
-# 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.
+# Emneord for listen
+
+# Emnefilteret kategoriserer hver e-mail som kommer til listen, efter
+# regexp-uttrykkene du skriver nedenfor. Hvis feltene Subject: eller
+# Keywords: i mailhovedet i en mail passer imod disse udtryk, blir den
+# placeret under dette emne. Hvert medlem af listen kan vælge kun at
+# modtage mail der passer til de &oslash;nskede emner. e-mail som ikke
+# g&aring;r under noget emne, blir ikke leveret.
+# 
+# Bemerk: Dette fungerer kun i normal-modus, ikke i sammendrag-modus.
+# 
+# Indholdet i len kan ogs&aring; unders&oslash;ges for Subject: og
+# Keyword: felter, alt efter hvad indstillingen topics_bodylines_limit
+# er sat til.
 #
-# legal values are:
-#    0 = "Disabled"
-#    1 = "Enabled"
+# gyldige værdier:
+#    0 = "Ikke tilgængelig"
+#    1 = "Tilgængelig"
 topics_enabled = 0
 
-# 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.
-# 
+# Her opgiver du hvor mange linier af mailens indhold som emnefilteret
+# skal s&oslash;ge igennem. En s&oslash;gning stopper n&aring;r s&aring;
+# mange linier er gennoms&oslash;gt, eller n&aring;r det m&oslash;der en
+# linie som ikke ser ud som et meddelelsesfelt. Ved at sætte denne til
+# null (0), vil ingen linier i indholdet blive unders&oslash;gt (dvs.
+# kun Keywords: og Subject: i meddelelseshovedet unders&oslash;ges). Ved
+# at sætte denne værdi til et negativt tal, vil alle linier blive
+# unders&oslash;gt frem til den f&oslash;rste linie som ikke ser ut som
+# et mailhoved-felt.
 topics_bodylines_limit = 5
 
-# 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.
+# Hvert emneord er faktisk et regexp-udtryk, der sammenlignes imod dele
+# af mailen, nemlig feltene Keywords: og Subject: i meldingshodet.
+# Bem&aelig;rk at de f&oslash;ste linier i mailens indhold ogs&aring;
+# kan best&aring; af s&aring;danne "felter", og kan dermed ogs&aring;
+# bli unders&oslash;gt.
 topics = []
 
diff --git a/mailman/assilissat.py b/mailman/assilissat.py
index c0167e6..1b7b219 100644
--- a/mailman/assilissat.py
+++ b/mailman/assilissat.py
@@ -1,362 +1,386 @@
-## "assilissat" mailing list configuration settings -*- python -*-
-## captured on Wed Mar 16 02:40:56 2005
+## Indstillinger for maillisten "assilissat"  -*- python -*-
+## Dato: Thu May  5 09:52:36 2005
 
 ## General options
 #
-# 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 :-)
+# Grundlæggende egenskaber for listen, blant andet en beskrivelse af
+# listen, og hvordan den opf&oslash;rer sig.
+
+# Her kan du f.eks. stave navnet med stort forbogstav, eller ændre visse
+# bogstaver til store sådan at navnet kan udtales p&aring; en rigtig
+# m&aring;de eller at forkortelser fremhæves. Bemærk at dette navn
+# bruges i e-maillistens adresse (f.eks. i bekræftigelser ved
+# tilmeldinger), s&aring; der 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 :-)
 real_name = 'Assilissat'
 
-# 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.
+# Der er to roller forbundet med hver mailliste. Listeadministratorene
+# 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.
+# 
+# Listemoderatorene har begrænset adgang; de kan ikke ændre
+# indstillinger for e-maillisten, men de kan tage sig af
+# foresp&oslash;rgsler i forbindlse med listen, f.eks. ans&oslash;gning
+# om medlemskab, eller godkende/afvise meddelelser der skal godkendes
+# for at kunne udsendes til listen. Listeadministratorene kan ogs&aring;
+# udf&oslash;re disse opgaver.
+# 
+# For at aktivere muligheden for at have listemoderatorer, og p&aring;
+# den m&aring;de opdele arbejdsopgaverne forbundet med listen, skal du
+# s&aelig;tte dit eget moderatorpassword, og angive din
+# e-mailadressen(e) til den/de som skal v&aelig;re listemoderator(er).
+# Bemærk at i tekstboksene nedenfor skal du skrive e-mailadressen(e) til
+# listeadministratoren(e).
 owner = ['inuk@jones.dk']
 
-# 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.
+# Det er to ejerskab forbundet med hver mailliste. Listeadministratorene
+# er dem der har den endelige kontrol over alle indstillingerne for
+# e-mallisten. De kan &aelig;ndre alle indstillinger der er tilgengelige
+# via disse administrative websider.
+# 
+# Listemoderatorene har begr&aelig;nset adgang; de kan ikke &aelig;ndre
+# indstillinger for e-maillisten, men de kan tage sig af
+# foresp&oslash;rgsler ang&aring;ende listen, f.eks. ans&oslash;gning om
+# medlemskab, eller godkende/afvise meddelelser der skal godkendes for
+# at kunne udsendes p&aring; listen. Listeadministratorene kan selvsagt
+# ogs&aring; udf&oslash;re disse opgaver.
+# 
+# For at aktivere muligheten for at have listemoderatorer, og p&aring;
+# den m&aring;den opdele arbejdsopgaverne der er forbundet med listen,
+# skal du s&aelig;tte dit eget moderatorpassword, og indtaste din
+# e-mailadresse(r) til den/de der skal v&aelig;re listemoderator(er).
+# Bemærk at i tekstboksene nedenfor skal du skrive e-mailadressen(e) til
+# listemoderatoren(e).
 moderator = []
 
-# 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.
+# Denne beskrivelsen 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 gj&oslash;re det uklart
+# hvad meningen med maillisten er eller hvad den skal bruges til.
 description = ''
 
-# 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.
+# Teksten tolkes som html bortset fra linieskift, der vil blive
+# &aelig;ndret til html-tag'en '<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. Benytter du html-kode,
+# husk da at gennemse meget grundigt, for fejl (f.eks. manglende
+# slutt-tag's) kan f&oslash;re til at listens informationsside ikke vil
+# vises s&aring;dan som den skal.
 info = ''
 
-# 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 er sat ind foran emne-/tittelfeltet i e-mail der sendes
+# til listen, for at skille e-mailliste-meddelelser i e-mailboksen fra
+# dem der er medlem af listen. Denne tekst b&oslash;r holdes p&aring; et
+# absolut minimum, benytter du f.eks. listens navn og navnet er langt,
+# b&oslash;r du stave det endnu kortere her. Men den b&oslash;r fremover
+# v&aelig;re beskrivende for listen.
 subject_prefix = '[Assilissat] '
 
-# Hide the sender of a message, replacing it with the list address
-# (Removes From, Sender and Reply-To fields)
+# Skjule afsenderen af meddelser, ved at erstatte den med e-maillistens
+# adresse (Dette medfører at alle From:, Sender, og Reply-To: felter
+# fjernes)
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 anonymous_list = 0
 
-# 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.
+# Skal eksisterende Reply-To: felt i meddelelseshovedet fjernes? Hvis ja
+# vil dette blive gjort uanset om Mailman tlføjer et Reply-To: felt
+# eller ikke.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 first_strip_reply_to = 0
 
-# 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.org/essays/reply-to-useful.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.
+# Denne indstillling fort&aelig;ller hvad Mailman skal gj&oslash;re med
+# Reply-To: feltet i meddelelseshovedet 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;dan 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 diskusion omkring
+# emnet. Se Reply-To Munging Considered Useful for modsatte meninger.
+# 
+# Nogle maillister har begr&aelig;nset adgang, med en egen parallell
+# liste beregnet til diskutioner. Eksempler p&aring; dette er 'patches'
+# eller 'checkin' lister, som system for revisionskontrol sender
+# &aelig;ndringer i programmet til, men diskusioner omkring udvikling af
+# programmet sendes til udviklerenes 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 diskusionsliste.
 #
-# legal values are:
-#    0 = "Poster"
-#    1 = "This list"
-#    2 = "Explicit address"
+# gyldige værdier:
+#    0 = "Afsender"
+#    1 = "mail listens adresse"
+#    2 = "Egendefineret adresse"
 reply_goes_to_list = 0
 
-# 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.org/essays/reply-to-useful.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.
+# 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 modifikasion af Reply-To:
+# adressen g&oslash;r det vanskeligere at sende svar kun til afsender.
+# Se 'Reply-To' Munging Considered Harmful for en diskusion omkring
+# temaet. Se Reply-To Munging Considered Useful for modsatte meninger.
+# 
+# Nogen maillister har begr&aelig;nset adgang, med en egen parallell
+# liste beregnet for diskusioner. Eksempler p&aring; dette er 'patches'
+# eller 'checkin' lister, som system for revisionskontrol sender
+# &aelig;ndringer til i programmet, men diskusioner rundt udvikling af
+# programmet sendes til udviklerenes egen mailliste. For at
+# st&oslash;tte s&aring;danne maillister, definer Reply-To: adressen
+# her, og vælg Egendefineret adresse i indstillingen reply_goes_to_list.
+# 
+# Bem&aelig;rk at hvis den oprindelige meddelse indeholder et Reply-To:
+# felt, vil det ikke &aelig;ndres.
 reply_to_address = ''
 
-# 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.
+# S&aelig;t denne til 'ja' hvis listen skal bruges som en "paraply" for
+# flere andre lister. N&aring;r denne er sat, vil bekr&aelig;ftigelser
+# og meddelelser med password blive sendt til en egen adresse som
+# beregnes ud fra e-mailadressen som er tilmeldt listen - v&aelig;rdien
+# af indstillingen "umbrella_member_suffix" bruges til dette. Denne
+# v&aelig;rdi tilf&oslash;jes til medlemmets kontonavn (det som
+# st&aring;r f&oslash;r @-tegnet).
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 umbrella_list = 0
 
-# 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".
+# N&aring;r "umbrella_list" indikerer at denne liste har andre
+# maillister som medlemmer, er det som regel &oslash;nskelig at
+# administrative meddelelser som f.eks. bekr&aelig;ftigelser og password
+# reminders ikke sendes til selve listen som er medlem, men til
+# administratoren for listen. Hvis dette er tilf&aelig;ldet, bruges
+# v&aelig;rdien af denne indstilling til at bestemme adressen sådan at
+# 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".
 umbrella_member_suffix = '-owner'
 
-# 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.
+# S&aelig;tt denne til hvis du vil have at password reminder skal sendes
+# til medlemmene en gang hver m&aring;ned. Husk at medlemmene kan
+# ogs&aring; selv frav&aelig;lge dette.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 send_reminders = 1
 
-# 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.
+# Tekst du skriver her vil blive tilf&oslash;jet &oslash;verst i
+# velkomsthilsenen der sendes til nye medlemmer. Velkomshilsenen
+# indeholder allerede viktige adresser og URLer knyttet til maillisten,
+# s&aring; sådan information er det ikke n&oslash;dvendig at inkludere
+# her. Her kan du indl&oslash;gge f.eks. oplysning om etikette eller
+# regler for brug af listen, o.l.
+# 
+# Bem&oslash;rk: Liniene i denne tekst vil brydes efter f&oslash;lgende
+# regler:
 # 
-# 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.
+# Hvert afsnit udfyldes s&aringdan at ingen linie er lenger en 70 tegn.
+# Enhver linie der begynder med blanke tegn udfyldes ikke. Blanke linier
+# adskiller afsnitt.
 # 
 welcome_msg = ''
 
-# 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.
+# S&aelig;t kun denne til 'Nej' hvis du skal il&aelig;gge nye medlemmer
+# manuelt, og ikke vil have de skal f&aring; dette 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.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 send_welcome_msg = 1
 
-# Text sent to people leaving the list.  If empty, no special text will
-# be added to the unsubscribe message.
+# Tekst der sendes til medlemmer der framelder sig fra listen. Hvis
+# denne er tom, l&aelig;gges det ikke noget tekst til frameldelsen.
 goodbye_msg = ''
 
-# Send goodbye message to members when they are unsubscribed?
+# Sende afskedshilsen til medlemmer n&aring;r de frameldes?
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 send_goodbye_msg = 1
 
-# 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.
+# Der udsendes en reminder til listemoderatoren(e) (og
+# listeadministratoren(e)) dagligt om foresp&oslash;rsler der af en
+# eller anden grund venter p&aring; behandling. V&aelig;lger du "Ja",
+# vil listeadminstratoren ogs&aring; motdtage en meddelelse s&aring;
+# snart en foresp&oslash;rsel kommer ind.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 admin_immed_notify = 1
 
-# Should administrator get notices of subscribes and unsubscribes?
+# Skal listeadministratoren(e) ogs&aring; modtage meddelelse om nye
+# medlemmer der tilmelder sig og gamle medlemmer som framelder sig?
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 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.
+# Besked om at en meddelelse skal godkendes sendes ud til afsenderen
+# s&aring;fremt meddelelsen stoppes pga. noget andet end listemoderation
+# eller spam filtre. S&aelig;ttes denne indstilling til 'Nej', vil
+# afsender overhovedet ikke modtage denne besked.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 respond_to_post_requests = 1
 
-# 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.
+# Når dette valg er aktiveret, vil alt e-mail til listen blive moderert.
+# 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-moderasjon" kan da hjælpe dig at fjerne usaglige meddelelser
+# til listen, og på den måden dysse en ophedet diskusion ned.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 emergency = 0
 
-# When a new member is subscribed to this list, their initial set of
-# options is taken from the this variable's setting.
+# Når et nyt medlem tilmeldes listen, blir medlemmets indstillinger
+# taget herfra.
 new_member_options = 256
 
-# 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.
+# Filter for administrative meddelelser vil unders&oslash;ge om
+# meddelelsen egentligt er ment som en administrativ foresp&oslash;rgsel
+# (f.eks. tilmelding, framelding, o.l.), og is&aring;fald sende
+# meddelelsen til administratoren i stedet.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 administrivia = 1
 
-# Maximum length in kilobytes (KB) of a message body.  Use 0 for no
-# limit.
+# Maximum st&oslash;rrelse i kilobytes (KB) for indholdet i e-mail der
+# sendes til listen. Brug verdien '0' for ikke at have en
+# begr&aelig;nsning.
 max_message_size = 40
 
-# 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.
+# "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; denne maskinen. Denne
+# indstillingen kan v&aelig;re nyttig hvis maskinen har flere navne.
 host_name = 'jones.dk'
 
-# 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).
+# I RFC 2369 defineres en r&aelig;kke List-* felter i
+# meddelelseshovedet, der normalt tilf&oslash;jes hver meddelelse der
+# sendes ud via listen. Disse felter kan hj&aelig;lpe de brugere af
+# listen der benytter et e-mailprogram som f&oslash;lger denne standard.
+# Disse felter b&oslash;r derfor altid v&aelig;re med.
+# 
+# Ikke alle e-mailprogrammer f&oslash;lger denne standard. Er det mange
+# af medlemmene p&aring; listen der benytter s&aring;danne
+# e-mailprogrammer, der ikke kan h&aring;ndtere disse felter i
+# meddelelseshovedet, kan det v&aelig;re du vil v&aelig;lge at udelade
+# dem. Men du b&oslash;r f&oslash;rst fors&oslash;ge at l&aelig;re og
+# forklare medlemmene 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 disse felter, men dette anbefales ikke (denne
+# muligheten kan faktisk ogs&aring; blive fjernet i senere versioner).
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 include_rfc2369_headers = 1
 
-# 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.)
+# List-Post: feltet er et af felterne anbefalet i RFC 2369. Visse
+# e-maillister (som f.eks. kun bruges til offentligørelser), er det kun
+# visse personer der har lov til at sende til; de som er medlem af
+# listen har generelt ikke lov til at sende til listen. For disse
+# lister, er List-Post: feltet forvirrende. I visse tilf&aelig;lde kan
+# det være forvirrende at s&aelig;tte denne indstilling til Nej,
+# s&aring; feltet ikke tilføjes. (Dette påvirker ikke andre List-*:
+# felter.)
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 include_list_post_header = 1
 
 ## Language options
 #
-# 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.
+# Underst&oslash;ttelse for flere sprog. (Internationalisering)
+
+# Dette er standardsproget som benyttes for denne mailliste. Hvis mer
+# 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.
 preferred_language = 'en'
 
-# These are all the natural languages supported by this list. Note that
-# the default language must be included.
+# Her er alle spr&aring;gene denne listen har underst&oslash;ttelse for.
+# Bem&aelig;rk at standardsproget skal v&aelig;re med.
 available_languages = ['en', 'da']
 
-# 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.
+# Hvis standardsproget for din mailliste benytter et andet tegns&aelig;t
+# end ASCII og tittel prefixet for listen indeholder tegn som ikke
+# findes i ASCII-tegns&aelig;ttet, vil prefixet alltid blive kodet i
+# henhold til den relevante standard. Hvis tittel prefixet kun
+# indeholder ASCII tegn, kan det imidlertid ske at du ønsker at sætte
+# dette valg til Aldrig for at undgå koding. Dette kan gøre titlen lidt
+# mere læselig for brugere med e-mailprogrammer der ikke takler andre
+# tegnsæt end ASCII på en rigtig måde.
+# 
+# Bemærk imidlertid at hvis din mailliste modtager både kodede og
+# ukodede tittel felt, kan det være bedst at vælge Efter behov. Med
+# denne indstilling vil Mailman ikke kode ASCII prefixer hvis resten af
+# tittelfeltet kun indeholder ASCII tegn, men vil kode prefixet hvis det
+# indeholder tegn som ikke er ASCII tegn. På denne måde undgås en [...]
+# i standarderne, som forårsager at visse e-mailprogrammer vil vise
+# ekstra eller manglende mellemrum imellom tittel prefixet og det
+# oprindelige tittelfelt.
 #
-# legal values are:
-#    0 = "Never"
-#    1 = "Always"
-#    2 = "As needed"
+# gyldige værdier:
+#    0 = "Aldrig"
+#    1 = "Altid"
+#    2 = "Efter behov"
 encode_ascii_prefixes = 0
 
 ## Nondigest options
 #
-# Policies concerning immediately delivered list traffic.
+# Regler for levering i normal-modus.
 
-# Can subscribers choose to receive mail immediately, rather than in
-# batched digests?
+# Kan medlemmer vælge normal-modus?
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 nondigestable = 1
 
-# 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:
+# 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:
 # 
 # 
 # real_name - The "pretty" name of the list; usually the list name with
@@ -381,9 +405,10 @@ nondigestable = 1
 # 
 msg_header = ''
 
-# 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:
+# Tekst som tilf&aelig;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:
 # 
 # 
 # real_name - The "pretty" name of the list; usually the list name with
@@ -413,42 +438,44 @@ msg_footer = """_______________________________________________
 
 ## Digest options
 #
-# Batched-delivery digest characteristics.
+# Opsætning af sammendrag-modus.
 
-# Can list members choose to receive list traffic bunched in digests?
+# Kan medlemmer af listen vælge at f&aring; tilsendt sammendrag i stedet
+# for?
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 digestable = 1
 
-# Which delivery mode is the default for new users?
+# Hvilken modus er standard for nye brugere?
 #
-# legal values are:
-#    0 = "Regular"
-#    1 = "Digest"
+# gyldige værdier:
+#    0 = "Normal"
+#    1 = "Sammendrag"
 digest_is_default = 0
 
-# When receiving digests, which format is default?
+# Hvilket format skal benyttes som standard for samle-email?
 #
-# legal values are:
-#    0 = "Plain"
+# gyldige værdier:
+#    0 = "Ren tekst"
 #    1 = "MIME"
 mime_is_default_digest = 0
 
-# How big in Kb should a digest be before it gets sent out?
+# Hvor stor (i Kb) m&aring; en samle-email h&oslash;jst v&aelig;re
+# f&oslash;r den udsendes?
 digest_size_threshhold = 30
 
-# Should a digest be dispatched daily when the size threshold isn't
-# reached?
+# Skal der sendes en samle-email dagligt, selv om st&oslash;rrelsen ikke
+# er opn&aring;et?
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 digest_send_periodic = 1
 
-# Text attached (as an initial message, before the table of contents) to
-# the top of digests. This text can include Python format strings which
+# Tekst som l&aelig;gges til &oslash;verst i samle-emailen, f&oslash;r
+# indholdsfortegnelsen.This text can include Python format strings which
 # are resolved against list attributes.  The list of substitutions
 # allowed are:
 # 
@@ -475,9 +502,10 @@ digest_send_periodic = 1
 # 
 digest_header = ''
 
-# 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:
+# Tekst der tilføjes nederst i hver samle-e-mail, som sidste
+# information.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
@@ -505,274 +533,277 @@ digest_footer = """_______________________________________________
 %(real_name)s@%(host_name)s
 %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s"""
 
-# When a new digest volume is started, the volume number is incremented
-# and the issue number is reset to 1.
+# N&aring;r et nyt volume startes, &oslash;ges volume nummeret, og
+# udgavenummeret s&aelig;ttes til 1.
 #
-# legal values are:
-#    0 = "Yearly"
-#    1 = "Monthly"
-#    2 = "Quarterly"
-#    3 = "Weekly"
-#    4 = "Daily"
+# gyldige værdier:
+#    0 = "&Aring;rlig"
+#    1 = "M&aring;nedlig"
+#    2 = "Kvartalsvis"
+#    3 = "Ugentlig"
+#    4 = "Daglig"
 digest_volume_frequency = 1
 
 ## Privacy options
 #
-# 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.
-
-# Advertise this list when people ask what lists are on this machine?
+# Her kan du bestemme hvad der kr&oslash;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&oslash;lder
+# arkivet og arkivering.
+
+# Vise denne mailliste n&aring;r nogn beder om at se en oversigt over
+# maillister p&aring; denne maskine?
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 advertised = 1
 
-# 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.
+# bek&aelig;ftigelse(*) - bekr&aelig;ftigelse af e-mail er
+# n&oslash;dvendig godkendelse - ans&oslash;gkning om medlemskabp skal
+# godkendes af listeadministrator (eller evt. listemoderator)
+# bekr&aelig;ftigelse+godkendelse - b&aring;de bekr&aelig;ftelse
+# p&aring; e-mail og godkendelse af listeadministrator (evt.
+# listemoderator) er nun&oslash;dvendig
+# 
+# (*) n&aring;r nogen vil tilmelde sig en liste, sender Mailman en
+# meddelelse med et uniktidentifikator som de skal opgive for at
+# bekr&oslash;fte tilmeldingen. P&aring; denne m&aring;den vil det da
+# ikke v&aelig;re muligt at tilmelde nogen til listen imod deres vilje.
 #
-# legal values are:
-#    1 = "Confirm"
-#    2 = "Require approval"
-#    3 = "Confirm and approve"
+# gyldige værdier:
+#    1 = "Bekr&aelig;ftigelse"
+#    2 = "Godkendelse"
+#    3 = "Bekr&aelig;ftigelse og godkendelse"
 subscribe_policy = 1
 
-# 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.
+# N&aring;r medlemmer &oslash;nsker at forlade en mailliste, sender de
+# en ans&oslash;gning om framelding, enten via web, eller via e-mail.
+# Normalt er det best at disse ans&oslash;gninger automatisk godkendes,
+# s&aring; meldemmer kan udmelde sig n&aring;r de &oslash;nsker det
+# (mange &oslash;nsker selv at kunne administrere en frameldelse. For
+# nogen f&aring; maillister kan det aligevel v&aelig;re aktuelt at have
+# kontrol over om medlemmer kan melde sig selv ud eller ikke. En liste
+# som alle ansatte i et firma M&Aring; v&aelig;re medlem af, er et
+# eksempel p&aring; en s&aring;dan liste.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 unsubscribe_policy = 0
 
-# 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.
+# Alle e-mailadresser som angives her vil blive udelukket fra listen, og
+# kan ikke tilmelde sig. Indtast e-mailadresser, en per linie, start
+# linien med tegnet ^ for at angive et regexp-udtryk der skal passe med
+# afsenderadressen.
 ban_list = ['afygrobo@hotmail.com', 'hxufesemwr@aaiworldmarket.com', 'nddtu@yahoo.com', 'uznnmnok@aaiworldmarket.com']
 
-# When set, the list of subscribers is protected by member or admin
-# password authentication.
+# Hvis denne indstilling er sat til, vil listen over medlemmer af
+# e-maillisten blive beskyttet af medlemmenes eller adminstratorens
+# password.
 #
-# legal values are:
-#    0 = "Anyone"
-#    1 = "List members"
-#    2 = "List admin only"
+# gyldige værdier:
+#    0 = "Alle"
+#    1 = "Kun medlemmer af listen"
+#    2 = "Kun listeadministrator"
 private_roster = 0
 
-# 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.
+# V&aelig;lger du 'Ja' her, vil medlemmers e-mailadresse omskrives
+# n&aring;r de vises i en oversigt p&aring; websidene (b&aring;de som
+# tekst og i linker), s&aring; de ikke er nemme at tolke som
+# e-mailadresser. Meningen med dette er at undg&aring; at e-mailsniffere
+# der gennemg&aring;r websider for at finde e-mailadresser (og derefter
+# bruge dem til at udsende spam/junk mail) til ikke at opsamle
+# medlemmenes e-mailadresser.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 obscure_addresses = 1
 
 ## Privacy options
 #
-# 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.
+# N&aring;r en meddelelse sendes til maillisten, g&aring;r den igennem
+# en r&aelig;kke trin for at afg&oslash;re om moderatoren m&aring;
+# godkende meddelelsen eller ikke. Her finder du indstillinger for 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 de sendes til listen.
+# 
+# <p>e-mail som ikke er sendt af medlemmer af listen, kan automatisk bli
+# <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">sendt
+# retur</a>, eller <a
+# href="?VARHELP=privacy/sender/discard_these_nonmembers">afvist</a>,
+# enten individuelt eller som en gruppe. All e-mail fra ikke-medlemmer,
+# som ikke specifikt bliver godkent, sendes retur, eller afvist, 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 il&aelig;gger du en e-mailadresse per
+# linie. Du kan ogs&aring; il&aelig;gge  <a
+# href="http://www.python.org/doc/current/lib/module-re.html">Python
+# regexp-uttrykk</a>. Begynd is&aring;fald linien med tegnet ^ for at
+# markere at det er et s&aring;dan udtryk. N&aring;r du benytter
+# backslash, skriv da lige som i rene strings (Python raw strings)
+# (normalt kun &eacute;n backslash af gangen).
+# 
+# <p>Bem&aelig;rk: match p&aring; 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-mail fra medlemmet kan sendes direkte til e-maillisten, eller om de
+# f&oslash;rst skal godkendes af listemoderatoren. N&aring;r
+# moderationsflaget er sat til, skal e-mail fra medlemmet godkendes af
+# listemoderatoren f&oslash;r det udsendes til alle p&aring; listen. Som
+# listeadminsitrator kan du for hvert enkelt medlem bestemme om
+# medlemmets e-mail skal modereres eller ikke. N&aring;r et nyt medlem
+# tilmeldes til 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
+# Administrere medlemmer siden.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 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.
 # 
-# Discard -- this simply discards the message, with no notice sent to
-# the post's author.
+# Holde tilbage -- meldingen holdes tilbage for godkendelse af
+# listemoderatoren(e). Afslå -- meldingen sendes automatisk retur til
+# afsender. Begrundelsen der sendes kan du skrive selv Slette --
+# meddelelsen blir afvist uden at give besked om dette til afsender.
 # 
 #
-# legal values are:
-#    0 = "Hold"
-#    1 = "Reject"
-#    2 = "Discard"
+# gyldige værdier:
+#    0 = "Holde&nbsp;tilbage"
+#    1 = "Afvis"
+#    2 = "Kassere"
 member_moderation_action = 0
 
-# 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.
+# Tekst som skal sendes med meldingen om retur som sendes til modereede
+# medlemmer af listen.
 member_moderation_notice = ''
 
-# 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.
+# e-mail fra disse ikke-medlemmer vil automatisk blive godkendt.
+# Il&aelig;g e-mailadresser, en per linie, start linien med tegnet ^ for
+# at angive et regexp-uttryk som skal passe med afsenderadressen.
 accept_these_nonmembers = []
 
-# 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.
+# e-mail fra disse ikke-medlemmer vil automatisk blive holdt tilbage for
+# vurdering af listemoderatorene. Afsenderen vil modtage en meddelelse
+# om dette, med bl.a. instruktioner om hvordan han/hun kan
+# tilbagetr&aelig;kke sin e-mails. Indtast e-mailadresser, en per linie,
+# start linien med tegnet ^ for at angive et regexp-uttrykk som skal
+# passe med afsenderadressen.
 hold_these_nonmembers = []
 
-# 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.
+# 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 spam-afsendere,
+# de b&oslash;r automatisk afvises. Indtast e-mailadresser, en per
+# linie, start linien med tegnet ^ for &aring; angiv et regexp-uttrykk
+# som skal passe med afsenderadressen.
 reject_these_nonmembers = []
 
-# 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.
+# e-mail fra disse ikke-medlemmer vil automatisk blive afvist. Det vil
+# sige at meddelelsen afvises uden nogen form for tilbagemelding, men
+# listemoderatorene kan (om ønskeligt) modtage en kopi af den afviste
+# e-mail. Tilf&oslash;je e-mailadresser, en per linie, start linien med
+# tegnet ^ for at angive et regexp-uttryk der skal passe med
+# afsenderadressen.
 discard_these_nonmembers = ['afygrobo@hotmail.com', 'hxufesemwr@aaiworldmarket.com', 'nddtu@yahoo.com', 'uznnmnok@aaiworldmarket.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.
+# N&aring;r en e-mail fra et ikke-medlem blir modtaget, sammenlignes
+# e-mailens afsender med listen over e-mailadresser der skal godkendes,
+# holdes tilbage, afvises (sendes i retur), og afvises. Hvis
+# afsenderadressen ikke passer med den der er opgivet i listene, blir
+# f&oslash;lgende afg&oslash;relse taget.
 #
-# legal values are:
-#    0 = "Accept"
-#    1 = "Hold"
-#    2 = "Reject"
-#    3 = "Discard"
+# gyldige værdier:
+#    0 = "Godkende"
+#    1 = "Holde&nbsp;tilbage"
+#    2 = "Afvis"
+#    3 = "Kassere"
 generic_nonmember_action = 0
 
-# Should messages from non-members, which are automatically discarded,
-# be forwarded to the list moderator?
+# Skal meddelelser fra ikke-medlemmer, som automatisk afvises, også
+# sendes til listemoderatoren?
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 forward_auto_discards = 1
 
 ## Privacy options
 #
-# This section allows you to configure various filters based on the
-# recipient of the message.
+# Her kan du ops&aelig;tte filtrering baseret på modtaeren af
+# meddelelsen.
 
-# 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.
+# Meget (faktisk det meste af) spam/junk mail har ikke de endelige
+# modtagere i modtagerfelterne. Faktisk s&aring; indeholder felterne To:
+# og/eller Cc: oftest en fuldst&aelig;ndig 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(e), men vil
+# aligevel blive fanget og blokkere det meste af spam/junk mail.
 # 
-# 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 ville 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
+# alias for listen.
 # 
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 require_explicit_destination = 1
 
-# 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.
+# Alternative e-mailadresser som godtages n&aring;r
+# 'require_explicit_destination' er sat til. Som v&aelig;rdi for denne
+# indstilling skal du opgive regexp-uttryk ("regular expressions"), et
+# udtryk per linie, der sammenlignes imod 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 imod den f&oslash;rste
+# del (det som st&aring;r f&oslash;r '@') af modtageradressen. Hvis
+# sammenligningen ikke lykkes, eller hvis udtrykket ikke indholder en
+# '@', sammenlignes udtrykket med hele modtageradressen.
+# 
+# Sammenligning kun imod den f&oslash;rste del af en modtageradresse
+# underst&oslash;ttes ikke i fr&aelig;mtidige udgaver af Mailman, vil
+# kun sammenligning imod hele modtageradresser blive
+# underst&oslash;ttet.
 acceptable_aliases = ''
 
-# If a posting has this number, or more, of recipients, it is held for
-# admin approval.  Use 0 for no ceiling.
+# Hvis en mail der er sendt til listen indeholder s&aring; mange
+# modtagere som, eller flere modtagere end, denne værdi, holdes malen
+# tilbage så listeadministratoren eventuelt kan godkende den. Brug
+# værdien 0 for ingen begrænsning.
 max_num_recipients = 10
 
 ## Privacy options
 #
-# 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.
-# 
+# Her kan du opsætte forskellige anti-spam filtre, som kan være til
+# hjælp for 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
@@ -785,16 +816,20 @@ max_num_recipients = 10
 # match.
 header_filter_rules = []
 
-# 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.
+# Brug denne indstilling til at fra-filtrere mail til listen, baseret
+# p&aring; indholdet af et eller flere felter i mailhovedet. Her skal du
+# skrive regexp-uttryk (regular expressions), et per linie, som
+# sammenlignes mod det aktuelle felt. Sammenligningen sk&aelig;lner ikke
+# imellem store og sm&aring; bogstaver. Linier der begynder med '#'
+# sammenlignes ikke.
 # 
-# For example:to: .*@public.com  says to hold all postings with a To:
-# mail header containing '@public.com' anywhere among the addresses.
+# For eksempel: udtrykket to: .*@public.com fort&aelig;ller at alt mail
+# som indeholder '@public.com' i To: feltet, skal holdes tilbage til
+# godkendelse.
 # 
-# 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.
+# Bem&aelig;rk: blanke tegn i starten af regexp-udtrykket fjernes. Dette
+# kan man undg&aring; p&aring; flere m&aring;ter, f.eks. ved at bruge
+# escape-tegn eller parenteser.
 bounce_matching_headers = """
 # Lines that *start* with a '#' are comments.
 to: friend@public.com
@@ -804,54 +839,56 @@ from: .*@uplinkpro.com"""
 
 ## Bounce options
 #
-# 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.
+# Disse regler bestemmer hvordan automatisk behandling af returmails
+# gj&oslash;res. Her er en oversigt over hvordan funktionen er.
+# 
+# <p>N&aring;r Mailman modtager en returmail, blir to ting
+# fors&oslash;kt tolket. Det ene er e-mailadressen til medlemmet som
+# egentlig skulle modtage e-mailen, og det andet er &aring;rsagen til
+# problemet. &Aring;rsagen tolkes til at v&aelig;re <em>alvorlig</em>
+# eller <em>lett</em> alt efter om &aring;rsagen er af kritisk eller af
+# mindre alvorlig art. Såfremt der er tvivl, tolkes &aring;rsaken som
+# alvorlig.
+# 
+# <p>Hvis ingen e-mailadresse kan hentes ud af meddelelsen, blir den
+# normalt afvist. Ellers, vil medlemmet som har e-mailadressen f&aring;
+# en <em>returtal</em>, og hver gang en returmeddelelse kommer vil
+# tallet &oslash;ges. Alvorlige &aring;rsaker f&oslash;rer til at tallet
+# &oslash;ges med 1, lette &aring;rsaker f&oslash;rer til at det
+# &oslash;kes med 0.5. Dette sker kun &eacute;n gang per dag, s&aring;
+# selv om det 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;ttest til igen.
+# Medlemmet vil med j&aelig;vne mellemrum modtage melding 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>Det er en vigtig indstilling til; efter en vis tid -- hvis ingen
+# returmeddelelser dukker op i l&oslash;bet af denne tid -- anses
+# returinformation som <a
+# href="?VARHELP=bounce/bounce_info_stale_after">udg&aring;et</a> og
+# afvises. Ved at justere denne værdi, og sætte en grænse for
+# returantallet, kan du bestemme hvor lang tid der skal gå f&oslash;r
+# levering til et medlem stoppes. Begge disse værdier skal du justere
+# alt efter hvor ofte og hvor meget e-mail der sendes til din liste.
+
+# Ved at sætte denne værdi til Nej, sætter du alt automatisk tolking af
+# returmeddelelser for denne liste fra. Bemærk at såfremt meddelelser
+# afvises vil listeadministratoren ikke blive forstyrret med dem.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 bounce_processing = 1
 
 # Each subscriber is assigned a bounce score, as a floating point
@@ -867,351 +904,345 @@ bounce_processing = 1
 # mailing list.
 bounce_score_threshold = 5.0
 
-# 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.
+# Antal dage f&oslash;r returinformation afvises såfremt der ikke dukker
+# flere returmails op. Dette tal skal v&aelig;re et heltal.
 bounce_info_stale_after = 7
 
-# 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.
+# Hvor mange Levering til dig er stoppet advarsler der skal sendes til
+# et medlem f&oslash;r medlemmet frameldes fra listen. S&aelig;t denne
+# værdi til 0 for at fjerne et medlem fra listen umiddelbart
+# s&aring;fremt der kommer returmails fra medlemmets e-mailadresse.
+# Dette tal skal være et heltal.
 bounce_you_are_disabled_warnings = 3
 
-# The number of days between sending the Your Membership Is Disabled
-# warnings.  This value must be an integer.
+# Antal dage imellem hver gang en Levering til dig er stoppet advarsel
+# skal sendes ud. Dette tal skal være et heltal.
 bounce_you_are_disabled_warnings_interval = 7
 
-# 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.
+# Mailmans automatiske returmailhåndtering er meget robust, men det er
+# aligevel umuligt at genkende alle typer returmails der kommer. Du bør
+# angive Ja her, af to grunde: 1) Hvis det virkelig er en permanent
+# returmail fra et medlem af listen, bør du antageligt manuelt udmelde
+# medlemmet fra listen, og 2) du vil måske sende meddelelse til
+# udviklerne af Mailman sådan at returmails automatisk genkendes af
+# Mailman i senere versioner. Hvis du ikke vil gøre nogen af delene, sæt
+# da denne indstilling til Nej. Så vil alle returmails afvises
+# automatisk uden videre behandling. Bem&aelig;rk: Denne indstilling vil
+# også indvirke på alt e-mail der sendes til listens -admin adresse. Den
+# adresse er gammel og udgået, men det kan være at nogen fortsat vil
+# sende e-mail til den. Hvis nogen gør det, og du har sat denne
+# indstilling til Nej, vil disse mails også blive afvist. Måske vil du
+# også opsætte et automatisk svar på e-mail sendt til -owner og -admin
+# adresserne.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 bounce_unrecognized_goes_to_list_owner = 1
 
-# 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.
+# Ved at sætte denne til Nej, fravælges beskeden der normalt sendes til
+# ejeren(e) af listen, når afsending 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.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 bounce_notify_owner_on_disable = 1
 
-# 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.
+# Ved at sætte denne til Nej, fravælges beskeden der normalt sendes til
+# ejeren(e) af listen, når et medlem frameldes fra listen på grund af
+# for mange returmails. Der vil til gengæld altid blive forsøgt afsendt
+# en e-mail med besked til medlemmet.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 bounce_notify_owner_on_removal = 1
 
 ## Archive options
 #
-# List traffic archival policies.
+# Regler for arkivering
 
-# Archive messages?
+# Arkivere e-mail i et arkiv?
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 archive = 1
 
-# Is archive file source for public or private archival?
+# Skal filen arkiveres i et privat eller i et offentlig arkiv?
 #
-# legal values are:
-#    0 = "public"
-#    1 = "private"
+# gyldige værdier:
+#    0 = "offentlig"
+#    1 = "privat"
 archive_private = 0
 
-# How often should a new archive volume be started?
+# Hvor ofte skal arkivet deles op?
 #
-# legal values are:
-#    0 = "Yearly"
-#    1 = "Monthly"
-#    2 = "Quarterly"
-#    3 = "Weekly"
-#    4 = "Daily"
+# gyldige værdier:
+#    0 = "&Aring;rlig"
+#    1 = "M&aring;nedlig"
+#    2 = "Kvartalsvis"
+#    3 = "Ugentlig"
+#    4 = "Daglig"
 archive_volume_frequency = 1
 
 ## Gateway options
 #
-# Mail-to-News and News-to-Mail gateway services.
+# e-mail-Til-Nyhedsgruppe og Nyhedsgruppe-Til-e-mail tjeneste.
 
-# 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.
+# 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.
 nntp_host = ''
 
-# The name of the Usenet group to gateway to and/or from.
+# Navn p&aring; nyhedsgruppe der skal sendes til og/eller fra.
 linked_newsgroup = ''
 
-# Should new posts to the mailing list be sent to the newsgroup?
+# Skal nye mail til denne liste sendes til nyhedsgruppen?
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 gateway_to_news = 0
 
-# Should new posts to the newsgroup be sent to the mailing list?
+# Skal nye meddelelser til nyhedsgruppen sendes til denne mailliste?
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 gateway_to_mail = 0
 
-# 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.
+# 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&aring;t da 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
+# Moderet, vil en ekstra meddelelse holdes tilbage i
+# godkendelsesprocessen. Alt mail sendt til maillisten skal godkendes
+# f&oslash;r de sendes til nyhedsgruppen, eller til medlemmene af
+# listen.
+# 
+# Vær opm&aelig;rksom p&aring; at hvis mailhovedet i mailen har et
+# Approved: felt med listens administrative password, 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 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 meddelelseshovedet.
 #
-# legal values are:
-#    0 = "None"
-#    1 = "Open list, moderated group"
-#    2 = "Moderated"
+# gyldige værdier:
+#    0 = "Ingen"
+#    1 = "Åben liste, modereret nyhedsgruppe"
+#    2 = "Modereret"
 news_moderation = 0
 
-# 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.
+# Mailman tilføjer normalt en tekst du selv 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 sette denne indstilling
+# til Nej hvis du ikke ønsker emne prefix tilføjet til mail som sendes
+# til Usenet. Sætter du emne prefix for listen til off, vil opsamlet
+# meddelelser heller ikke få præfix tilføjet.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 news_prefix_subject_too = 1
 
 ## Autoreply options
 #
-# Auto-responder characteristics.<p>
+# Indstillinger for automatiske svar.<p>
 # 
-# 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>
+# 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 epostadresse</em>
+# <li><b>owneremail</b> - <em>listens -owner epostadresse</em> </ul>
 # 
-# <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.
+# <p>Du kan enten skrive teksten direkte i tekstboksene, eller du kan
+# angive navnet p&aring; en fil som indeholder teksten. Denne file vil
+# s&aring; blive indl&aelig;st i tekstboksen, fra dit lokale filsystem.
 
-# Should Mailman send an auto-response to mailing list posters?
+# Skal Mailman sende et automatisk svar til dem der sender e-mail til
+# listen?
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 autorespond_postings = 0
 
-# Auto-response text to send to mailing list posters.
+# Automatisk svar der skal sendes.
 autoresponse_postings_text = ''
 
-# Should Mailman send an auto-response to emails sent to the -owner
-# address?
+# Skal Mailman sende et automatisk svar p&aring; e-mail der sendes til
+# -owner adressen?
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 autorespond_admin = 0
 
-# Auto-response text to send to -owner emails.
+# Automatisk svar p&aring; e-mail til -owner adressen.
 autoresponse_admin_text = ''
 
-# 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.
+# 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
+# ogs&aring; skal v&aelig;re med i det automatiske svar.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes, w/discard"
-#    2 = "Yes, w/forward"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja, men uden den originale e-mailn"
+#    2 = "Ja, og medtag den originale e-mail"
 autorespond_requests = 0
 
-# Auto-response text to send to -request emails.
+# Automatisk svar p&aring; e-mail til -request adressen.
 autoresponse_request_text = ''
 
-# 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).
+# Antal dage imellem automatisk svar p&aring; e-mail, fra samme
+# afsender, til listen eller til -request/-owner adressene. S&aelig;t
+# denne v&aelig;rdi til 0 (eller et negativt tal) for at sende
+# automatisk svar hver gang.
 autoresponse_graceperiod = 90
 
 ## Contentfilter options
 #
-# 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.  Then, each
-# <tt>multipart/alternative</tt> section will be replaced by just the
-# first alternative that is non-empty after filtering.
-# 
-# <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?
+# Regler for indhold i e-mail sendt til listen.
+# 
+# <p>Filtrering af indhold fungerer således: når listen modtger en
+# e-mail og du har beskyttelse med filtrering af indhold, sammenlignes
+# først eventuelle ved- hæftelser imod <a
+# href="?VARHELP=contentfilter/filter_mime_types">MIME filtre</a>. Hvis
+# en vedhæftelse passer med et af disse filtre, blir vedhæftelsen
+# fjernet.
+# 
+# <p>Derefter sammenlignes eventuelle vedhæftelser imod <a
+# href="?VARHELP=contentfilter/pass_mime_types">gyldige MIME typer</a>,
+# hvis nogen er defineret. Alle vedhæftelser som ikke passer med de
+# angivne MIME typene, blir fjernet.
+# 
+# <p>Efter disse filtre, vil alle tomme <tt>multipart</tt> vedhæftelser
+# blive fjernet. Hvis selve meddelelsen er helt tom efter denne
+# filtrering, vil meddelelsen bli afvist. Derefter vil hvert
+# <tt>multipart/alternative</tt> vedhæftelse blive erstattet af det
+# første alternative som ikke er tomt.
+# 
+# <p>Til slut vil alle <tt>text/html</tt> vedhæftelser som måtte være
+# tilbage i meddelelsen blive konverteret til <tt>text/plain</tt>
+# såfremt <a
+# href="?VARHELP=contentfilter/convert_html_to_plaintext">konvertere til
+# ren tekst</a> er sat til og serveren er konfigurert til at tillade
+# sådanne konverteringer.
+
+# Skal Mailman filtrere indhold i e-mail sendt til listen som angivet
+# nedenfor?
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 filter_content = 0
 
-# 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.
+# Brug denne instilling til at fjerne vedhæftelser der passer til MIME
+# typer. Hver linie skal her indeholde navnet på en MIME type/subtype,
+# f.eks. image/gif. Såfremt du ønsker at fjerne alle vedhæftelser som
+# har en given hoved MIME type, kan du lade være at angive subtype,
+# f.eks. image.
 # 
-# Blank lines are ignored.
+# Blanke linier medtages ikke.
 # 
-# See also <a href="?VARHELP=contentfilter/pass_mime_types"
-# >pass_mime_types for a content type whitelist.
+# Se også gyldige MIME typer for whitelist af MIME typer.
 filter_mime_types = ''
 
-# 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.
+# Brug denne indstilling for at definere hvilke MIME typer der skal være
+# tilladt. Krav og format for filtrering er identisk med MIME filtre.
 # 
-# 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.
+# Bem&aelig;rk: hvis du lægger noget ind her, men ikke angiver
+# multipart, vil al e-mail med vedhæftelser ikke blive medtaget.
 pass_mime_types = """multipart/mixed
 multipart/alternative
 text/plain"""
 
-# Should Mailman convert text/html parts to plain text?  This conversion
-# happens after MIME attachments have been stripped.
+# Skal Mailman konvertere text/html dele til ren tekst? Denne
+# konvertering vil finde sted efter at MIME filteret har fjernet de
+# ønskede dele.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 convert_html_to_plaintext = 1
 
-# One of these actions is take 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.
+# Her bestemmer du hvad der skal ske når en meddelelse filtreres fra af
+# et filter, altså såfremt vedhæftelsen filtreres fra MIME filteret,
+# eller ent vedhæftelse ikke har en af de gyldige MIME typer, eller
+# meddelelsen ender op med at være tom efter filtrering.
+# 
+# Bemærk at det du vælger her ikke vil ske såfremt en meddelelse stadig
+# indeholder noget efter filtrering. Så vil meddelelsen altid sendes
+# videre til listen.
+# 
+# Når meddelelsen afvises, skrives Message-ID'en til den afviste
+# meddelelse til loggen. Når meddelelsen sendes retur eller videresendes
+# til listens ejer, vil en begrundelse altid blive inkluderet i
+# returmail der sendes til afsenderen. Når meddelelserne skal bevares,
+# gemmes de i en specielt køkatalog på disk sådan at
+# serveradministratoren kan se (og måske gøre noget med) meddelelsen,
+# men ellers fjernet. Dette sidste valg er kun tilgængeligt såfremt
+# serveradministratoren har tilladt det.
 #
-# legal values are:
-#    0 = "Discard"
-#    1 = "Reject"
-#    2 = "Forward to List Owner"
-#    3 = "Preserve"
+# gyldige værdier:
+#    0 = "Kassere"
+#    1 = "Afvis"
+#    2 = "Videresend til Listens Ejer"
+#    3 = "Tag hånd om"
 filter_action = 0
 
 ## Topics options
 #
-# 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.
+# Emneord for listen
+
+# Emnefilteret kategoriserer hver e-mail som kommer til listen, efter
+# regexp-uttrykkene du skriver nedenfor. Hvis feltene Subject: eller
+# Keywords: i mailhovedet i en mail passer imod disse udtryk, blir den
+# placeret under dette emne. Hvert medlem af listen kan vælge kun at
+# modtage mail der passer til de &oslash;nskede emner. e-mail som ikke
+# g&aring;r under noget emne, blir ikke leveret.
+# 
+# Bemerk: Dette fungerer kun i normal-modus, ikke i sammendrag-modus.
+# 
+# Indholdet i len kan ogs&aring; unders&oslash;ges for Subject: og
+# Keyword: felter, alt efter hvad indstillingen topics_bodylines_limit
+# er sat til.
 #
-# legal values are:
-#    0 = "Disabled"
-#    1 = "Enabled"
+# gyldige værdier:
+#    0 = "Ikke tilgængelig"
+#    1 = "Tilgængelig"
 topics_enabled = 0
 
-# 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.
-# 
+# Her opgiver du hvor mange linier af mailens indhold som emnefilteret
+# skal s&oslash;ge igennem. En s&oslash;gning stopper n&aring;r s&aring;
+# mange linier er gennoms&oslash;gt, eller n&aring;r det m&oslash;der en
+# linie som ikke ser ud som et meddelelsesfelt. Ved at sætte denne til
+# null (0), vil ingen linier i indholdet blive unders&oslash;gt (dvs.
+# kun Keywords: og Subject: i meddelelseshovedet unders&oslash;ges). Ved
+# at sætte denne værdi til et negativt tal, vil alle linier blive
+# unders&oslash;gt frem til den f&oslash;rste linie som ikke ser ut som
+# et mailhoved-felt.
 topics_bodylines_limit = 5
 
-# 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.
+# Hvert emneord er faktisk et regexp-udtryk, der sammenlignes imod dele
+# af mailen, nemlig feltene Keywords: og Subject: i meldingshodet.
+# Bem&aelig;rk at de f&oslash;ste linier i mailens indhold ogs&aring;
+# kan best&aring; af s&aring;danne "felter", og kan dermed ogs&aring;
+# bli unders&oslash;gt.
 topics = []
 
diff --git a/mailman/bestyrelse.members b/mailman/bestyrelse.members
index e69de29..784b3b4 100644
--- a/mailman/bestyrelse.members
+++ b/mailman/bestyrelse.members
@@ -0,0 +1,12 @@
+Anna Margrete Majgaard <Anna.Margrete.Majgaard@munksoegaard.dk>
+Lone Samuelsson <LOS@munksoegaard.dk>
+Annelise Jensen <annelise.jensen@munksoegaard.dk>
+Bodil Arlif <bodil.arlif@munksoegaard.dk>
+Jens Asger Hansen <hanne.isaksen@munksoegaard.dk>
+Jacob B?kke <jacob_baekke@munksoegaard.dk>
+Jonas Smedegaard <jones@munksoegaard.dk>
+Niels Th?gersen <niels.thoegersen@munksoegaard.dk>
+Ole Winther Olsen <owo@munksoegaard.dk>
+Per Helmer Roos <phr@oes.dk>
+Rikke N?raa <rikke.naeraa@munksoegaard.dk>
+Siri Reiter <siri_snell_reiter@munksoegaard.dk>
diff --git a/mailman/bestyrelse.py b/mailman/bestyrelse.py
index 737eec3..19bbc8b 100644
--- a/mailman/bestyrelse.py
+++ b/mailman/bestyrelse.py
@@ -1,375 +1,394 @@
-## "bestyrelse" mailing list configuration settings -*- python -*-
-## captured on Wed Mar 16 02:40:57 2005
+## Indstillinger for maillisten "bestyrelse"  -*- python -*-
+## Dato: Thu May  5 09:52:37 2005
 
 ## General options
 #
-# 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 :-)
+# Grundlæggende egenskaber for listen, blant andet en beskrivelse af
+# listen, og hvordan den opf&oslash;rer sig.
+
+# Her kan du f.eks. stave navnet med stort forbogstav, eller ændre visse
+# bogstaver til store sådan at navnet kan udtales p&aring; en rigtig
+# m&aring;de eller at forkortelser fremhæves. Bemærk at dette navn
+# bruges i e-maillistens adresse (f.eks. i bekræftigelser ved
+# tilmeldinger), s&aring; der 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 :-)
 real_name = 'Bestyrelse'
 
-# 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.
+# Der er to roller forbundet med hver mailliste. Listeadministratorene
+# 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.
+# 
+# Listemoderatorene har begrænset adgang; de kan ikke ændre
+# indstillinger for e-maillisten, men de kan tage sig af
+# foresp&oslash;rgsler i forbindlse med listen, f.eks. ans&oslash;gning
+# om medlemskab, eller godkende/afvise meddelelser der skal godkendes
+# for at kunne udsendes til listen. Listeadministratorene kan ogs&aring;
+# udf&oslash;re disse opgaver.
+# 
+# For at aktivere muligheden for at have listemoderatorer, og p&aring;
+# den m&aring;de opdele arbejdsopgaverne forbundet med listen, skal du
+# s&aelig;tte dit eget moderatorpassword, og angive din
+# e-mailadressen(e) til den/de som skal v&aelig;re listemoderator(er).
+# Bemærk at i tekstboksene nedenfor skal du skrive e-mailadressen(e) til
+# listeadministratoren(e).
 owner = ['listmaster@olinegaard.dk']
 
-# 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 = []
-
-# 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 = 'Bestyrelsen af Olinegaard'
-
-# 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 = """Email-liste om (og for) Bestyrelsen af Olinegaard.
-
-Hver email kan fylde max. 40 KiB, og ikke-tekst filtreres fra.
-
-Alle kan sende til listen; kun Olinegaards bestyrelse tilmeldes til at modtage.
-
-Kun listemedlemmer har 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.
-subject_prefix = '[Bestyrelse] '
-
-# Hide the sender of a message, replacing it with the list address
-# (Removes From, Sender and Reply-To fields)
+# Det er to ejerskab forbundet med hver mailliste. Listeadministratorene
+# er dem der har den endelige kontrol over alle indstillingerne for
+# e-mallisten. De kan &aelig;ndre alle indstillinger der er tilgengelige
+# via disse administrative websider.
+# 
+# Listemoderatorene har begr&aelig;nset adgang; de kan ikke &aelig;ndre
+# indstillinger for e-maillisten, men de kan tage sig af
+# foresp&oslash;rgsler ang&aring;ende listen, f.eks. ans&oslash;gning om
+# medlemskab, eller godkende/afvise meddelelser der skal godkendes for
+# at kunne udsendes p&aring; listen. Listeadministratorene kan selvsagt
+# ogs&aring; udf&oslash;re disse opgaver.
+# 
+# For at aktivere muligheten for at have listemoderatorer, og p&aring;
+# den m&aring;den opdele arbejdsopgaverne der er forbundet med listen,
+# skal du s&aelig;tte dit eget moderatorpassword, og indtaste din
+# e-mailadresse(r) til den/de der skal v&aelig;re listemoderator(er).
+# Bemærk at i tekstboksene nedenfor skal du skrive e-mailadressen(e) til
+# listemoderatoren(e).
+moderator = ['LOS@munksoegaard.dk']
+
+# Denne beskrivelsen 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 gj&oslash;re det uklart
+# hvad meningen med maillisten er eller hvad den skal bruges til.
+description = 'Oline bestyrelse'
+
+# Teksten tolkes som html bortset fra linieskift, der vil blive
+# &aelig;ndret til html-tag'en '<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. Benytter du html-kode,
+# husk da at gennemse meget grundigt, for fejl (f.eks. manglende
+# slutt-tag's) kan f&oslash;re til at listens informationsside ikke vil
+# vises s&aring;dan som den skal.
+info = """Lukket liste til bestyrelsen af Olinegaard.
+
+ * Alle kan sende til listen (max. 200KiB).
+ * Alle kan se medlemmer af listen.
+ * Emails arkiveres. Arkivet er kun for listens medlemmer."""
+
+# Denne tekst er sat ind foran emne-/tittelfeltet i e-mail der sendes
+# til listen, for at skille e-mailliste-meddelelser i e-mailboksen fra
+# dem der er medlem af listen. Denne tekst b&oslash;r holdes p&aring; et
+# absolut minimum, benytter du f.eks. listens navn og navnet er langt,
+# b&oslash;r du stave det endnu kortere her. Men den b&oslash;r fremover
+# v&aelig;re beskrivende for listen.
+subject_prefix = '[Oline bestyrelse] '
+
+# Skjule afsenderen af meddelser, ved at erstatte den med e-maillistens
+# adresse (Dette medfører at alle From:, Sender, og Reply-To: felter
+# fjernes)
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 anonymous_list = False
 
-# 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.
+# Skal eksisterende Reply-To: felt i meddelelseshovedet fjernes? Hvis ja
+# vil dette blive gjort uanset om Mailman tlføjer et Reply-To: felt
+# eller ikke.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 first_strip_reply_to = False
 
-# 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.org/essays/reply-to-useful.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.
+# Denne indstillling fort&aelig;ller hvad Mailman skal gj&oslash;re med
+# Reply-To: feltet i meddelelseshovedet 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;dan 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 diskusion omkring
+# emnet. Se Reply-To Munging Considered Useful for modsatte meninger.
+# 
+# Nogle maillister har begr&aelig;nset adgang, med en egen parallell
+# liste beregnet til diskutioner. Eksempler p&aring; dette er 'patches'
+# eller 'checkin' lister, som system for revisionskontrol sender
+# &aelig;ndringer i programmet til, men diskusioner omkring udvikling af
+# programmet sendes til udviklerenes 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 diskusionsliste.
 #
-# legal values are:
-#    0 = "Poster"
-#    1 = "This list"
-#    2 = "Explicit address"
+# gyldige værdier:
+#    0 = "Afsender"
+#    1 = "mail listens adresse"
+#    2 = "Egendefineret adresse"
 reply_goes_to_list = 0
 
-# 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.org/essays/reply-to-useful.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.
+# 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 modifikasion af Reply-To:
+# adressen g&oslash;r det vanskeligere at sende svar kun til afsender.
+# Se 'Reply-To' Munging Considered Harmful for en diskusion omkring
+# temaet. Se Reply-To Munging Considered Useful for modsatte meninger.
+# 
+# Nogen maillister har begr&aelig;nset adgang, med en egen parallell
+# liste beregnet for diskusioner. Eksempler p&aring; dette er 'patches'
+# eller 'checkin' lister, som system for revisionskontrol sender
+# &aelig;ndringer til i programmet, men diskusioner rundt udvikling af
+# programmet sendes til udviklerenes egen mailliste. For at
+# st&oslash;tte s&aring;danne maillister, definer Reply-To: adressen
+# her, og vælg Egendefineret adresse i indstillingen reply_goes_to_list.
+# 
+# Bem&aelig;rk at hvis den oprindelige meddelse indeholder et Reply-To:
+# felt, vil det ikke &aelig;ndres.
 reply_to_address = ''
 
-# 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.
+# S&aelig;t denne til 'ja' hvis listen skal bruges som en "paraply" for
+# flere andre lister. N&aring;r denne er sat, vil bekr&aelig;ftigelser
+# og meddelelser med password blive sendt til en egen adresse som
+# beregnes ud fra e-mailadressen som er tilmeldt listen - v&aelig;rdien
+# af indstillingen "umbrella_member_suffix" bruges til dette. Denne
+# v&aelig;rdi tilf&oslash;jes til medlemmets kontonavn (det som
+# st&aring;r f&oslash;r @-tegnet).
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 umbrella_list = False
 
-# 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".
+# N&aring;r "umbrella_list" indikerer at denne liste har andre
+# maillister som medlemmer, er det som regel &oslash;nskelig at
+# administrative meddelelser som f.eks. bekr&aelig;ftigelser og password
+# reminders ikke sendes til selve listen som er medlem, men til
+# administratoren for listen. Hvis dette er tilf&aelig;ldet, bruges
+# v&aelig;rdien af denne indstilling til at bestemme adressen sådan at
+# 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".
 umbrella_member_suffix = '-owner'
 
-# 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.
+# S&aelig;tt denne til hvis du vil have at password reminder skal sendes
+# til medlemmene en gang hver m&aring;ned. Husk at medlemmene kan
+# ogs&aring; selv frav&aelig;lge dette.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 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.
+# Tekst du skriver her vil blive tilf&oslash;jet &oslash;verst i
+# velkomsthilsenen der sendes til nye medlemmer. Velkomshilsenen
+# indeholder allerede viktige adresser og URLer knyttet til maillisten,
+# s&aring; sådan information er det ikke n&oslash;dvendig at inkludere
+# her. Her kan du indl&oslash;gge f.eks. oplysning om etikette eller
+# regler for brug af listen, o.l.
 # 
-# 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.
+# Bem&oslash;rk: Liniene i denne tekst vil brydes efter f&oslash;lgende
+# regler:
 # 
-welcome_msg = """Dette er en email-liste om (og for) Bestyrelsen af Olinegaard.
-
-Hver email kan fylde max. 40 KiB, og ikke-tekst filtreres fra.
-
-Alle kan sende til listen; kun Olinegaards bestyrelse tilmeldes til at modtage.
+# Hvert afsnit udfyldes s&aringdan at ingen linie er lenger en 70 tegn.
+# Enhver linie der begynder med blanke tegn udfyldes ikke. Blanke linier
+# adskiller afsnitt.
+# 
+welcome_msg = """Dette er en lukket liste til bestyrelsen af Olinegaard.
 
-Kun listemedlemmer har adgang til email-arkiv."""
+ * Alle kan sende til listen (max. 200KiB).
+ * Alle kan se medlemmer af listen.
+ * Emails arkiveres. Arkivet er kun for listens medlemmer."""
 
-# 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.
+# S&aelig;t kun denne til 'Nej' hvis du skal il&aelig;gge nye medlemmer
+# manuelt, og ikke vil have de skal f&aring; dette 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.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 send_welcome_msg = True
 
-# Text sent to people leaving the list.  If empty, no special text will
-# be added to the unsubscribe message.
+# Tekst der sendes til medlemmer der framelder sig fra listen. Hvis
+# denne er tom, l&aelig;gges det ikke noget tekst til frameldelsen.
 goodbye_msg = ''
 
-# Send goodbye message to members when they are unsubscribed?
+# Sende afskedshilsen til medlemmer n&aring;r de frameldes?
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 send_goodbye_msg = True
 
-# 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.
+# Der udsendes en reminder til listemoderatoren(e) (og
+# listeadministratoren(e)) dagligt om foresp&oslash;rsler der af en
+# eller anden grund venter p&aring; behandling. V&aelig;lger du "Ja",
+# vil listeadminstratoren ogs&aring; motdtage en meddelelse s&aring;
+# snart en foresp&oslash;rsel kommer ind.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 admin_immed_notify = True
 
-# Should administrator get notices of subscribes and unsubscribes?
+# Skal listeadministratoren(e) ogs&aring; modtage meddelelse om nye
+# medlemmer der tilmelder sig og gamle medlemmer som framelder sig?
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    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.
+# Besked om at en meddelelse skal godkendes sendes ud til afsenderen
+# s&aring;fremt meddelelsen stoppes pga. noget andet end listemoderation
+# eller spam filtre. S&aelig;ttes denne indstilling til 'Nej', vil
+# afsender overhovedet ikke modtage denne besked.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 respond_to_post_requests = 1
 
-# 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.
+# Når dette valg er aktiveret, vil alt e-mail til listen blive moderert.
+# 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-moderasjon" kan da hjælpe dig at fjerne usaglige meddelelser
+# til listen, og på den måden dysse en ophedet diskusion ned.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 emergency = 0
 
-# When a new member is subscribed to this list, their initial set of
-# options is taken from the this variable's setting.
+# Når et nyt medlem tilmeldes listen, blir medlemmets indstillinger
+# taget herfra.
 new_member_options = 256
 
-# 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.
+# Filter for administrative meddelelser vil unders&oslash;ge om
+# meddelelsen egentligt er ment som en administrativ foresp&oslash;rgsel
+# (f.eks. tilmelding, framelding, o.l.), og is&aring;fald sende
+# meddelelsen til administratoren i stedet.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 administrivia = True
 
-# Maximum length in kilobytes (KB) of a message body.  Use 0 for no
-# limit.
-max_message_size = 40
+# Maximum st&oslash;rrelse i kilobytes (KB) for indholdet i e-mail der
+# sendes til listen. Brug verdien '0' for ikke at have en
+# begr&aelig;nsning.
+max_message_size = 200
 
-# 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.
+# "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; denne maskinen. Denne
+# indstillingen kan v&aelig;re nyttig hvis maskinen har flere navne.
 host_name = 'olinegaard.dk'
 
-# 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).
+# I RFC 2369 defineres en r&aelig;kke List-* felter i
+# meddelelseshovedet, der normalt tilf&oslash;jes hver meddelelse der
+# sendes ud via listen. Disse felter kan hj&aelig;lpe de brugere af
+# listen der benytter et e-mailprogram som f&oslash;lger denne standard.
+# Disse felter b&oslash;r derfor altid v&aelig;re med.
+# 
+# Ikke alle e-mailprogrammer f&oslash;lger denne standard. Er det mange
+# af medlemmene p&aring; listen der benytter s&aring;danne
+# e-mailprogrammer, der ikke kan h&aring;ndtere disse felter i
+# meddelelseshovedet, kan det v&aelig;re du vil v&aelig;lge at udelade
+# dem. Men du b&oslash;r f&oslash;rst fors&oslash;ge at l&aelig;re og
+# forklare medlemmene 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 disse felter, men dette anbefales ikke (denne
+# muligheten kan faktisk ogs&aring; blive fjernet i senere versioner).
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 include_rfc2369_headers = 1
 
-# 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.)
+# List-Post: feltet er et af felterne anbefalet i RFC 2369. Visse
+# e-maillister (som f.eks. kun bruges til offentligørelser), er det kun
+# visse personer der har lov til at sende til; de som er medlem af
+# listen har generelt ikke lov til at sende til listen. For disse
+# lister, er List-Post: feltet forvirrende. I visse tilf&aelig;lde kan
+# det være forvirrende at s&aelig;tte denne indstilling til Nej,
+# s&aring; feltet ikke tilføjes. (Dette påvirker ikke andre List-*:
+# felter.)
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 include_list_post_header = 1
 
 ## Language options
 #
-# 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.
+# Underst&oslash;ttelse for flere sprog. (Internationalisering)
+
+# Dette er standardsproget som benyttes for denne mailliste. Hvis mer
+# 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.
 preferred_language = 'da'
 
-# These are all the natural languages supported by this list. Note that
-# the default language must be included.
+# Her er alle spr&aring;gene denne listen har underst&oslash;ttelse for.
+# Bem&aelig;rk at standardsproget skal v&aelig;re med.
 available_languages = ['en', 'da']
 
-# 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.
+# Hvis standardsproget for din mailliste benytter et andet tegns&aelig;t
+# end ASCII og tittel prefixet for listen indeholder tegn som ikke
+# findes i ASCII-tegns&aelig;ttet, vil prefixet alltid blive kodet i
+# henhold til den relevante standard. Hvis tittel prefixet kun
+# indeholder ASCII tegn, kan det imidlertid ske at du ønsker at sætte
+# dette valg til Aldrig for at undgå koding. Dette kan gøre titlen lidt
+# mere læselig for brugere med e-mailprogrammer der ikke takler andre
+# tegnsæt end ASCII på en rigtig måde.
+# 
+# Bemærk imidlertid at hvis din mailliste modtager både kodede og
+# ukodede tittel felt, kan det være bedst at vælge Efter behov. Med
+# denne indstilling vil Mailman ikke kode ASCII prefixer hvis resten af
+# tittelfeltet kun indeholder ASCII tegn, men vil kode prefixet hvis det
+# indeholder tegn som ikke er ASCII tegn. På denne måde undgås en [...]
+# i standarderne, som forårsager at visse e-mailprogrammer vil vise
+# ekstra eller manglende mellemrum imellom tittel prefixet og det
+# oprindelige tittelfelt.
 #
-# legal values are:
-#    0 = "Never"
-#    1 = "Always"
-#    2 = "As needed"
+# gyldige værdier:
+#    0 = "Aldrig"
+#    1 = "Altid"
+#    2 = "Efter behov"
 encode_ascii_prefixes = 2
 
 ## Nondigest options
 #
-# Policies concerning immediately delivered list traffic.
+# Regler for levering i normal-modus.
 
-# Can subscribers choose to receive mail immediately, rather than in
-# batched digests?
+# Kan medlemmer vælge normal-modus?
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 nondigestable = True
 
-# Text prepended to the top of every immediately-delivery message.
-# Teksten kan inneholde formateringskoder som byttes ut med verdier fra
-# listens oppsett. For detaljer, se Pythons formateringsregler
-# (engelsk). Gyldige koder er:
+# 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
+# formateringsregler (engelsk). Gyldige koder er:
 # 
 # 
 # real_name - Listens formaterede navn; normalt listenavnet med stort
@@ -395,10 +414,10 @@ nondigestable = True
 # 
 msg_header = ''
 
-# Text appended to the bottom of every immediately-delivery message.
-# Teksten kan inneholde formateringskoder som byttes ut med verdier fra
-# listens oppsett. For detaljer, se Pythons formateringsregler
-# (engelsk). Gyldige koder er:
+# Tekst som tilf&aelig;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
+# formateringsregler (engelsk). Gyldige koder er:
 # 
 # 
 # real_name - Listens formaterede navn; normalt listenavnet med stort
@@ -422,50 +441,52 @@ msg_header = ''
 # cgiext - Tillaeg som laegges til CGI scripts.
 # 
 # 
-msg_footer = """_______________________________________________
-%(real_name)s mailing list
+msg_footer = """-- 
+%(real_name)s email-liste
 %(real_name)s@%(host_name)s
 %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s"""
 
 ## Digest options
 #
-# Batched-delivery digest characteristics.
+# Opsætning af sammendrag-modus.
 
-# Can list members choose to receive list traffic bunched in digests?
+# Kan medlemmer af listen vælge at f&aring; tilsendt sammendrag i stedet
+# for?
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 digestable = True
 
-# Which delivery mode is the default for new users?
+# Hvilken modus er standard for nye brugere?
 #
-# legal values are:
-#    0 = "Regular"
-#    1 = "Digest"
+# gyldige værdier:
+#    0 = "Normal"
+#    1 = "Sammendrag"
 digest_is_default = False
 
-# When receiving digests, which format is default?
+# Hvilket format skal benyttes som standard for samle-email?
 #
-# legal values are:
-#    0 = "Plain"
+# gyldige værdier:
+#    0 = "Ren tekst"
 #    1 = "MIME"
-mime_is_default_digest = 1
+mime_is_default_digest = 0
 
-# How big in Kb should a digest be before it gets sent out?
-digest_size_threshhold = 30
+# Hvor stor (i Kb) m&aring; en samle-email h&oslash;jst v&aelig;re
+# f&oslash;r den udsendes?
+digest_size_threshhold = 300
 
-# Should a digest be dispatched daily when the size threshold isn't
-# reached?
+# Skal der sendes en samle-email dagligt, selv om st&oslash;rrelsen ikke
+# er opn&aring;et?
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 digest_send_periodic = True
 
-# Text attached (as an initial message, before the table of contents) to
-# the top of digests. Teksten kan inneholde formateringskoder som byttes
-# ut med verdier fra listens oppsett. For detaljer, se Pythons
+# Tekst som l&aelig;gges til &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:
 # 
 # 
@@ -492,10 +513,10 @@ digest_send_periodic = True
 # 
 digest_header = ''
 
-# Text attached (as a final message) to the bottom of digests. Teksten
-# kan inneholde formateringskoder som byttes ut med verdier fra listens
-# oppsett. For detaljer, se Pythons formateringsregler (engelsk).
-# Gyldige koder er:
+# Tekst der tilføjes nederst i hver samle-e-mail, som sidste
+# information.Teksten kan inneholde formateringskoder som byttes ut med
+# verdier fra listens oppsett. For detaljer, se Pythons
+# formateringsregler (engelsk). Gyldige koder er:
 # 
 # 
 # real_name - Listens formaterede navn; normalt listenavnet med stort
@@ -519,279 +540,282 @@ digest_header = ''
 # cgiext - Tillaeg som laegges til CGI scripts.
 # 
 # 
-digest_footer = """_______________________________________________
-%(real_name)s mailing list
+digest_footer = """-- 
+%(real_name)s email-liste
 %(real_name)s@%(host_name)s
 %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s"""
 
-# When a new digest volume is started, the volume number is incremented
-# and the issue number is reset to 1.
+# N&aring;r et nyt volume startes, &oslash;ges volume nummeret, og
+# udgavenummeret s&aelig;ttes til 1.
 #
-# legal values are:
-#    0 = "Yearly"
-#    1 = "Monthly"
-#    2 = "Quarterly"
-#    3 = "Weekly"
-#    4 = "Daily"
+# gyldige værdier:
+#    0 = "&Aring;rlig"
+#    1 = "M&aring;nedlig"
+#    2 = "Kvartalsvis"
+#    3 = "Ugentlig"
+#    4 = "Daglig"
 digest_volume_frequency = 1
 
 ## Privacy options
 #
-# 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://olinegaard.dk/mailman/admin/bestyrelse/archive">Archival
-# Options</a> section for separate archive-related privacy settings.
-
-# Advertise this list when people ask what lists are on this machine?
+# Her kan du bestemme hvad der kr&oslash;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://lists.olinegaard.dk/mailman/admin/bestyrelse/archive">Indstillinger 
+# for arkivering</a> for egne indstillinger n&aring;r det g&oslash;lder
+# arkivet og arkivering.
+
+# Vise denne mailliste n&aring;r nogn beder om at se en oversigt over
+# maillister p&aring; denne maskine?
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 advertised = 1
 
-# 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.
+# bek&aelig;ftigelse(*) - bekr&aelig;ftigelse af e-mail er
+# n&oslash;dvendig godkendelse - ans&oslash;gkning om medlemskabp skal
+# godkendes af listeadministrator (eller evt. listemoderator)
+# bekr&aelig;ftigelse+godkendelse - b&aring;de bekr&aelig;ftelse
+# p&aring; e-mail og godkendelse af listeadministrator (evt.
+# listemoderator) er nun&oslash;dvendig
+# 
+# (*) n&aring;r nogen vil tilmelde sig en liste, sender Mailman en
+# meddelelse med et uniktidentifikator som de skal opgive for at
+# bekr&oslash;fte tilmeldingen. P&aring; denne m&aring;den vil det da
+# ikke v&aelig;re muligt at tilmelde nogen til listen imod deres vilje.
 #
-# legal values are:
-#    1 = "Confirm"
-#    2 = "Require approval"
-#    3 = "Confirm and approve"
+# gyldige værdier:
+#    1 = "Bekr&aelig;ftigelse"
+#    2 = "Godkendelse"
+#    3 = "Bekr&aelig;ftigelse og godkendelse"
 subscribe_policy = 2
 
-# 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.
+# N&aring;r medlemmer &oslash;nsker at forlade en mailliste, sender de
+# en ans&oslash;gning om framelding, enten via web, eller via e-mail.
+# Normalt er det best at disse ans&oslash;gninger automatisk godkendes,
+# s&aring; meldemmer kan udmelde sig n&aring;r de &oslash;nsker det
+# (mange &oslash;nsker selv at kunne administrere en frameldelse. For
+# nogen f&aring; maillister kan det aligevel v&aelig;re aktuelt at have
+# kontrol over om medlemmer kan melde sig selv ud eller ikke. En liste
+# som alle ansatte i et firma M&Aring; v&aelig;re medlem af, er et
+# eksempel p&aring; en s&aring;dan liste.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 unsubscribe_policy = 0
 
-# 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.
+# Alle e-mailadresser som angives her vil blive udelukket fra listen, og
+# kan ikke tilmelde sig. Indtast e-mailadresser, en per linie, start
+# linien med tegnet ^ for at angive et regexp-udtryk der skal passe med
+# afsenderadressen.
 ban_list = []
 
-# When set, the list of subscribers is protected by member or admin
-# password authentication.
+# Hvis denne indstilling er sat til, vil listen over medlemmer af
+# e-maillisten blive beskyttet af medlemmenes eller adminstratorens
+# password.
 #
-# legal values are:
-#    0 = "Anyone"
-#    1 = "List members"
-#    2 = "List admin only"
-private_roster = 1
-
-# 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.
+# gyldige værdier:
+#    0 = "Alle"
+#    1 = "Kun medlemmer af listen"
+#    2 = "Kun listeadministrator"
+private_roster = 0
+
+# V&aelig;lger du 'Ja' her, vil medlemmers e-mailadresse omskrives
+# n&aring;r de vises i en oversigt p&aring; websidene (b&aring;de som
+# tekst og i linker), s&aring; de ikke er nemme at tolke som
+# e-mailadresser. Meningen med dette er at undg&aring; at e-mailsniffere
+# der gennemg&aring;r websider for at finde e-mailadresser (og derefter
+# bruge dem til at udsende spam/junk mail) til ikke at opsamle
+# medlemmenes e-mailadresser.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 obscure_addresses = 1
 
 ## Privacy options
 #
-# 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.
+# N&aring;r en meddelelse sendes til maillisten, g&aring;r den igennem
+# en r&aelig;kke trin for at afg&oslash;re om moderatoren m&aring;
+# godkende meddelelsen eller ikke. Her finder du indstillinger for 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 de sendes til listen.
+# 
+# <p>e-mail som ikke er sendt af medlemmer af listen, kan automatisk bli
+# <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">sendt
+# retur</a>, eller <a
+# href="?VARHELP=privacy/sender/discard_these_nonmembers">afvist</a>,
+# enten individuelt eller som en gruppe. All e-mail fra ikke-medlemmer,
+# som ikke specifikt bliver godkent, sendes retur, eller afvist, 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 il&aelig;gger du en e-mailadresse per
+# linie. Du kan ogs&aring; il&aelig;gge  <a
+# href="http://www.python.org/doc/current/lib/module-re.html">Python
+# regexp-uttrykk</a>. Begynd is&aring;fald linien med tegnet ^ for at
+# markere at det er et s&aring;dan udtryk. N&aring;r du benytter
+# backslash, skriv da lige som i rene strings (Python raw strings)
+# (normalt kun &eacute;n backslash af gangen).
+# 
+# <p>Bem&aelig;rk: match p&aring; 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-mail fra medlemmet kan sendes direkte til e-maillisten, eller om de
+# f&oslash;rst skal godkendes af listemoderatoren. N&aring;r
+# moderationsflaget er sat til, skal e-mail fra medlemmet godkendes af
+# listemoderatoren f&oslash;r det udsendes til alle p&aring; listen. Som
+# listeadminsitrator kan du for hvert enkelt medlem bestemme om
+# medlemmets e-mail skal modereres eller ikke. N&aring;r et nyt medlem
+# tilmeldes til 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
+# Administrere medlemmer siden.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 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.
 # 
-# Discard -- this simply discards the message, with no notice sent to
-# the post's author.
+# Holde tilbage -- meldingen holdes tilbage for godkendelse af
+# listemoderatoren(e). Afslå -- meldingen sendes automatisk retur til
+# afsender. Begrundelsen der sendes kan du skrive selv Slette --
+# meddelelsen blir afvist uden at give besked om dette til afsender.
 # 
 #
-# legal values are:
-#    0 = "Hold"
-#    1 = "Reject"
-#    2 = "Discard"
+# gyldige værdier:
+#    0 = "Holde&nbsp;tilbage"
+#    1 = "Afvis"
+#    2 = "Kassere"
 member_moderation_action = 0
 
-# 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.
+# Tekst som skal sendes med meldingen om retur som sendes til modereede
+# medlemmer af listen.
 member_moderation_notice = ''
 
-# 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.
+# e-mail fra disse ikke-medlemmer vil automatisk blive godkendt.
+# Il&aelig;g e-mailadresser, en per linie, start linien med tegnet ^ for
+# at angive et regexp-uttryk som skal passe med afsenderadressen.
 accept_these_nonmembers = []
 
-# 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.
+# e-mail fra disse ikke-medlemmer vil automatisk blive holdt tilbage for
+# vurdering af listemoderatorene. Afsenderen vil modtage en meddelelse
+# om dette, med bl.a. instruktioner om hvordan han/hun kan
+# tilbagetr&aelig;kke sin e-mails. Indtast e-mailadresser, en per linie,
+# start linien med tegnet ^ for at angive et regexp-uttrykk som skal
+# passe med afsenderadressen.
 hold_these_nonmembers = []
 
-# 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.
+# 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 spam-afsendere,
+# de b&oslash;r automatisk afvises. Indtast e-mailadresser, en per
+# linie, start linien med tegnet ^ for &aring; angiv et regexp-uttrykk
+# som skal passe med afsenderadressen.
 reject_these_nonmembers = []
 
-# 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.
+# e-mail fra disse ikke-medlemmer vil automatisk blive afvist. Det vil
+# sige at meddelelsen afvises uden nogen form for tilbagemelding, men
+# listemoderatorene kan (om ønskeligt) modtage en kopi af den afviste
+# e-mail. Tilf&oslash;je e-mailadresser, en per linie, start linien med
+# tegnet ^ for at angive et regexp-uttryk der skal passe med
+# afsenderadressen.
 discard_these_nonmembers = []
 
-# 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.
+# N&aring;r en e-mail fra et ikke-medlem blir modtaget, sammenlignes
+# e-mailens afsender med listen over e-mailadresser der skal godkendes,
+# holdes tilbage, afvises (sendes i retur), og afvises. Hvis
+# afsenderadressen ikke passer med den der er opgivet i listene, blir
+# f&oslash;lgende afg&oslash;relse taget.
 #
-# legal values are:
-#    0 = "Accept"
-#    1 = "Hold"
-#    2 = "Reject"
-#    3 = "Discard"
+# gyldige værdier:
+#    0 = "Godkende"
+#    1 = "Holde&nbsp;tilbage"
+#    2 = "Afvis"
+#    3 = "Kassere"
 generic_nonmember_action = 0
 
-# Should messages from non-members, which are automatically discarded,
-# be forwarded to the list moderator?
+# Skal meddelelser fra ikke-medlemmer, som automatisk afvises, også
+# sendes til listemoderatoren?
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 forward_auto_discards = 1
 
 ## Privacy options
 #
-# This section allows you to configure various filters based on the
-# recipient of the message.
+# Her kan du ops&aelig;tte filtrering baseret på modtaeren af
+# meddelelsen.
 
-# 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
+# Meget (faktisk det meste af) spam/junk mail har ikke de endelige
+# modtagere i modtagerfelterne. Faktisk s&aring; indeholder felterne To:
+# og/eller Cc: oftest en fuldst&aelig;ndig 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(e), men vil
+# aligevel blive fanget og blokkere det meste af spam/junk mail.
 # 
+# Prisen for dette er at listen ikke uhindret ville 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
+# alias for listen.
 # 
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 require_explicit_destination = 1
 
-# 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.
+# Alternative e-mailadresser som godtages n&aring;r
+# 'require_explicit_destination' er sat til. Som v&aelig;rdi for denne
+# indstilling skal du opgive regexp-uttryk ("regular expressions"), et
+# udtryk per linie, der sammenlignes imod 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 imod den f&oslash;rste
+# del (det som st&aring;r f&oslash;r '@') af modtageradressen. Hvis
+# sammenligningen ikke lykkes, eller hvis udtrykket ikke indholder en
+# '@', sammenlignes udtrykket med hele modtageradressen.
+# 
+# Sammenligning kun imod den f&oslash;rste del af en modtageradresse
+# underst&oslash;ttes ikke i fr&aelig;mtidige udgaver af Mailman, vil
+# kun sammenligning imod hele modtageradresser blive
+# underst&oslash;ttet.
 acceptable_aliases = ''
 
-# If a posting has this number, or more, of recipients, it is held for
-# admin approval.  Use 0 for no ceiling.
+# Hvis en mail der er sendt til listen indeholder s&aring; mange
+# modtagere som, eller flere modtagere end, denne værdi, holdes malen
+# tilbage så listeadministratoren eventuelt kan godkende den. Brug
+# værdien 0 for ingen begrænsning.
 max_num_recipients = 10
 
 ## Privacy options
 #
-# 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.
-# 
+# Her kan du opsætte forskellige anti-spam filtre, som kan være til
+# hjælp for 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
@@ -804,16 +828,20 @@ max_num_recipients = 10
 # match.
 header_filter_rules = []
 
-# 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.
+# Brug denne indstilling til at fra-filtrere mail til listen, baseret
+# p&aring; indholdet af et eller flere felter i mailhovedet. Her skal du
+# skrive regexp-uttryk (regular expressions), et per linie, som
+# sammenlignes mod det aktuelle felt. Sammenligningen sk&aelig;lner ikke
+# imellem store og sm&aring; bogstaver. Linier der begynder med '#'
+# sammenlignes ikke.
 # 
-# For example:to: .*@public.com  says to hold all postings with a To:
-# mail header containing '@public.com' anywhere among the addresses.
+# For eksempel: udtrykket to: .*@public.com fort&aelig;ller at alt mail
+# som indeholder '@public.com' i To: feltet, skal holdes tilbage til
+# godkendelse.
 # 
-# 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.
+# Bem&aelig;rk: blanke tegn i starten af regexp-udtrykket fjernes. Dette
+# kan man undg&aring; p&aring; flere m&aring;ter, f.eks. ved at bruge
+# escape-tegn eller parenteser.
 bounce_matching_headers = """
 # Lines that *start* with a '#' are comments.
 to: friend@public.com
@@ -823,54 +851,56 @@ from: .*@uplinkpro.com"""
 
 ## Bounce options
 #
-# 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.
+# Disse regler bestemmer hvordan automatisk behandling af returmails
+# gj&oslash;res. Her er en oversigt over hvordan funktionen er.
+# 
+# <p>N&aring;r Mailman modtager en returmail, blir to ting
+# fors&oslash;kt tolket. Det ene er e-mailadressen til medlemmet som
+# egentlig skulle modtage e-mailen, og det andet er &aring;rsagen til
+# problemet. &Aring;rsagen tolkes til at v&aelig;re <em>alvorlig</em>
+# eller <em>lett</em> alt efter om &aring;rsagen er af kritisk eller af
+# mindre alvorlig art. Såfremt der er tvivl, tolkes &aring;rsaken som
+# alvorlig.
+# 
+# <p>Hvis ingen e-mailadresse kan hentes ud af meddelelsen, blir den
+# normalt afvist. Ellers, vil medlemmet som har e-mailadressen f&aring;
+# en <em>returtal</em>, og hver gang en returmeddelelse kommer vil
+# tallet &oslash;ges. Alvorlige &aring;rsaker f&oslash;rer til at tallet
+# &oslash;ges med 1, lette &aring;rsaker f&oslash;rer til at det
+# &oslash;kes med 0.5. Dette sker kun &eacute;n gang per dag, s&aring;
+# selv om det 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;ttest til igen.
+# Medlemmet vil med j&aelig;vne mellemrum modtage melding 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>Det er en vigtig indstilling til; efter en vis tid -- hvis ingen
+# returmeddelelser dukker op i l&oslash;bet af denne tid -- anses
+# returinformation som <a
+# href="?VARHELP=bounce/bounce_info_stale_after">udg&aring;et</a> og
+# afvises. Ved at justere denne værdi, og sætte en grænse for
+# returantallet, kan du bestemme hvor lang tid der skal gå f&oslash;r
+# levering til et medlem stoppes. Begge disse værdier skal du justere
+# alt efter hvor ofte og hvor meget e-mail der sendes til din liste.
+
+# Ved at sætte denne værdi til Nej, sætter du alt automatisk tolking af
+# returmeddelelser for denne liste fra. Bemærk at såfremt meddelelser
+# afvises vil listeadministratoren ikke blive forstyrret med dem.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 bounce_processing = True
 
 # Each subscriber is assigned a bounce score, as a floating point
@@ -886,351 +916,345 @@ bounce_processing = True
 # mailing list.
 bounce_score_threshold = 5.0
 
-# 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.
+# Antal dage f&oslash;r returinformation afvises såfremt der ikke dukker
+# flere returmails op. Dette tal skal v&aelig;re et heltal.
 bounce_info_stale_after = 7
 
-# 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.
+# Hvor mange Levering til dig er stoppet advarsler der skal sendes til
+# et medlem f&oslash;r medlemmet frameldes fra listen. S&aelig;t denne
+# værdi til 0 for at fjerne et medlem fra listen umiddelbart
+# s&aring;fremt der kommer returmails fra medlemmets e-mailadresse.
+# Dette tal skal være et heltal.
 bounce_you_are_disabled_warnings = 3
 
-# The number of days between sending the Your Membership Is Disabled
-# warnings.  This value must be an integer.
+# Antal dage imellem hver gang en Levering til dig er stoppet advarsel
+# skal sendes ud. Dette tal skal være et heltal.
 bounce_you_are_disabled_warnings_interval = 7
 
-# 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.
+# Mailmans automatiske returmailhåndtering er meget robust, men det er
+# aligevel umuligt at genkende alle typer returmails der kommer. Du bør
+# angive Ja her, af to grunde: 1) Hvis det virkelig er en permanent
+# returmail fra et medlem af listen, bør du antageligt manuelt udmelde
+# medlemmet fra listen, og 2) du vil måske sende meddelelse til
+# udviklerne af Mailman sådan at returmails automatisk genkendes af
+# Mailman i senere versioner. Hvis du ikke vil gøre nogen af delene, sæt
+# da denne indstilling til Nej. Så vil alle returmails afvises
+# automatisk uden videre behandling. Bem&aelig;rk: Denne indstilling vil
+# også indvirke på alt e-mail der sendes til listens -admin adresse. Den
+# adresse er gammel og udgået, men det kan være at nogen fortsat vil
+# sende e-mail til den. Hvis nogen gør det, og du har sat denne
+# indstilling til Nej, vil disse mails også blive afvist. Måske vil du
+# også opsætte et automatisk svar på e-mail sendt til -owner og -admin
+# adresserne.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 bounce_unrecognized_goes_to_list_owner = True
 
-# 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.
+# Ved at sætte denne til Nej, fravælges beskeden der normalt sendes til
+# ejeren(e) af listen, når afsending 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.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 bounce_notify_owner_on_disable = True
 
-# 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.
+# Ved at sætte denne til Nej, fravælges beskeden der normalt sendes til
+# ejeren(e) af listen, når et medlem frameldes fra listen på grund af
+# for mange returmails. Der vil til gengæld altid blive forsøgt afsendt
+# en e-mail med besked til medlemmet.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 bounce_notify_owner_on_removal = True
 
 ## Archive options
 #
-# List traffic archival policies.
+# Regler for arkivering
 
-# Archive messages?
+# Arkivere e-mail i et arkiv?
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 archive = True
 
-# Is archive file source for public or private archival?
+# Skal filen arkiveres i et privat eller i et offentlig arkiv?
 #
-# legal values are:
-#    0 = "public"
-#    1 = "private"
+# gyldige værdier:
+#    0 = "offentlig"
+#    1 = "privat"
 archive_private = 1
 
-# How often should a new archive volume be started?
+# Hvor ofte skal arkivet deles op?
 #
-# legal values are:
-#    0 = "Yearly"
-#    1 = "Monthly"
-#    2 = "Quarterly"
-#    3 = "Weekly"
-#    4 = "Daily"
+# gyldige værdier:
+#    0 = "&Aring;rlig"
+#    1 = "M&aring;nedlig"
+#    2 = "Kvartalsvis"
+#    3 = "Ugentlig"
+#    4 = "Daglig"
 archive_volume_frequency = 2
 
 ## Gateway options
 #
-# Mail-to-News and News-to-Mail gateway services.
+# e-mail-Til-Nyhedsgruppe og Nyhedsgruppe-Til-e-mail tjeneste.
 
-# 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.
+# 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.
 nntp_host = ''
 
-# The name of the Usenet group to gateway to and/or from.
+# Navn p&aring; nyhedsgruppe der skal sendes til og/eller fra.
 linked_newsgroup = ''
 
-# Should new posts to the mailing list be sent to the newsgroup?
+# Skal nye mail til denne liste sendes til nyhedsgruppen?
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 gateway_to_news = 0
 
-# Should new posts to the newsgroup be sent to the mailing list?
+# Skal nye meddelelser til nyhedsgruppen sendes til denne mailliste?
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 gateway_to_mail = 0
 
-# 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.
+# 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&aring;t da 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
+# Moderet, vil en ekstra meddelelse holdes tilbage i
+# godkendelsesprocessen. Alt mail sendt til maillisten skal godkendes
+# f&oslash;r de sendes til nyhedsgruppen, eller til medlemmene af
+# listen.
+# 
+# Vær opm&aelig;rksom p&aring; at hvis mailhovedet i mailen har et
+# Approved: felt med listens administrative password, 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 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 meddelelseshovedet.
 #
-# legal values are:
-#    0 = "None"
-#    1 = "Open list, moderated group"
-#    2 = "Moderated"
+# gyldige værdier:
+#    0 = "Ingen"
+#    1 = "Åben liste, modereret nyhedsgruppe"
+#    2 = "Modereret"
 news_moderation = 0
 
-# 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.
+# Mailman tilføjer normalt en tekst du selv 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 sette denne indstilling
+# til Nej hvis du ikke ønsker emne prefix tilføjet til mail som sendes
+# til Usenet. Sætter du emne prefix for listen til off, vil opsamlet
+# meddelelser heller ikke få præfix tilføjet.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 news_prefix_subject_too = 1
 
 ## Autoreply options
 #
-# Auto-responder characteristics.<p>
+# Indstillinger for automatiske svar.<p>
 # 
-# 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>
+# 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 epostadresse</em>
+# <li><b>owneremail</b> - <em>listens -owner epostadresse</em> </ul>
 # 
-# <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.
+# <p>Du kan enten skrive teksten direkte i tekstboksene, eller du kan
+# angive navnet p&aring; en fil som indeholder teksten. Denne file vil
+# s&aring; blive indl&aelig;st i tekstboksen, fra dit lokale filsystem.
 
-# Should Mailman send an auto-response to mailing list posters?
+# Skal Mailman sende et automatisk svar til dem der sender e-mail til
+# listen?
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 autorespond_postings = 0
 
-# Auto-response text to send to mailing list posters.
+# Automatisk svar der skal sendes.
 autoresponse_postings_text = ''
 
-# Should Mailman send an auto-response to emails sent to the -owner
-# address?
+# Skal Mailman sende et automatisk svar p&aring; e-mail der sendes til
+# -owner adressen?
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 autorespond_admin = 0
 
-# Auto-response text to send to -owner emails.
+# Automatisk svar p&aring; e-mail til -owner adressen.
 autoresponse_admin_text = ''
 
-# 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.
+# 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
+# ogs&aring; skal v&aelig;re med i det automatiske svar.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes, w/discard"
-#    2 = "Yes, w/forward"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja, men uden den originale e-mailn"
+#    2 = "Ja, og medtag den originale e-mail"
 autorespond_requests = 0
 
-# Auto-response text to send to -request emails.
+# Automatisk svar p&aring; e-mail til -request adressen.
 autoresponse_request_text = ''
 
-# 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).
+# Antal dage imellem automatisk svar p&aring; e-mail, fra samme
+# afsender, til listen eller til -request/-owner adressene. S&aelig;t
+# denne v&aelig;rdi til 0 (eller et negativt tal) for at sende
+# automatisk svar hver gang.
 autoresponse_graceperiod = 90
 
 ## Contentfilter options
 #
-# 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.  Then, each
-# <tt>multipart/alternative</tt> section will be replaced by just the
-# first alternative that is non-empty after filtering.
-# 
-# <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?
+# Regler for indhold i e-mail sendt til listen.
+# 
+# <p>Filtrering af indhold fungerer således: når listen modtger en
+# e-mail og du har beskyttelse med filtrering af indhold, sammenlignes
+# først eventuelle ved- hæftelser imod <a
+# href="?VARHELP=contentfilter/filter_mime_types">MIME filtre</a>. Hvis
+# en vedhæftelse passer med et af disse filtre, blir vedhæftelsen
+# fjernet.
+# 
+# <p>Derefter sammenlignes eventuelle vedhæftelser imod <a
+# href="?VARHELP=contentfilter/pass_mime_types">gyldige MIME typer</a>,
+# hvis nogen er defineret. Alle vedhæftelser som ikke passer med de
+# angivne MIME typene, blir fjernet.
+# 
+# <p>Efter disse filtre, vil alle tomme <tt>multipart</tt> vedhæftelser
+# blive fjernet. Hvis selve meddelelsen er helt tom efter denne
+# filtrering, vil meddelelsen bli afvist. Derefter vil hvert
+# <tt>multipart/alternative</tt> vedhæftelse blive erstattet af det
+# første alternative som ikke er tomt.
+# 
+# <p>Til slut vil alle <tt>text/html</tt> vedhæftelser som måtte være
+# tilbage i meddelelsen blive konverteret til <tt>text/plain</tt>
+# såfremt <a
+# href="?VARHELP=contentfilter/convert_html_to_plaintext">konvertere til
+# ren tekst</a> er sat til og serveren er konfigurert til at tillade
+# sådanne konverteringer.
+
+# Skal Mailman filtrere indhold i e-mail sendt til listen som angivet
+# nedenfor?
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
-filter_content = 1
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
+filter_content = 0
 
-# 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.
+# Brug denne instilling til at fjerne vedhæftelser der passer til MIME
+# typer. Hver linie skal her indeholde navnet på en MIME type/subtype,
+# f.eks. image/gif. Såfremt du ønsker at fjerne alle vedhæftelser som
+# har en given hoved MIME type, kan du lade være at angive subtype,
+# f.eks. image.
 # 
-# Blank lines are ignored.
+# Blanke linier medtages ikke.
 # 
-# See also <a href="?VARHELP=contentfilter/pass_mime_types"
-# >pass_mime_types for a content type whitelist.
-filter_mime_types = 'image'
+# Se også gyldige MIME typer for whitelist af MIME typer.
+filter_mime_types = ''
 
-# 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.
+# Brug denne indstilling for at definere hvilke MIME typer der skal være
+# tilladt. Krav og format for filtrering er identisk med MIME filtre.
 # 
-# 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.
+# Bem&aelig;rk: hvis du lægger noget ind her, men ikke angiver
+# multipart, vil al e-mail med vedhæftelser ikke blive medtaget.
 pass_mime_types = """multipart/mixed
 multipart/alternative
 text/plain"""
 
-# Should Mailman convert text/html parts to plain text?  This conversion
-# happens after MIME attachments have been stripped.
+# Skal Mailman konvertere text/html dele til ren tekst? Denne
+# konvertering vil finde sted efter at MIME filteret har fjernet de
+# ønskede dele.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 convert_html_to_plaintext = True
 
-# One of these actions is take 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.
+# Her bestemmer du hvad der skal ske når en meddelelse filtreres fra af
+# et filter, altså såfremt vedhæftelsen filtreres fra MIME filteret,
+# eller ent vedhæftelse ikke har en af de gyldige MIME typer, eller
+# meddelelsen ender op med at være tom efter filtrering.
+# 
+# Bemærk at det du vælger her ikke vil ske såfremt en meddelelse stadig
+# indeholder noget efter filtrering. Så vil meddelelsen altid sendes
+# videre til listen.
+# 
+# Når meddelelsen afvises, skrives Message-ID'en til den afviste
+# meddelelse til loggen. Når meddelelsen sendes retur eller videresendes
+# til listens ejer, vil en begrundelse altid blive inkluderet i
+# returmail der sendes til afsenderen. Når meddelelserne skal bevares,
+# gemmes de i en specielt køkatalog på disk sådan at
+# serveradministratoren kan se (og måske gøre noget med) meddelelsen,
+# men ellers fjernet. Dette sidste valg er kun tilgængeligt såfremt
+# serveradministratoren har tilladt det.
 #
-# legal values are:
-#    0 = "Discard"
-#    1 = "Reject"
-#    2 = "Forward to List Owner"
-#    3 = "Preserve"
+# gyldige værdier:
+#    0 = "Kassere"
+#    1 = "Afvis"
+#    2 = "Videresend til Listens Ejer"
+#    3 = "Tag hånd om"
 filter_action = 1
 
 ## Topics options
 #
-# 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.
+# Emneord for listen
+
+# Emnefilteret kategoriserer hver e-mail som kommer til listen, efter
+# regexp-uttrykkene du skriver nedenfor. Hvis feltene Subject: eller
+# Keywords: i mailhovedet i en mail passer imod disse udtryk, blir den
+# placeret under dette emne. Hvert medlem af listen kan vælge kun at
+# modtage mail der passer til de &oslash;nskede emner. e-mail som ikke
+# g&aring;r under noget emne, blir ikke leveret.
+# 
+# Bemerk: Dette fungerer kun i normal-modus, ikke i sammendrag-modus.
+# 
+# Indholdet i len kan ogs&aring; unders&oslash;ges for Subject: og
+# Keyword: felter, alt efter hvad indstillingen topics_bodylines_limit
+# er sat til.
 #
-# legal values are:
-#    0 = "Disabled"
-#    1 = "Enabled"
+# gyldige værdier:
+#    0 = "Ikke tilgængelig"
+#    1 = "Tilgængelig"
 topics_enabled = 0
 
-# 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.
-# 
+# Her opgiver du hvor mange linier af mailens indhold som emnefilteret
+# skal s&oslash;ge igennem. En s&oslash;gning stopper n&aring;r s&aring;
+# mange linier er gennoms&oslash;gt, eller n&aring;r det m&oslash;der en
+# linie som ikke ser ud som et meddelelsesfelt. Ved at sætte denne til
+# null (0), vil ingen linier i indholdet blive unders&oslash;gt (dvs.
+# kun Keywords: og Subject: i meddelelseshovedet unders&oslash;ges). Ved
+# at sætte denne værdi til et negativt tal, vil alle linier blive
+# unders&oslash;gt frem til den f&oslash;rste linie som ikke ser ut som
+# et mailhoved-felt.
 topics_bodylines_limit = 5
 
-# 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.
+# Hvert emneord er faktisk et regexp-udtryk, der sammenlignes imod dele
+# af mailen, nemlig feltene Keywords: og Subject: i meldingshodet.
+# Bem&aelig;rk at de f&oslash;ste linier i mailens indhold ogs&aring;
+# kan best&aring; af s&aring;danne "felter", og kan dermed ogs&aring;
+# bli unders&oslash;gt.
 topics = []
 
diff --git a/mailman/debian.py b/mailman/debian.py
index 52b50d4..24a94cb 100644
--- a/mailman/debian.py
+++ b/mailman/debian.py
@@ -1,362 +1,386 @@
-## "debian" mailing list configuration settings -*- python -*-
-## captured on Wed Mar 16 02:40:59 2005
+## Indstillinger for maillisten "debian"  -*- python -*-
+## Dato: Thu May  5 09:52:39 2005
 
 ## General options
 #
-# 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 :-)
+# Grundlæggende egenskaber for listen, blant andet en beskrivelse af
+# listen, og hvordan den opf&oslash;rer sig.
+
+# Her kan du f.eks. stave navnet med stort forbogstav, eller ændre visse
+# bogstaver til store sådan at navnet kan udtales p&aring; en rigtig
+# m&aring;de eller at forkortelser fremhæves. Bemærk at dette navn
+# bruges i e-maillistens adresse (f.eks. i bekræftigelser ved
+# tilmeldinger), s&aring; der 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 :-)
 real_name = 'Debian'
 
-# 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.
+# Der er to roller forbundet med hver mailliste. Listeadministratorene
+# 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.
+# 
+# Listemoderatorene har begrænset adgang; de kan ikke ændre
+# indstillinger for e-maillisten, men de kan tage sig af
+# foresp&oslash;rgsler i forbindlse med listen, f.eks. ans&oslash;gning
+# om medlemskab, eller godkende/afvise meddelelser der skal godkendes
+# for at kunne udsendes til listen. Listeadministratorene kan ogs&aring;
+# udf&oslash;re disse opgaver.
+# 
+# For at aktivere muligheden for at have listemoderatorer, og p&aring;
+# den m&aring;de opdele arbejdsopgaverne forbundet med listen, skal du
+# s&aelig;tte dit eget moderatorpassword, og angive din
+# e-mailadressen(e) til den/de som skal v&aelig;re listemoderator(er).
+# Bemærk at i tekstboksene nedenfor skal du skrive e-mailadressen(e) til
+# listeadministratoren(e).
 owner = ['dr@jones.dk']
 
-# 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.
+# Det er to ejerskab forbundet med hver mailliste. Listeadministratorene
+# er dem der har den endelige kontrol over alle indstillingerne for
+# e-mallisten. De kan &aelig;ndre alle indstillinger der er tilgengelige
+# via disse administrative websider.
+# 
+# Listemoderatorene har begr&aelig;nset adgang; de kan ikke &aelig;ndre
+# indstillinger for e-maillisten, men de kan tage sig af
+# foresp&oslash;rgsler ang&aring;ende listen, f.eks. ans&oslash;gning om
+# medlemskab, eller godkende/afvise meddelelser der skal godkendes for
+# at kunne udsendes p&aring; listen. Listeadministratorene kan selvsagt
+# ogs&aring; udf&oslash;re disse opgaver.
+# 
+# For at aktivere muligheten for at have listemoderatorer, og p&aring;
+# den m&aring;den opdele arbejdsopgaverne der er forbundet med listen,
+# skal du s&aelig;tte dit eget moderatorpassword, og indtaste din
+# e-mailadresse(r) til den/de der skal v&aelig;re listemoderator(er).
+# Bemærk at i tekstboksene nedenfor skal du skrive e-mailadressen(e) til
+# listemoderatoren(e).
 moderator = []
 
-# 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.
+# Denne beskrivelsen 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 gj&oslash;re det uklart
+# hvad meningen med maillisten er eller hvad den skal bruges til.
 description = 'Discussions regarding unofficial Debian packages at debian.jones.dk'
 
-# 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.
+# Teksten tolkes som html bortset fra linieskift, der vil blive
+# &aelig;ndret til html-tag'en '<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. Benytter du html-kode,
+# husk da at gennemse meget grundigt, for fejl (f.eks. manglende
+# slutt-tag's) kan f&oslash;re til at listens informationsside ikke vil
+# vises s&aring;dan som den skal.
 info = ''
 
-# 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 er sat ind foran emne-/tittelfeltet i e-mail der sendes
+# til listen, for at skille e-mailliste-meddelelser i e-mailboksen fra
+# dem der er medlem af listen. Denne tekst b&oslash;r holdes p&aring; et
+# absolut minimum, benytter du f.eks. listens navn og navnet er langt,
+# b&oslash;r du stave det endnu kortere her. Men den b&oslash;r fremover
+# v&aelig;re beskrivende for listen.
 subject_prefix = '[Debian] '
 
-# Hide the sender of a message, replacing it with the list address
-# (Removes From, Sender and Reply-To fields)
+# Skjule afsenderen af meddelser, ved at erstatte den med e-maillistens
+# adresse (Dette medfører at alle From:, Sender, og Reply-To: felter
+# fjernes)
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 anonymous_list = 0
 
-# 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.
+# Skal eksisterende Reply-To: felt i meddelelseshovedet fjernes? Hvis ja
+# vil dette blive gjort uanset om Mailman tlføjer et Reply-To: felt
+# eller ikke.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 first_strip_reply_to = 0
 
-# 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.org/essays/reply-to-useful.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.
+# Denne indstillling fort&aelig;ller hvad Mailman skal gj&oslash;re med
+# Reply-To: feltet i meddelelseshovedet 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;dan 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 diskusion omkring
+# emnet. Se Reply-To Munging Considered Useful for modsatte meninger.
+# 
+# Nogle maillister har begr&aelig;nset adgang, med en egen parallell
+# liste beregnet til diskutioner. Eksempler p&aring; dette er 'patches'
+# eller 'checkin' lister, som system for revisionskontrol sender
+# &aelig;ndringer i programmet til, men diskusioner omkring udvikling af
+# programmet sendes til udviklerenes 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 diskusionsliste.
 #
-# legal values are:
-#    0 = "Poster"
-#    1 = "This list"
-#    2 = "Explicit address"
+# gyldige værdier:
+#    0 = "Afsender"
+#    1 = "mail listens adresse"
+#    2 = "Egendefineret adresse"
 reply_goes_to_list = 1
 
-# 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.org/essays/reply-to-useful.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.
+# 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 modifikasion af Reply-To:
+# adressen g&oslash;r det vanskeligere at sende svar kun til afsender.
+# Se 'Reply-To' Munging Considered Harmful for en diskusion omkring
+# temaet. Se Reply-To Munging Considered Useful for modsatte meninger.
+# 
+# Nogen maillister har begr&aelig;nset adgang, med en egen parallell
+# liste beregnet for diskusioner. Eksempler p&aring; dette er 'patches'
+# eller 'checkin' lister, som system for revisionskontrol sender
+# &aelig;ndringer til i programmet, men diskusioner rundt udvikling af
+# programmet sendes til udviklerenes egen mailliste. For at
+# st&oslash;tte s&aring;danne maillister, definer Reply-To: adressen
+# her, og vælg Egendefineret adresse i indstillingen reply_goes_to_list.
+# 
+# Bem&aelig;rk at hvis den oprindelige meddelse indeholder et Reply-To:
+# felt, vil det ikke &aelig;ndres.
 reply_to_address = ''
 
-# 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.
+# S&aelig;t denne til 'ja' hvis listen skal bruges som en "paraply" for
+# flere andre lister. N&aring;r denne er sat, vil bekr&aelig;ftigelser
+# og meddelelser med password blive sendt til en egen adresse som
+# beregnes ud fra e-mailadressen som er tilmeldt listen - v&aelig;rdien
+# af indstillingen "umbrella_member_suffix" bruges til dette. Denne
+# v&aelig;rdi tilf&oslash;jes til medlemmets kontonavn (det som
+# st&aring;r f&oslash;r @-tegnet).
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 umbrella_list = 0
 
-# 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".
+# N&aring;r "umbrella_list" indikerer at denne liste har andre
+# maillister som medlemmer, er det som regel &oslash;nskelig at
+# administrative meddelelser som f.eks. bekr&aelig;ftigelser og password
+# reminders ikke sendes til selve listen som er medlem, men til
+# administratoren for listen. Hvis dette er tilf&aelig;ldet, bruges
+# v&aelig;rdien af denne indstilling til at bestemme adressen sådan at
+# 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".
 umbrella_member_suffix = '-owner'
 
-# 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.
+# S&aelig;tt denne til hvis du vil have at password reminder skal sendes
+# til medlemmene en gang hver m&aring;ned. Husk at medlemmene kan
+# ogs&aring; selv frav&aelig;lge dette.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 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.
+# Tekst du skriver her vil blive tilf&oslash;jet &oslash;verst i
+# velkomsthilsenen der sendes til nye medlemmer. Velkomshilsenen
+# indeholder allerede viktige adresser og URLer knyttet til maillisten,
+# s&aring; sådan information er det ikke n&oslash;dvendig at inkludere
+# her. Her kan du indl&oslash;gge f.eks. oplysning om etikette eller
+# regler for brug af listen, o.l.
+# 
+# Bem&oslash;rk: Liniene i denne tekst vil brydes efter f&oslash;lgende
+# regler:
 # 
-# 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.
+# Hvert afsnit udfyldes s&aringdan at ingen linie er lenger en 70 tegn.
+# Enhver linie der begynder med blanke tegn udfyldes ikke. Blanke linier
+# adskiller afsnitt.
 # 
 welcome_msg = ''
 
-# 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.
+# S&aelig;t kun denne til 'Nej' hvis du skal il&aelig;gge nye medlemmer
+# manuelt, og ikke vil have de skal f&aring; dette 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.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 send_welcome_msg = 1
 
-# Text sent to people leaving the list.  If empty, no special text will
-# be added to the unsubscribe message.
+# Tekst der sendes til medlemmer der framelder sig fra listen. Hvis
+# denne er tom, l&aelig;gges det ikke noget tekst til frameldelsen.
 goodbye_msg = ''
 
-# Send goodbye message to members when they are unsubscribed?
+# Sende afskedshilsen til medlemmer n&aring;r de frameldes?
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 send_goodbye_msg = 1
 
-# 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.
+# Der udsendes en reminder til listemoderatoren(e) (og
+# listeadministratoren(e)) dagligt om foresp&oslash;rsler der af en
+# eller anden grund venter p&aring; behandling. V&aelig;lger du "Ja",
+# vil listeadminstratoren ogs&aring; motdtage en meddelelse s&aring;
+# snart en foresp&oslash;rsel kommer ind.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 admin_immed_notify = 1
 
-# Should administrator get notices of subscribes and unsubscribes?
+# Skal listeadministratoren(e) ogs&aring; modtage meddelelse om nye
+# medlemmer der tilmelder sig og gamle medlemmer som framelder sig?
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 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.
+# Besked om at en meddelelse skal godkendes sendes ud til afsenderen
+# s&aring;fremt meddelelsen stoppes pga. noget andet end listemoderation
+# eller spam filtre. S&aelig;ttes denne indstilling til 'Nej', vil
+# afsender overhovedet ikke modtage denne besked.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 respond_to_post_requests = 1
 
-# 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.
+# Når dette valg er aktiveret, vil alt e-mail til listen blive moderert.
+# 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-moderasjon" kan da hjælpe dig at fjerne usaglige meddelelser
+# til listen, og på den måden dysse en ophedet diskusion ned.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 emergency = 0
 
-# When a new member is subscribed to this list, their initial set of
-# options is taken from the this variable's setting.
+# Når et nyt medlem tilmeldes listen, blir medlemmets indstillinger
+# taget herfra.
 new_member_options = 256
 
-# 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.
+# Filter for administrative meddelelser vil unders&oslash;ge om
+# meddelelsen egentligt er ment som en administrativ foresp&oslash;rgsel
+# (f.eks. tilmelding, framelding, o.l.), og is&aring;fald sende
+# meddelelsen til administratoren i stedet.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 administrivia = 1
 
-# Maximum length in kilobytes (KB) of a message body.  Use 0 for no
-# limit.
+# Maximum st&oslash;rrelse i kilobytes (KB) for indholdet i e-mail der
+# sendes til listen. Brug verdien '0' for ikke at have en
+# begr&aelig;nsning.
 max_message_size = 40
 
-# 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.
+# "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; denne maskinen. Denne
+# indstillingen kan v&aelig;re nyttig hvis maskinen har flere navne.
 host_name = 'jones.dk'
 
-# 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).
+# I RFC 2369 defineres en r&aelig;kke List-* felter i
+# meddelelseshovedet, der normalt tilf&oslash;jes hver meddelelse der
+# sendes ud via listen. Disse felter kan hj&aelig;lpe de brugere af
+# listen der benytter et e-mailprogram som f&oslash;lger denne standard.
+# Disse felter b&oslash;r derfor altid v&aelig;re med.
+# 
+# Ikke alle e-mailprogrammer f&oslash;lger denne standard. Er det mange
+# af medlemmene p&aring; listen der benytter s&aring;danne
+# e-mailprogrammer, der ikke kan h&aring;ndtere disse felter i
+# meddelelseshovedet, kan det v&aelig;re du vil v&aelig;lge at udelade
+# dem. Men du b&oslash;r f&oslash;rst fors&oslash;ge at l&aelig;re og
+# forklare medlemmene 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 disse felter, men dette anbefales ikke (denne
+# muligheten kan faktisk ogs&aring; blive fjernet i senere versioner).
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 include_rfc2369_headers = 1
 
-# 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.)
+# List-Post: feltet er et af felterne anbefalet i RFC 2369. Visse
+# e-maillister (som f.eks. kun bruges til offentligørelser), er det kun
+# visse personer der har lov til at sende til; de som er medlem af
+# listen har generelt ikke lov til at sende til listen. For disse
+# lister, er List-Post: feltet forvirrende. I visse tilf&aelig;lde kan
+# det være forvirrende at s&aelig;tte denne indstilling til Nej,
+# s&aring; feltet ikke tilføjes. (Dette påvirker ikke andre List-*:
+# felter.)
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 include_list_post_header = 1
 
 ## Language options
 #
-# 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.
+# Underst&oslash;ttelse for flere sprog. (Internationalisering)
+
+# Dette er standardsproget som benyttes for denne mailliste. Hvis mer
+# 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.
 preferred_language = 'en'
 
-# These are all the natural languages supported by this list. Note that
-# the default language must be included.
+# Her er alle spr&aring;gene denne listen har underst&oslash;ttelse for.
+# Bem&aelig;rk at standardsproget skal v&aelig;re med.
 available_languages = ['da', 'de', 'en', 'no', 'sv']
 
-# 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.
+# Hvis standardsproget for din mailliste benytter et andet tegns&aelig;t
+# end ASCII og tittel prefixet for listen indeholder tegn som ikke
+# findes i ASCII-tegns&aelig;ttet, vil prefixet alltid blive kodet i
+# henhold til den relevante standard. Hvis tittel prefixet kun
+# indeholder ASCII tegn, kan det imidlertid ske at du ønsker at sætte
+# dette valg til Aldrig for at undgå koding. Dette kan gøre titlen lidt
+# mere læselig for brugere med e-mailprogrammer der ikke takler andre
+# tegnsæt end ASCII på en rigtig måde.
+# 
+# Bemærk imidlertid at hvis din mailliste modtager både kodede og
+# ukodede tittel felt, kan det være bedst at vælge Efter behov. Med
+# denne indstilling vil Mailman ikke kode ASCII prefixer hvis resten af
+# tittelfeltet kun indeholder ASCII tegn, men vil kode prefixet hvis det
+# indeholder tegn som ikke er ASCII tegn. På denne måde undgås en [...]
+# i standarderne, som forårsager at visse e-mailprogrammer vil vise
+# ekstra eller manglende mellemrum imellom tittel prefixet og det
+# oprindelige tittelfelt.
 #
-# legal values are:
-#    0 = "Never"
-#    1 = "Always"
-#    2 = "As needed"
+# gyldige værdier:
+#    0 = "Aldrig"
+#    1 = "Altid"
+#    2 = "Efter behov"
 encode_ascii_prefixes = 0
 
 ## Nondigest options
 #
-# Policies concerning immediately delivered list traffic.
+# Regler for levering i normal-modus.
 
-# Can subscribers choose to receive mail immediately, rather than in
-# batched digests?
+# Kan medlemmer vælge normal-modus?
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 nondigestable = 1
 
-# 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:
+# 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:
 # 
 # 
 # real_name - The "pretty" name of the list; usually the list name with
@@ -381,9 +405,10 @@ nondigestable = 1
 # 
 msg_header = ''
 
-# 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:
+# Tekst som tilf&aelig;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:
 # 
 # 
 # real_name - The "pretty" name of the list; usually the list name with
@@ -413,42 +438,44 @@ msg_footer = """_______________________________________________
 
 ## Digest options
 #
-# Batched-delivery digest characteristics.
+# Opsætning af sammendrag-modus.
 
-# Can list members choose to receive list traffic bunched in digests?
+# Kan medlemmer af listen vælge at f&aring; tilsendt sammendrag i stedet
+# for?
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 digestable = 1
 
-# Which delivery mode is the default for new users?
+# Hvilken modus er standard for nye brugere?
 #
-# legal values are:
-#    0 = "Regular"
-#    1 = "Digest"
+# gyldige værdier:
+#    0 = "Normal"
+#    1 = "Sammendrag"
 digest_is_default = 0
 
-# When receiving digests, which format is default?
+# Hvilket format skal benyttes som standard for samle-email?
 #
-# legal values are:
-#    0 = "Plain"
+# gyldige værdier:
+#    0 = "Ren tekst"
 #    1 = "MIME"
 mime_is_default_digest = 0
 
-# How big in Kb should a digest be before it gets sent out?
+# Hvor stor (i Kb) m&aring; en samle-email h&oslash;jst v&aelig;re
+# f&oslash;r den udsendes?
 digest_size_threshhold = 30
 
-# Should a digest be dispatched daily when the size threshold isn't
-# reached?
+# Skal der sendes en samle-email dagligt, selv om st&oslash;rrelsen ikke
+# er opn&aring;et?
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 digest_send_periodic = 1
 
-# Text attached (as an initial message, before the table of contents) to
-# the top of digests. This text can include Python format strings which
+# Tekst som l&aelig;gges til &oslash;verst i samle-emailen, f&oslash;r
+# indholdsfortegnelsen.This text can include Python format strings which
 # are resolved against list attributes.  The list of substitutions
 # allowed are:
 # 
@@ -475,9 +502,10 @@ digest_send_periodic = 1
 # 
 digest_header = ''
 
-# 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:
+# Tekst der tilføjes nederst i hver samle-e-mail, som sidste
+# information.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
@@ -505,274 +533,277 @@ digest_footer = """_______________________________________________
 %(real_name)s@%(host_name)s
 %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s"""
 
-# When a new digest volume is started, the volume number is incremented
-# and the issue number is reset to 1.
+# N&aring;r et nyt volume startes, &oslash;ges volume nummeret, og
+# udgavenummeret s&aelig;ttes til 1.
 #
-# legal values are:
-#    0 = "Yearly"
-#    1 = "Monthly"
-#    2 = "Quarterly"
-#    3 = "Weekly"
-#    4 = "Daily"
+# gyldige værdier:
+#    0 = "&Aring;rlig"
+#    1 = "M&aring;nedlig"
+#    2 = "Kvartalsvis"
+#    3 = "Ugentlig"
+#    4 = "Daglig"
 digest_volume_frequency = 1
 
 ## Privacy options
 #
-# 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.
-
-# Advertise this list when people ask what lists are on this machine?
+# Her kan du bestemme hvad der kr&oslash;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&oslash;lder
+# arkivet og arkivering.
+
+# Vise denne mailliste n&aring;r nogn beder om at se en oversigt over
+# maillister p&aring; denne maskine?
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 advertised = 1
 
-# 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.
+# bek&aelig;ftigelse(*) - bekr&aelig;ftigelse af e-mail er
+# n&oslash;dvendig godkendelse - ans&oslash;gkning om medlemskabp skal
+# godkendes af listeadministrator (eller evt. listemoderator)
+# bekr&aelig;ftigelse+godkendelse - b&aring;de bekr&aelig;ftelse
+# p&aring; e-mail og godkendelse af listeadministrator (evt.
+# listemoderator) er nun&oslash;dvendig
+# 
+# (*) n&aring;r nogen vil tilmelde sig en liste, sender Mailman en
+# meddelelse med et uniktidentifikator som de skal opgive for at
+# bekr&oslash;fte tilmeldingen. P&aring; denne m&aring;den vil det da
+# ikke v&aelig;re muligt at tilmelde nogen til listen imod deres vilje.
 #
-# legal values are:
-#    1 = "Confirm"
-#    2 = "Require approval"
-#    3 = "Confirm and approve"
+# gyldige værdier:
+#    1 = "Bekr&aelig;ftigelse"
+#    2 = "Godkendelse"
+#    3 = "Bekr&aelig;ftigelse og godkendelse"
 subscribe_policy = 1
 
-# 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.
+# N&aring;r medlemmer &oslash;nsker at forlade en mailliste, sender de
+# en ans&oslash;gning om framelding, enten via web, eller via e-mail.
+# Normalt er det best at disse ans&oslash;gninger automatisk godkendes,
+# s&aring; meldemmer kan udmelde sig n&aring;r de &oslash;nsker det
+# (mange &oslash;nsker selv at kunne administrere en frameldelse. For
+# nogen f&aring; maillister kan det aligevel v&aelig;re aktuelt at have
+# kontrol over om medlemmer kan melde sig selv ud eller ikke. En liste
+# som alle ansatte i et firma M&Aring; v&aelig;re medlem af, er et
+# eksempel p&aring; en s&aring;dan liste.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 unsubscribe_policy = 0
 
-# 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.
+# Alle e-mailadresser som angives her vil blive udelukket fra listen, og
+# kan ikke tilmelde sig. Indtast e-mailadresser, en per linie, start
+# linien med tegnet ^ for at angive et regexp-udtryk der skal passe med
+# afsenderadressen.
 ban_list = []
 
-# When set, the list of subscribers is protected by member or admin
-# password authentication.
+# Hvis denne indstilling er sat til, vil listen over medlemmer af
+# e-maillisten blive beskyttet af medlemmenes eller adminstratorens
+# password.
 #
-# legal values are:
-#    0 = "Anyone"
-#    1 = "List members"
-#    2 = "List admin only"
+# gyldige værdier:
+#    0 = "Alle"
+#    1 = "Kun medlemmer af listen"
+#    2 = "Kun listeadministrator"
 private_roster = 0
 
-# 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.
+# V&aelig;lger du 'Ja' her, vil medlemmers e-mailadresse omskrives
+# n&aring;r de vises i en oversigt p&aring; websidene (b&aring;de som
+# tekst og i linker), s&aring; de ikke er nemme at tolke som
+# e-mailadresser. Meningen med dette er at undg&aring; at e-mailsniffere
+# der gennemg&aring;r websider for at finde e-mailadresser (og derefter
+# bruge dem til at udsende spam/junk mail) til ikke at opsamle
+# medlemmenes e-mailadresser.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 obscure_addresses = 1
 
 ## Privacy options
 #
-# 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.
+# N&aring;r en meddelelse sendes til maillisten, g&aring;r den igennem
+# en r&aelig;kke trin for at afg&oslash;re om moderatoren m&aring;
+# godkende meddelelsen eller ikke. Her finder du indstillinger for 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 de sendes til listen.
+# 
+# <p>e-mail som ikke er sendt af medlemmer af listen, kan automatisk bli
+# <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">sendt
+# retur</a>, eller <a
+# href="?VARHELP=privacy/sender/discard_these_nonmembers">afvist</a>,
+# enten individuelt eller som en gruppe. All e-mail fra ikke-medlemmer,
+# som ikke specifikt bliver godkent, sendes retur, eller afvist, 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 il&aelig;gger du en e-mailadresse per
+# linie. Du kan ogs&aring; il&aelig;gge  <a
+# href="http://www.python.org/doc/current/lib/module-re.html">Python
+# regexp-uttrykk</a>. Begynd is&aring;fald linien med tegnet ^ for at
+# markere at det er et s&aring;dan udtryk. N&aring;r du benytter
+# backslash, skriv da lige som i rene strings (Python raw strings)
+# (normalt kun &eacute;n backslash af gangen).
+# 
+# <p>Bem&aelig;rk: match p&aring; 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-mail fra medlemmet kan sendes direkte til e-maillisten, eller om de
+# f&oslash;rst skal godkendes af listemoderatoren. N&aring;r
+# moderationsflaget er sat til, skal e-mail fra medlemmet godkendes af
+# listemoderatoren f&oslash;r det udsendes til alle p&aring; listen. Som
+# listeadminsitrator kan du for hvert enkelt medlem bestemme om
+# medlemmets e-mail skal modereres eller ikke. N&aring;r et nyt medlem
+# tilmeldes til 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
+# Administrere medlemmer siden.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 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.
 # 
-# Discard -- this simply discards the message, with no notice sent to
-# the post's author.
+# Holde tilbage -- meldingen holdes tilbage for godkendelse af
+# listemoderatoren(e). Afslå -- meldingen sendes automatisk retur til
+# afsender. Begrundelsen der sendes kan du skrive selv Slette --
+# meddelelsen blir afvist uden at give besked om dette til afsender.
 # 
 #
-# legal values are:
-#    0 = "Hold"
-#    1 = "Reject"
-#    2 = "Discard"
+# gyldige værdier:
+#    0 = "Holde&nbsp;tilbage"
+#    1 = "Afvis"
+#    2 = "Kassere"
 member_moderation_action = 0
 
-# 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.
+# Tekst som skal sendes med meldingen om retur som sendes til modereede
+# medlemmer af listen.
 member_moderation_notice = ''
 
-# 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.
+# e-mail fra disse ikke-medlemmer vil automatisk blive godkendt.
+# Il&aelig;g e-mailadresser, en per linie, start linien med tegnet ^ for
+# at angive et regexp-uttryk som skal passe med afsenderadressen.
 accept_these_nonmembers = []
 
-# 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.
+# e-mail fra disse ikke-medlemmer vil automatisk blive holdt tilbage for
+# vurdering af listemoderatorene. Afsenderen vil modtage en meddelelse
+# om dette, med bl.a. instruktioner om hvordan han/hun kan
+# tilbagetr&aelig;kke sin e-mails. Indtast e-mailadresser, en per linie,
+# start linien med tegnet ^ for at angive et regexp-uttrykk som skal
+# passe med afsenderadressen.
 hold_these_nonmembers = []
 
-# 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.
+# 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 spam-afsendere,
+# de b&oslash;r automatisk afvises. Indtast e-mailadresser, en per
+# linie, start linien med tegnet ^ for &aring; angiv et regexp-uttrykk
+# som skal passe med afsenderadressen.
 reject_these_nonmembers = []
 
-# 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.
+# e-mail fra disse ikke-medlemmer vil automatisk blive afvist. Det vil
+# sige at meddelelsen afvises uden nogen form for tilbagemelding, men
+# listemoderatorene kan (om ønskeligt) modtage en kopi af den afviste
+# e-mail. Tilf&oslash;je e-mailadresser, en per linie, start linien med
+# tegnet ^ for at angive et regexp-uttryk der skal passe med
+# afsenderadressen.
 discard_these_nonmembers = []
 
-# 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.
+# N&aring;r en e-mail fra et ikke-medlem blir modtaget, sammenlignes
+# e-mailens afsender med listen over e-mailadresser der skal godkendes,
+# holdes tilbage, afvises (sendes i retur), og afvises. Hvis
+# afsenderadressen ikke passer med den der er opgivet i listene, blir
+# f&oslash;lgende afg&oslash;relse taget.
 #
-# legal values are:
-#    0 = "Accept"
-#    1 = "Hold"
-#    2 = "Reject"
-#    3 = "Discard"
+# gyldige værdier:
+#    0 = "Godkende"
+#    1 = "Holde&nbsp;tilbage"
+#    2 = "Afvis"
+#    3 = "Kassere"
 generic_nonmember_action = 0
 
-# Should messages from non-members, which are automatically discarded,
-# be forwarded to the list moderator?
+# Skal meddelelser fra ikke-medlemmer, som automatisk afvises, også
+# sendes til listemoderatoren?
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 forward_auto_discards = 1
 
 ## Privacy options
 #
-# This section allows you to configure various filters based on the
-# recipient of the message.
+# Her kan du ops&aelig;tte filtrering baseret på modtaeren af
+# meddelelsen.
 
-# 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.
+# Meget (faktisk det meste af) spam/junk mail har ikke de endelige
+# modtagere i modtagerfelterne. Faktisk s&aring; indeholder felterne To:
+# og/eller Cc: oftest en fuldst&aelig;ndig 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(e), men vil
+# aligevel blive fanget og blokkere det meste af spam/junk mail.
 # 
-# 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 ville 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
+# alias for listen.
 # 
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 require_explicit_destination = 1
 
-# 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.
+# Alternative e-mailadresser som godtages n&aring;r
+# 'require_explicit_destination' er sat til. Som v&aelig;rdi for denne
+# indstilling skal du opgive regexp-uttryk ("regular expressions"), et
+# udtryk per linie, der sammenlignes imod 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 imod den f&oslash;rste
+# del (det som st&aring;r f&oslash;r '@') af modtageradressen. Hvis
+# sammenligningen ikke lykkes, eller hvis udtrykket ikke indholder en
+# '@', sammenlignes udtrykket med hele modtageradressen.
+# 
+# Sammenligning kun imod den f&oslash;rste del af en modtageradresse
+# underst&oslash;ttes ikke i fr&aelig;mtidige udgaver af Mailman, vil
+# kun sammenligning imod hele modtageradresser blive
+# underst&oslash;ttet.
 acceptable_aliases = ''
 
-# If a posting has this number, or more, of recipients, it is held for
-# admin approval.  Use 0 for no ceiling.
+# Hvis en mail der er sendt til listen indeholder s&aring; mange
+# modtagere som, eller flere modtagere end, denne værdi, holdes malen
+# tilbage så listeadministratoren eventuelt kan godkende den. Brug
+# værdien 0 for ingen begrænsning.
 max_num_recipients = 10
 
 ## Privacy options
 #
-# 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.
-# 
+# Her kan du opsætte forskellige anti-spam filtre, som kan være til
+# hjælp for 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
@@ -785,16 +816,20 @@ max_num_recipients = 10
 # match.
 header_filter_rules = []
 
-# 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.
+# Brug denne indstilling til at fra-filtrere mail til listen, baseret
+# p&aring; indholdet af et eller flere felter i mailhovedet. Her skal du
+# skrive regexp-uttryk (regular expressions), et per linie, som
+# sammenlignes mod det aktuelle felt. Sammenligningen sk&aelig;lner ikke
+# imellem store og sm&aring; bogstaver. Linier der begynder med '#'
+# sammenlignes ikke.
 # 
-# For example:to: .*@public.com  says to hold all postings with a To:
-# mail header containing '@public.com' anywhere among the addresses.
+# For eksempel: udtrykket to: .*@public.com fort&aelig;ller at alt mail
+# som indeholder '@public.com' i To: feltet, skal holdes tilbage til
+# godkendelse.
 # 
-# 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.
+# Bem&aelig;rk: blanke tegn i starten af regexp-udtrykket fjernes. Dette
+# kan man undg&aring; p&aring; flere m&aring;ter, f.eks. ved at bruge
+# escape-tegn eller parenteser.
 bounce_matching_headers = """
 # Lines that *start* with a '#' are comments.
 to: friend@public.com
@@ -804,54 +839,56 @@ from: .*@uplinkpro.com"""
 
 ## Bounce options
 #
-# 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.
+# Disse regler bestemmer hvordan automatisk behandling af returmails
+# gj&oslash;res. Her er en oversigt over hvordan funktionen er.
+# 
+# <p>N&aring;r Mailman modtager en returmail, blir to ting
+# fors&oslash;kt tolket. Det ene er e-mailadressen til medlemmet som
+# egentlig skulle modtage e-mailen, og det andet er &aring;rsagen til
+# problemet. &Aring;rsagen tolkes til at v&aelig;re <em>alvorlig</em>
+# eller <em>lett</em> alt efter om &aring;rsagen er af kritisk eller af
+# mindre alvorlig art. Såfremt der er tvivl, tolkes &aring;rsaken som
+# alvorlig.
+# 
+# <p>Hvis ingen e-mailadresse kan hentes ud af meddelelsen, blir den
+# normalt afvist. Ellers, vil medlemmet som har e-mailadressen f&aring;
+# en <em>returtal</em>, og hver gang en returmeddelelse kommer vil
+# tallet &oslash;ges. Alvorlige &aring;rsaker f&oslash;rer til at tallet
+# &oslash;ges med 1, lette &aring;rsaker f&oslash;rer til at det
+# &oslash;kes med 0.5. Dette sker kun &eacute;n gang per dag, s&aring;
+# selv om det 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;ttest til igen.
+# Medlemmet vil med j&aelig;vne mellemrum modtage melding 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>Det er en vigtig indstilling til; efter en vis tid -- hvis ingen
+# returmeddelelser dukker op i l&oslash;bet af denne tid -- anses
+# returinformation som <a
+# href="?VARHELP=bounce/bounce_info_stale_after">udg&aring;et</a> og
+# afvises. Ved at justere denne værdi, og sætte en grænse for
+# returantallet, kan du bestemme hvor lang tid der skal gå f&oslash;r
+# levering til et medlem stoppes. Begge disse værdier skal du justere
+# alt efter hvor ofte og hvor meget e-mail der sendes til din liste.
+
+# Ved at sætte denne værdi til Nej, sætter du alt automatisk tolking af
+# returmeddelelser for denne liste fra. Bemærk at såfremt meddelelser
+# afvises vil listeadministratoren ikke blive forstyrret med dem.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 bounce_processing = 1
 
 # Each subscriber is assigned a bounce score, as a floating point
@@ -867,351 +904,345 @@ bounce_processing = 1
 # mailing list.
 bounce_score_threshold = 5.0
 
-# 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.
+# Antal dage f&oslash;r returinformation afvises såfremt der ikke dukker
+# flere returmails op. Dette tal skal v&aelig;re et heltal.
 bounce_info_stale_after = 7
 
-# 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.
+# Hvor mange Levering til dig er stoppet advarsler der skal sendes til
+# et medlem f&oslash;r medlemmet frameldes fra listen. S&aelig;t denne
+# værdi til 0 for at fjerne et medlem fra listen umiddelbart
+# s&aring;fremt der kommer returmails fra medlemmets e-mailadresse.
+# Dette tal skal være et heltal.
 bounce_you_are_disabled_warnings = 3
 
-# The number of days between sending the Your Membership Is Disabled
-# warnings.  This value must be an integer.
+# Antal dage imellem hver gang en Levering til dig er stoppet advarsel
+# skal sendes ud. Dette tal skal være et heltal.
 bounce_you_are_disabled_warnings_interval = 7
 
-# 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.
+# Mailmans automatiske returmailhåndtering er meget robust, men det er
+# aligevel umuligt at genkende alle typer returmails der kommer. Du bør
+# angive Ja her, af to grunde: 1) Hvis det virkelig er en permanent
+# returmail fra et medlem af listen, bør du antageligt manuelt udmelde
+# medlemmet fra listen, og 2) du vil måske sende meddelelse til
+# udviklerne af Mailman sådan at returmails automatisk genkendes af
+# Mailman i senere versioner. Hvis du ikke vil gøre nogen af delene, sæt
+# da denne indstilling til Nej. Så vil alle returmails afvises
+# automatisk uden videre behandling. Bem&aelig;rk: Denne indstilling vil
+# også indvirke på alt e-mail der sendes til listens -admin adresse. Den
+# adresse er gammel og udgået, men det kan være at nogen fortsat vil
+# sende e-mail til den. Hvis nogen gør det, og du har sat denne
+# indstilling til Nej, vil disse mails også blive afvist. Måske vil du
+# også opsætte et automatisk svar på e-mail sendt til -owner og -admin
+# adresserne.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 bounce_unrecognized_goes_to_list_owner = 1
 
-# 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.
+# Ved at sætte denne til Nej, fravælges beskeden der normalt sendes til
+# ejeren(e) af listen, når afsending 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.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 bounce_notify_owner_on_disable = 1
 
-# 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.
+# Ved at sætte denne til Nej, fravælges beskeden der normalt sendes til
+# ejeren(e) af listen, når et medlem frameldes fra listen på grund af
+# for mange returmails. Der vil til gengæld altid blive forsøgt afsendt
+# en e-mail med besked til medlemmet.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 bounce_notify_owner_on_removal = 1
 
 ## Archive options
 #
-# List traffic archival policies.
+# Regler for arkivering
 
-# Archive messages?
+# Arkivere e-mail i et arkiv?
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 archive = 1
 
-# Is archive file source for public or private archival?
+# Skal filen arkiveres i et privat eller i et offentlig arkiv?
 #
-# legal values are:
-#    0 = "public"
-#    1 = "private"
+# gyldige værdier:
+#    0 = "offentlig"
+#    1 = "privat"
 archive_private = 0
 
-# How often should a new archive volume be started?
+# Hvor ofte skal arkivet deles op?
 #
-# legal values are:
-#    0 = "Yearly"
-#    1 = "Monthly"
-#    2 = "Quarterly"
-#    3 = "Weekly"
-#    4 = "Daily"
+# gyldige værdier:
+#    0 = "&Aring;rlig"
+#    1 = "M&aring;nedlig"
+#    2 = "Kvartalsvis"
+#    3 = "Ugentlig"
+#    4 = "Daglig"
 archive_volume_frequency = 2
 
 ## Gateway options
 #
-# Mail-to-News and News-to-Mail gateway services.
+# e-mail-Til-Nyhedsgruppe og Nyhedsgruppe-Til-e-mail tjeneste.
 
-# 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.
+# 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.
 nntp_host = ''
 
-# The name of the Usenet group to gateway to and/or from.
+# Navn p&aring; nyhedsgruppe der skal sendes til og/eller fra.
 linked_newsgroup = ''
 
-# Should new posts to the mailing list be sent to the newsgroup?
+# Skal nye mail til denne liste sendes til nyhedsgruppen?
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 gateway_to_news = 0
 
-# Should new posts to the newsgroup be sent to the mailing list?
+# Skal nye meddelelser til nyhedsgruppen sendes til denne mailliste?
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 gateway_to_mail = 0
 
-# 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.
+# 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&aring;t da 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
+# Moderet, vil en ekstra meddelelse holdes tilbage i
+# godkendelsesprocessen. Alt mail sendt til maillisten skal godkendes
+# f&oslash;r de sendes til nyhedsgruppen, eller til medlemmene af
+# listen.
+# 
+# Vær opm&aelig;rksom p&aring; at hvis mailhovedet i mailen har et
+# Approved: felt med listens administrative password, 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 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 meddelelseshovedet.
 #
-# legal values are:
-#    0 = "None"
-#    1 = "Open list, moderated group"
-#    2 = "Moderated"
+# gyldige værdier:
+#    0 = "Ingen"
+#    1 = "Åben liste, modereret nyhedsgruppe"
+#    2 = "Modereret"
 news_moderation = 0
 
-# 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.
+# Mailman tilføjer normalt en tekst du selv 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 sette denne indstilling
+# til Nej hvis du ikke ønsker emne prefix tilføjet til mail som sendes
+# til Usenet. Sætter du emne prefix for listen til off, vil opsamlet
+# meddelelser heller ikke få præfix tilføjet.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 news_prefix_subject_too = 1
 
 ## Autoreply options
 #
-# Auto-responder characteristics.<p>
+# Indstillinger for automatiske svar.<p>
 # 
-# 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>
+# 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 epostadresse</em>
+# <li><b>owneremail</b> - <em>listens -owner epostadresse</em> </ul>
 # 
-# <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.
+# <p>Du kan enten skrive teksten direkte i tekstboksene, eller du kan
+# angive navnet p&aring; en fil som indeholder teksten. Denne file vil
+# s&aring; blive indl&aelig;st i tekstboksen, fra dit lokale filsystem.
 
-# Should Mailman send an auto-response to mailing list posters?
+# Skal Mailman sende et automatisk svar til dem der sender e-mail til
+# listen?
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 autorespond_postings = 0
 
-# Auto-response text to send to mailing list posters.
+# Automatisk svar der skal sendes.
 autoresponse_postings_text = ''
 
-# Should Mailman send an auto-response to emails sent to the -owner
-# address?
+# Skal Mailman sende et automatisk svar p&aring; e-mail der sendes til
+# -owner adressen?
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 autorespond_admin = 0
 
-# Auto-response text to send to -owner emails.
+# Automatisk svar p&aring; e-mail til -owner adressen.
 autoresponse_admin_text = ''
 
-# 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.
+# 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
+# ogs&aring; skal v&aelig;re med i det automatiske svar.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes, w/discard"
-#    2 = "Yes, w/forward"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja, men uden den originale e-mailn"
+#    2 = "Ja, og medtag den originale e-mail"
 autorespond_requests = 0
 
-# Auto-response text to send to -request emails.
+# Automatisk svar p&aring; e-mail til -request adressen.
 autoresponse_request_text = ''
 
-# 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).
+# Antal dage imellem automatisk svar p&aring; e-mail, fra samme
+# afsender, til listen eller til -request/-owner adressene. S&aelig;t
+# denne v&aelig;rdi til 0 (eller et negativt tal) for at sende
+# automatisk svar hver gang.
 autoresponse_graceperiod = 90
 
 ## Contentfilter options
 #
-# 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.  Then, each
-# <tt>multipart/alternative</tt> section will be replaced by just the
-# first alternative that is non-empty after filtering.
-# 
-# <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?
+# Regler for indhold i e-mail sendt til listen.
+# 
+# <p>Filtrering af indhold fungerer således: når listen modtger en
+# e-mail og du har beskyttelse med filtrering af indhold, sammenlignes
+# først eventuelle ved- hæftelser imod <a
+# href="?VARHELP=contentfilter/filter_mime_types">MIME filtre</a>. Hvis
+# en vedhæftelse passer med et af disse filtre, blir vedhæftelsen
+# fjernet.
+# 
+# <p>Derefter sammenlignes eventuelle vedhæftelser imod <a
+# href="?VARHELP=contentfilter/pass_mime_types">gyldige MIME typer</a>,
+# hvis nogen er defineret. Alle vedhæftelser som ikke passer med de
+# angivne MIME typene, blir fjernet.
+# 
+# <p>Efter disse filtre, vil alle tomme <tt>multipart</tt> vedhæftelser
+# blive fjernet. Hvis selve meddelelsen er helt tom efter denne
+# filtrering, vil meddelelsen bli afvist. Derefter vil hvert
+# <tt>multipart/alternative</tt> vedhæftelse blive erstattet af det
+# første alternative som ikke er tomt.
+# 
+# <p>Til slut vil alle <tt>text/html</tt> vedhæftelser som måtte være
+# tilbage i meddelelsen blive konverteret til <tt>text/plain</tt>
+# såfremt <a
+# href="?VARHELP=contentfilter/convert_html_to_plaintext">konvertere til
+# ren tekst</a> er sat til og serveren er konfigurert til at tillade
+# sådanne konverteringer.
+
+# Skal Mailman filtrere indhold i e-mail sendt til listen som angivet
+# nedenfor?
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 filter_content = 0
 
-# 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.
+# Brug denne instilling til at fjerne vedhæftelser der passer til MIME
+# typer. Hver linie skal her indeholde navnet på en MIME type/subtype,
+# f.eks. image/gif. Såfremt du ønsker at fjerne alle vedhæftelser som
+# har en given hoved MIME type, kan du lade være at angive subtype,
+# f.eks. image.
 # 
-# Blank lines are ignored.
+# Blanke linier medtages ikke.
 # 
-# See also <a href="?VARHELP=contentfilter/pass_mime_types"
-# >pass_mime_types for a content type whitelist.
+# Se også gyldige MIME typer for whitelist af MIME typer.
 filter_mime_types = ''
 
-# 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.
+# Brug denne indstilling for at definere hvilke MIME typer der skal være
+# tilladt. Krav og format for filtrering er identisk med MIME filtre.
 # 
-# 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.
+# Bem&aelig;rk: hvis du lægger noget ind her, men ikke angiver
+# multipart, vil al e-mail med vedhæftelser ikke blive medtaget.
 pass_mime_types = """multipart/mixed
 multipart/alternative
 text/plain"""
 
-# Should Mailman convert text/html parts to plain text?  This conversion
-# happens after MIME attachments have been stripped.
+# Skal Mailman konvertere text/html dele til ren tekst? Denne
+# konvertering vil finde sted efter at MIME filteret har fjernet de
+# ønskede dele.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 convert_html_to_plaintext = 1
 
-# One of these actions is take 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.
+# Her bestemmer du hvad der skal ske når en meddelelse filtreres fra af
+# et filter, altså såfremt vedhæftelsen filtreres fra MIME filteret,
+# eller ent vedhæftelse ikke har en af de gyldige MIME typer, eller
+# meddelelsen ender op med at være tom efter filtrering.
+# 
+# Bemærk at det du vælger her ikke vil ske såfremt en meddelelse stadig
+# indeholder noget efter filtrering. Så vil meddelelsen altid sendes
+# videre til listen.
+# 
+# Når meddelelsen afvises, skrives Message-ID'en til den afviste
+# meddelelse til loggen. Når meddelelsen sendes retur eller videresendes
+# til listens ejer, vil en begrundelse altid blive inkluderet i
+# returmail der sendes til afsenderen. Når meddelelserne skal bevares,
+# gemmes de i en specielt køkatalog på disk sådan at
+# serveradministratoren kan se (og måske gøre noget med) meddelelsen,
+# men ellers fjernet. Dette sidste valg er kun tilgængeligt såfremt
+# serveradministratoren har tilladt det.
 #
-# legal values are:
-#    0 = "Discard"
-#    1 = "Reject"
-#    2 = "Forward to List Owner"
-#    3 = "Preserve"
+# gyldige værdier:
+#    0 = "Kassere"
+#    1 = "Afvis"
+#    2 = "Videresend til Listens Ejer"
+#    3 = "Tag hånd om"
 filter_action = 0
 
 ## Topics options
 #
-# 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.
+# Emneord for listen
+
+# Emnefilteret kategoriserer hver e-mail som kommer til listen, efter
+# regexp-uttrykkene du skriver nedenfor. Hvis feltene Subject: eller
+# Keywords: i mailhovedet i en mail passer imod disse udtryk, blir den
+# placeret under dette emne. Hvert medlem af listen kan vælge kun at
+# modtage mail der passer til de &oslash;nskede emner. e-mail som ikke
+# g&aring;r under noget emne, blir ikke leveret.
+# 
+# Bemerk: Dette fungerer kun i normal-modus, ikke i sammendrag-modus.
+# 
+# Indholdet i len kan ogs&aring; unders&oslash;ges for Subject: og
+# Keyword: felter, alt efter hvad indstillingen topics_bodylines_limit
+# er sat til.
 #
-# legal values are:
-#    0 = "Disabled"
-#    1 = "Enabled"
+# gyldige værdier:
+#    0 = "Ikke tilgængelig"
+#    1 = "Tilgængelig"
 topics_enabled = 0
 
-# 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.
-# 
+# Her opgiver du hvor mange linier af mailens indhold som emnefilteret
+# skal s&oslash;ge igennem. En s&oslash;gning stopper n&aring;r s&aring;
+# mange linier er gennoms&oslash;gt, eller n&aring;r det m&oslash;der en
+# linie som ikke ser ud som et meddelelsesfelt. Ved at sætte denne til
+# null (0), vil ingen linier i indholdet blive unders&oslash;gt (dvs.
+# kun Keywords: og Subject: i meddelelseshovedet unders&oslash;ges). Ved
+# at sætte denne værdi til et negativt tal, vil alle linier blive
+# unders&oslash;gt frem til den f&oslash;rste linie som ikke ser ut som
+# et mailhoved-felt.
 topics_bodylines_limit = 5
 
-# 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.
+# Hvert emneord er faktisk et regexp-udtryk, der sammenlignes imod dele
+# af mailen, nemlig feltene Keywords: og Subject: i meldingshodet.
+# Bem&aelig;rk at de f&oslash;ste linier i mailens indhold ogs&aring;
+# kan best&aring; af s&aring;danne "felter", og kan dermed ogs&aring;
+# bli unders&oslash;gt.
 topics = []
 
diff --git a/mailman/friends.py b/mailman/friends.py
index 37cab57..98c9d3b 100644
--- a/mailman/friends.py
+++ b/mailman/friends.py
@@ -1,366 +1,390 @@
-## "friends" mailing list configuration settings -*- python -*-
-## captured on Wed Mar 16 02:41:00 2005
+## Indstillinger for maillisten "friends"  -*- python -*-
+## Dato: Thu May  5 09:52:39 2005
 
 ## General options
 #
-# 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 :-)
+# Grundlæggende egenskaber for listen, blant andet en beskrivelse af
+# listen, og hvordan den opf&oslash;rer sig.
+
+# Her kan du f.eks. stave navnet med stort forbogstav, eller ændre visse
+# bogstaver til store sådan at navnet kan udtales p&aring; en rigtig
+# m&aring;de eller at forkortelser fremhæves. Bemærk at dette navn
+# bruges i e-maillistens adresse (f.eks. i bekræftigelser ved
+# tilmeldinger), s&aring; der 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 :-)
 real_name = 'Friends'
 
-# 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.
+# Der er to roller forbundet med hver mailliste. Listeadministratorene
+# 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.
+# 
+# Listemoderatorene har begrænset adgang; de kan ikke ændre
+# indstillinger for e-maillisten, men de kan tage sig af
+# foresp&oslash;rgsler i forbindlse med listen, f.eks. ans&oslash;gning
+# om medlemskab, eller godkende/afvise meddelelser der skal godkendes
+# for at kunne udsendes til listen. Listeadministratorene kan ogs&aring;
+# udf&oslash;re disse opgaver.
+# 
+# For at aktivere muligheden for at have listemoderatorer, og p&aring;
+# den m&aring;de opdele arbejdsopgaverne forbundet med listen, skal du
+# s&aelig;tte dit eget moderatorpassword, og angive din
+# e-mailadressen(e) til den/de som skal v&aelig;re listemoderator(er).
+# Bemærk at i tekstboksene nedenfor skal du skrive e-mailadressen(e) til
+# listeadministratoren(e).
 owner = ['dr@jones.dk']
 
-# 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.
+# Det er to ejerskab forbundet med hver mailliste. Listeadministratorene
+# er dem der har den endelige kontrol over alle indstillingerne for
+# e-mallisten. De kan &aelig;ndre alle indstillinger der er tilgengelige
+# via disse administrative websider.
+# 
+# Listemoderatorene har begr&aelig;nset adgang; de kan ikke &aelig;ndre
+# indstillinger for e-maillisten, men de kan tage sig af
+# foresp&oslash;rgsler ang&aring;ende listen, f.eks. ans&oslash;gning om
+# medlemskab, eller godkende/afvise meddelelser der skal godkendes for
+# at kunne udsendes p&aring; listen. Listeadministratorene kan selvsagt
+# ogs&aring; udf&oslash;re disse opgaver.
+# 
+# For at aktivere muligheten for at have listemoderatorer, og p&aring;
+# den m&aring;den opdele arbejdsopgaverne der er forbundet med listen,
+# skal du s&aelig;tte dit eget moderatorpassword, og indtaste din
+# e-mailadresse(r) til den/de der skal v&aelig;re listemoderator(er).
+# Bemærk at i tekstboksene nedenfor skal du skrive e-mailadressen(e) til
+# listemoderatoren(e).
 moderator = []
 
-# 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.
+# Denne beskrivelsen 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 gj&oslash;re det uklart
+# hvad meningen med maillisten er eller hvad den skal bruges til.
 description = 'News about me to all of my friends'
 
-# 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.
+# Teksten tolkes som html bortset fra linieskift, der vil blive
+# &aelig;ndret til html-tag'en '<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. Benytter du html-kode,
+# husk da at gennemse meget grundigt, for fejl (f.eks. manglende
+# slutt-tag's) kan f&oslash;re til at listens informationsside ikke vil
+# vises s&aring;dan som den skal.
 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.
-# 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 er sat ind foran emne-/tittelfeltet i e-mail der sendes
+# til listen, for at skille e-mailliste-meddelelser i e-mailboksen fra
+# dem der er medlem af listen. Denne tekst b&oslash;r holdes p&aring; et
+# absolut minimum, benytter du f.eks. listens navn og navnet er langt,
+# b&oslash;r du stave det endnu kortere her. Men den b&oslash;r fremover
+# v&aelig;re beskrivende for listen.
 subject_prefix = '[Friends] '
 
-# Hide the sender of a message, replacing it with the list address
-# (Removes From, Sender and Reply-To fields)
+# Skjule afsenderen af meddelser, ved at erstatte den med e-maillistens
+# adresse (Dette medfører at alle From:, Sender, og Reply-To: felter
+# fjernes)
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 anonymous_list = 0
 
-# 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.
+# Skal eksisterende Reply-To: felt i meddelelseshovedet fjernes? Hvis ja
+# vil dette blive gjort uanset om Mailman tlføjer et Reply-To: felt
+# eller ikke.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 first_strip_reply_to = 0
 
-# 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.org/essays/reply-to-useful.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.
+# Denne indstillling fort&aelig;ller hvad Mailman skal gj&oslash;re med
+# Reply-To: feltet i meddelelseshovedet 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;dan 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 diskusion omkring
+# emnet. Se Reply-To Munging Considered Useful for modsatte meninger.
+# 
+# Nogle maillister har begr&aelig;nset adgang, med en egen parallell
+# liste beregnet til diskutioner. Eksempler p&aring; dette er 'patches'
+# eller 'checkin' lister, som system for revisionskontrol sender
+# &aelig;ndringer i programmet til, men diskusioner omkring udvikling af
+# programmet sendes til udviklerenes 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 diskusionsliste.
 #
-# legal values are:
-#    0 = "Poster"
-#    1 = "This list"
-#    2 = "Explicit address"
+# gyldige værdier:
+#    0 = "Afsender"
+#    1 = "mail listens adresse"
+#    2 = "Egendefineret adresse"
 reply_goes_to_list = 0
 
-# 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.org/essays/reply-to-useful.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.
+# 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 modifikasion af Reply-To:
+# adressen g&oslash;r det vanskeligere at sende svar kun til afsender.
+# Se 'Reply-To' Munging Considered Harmful for en diskusion omkring
+# temaet. Se Reply-To Munging Considered Useful for modsatte meninger.
+# 
+# Nogen maillister har begr&aelig;nset adgang, med en egen parallell
+# liste beregnet for diskusioner. Eksempler p&aring; dette er 'patches'
+# eller 'checkin' lister, som system for revisionskontrol sender
+# &aelig;ndringer til i programmet, men diskusioner rundt udvikling af
+# programmet sendes til udviklerenes egen mailliste. For at
+# st&oslash;tte s&aring;danne maillister, definer Reply-To: adressen
+# her, og vælg Egendefineret adresse i indstillingen reply_goes_to_list.
+# 
+# Bem&aelig;rk at hvis den oprindelige meddelse indeholder et Reply-To:
+# felt, vil det ikke &aelig;ndres.
 reply_to_address = ''
 
-# 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.
+# S&aelig;t denne til 'ja' hvis listen skal bruges som en "paraply" for
+# flere andre lister. N&aring;r denne er sat, vil bekr&aelig;ftigelser
+# og meddelelser med password blive sendt til en egen adresse som
+# beregnes ud fra e-mailadressen som er tilmeldt listen - v&aelig;rdien
+# af indstillingen "umbrella_member_suffix" bruges til dette. Denne
+# v&aelig;rdi tilf&oslash;jes til medlemmets kontonavn (det som
+# st&aring;r f&oslash;r @-tegnet).
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 umbrella_list = 0
 
-# 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".
+# N&aring;r "umbrella_list" indikerer at denne liste har andre
+# maillister som medlemmer, er det som regel &oslash;nskelig at
+# administrative meddelelser som f.eks. bekr&aelig;ftigelser og password
+# reminders ikke sendes til selve listen som er medlem, men til
+# administratoren for listen. Hvis dette er tilf&aelig;ldet, bruges
+# v&aelig;rdien af denne indstilling til at bestemme adressen sådan at
+# 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".
 umbrella_member_suffix = '-owner'
 
-# 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.
+# S&aelig;tt denne til hvis du vil have at password reminder skal sendes
+# til medlemmene en gang hver m&aring;ned. Husk at medlemmene kan
+# ogs&aring; selv frav&aelig;lge dette.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 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.
+# Tekst du skriver her vil blive tilf&oslash;jet &oslash;verst i
+# velkomsthilsenen der sendes til nye medlemmer. Velkomshilsenen
+# indeholder allerede viktige adresser og URLer knyttet til maillisten,
+# s&aring; sådan information er det ikke n&oslash;dvendig at inkludere
+# her. Her kan du indl&oslash;gge f.eks. oplysning om etikette eller
+# regler for brug af listen, o.l.
+# 
+# Bem&oslash;rk: Liniene i denne tekst vil brydes efter f&oslash;lgende
+# regler:
 # 
-# 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.
+# Hvert afsnit udfyldes s&aringdan at ingen linie er lenger en 70 tegn.
+# Enhver linie der begynder med blanke tegn udfyldes ikke. Blanke linier
+# adskiller afsnitt.
 # 
 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..."""
 
-# 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.
+# S&aelig;t kun denne til 'Nej' hvis du skal il&aelig;gge nye medlemmer
+# manuelt, og ikke vil have de skal f&aring; dette 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.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 send_welcome_msg = 1
 
-# Text sent to people leaving the list.  If empty, no special text will
-# be added to the unsubscribe message.
+# Tekst der sendes til medlemmer der framelder sig fra listen. Hvis
+# denne er tom, l&aelig;gges det ikke noget tekst til frameldelsen.
 goodbye_msg = ''
 
-# Send goodbye message to members when they are unsubscribed?
+# Sende afskedshilsen til medlemmer n&aring;r de frameldes?
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 send_goodbye_msg = 1
 
-# 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.
+# Der udsendes en reminder til listemoderatoren(e) (og
+# listeadministratoren(e)) dagligt om foresp&oslash;rsler der af en
+# eller anden grund venter p&aring; behandling. V&aelig;lger du "Ja",
+# vil listeadminstratoren ogs&aring; motdtage en meddelelse s&aring;
+# snart en foresp&oslash;rsel kommer ind.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 admin_immed_notify = 1
 
-# Should administrator get notices of subscribes and unsubscribes?
+# Skal listeadministratoren(e) ogs&aring; modtage meddelelse om nye
+# medlemmer der tilmelder sig og gamle medlemmer som framelder sig?
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 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.
+# Besked om at en meddelelse skal godkendes sendes ud til afsenderen
+# s&aring;fremt meddelelsen stoppes pga. noget andet end listemoderation
+# eller spam filtre. S&aelig;ttes denne indstilling til 'Nej', vil
+# afsender overhovedet ikke modtage denne besked.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 respond_to_post_requests = 1
 
-# 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.
+# Når dette valg er aktiveret, vil alt e-mail til listen blive moderert.
+# 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-moderasjon" kan da hjælpe dig at fjerne usaglige meddelelser
+# til listen, og på den måden dysse en ophedet diskusion ned.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 emergency = 0
 
-# When a new member is subscribed to this list, their initial set of
-# options is taken from the this variable's setting.
+# Når et nyt medlem tilmeldes listen, blir medlemmets indstillinger
+# taget herfra.
 new_member_options = 256
 
-# 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.
+# Filter for administrative meddelelser vil unders&oslash;ge om
+# meddelelsen egentligt er ment som en administrativ foresp&oslash;rgsel
+# (f.eks. tilmelding, framelding, o.l.), og is&aring;fald sende
+# meddelelsen til administratoren i stedet.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 administrivia = 1
 
-# Maximum length in kilobytes (KB) of a message body.  Use 0 for no
-# limit.
+# Maximum st&oslash;rrelse i kilobytes (KB) for indholdet i e-mail der
+# sendes til listen. Brug verdien '0' for ikke at have en
+# begr&aelig;nsning.
 max_message_size = 40
 
-# 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.
+# "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; denne maskinen. Denne
+# indstillingen kan v&aelig;re nyttig hvis maskinen har flere navne.
 host_name = 'jones.dk'
 
-# 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).
+# I RFC 2369 defineres en r&aelig;kke List-* felter i
+# meddelelseshovedet, der normalt tilf&oslash;jes hver meddelelse der
+# sendes ud via listen. Disse felter kan hj&aelig;lpe de brugere af
+# listen der benytter et e-mailprogram som f&oslash;lger denne standard.
+# Disse felter b&oslash;r derfor altid v&aelig;re med.
+# 
+# Ikke alle e-mailprogrammer f&oslash;lger denne standard. Er det mange
+# af medlemmene p&aring; listen der benytter s&aring;danne
+# e-mailprogrammer, der ikke kan h&aring;ndtere disse felter i
+# meddelelseshovedet, kan det v&aelig;re du vil v&aelig;lge at udelade
+# dem. Men du b&oslash;r f&oslash;rst fors&oslash;ge at l&aelig;re og
+# forklare medlemmene 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 disse felter, men dette anbefales ikke (denne
+# muligheten kan faktisk ogs&aring; blive fjernet i senere versioner).
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 include_rfc2369_headers = 1
 
-# 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.)
+# List-Post: feltet er et af felterne anbefalet i RFC 2369. Visse
+# e-maillister (som f.eks. kun bruges til offentligørelser), er det kun
+# visse personer der har lov til at sende til; de som er medlem af
+# listen har generelt ikke lov til at sende til listen. For disse
+# lister, er List-Post: feltet forvirrende. I visse tilf&aelig;lde kan
+# det være forvirrende at s&aelig;tte denne indstilling til Nej,
+# s&aring; feltet ikke tilføjes. (Dette påvirker ikke andre List-*:
+# felter.)
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 include_list_post_header = 1
 
 ## Language options
 #
-# 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.
+# Underst&oslash;ttelse for flere sprog. (Internationalisering)
+
+# Dette er standardsproget som benyttes for denne mailliste. Hvis mer
+# 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.
 preferred_language = 'en'
 
-# These are all the natural languages supported by this list. Note that
-# the default language must be included.
+# Her er alle spr&aring;gene denne listen har underst&oslash;ttelse for.
+# Bem&aelig;rk at standardsproget skal v&aelig;re med.
 available_languages = ['da', 'en']
 
-# 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.
+# Hvis standardsproget for din mailliste benytter et andet tegns&aelig;t
+# end ASCII og tittel prefixet for listen indeholder tegn som ikke
+# findes i ASCII-tegns&aelig;ttet, vil prefixet alltid blive kodet i
+# henhold til den relevante standard. Hvis tittel prefixet kun
+# indeholder ASCII tegn, kan det imidlertid ske at du ønsker at sætte
+# dette valg til Aldrig for at undgå koding. Dette kan gøre titlen lidt
+# mere læselig for brugere med e-mailprogrammer der ikke takler andre
+# tegnsæt end ASCII på en rigtig måde.
+# 
+# Bemærk imidlertid at hvis din mailliste modtager både kodede og
+# ukodede tittel felt, kan det være bedst at vælge Efter behov. Med
+# denne indstilling vil Mailman ikke kode ASCII prefixer hvis resten af
+# tittelfeltet kun indeholder ASCII tegn, men vil kode prefixet hvis det
+# indeholder tegn som ikke er ASCII tegn. På denne måde undgås en [...]
+# i standarderne, som forårsager at visse e-mailprogrammer vil vise
+# ekstra eller manglende mellemrum imellom tittel prefixet og det
+# oprindelige tittelfelt.
 #
-# legal values are:
-#    0 = "Never"
-#    1 = "Always"
-#    2 = "As needed"
+# gyldige værdier:
+#    0 = "Aldrig"
+#    1 = "Altid"
+#    2 = "Efter behov"
 encode_ascii_prefixes = 0
 
 ## Nondigest options
 #
-# Policies concerning immediately delivered list traffic.
+# Regler for levering i normal-modus.
 
-# Can subscribers choose to receive mail immediately, rather than in
-# batched digests?
+# Kan medlemmer vælge normal-modus?
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 nondigestable = 1
 
-# 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:
+# 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:
 # 
 # 
 # real_name - The "pretty" name of the list; usually the list name with
@@ -385,9 +409,10 @@ nondigestable = 1
 # 
 msg_header = ''
 
-# 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:
+# Tekst som tilf&aelig;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:
 # 
 # 
 # real_name - The "pretty" name of the list; usually the list name with
@@ -416,42 +441,44 @@ msg_footer = """_______________________________________________
 
 ## Digest options
 #
-# Batched-delivery digest characteristics.
+# Opsætning af sammendrag-modus.
 
-# Can list members choose to receive list traffic bunched in digests?
+# Kan medlemmer af listen vælge at f&aring; tilsendt sammendrag i stedet
+# for?
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 digestable = 1
 
-# Which delivery mode is the default for new users?
+# Hvilken modus er standard for nye brugere?
 #
-# legal values are:
-#    0 = "Regular"
-#    1 = "Digest"
+# gyldige værdier:
+#    0 = "Normal"
+#    1 = "Sammendrag"
 digest_is_default = 0
 
-# When receiving digests, which format is default?
+# Hvilket format skal benyttes som standard for samle-email?
 #
-# legal values are:
-#    0 = "Plain"
+# gyldige værdier:
+#    0 = "Ren tekst"
 #    1 = "MIME"
 mime_is_default_digest = 0
 
-# How big in Kb should a digest be before it gets sent out?
+# Hvor stor (i Kb) m&aring; en samle-email h&oslash;jst v&aelig;re
+# f&oslash;r den udsendes?
 digest_size_threshhold = 30
 
-# Should a digest be dispatched daily when the size threshold isn't
-# reached?
+# Skal der sendes en samle-email dagligt, selv om st&oslash;rrelsen ikke
+# er opn&aring;et?
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 digest_send_periodic = 1
 
-# Text attached (as an initial message, before the table of contents) to
-# the top of digests. This text can include Python format strings which
+# Tekst som l&aelig;gges til &oslash;verst i samle-emailen, f&oslash;r
+# indholdsfortegnelsen.This text can include Python format strings which
 # are resolved against list attributes.  The list of substitutions
 # allowed are:
 # 
@@ -478,9 +505,10 @@ digest_send_periodic = 1
 # 
 digest_header = ''
 
-# 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:
+# Tekst der tilføjes nederst i hver samle-e-mail, som sidste
+# information.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
@@ -507,274 +535,277 @@ digest_footer = """_______________________________________________
 %(real_name)s maillist  -  %(real_name)s@%(host_name)s
 %(web_page_url)slistinfo/%(_internal_name)s"""
 
-# When a new digest volume is started, the volume number is incremented
-# and the issue number is reset to 1.
+# N&aring;r et nyt volume startes, &oslash;ges volume nummeret, og
+# udgavenummeret s&aelig;ttes til 1.
 #
-# legal values are:
-#    0 = "Yearly"
-#    1 = "Monthly"
-#    2 = "Quarterly"
-#    3 = "Weekly"
-#    4 = "Daily"
+# gyldige værdier:
+#    0 = "&Aring;rlig"
+#    1 = "M&aring;nedlig"
+#    2 = "Kvartalsvis"
+#    3 = "Ugentlig"
+#    4 = "Daglig"
 digest_volume_frequency = 1
 
 ## Privacy options
 #
-# 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.
-
-# Advertise this list when people ask what lists are on this machine?
+# Her kan du bestemme hvad der kr&oslash;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&oslash;lder
+# arkivet og arkivering.
+
+# Vise denne mailliste n&aring;r nogn beder om at se en oversigt over
+# maillister p&aring; denne maskine?
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 advertised = 1
 
-# 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.
+# bek&aelig;ftigelse(*) - bekr&aelig;ftigelse af e-mail er
+# n&oslash;dvendig godkendelse - ans&oslash;gkning om medlemskabp skal
+# godkendes af listeadministrator (eller evt. listemoderator)
+# bekr&aelig;ftigelse+godkendelse - b&aring;de bekr&aelig;ftelse
+# p&aring; e-mail og godkendelse af listeadministrator (evt.
+# listemoderator) er nun&oslash;dvendig
+# 
+# (*) n&aring;r nogen vil tilmelde sig en liste, sender Mailman en
+# meddelelse med et uniktidentifikator som de skal opgive for at
+# bekr&oslash;fte tilmeldingen. P&aring; denne m&aring;den vil det da
+# ikke v&aelig;re muligt at tilmelde nogen til listen imod deres vilje.
 #
-# legal values are:
-#    1 = "Confirm"
-#    2 = "Require approval"
-#    3 = "Confirm and approve"
+# gyldige værdier:
+#    1 = "Bekr&aelig;ftigelse"
+#    2 = "Godkendelse"
+#    3 = "Bekr&aelig;ftigelse og godkendelse"
 subscribe_policy = 1
 
-# 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.
+# N&aring;r medlemmer &oslash;nsker at forlade en mailliste, sender de
+# en ans&oslash;gning om framelding, enten via web, eller via e-mail.
+# Normalt er det best at disse ans&oslash;gninger automatisk godkendes,
+# s&aring; meldemmer kan udmelde sig n&aring;r de &oslash;nsker det
+# (mange &oslash;nsker selv at kunne administrere en frameldelse. For
+# nogen f&aring; maillister kan det aligevel v&aelig;re aktuelt at have
+# kontrol over om medlemmer kan melde sig selv ud eller ikke. En liste
+# som alle ansatte i et firma M&Aring; v&aelig;re medlem af, er et
+# eksempel p&aring; en s&aring;dan liste.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 unsubscribe_policy = 0
 
-# 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.
+# Alle e-mailadresser som angives her vil blive udelukket fra listen, og
+# kan ikke tilmelde sig. Indtast e-mailadresser, en per linie, start
+# linien med tegnet ^ for at angive et regexp-udtryk der skal passe med
+# afsenderadressen.
 ban_list = []
 
-# When set, the list of subscribers is protected by member or admin
-# password authentication.
+# Hvis denne indstilling er sat til, vil listen over medlemmer af
+# e-maillisten blive beskyttet af medlemmenes eller adminstratorens
+# password.
 #
-# legal values are:
-#    0 = "Anyone"
-#    1 = "List members"
-#    2 = "List admin only"
+# gyldige værdier:
+#    0 = "Alle"
+#    1 = "Kun medlemmer af listen"
+#    2 = "Kun listeadministrator"
 private_roster = 1
 
-# 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.
+# V&aelig;lger du 'Ja' her, vil medlemmers e-mailadresse omskrives
+# n&aring;r de vises i en oversigt p&aring; websidene (b&aring;de som
+# tekst og i linker), s&aring; de ikke er nemme at tolke som
+# e-mailadresser. Meningen med dette er at undg&aring; at e-mailsniffere
+# der gennemg&aring;r websider for at finde e-mailadresser (og derefter
+# bruge dem til at udsende spam/junk mail) til ikke at opsamle
+# medlemmenes e-mailadresser.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 obscure_addresses = 1
 
 ## Privacy options
 #
-# 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.
+# N&aring;r en meddelelse sendes til maillisten, g&aring;r den igennem
+# en r&aelig;kke trin for at afg&oslash;re om moderatoren m&aring;
+# godkende meddelelsen eller ikke. Her finder du indstillinger for 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 de sendes til listen.
+# 
+# <p>e-mail som ikke er sendt af medlemmer af listen, kan automatisk bli
+# <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">sendt
+# retur</a>, eller <a
+# href="?VARHELP=privacy/sender/discard_these_nonmembers">afvist</a>,
+# enten individuelt eller som en gruppe. All e-mail fra ikke-medlemmer,
+# som ikke specifikt bliver godkent, sendes retur, eller afvist, 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 il&aelig;gger du en e-mailadresse per
+# linie. Du kan ogs&aring; il&aelig;gge  <a
+# href="http://www.python.org/doc/current/lib/module-re.html">Python
+# regexp-uttrykk</a>. Begynd is&aring;fald linien med tegnet ^ for at
+# markere at det er et s&aring;dan udtryk. N&aring;r du benytter
+# backslash, skriv da lige som i rene strings (Python raw strings)
+# (normalt kun &eacute;n backslash af gangen).
+# 
+# <p>Bem&aelig;rk: match p&aring; 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-mail fra medlemmet kan sendes direkte til e-maillisten, eller om de
+# f&oslash;rst skal godkendes af listemoderatoren. N&aring;r
+# moderationsflaget er sat til, skal e-mail fra medlemmet godkendes af
+# listemoderatoren f&oslash;r det udsendes til alle p&aring; listen. Som
+# listeadminsitrator kan du for hvert enkelt medlem bestemme om
+# medlemmets e-mail skal modereres eller ikke. N&aring;r et nyt medlem
+# tilmeldes til 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
+# Administrere medlemmer siden.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 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.
 # 
-# Discard -- this simply discards the message, with no notice sent to
-# the post's author.
+# Holde tilbage -- meldingen holdes tilbage for godkendelse af
+# listemoderatoren(e). Afslå -- meldingen sendes automatisk retur til
+# afsender. Begrundelsen der sendes kan du skrive selv Slette --
+# meddelelsen blir afvist uden at give besked om dette til afsender.
 # 
 #
-# legal values are:
-#    0 = "Hold"
-#    1 = "Reject"
-#    2 = "Discard"
+# gyldige værdier:
+#    0 = "Holde&nbsp;tilbage"
+#    1 = "Afvis"
+#    2 = "Kassere"
 member_moderation_action = 0
 
-# 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.
+# Tekst som skal sendes med meldingen om retur som sendes til modereede
+# medlemmer af listen.
 member_moderation_notice = ''
 
-# 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.
+# e-mail fra disse ikke-medlemmer vil automatisk blive godkendt.
+# Il&aelig;g e-mailadresser, en per linie, start linien med tegnet ^ for
+# at angive et regexp-uttryk som skal passe med afsenderadressen.
 accept_these_nonmembers = ['dr@jones.dk', 'dr.jones@pobox.com']
 
-# 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.
+# e-mail fra disse ikke-medlemmer vil automatisk blive holdt tilbage for
+# vurdering af listemoderatorene. Afsenderen vil modtage en meddelelse
+# om dette, med bl.a. instruktioner om hvordan han/hun kan
+# tilbagetr&aelig;kke sin e-mails. Indtast e-mailadresser, en per linie,
+# start linien med tegnet ^ for at angive et regexp-uttrykk som skal
+# passe med afsenderadressen.
 hold_these_nonmembers = []
 
-# 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.
+# 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 spam-afsendere,
+# de b&oslash;r automatisk afvises. Indtast e-mailadresser, en per
+# linie, start linien med tegnet ^ for &aring; angiv et regexp-uttrykk
+# som skal passe med afsenderadressen.
 reject_these_nonmembers = []
 
-# 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.
+# e-mail fra disse ikke-medlemmer vil automatisk blive afvist. Det vil
+# sige at meddelelsen afvises uden nogen form for tilbagemelding, men
+# listemoderatorene kan (om ønskeligt) modtage en kopi af den afviste
+# e-mail. Tilf&oslash;je e-mailadresser, en per linie, start linien med
+# tegnet ^ for at angive et regexp-uttryk der skal passe med
+# afsenderadressen.
 discard_these_nonmembers = []
 
-# 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.
+# N&aring;r en e-mail fra et ikke-medlem blir modtaget, sammenlignes
+# e-mailens afsender med listen over e-mailadresser der skal godkendes,
+# holdes tilbage, afvises (sendes i retur), og afvises. Hvis
+# afsenderadressen ikke passer med den der er opgivet i listene, blir
+# f&oslash;lgende afg&oslash;relse taget.
 #
-# legal values are:
-#    0 = "Accept"
-#    1 = "Hold"
-#    2 = "Reject"
-#    3 = "Discard"
+# gyldige værdier:
+#    0 = "Godkende"
+#    1 = "Holde&nbsp;tilbage"
+#    2 = "Afvis"
+#    3 = "Kassere"
 generic_nonmember_action = 1
 
-# Should messages from non-members, which are automatically discarded,
-# be forwarded to the list moderator?
+# Skal meddelelser fra ikke-medlemmer, som automatisk afvises, også
+# sendes til listemoderatoren?
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 forward_auto_discards = 1
 
 ## Privacy options
 #
-# This section allows you to configure various filters based on the
-# recipient of the message.
+# Her kan du ops&aelig;tte filtrering baseret på modtaeren af
+# meddelelsen.
 
-# 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.
+# Meget (faktisk det meste af) spam/junk mail har ikke de endelige
+# modtagere i modtagerfelterne. Faktisk s&aring; indeholder felterne To:
+# og/eller Cc: oftest en fuldst&aelig;ndig 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(e), men vil
+# aligevel blive fanget og blokkere det meste af spam/junk mail.
 # 
-# 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 ville 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
+# alias for listen.
 # 
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 require_explicit_destination = 1
 
-# 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.
+# Alternative e-mailadresser som godtages n&aring;r
+# 'require_explicit_destination' er sat til. Som v&aelig;rdi for denne
+# indstilling skal du opgive regexp-uttryk ("regular expressions"), et
+# udtryk per linie, der sammenlignes imod 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 imod den f&oslash;rste
+# del (det som st&aring;r f&oslash;r '@') af modtageradressen. Hvis
+# sammenligningen ikke lykkes, eller hvis udtrykket ikke indholder en
+# '@', sammenlignes udtrykket med hele modtageradressen.
+# 
+# Sammenligning kun imod den f&oslash;rste del af en modtageradresse
+# underst&oslash;ttes ikke i fr&aelig;mtidige udgaver af Mailman, vil
+# kun sammenligning imod hele modtageradresser blive
+# underst&oslash;ttet.
 acceptable_aliases = ''
 
-# If a posting has this number, or more, of recipients, it is held for
-# admin approval.  Use 0 for no ceiling.
+# Hvis en mail der er sendt til listen indeholder s&aring; mange
+# modtagere som, eller flere modtagere end, denne værdi, holdes malen
+# tilbage så listeadministratoren eventuelt kan godkende den. Brug
+# værdien 0 for ingen begrænsning.
 max_num_recipients = 10
 
 ## Privacy options
 #
-# 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.
-# 
+# Her kan du opsætte forskellige anti-spam filtre, som kan være til
+# hjælp for 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
@@ -787,16 +818,20 @@ max_num_recipients = 10
 # match.
 header_filter_rules = []
 
-# 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.
+# Brug denne indstilling til at fra-filtrere mail til listen, baseret
+# p&aring; indholdet af et eller flere felter i mailhovedet. Her skal du
+# skrive regexp-uttryk (regular expressions), et per linie, som
+# sammenlignes mod det aktuelle felt. Sammenligningen sk&aelig;lner ikke
+# imellem store og sm&aring; bogstaver. Linier der begynder med '#'
+# sammenlignes ikke.
 # 
-# For example:to: .*@public.com  says to hold all postings with a To:
-# mail header containing '@public.com' anywhere among the addresses.
+# For eksempel: udtrykket to: .*@public.com fort&aelig;ller at alt mail
+# som indeholder '@public.com' i To: feltet, skal holdes tilbage til
+# godkendelse.
 # 
-# 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.
+# Bem&aelig;rk: blanke tegn i starten af regexp-udtrykket fjernes. Dette
+# kan man undg&aring; p&aring; flere m&aring;ter, f.eks. ved at bruge
+# escape-tegn eller parenteser.
 bounce_matching_headers = """# Lines that *start* with a '#' are comments.
 to: friend@public.com
 message-id: relay.comanche.denmark.eu
@@ -805,54 +840,56 @@ from: .*@uplinkpro.com"""
 
 ## Bounce options
 #
-# 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.
+# Disse regler bestemmer hvordan automatisk behandling af returmails
+# gj&oslash;res. Her er en oversigt over hvordan funktionen er.
+# 
+# <p>N&aring;r Mailman modtager en returmail, blir to ting
+# fors&oslash;kt tolket. Det ene er e-mailadressen til medlemmet som
+# egentlig skulle modtage e-mailen, og det andet er &aring;rsagen til
+# problemet. &Aring;rsagen tolkes til at v&aelig;re <em>alvorlig</em>
+# eller <em>lett</em> alt efter om &aring;rsagen er af kritisk eller af
+# mindre alvorlig art. Såfremt der er tvivl, tolkes &aring;rsaken som
+# alvorlig.
+# 
+# <p>Hvis ingen e-mailadresse kan hentes ud af meddelelsen, blir den
+# normalt afvist. Ellers, vil medlemmet som har e-mailadressen f&aring;
+# en <em>returtal</em>, og hver gang en returmeddelelse kommer vil
+# tallet &oslash;ges. Alvorlige &aring;rsaker f&oslash;rer til at tallet
+# &oslash;ges med 1, lette &aring;rsaker f&oslash;rer til at det
+# &oslash;kes med 0.5. Dette sker kun &eacute;n gang per dag, s&aring;
+# selv om det 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;ttest til igen.
+# Medlemmet vil med j&aelig;vne mellemrum modtage melding 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>Det er en vigtig indstilling til; efter en vis tid -- hvis ingen
+# returmeddelelser dukker op i l&oslash;bet af denne tid -- anses
+# returinformation som <a
+# href="?VARHELP=bounce/bounce_info_stale_after">udg&aring;et</a> og
+# afvises. Ved at justere denne værdi, og sætte en grænse for
+# returantallet, kan du bestemme hvor lang tid der skal gå f&oslash;r
+# levering til et medlem stoppes. Begge disse værdier skal du justere
+# alt efter hvor ofte og hvor meget e-mail der sendes til din liste.
+
+# Ved at sætte denne værdi til Nej, sætter du alt automatisk tolking af
+# returmeddelelser for denne liste fra. Bemærk at såfremt meddelelser
+# afvises vil listeadministratoren ikke blive forstyrret med dem.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 bounce_processing = 1
 
 # Each subscriber is assigned a bounce score, as a floating point
@@ -868,351 +905,345 @@ bounce_processing = 1
 # mailing list.
 bounce_score_threshold = 5.0
 
-# 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.
+# Antal dage f&oslash;r returinformation afvises såfremt der ikke dukker
+# flere returmails op. Dette tal skal v&aelig;re et heltal.
 bounce_info_stale_after = 7
 
-# 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.
+# Hvor mange Levering til dig er stoppet advarsler der skal sendes til
+# et medlem f&oslash;r medlemmet frameldes fra listen. S&aelig;t denne
+# værdi til 0 for at fjerne et medlem fra listen umiddelbart
+# s&aring;fremt der kommer returmails fra medlemmets e-mailadresse.
+# Dette tal skal være et heltal.
 bounce_you_are_disabled_warnings = 3
 
-# The number of days between sending the Your Membership Is Disabled
-# warnings.  This value must be an integer.
+# Antal dage imellem hver gang en Levering til dig er stoppet advarsel
+# skal sendes ud. Dette tal skal være et heltal.
 bounce_you_are_disabled_warnings_interval = 7
 
-# 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.
+# Mailmans automatiske returmailhåndtering er meget robust, men det er
+# aligevel umuligt at genkende alle typer returmails der kommer. Du bør
+# angive Ja her, af to grunde: 1) Hvis det virkelig er en permanent
+# returmail fra et medlem af listen, bør du antageligt manuelt udmelde
+# medlemmet fra listen, og 2) du vil måske sende meddelelse til
+# udviklerne af Mailman sådan at returmails automatisk genkendes af
+# Mailman i senere versioner. Hvis du ikke vil gøre nogen af delene, sæt
+# da denne indstilling til Nej. Så vil alle returmails afvises
+# automatisk uden videre behandling. Bem&aelig;rk: Denne indstilling vil
+# også indvirke på alt e-mail der sendes til listens -admin adresse. Den
+# adresse er gammel og udgået, men det kan være at nogen fortsat vil
+# sende e-mail til den. Hvis nogen gør det, og du har sat denne
+# indstilling til Nej, vil disse mails også blive afvist. Måske vil du
+# også opsætte et automatisk svar på e-mail sendt til -owner og -admin
+# adresserne.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 bounce_unrecognized_goes_to_list_owner = 1
 
-# 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.
+# Ved at sætte denne til Nej, fravælges beskeden der normalt sendes til
+# ejeren(e) af listen, når afsending 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.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 bounce_notify_owner_on_disable = 1
 
-# 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.
+# Ved at sætte denne til Nej, fravælges beskeden der normalt sendes til
+# ejeren(e) af listen, når et medlem frameldes fra listen på grund af
+# for mange returmails. Der vil til gengæld altid blive forsøgt afsendt
+# en e-mail med besked til medlemmet.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 bounce_notify_owner_on_removal = 1
 
 ## Archive options
 #
-# List traffic archival policies.
+# Regler for arkivering
 
-# Archive messages?
+# Arkivere e-mail i et arkiv?
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 archive = 1
 
-# Is archive file source for public or private archival?
+# Skal filen arkiveres i et privat eller i et offentlig arkiv?
 #
-# legal values are:
-#    0 = "public"
-#    1 = "private"
+# gyldige værdier:
+#    0 = "offentlig"
+#    1 = "privat"
 archive_private = 0
 
-# How often should a new archive volume be started?
+# Hvor ofte skal arkivet deles op?
 #
-# legal values are:
-#    0 = "Yearly"
-#    1 = "Monthly"
-#    2 = "Quarterly"
-#    3 = "Weekly"
-#    4 = "Daily"
+# gyldige værdier:
+#    0 = "&Aring;rlig"
+#    1 = "M&aring;nedlig"
+#    2 = "Kvartalsvis"
+#    3 = "Ugentlig"
+#    4 = "Daglig"
 archive_volume_frequency = 0
 
 ## Gateway options
 #
-# Mail-to-News and News-to-Mail gateway services.
+# e-mail-Til-Nyhedsgruppe og Nyhedsgruppe-Til-e-mail tjeneste.
 
-# 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.
+# 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.
 nntp_host = ''
 
-# The name of the Usenet group to gateway to and/or from.
+# Navn p&aring; nyhedsgruppe der skal sendes til og/eller fra.
 linked_newsgroup = ''
 
-# Should new posts to the mailing list be sent to the newsgroup?
+# Skal nye mail til denne liste sendes til nyhedsgruppen?
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 gateway_to_news = 0
 
-# Should new posts to the newsgroup be sent to the mailing list?
+# Skal nye meddelelser til nyhedsgruppen sendes til denne mailliste?
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 gateway_to_mail = 0
 
-# 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.
+# 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&aring;t da 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
+# Moderet, vil en ekstra meddelelse holdes tilbage i
+# godkendelsesprocessen. Alt mail sendt til maillisten skal godkendes
+# f&oslash;r de sendes til nyhedsgruppen, eller til medlemmene af
+# listen.
+# 
+# Vær opm&aelig;rksom p&aring; at hvis mailhovedet i mailen har et
+# Approved: felt med listens administrative password, 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 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 meddelelseshovedet.
 #
-# legal values are:
-#    0 = "None"
-#    1 = "Open list, moderated group"
-#    2 = "Moderated"
+# gyldige værdier:
+#    0 = "Ingen"
+#    1 = "Åben liste, modereret nyhedsgruppe"
+#    2 = "Modereret"
 news_moderation = 0
 
-# 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.
+# Mailman tilføjer normalt en tekst du selv 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 sette denne indstilling
+# til Nej hvis du ikke ønsker emne prefix tilføjet til mail som sendes
+# til Usenet. Sætter du emne prefix for listen til off, vil opsamlet
+# meddelelser heller ikke få præfix tilføjet.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 news_prefix_subject_too = 1
 
 ## Autoreply options
 #
-# Auto-responder characteristics.<p>
+# Indstillinger for automatiske svar.<p>
 # 
-# 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>
+# 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 epostadresse</em>
+# <li><b>owneremail</b> - <em>listens -owner epostadresse</em> </ul>
 # 
-# <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.
+# <p>Du kan enten skrive teksten direkte i tekstboksene, eller du kan
+# angive navnet p&aring; en fil som indeholder teksten. Denne file vil
+# s&aring; blive indl&aelig;st i tekstboksen, fra dit lokale filsystem.
 
-# Should Mailman send an auto-response to mailing list posters?
+# Skal Mailman sende et automatisk svar til dem der sender e-mail til
+# listen?
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 autorespond_postings = 0
 
-# Auto-response text to send to mailing list posters.
+# Automatisk svar der skal sendes.
 autoresponse_postings_text = ''
 
-# Should Mailman send an auto-response to emails sent to the -owner
-# address?
+# Skal Mailman sende et automatisk svar p&aring; e-mail der sendes til
+# -owner adressen?
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 autorespond_admin = 0
 
-# Auto-response text to send to -owner emails.
+# Automatisk svar p&aring; e-mail til -owner adressen.
 autoresponse_admin_text = ''
 
-# 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.
+# 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
+# ogs&aring; skal v&aelig;re med i det automatiske svar.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes, w/discard"
-#    2 = "Yes, w/forward"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja, men uden den originale e-mailn"
+#    2 = "Ja, og medtag den originale e-mail"
 autorespond_requests = 0
 
-# Auto-response text to send to -request emails.
+# Automatisk svar p&aring; e-mail til -request adressen.
 autoresponse_request_text = ''
 
-# 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).
+# Antal dage imellem automatisk svar p&aring; e-mail, fra samme
+# afsender, til listen eller til -request/-owner adressene. S&aelig;t
+# denne v&aelig;rdi til 0 (eller et negativt tal) for at sende
+# automatisk svar hver gang.
 autoresponse_graceperiod = 90
 
 ## Contentfilter options
 #
-# 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.  Then, each
-# <tt>multipart/alternative</tt> section will be replaced by just the
-# first alternative that is non-empty after filtering.
-# 
-# <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?
+# Regler for indhold i e-mail sendt til listen.
+# 
+# <p>Filtrering af indhold fungerer således: når listen modtger en
+# e-mail og du har beskyttelse med filtrering af indhold, sammenlignes
+# først eventuelle ved- hæftelser imod <a
+# href="?VARHELP=contentfilter/filter_mime_types">MIME filtre</a>. Hvis
+# en vedhæftelse passer med et af disse filtre, blir vedhæftelsen
+# fjernet.
+# 
+# <p>Derefter sammenlignes eventuelle vedhæftelser imod <a
+# href="?VARHELP=contentfilter/pass_mime_types">gyldige MIME typer</a>,
+# hvis nogen er defineret. Alle vedhæftelser som ikke passer med de
+# angivne MIME typene, blir fjernet.
+# 
+# <p>Efter disse filtre, vil alle tomme <tt>multipart</tt> vedhæftelser
+# blive fjernet. Hvis selve meddelelsen er helt tom efter denne
+# filtrering, vil meddelelsen bli afvist. Derefter vil hvert
+# <tt>multipart/alternative</tt> vedhæftelse blive erstattet af det
+# første alternative som ikke er tomt.
+# 
+# <p>Til slut vil alle <tt>text/html</tt> vedhæftelser som måtte være
+# tilbage i meddelelsen blive konverteret til <tt>text/plain</tt>
+# såfremt <a
+# href="?VARHELP=contentfilter/convert_html_to_plaintext">konvertere til
+# ren tekst</a> er sat til og serveren er konfigurert til at tillade
+# sådanne konverteringer.
+
+# Skal Mailman filtrere indhold i e-mail sendt til listen som angivet
+# nedenfor?
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 filter_content = 0
 
-# 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.
+# Brug denne instilling til at fjerne vedhæftelser der passer til MIME
+# typer. Hver linie skal her indeholde navnet på en MIME type/subtype,
+# f.eks. image/gif. Såfremt du ønsker at fjerne alle vedhæftelser som
+# har en given hoved MIME type, kan du lade være at angive subtype,
+# f.eks. image.
 # 
-# Blank lines are ignored.
+# Blanke linier medtages ikke.
 # 
-# See also <a href="?VARHELP=contentfilter/pass_mime_types"
-# >pass_mime_types for a content type whitelist.
+# Se også gyldige MIME typer for whitelist af MIME typer.
 filter_mime_types = ''
 
-# 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.
+# Brug denne indstilling for at definere hvilke MIME typer der skal være
+# tilladt. Krav og format for filtrering er identisk med MIME filtre.
 # 
-# 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.
+# Bem&aelig;rk: hvis du lægger noget ind her, men ikke angiver
+# multipart, vil al e-mail med vedhæftelser ikke blive medtaget.
 pass_mime_types = """multipart/mixed
 multipart/alternative
 text/plain"""
 
-# Should Mailman convert text/html parts to plain text?  This conversion
-# happens after MIME attachments have been stripped.
+# Skal Mailman konvertere text/html dele til ren tekst? Denne
+# konvertering vil finde sted efter at MIME filteret har fjernet de
+# ønskede dele.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 convert_html_to_plaintext = 1
 
-# One of these actions is take 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.
+# Her bestemmer du hvad der skal ske når en meddelelse filtreres fra af
+# et filter, altså såfremt vedhæftelsen filtreres fra MIME filteret,
+# eller ent vedhæftelse ikke har en af de gyldige MIME typer, eller
+# meddelelsen ender op med at være tom efter filtrering.
+# 
+# Bemærk at det du vælger her ikke vil ske såfremt en meddelelse stadig
+# indeholder noget efter filtrering. Så vil meddelelsen altid sendes
+# videre til listen.
+# 
+# Når meddelelsen afvises, skrives Message-ID'en til den afviste
+# meddelelse til loggen. Når meddelelsen sendes retur eller videresendes
+# til listens ejer, vil en begrundelse altid blive inkluderet i
+# returmail der sendes til afsenderen. Når meddelelserne skal bevares,
+# gemmes de i en specielt køkatalog på disk sådan at
+# serveradministratoren kan se (og måske gøre noget med) meddelelsen,
+# men ellers fjernet. Dette sidste valg er kun tilgængeligt såfremt
+# serveradministratoren har tilladt det.
 #
-# legal values are:
-#    0 = "Discard"
-#    1 = "Reject"
-#    2 = "Forward to List Owner"
-#    3 = "Preserve"
+# gyldige værdier:
+#    0 = "Kassere"
+#    1 = "Afvis"
+#    2 = "Videresend til Listens Ejer"
+#    3 = "Tag hånd om"
 filter_action = 0
 
 ## Topics options
 #
-# 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.
+# Emneord for listen
+
+# Emnefilteret kategoriserer hver e-mail som kommer til listen, efter
+# regexp-uttrykkene du skriver nedenfor. Hvis feltene Subject: eller
+# Keywords: i mailhovedet i en mail passer imod disse udtryk, blir den
+# placeret under dette emne. Hvert medlem af listen kan vælge kun at
+# modtage mail der passer til de &oslash;nskede emner. e-mail som ikke
+# g&aring;r under noget emne, blir ikke leveret.
+# 
+# Bemerk: Dette fungerer kun i normal-modus, ikke i sammendrag-modus.
+# 
+# Indholdet i len kan ogs&aring; unders&oslash;ges for Subject: og
+# Keyword: felter, alt efter hvad indstillingen topics_bodylines_limit
+# er sat til.
 #
-# legal values are:
-#    0 = "Disabled"
-#    1 = "Enabled"
+# gyldige værdier:
+#    0 = "Ikke tilgængelig"
+#    1 = "Tilgængelig"
 topics_enabled = 0
 
-# 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.
-# 
+# Her opgiver du hvor mange linier af mailens indhold som emnefilteret
+# skal s&oslash;ge igennem. En s&oslash;gning stopper n&aring;r s&aring;
+# mange linier er gennoms&oslash;gt, eller n&aring;r det m&oslash;der en
+# linie som ikke ser ud som et meddelelsesfelt. Ved at sætte denne til
+# null (0), vil ingen linier i indholdet blive unders&oslash;gt (dvs.
+# kun Keywords: og Subject: i meddelelseshovedet unders&oslash;ges). Ved
+# at sætte denne værdi til et negativt tal, vil alle linier blive
+# unders&oslash;gt frem til den f&oslash;rste linie som ikke ser ut som
+# et mailhoved-felt.
 topics_bodylines_limit = 5
 
-# 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.
+# Hvert emneord er faktisk et regexp-udtryk, der sammenlignes imod dele
+# af mailen, nemlig feltene Keywords: og Subject: i meldingshodet.
+# Bem&aelig;rk at de f&oslash;ste linier i mailens indhold ogs&aring;
+# kan best&aring; af s&aring;danne "felter", og kan dermed ogs&aring;
+# bli unders&oslash;gt.
 topics = []
 
diff --git a/mailman/info.members b/mailman/info.members
deleted file mode 100644
index e69de29..0000000
--- a/mailman/info.members
+++ /dev/null
diff --git a/mailman/info.py b/mailman/info.py
deleted file mode 100644
index c11f4b3..0000000
--- a/mailman/info.py
+++ /dev/null
@@ -1,1236 +0,0 @@
-## "info" mailing list configuration settings -*- python -*-
-## captured on Wed Mar 16 02:41:01 2005
-
-## General options
-#
-# 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 = 'Info'
-
-# 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@olinesgaard.dk']
-
-# 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 = []
-
-# 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 om Olines Gaard'
-
-# 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 = """Email-liste om Olines Gaard.
-
-Hver email kan fylde max. 40 KiB, og ikke-tekst filtreres fra.
-
-Alle kan sende til listen, og alle kan tilmelde sig til 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.
-subject_prefix = '[Info] '
-
-# Hide the sender of a message, replacing it with the list address
-# (Removes From, Sender and Reply-To fields)
-#
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
-anonymous_list = False
-
-# 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.
-#
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
-first_strip_reply_to = False
-
-# 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.org/essays/reply-to-useful.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
-
-# 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.org/essays/reply-to-useful.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 = ''
-
-# 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.
-#
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
-umbrella_list = False
-
-# 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'
-
-# 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.
-#
-# 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 = """Dette er en email-liste om Olines Gaard.
-
-Hver email kan fylde max. 40 KiB, og ikke-tekst filtreres fra.
-
-Alle kan sende til listen, og alle kan tilmelde sig til at modtage.
-
-Der er offentlig adgang til email-arkiv."""
-
-# 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.
-#
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
-send_welcome_msg = True
-
-# Text sent to people leaving the list.  If empty, no special text will
-# be added to the unsubscribe message.
-goodbye_msg = ''
-
-# Send goodbye message to members when they are unsubscribed?
-#
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
-send_goodbye_msg = True
-
-# 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.
-#
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
-admin_immed_notify = True
-
-# Should administrator get notices of subscribes and unsubscribes?
-#
-# 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.
-#
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
-respond_to_post_requests = 1
-
-# 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.
-#
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
-emergency = 0
-
-# 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
-
-# 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.
-#
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
-administrivia = True
-
-# Maximum length in kilobytes (KB) of a message body.  Use 0 for no
-# limit.
-max_message_size = 40
-
-# 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 = 'olinesgaard.dk'
-
-# 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
-
-# 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
-
-## Language options
-#
-# 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 = 'da'
-
-# These are all the natural languages supported by this list. Note that
-# the default language must be included.
-available_languages = ['en', 'da']
-
-# 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
-#
-# Policies concerning immediately delivered list traffic.
-
-# Can subscribers choose to receive mail immediately, rather than in
-# batched digests?
-#
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
-nondigestable = True
-
-# Text prepended to the top of every immediately-delivery message.
-# Teksten kan inneholde formateringskoder som byttes ut med verdier fra
-# listens oppsett. 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
-# 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;.
-# 
-# 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.
-# 
-# description - En kort beskrivelse af listen.
-# 
-# info - Full beskrivelse af listen.
-# 
-# cgiext - Tillaeg som laegges til CGI scripts.
-# 
-# 
-msg_header = ''
-
-# Text appended to the bottom of every immediately-delivery message.
-# Teksten kan inneholde formateringskoder som byttes ut med verdier fra
-# listens oppsett. 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
-# 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;.
-# 
-# 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.
-# 
-# description - En kort beskrivelse af listen.
-# 
-# info - Full beskrivelse af listen.
-# 
-# cgiext - Tillaeg som laegges til CGI scripts.
-# 
-# 
-msg_footer = """_______________________________________________
-%(real_name)s mailing list
-%(real_name)s@%(host_name)s
-%(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s"""
-
-## Digest options
-#
-# Batched-delivery digest characteristics.
-
-# Can list members choose to receive list traffic bunched in digests?
-#
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
-digestable = True
-
-# Which delivery mode is the default for new users?
-#
-# legal values are:
-#    0 = "Regular"
-#    1 = "Digest"
-digest_is_default = False
-
-# When receiving digests, which format is default?
-#
-# legal values are:
-#    0 = "Plain"
-#    1 = "MIME"
-mime_is_default_digest = 1
-
-# How big in Kb should a digest be before it gets sent out?
-digest_size_threshhold = 30
-
-# Should a digest be dispatched daily when the size threshold isn't
-# reached?
-#
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
-digest_send_periodic = True
-
-# Text attached (as an initial message, before the table of contents) to
-# the top of digests. Teksten kan inneholde formateringskoder som byttes
-# ut med verdier fra listens oppsett. 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
-# 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;.
-# 
-# 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.
-# 
-# description - En kort beskrivelse af listen.
-# 
-# info - Full beskrivelse af listen.
-# 
-# cgiext - Tillaeg som laegges til CGI scripts.
-# 
-# 
-digest_header = ''
-
-# Text attached (as a final message) to the bottom of digests. Teksten
-# kan inneholde formateringskoder som byttes ut med verdier fra listens
-# oppsett. 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
-# 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;.
-# 
-# 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.
-# 
-# description - En kort beskrivelse af listen.
-# 
-# info - Full beskrivelse af listen.
-# 
-# cgiext - Tillaeg som laegges til CGI scripts.
-# 
-# 
-digest_footer = """_______________________________________________
-%(real_name)s mailing list
-%(real_name)s@%(host_name)s
-%(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s"""
-
-# When a new digest volume is started, the volume number is incremented
-# and the issue number is reset to 1.
-#
-# legal values are:
-#    0 = "Yearly"
-#    1 = "Monthly"
-#    2 = "Quarterly"
-#    3 = "Weekly"
-#    4 = "Daily"
-digest_volume_frequency = 1
-
-## Privacy options
-#
-# 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://olinegaard.dk/mailman/admin/info/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 = 1
-
-# 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
-
-# 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
-
-# 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 = []
-
-# When set, the list of subscribers is protected by member or admin
-# password authentication.
-#
-# legal values are:
-#    0 = "Anyone"
-#    1 = "List members"
-#    2 = "List admin only"
-private_roster = 1
-
-# 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
-#
-# 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.
-# 
-# Discard -- this simply discards the message, with no notice sent to
-# the post's author.
-# 
-#
-# legal values are:
-#    0 = "Hold"
-#    1 = "Reject"
-#    2 = "Discard"
-member_moderation_action = 0
-
-# 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 = ''
-
-# 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 = []
-
-# 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 = []
-
-# 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 = []
-
-# 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 = []
-
-# 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
-
-# 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
-
-## Privacy options
-#
-# This section allows you to configure various filters based on the
-# recipient of the message.
-
-# 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
-# 
-# 
-# The relaying address has the same name, or
-# 
-# The relaying address name is included on the options that specifies
-# acceptable aliases for the list.
-# 
-# 
-#
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
-require_explicit_destination = 1
-
-# 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 = ''
-
-# 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
-#
-# 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
-# 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.
-header_filter_rules = []
-
-# 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 example:to: .*@public.com  says to hold all postings with a To:
-# mail header containing '@public.com' anywhere among the addresses.
-# 
-# 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
-from: list@listme.com
-from: .*@uplinkpro.com"""
-
-## Bounce options
-#
-# 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
-
-# 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
-
-# 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
-
-# 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
-
-# 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
-
-# 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
-
-# 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.
-#
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
-bounce_notify_owner_on_disable = True
-
-# 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.
-#
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
-bounce_notify_owner_on_removal = True
-
-## Archive options
-#
-# List traffic archival policies.
-
-# Archive messages?
-#
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
-archive = True
-
-# Is archive file source for public or private archival?
-#
-# legal values are:
-#    0 = "public"
-#    1 = "private"
-archive_private = 0
-
-# How often should a new archive volume be started?
-#
-# legal values are:
-#    0 = "Yearly"
-#    1 = "Monthly"
-#    2 = "Quarterly"
-#    3 = "Weekly"
-#    4 = "Daily"
-archive_volume_frequency = 2
-
-## Gateway options
-#
-# Mail-to-News and News-to-Mail gateway services.
-
-# 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 = ''
-
-# The name of the Usenet group to gateway to and/or from.
-linked_newsgroup = ''
-
-# Should new posts to the mailing list be sent to the newsgroup?
-#
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
-gateway_to_news = 0
-
-# Should new posts to the newsgroup be sent to the mailing list?
-#
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
-gateway_to_mail = 0
-
-# 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 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.
-#
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
-news_prefix_subject_too = 1
-
-## Autoreply options
-#
-# Auto-responder characteristics.<p>
-# 
-# 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>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.
-
-# Should Mailman send an auto-response to mailing list posters?
-#
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
-autorespond_postings = 0
-
-# Auto-response text to send to mailing list posters.
-autoresponse_postings_text = ''
-
-# Should Mailman send an auto-response to emails sent to the -owner
-# address?
-#
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
-autorespond_admin = 0
-
-# Auto-response text to send to -owner emails.
-autoresponse_admin_text = ''
-
-# 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.
-#
-# legal values are:
-#    0 = "No"
-#    1 = "Yes, w/discard"
-#    2 = "Yes, w/forward"
-autorespond_requests = 0
-
-# Auto-response text to send to -request emails.
-autoresponse_request_text = ''
-
-# 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
-#
-# 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.  Then, each
-# <tt>multipart/alternative</tt> section will be replaced by just the
-# first alternative that is non-empty after filtering.
-# 
-# <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 = 1
-
-# 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.
-# 
-# Blank lines are ignored.
-# 
-# See also <a href="?VARHELP=contentfilter/pass_mime_types"
-# >pass_mime_types for a content type whitelist.
-filter_mime_types = 'image'
-
-# 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.
-# 
-# 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"""
-
-# 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
-
-# One of these actions is take 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 = 1
-
-## Topics options
-#
-# 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.
-#
-# legal values are:
-#    0 = "Disabled"
-#    1 = "Enabled"
-topics_enabled = 0
-
-# 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
-
-# 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 839b49e..1f86f9b 100644
--- a/mailman/mailman.py
+++ b/mailman/mailman.py
@@ -1,362 +1,386 @@
-## "mailman" mailing list configuration settings -*- python -*-
-## captured on Wed Mar 16 02:41:03 2005
+## Indstillinger for maillisten "mailman"  -*- python -*-
+## Dato: Thu May  5 09:52:40 2005
 
 ## General options
 #
-# 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 :-)
+# Grundlæggende egenskaber for listen, blant andet en beskrivelse af
+# listen, og hvordan den opf&oslash;rer sig.
+
+# Her kan du f.eks. stave navnet med stort forbogstav, eller ændre visse
+# bogstaver til store sådan at navnet kan udtales p&aring; en rigtig
+# m&aring;de eller at forkortelser fremhæves. Bemærk at dette navn
+# bruges i e-maillistens adresse (f.eks. i bekræftigelser ved
+# tilmeldinger), s&aring; der 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 :-)
 real_name = 'Mailman'
 
-# 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.
+# Der er to roller forbundet med hver mailliste. Listeadministratorene
+# 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.
+# 
+# Listemoderatorene har begrænset adgang; de kan ikke ændre
+# indstillinger for e-maillisten, men de kan tage sig af
+# foresp&oslash;rgsler i forbindlse med listen, f.eks. ans&oslash;gning
+# om medlemskab, eller godkende/afvise meddelelser der skal godkendes
+# for at kunne udsendes til listen. Listeadministratorene kan ogs&aring;
+# udf&oslash;re disse opgaver.
+# 
+# For at aktivere muligheden for at have listemoderatorer, og p&aring;
+# den m&aring;de opdele arbejdsopgaverne forbundet med listen, skal du
+# s&aelig;tte dit eget moderatorpassword, og angive din
+# e-mailadressen(e) til den/de som skal v&aelig;re listemoderator(er).
+# Bemærk at i tekstboksene nedenfor skal du skrive e-mailadressen(e) til
+# listeadministratoren(e).
 owner = ['postmaster@jones.dk']
 
-# 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.
+# Det er to ejerskab forbundet med hver mailliste. Listeadministratorene
+# er dem der har den endelige kontrol over alle indstillingerne for
+# e-mallisten. De kan &aelig;ndre alle indstillinger der er tilgengelige
+# via disse administrative websider.
+# 
+# Listemoderatorene har begr&aelig;nset adgang; de kan ikke &aelig;ndre
+# indstillinger for e-maillisten, men de kan tage sig af
+# foresp&oslash;rgsler ang&aring;ende listen, f.eks. ans&oslash;gning om
+# medlemskab, eller godkende/afvise meddelelser der skal godkendes for
+# at kunne udsendes p&aring; listen. Listeadministratorene kan selvsagt
+# ogs&aring; udf&oslash;re disse opgaver.
+# 
+# For at aktivere muligheten for at have listemoderatorer, og p&aring;
+# den m&aring;den opdele arbejdsopgaverne der er forbundet med listen,
+# skal du s&aelig;tte dit eget moderatorpassword, og indtaste din
+# e-mailadresse(r) til den/de der skal v&aelig;re listemoderator(er).
+# Bemærk at i tekstboksene nedenfor skal du skrive e-mailadressen(e) til
+# listemoderatoren(e).
 moderator = []
 
-# 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.
+# Denne beskrivelsen 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 gj&oslash;re det uklart
+# hvad meningen med maillisten er eller hvad den skal bruges til.
 description = ''
 
-# 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.
+# Teksten tolkes som html bortset fra linieskift, der vil blive
+# &aelig;ndret til html-tag'en '<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. Benytter du html-kode,
+# husk da at gennemse meget grundigt, for fejl (f.eks. manglende
+# slutt-tag's) kan f&oslash;re til at listens informationsside ikke vil
+# vises s&aring;dan som den skal.
 info = ''
 
-# 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 er sat ind foran emne-/tittelfeltet i e-mail der sendes
+# til listen, for at skille e-mailliste-meddelelser i e-mailboksen fra
+# dem der er medlem af listen. Denne tekst b&oslash;r holdes p&aring; et
+# absolut minimum, benytter du f.eks. listens navn og navnet er langt,
+# b&oslash;r du stave det endnu kortere her. Men den b&oslash;r fremover
+# v&aelig;re beskrivende for listen.
 subject_prefix = '[Mailman] '
 
-# Hide the sender of a message, replacing it with the list address
-# (Removes From, Sender and Reply-To fields)
+# Skjule afsenderen af meddelser, ved at erstatte den med e-maillistens
+# adresse (Dette medfører at alle From:, Sender, og Reply-To: felter
+# fjernes)
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 anonymous_list = 0
 
-# 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.
+# Skal eksisterende Reply-To: felt i meddelelseshovedet fjernes? Hvis ja
+# vil dette blive gjort uanset om Mailman tlføjer et Reply-To: felt
+# eller ikke.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 first_strip_reply_to = 0
 
-# 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.org/essays/reply-to-useful.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.
+# Denne indstillling fort&aelig;ller hvad Mailman skal gj&oslash;re med
+# Reply-To: feltet i meddelelseshovedet 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;dan 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 diskusion omkring
+# emnet. Se Reply-To Munging Considered Useful for modsatte meninger.
+# 
+# Nogle maillister har begr&aelig;nset adgang, med en egen parallell
+# liste beregnet til diskutioner. Eksempler p&aring; dette er 'patches'
+# eller 'checkin' lister, som system for revisionskontrol sender
+# &aelig;ndringer i programmet til, men diskusioner omkring udvikling af
+# programmet sendes til udviklerenes 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 diskusionsliste.
 #
-# legal values are:
-#    0 = "Poster"
-#    1 = "This list"
-#    2 = "Explicit address"
+# gyldige værdier:
+#    0 = "Afsender"
+#    1 = "mail listens adresse"
+#    2 = "Egendefineret adresse"
 reply_goes_to_list = 0
 
-# 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.org/essays/reply-to-useful.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.
+# 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 modifikasion af Reply-To:
+# adressen g&oslash;r det vanskeligere at sende svar kun til afsender.
+# Se 'Reply-To' Munging Considered Harmful for en diskusion omkring
+# temaet. Se Reply-To Munging Considered Useful for modsatte meninger.
+# 
+# Nogen maillister har begr&aelig;nset adgang, med en egen parallell
+# liste beregnet for diskusioner. Eksempler p&aring; dette er 'patches'
+# eller 'checkin' lister, som system for revisionskontrol sender
+# &aelig;ndringer til i programmet, men diskusioner rundt udvikling af
+# programmet sendes til udviklerenes egen mailliste. For at
+# st&oslash;tte s&aring;danne maillister, definer Reply-To: adressen
+# her, og vælg Egendefineret adresse i indstillingen reply_goes_to_list.
+# 
+# Bem&aelig;rk at hvis den oprindelige meddelse indeholder et Reply-To:
+# felt, vil det ikke &aelig;ndres.
 reply_to_address = ''
 
-# 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.
+# S&aelig;t denne til 'ja' hvis listen skal bruges som en "paraply" for
+# flere andre lister. N&aring;r denne er sat, vil bekr&aelig;ftigelser
+# og meddelelser med password blive sendt til en egen adresse som
+# beregnes ud fra e-mailadressen som er tilmeldt listen - v&aelig;rdien
+# af indstillingen "umbrella_member_suffix" bruges til dette. Denne
+# v&aelig;rdi tilf&oslash;jes til medlemmets kontonavn (det som
+# st&aring;r f&oslash;r @-tegnet).
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 umbrella_list = 0
 
-# 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".
+# N&aring;r "umbrella_list" indikerer at denne liste har andre
+# maillister som medlemmer, er det som regel &oslash;nskelig at
+# administrative meddelelser som f.eks. bekr&aelig;ftigelser og password
+# reminders ikke sendes til selve listen som er medlem, men til
+# administratoren for listen. Hvis dette er tilf&aelig;ldet, bruges
+# v&aelig;rdien af denne indstilling til at bestemme adressen sådan at
+# 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".
 umbrella_member_suffix = '-owner'
 
-# 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.
+# S&aelig;tt denne til hvis du vil have at password reminder skal sendes
+# til medlemmene en gang hver m&aring;ned. Husk at medlemmene kan
+# ogs&aring; selv frav&aelig;lge dette.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 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.
+# Tekst du skriver her vil blive tilf&oslash;jet &oslash;verst i
+# velkomsthilsenen der sendes til nye medlemmer. Velkomshilsenen
+# indeholder allerede viktige adresser og URLer knyttet til maillisten,
+# s&aring; sådan information er det ikke n&oslash;dvendig at inkludere
+# her. Her kan du indl&oslash;gge f.eks. oplysning om etikette eller
+# regler for brug af listen, o.l.
+# 
+# Bem&oslash;rk: Liniene i denne tekst vil brydes efter f&oslash;lgende
+# regler:
 # 
-# 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.
+# Hvert afsnit udfyldes s&aringdan at ingen linie er lenger en 70 tegn.
+# Enhver linie der begynder med blanke tegn udfyldes ikke. Blanke linier
+# adskiller afsnitt.
 # 
 welcome_msg = ''
 
-# 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.
+# S&aelig;t kun denne til 'Nej' hvis du skal il&aelig;gge nye medlemmer
+# manuelt, og ikke vil have de skal f&aring; dette 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.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 send_welcome_msg = 1
 
-# Text sent to people leaving the list.  If empty, no special text will
-# be added to the unsubscribe message.
+# Tekst der sendes til medlemmer der framelder sig fra listen. Hvis
+# denne er tom, l&aelig;gges det ikke noget tekst til frameldelsen.
 goodbye_msg = ''
 
-# Send goodbye message to members when they are unsubscribed?
+# Sende afskedshilsen til medlemmer n&aring;r de frameldes?
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 send_goodbye_msg = 1
 
-# 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.
+# Der udsendes en reminder til listemoderatoren(e) (og
+# listeadministratoren(e)) dagligt om foresp&oslash;rsler der af en
+# eller anden grund venter p&aring; behandling. V&aelig;lger du "Ja",
+# vil listeadminstratoren ogs&aring; motdtage en meddelelse s&aring;
+# snart en foresp&oslash;rsel kommer ind.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 admin_immed_notify = 1
 
-# Should administrator get notices of subscribes and unsubscribes?
+# Skal listeadministratoren(e) ogs&aring; modtage meddelelse om nye
+# medlemmer der tilmelder sig og gamle medlemmer som framelder sig?
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 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.
+# Besked om at en meddelelse skal godkendes sendes ud til afsenderen
+# s&aring;fremt meddelelsen stoppes pga. noget andet end listemoderation
+# eller spam filtre. S&aelig;ttes denne indstilling til 'Nej', vil
+# afsender overhovedet ikke modtage denne besked.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 respond_to_post_requests = 1
 
-# 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.
+# Når dette valg er aktiveret, vil alt e-mail til listen blive moderert.
+# 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-moderasjon" kan da hjælpe dig at fjerne usaglige meddelelser
+# til listen, og på den måden dysse en ophedet diskusion ned.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 emergency = 0
 
-# When a new member is subscribed to this list, their initial set of
-# options is taken from the this variable's setting.
+# Når et nyt medlem tilmeldes listen, blir medlemmets indstillinger
+# taget herfra.
 new_member_options = 256
 
-# 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.
+# Filter for administrative meddelelser vil unders&oslash;ge om
+# meddelelsen egentligt er ment som en administrativ foresp&oslash;rgsel
+# (f.eks. tilmelding, framelding, o.l.), og is&aring;fald sende
+# meddelelsen til administratoren i stedet.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 administrivia = 1
 
-# Maximum length in kilobytes (KB) of a message body.  Use 0 for no
-# limit.
+# Maximum st&oslash;rrelse i kilobytes (KB) for indholdet i e-mail der
+# sendes til listen. Brug verdien '0' for ikke at have en
+# begr&aelig;nsning.
 max_message_size = 40
 
-# 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.
+# "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; denne maskinen. Denne
+# indstillingen kan v&aelig;re nyttig hvis maskinen har flere navne.
 host_name = 'jones.dk'
 
-# 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).
+# I RFC 2369 defineres en r&aelig;kke List-* felter i
+# meddelelseshovedet, der normalt tilf&oslash;jes hver meddelelse der
+# sendes ud via listen. Disse felter kan hj&aelig;lpe de brugere af
+# listen der benytter et e-mailprogram som f&oslash;lger denne standard.
+# Disse felter b&oslash;r derfor altid v&aelig;re med.
+# 
+# Ikke alle e-mailprogrammer f&oslash;lger denne standard. Er det mange
+# af medlemmene p&aring; listen der benytter s&aring;danne
+# e-mailprogrammer, der ikke kan h&aring;ndtere disse felter i
+# meddelelseshovedet, kan det v&aelig;re du vil v&aelig;lge at udelade
+# dem. Men du b&oslash;r f&oslash;rst fors&oslash;ge at l&aelig;re og
+# forklare medlemmene 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 disse felter, men dette anbefales ikke (denne
+# muligheten kan faktisk ogs&aring; blive fjernet i senere versioner).
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 include_rfc2369_headers = 1
 
-# 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.)
+# List-Post: feltet er et af felterne anbefalet i RFC 2369. Visse
+# e-maillister (som f.eks. kun bruges til offentligørelser), er det kun
+# visse personer der har lov til at sende til; de som er medlem af
+# listen har generelt ikke lov til at sende til listen. For disse
+# lister, er List-Post: feltet forvirrende. I visse tilf&aelig;lde kan
+# det være forvirrende at s&aelig;tte denne indstilling til Nej,
+# s&aring; feltet ikke tilføjes. (Dette påvirker ikke andre List-*:
+# felter.)
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 include_list_post_header = 1
 
 ## Language options
 #
-# 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.
+# Underst&oslash;ttelse for flere sprog. (Internationalisering)
+
+# Dette er standardsproget som benyttes for denne mailliste. Hvis mer
+# 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.
 preferred_language = 'en'
 
-# These are all the natural languages supported by this list. Note that
-# the default language must be included.
+# Her er alle spr&aring;gene denne listen har underst&oslash;ttelse for.
+# Bem&aelig;rk at standardsproget skal v&aelig;re med.
 available_languages = ['en', 'da']
 
-# 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.
+# Hvis standardsproget for din mailliste benytter et andet tegns&aelig;t
+# end ASCII og tittel prefixet for listen indeholder tegn som ikke
+# findes i ASCII-tegns&aelig;ttet, vil prefixet alltid blive kodet i
+# henhold til den relevante standard. Hvis tittel prefixet kun
+# indeholder ASCII tegn, kan det imidlertid ske at du ønsker at sætte
+# dette valg til Aldrig for at undgå koding. Dette kan gøre titlen lidt
+# mere læselig for brugere med e-mailprogrammer der ikke takler andre
+# tegnsæt end ASCII på en rigtig måde.
+# 
+# Bemærk imidlertid at hvis din mailliste modtager både kodede og
+# ukodede tittel felt, kan det være bedst at vælge Efter behov. Med
+# denne indstilling vil Mailman ikke kode ASCII prefixer hvis resten af
+# tittelfeltet kun indeholder ASCII tegn, men vil kode prefixet hvis det
+# indeholder tegn som ikke er ASCII tegn. På denne måde undgås en [...]
+# i standarderne, som forårsager at visse e-mailprogrammer vil vise
+# ekstra eller manglende mellemrum imellom tittel prefixet og det
+# oprindelige tittelfelt.
 #
-# legal values are:
-#    0 = "Never"
-#    1 = "Always"
-#    2 = "As needed"
+# gyldige værdier:
+#    0 = "Aldrig"
+#    1 = "Altid"
+#    2 = "Efter behov"
 encode_ascii_prefixes = 0
 
 ## Nondigest options
 #
-# Policies concerning immediately delivered list traffic.
+# Regler for levering i normal-modus.
 
-# Can subscribers choose to receive mail immediately, rather than in
-# batched digests?
+# Kan medlemmer vælge normal-modus?
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 nondigestable = 1
 
-# 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:
+# 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:
 # 
 # 
 # real_name - The "pretty" name of the list; usually the list name with
@@ -381,9 +405,10 @@ nondigestable = 1
 # 
 msg_header = ''
 
-# 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:
+# Tekst som tilf&aelig;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:
 # 
 # 
 # real_name - The "pretty" name of the list; usually the list name with
@@ -413,42 +438,44 @@ msg_footer = """_______________________________________________
 
 ## Digest options
 #
-# Batched-delivery digest characteristics.
+# Opsætning af sammendrag-modus.
 
-# Can list members choose to receive list traffic bunched in digests?
+# Kan medlemmer af listen vælge at f&aring; tilsendt sammendrag i stedet
+# for?
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 digestable = 1
 
-# Which delivery mode is the default for new users?
+# Hvilken modus er standard for nye brugere?
 #
-# legal values are:
-#    0 = "Regular"
-#    1 = "Digest"
+# gyldige værdier:
+#    0 = "Normal"
+#    1 = "Sammendrag"
 digest_is_default = 0
 
-# When receiving digests, which format is default?
+# Hvilket format skal benyttes som standard for samle-email?
 #
-# legal values are:
-#    0 = "Plain"
+# gyldige værdier:
+#    0 = "Ren tekst"
 #    1 = "MIME"
 mime_is_default_digest = 0
 
-# How big in Kb should a digest be before it gets sent out?
+# Hvor stor (i Kb) m&aring; en samle-email h&oslash;jst v&aelig;re
+# f&oslash;r den udsendes?
 digest_size_threshhold = 30
 
-# Should a digest be dispatched daily when the size threshold isn't
-# reached?
+# Skal der sendes en samle-email dagligt, selv om st&oslash;rrelsen ikke
+# er opn&aring;et?
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 digest_send_periodic = 1
 
-# Text attached (as an initial message, before the table of contents) to
-# the top of digests. This text can include Python format strings which
+# Tekst som l&aelig;gges til &oslash;verst i samle-emailen, f&oslash;r
+# indholdsfortegnelsen.This text can include Python format strings which
 # are resolved against list attributes.  The list of substitutions
 # allowed are:
 # 
@@ -475,9 +502,10 @@ digest_send_periodic = 1
 # 
 digest_header = ''
 
-# 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:
+# Tekst der tilføjes nederst i hver samle-e-mail, som sidste
+# information.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
@@ -505,274 +533,277 @@ digest_footer = """_______________________________________________
 %(real_name)s@%(host_name)s
 %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s"""
 
-# When a new digest volume is started, the volume number is incremented
-# and the issue number is reset to 1.
+# N&aring;r et nyt volume startes, &oslash;ges volume nummeret, og
+# udgavenummeret s&aelig;ttes til 1.
 #
-# legal values are:
-#    0 = "Yearly"
-#    1 = "Monthly"
-#    2 = "Quarterly"
-#    3 = "Weekly"
-#    4 = "Daily"
+# gyldige værdier:
+#    0 = "&Aring;rlig"
+#    1 = "M&aring;nedlig"
+#    2 = "Kvartalsvis"
+#    3 = "Ugentlig"
+#    4 = "Daglig"
 digest_volume_frequency = 1
 
 ## Privacy options
 #
-# 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?
+# Her kan du bestemme hvad der kr&oslash;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&oslash;lder
+# arkivet og arkivering.
+
+# Vise denne mailliste n&aring;r nogn beder om at se en oversigt over
+# maillister p&aring; denne maskine?
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 advertised = 1
 
-# 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.
+# bek&aelig;ftigelse(*) - bekr&aelig;ftigelse af e-mail er
+# n&oslash;dvendig godkendelse - ans&oslash;gkning om medlemskabp skal
+# godkendes af listeadministrator (eller evt. listemoderator)
+# bekr&aelig;ftigelse+godkendelse - b&aring;de bekr&aelig;ftelse
+# p&aring; e-mail og godkendelse af listeadministrator (evt.
+# listemoderator) er nun&oslash;dvendig
+# 
+# (*) n&aring;r nogen vil tilmelde sig en liste, sender Mailman en
+# meddelelse med et uniktidentifikator som de skal opgive for at
+# bekr&oslash;fte tilmeldingen. P&aring; denne m&aring;den vil det da
+# ikke v&aelig;re muligt at tilmelde nogen til listen imod deres vilje.
 #
-# legal values are:
-#    1 = "Confirm"
-#    2 = "Require approval"
-#    3 = "Confirm and approve"
+# gyldige værdier:
+#    1 = "Bekr&aelig;ftigelse"
+#    2 = "Godkendelse"
+#    3 = "Bekr&aelig;ftigelse og godkendelse"
 subscribe_policy = 1
 
-# 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.
+# N&aring;r medlemmer &oslash;nsker at forlade en mailliste, sender de
+# en ans&oslash;gning om framelding, enten via web, eller via e-mail.
+# Normalt er det best at disse ans&oslash;gninger automatisk godkendes,
+# s&aring; meldemmer kan udmelde sig n&aring;r de &oslash;nsker det
+# (mange &oslash;nsker selv at kunne administrere en frameldelse. For
+# nogen f&aring; maillister kan det aligevel v&aelig;re aktuelt at have
+# kontrol over om medlemmer kan melde sig selv ud eller ikke. En liste
+# som alle ansatte i et firma M&Aring; v&aelig;re medlem af, er et
+# eksempel p&aring; en s&aring;dan liste.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 unsubscribe_policy = 0
 
-# 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.
+# Alle e-mailadresser som angives her vil blive udelukket fra listen, og
+# kan ikke tilmelde sig. Indtast e-mailadresser, en per linie, start
+# linien med tegnet ^ for at angive et regexp-udtryk der skal passe med
+# afsenderadressen.
 ban_list = []
 
-# When set, the list of subscribers is protected by member or admin
-# password authentication.
+# Hvis denne indstilling er sat til, vil listen over medlemmer af
+# e-maillisten blive beskyttet af medlemmenes eller adminstratorens
+# password.
 #
-# legal values are:
-#    0 = "Anyone"
-#    1 = "List members"
-#    2 = "List admin only"
+# gyldige værdier:
+#    0 = "Alle"
+#    1 = "Kun medlemmer af listen"
+#    2 = "Kun listeadministrator"
 private_roster = 1
 
-# 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.
+# V&aelig;lger du 'Ja' her, vil medlemmers e-mailadresse omskrives
+# n&aring;r de vises i en oversigt p&aring; websidene (b&aring;de som
+# tekst og i linker), s&aring; de ikke er nemme at tolke som
+# e-mailadresser. Meningen med dette er at undg&aring; at e-mailsniffere
+# der gennemg&aring;r websider for at finde e-mailadresser (og derefter
+# bruge dem til at udsende spam/junk mail) til ikke at opsamle
+# medlemmenes e-mailadresser.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 obscure_addresses = 1
 
 ## Privacy options
 #
-# 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.
+# N&aring;r en meddelelse sendes til maillisten, g&aring;r den igennem
+# en r&aelig;kke trin for at afg&oslash;re om moderatoren m&aring;
+# godkende meddelelsen eller ikke. Her finder du indstillinger for 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 de sendes til listen.
+# 
+# <p>e-mail som ikke er sendt af medlemmer af listen, kan automatisk bli
+# <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">sendt
+# retur</a>, eller <a
+# href="?VARHELP=privacy/sender/discard_these_nonmembers">afvist</a>,
+# enten individuelt eller som en gruppe. All e-mail fra ikke-medlemmer,
+# som ikke specifikt bliver godkent, sendes retur, eller afvist, 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 il&aelig;gger du en e-mailadresse per
+# linie. Du kan ogs&aring; il&aelig;gge  <a
+# href="http://www.python.org/doc/current/lib/module-re.html">Python
+# regexp-uttrykk</a>. Begynd is&aring;fald linien med tegnet ^ for at
+# markere at det er et s&aring;dan udtryk. N&aring;r du benytter
+# backslash, skriv da lige som i rene strings (Python raw strings)
+# (normalt kun &eacute;n backslash af gangen).
+# 
+# <p>Bem&aelig;rk: match p&aring; 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-mail fra medlemmet kan sendes direkte til e-maillisten, eller om de
+# f&oslash;rst skal godkendes af listemoderatoren. N&aring;r
+# moderationsflaget er sat til, skal e-mail fra medlemmet godkendes af
+# listemoderatoren f&oslash;r det udsendes til alle p&aring; listen. Som
+# listeadminsitrator kan du for hvert enkelt medlem bestemme om
+# medlemmets e-mail skal modereres eller ikke. N&aring;r et nyt medlem
+# tilmeldes til 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
+# Administrere medlemmer siden.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 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.
 # 
-# Discard -- this simply discards the message, with no notice sent to
-# the post's author.
+# Holde tilbage -- meldingen holdes tilbage for godkendelse af
+# listemoderatoren(e). Afslå -- meldingen sendes automatisk retur til
+# afsender. Begrundelsen der sendes kan du skrive selv Slette --
+# meddelelsen blir afvist uden at give besked om dette til afsender.
 # 
 #
-# legal values are:
-#    0 = "Hold"
-#    1 = "Reject"
-#    2 = "Discard"
+# gyldige værdier:
+#    0 = "Holde&nbsp;tilbage"
+#    1 = "Afvis"
+#    2 = "Kassere"
 member_moderation_action = 0
 
-# 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.
+# Tekst som skal sendes med meldingen om retur som sendes til modereede
+# medlemmer af listen.
 member_moderation_notice = ''
 
-# 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.
+# e-mail fra disse ikke-medlemmer vil automatisk blive godkendt.
+# Il&aelig;g e-mailadresser, en per linie, start linien med tegnet ^ for
+# at angive et regexp-uttryk som skal passe med afsenderadressen.
 accept_these_nonmembers = []
 
-# 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.
+# e-mail fra disse ikke-medlemmer vil automatisk blive holdt tilbage for
+# vurdering af listemoderatorene. Afsenderen vil modtage en meddelelse
+# om dette, med bl.a. instruktioner om hvordan han/hun kan
+# tilbagetr&aelig;kke sin e-mails. Indtast e-mailadresser, en per linie,
+# start linien med tegnet ^ for at angive et regexp-uttrykk som skal
+# passe med afsenderadressen.
 hold_these_nonmembers = []
 
-# 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.
+# 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 spam-afsendere,
+# de b&oslash;r automatisk afvises. Indtast e-mailadresser, en per
+# linie, start linien med tegnet ^ for &aring; angiv et regexp-uttrykk
+# som skal passe med afsenderadressen.
 reject_these_nonmembers = []
 
-# 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.
+# e-mail fra disse ikke-medlemmer vil automatisk blive afvist. Det vil
+# sige at meddelelsen afvises uden nogen form for tilbagemelding, men
+# listemoderatorene kan (om ønskeligt) modtage en kopi af den afviste
+# e-mail. Tilf&oslash;je e-mailadresser, en per linie, start linien med
+# tegnet ^ for at angive et regexp-uttryk der skal passe med
+# afsenderadressen.
 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']
 
-# 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.
+# N&aring;r en e-mail fra et ikke-medlem blir modtaget, sammenlignes
+# e-mailens afsender med listen over e-mailadresser der skal godkendes,
+# holdes tilbage, afvises (sendes i retur), og afvises. Hvis
+# afsenderadressen ikke passer med den der er opgivet i listene, blir
+# f&oslash;lgende afg&oslash;relse taget.
 #
-# legal values are:
-#    0 = "Accept"
-#    1 = "Hold"
-#    2 = "Reject"
-#    3 = "Discard"
+# gyldige værdier:
+#    0 = "Godkende"
+#    1 = "Holde&nbsp;tilbage"
+#    2 = "Afvis"
+#    3 = "Kassere"
 generic_nonmember_action = 1
 
-# Should messages from non-members, which are automatically discarded,
-# be forwarded to the list moderator?
+# Skal meddelelser fra ikke-medlemmer, som automatisk afvises, også
+# sendes til listemoderatoren?
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 forward_auto_discards = 1
 
 ## Privacy options
 #
-# This section allows you to configure various filters based on the
-# recipient of the message.
+# Her kan du ops&aelig;tte filtrering baseret på modtaeren af
+# meddelelsen.
 
-# 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.
+# Meget (faktisk det meste af) spam/junk mail har ikke de endelige
+# modtagere i modtagerfelterne. Faktisk s&aring; indeholder felterne To:
+# og/eller Cc: oftest en fuldst&aelig;ndig 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(e), men vil
+# aligevel blive fanget og blokkere det meste af spam/junk mail.
 # 
-# 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 ville 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
+# alias for listen.
 # 
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 require_explicit_destination = 1
 
-# 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.
+# Alternative e-mailadresser som godtages n&aring;r
+# 'require_explicit_destination' er sat til. Som v&aelig;rdi for denne
+# indstilling skal du opgive regexp-uttryk ("regular expressions"), et
+# udtryk per linie, der sammenlignes imod 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 imod den f&oslash;rste
+# del (det som st&aring;r f&oslash;r '@') af modtageradressen. Hvis
+# sammenligningen ikke lykkes, eller hvis udtrykket ikke indholder en
+# '@', sammenlignes udtrykket med hele modtageradressen.
+# 
+# Sammenligning kun imod den f&oslash;rste del af en modtageradresse
+# underst&oslash;ttes ikke i fr&aelig;mtidige udgaver af Mailman, vil
+# kun sammenligning imod hele modtageradresser blive
+# underst&oslash;ttet.
 acceptable_aliases = ''
 
-# If a posting has this number, or more, of recipients, it is held for
-# admin approval.  Use 0 for no ceiling.
+# Hvis en mail der er sendt til listen indeholder s&aring; mange
+# modtagere som, eller flere modtagere end, denne værdi, holdes malen
+# tilbage så listeadministratoren eventuelt kan godkende den. Brug
+# værdien 0 for ingen begrænsning.
 max_num_recipients = 10
 
 ## Privacy options
 #
-# 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.
-# 
+# Her kan du opsætte forskellige anti-spam filtre, som kan være til
+# hjælp for 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
@@ -785,16 +816,20 @@ max_num_recipients = 10
 # match.
 header_filter_rules = []
 
-# 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.
+# Brug denne indstilling til at fra-filtrere mail til listen, baseret
+# p&aring; indholdet af et eller flere felter i mailhovedet. Her skal du
+# skrive regexp-uttryk (regular expressions), et per linie, som
+# sammenlignes mod det aktuelle felt. Sammenligningen sk&aelig;lner ikke
+# imellem store og sm&aring; bogstaver. Linier der begynder med '#'
+# sammenlignes ikke.
 # 
-# For example:to: .*@public.com  says to hold all postings with a To:
-# mail header containing '@public.com' anywhere among the addresses.
+# For eksempel: udtrykket to: .*@public.com fort&aelig;ller at alt mail
+# som indeholder '@public.com' i To: feltet, skal holdes tilbage til
+# godkendelse.
 # 
-# 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.
+# Bem&aelig;rk: blanke tegn i starten af regexp-udtrykket fjernes. Dette
+# kan man undg&aring; p&aring; flere m&aring;ter, f.eks. ved at bruge
+# escape-tegn eller parenteser.
 bounce_matching_headers = """
 # Lines that *start* with a '#' are comments.
 to: friend@public.com
@@ -804,54 +839,56 @@ from: .*@uplinkpro.com"""
 
 ## Bounce options
 #
-# 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.
+# Disse regler bestemmer hvordan automatisk behandling af returmails
+# gj&oslash;res. Her er en oversigt over hvordan funktionen er.
+# 
+# <p>N&aring;r Mailman modtager en returmail, blir to ting
+# fors&oslash;kt tolket. Det ene er e-mailadressen til medlemmet som
+# egentlig skulle modtage e-mailen, og det andet er &aring;rsagen til
+# problemet. &Aring;rsagen tolkes til at v&aelig;re <em>alvorlig</em>
+# eller <em>lett</em> alt efter om &aring;rsagen er af kritisk eller af
+# mindre alvorlig art. Såfremt der er tvivl, tolkes &aring;rsaken som
+# alvorlig.
+# 
+# <p>Hvis ingen e-mailadresse kan hentes ud af meddelelsen, blir den
+# normalt afvist. Ellers, vil medlemmet som har e-mailadressen f&aring;
+# en <em>returtal</em>, og hver gang en returmeddelelse kommer vil
+# tallet &oslash;ges. Alvorlige &aring;rsaker f&oslash;rer til at tallet
+# &oslash;ges med 1, lette &aring;rsaker f&oslash;rer til at det
+# &oslash;kes med 0.5. Dette sker kun &eacute;n gang per dag, s&aring;
+# selv om det 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;ttest til igen.
+# Medlemmet vil med j&aelig;vne mellemrum modtage melding 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>Det er en vigtig indstilling til; efter en vis tid -- hvis ingen
+# returmeddelelser dukker op i l&oslash;bet af denne tid -- anses
+# returinformation som <a
+# href="?VARHELP=bounce/bounce_info_stale_after">udg&aring;et</a> og
+# afvises. Ved at justere denne værdi, og sætte en grænse for
+# returantallet, kan du bestemme hvor lang tid der skal gå f&oslash;r
+# levering til et medlem stoppes. Begge disse værdier skal du justere
+# alt efter hvor ofte og hvor meget e-mail der sendes til din liste.
+
+# Ved at sætte denne værdi til Nej, sætter du alt automatisk tolking af
+# returmeddelelser for denne liste fra. Bemærk at såfremt meddelelser
+# afvises vil listeadministratoren ikke blive forstyrret med dem.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 bounce_processing = 1
 
 # Each subscriber is assigned a bounce score, as a floating point
@@ -867,351 +904,345 @@ bounce_processing = 1
 # mailing list.
 bounce_score_threshold = 5.0
 
-# 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.
+# Antal dage f&oslash;r returinformation afvises såfremt der ikke dukker
+# flere returmails op. Dette tal skal v&aelig;re et heltal.
 bounce_info_stale_after = 7
 
-# 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.
+# Hvor mange Levering til dig er stoppet advarsler der skal sendes til
+# et medlem f&oslash;r medlemmet frameldes fra listen. S&aelig;t denne
+# værdi til 0 for at fjerne et medlem fra listen umiddelbart
+# s&aring;fremt der kommer returmails fra medlemmets e-mailadresse.
+# Dette tal skal være et heltal.
 bounce_you_are_disabled_warnings = 3
 
-# The number of days between sending the Your Membership Is Disabled
-# warnings.  This value must be an integer.
+# Antal dage imellem hver gang en Levering til dig er stoppet advarsel
+# skal sendes ud. Dette tal skal være et heltal.
 bounce_you_are_disabled_warnings_interval = 7
 
-# 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.
+# Mailmans automatiske returmailhåndtering er meget robust, men det er
+# aligevel umuligt at genkende alle typer returmails der kommer. Du bør
+# angive Ja her, af to grunde: 1) Hvis det virkelig er en permanent
+# returmail fra et medlem af listen, bør du antageligt manuelt udmelde
+# medlemmet fra listen, og 2) du vil måske sende meddelelse til
+# udviklerne af Mailman sådan at returmails automatisk genkendes af
+# Mailman i senere versioner. Hvis du ikke vil gøre nogen af delene, sæt
+# da denne indstilling til Nej. Så vil alle returmails afvises
+# automatisk uden videre behandling. Bem&aelig;rk: Denne indstilling vil
+# også indvirke på alt e-mail der sendes til listens -admin adresse. Den
+# adresse er gammel og udgået, men det kan være at nogen fortsat vil
+# sende e-mail til den. Hvis nogen gør det, og du har sat denne
+# indstilling til Nej, vil disse mails også blive afvist. Måske vil du
+# også opsætte et automatisk svar på e-mail sendt til -owner og -admin
+# adresserne.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 bounce_unrecognized_goes_to_list_owner = 1
 
-# 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.
+# Ved at sætte denne til Nej, fravælges beskeden der normalt sendes til
+# ejeren(e) af listen, når afsending 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.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 bounce_notify_owner_on_disable = 1
 
-# 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.
+# Ved at sætte denne til Nej, fravælges beskeden der normalt sendes til
+# ejeren(e) af listen, når et medlem frameldes fra listen på grund af
+# for mange returmails. Der vil til gengæld altid blive forsøgt afsendt
+# en e-mail med besked til medlemmet.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 bounce_notify_owner_on_removal = 1
 
 ## Archive options
 #
-# List traffic archival policies.
+# Regler for arkivering
 
-# Archive messages?
+# Arkivere e-mail i et arkiv?
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 archive = 1
 
-# Is archive file source for public or private archival?
+# Skal filen arkiveres i et privat eller i et offentlig arkiv?
 #
-# legal values are:
-#    0 = "public"
-#    1 = "private"
+# gyldige værdier:
+#    0 = "offentlig"
+#    1 = "privat"
 archive_private = 0
 
-# How often should a new archive volume be started?
+# Hvor ofte skal arkivet deles op?
 #
-# legal values are:
-#    0 = "Yearly"
-#    1 = "Monthly"
-#    2 = "Quarterly"
-#    3 = "Weekly"
-#    4 = "Daily"
+# gyldige værdier:
+#    0 = "&Aring;rlig"
+#    1 = "M&aring;nedlig"
+#    2 = "Kvartalsvis"
+#    3 = "Ugentlig"
+#    4 = "Daglig"
 archive_volume_frequency = 1
 
 ## Gateway options
 #
-# Mail-to-News and News-to-Mail gateway services.
+# e-mail-Til-Nyhedsgruppe og Nyhedsgruppe-Til-e-mail tjeneste.
 
-# 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.
+# 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.
 nntp_host = ''
 
-# The name of the Usenet group to gateway to and/or from.
+# Navn p&aring; nyhedsgruppe der skal sendes til og/eller fra.
 linked_newsgroup = ''
 
-# Should new posts to the mailing list be sent to the newsgroup?
+# Skal nye mail til denne liste sendes til nyhedsgruppen?
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 gateway_to_news = 0
 
-# Should new posts to the newsgroup be sent to the mailing list?
+# Skal nye meddelelser til nyhedsgruppen sendes til denne mailliste?
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 gateway_to_mail = 0
 
-# 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.
+# 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&aring;t da 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
+# Moderet, vil en ekstra meddelelse holdes tilbage i
+# godkendelsesprocessen. Alt mail sendt til maillisten skal godkendes
+# f&oslash;r de sendes til nyhedsgruppen, eller til medlemmene af
+# listen.
+# 
+# Vær opm&aelig;rksom p&aring; at hvis mailhovedet i mailen har et
+# Approved: felt med listens administrative password, 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 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 meddelelseshovedet.
 #
-# legal values are:
-#    0 = "None"
-#    1 = "Open list, moderated group"
-#    2 = "Moderated"
+# gyldige værdier:
+#    0 = "Ingen"
+#    1 = "Åben liste, modereret nyhedsgruppe"
+#    2 = "Modereret"
 news_moderation = 0
 
-# 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.
+# Mailman tilføjer normalt en tekst du selv 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 sette denne indstilling
+# til Nej hvis du ikke ønsker emne prefix tilføjet til mail som sendes
+# til Usenet. Sætter du emne prefix for listen til off, vil opsamlet
+# meddelelser heller ikke få præfix tilføjet.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 news_prefix_subject_too = 1
 
 ## Autoreply options
 #
-# Auto-responder characteristics.<p>
+# Indstillinger for automatiske svar.<p>
 # 
-# 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>
+# 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 epostadresse</em>
+# <li><b>owneremail</b> - <em>listens -owner epostadresse</em> </ul>
 # 
-# <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.
+# <p>Du kan enten skrive teksten direkte i tekstboksene, eller du kan
+# angive navnet p&aring; en fil som indeholder teksten. Denne file vil
+# s&aring; blive indl&aelig;st i tekstboksen, fra dit lokale filsystem.
 
-# Should Mailman send an auto-response to mailing list posters?
+# Skal Mailman sende et automatisk svar til dem der sender e-mail til
+# listen?
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 autorespond_postings = 0
 
-# Auto-response text to send to mailing list posters.
+# Automatisk svar der skal sendes.
 autoresponse_postings_text = ''
 
-# Should Mailman send an auto-response to emails sent to the -owner
-# address?
+# Skal Mailman sende et automatisk svar p&aring; e-mail der sendes til
+# -owner adressen?
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 autorespond_admin = 0
 
-# Auto-response text to send to -owner emails.
+# Automatisk svar p&aring; e-mail til -owner adressen.
 autoresponse_admin_text = ''
 
-# 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.
+# 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
+# ogs&aring; skal v&aelig;re med i det automatiske svar.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes, w/discard"
-#    2 = "Yes, w/forward"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja, men uden den originale e-mailn"
+#    2 = "Ja, og medtag den originale e-mail"
 autorespond_requests = 0
 
-# Auto-response text to send to -request emails.
+# Automatisk svar p&aring; e-mail til -request adressen.
 autoresponse_request_text = ''
 
-# 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).
+# Antal dage imellem automatisk svar p&aring; e-mail, fra samme
+# afsender, til listen eller til -request/-owner adressene. S&aelig;t
+# denne v&aelig;rdi til 0 (eller et negativt tal) for at sende
+# automatisk svar hver gang.
 autoresponse_graceperiod = 90
 
 ## Contentfilter options
 #
-# 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.  Then, each
-# <tt>multipart/alternative</tt> section will be replaced by just the
-# first alternative that is non-empty after filtering.
-# 
-# <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?
+# Regler for indhold i e-mail sendt til listen.
+# 
+# <p>Filtrering af indhold fungerer således: når listen modtger en
+# e-mail og du har beskyttelse med filtrering af indhold, sammenlignes
+# først eventuelle ved- hæftelser imod <a
+# href="?VARHELP=contentfilter/filter_mime_types">MIME filtre</a>. Hvis
+# en vedhæftelse passer med et af disse filtre, blir vedhæftelsen
+# fjernet.
+# 
+# <p>Derefter sammenlignes eventuelle vedhæftelser imod <a
+# href="?VARHELP=contentfilter/pass_mime_types">gyldige MIME typer</a>,
+# hvis nogen er defineret. Alle vedhæftelser som ikke passer med de
+# angivne MIME typene, blir fjernet.
+# 
+# <p>Efter disse filtre, vil alle tomme <tt>multipart</tt> vedhæftelser
+# blive fjernet. Hvis selve meddelelsen er helt tom efter denne
+# filtrering, vil meddelelsen bli afvist. Derefter vil hvert
+# <tt>multipart/alternative</tt> vedhæftelse blive erstattet af det
+# første alternative som ikke er tomt.
+# 
+# <p>Til slut vil alle <tt>text/html</tt> vedhæftelser som måtte være
+# tilbage i meddelelsen blive konverteret til <tt>text/plain</tt>
+# såfremt <a
+# href="?VARHELP=contentfilter/convert_html_to_plaintext">konvertere til
+# ren tekst</a> er sat til og serveren er konfigurert til at tillade
+# sådanne konverteringer.
+
+# Skal Mailman filtrere indhold i e-mail sendt til listen som angivet
+# nedenfor?
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 filter_content = 0
 
-# 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.
+# Brug denne instilling til at fjerne vedhæftelser der passer til MIME
+# typer. Hver linie skal her indeholde navnet på en MIME type/subtype,
+# f.eks. image/gif. Såfremt du ønsker at fjerne alle vedhæftelser som
+# har en given hoved MIME type, kan du lade være at angive subtype,
+# f.eks. image.
 # 
-# Blank lines are ignored.
+# Blanke linier medtages ikke.
 # 
-# See also <a href="?VARHELP=contentfilter/pass_mime_types"
-# >pass_mime_types for a content type whitelist.
+# Se også gyldige MIME typer for whitelist af MIME typer.
 filter_mime_types = ''
 
-# 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.
+# Brug denne indstilling for at definere hvilke MIME typer der skal være
+# tilladt. Krav og format for filtrering er identisk med MIME filtre.
 # 
-# 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.
+# Bem&aelig;rk: hvis du lægger noget ind her, men ikke angiver
+# multipart, vil al e-mail med vedhæftelser ikke blive medtaget.
 pass_mime_types = """multipart/mixed
 multipart/alternative
 text/plain"""
 
-# Should Mailman convert text/html parts to plain text?  This conversion
-# happens after MIME attachments have been stripped.
+# Skal Mailman konvertere text/html dele til ren tekst? Denne
+# konvertering vil finde sted efter at MIME filteret har fjernet de
+# ønskede dele.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 convert_html_to_plaintext = 1
 
-# One of these actions is take 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.
+# Her bestemmer du hvad der skal ske når en meddelelse filtreres fra af
+# et filter, altså såfremt vedhæftelsen filtreres fra MIME filteret,
+# eller ent vedhæftelse ikke har en af de gyldige MIME typer, eller
+# meddelelsen ender op med at være tom efter filtrering.
+# 
+# Bemærk at det du vælger her ikke vil ske såfremt en meddelelse stadig
+# indeholder noget efter filtrering. Så vil meddelelsen altid sendes
+# videre til listen.
+# 
+# Når meddelelsen afvises, skrives Message-ID'en til den afviste
+# meddelelse til loggen. Når meddelelsen sendes retur eller videresendes
+# til listens ejer, vil en begrundelse altid blive inkluderet i
+# returmail der sendes til afsenderen. Når meddelelserne skal bevares,
+# gemmes de i en specielt køkatalog på disk sådan at
+# serveradministratoren kan se (og måske gøre noget med) meddelelsen,
+# men ellers fjernet. Dette sidste valg er kun tilgængeligt såfremt
+# serveradministratoren har tilladt det.
 #
-# legal values are:
-#    0 = "Discard"
-#    1 = "Reject"
-#    2 = "Forward to List Owner"
-#    3 = "Preserve"
+# gyldige værdier:
+#    0 = "Kassere"
+#    1 = "Afvis"
+#    2 = "Videresend til Listens Ejer"
+#    3 = "Tag hånd om"
 filter_action = 0
 
 ## Topics options
 #
-# 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.
+# Emneord for listen
+
+# Emnefilteret kategoriserer hver e-mail som kommer til listen, efter
+# regexp-uttrykkene du skriver nedenfor. Hvis feltene Subject: eller
+# Keywords: i mailhovedet i en mail passer imod disse udtryk, blir den
+# placeret under dette emne. Hvert medlem af listen kan vælge kun at
+# modtage mail der passer til de &oslash;nskede emner. e-mail som ikke
+# g&aring;r under noget emne, blir ikke leveret.
+# 
+# Bemerk: Dette fungerer kun i normal-modus, ikke i sammendrag-modus.
+# 
+# Indholdet i len kan ogs&aring; unders&oslash;ges for Subject: og
+# Keyword: felter, alt efter hvad indstillingen topics_bodylines_limit
+# er sat til.
 #
-# legal values are:
-#    0 = "Disabled"
-#    1 = "Enabled"
+# gyldige værdier:
+#    0 = "Ikke tilgængelig"
+#    1 = "Tilgængelig"
 topics_enabled = 0
 
-# 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.
-# 
+# Her opgiver du hvor mange linier af mailens indhold som emnefilteret
+# skal s&oslash;ge igennem. En s&oslash;gning stopper n&aring;r s&aring;
+# mange linier er gennoms&oslash;gt, eller n&aring;r det m&oslash;der en
+# linie som ikke ser ud som et meddelelsesfelt. Ved at sætte denne til
+# null (0), vil ingen linier i indholdet blive unders&oslash;gt (dvs.
+# kun Keywords: og Subject: i meddelelseshovedet unders&oslash;ges). Ved
+# at sætte denne værdi til et negativt tal, vil alle linier blive
+# unders&oslash;gt frem til den f&oslash;rste linie som ikke ser ut som
+# et mailhoved-felt.
 topics_bodylines_limit = 5
 
-# 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.
+# Hvert emneord er faktisk et regexp-udtryk, der sammenlignes imod dele
+# af mailen, nemlig feltene Keywords: og Subject: i meldingshodet.
+# Bem&aelig;rk at de f&oslash;ste linier i mailens indhold ogs&aring;
+# kan best&aring; af s&aring;danne "felter", og kan dermed ogs&aring;
+# bli unders&oslash;gt.
 topics = []
 
diff --git a/mailman/nilsstaerk.members b/mailman/nilsstaerk.members
index 3f97417..335eeb6 100644
--- a/mailman/nilsstaerk.members
+++ b/mailman/nilsstaerk.members
@@ -121,6 +121,8 @@ b2dk@yahoo.fr
 bartschi@worldcom.ch
 batkin@bard.edu
 baungaard@mail.dk
+bcn2022@hotmail.com
+bcr2022@hotmail.com
 bellet@lemonde.fr
 benmonga@yahoo.fr
 benteelisabeth@private.dk
@@ -134,6 +136,7 @@ bob@bobvanorsouw.ch
 bobokrabbe@hotmail.com
 bodild@dragoer.dk
 bogh@hum.ku.dk
+brad@bmossman.com
 brammer@os.dk
 bryggebladet@mail.dk
 bt@danx.dk
@@ -164,6 +167,7 @@ cecid@bway.net
 cecilia.pereira.marimon@xunta.es
 ceinstein@daileyads.com
 cemetiah@indosat.net.id
+cffm@novonordisk.com
 cgarrido.fundacio@lacaixa.es
 charlotte.o@wanadoo.dk
 charlotte.s@smk.dk
@@ -189,10 +193,12 @@ cjennow@hotmail.com
 clairecanning@tankmagazine.com
 clau0111@hotmail.com
 claus.carstensen@pc.dk
+clausanton@berdal.dk
 clausen@kunst.dk
 cleocaf@yahoo.com
 cmedin@yahoo.com
 columnadearena@hotmail.com
+comp@dr.dk
 contact@meyerkainer.at
 contact@paulknight.com.au
 contact@photography-now.com
@@ -208,6 +214,7 @@ d.dekerckhove@utoronto.ca
 d.elliott@mori.art.museum
 dack9245@aol.com
 dalgaspanda@yahoo.com
+dan@bro.dk
 dangermouse1@earthlink.net
 danpty@fastwebnet.it
 daross222@earthlink.net
@@ -276,6 +283,7 @@ email@stereobar.dk
 emif@micronet.it
 emma.lequeux@free.fr
 enarmstrong@cox.net
+eneboer@paradis.dk
 enrique.juncosa@modernart.ie
 eriksenpeter@mail.dk
 eriksteffensen@mail.dk
@@ -358,6 +366,7 @@ habres@nacpool.at
 halbergemilie@hotmail.com
 halldor@netcom.ca
 hanaltc@hotmail.com
+hanschr@privat.dk
 hanuta77@hotmail.com
 hb@emerge.dk
 heide.kramer@basis-wien.at
@@ -432,6 +441,7 @@ jacobrantzau@hotmail.com
 jacobweinberger@adr.dk
 jade@dr.dk
 jahn@wkv-stuttgart.de
+jakob@hunosoe.dk
 jakob_witt@hotmail.com
 jakobjakobsen@adr.dk
 jakobjensen@gmx.net
@@ -483,6 +493,7 @@ jucarpa@inwind.it
 judelson@i-20.com
 judith.quentel@fracdespaysdelaloie.com
 julie.damgaard@tdcadsl.dk
+julielb@mac.com
 julieta68@bellsouth.net
 julieta68@yahoo.com
 jvaliaga@hotmail.com
@@ -519,6 +530,7 @@ kjelman@online.no
 kkanatani@guggenheim.org
 kkern@worldonline.dk
 kkr@codan.dk
+kkuramitsu@nortonfamilyoffice.com
 koenig@museum-ludwig.de
 kolovskaya@proarte.ru
 konjitseyoum@hotmail.com
@@ -577,6 +589,7 @@ llagnado@nw.com.br
 lmiller@fluentcollab.org
 lone@jones.dk
 lonedan@centrum.dk
+lorena110577@yahoo.es
 lose@postman.dk
 lotte.n@dgmedia.dk
 lottenburger@worldonline.dk
@@ -639,6 +652,7 @@ mathias_seeberg@hotmail.com
 mats.eriksson@brevet.nu
 matthew@frieze.com
 matti.bekkevold@pol.dk
+mc@madsclausen.com
 me@thorbjoernkoenig.com
 melissaneumann@verizon.net
 mepacheco@malba.org.ar
@@ -646,6 +660,7 @@ meraso@kultura.gipuzkoa.net
 mestrom@mindspring.com
 mette@aok.dk
 mette@skjoedt.com
+mfm@berlingske.dk
 mia@fryland.org
 michaelbach@wanadoo.es
 michaelrooks@earthlink.net
@@ -730,6 +745,7 @@ per@flydal.no
 perch@dadlnet.dk
 perezoramas@vzavenue.net
 pernille@thura.com
+pernillecoulthard@hotmail.com
 pernillegrane@aol.com
 peter.friis@mercuriurval.com
 peter.rohleder@lavandoo.com
@@ -789,6 +805,7 @@ reviews@frieze.com
 reyna@mail.utexas.edu
 rhill@guggenheim.org
 ricardo@amaste.com
+richard@paradox.no
 richarddorment@dial.pipex.com
 rikke@artlover.com
 rikke@kridt.biz
diff --git a/mailman/nilsstaerk.py b/mailman/nilsstaerk.py
index f427431..56583fe 100644
--- a/mailman/nilsstaerk.py
+++ b/mailman/nilsstaerk.py
@@ -1,362 +1,386 @@
-## "nilsstaerk" mailing list configuration settings -*- python -*-
-## captured on Wed Mar 16 02:41:04 2005
+## Indstillinger for maillisten "nilsstaerk"  -*- python -*-
+## Dato: Thu May  5 09:52:41 2005
 
 ## General options
 #
-# 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 :-)
+# Grundlæggende egenskaber for listen, blant andet en beskrivelse af
+# listen, og hvordan den opf&oslash;rer sig.
+
+# Her kan du f.eks. stave navnet med stort forbogstav, eller ændre visse
+# bogstaver til store sådan at navnet kan udtales p&aring; en rigtig
+# m&aring;de eller at forkortelser fremhæves. Bemærk at dette navn
+# bruges i e-maillistens adresse (f.eks. i bekræftigelser ved
+# tilmeldinger), s&aring; der 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 :-)
 real_name = 'NilsStaerk'
 
-# 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.
+# Der er to roller forbundet med hver mailliste. Listeadministratorene
+# 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.
+# 
+# Listemoderatorene har begrænset adgang; de kan ikke ændre
+# indstillinger for e-maillisten, men de kan tage sig af
+# foresp&oslash;rgsler i forbindlse med listen, f.eks. ans&oslash;gning
+# om medlemskab, eller godkende/afvise meddelelser der skal godkendes
+# for at kunne udsendes til listen. Listeadministratorene kan ogs&aring;
+# udf&oslash;re disse opgaver.
+# 
+# For at aktivere muligheden for at have listemoderatorer, og p&aring;
+# den m&aring;de opdele arbejdsopgaverne forbundet med listen, skal du
+# s&aelig;tte dit eget moderatorpassword, og angive din
+# e-mailadressen(e) til den/de som skal v&aelig;re listemoderator(er).
+# Bemærk at i tekstboksene nedenfor skal du skrive e-mailadressen(e) til
+# listeadministratoren(e).
 owner = ['nils@nilsstaerk.dk']
 
-# 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.
+# Det er to ejerskab forbundet med hver mailliste. Listeadministratorene
+# er dem der har den endelige kontrol over alle indstillingerne for
+# e-mallisten. De kan &aelig;ndre alle indstillinger der er tilgengelige
+# via disse administrative websider.
+# 
+# Listemoderatorene har begr&aelig;nset adgang; de kan ikke &aelig;ndre
+# indstillinger for e-maillisten, men de kan tage sig af
+# foresp&oslash;rgsler ang&aring;ende listen, f.eks. ans&oslash;gning om
+# medlemskab, eller godkende/afvise meddelelser der skal godkendes for
+# at kunne udsendes p&aring; listen. Listeadministratorene kan selvsagt
+# ogs&aring; udf&oslash;re disse opgaver.
+# 
+# For at aktivere muligheten for at have listemoderatorer, og p&aring;
+# den m&aring;den opdele arbejdsopgaverne der er forbundet med listen,
+# skal du s&aelig;tte dit eget moderatorpassword, og indtaste din
+# e-mailadresse(r) til den/de der skal v&aelig;re listemoderator(er).
+# Bemærk at i tekstboksene nedenfor skal du skrive e-mailadressen(e) til
+# listemoderatoren(e).
 moderator = []
 
-# 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.
+# Denne beskrivelsen 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 gj&oslash;re det uklart
+# hvad meningen med maillisten er eller hvad den skal bruges til.
 description = 'Info regarding Nils Staerk'
 
-# 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.
+# Teksten tolkes som html bortset fra linieskift, der vil blive
+# &aelig;ndret til html-tag'en '<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. Benytter du html-kode,
+# husk da at gennemse meget grundigt, for fejl (f.eks. manglende
+# slutt-tag's) kan f&oslash;re til at listens informationsside ikke vil
+# vises s&aring;dan som den skal.
 info = ''
 
-# 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 er sat ind foran emne-/tittelfeltet i e-mail der sendes
+# til listen, for at skille e-mailliste-meddelelser i e-mailboksen fra
+# dem der er medlem af listen. Denne tekst b&oslash;r holdes p&aring; et
+# absolut minimum, benytter du f.eks. listens navn og navnet er langt,
+# b&oslash;r du stave det endnu kortere her. Men den b&oslash;r fremover
+# v&aelig;re beskrivende for listen.
 subject_prefix = '[Nilsstaerk] '
 
-# Hide the sender of a message, replacing it with the list address
-# (Removes From, Sender and Reply-To fields)
+# Skjule afsenderen af meddelser, ved at erstatte den med e-maillistens
+# adresse (Dette medfører at alle From:, Sender, og Reply-To: felter
+# fjernes)
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 anonymous_list = 0
 
-# 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.
+# Skal eksisterende Reply-To: felt i meddelelseshovedet fjernes? Hvis ja
+# vil dette blive gjort uanset om Mailman tlføjer et Reply-To: felt
+# eller ikke.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 first_strip_reply_to = 0
 
-# 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.org/essays/reply-to-useful.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.
+# Denne indstillling fort&aelig;ller hvad Mailman skal gj&oslash;re med
+# Reply-To: feltet i meddelelseshovedet 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;dan 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 diskusion omkring
+# emnet. Se Reply-To Munging Considered Useful for modsatte meninger.
+# 
+# Nogle maillister har begr&aelig;nset adgang, med en egen parallell
+# liste beregnet til diskutioner. Eksempler p&aring; dette er 'patches'
+# eller 'checkin' lister, som system for revisionskontrol sender
+# &aelig;ndringer i programmet til, men diskusioner omkring udvikling af
+# programmet sendes til udviklerenes 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 diskusionsliste.
 #
-# legal values are:
-#    0 = "Poster"
-#    1 = "This list"
-#    2 = "Explicit address"
+# gyldige værdier:
+#    0 = "Afsender"
+#    1 = "mail listens adresse"
+#    2 = "Egendefineret adresse"
 reply_goes_to_list = 0
 
-# 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.org/essays/reply-to-useful.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.
+# 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 modifikasion af Reply-To:
+# adressen g&oslash;r det vanskeligere at sende svar kun til afsender.
+# Se 'Reply-To' Munging Considered Harmful for en diskusion omkring
+# temaet. Se Reply-To Munging Considered Useful for modsatte meninger.
+# 
+# Nogen maillister har begr&aelig;nset adgang, med en egen parallell
+# liste beregnet for diskusioner. Eksempler p&aring; dette er 'patches'
+# eller 'checkin' lister, som system for revisionskontrol sender
+# &aelig;ndringer til i programmet, men diskusioner rundt udvikling af
+# programmet sendes til udviklerenes egen mailliste. For at
+# st&oslash;tte s&aring;danne maillister, definer Reply-To: adressen
+# her, og vælg Egendefineret adresse i indstillingen reply_goes_to_list.
+# 
+# Bem&aelig;rk at hvis den oprindelige meddelse indeholder et Reply-To:
+# felt, vil det ikke &aelig;ndres.
 reply_to_address = ''
 
-# 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.
+# S&aelig;t denne til 'ja' hvis listen skal bruges som en "paraply" for
+# flere andre lister. N&aring;r denne er sat, vil bekr&aelig;ftigelser
+# og meddelelser med password blive sendt til en egen adresse som
+# beregnes ud fra e-mailadressen som er tilmeldt listen - v&aelig;rdien
+# af indstillingen "umbrella_member_suffix" bruges til dette. Denne
+# v&aelig;rdi tilf&oslash;jes til medlemmets kontonavn (det som
+# st&aring;r f&oslash;r @-tegnet).
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 umbrella_list = 0
 
-# 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".
+# N&aring;r "umbrella_list" indikerer at denne liste har andre
+# maillister som medlemmer, er det som regel &oslash;nskelig at
+# administrative meddelelser som f.eks. bekr&aelig;ftigelser og password
+# reminders ikke sendes til selve listen som er medlem, men til
+# administratoren for listen. Hvis dette er tilf&aelig;ldet, bruges
+# v&aelig;rdien af denne indstilling til at bestemme adressen sådan at
+# 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".
 umbrella_member_suffix = '-owner'
 
-# 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.
+# S&aelig;tt denne til hvis du vil have at password reminder skal sendes
+# til medlemmene en gang hver m&aring;ned. Husk at medlemmene kan
+# ogs&aring; selv frav&aelig;lge dette.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 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.
+# Tekst du skriver her vil blive tilf&oslash;jet &oslash;verst i
+# velkomsthilsenen der sendes til nye medlemmer. Velkomshilsenen
+# indeholder allerede viktige adresser og URLer knyttet til maillisten,
+# s&aring; sådan information er det ikke n&oslash;dvendig at inkludere
+# her. Her kan du indl&oslash;gge f.eks. oplysning om etikette eller
+# regler for brug af listen, o.l.
+# 
+# Bem&oslash;rk: Liniene i denne tekst vil brydes efter f&oslash;lgende
+# regler:
 # 
-# 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.
+# Hvert afsnit udfyldes s&aringdan at ingen linie er lenger en 70 tegn.
+# Enhver linie der begynder med blanke tegn udfyldes ikke. Blanke linier
+# adskiller afsnitt.
 # 
 welcome_msg = ''
 
-# 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.
+# S&aelig;t kun denne til 'Nej' hvis du skal il&aelig;gge nye medlemmer
+# manuelt, og ikke vil have de skal f&aring; dette 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.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 send_welcome_msg = 0
 
-# Text sent to people leaving the list.  If empty, no special text will
-# be added to the unsubscribe message.
+# Tekst der sendes til medlemmer der framelder sig fra listen. Hvis
+# denne er tom, l&aelig;gges det ikke noget tekst til frameldelsen.
 goodbye_msg = ''
 
-# Send goodbye message to members when they are unsubscribed?
+# Sende afskedshilsen til medlemmer n&aring;r de frameldes?
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 send_goodbye_msg = 1
 
-# 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.
+# Der udsendes en reminder til listemoderatoren(e) (og
+# listeadministratoren(e)) dagligt om foresp&oslash;rsler der af en
+# eller anden grund venter p&aring; behandling. V&aelig;lger du "Ja",
+# vil listeadminstratoren ogs&aring; motdtage en meddelelse s&aring;
+# snart en foresp&oslash;rsel kommer ind.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 admin_immed_notify = 1
 
-# Should administrator get notices of subscribes and unsubscribes?
+# Skal listeadministratoren(e) ogs&aring; modtage meddelelse om nye
+# medlemmer der tilmelder sig og gamle medlemmer som framelder sig?
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 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.
+# Besked om at en meddelelse skal godkendes sendes ud til afsenderen
+# s&aring;fremt meddelelsen stoppes pga. noget andet end listemoderation
+# eller spam filtre. S&aelig;ttes denne indstilling til 'Nej', vil
+# afsender overhovedet ikke modtage denne besked.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 respond_to_post_requests = 1
 
-# 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.
+# Når dette valg er aktiveret, vil alt e-mail til listen blive moderert.
+# 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-moderasjon" kan da hjælpe dig at fjerne usaglige meddelelser
+# til listen, og på den måden dysse en ophedet diskusion ned.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
-emergency = 1
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
+emergency = 0
 
-# When a new member is subscribed to this list, their initial set of
-# options is taken from the this variable's setting.
+# Når et nyt medlem tilmeldes listen, blir medlemmets indstillinger
+# taget herfra.
 new_member_options = 256
 
-# 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.
+# Filter for administrative meddelelser vil unders&oslash;ge om
+# meddelelsen egentligt er ment som en administrativ foresp&oslash;rgsel
+# (f.eks. tilmelding, framelding, o.l.), og is&aring;fald sende
+# meddelelsen til administratoren i stedet.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 administrivia = 1
 
-# Maximum length in kilobytes (KB) of a message body.  Use 0 for no
-# limit.
+# Maximum st&oslash;rrelse i kilobytes (KB) for indholdet i e-mail der
+# sendes til listen. Brug verdien '0' for ikke at have en
+# begr&aelig;nsning.
 max_message_size = 40
 
-# 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'
-
-# 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).
+# "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; denne maskinen. Denne
+# indstillingen kan v&aelig;re nyttig hvis maskinen har flere navne.
+host_name = 'www.nilsstaerk.dk'
+
+# I RFC 2369 defineres en r&aelig;kke List-* felter i
+# meddelelseshovedet, der normalt tilf&oslash;jes hver meddelelse der
+# sendes ud via listen. Disse felter kan hj&aelig;lpe de brugere af
+# listen der benytter et e-mailprogram som f&oslash;lger denne standard.
+# Disse felter b&oslash;r derfor altid v&aelig;re med.
+# 
+# Ikke alle e-mailprogrammer f&oslash;lger denne standard. Er det mange
+# af medlemmene p&aring; listen der benytter s&aring;danne
+# e-mailprogrammer, der ikke kan h&aring;ndtere disse felter i
+# meddelelseshovedet, kan det v&aelig;re du vil v&aelig;lge at udelade
+# dem. Men du b&oslash;r f&oslash;rst fors&oslash;ge at l&aelig;re og
+# forklare medlemmene 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 disse felter, men dette anbefales ikke (denne
+# muligheten kan faktisk ogs&aring; blive fjernet i senere versioner).
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 include_rfc2369_headers = 1
 
-# 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.)
+# List-Post: feltet er et af felterne anbefalet i RFC 2369. Visse
+# e-maillister (som f.eks. kun bruges til offentligørelser), er det kun
+# visse personer der har lov til at sende til; de som er medlem af
+# listen har generelt ikke lov til at sende til listen. For disse
+# lister, er List-Post: feltet forvirrende. I visse tilf&aelig;lde kan
+# det være forvirrende at s&aelig;tte denne indstilling til Nej,
+# s&aring; feltet ikke tilføjes. (Dette påvirker ikke andre List-*:
+# felter.)
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 include_list_post_header = 1
 
 ## Language options
 #
-# 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.
+# Underst&oslash;ttelse for flere sprog. (Internationalisering)
+
+# Dette er standardsproget som benyttes for denne mailliste. Hvis mer
+# 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.
 preferred_language = 'en'
 
-# These are all the natural languages supported by this list. Note that
-# the default language must be included.
+# Her er alle spr&aring;gene denne listen har underst&oslash;ttelse for.
+# Bem&aelig;rk at standardsproget skal v&aelig;re med.
 available_languages = ['en', 'da']
 
-# 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.
+# Hvis standardsproget for din mailliste benytter et andet tegns&aelig;t
+# end ASCII og tittel prefixet for listen indeholder tegn som ikke
+# findes i ASCII-tegns&aelig;ttet, vil prefixet alltid blive kodet i
+# henhold til den relevante standard. Hvis tittel prefixet kun
+# indeholder ASCII tegn, kan det imidlertid ske at du ønsker at sætte
+# dette valg til Aldrig for at undgå koding. Dette kan gøre titlen lidt
+# mere læselig for brugere med e-mailprogrammer der ikke takler andre
+# tegnsæt end ASCII på en rigtig måde.
+# 
+# Bemærk imidlertid at hvis din mailliste modtager både kodede og
+# ukodede tittel felt, kan det være bedst at vælge Efter behov. Med
+# denne indstilling vil Mailman ikke kode ASCII prefixer hvis resten af
+# tittelfeltet kun indeholder ASCII tegn, men vil kode prefixet hvis det
+# indeholder tegn som ikke er ASCII tegn. På denne måde undgås en [...]
+# i standarderne, som forårsager at visse e-mailprogrammer vil vise
+# ekstra eller manglende mellemrum imellom tittel prefixet og det
+# oprindelige tittelfelt.
 #
-# legal values are:
-#    0 = "Never"
-#    1 = "Always"
-#    2 = "As needed"
+# gyldige værdier:
+#    0 = "Aldrig"
+#    1 = "Altid"
+#    2 = "Efter behov"
 encode_ascii_prefixes = 0
 
 ## Nondigest options
 #
-# Policies concerning immediately delivered list traffic.
+# Regler for levering i normal-modus.
 
-# Can subscribers choose to receive mail immediately, rather than in
-# batched digests?
+# Kan medlemmer vælge normal-modus?
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 nondigestable = 1
 
-# 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:
+# 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:
 # 
 # 
 # real_name - The "pretty" name of the list; usually the list name with
@@ -381,9 +405,10 @@ nondigestable = 1
 # 
 msg_header = ''
 
-# 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:
+# Tekst som tilf&aelig;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:
 # 
 # 
 # real_name - The "pretty" name of the list; usually the list name with
@@ -413,42 +438,44 @@ msg_footer = """_______________________________________________
 
 ## Digest options
 #
-# Batched-delivery digest characteristics.
+# Opsætning af sammendrag-modus.
 
-# Can list members choose to receive list traffic bunched in digests?
+# Kan medlemmer af listen vælge at f&aring; tilsendt sammendrag i stedet
+# for?
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 digestable = 1
 
-# Which delivery mode is the default for new users?
+# Hvilken modus er standard for nye brugere?
 #
-# legal values are:
-#    0 = "Regular"
-#    1 = "Digest"
+# gyldige værdier:
+#    0 = "Normal"
+#    1 = "Sammendrag"
 digest_is_default = 0
 
-# When receiving digests, which format is default?
+# Hvilket format skal benyttes som standard for samle-email?
 #
-# legal values are:
-#    0 = "Plain"
+# gyldige værdier:
+#    0 = "Ren tekst"
 #    1 = "MIME"
 mime_is_default_digest = 0
 
-# How big in Kb should a digest be before it gets sent out?
+# Hvor stor (i Kb) m&aring; en samle-email h&oslash;jst v&aelig;re
+# f&oslash;r den udsendes?
 digest_size_threshhold = 30
 
-# Should a digest be dispatched daily when the size threshold isn't
-# reached?
+# Skal der sendes en samle-email dagligt, selv om st&oslash;rrelsen ikke
+# er opn&aring;et?
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 digest_send_periodic = 1
 
-# Text attached (as an initial message, before the table of contents) to
-# the top of digests. This text can include Python format strings which
+# Tekst som l&aelig;gges til &oslash;verst i samle-emailen, f&oslash;r
+# indholdsfortegnelsen.This text can include Python format strings which
 # are resolved against list attributes.  The list of substitutions
 # allowed are:
 # 
@@ -475,9 +502,10 @@ digest_send_periodic = 1
 # 
 digest_header = ''
 
-# 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:
+# Tekst der tilføjes nederst i hver samle-e-mail, som sidste
+# information.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
@@ -505,274 +533,277 @@ digest_footer = """_______________________________________________
 %(real_name)s@%(host_name)s
 %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s"""
 
-# When a new digest volume is started, the volume number is incremented
-# and the issue number is reset to 1.
+# N&aring;r et nyt volume startes, &oslash;ges volume nummeret, og
+# udgavenummeret s&aelig;ttes til 1.
 #
-# legal values are:
-#    0 = "Yearly"
-#    1 = "Monthly"
-#    2 = "Quarterly"
-#    3 = "Weekly"
-#    4 = "Daily"
+# gyldige værdier:
+#    0 = "&Aring;rlig"
+#    1 = "M&aring;nedlig"
+#    2 = "Kvartalsvis"
+#    3 = "Ugentlig"
+#    4 = "Daglig"
 digest_volume_frequency = 1
 
 ## Privacy options
 #
-# 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/nilsstaerk/archive">Archival 
-# Options</a> section for separate archive-related privacy settings.
-
-# Advertise this list when people ask what lists are on this machine?
+# Her kan du bestemme hvad der kr&oslash;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&oslash;lder
+# arkivet og arkivering.
+
+# Vise denne mailliste n&aring;r nogn beder om at se en oversigt over
+# maillister p&aring; denne maskine?
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 advertised = 1
 
-# 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.
+# bek&aelig;ftigelse(*) - bekr&aelig;ftigelse af e-mail er
+# n&oslash;dvendig godkendelse - ans&oslash;gkning om medlemskabp skal
+# godkendes af listeadministrator (eller evt. listemoderator)
+# bekr&aelig;ftigelse+godkendelse - b&aring;de bekr&aelig;ftelse
+# p&aring; e-mail og godkendelse af listeadministrator (evt.
+# listemoderator) er nun&oslash;dvendig
+# 
+# (*) n&aring;r nogen vil tilmelde sig en liste, sender Mailman en
+# meddelelse med et uniktidentifikator som de skal opgive for at
+# bekr&oslash;fte tilmeldingen. P&aring; denne m&aring;den vil det da
+# ikke v&aelig;re muligt at tilmelde nogen til listen imod deres vilje.
 #
-# legal values are:
-#    1 = "Confirm"
-#    2 = "Require approval"
-#    3 = "Confirm and approve"
+# gyldige værdier:
+#    1 = "Bekr&aelig;ftigelse"
+#    2 = "Godkendelse"
+#    3 = "Bekr&aelig;ftigelse og godkendelse"
 subscribe_policy = 2
 
-# 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.
+# N&aring;r medlemmer &oslash;nsker at forlade en mailliste, sender de
+# en ans&oslash;gning om framelding, enten via web, eller via e-mail.
+# Normalt er det best at disse ans&oslash;gninger automatisk godkendes,
+# s&aring; meldemmer kan udmelde sig n&aring;r de &oslash;nsker det
+# (mange &oslash;nsker selv at kunne administrere en frameldelse. For
+# nogen f&aring; maillister kan det aligevel v&aelig;re aktuelt at have
+# kontrol over om medlemmer kan melde sig selv ud eller ikke. En liste
+# som alle ansatte i et firma M&Aring; v&aelig;re medlem af, er et
+# eksempel p&aring; en s&aring;dan liste.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 unsubscribe_policy = 0
 
-# 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.
+# Alle e-mailadresser som angives her vil blive udelukket fra listen, og
+# kan ikke tilmelde sig. Indtast e-mailadresser, en per linie, start
+# linien med tegnet ^ for at angive et regexp-udtryk der skal passe 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']
 
-# When set, the list of subscribers is protected by member or admin
-# password authentication.
+# Hvis denne indstilling er sat til, vil listen over medlemmer af
+# e-maillisten blive beskyttet af medlemmenes eller adminstratorens
+# password.
 #
-# legal values are:
-#    0 = "Anyone"
-#    1 = "List members"
-#    2 = "List admin only"
+# gyldige værdier:
+#    0 = "Alle"
+#    1 = "Kun medlemmer af listen"
+#    2 = "Kun listeadministrator"
 private_roster = 2
 
-# 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.
+# V&aelig;lger du 'Ja' her, vil medlemmers e-mailadresse omskrives
+# n&aring;r de vises i en oversigt p&aring; websidene (b&aring;de som
+# tekst og i linker), s&aring; de ikke er nemme at tolke som
+# e-mailadresser. Meningen med dette er at undg&aring; at e-mailsniffere
+# der gennemg&aring;r websider for at finde e-mailadresser (og derefter
+# bruge dem til at udsende spam/junk mail) til ikke at opsamle
+# medlemmenes e-mailadresser.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 obscure_addresses = 0
 
 ## Privacy options
 #
-# 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.
+# N&aring;r en meddelelse sendes til maillisten, g&aring;r den igennem
+# en r&aelig;kke trin for at afg&oslash;re om moderatoren m&aring;
+# godkende meddelelsen eller ikke. Her finder du indstillinger for 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 de sendes til listen.
+# 
+# <p>e-mail som ikke er sendt af medlemmer af listen, kan automatisk bli
+# <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">sendt
+# retur</a>, eller <a
+# href="?VARHELP=privacy/sender/discard_these_nonmembers">afvist</a>,
+# enten individuelt eller som en gruppe. All e-mail fra ikke-medlemmer,
+# som ikke specifikt bliver godkent, sendes retur, eller afvist, 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 il&aelig;gger du en e-mailadresse per
+# linie. Du kan ogs&aring; il&aelig;gge  <a
+# href="http://www.python.org/doc/current/lib/module-re.html">Python
+# regexp-uttrykk</a>. Begynd is&aring;fald linien med tegnet ^ for at
+# markere at det er et s&aring;dan udtryk. N&aring;r du benytter
+# backslash, skriv da lige som i rene strings (Python raw strings)
+# (normalt kun &eacute;n backslash af gangen).
+# 
+# <p>Bem&aelig;rk: match p&aring; 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-mail fra medlemmet kan sendes direkte til e-maillisten, eller om de
+# f&oslash;rst skal godkendes af listemoderatoren. N&aring;r
+# moderationsflaget er sat til, skal e-mail fra medlemmet godkendes af
+# listemoderatoren f&oslash;r det udsendes til alle p&aring; listen. Som
+# listeadminsitrator kan du for hvert enkelt medlem bestemme om
+# medlemmets e-mail skal modereres eller ikke. N&aring;r et nyt medlem
+# tilmeldes til 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
+# Administrere medlemmer siden.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 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.
 # 
-# Discard -- this simply discards the message, with no notice sent to
-# the post's author.
+# Holde tilbage -- meldingen holdes tilbage for godkendelse af
+# listemoderatoren(e). Afslå -- meldingen sendes automatisk retur til
+# afsender. Begrundelsen der sendes kan du skrive selv Slette --
+# meddelelsen blir afvist uden at give besked om dette til afsender.
 # 
 #
-# legal values are:
-#    0 = "Hold"
-#    1 = "Reject"
-#    2 = "Discard"
+# gyldige værdier:
+#    0 = "Holde&nbsp;tilbage"
+#    1 = "Afvis"
+#    2 = "Kassere"
 member_moderation_action = 0
 
-# 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.
+# Tekst som skal sendes med meldingen om retur som sendes til modereede
+# medlemmer af listen.
 member_moderation_notice = ''
 
-# 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.
+# e-mail fra disse ikke-medlemmer vil automatisk blive godkendt.
+# Il&aelig;g e-mailadresser, en per linie, start linien med tegnet ^ for
+# at angive et regexp-uttryk som skal passe med afsenderadressen.
 accept_these_nonmembers = []
 
-# 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.
+# e-mail fra disse ikke-medlemmer vil automatisk blive holdt tilbage for
+# vurdering af listemoderatorene. Afsenderen vil modtage en meddelelse
+# om dette, med bl.a. instruktioner om hvordan han/hun kan
+# tilbagetr&aelig;kke sin e-mails. Indtast e-mailadresser, en per linie,
+# start linien med tegnet ^ for at angive et regexp-uttrykk som skal
+# passe med afsenderadressen.
 hold_these_nonmembers = []
 
-# 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.
+# 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 spam-afsendere,
+# de b&oslash;r automatisk afvises. Indtast e-mailadresser, en per
+# linie, start linien med tegnet ^ for &aring; angiv et regexp-uttrykk
+# som skal passe 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']
 
-# 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.
+# e-mail fra disse ikke-medlemmer vil automatisk blive afvist. Det vil
+# sige at meddelelsen afvises uden nogen form for tilbagemelding, men
+# listemoderatorene kan (om ønskeligt) modtage en kopi af den afviste
+# e-mail. Tilf&oslash;je e-mailadresser, en per linie, start linien med
+# tegnet ^ for at angive et regexp-uttryk der skal passe med
+# afsenderadressen.
 discard_these_nonmembers = []
 
-# 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.
+# N&aring;r en e-mail fra et ikke-medlem blir modtaget, sammenlignes
+# e-mailens afsender med listen over e-mailadresser der skal godkendes,
+# holdes tilbage, afvises (sendes i retur), og afvises. Hvis
+# afsenderadressen ikke passer med den der er opgivet i listene, blir
+# f&oslash;lgende afg&oslash;relse taget.
 #
-# legal values are:
-#    0 = "Accept"
-#    1 = "Hold"
-#    2 = "Reject"
-#    3 = "Discard"
+# gyldige værdier:
+#    0 = "Godkende"
+#    1 = "Holde&nbsp;tilbage"
+#    2 = "Afvis"
+#    3 = "Kassere"
 generic_nonmember_action = 1
 
-# Should messages from non-members, which are automatically discarded,
-# be forwarded to the list moderator?
+# Skal meddelelser fra ikke-medlemmer, som automatisk afvises, også
+# sendes til listemoderatoren?
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 forward_auto_discards = 1
 
 ## Privacy options
 #
-# This section allows you to configure various filters based on the
-# recipient of the message.
+# Her kan du ops&aelig;tte filtrering baseret på modtaeren af
+# meddelelsen.
 
-# 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.
+# Meget (faktisk det meste af) spam/junk mail har ikke de endelige
+# modtagere i modtagerfelterne. Faktisk s&aring; indeholder felterne To:
+# og/eller Cc: oftest en fuldst&aelig;ndig 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(e), men vil
+# aligevel blive fanget og blokkere det meste af spam/junk mail.
 # 
-# 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 ville 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
+# alias for listen.
 # 
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 require_explicit_destination = 1
 
-# 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.
+# Alternative e-mailadresser som godtages n&aring;r
+# 'require_explicit_destination' er sat til. Som v&aelig;rdi for denne
+# indstilling skal du opgive regexp-uttryk ("regular expressions"), et
+# udtryk per linie, der sammenlignes imod 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 imod den f&oslash;rste
+# del (det som st&aring;r f&oslash;r '@') af modtageradressen. Hvis
+# sammenligningen ikke lykkes, eller hvis udtrykket ikke indholder en
+# '@', sammenlignes udtrykket med hele modtageradressen.
+# 
+# Sammenligning kun imod den f&oslash;rste del af en modtageradresse
+# underst&oslash;ttes ikke i fr&aelig;mtidige udgaver af Mailman, vil
+# kun sammenligning imod hele modtageradresser blive
+# underst&oslash;ttet.
 acceptable_aliases = ''
 
-# If a posting has this number, or more, of recipients, it is held for
-# admin approval.  Use 0 for no ceiling.
+# Hvis en mail der er sendt til listen indeholder s&aring; mange
+# modtagere som, eller flere modtagere end, denne værdi, holdes malen
+# tilbage så listeadministratoren eventuelt kan godkende den. Brug
+# værdien 0 for ingen begrænsning.
 max_num_recipients = 10
 
 ## Privacy options
 #
-# 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.
-# 
+# Her kan du opsætte forskellige anti-spam filtre, som kan være til
+# hjælp for 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
@@ -785,16 +816,20 @@ max_num_recipients = 10
 # match.
 header_filter_rules = []
 
-# 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.
+# Brug denne indstilling til at fra-filtrere mail til listen, baseret
+# p&aring; indholdet af et eller flere felter i mailhovedet. Her skal du
+# skrive regexp-uttryk (regular expressions), et per linie, som
+# sammenlignes mod det aktuelle felt. Sammenligningen sk&aelig;lner ikke
+# imellem store og sm&aring; bogstaver. Linier der begynder med '#'
+# sammenlignes ikke.
 # 
-# For example:to: .*@public.com  says to hold all postings with a To:
-# mail header containing '@public.com' anywhere among the addresses.
+# For eksempel: udtrykket to: .*@public.com fort&aelig;ller at alt mail
+# som indeholder '@public.com' i To: feltet, skal holdes tilbage til
+# godkendelse.
 # 
-# 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.
+# Bem&aelig;rk: blanke tegn i starten af regexp-udtrykket fjernes. Dette
+# kan man undg&aring; p&aring; flere m&aring;ter, f.eks. ved at bruge
+# escape-tegn eller parenteser.
 bounce_matching_headers = """# Lines that *start* with a '#' are comments.
 to: friend@public.com
 message-id: relay.comanche.denmark.eu
@@ -803,54 +838,56 @@ from: .*@uplinkpro.com"""
 
 ## Bounce options
 #
-# 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.
+# Disse regler bestemmer hvordan automatisk behandling af returmails
+# gj&oslash;res. Her er en oversigt over hvordan funktionen er.
+# 
+# <p>N&aring;r Mailman modtager en returmail, blir to ting
+# fors&oslash;kt tolket. Det ene er e-mailadressen til medlemmet som
+# egentlig skulle modtage e-mailen, og det andet er &aring;rsagen til
+# problemet. &Aring;rsagen tolkes til at v&aelig;re <em>alvorlig</em>
+# eller <em>lett</em> alt efter om &aring;rsagen er af kritisk eller af
+# mindre alvorlig art. Såfremt der er tvivl, tolkes &aring;rsaken som
+# alvorlig.
+# 
+# <p>Hvis ingen e-mailadresse kan hentes ud af meddelelsen, blir den
+# normalt afvist. Ellers, vil medlemmet som har e-mailadressen f&aring;
+# en <em>returtal</em>, og hver gang en returmeddelelse kommer vil
+# tallet &oslash;ges. Alvorlige &aring;rsaker f&oslash;rer til at tallet
+# &oslash;ges med 1, lette &aring;rsaker f&oslash;rer til at det
+# &oslash;kes med 0.5. Dette sker kun &eacute;n gang per dag, s&aring;
+# selv om det 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;ttest til igen.
+# Medlemmet vil med j&aelig;vne mellemrum modtage melding 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>Det er en vigtig indstilling til; efter en vis tid -- hvis ingen
+# returmeddelelser dukker op i l&oslash;bet af denne tid -- anses
+# returinformation som <a
+# href="?VARHELP=bounce/bounce_info_stale_after">udg&aring;et</a> og
+# afvises. Ved at justere denne værdi, og sætte en grænse for
+# returantallet, kan du bestemme hvor lang tid der skal gå f&oslash;r
+# levering til et medlem stoppes. Begge disse værdier skal du justere
+# alt efter hvor ofte og hvor meget e-mail der sendes til din liste.
+
+# Ved at sætte denne værdi til Nej, sætter du alt automatisk tolking af
+# returmeddelelser for denne liste fra. Bemærk at såfremt meddelelser
+# afvises vil listeadministratoren ikke blive forstyrret med dem.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 bounce_processing = 1
 
 # Each subscriber is assigned a bounce score, as a floating point
@@ -866,351 +903,345 @@ bounce_processing = 1
 # mailing list.
 bounce_score_threshold = 5.0
 
-# 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.
+# Antal dage f&oslash;r returinformation afvises såfremt der ikke dukker
+# flere returmails op. Dette tal skal v&aelig;re et heltal.
 bounce_info_stale_after = 7
 
-# 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.
+# Hvor mange Levering til dig er stoppet advarsler der skal sendes til
+# et medlem f&oslash;r medlemmet frameldes fra listen. S&aelig;t denne
+# værdi til 0 for at fjerne et medlem fra listen umiddelbart
+# s&aring;fremt der kommer returmails fra medlemmets e-mailadresse.
+# Dette tal skal være et heltal.
 bounce_you_are_disabled_warnings = 3
 
-# The number of days between sending the Your Membership Is Disabled
-# warnings.  This value must be an integer.
+# Antal dage imellem hver gang en Levering til dig er stoppet advarsel
+# skal sendes ud. Dette tal skal være et heltal.
 bounce_you_are_disabled_warnings_interval = 7
 
-# 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.
+# Mailmans automatiske returmailhåndtering er meget robust, men det er
+# aligevel umuligt at genkende alle typer returmails der kommer. Du bør
+# angive Ja her, af to grunde: 1) Hvis det virkelig er en permanent
+# returmail fra et medlem af listen, bør du antageligt manuelt udmelde
+# medlemmet fra listen, og 2) du vil måske sende meddelelse til
+# udviklerne af Mailman sådan at returmails automatisk genkendes af
+# Mailman i senere versioner. Hvis du ikke vil gøre nogen af delene, sæt
+# da denne indstilling til Nej. Så vil alle returmails afvises
+# automatisk uden videre behandling. Bem&aelig;rk: Denne indstilling vil
+# også indvirke på alt e-mail der sendes til listens -admin adresse. Den
+# adresse er gammel og udgået, men det kan være at nogen fortsat vil
+# sende e-mail til den. Hvis nogen gør det, og du har sat denne
+# indstilling til Nej, vil disse mails også blive afvist. Måske vil du
+# også opsætte et automatisk svar på e-mail sendt til -owner og -admin
+# adresserne.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 bounce_unrecognized_goes_to_list_owner = 1
 
-# 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.
+# Ved at sætte denne til Nej, fravælges beskeden der normalt sendes til
+# ejeren(e) af listen, når afsending 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.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 bounce_notify_owner_on_disable = 1
 
-# 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.
+# Ved at sætte denne til Nej, fravælges beskeden der normalt sendes til
+# ejeren(e) af listen, når et medlem frameldes fra listen på grund af
+# for mange returmails. Der vil til gengæld altid blive forsøgt afsendt
+# en e-mail med besked til medlemmet.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 bounce_notify_owner_on_removal = 1
 
 ## Archive options
 #
-# List traffic archival policies.
+# Regler for arkivering
 
-# Archive messages?
+# Arkivere e-mail i et arkiv?
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 archive = 0
 
-# Is archive file source for public or private archival?
+# Skal filen arkiveres i et privat eller i et offentlig arkiv?
 #
-# legal values are:
-#    0 = "public"
-#    1 = "private"
+# gyldige værdier:
+#    0 = "offentlig"
+#    1 = "privat"
 archive_private = 0
 
-# How often should a new archive volume be started?
+# Hvor ofte skal arkivet deles op?
 #
-# legal values are:
-#    0 = "Yearly"
-#    1 = "Monthly"
-#    2 = "Quarterly"
-#    3 = "Weekly"
-#    4 = "Daily"
+# gyldige værdier:
+#    0 = "&Aring;rlig"
+#    1 = "M&aring;nedlig"
+#    2 = "Kvartalsvis"
+#    3 = "Ugentlig"
+#    4 = "Daglig"
 archive_volume_frequency = 2
 
 ## Gateway options
 #
-# Mail-to-News and News-to-Mail gateway services.
+# e-mail-Til-Nyhedsgruppe og Nyhedsgruppe-Til-e-mail tjeneste.
 
-# 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.
+# 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.
 nntp_host = ''
 
-# The name of the Usenet group to gateway to and/or from.
+# Navn p&aring; nyhedsgruppe der skal sendes til og/eller fra.
 linked_newsgroup = ''
 
-# Should new posts to the mailing list be sent to the newsgroup?
+# Skal nye mail til denne liste sendes til nyhedsgruppen?
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 gateway_to_news = 0
 
-# Should new posts to the newsgroup be sent to the mailing list?
+# Skal nye meddelelser til nyhedsgruppen sendes til denne mailliste?
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 gateway_to_mail = 0
 
-# 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.
+# 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&aring;t da 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
+# Moderet, vil en ekstra meddelelse holdes tilbage i
+# godkendelsesprocessen. Alt mail sendt til maillisten skal godkendes
+# f&oslash;r de sendes til nyhedsgruppen, eller til medlemmene af
+# listen.
+# 
+# Vær opm&aelig;rksom p&aring; at hvis mailhovedet i mailen har et
+# Approved: felt med listens administrative password, 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 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 meddelelseshovedet.
 #
-# legal values are:
-#    0 = "None"
-#    1 = "Open list, moderated group"
-#    2 = "Moderated"
+# gyldige værdier:
+#    0 = "Ingen"
+#    1 = "Åben liste, modereret nyhedsgruppe"
+#    2 = "Modereret"
 news_moderation = 0
 
-# 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.
+# Mailman tilføjer normalt en tekst du selv 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 sette denne indstilling
+# til Nej hvis du ikke ønsker emne prefix tilføjet til mail som sendes
+# til Usenet. Sætter du emne prefix for listen til off, vil opsamlet
+# meddelelser heller ikke få præfix tilføjet.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 news_prefix_subject_too = 1
 
 ## Autoreply options
 #
-# Auto-responder characteristics.<p>
+# Indstillinger for automatiske svar.<p>
 # 
-# 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>
+# 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 epostadresse</em>
+# <li><b>owneremail</b> - <em>listens -owner epostadresse</em> </ul>
 # 
-# <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.
+# <p>Du kan enten skrive teksten direkte i tekstboksene, eller du kan
+# angive navnet p&aring; en fil som indeholder teksten. Denne file vil
+# s&aring; blive indl&aelig;st i tekstboksen, fra dit lokale filsystem.
 
-# Should Mailman send an auto-response to mailing list posters?
+# Skal Mailman sende et automatisk svar til dem der sender e-mail til
+# listen?
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 autorespond_postings = 0
 
-# Auto-response text to send to mailing list posters.
+# Automatisk svar der skal sendes.
 autoresponse_postings_text = ''
 
-# Should Mailman send an auto-response to emails sent to the -owner
-# address?
+# Skal Mailman sende et automatisk svar p&aring; e-mail der sendes til
+# -owner adressen?
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 autorespond_admin = 0
 
-# Auto-response text to send to -owner emails.
+# Automatisk svar p&aring; e-mail til -owner adressen.
 autoresponse_admin_text = ''
 
-# 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.
+# 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
+# ogs&aring; skal v&aelig;re med i det automatiske svar.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes, w/discard"
-#    2 = "Yes, w/forward"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja, men uden den originale e-mailn"
+#    2 = "Ja, og medtag den originale e-mail"
 autorespond_requests = 0
 
-# Auto-response text to send to -request emails.
+# Automatisk svar p&aring; e-mail til -request adressen.
 autoresponse_request_text = ''
 
-# 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).
+# Antal dage imellem automatisk svar p&aring; e-mail, fra samme
+# afsender, til listen eller til -request/-owner adressene. S&aelig;t
+# denne v&aelig;rdi til 0 (eller et negativt tal) for at sende
+# automatisk svar hver gang.
 autoresponse_graceperiod = 90
 
 ## Contentfilter options
 #
-# 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.  Then, each
-# <tt>multipart/alternative</tt> section will be replaced by just the
-# first alternative that is non-empty after filtering.
-# 
-# <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?
+# Regler for indhold i e-mail sendt til listen.
+# 
+# <p>Filtrering af indhold fungerer således: når listen modtger en
+# e-mail og du har beskyttelse med filtrering af indhold, sammenlignes
+# først eventuelle ved- hæftelser imod <a
+# href="?VARHELP=contentfilter/filter_mime_types">MIME filtre</a>. Hvis
+# en vedhæftelse passer med et af disse filtre, blir vedhæftelsen
+# fjernet.
+# 
+# <p>Derefter sammenlignes eventuelle vedhæftelser imod <a
+# href="?VARHELP=contentfilter/pass_mime_types">gyldige MIME typer</a>,
+# hvis nogen er defineret. Alle vedhæftelser som ikke passer med de
+# angivne MIME typene, blir fjernet.
+# 
+# <p>Efter disse filtre, vil alle tomme <tt>multipart</tt> vedhæftelser
+# blive fjernet. Hvis selve meddelelsen er helt tom efter denne
+# filtrering, vil meddelelsen bli afvist. Derefter vil hvert
+# <tt>multipart/alternative</tt> vedhæftelse blive erstattet af det
+# første alternative som ikke er tomt.
+# 
+# <p>Til slut vil alle <tt>text/html</tt> vedhæftelser som måtte være
+# tilbage i meddelelsen blive konverteret til <tt>text/plain</tt>
+# såfremt <a
+# href="?VARHELP=contentfilter/convert_html_to_plaintext">konvertere til
+# ren tekst</a> er sat til og serveren er konfigurert til at tillade
+# sådanne konverteringer.
+
+# Skal Mailman filtrere indhold i e-mail sendt til listen som angivet
+# nedenfor?
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 filter_content = 0
 
-# 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.
+# Brug denne instilling til at fjerne vedhæftelser der passer til MIME
+# typer. Hver linie skal her indeholde navnet på en MIME type/subtype,
+# f.eks. image/gif. Såfremt du ønsker at fjerne alle vedhæftelser som
+# har en given hoved MIME type, kan du lade være at angive subtype,
+# f.eks. image.
 # 
-# Blank lines are ignored.
+# Blanke linier medtages ikke.
 # 
-# See also <a href="?VARHELP=contentfilter/pass_mime_types"
-# >pass_mime_types for a content type whitelist.
+# Se også gyldige MIME typer for whitelist af MIME typer.
 filter_mime_types = ''
 
-# 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.
+# Brug denne indstilling for at definere hvilke MIME typer der skal være
+# tilladt. Krav og format for filtrering er identisk med MIME filtre.
 # 
-# 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.
+# Bem&aelig;rk: hvis du lægger noget ind her, men ikke angiver
+# multipart, vil al e-mail med vedhæftelser ikke blive medtaget.
 pass_mime_types = """multipart/mixed
 multipart/alternative
 text/plain"""
 
-# Should Mailman convert text/html parts to plain text?  This conversion
-# happens after MIME attachments have been stripped.
+# Skal Mailman konvertere text/html dele til ren tekst? Denne
+# konvertering vil finde sted efter at MIME filteret har fjernet de
+# ønskede dele.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 convert_html_to_plaintext = 1
 
-# One of these actions is take 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.
+# Her bestemmer du hvad der skal ske når en meddelelse filtreres fra af
+# et filter, altså såfremt vedhæftelsen filtreres fra MIME filteret,
+# eller ent vedhæftelse ikke har en af de gyldige MIME typer, eller
+# meddelelsen ender op med at være tom efter filtrering.
+# 
+# Bemærk at det du vælger her ikke vil ske såfremt en meddelelse stadig
+# indeholder noget efter filtrering. Så vil meddelelsen altid sendes
+# videre til listen.
+# 
+# Når meddelelsen afvises, skrives Message-ID'en til den afviste
+# meddelelse til loggen. Når meddelelsen sendes retur eller videresendes
+# til listens ejer, vil en begrundelse altid blive inkluderet i
+# returmail der sendes til afsenderen. Når meddelelserne skal bevares,
+# gemmes de i en specielt køkatalog på disk sådan at
+# serveradministratoren kan se (og måske gøre noget med) meddelelsen,
+# men ellers fjernet. Dette sidste valg er kun tilgængeligt såfremt
+# serveradministratoren har tilladt det.
 #
-# legal values are:
-#    0 = "Discard"
-#    1 = "Reject"
-#    2 = "Forward to List Owner"
-#    3 = "Preserve"
+# gyldige værdier:
+#    0 = "Kassere"
+#    1 = "Afvis"
+#    2 = "Videresend til Listens Ejer"
+#    3 = "Tag hånd om"
 filter_action = 0
 
 ## Topics options
 #
-# 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.
+# Emneord for listen
+
+# Emnefilteret kategoriserer hver e-mail som kommer til listen, efter
+# regexp-uttrykkene du skriver nedenfor. Hvis feltene Subject: eller
+# Keywords: i mailhovedet i en mail passer imod disse udtryk, blir den
+# placeret under dette emne. Hvert medlem af listen kan vælge kun at
+# modtage mail der passer til de &oslash;nskede emner. e-mail som ikke
+# g&aring;r under noget emne, blir ikke leveret.
+# 
+# Bemerk: Dette fungerer kun i normal-modus, ikke i sammendrag-modus.
+# 
+# Indholdet i len kan ogs&aring; unders&oslash;ges for Subject: og
+# Keyword: felter, alt efter hvad indstillingen topics_bodylines_limit
+# er sat til.
 #
-# legal values are:
-#    0 = "Disabled"
-#    1 = "Enabled"
+# gyldige værdier:
+#    0 = "Ikke tilgængelig"
+#    1 = "Tilgængelig"
 topics_enabled = 0
 
-# 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.
-# 
+# Her opgiver du hvor mange linier af mailens indhold som emnefilteret
+# skal s&oslash;ge igennem. En s&oslash;gning stopper n&aring;r s&aring;
+# mange linier er gennoms&oslash;gt, eller n&aring;r det m&oslash;der en
+# linie som ikke ser ud som et meddelelsesfelt. Ved at sætte denne til
+# null (0), vil ingen linier i indholdet blive unders&oslash;gt (dvs.
+# kun Keywords: og Subject: i meddelelseshovedet unders&oslash;ges). Ved
+# at sætte denne værdi til et negativt tal, vil alle linier blive
+# unders&oslash;gt frem til den f&oslash;rste linie som ikke ser ut som
+# et mailhoved-felt.
 topics_bodylines_limit = 5
 
-# 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.
+# Hvert emneord er faktisk et regexp-udtryk, der sammenlignes imod dele
+# af mailen, nemlig feltene Keywords: og Subject: i meldingshodet.
+# Bem&aelig;rk at de f&oslash;ste linier i mailens indhold ogs&aring;
+# kan best&aring; af s&aring;danne "felter", og kan dermed ogs&aring;
+# bli unders&oslash;gt.
 topics = []
 
diff --git a/mailman/nord-utte.py b/mailman/nord-utte.py
index 0628dfa..dc4055f 100644
--- a/mailman/nord-utte.py
+++ b/mailman/nord-utte.py
@@ -1,362 +1,386 @@
-## "nord-utte" mailing list configuration settings -*- python -*-
-## captured on Wed Mar 16 02:41:05 2005
+## Indstillinger for maillisten "nord-utte"  -*- python -*-
+## Dato: Thu May  5 09:52:42 2005
 
 ## General options
 #
-# 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 :-)
+# Grundlæggende egenskaber for listen, blant andet en beskrivelse af
+# listen, og hvordan den opf&oslash;rer sig.
+
+# Her kan du f.eks. stave navnet med stort forbogstav, eller ændre visse
+# bogstaver til store sådan at navnet kan udtales p&aring; en rigtig
+# m&aring;de eller at forkortelser fremhæves. Bemærk at dette navn
+# bruges i e-maillistens adresse (f.eks. i bekræftigelser ved
+# tilmeldinger), s&aring; der 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 :-)
 real_name = 'Nord-utte'
 
-# 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.
+# Der er to roller forbundet med hver mailliste. Listeadministratorene
+# 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.
+# 
+# Listemoderatorene har begrænset adgang; de kan ikke ændre
+# indstillinger for e-maillisten, men de kan tage sig af
+# foresp&oslash;rgsler i forbindlse med listen, f.eks. ans&oslash;gning
+# om medlemskab, eller godkende/afvise meddelelser der skal godkendes
+# for at kunne udsendes til listen. Listeadministratorene kan ogs&aring;
+# udf&oslash;re disse opgaver.
+# 
+# For at aktivere muligheden for at have listemoderatorer, og p&aring;
+# den m&aring;de opdele arbejdsopgaverne forbundet med listen, skal du
+# s&aelig;tte dit eget moderatorpassword, og angive din
+# e-mailadressen(e) til den/de som skal v&aelig;re listemoderator(er).
+# Bemærk at i tekstboksene nedenfor skal du skrive e-mailadressen(e) til
+# listeadministratoren(e).
 owner = ['dr@jones.dk']
 
-# 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.
+# Det er to ejerskab forbundet med hver mailliste. Listeadministratorene
+# er dem der har den endelige kontrol over alle indstillingerne for
+# e-mallisten. De kan &aelig;ndre alle indstillinger der er tilgengelige
+# via disse administrative websider.
+# 
+# Listemoderatorene har begr&aelig;nset adgang; de kan ikke &aelig;ndre
+# indstillinger for e-maillisten, men de kan tage sig af
+# foresp&oslash;rgsler ang&aring;ende listen, f.eks. ans&oslash;gning om
+# medlemskab, eller godkende/afvise meddelelser der skal godkendes for
+# at kunne udsendes p&aring; listen. Listeadministratorene kan selvsagt
+# ogs&aring; udf&oslash;re disse opgaver.
+# 
+# For at aktivere muligheten for at have listemoderatorer, og p&aring;
+# den m&aring;den opdele arbejdsopgaverne der er forbundet med listen,
+# skal du s&aelig;tte dit eget moderatorpassword, og indtaste din
+# e-mailadresse(r) til den/de der skal v&aelig;re listemoderator(er).
+# Bemærk at i tekstboksene nedenfor skal du skrive e-mailadressen(e) til
+# listemoderatoren(e).
 moderator = []
 
-# 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.
+# Denne beskrivelsen 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 gj&oslash;re det uklart
+# hvad meningen med maillisten er eller hvad den skal bruges til.
 description = 'Private list about Nord-utte website/intranet'
 
-# 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.
+# Teksten tolkes som html bortset fra linieskift, der vil blive
+# &aelig;ndret til html-tag'en '<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. Benytter du html-kode,
+# husk da at gennemse meget grundigt, for fejl (f.eks. manglende
+# slutt-tag's) kan f&oslash;re til at listens informationsside ikke vil
+# vises s&aring;dan som den skal.
 info = 'Private list about Nord-utte website/intranet'
 
-# 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 er sat ind foran emne-/tittelfeltet i e-mail der sendes
+# til listen, for at skille e-mailliste-meddelelser i e-mailboksen fra
+# dem der er medlem af listen. Denne tekst b&oslash;r holdes p&aring; et
+# absolut minimum, benytter du f.eks. listens navn og navnet er langt,
+# b&oslash;r du stave det endnu kortere her. Men den b&oslash;r fremover
+# v&aelig;re beskrivende for listen.
 subject_prefix = '[Nord-utte] '
 
-# Hide the sender of a message, replacing it with the list address
-# (Removes From, Sender and Reply-To fields)
+# Skjule afsenderen af meddelser, ved at erstatte den med e-maillistens
+# adresse (Dette medfører at alle From:, Sender, og Reply-To: felter
+# fjernes)
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 anonymous_list = 0
 
-# 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.
+# Skal eksisterende Reply-To: felt i meddelelseshovedet fjernes? Hvis ja
+# vil dette blive gjort uanset om Mailman tlføjer et Reply-To: felt
+# eller ikke.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 first_strip_reply_to = 0
 
-# 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.org/essays/reply-to-useful.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.
+# Denne indstillling fort&aelig;ller hvad Mailman skal gj&oslash;re med
+# Reply-To: feltet i meddelelseshovedet 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;dan 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 diskusion omkring
+# emnet. Se Reply-To Munging Considered Useful for modsatte meninger.
+# 
+# Nogle maillister har begr&aelig;nset adgang, med en egen parallell
+# liste beregnet til diskutioner. Eksempler p&aring; dette er 'patches'
+# eller 'checkin' lister, som system for revisionskontrol sender
+# &aelig;ndringer i programmet til, men diskusioner omkring udvikling af
+# programmet sendes til udviklerenes 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 diskusionsliste.
 #
-# legal values are:
-#    0 = "Poster"
-#    1 = "This list"
-#    2 = "Explicit address"
+# gyldige værdier:
+#    0 = "Afsender"
+#    1 = "mail listens adresse"
+#    2 = "Egendefineret adresse"
 reply_goes_to_list = 1
 
-# 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.org/essays/reply-to-useful.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.
+# 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 modifikasion af Reply-To:
+# adressen g&oslash;r det vanskeligere at sende svar kun til afsender.
+# Se 'Reply-To' Munging Considered Harmful for en diskusion omkring
+# temaet. Se Reply-To Munging Considered Useful for modsatte meninger.
+# 
+# Nogen maillister har begr&aelig;nset adgang, med en egen parallell
+# liste beregnet for diskusioner. Eksempler p&aring; dette er 'patches'
+# eller 'checkin' lister, som system for revisionskontrol sender
+# &aelig;ndringer til i programmet, men diskusioner rundt udvikling af
+# programmet sendes til udviklerenes egen mailliste. For at
+# st&oslash;tte s&aring;danne maillister, definer Reply-To: adressen
+# her, og vælg Egendefineret adresse i indstillingen reply_goes_to_list.
+# 
+# Bem&aelig;rk at hvis den oprindelige meddelse indeholder et Reply-To:
+# felt, vil det ikke &aelig;ndres.
 reply_to_address = ''
 
-# 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.
+# S&aelig;t denne til 'ja' hvis listen skal bruges som en "paraply" for
+# flere andre lister. N&aring;r denne er sat, vil bekr&aelig;ftigelser
+# og meddelelser med password blive sendt til en egen adresse som
+# beregnes ud fra e-mailadressen som er tilmeldt listen - v&aelig;rdien
+# af indstillingen "umbrella_member_suffix" bruges til dette. Denne
+# v&aelig;rdi tilf&oslash;jes til medlemmets kontonavn (det som
+# st&aring;r f&oslash;r @-tegnet).
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 umbrella_list = 0
 
-# 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".
+# N&aring;r "umbrella_list" indikerer at denne liste har andre
+# maillister som medlemmer, er det som regel &oslash;nskelig at
+# administrative meddelelser som f.eks. bekr&aelig;ftigelser og password
+# reminders ikke sendes til selve listen som er medlem, men til
+# administratoren for listen. Hvis dette er tilf&aelig;ldet, bruges
+# v&aelig;rdien af denne indstilling til at bestemme adressen sådan at
+# 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".
 umbrella_member_suffix = '-owner'
 
-# 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.
+# S&aelig;tt denne til hvis du vil have at password reminder skal sendes
+# til medlemmene en gang hver m&aring;ned. Husk at medlemmene kan
+# ogs&aring; selv frav&aelig;lge dette.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 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.
+# Tekst du skriver her vil blive tilf&oslash;jet &oslash;verst i
+# velkomsthilsenen der sendes til nye medlemmer. Velkomshilsenen
+# indeholder allerede viktige adresser og URLer knyttet til maillisten,
+# s&aring; sådan information er det ikke n&oslash;dvendig at inkludere
+# her. Her kan du indl&oslash;gge f.eks. oplysning om etikette eller
+# regler for brug af listen, o.l.
+# 
+# Bem&oslash;rk: Liniene i denne tekst vil brydes efter f&oslash;lgende
+# regler:
 # 
-# 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.
+# Hvert afsnit udfyldes s&aringdan at ingen linie er lenger en 70 tegn.
+# Enhver linie der begynder med blanke tegn udfyldes ikke. Blanke linier
+# adskiller afsnitt.
 # 
 welcome_msg = ''
 
-# 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.
+# S&aelig;t kun denne til 'Nej' hvis du skal il&aelig;gge nye medlemmer
+# manuelt, og ikke vil have de skal f&aring; dette 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.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 send_welcome_msg = 1
 
-# Text sent to people leaving the list.  If empty, no special text will
-# be added to the unsubscribe message.
+# Tekst der sendes til medlemmer der framelder sig fra listen. Hvis
+# denne er tom, l&aelig;gges det ikke noget tekst til frameldelsen.
 goodbye_msg = ''
 
-# Send goodbye message to members when they are unsubscribed?
+# Sende afskedshilsen til medlemmer n&aring;r de frameldes?
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 send_goodbye_msg = 1
 
-# 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.
+# Der udsendes en reminder til listemoderatoren(e) (og
+# listeadministratoren(e)) dagligt om foresp&oslash;rsler der af en
+# eller anden grund venter p&aring; behandling. V&aelig;lger du "Ja",
+# vil listeadminstratoren ogs&aring; motdtage en meddelelse s&aring;
+# snart en foresp&oslash;rsel kommer ind.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 admin_immed_notify = 1
 
-# Should administrator get notices of subscribes and unsubscribes?
+# Skal listeadministratoren(e) ogs&aring; modtage meddelelse om nye
+# medlemmer der tilmelder sig og gamle medlemmer som framelder sig?
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 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.
+# Besked om at en meddelelse skal godkendes sendes ud til afsenderen
+# s&aring;fremt meddelelsen stoppes pga. noget andet end listemoderation
+# eller spam filtre. S&aelig;ttes denne indstilling til 'Nej', vil
+# afsender overhovedet ikke modtage denne besked.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 respond_to_post_requests = 1
 
-# 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.
+# Når dette valg er aktiveret, vil alt e-mail til listen blive moderert.
+# 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-moderasjon" kan da hjælpe dig at fjerne usaglige meddelelser
+# til listen, og på den måden dysse en ophedet diskusion ned.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 emergency = 0
 
-# When a new member is subscribed to this list, their initial set of
-# options is taken from the this variable's setting.
+# Når et nyt medlem tilmeldes listen, blir medlemmets indstillinger
+# taget herfra.
 new_member_options = 256
 
-# 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.
+# Filter for administrative meddelelser vil unders&oslash;ge om
+# meddelelsen egentligt er ment som en administrativ foresp&oslash;rgsel
+# (f.eks. tilmelding, framelding, o.l.), og is&aring;fald sende
+# meddelelsen til administratoren i stedet.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 administrivia = 1
 
-# Maximum length in kilobytes (KB) of a message body.  Use 0 for no
-# limit.
+# Maximum st&oslash;rrelse i kilobytes (KB) for indholdet i e-mail der
+# sendes til listen. Brug verdien '0' for ikke at have en
+# begr&aelig;nsning.
 max_message_size = 200
 
-# 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.
+# "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; denne maskinen. Denne
+# indstillingen kan v&aelig;re nyttig hvis maskinen har flere navne.
 host_name = 'jones.dk'
 
-# 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).
+# I RFC 2369 defineres en r&aelig;kke List-* felter i
+# meddelelseshovedet, der normalt tilf&oslash;jes hver meddelelse der
+# sendes ud via listen. Disse felter kan hj&aelig;lpe de brugere af
+# listen der benytter et e-mailprogram som f&oslash;lger denne standard.
+# Disse felter b&oslash;r derfor altid v&aelig;re med.
+# 
+# Ikke alle e-mailprogrammer f&oslash;lger denne standard. Er det mange
+# af medlemmene p&aring; listen der benytter s&aring;danne
+# e-mailprogrammer, der ikke kan h&aring;ndtere disse felter i
+# meddelelseshovedet, kan det v&aelig;re du vil v&aelig;lge at udelade
+# dem. Men du b&oslash;r f&oslash;rst fors&oslash;ge at l&aelig;re og
+# forklare medlemmene 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 disse felter, men dette anbefales ikke (denne
+# muligheten kan faktisk ogs&aring; blive fjernet i senere versioner).
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 include_rfc2369_headers = 1
 
-# 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.)
+# List-Post: feltet er et af felterne anbefalet i RFC 2369. Visse
+# e-maillister (som f.eks. kun bruges til offentligørelser), er det kun
+# visse personer der har lov til at sende til; de som er medlem af
+# listen har generelt ikke lov til at sende til listen. For disse
+# lister, er List-Post: feltet forvirrende. I visse tilf&aelig;lde kan
+# det være forvirrende at s&aelig;tte denne indstilling til Nej,
+# s&aring; feltet ikke tilføjes. (Dette påvirker ikke andre List-*:
+# felter.)
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 include_list_post_header = 1
 
 ## Language options
 #
-# 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.
+# Underst&oslash;ttelse for flere sprog. (Internationalisering)
+
+# Dette er standardsproget som benyttes for denne mailliste. Hvis mer
+# 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.
 preferred_language = 'en'
 
-# These are all the natural languages supported by this list. Note that
-# the default language must be included.
+# Her er alle spr&aring;gene denne listen har underst&oslash;ttelse for.
+# Bem&aelig;rk at standardsproget skal v&aelig;re med.
 available_languages = ['en', 'da']
 
-# 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.
+# Hvis standardsproget for din mailliste benytter et andet tegns&aelig;t
+# end ASCII og tittel prefixet for listen indeholder tegn som ikke
+# findes i ASCII-tegns&aelig;ttet, vil prefixet alltid blive kodet i
+# henhold til den relevante standard. Hvis tittel prefixet kun
+# indeholder ASCII tegn, kan det imidlertid ske at du ønsker at sætte
+# dette valg til Aldrig for at undgå koding. Dette kan gøre titlen lidt
+# mere læselig for brugere med e-mailprogrammer der ikke takler andre
+# tegnsæt end ASCII på en rigtig måde.
+# 
+# Bemærk imidlertid at hvis din mailliste modtager både kodede og
+# ukodede tittel felt, kan det være bedst at vælge Efter behov. Med
+# denne indstilling vil Mailman ikke kode ASCII prefixer hvis resten af
+# tittelfeltet kun indeholder ASCII tegn, men vil kode prefixet hvis det
+# indeholder tegn som ikke er ASCII tegn. På denne måde undgås en [...]
+# i standarderne, som forårsager at visse e-mailprogrammer vil vise
+# ekstra eller manglende mellemrum imellom tittel prefixet og det
+# oprindelige tittelfelt.
 #
-# legal values are:
-#    0 = "Never"
-#    1 = "Always"
-#    2 = "As needed"
+# gyldige værdier:
+#    0 = "Aldrig"
+#    1 = "Altid"
+#    2 = "Efter behov"
 encode_ascii_prefixes = 0
 
 ## Nondigest options
 #
-# Policies concerning immediately delivered list traffic.
+# Regler for levering i normal-modus.
 
-# Can subscribers choose to receive mail immediately, rather than in
-# batched digests?
+# Kan medlemmer vælge normal-modus?
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 nondigestable = 1
 
-# 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:
+# 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:
 # 
 # 
 # real_name - The "pretty" name of the list; usually the list name with
@@ -381,9 +405,10 @@ nondigestable = 1
 # 
 msg_header = ''
 
-# 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:
+# Tekst som tilf&aelig;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:
 # 
 # 
 # real_name - The "pretty" name of the list; usually the list name with
@@ -413,42 +438,44 @@ msg_footer = """_______________________________________________
 
 ## Digest options
 #
-# Batched-delivery digest characteristics.
+# Opsætning af sammendrag-modus.
 
-# Can list members choose to receive list traffic bunched in digests?
+# Kan medlemmer af listen vælge at f&aring; tilsendt sammendrag i stedet
+# for?
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 digestable = 1
 
-# Which delivery mode is the default for new users?
+# Hvilken modus er standard for nye brugere?
 #
-# legal values are:
-#    0 = "Regular"
-#    1 = "Digest"
+# gyldige værdier:
+#    0 = "Normal"
+#    1 = "Sammendrag"
 digest_is_default = 0
 
-# When receiving digests, which format is default?
+# Hvilket format skal benyttes som standard for samle-email?
 #
-# legal values are:
-#    0 = "Plain"
+# gyldige værdier:
+#    0 = "Ren tekst"
 #    1 = "MIME"
 mime_is_default_digest = 0
 
-# How big in Kb should a digest be before it gets sent out?
+# Hvor stor (i Kb) m&aring; en samle-email h&oslash;jst v&aelig;re
+# f&oslash;r den udsendes?
 digest_size_threshhold = 30
 
-# Should a digest be dispatched daily when the size threshold isn't
-# reached?
+# Skal der sendes en samle-email dagligt, selv om st&oslash;rrelsen ikke
+# er opn&aring;et?
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 digest_send_periodic = 1
 
-# Text attached (as an initial message, before the table of contents) to
-# the top of digests. This text can include Python format strings which
+# Tekst som l&aelig;gges til &oslash;verst i samle-emailen, f&oslash;r
+# indholdsfortegnelsen.This text can include Python format strings which
 # are resolved against list attributes.  The list of substitutions
 # allowed are:
 # 
@@ -475,9 +502,10 @@ digest_send_periodic = 1
 # 
 digest_header = ''
 
-# 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:
+# Tekst der tilføjes nederst i hver samle-e-mail, som sidste
+# information.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
@@ -505,274 +533,277 @@ digest_footer = """_______________________________________________
 %(real_name)s@%(host_name)s
 %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s"""
 
-# When a new digest volume is started, the volume number is incremented
-# and the issue number is reset to 1.
+# N&aring;r et nyt volume startes, &oslash;ges volume nummeret, og
+# udgavenummeret s&aelig;ttes til 1.
 #
-# legal values are:
-#    0 = "Yearly"
-#    1 = "Monthly"
-#    2 = "Quarterly"
-#    3 = "Weekly"
-#    4 = "Daily"
+# gyldige værdier:
+#    0 = "&Aring;rlig"
+#    1 = "M&aring;nedlig"
+#    2 = "Kvartalsvis"
+#    3 = "Ugentlig"
+#    4 = "Daglig"
 digest_volume_frequency = 1
 
 ## Privacy options
 #
-# 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/nord-utte/archive">Archival 
-# Options</a> section for separate archive-related privacy settings.
-
-# Advertise this list when people ask what lists are on this machine?
+# Her kan du bestemme hvad der kr&oslash;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/nord-utte/archive">Indstillinger 
+# for arkivering</a> for egne indstillinger n&aring;r det g&oslash;lder
+# arkivet og arkivering.
+
+# Vise denne mailliste n&aring;r nogn beder om at se en oversigt over
+# maillister p&aring; denne maskine?
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 advertised = 1
 
-# 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.
+# bek&aelig;ftigelse(*) - bekr&aelig;ftigelse af e-mail er
+# n&oslash;dvendig godkendelse - ans&oslash;gkning om medlemskabp skal
+# godkendes af listeadministrator (eller evt. listemoderator)
+# bekr&aelig;ftigelse+godkendelse - b&aring;de bekr&aelig;ftelse
+# p&aring; e-mail og godkendelse af listeadministrator (evt.
+# listemoderator) er nun&oslash;dvendig
+# 
+# (*) n&aring;r nogen vil tilmelde sig en liste, sender Mailman en
+# meddelelse med et uniktidentifikator som de skal opgive for at
+# bekr&oslash;fte tilmeldingen. P&aring; denne m&aring;den vil det da
+# ikke v&aelig;re muligt at tilmelde nogen til listen imod deres vilje.
 #
-# legal values are:
-#    1 = "Confirm"
-#    2 = "Require approval"
-#    3 = "Confirm and approve"
+# gyldige værdier:
+#    1 = "Bekr&aelig;ftigelse"
+#    2 = "Godkendelse"
+#    3 = "Bekr&aelig;ftigelse og godkendelse"
 subscribe_policy = 2
 
-# 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.
+# N&aring;r medlemmer &oslash;nsker at forlade en mailliste, sender de
+# en ans&oslash;gning om framelding, enten via web, eller via e-mail.
+# Normalt er det best at disse ans&oslash;gninger automatisk godkendes,
+# s&aring; meldemmer kan udmelde sig n&aring;r de &oslash;nsker det
+# (mange &oslash;nsker selv at kunne administrere en frameldelse. For
+# nogen f&aring; maillister kan det aligevel v&aelig;re aktuelt at have
+# kontrol over om medlemmer kan melde sig selv ud eller ikke. En liste
+# som alle ansatte i et firma M&Aring; v&aelig;re medlem af, er et
+# eksempel p&aring; en s&aring;dan liste.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 unsubscribe_policy = 0
 
-# 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.
+# Alle e-mailadresser som angives her vil blive udelukket fra listen, og
+# kan ikke tilmelde sig. Indtast e-mailadresser, en per linie, start
+# linien med tegnet ^ for at angive et regexp-udtryk der skal passe med
+# afsenderadressen.
 ban_list = []
 
-# When set, the list of subscribers is protected by member or admin
-# password authentication.
+# Hvis denne indstilling er sat til, vil listen over medlemmer af
+# e-maillisten blive beskyttet af medlemmenes eller adminstratorens
+# password.
 #
-# legal values are:
-#    0 = "Anyone"
-#    1 = "List members"
-#    2 = "List admin only"
+# gyldige værdier:
+#    0 = "Alle"
+#    1 = "Kun medlemmer af listen"
+#    2 = "Kun listeadministrator"
 private_roster = 1
 
-# 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.
+# V&aelig;lger du 'Ja' her, vil medlemmers e-mailadresse omskrives
+# n&aring;r de vises i en oversigt p&aring; websidene (b&aring;de som
+# tekst og i linker), s&aring; de ikke er nemme at tolke som
+# e-mailadresser. Meningen med dette er at undg&aring; at e-mailsniffere
+# der gennemg&aring;r websider for at finde e-mailadresser (og derefter
+# bruge dem til at udsende spam/junk mail) til ikke at opsamle
+# medlemmenes e-mailadresser.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 obscure_addresses = 0
 
 ## Privacy options
 #
-# 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.
+# N&aring;r en meddelelse sendes til maillisten, g&aring;r den igennem
+# en r&aelig;kke trin for at afg&oslash;re om moderatoren m&aring;
+# godkende meddelelsen eller ikke. Her finder du indstillinger for 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 de sendes til listen.
+# 
+# <p>e-mail som ikke er sendt af medlemmer af listen, kan automatisk bli
+# <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">sendt
+# retur</a>, eller <a
+# href="?VARHELP=privacy/sender/discard_these_nonmembers">afvist</a>,
+# enten individuelt eller som en gruppe. All e-mail fra ikke-medlemmer,
+# som ikke specifikt bliver godkent, sendes retur, eller afvist, 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 il&aelig;gger du en e-mailadresse per
+# linie. Du kan ogs&aring; il&aelig;gge  <a
+# href="http://www.python.org/doc/current/lib/module-re.html">Python
+# regexp-uttrykk</a>. Begynd is&aring;fald linien med tegnet ^ for at
+# markere at det er et s&aring;dan udtryk. N&aring;r du benytter
+# backslash, skriv da lige som i rene strings (Python raw strings)
+# (normalt kun &eacute;n backslash af gangen).
+# 
+# <p>Bem&aelig;rk: match p&aring; 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-mail fra medlemmet kan sendes direkte til e-maillisten, eller om de
+# f&oslash;rst skal godkendes af listemoderatoren. N&aring;r
+# moderationsflaget er sat til, skal e-mail fra medlemmet godkendes af
+# listemoderatoren f&oslash;r det udsendes til alle p&aring; listen. Som
+# listeadminsitrator kan du for hvert enkelt medlem bestemme om
+# medlemmets e-mail skal modereres eller ikke. N&aring;r et nyt medlem
+# tilmeldes til 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
+# Administrere medlemmer siden.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 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.
 # 
-# Discard -- this simply discards the message, with no notice sent to
-# the post's author.
+# Holde tilbage -- meldingen holdes tilbage for godkendelse af
+# listemoderatoren(e). Afslå -- meldingen sendes automatisk retur til
+# afsender. Begrundelsen der sendes kan du skrive selv Slette --
+# meddelelsen blir afvist uden at give besked om dette til afsender.
 # 
 #
-# legal values are:
-#    0 = "Hold"
-#    1 = "Reject"
-#    2 = "Discard"
+# gyldige værdier:
+#    0 = "Holde&nbsp;tilbage"
+#    1 = "Afvis"
+#    2 = "Kassere"
 member_moderation_action = 0
 
-# 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.
+# Tekst som skal sendes med meldingen om retur som sendes til modereede
+# medlemmer af listen.
 member_moderation_notice = ''
 
-# 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.
+# e-mail fra disse ikke-medlemmer vil automatisk blive godkendt.
+# Il&aelig;g e-mailadresser, en per linie, start linien med tegnet ^ for
+# at angive et regexp-uttryk som skal passe med afsenderadressen.
 accept_these_nonmembers = []
 
-# 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.
+# e-mail fra disse ikke-medlemmer vil automatisk blive holdt tilbage for
+# vurdering af listemoderatorene. Afsenderen vil modtage en meddelelse
+# om dette, med bl.a. instruktioner om hvordan han/hun kan
+# tilbagetr&aelig;kke sin e-mails. Indtast e-mailadresser, en per linie,
+# start linien med tegnet ^ for at angive et regexp-uttrykk som skal
+# passe med afsenderadressen.
 hold_these_nonmembers = []
 
-# 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.
+# 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 spam-afsendere,
+# de b&oslash;r automatisk afvises. Indtast e-mailadresser, en per
+# linie, start linien med tegnet ^ for &aring; angiv et regexp-uttrykk
+# som skal passe med afsenderadressen.
 reject_these_nonmembers = []
 
-# 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.
+# e-mail fra disse ikke-medlemmer vil automatisk blive afvist. Det vil
+# sige at meddelelsen afvises uden nogen form for tilbagemelding, men
+# listemoderatorene kan (om ønskeligt) modtage en kopi af den afviste
+# e-mail. Tilf&oslash;je e-mailadresser, en per linie, start linien med
+# tegnet ^ for at angive et regexp-uttryk der skal passe med
+# afsenderadressen.
 discard_these_nonmembers = []
 
-# 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.
+# N&aring;r en e-mail fra et ikke-medlem blir modtaget, sammenlignes
+# e-mailens afsender med listen over e-mailadresser der skal godkendes,
+# holdes tilbage, afvises (sendes i retur), og afvises. Hvis
+# afsenderadressen ikke passer med den der er opgivet i listene, blir
+# f&oslash;lgende afg&oslash;relse taget.
 #
-# legal values are:
-#    0 = "Accept"
-#    1 = "Hold"
-#    2 = "Reject"
-#    3 = "Discard"
+# gyldige værdier:
+#    0 = "Godkende"
+#    1 = "Holde&nbsp;tilbage"
+#    2 = "Afvis"
+#    3 = "Kassere"
 generic_nonmember_action = 0
 
-# Should messages from non-members, which are automatically discarded,
-# be forwarded to the list moderator?
+# Skal meddelelser fra ikke-medlemmer, som automatisk afvises, også
+# sendes til listemoderatoren?
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 forward_auto_discards = 1
 
 ## Privacy options
 #
-# This section allows you to configure various filters based on the
-# recipient of the message.
+# Her kan du ops&aelig;tte filtrering baseret på modtaeren af
+# meddelelsen.
 
-# 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.
+# Meget (faktisk det meste af) spam/junk mail har ikke de endelige
+# modtagere i modtagerfelterne. Faktisk s&aring; indeholder felterne To:
+# og/eller Cc: oftest en fuldst&aelig;ndig 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(e), men vil
+# aligevel blive fanget og blokkere det meste af spam/junk mail.
 # 
-# 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 ville 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
+# alias for listen.
 # 
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 require_explicit_destination = 0
 
-# 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.
+# Alternative e-mailadresser som godtages n&aring;r
+# 'require_explicit_destination' er sat til. Som v&aelig;rdi for denne
+# indstilling skal du opgive regexp-uttryk ("regular expressions"), et
+# udtryk per linie, der sammenlignes imod 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 imod den f&oslash;rste
+# del (det som st&aring;r f&oslash;r '@') af modtageradressen. Hvis
+# sammenligningen ikke lykkes, eller hvis udtrykket ikke indholder en
+# '@', sammenlignes udtrykket med hele modtageradressen.
+# 
+# Sammenligning kun imod den f&oslash;rste del af en modtageradresse
+# underst&oslash;ttes ikke i fr&aelig;mtidige udgaver af Mailman, vil
+# kun sammenligning imod hele modtageradresser blive
+# underst&oslash;ttet.
 acceptable_aliases = ''
 
-# If a posting has this number, or more, of recipients, it is held for
-# admin approval.  Use 0 for no ceiling.
+# Hvis en mail der er sendt til listen indeholder s&aring; mange
+# modtagere som, eller flere modtagere end, denne værdi, holdes malen
+# tilbage så listeadministratoren eventuelt kan godkende den. Brug
+# værdien 0 for ingen begrænsning.
 max_num_recipients = 20
 
 ## Privacy options
 #
-# 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.
-# 
+# Her kan du opsætte forskellige anti-spam filtre, som kan være til
+# hjælp for 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
@@ -785,16 +816,20 @@ max_num_recipients = 20
 # match.
 header_filter_rules = []
 
-# 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.
+# Brug denne indstilling til at fra-filtrere mail til listen, baseret
+# p&aring; indholdet af et eller flere felter i mailhovedet. Her skal du
+# skrive regexp-uttryk (regular expressions), et per linie, som
+# sammenlignes mod det aktuelle felt. Sammenligningen sk&aelig;lner ikke
+# imellem store og sm&aring; bogstaver. Linier der begynder med '#'
+# sammenlignes ikke.
 # 
-# For example:to: .*@public.com  says to hold all postings with a To:
-# mail header containing '@public.com' anywhere among the addresses.
+# For eksempel: udtrykket to: .*@public.com fort&aelig;ller at alt mail
+# som indeholder '@public.com' i To: feltet, skal holdes tilbage til
+# godkendelse.
 # 
-# 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.
+# Bem&aelig;rk: blanke tegn i starten af regexp-udtrykket fjernes. Dette
+# kan man undg&aring; p&aring; flere m&aring;ter, f.eks. ved at bruge
+# escape-tegn eller parenteser.
 bounce_matching_headers = """# Lines that *start* with a '#' are comments.
 to: friend@public.com
 message-id: relay.comanche.denmark.eu
@@ -803,54 +838,56 @@ from: .*@uplinkpro.com"""
 
 ## Bounce options
 #
-# 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.
+# Disse regler bestemmer hvordan automatisk behandling af returmails
+# gj&oslash;res. Her er en oversigt over hvordan funktionen er.
+# 
+# <p>N&aring;r Mailman modtager en returmail, blir to ting
+# fors&oslash;kt tolket. Det ene er e-mailadressen til medlemmet som
+# egentlig skulle modtage e-mailen, og det andet er &aring;rsagen til
+# problemet. &Aring;rsagen tolkes til at v&aelig;re <em>alvorlig</em>
+# eller <em>lett</em> alt efter om &aring;rsagen er af kritisk eller af
+# mindre alvorlig art. Såfremt der er tvivl, tolkes &aring;rsaken som
+# alvorlig.
+# 
+# <p>Hvis ingen e-mailadresse kan hentes ud af meddelelsen, blir den
+# normalt afvist. Ellers, vil medlemmet som har e-mailadressen f&aring;
+# en <em>returtal</em>, og hver gang en returmeddelelse kommer vil
+# tallet &oslash;ges. Alvorlige &aring;rsaker f&oslash;rer til at tallet
+# &oslash;ges med 1, lette &aring;rsaker f&oslash;rer til at det
+# &oslash;kes med 0.5. Dette sker kun &eacute;n gang per dag, s&aring;
+# selv om det 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;ttest til igen.
+# Medlemmet vil med j&aelig;vne mellemrum modtage melding 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>Det er en vigtig indstilling til; efter en vis tid -- hvis ingen
+# returmeddelelser dukker op i l&oslash;bet af denne tid -- anses
+# returinformation som <a
+# href="?VARHELP=bounce/bounce_info_stale_after">udg&aring;et</a> og
+# afvises. Ved at justere denne værdi, og sætte en grænse for
+# returantallet, kan du bestemme hvor lang tid der skal gå f&oslash;r
+# levering til et medlem stoppes. Begge disse værdier skal du justere
+# alt efter hvor ofte og hvor meget e-mail der sendes til din liste.
+
+# Ved at sætte denne værdi til Nej, sætter du alt automatisk tolking af
+# returmeddelelser for denne liste fra. Bemærk at såfremt meddelelser
+# afvises vil listeadministratoren ikke blive forstyrret med dem.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 bounce_processing = 1
 
 # Each subscriber is assigned a bounce score, as a floating point
@@ -866,351 +903,345 @@ bounce_processing = 1
 # mailing list.
 bounce_score_threshold = 5.0
 
-# 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.
+# Antal dage f&oslash;r returinformation afvises såfremt der ikke dukker
+# flere returmails op. Dette tal skal v&aelig;re et heltal.
 bounce_info_stale_after = 7
 
-# 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.
+# Hvor mange Levering til dig er stoppet advarsler der skal sendes til
+# et medlem f&oslash;r medlemmet frameldes fra listen. S&aelig;t denne
+# værdi til 0 for at fjerne et medlem fra listen umiddelbart
+# s&aring;fremt der kommer returmails fra medlemmets e-mailadresse.
+# Dette tal skal være et heltal.
 bounce_you_are_disabled_warnings = 3
 
-# The number of days between sending the Your Membership Is Disabled
-# warnings.  This value must be an integer.
+# Antal dage imellem hver gang en Levering til dig er stoppet advarsel
+# skal sendes ud. Dette tal skal være et heltal.
 bounce_you_are_disabled_warnings_interval = 7
 
-# 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.
+# Mailmans automatiske returmailhåndtering er meget robust, men det er
+# aligevel umuligt at genkende alle typer returmails der kommer. Du bør
+# angive Ja her, af to grunde: 1) Hvis det virkelig er en permanent
+# returmail fra et medlem af listen, bør du antageligt manuelt udmelde
+# medlemmet fra listen, og 2) du vil måske sende meddelelse til
+# udviklerne af Mailman sådan at returmails automatisk genkendes af
+# Mailman i senere versioner. Hvis du ikke vil gøre nogen af delene, sæt
+# da denne indstilling til Nej. Så vil alle returmails afvises
+# automatisk uden videre behandling. Bem&aelig;rk: Denne indstilling vil
+# også indvirke på alt e-mail der sendes til listens -admin adresse. Den
+# adresse er gammel og udgået, men det kan være at nogen fortsat vil
+# sende e-mail til den. Hvis nogen gør det, og du har sat denne
+# indstilling til Nej, vil disse mails også blive afvist. Måske vil du
+# også opsætte et automatisk svar på e-mail sendt til -owner og -admin
+# adresserne.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 bounce_unrecognized_goes_to_list_owner = 1
 
-# 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.
+# Ved at sætte denne til Nej, fravælges beskeden der normalt sendes til
+# ejeren(e) af listen, når afsending 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.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 bounce_notify_owner_on_disable = 1
 
-# 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.
+# Ved at sætte denne til Nej, fravælges beskeden der normalt sendes til
+# ejeren(e) af listen, når et medlem frameldes fra listen på grund af
+# for mange returmails. Der vil til gengæld altid blive forsøgt afsendt
+# en e-mail med besked til medlemmet.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 bounce_notify_owner_on_removal = 1
 
 ## Archive options
 #
-# List traffic archival policies.
+# Regler for arkivering
 
-# Archive messages?
+# Arkivere e-mail i et arkiv?
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 archive = 1
 
-# Is archive file source for public or private archival?
+# Skal filen arkiveres i et privat eller i et offentlig arkiv?
 #
-# legal values are:
-#    0 = "public"
-#    1 = "private"
+# gyldige værdier:
+#    0 = "offentlig"
+#    1 = "privat"
 archive_private = 1
 
-# How often should a new archive volume be started?
+# Hvor ofte skal arkivet deles op?
 #
-# legal values are:
-#    0 = "Yearly"
-#    1 = "Monthly"
-#    2 = "Quarterly"
-#    3 = "Weekly"
-#    4 = "Daily"
+# gyldige værdier:
+#    0 = "&Aring;rlig"
+#    1 = "M&aring;nedlig"
+#    2 = "Kvartalsvis"
+#    3 = "Ugentlig"
+#    4 = "Daglig"
 archive_volume_frequency = 1
 
 ## Gateway options
 #
-# Mail-to-News and News-to-Mail gateway services.
+# e-mail-Til-Nyhedsgruppe og Nyhedsgruppe-Til-e-mail tjeneste.
 
-# 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.
+# 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.
 nntp_host = ''
 
-# The name of the Usenet group to gateway to and/or from.
+# Navn p&aring; nyhedsgruppe der skal sendes til og/eller fra.
 linked_newsgroup = ''
 
-# Should new posts to the mailing list be sent to the newsgroup?
+# Skal nye mail til denne liste sendes til nyhedsgruppen?
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 gateway_to_news = 0
 
-# Should new posts to the newsgroup be sent to the mailing list?
+# Skal nye meddelelser til nyhedsgruppen sendes til denne mailliste?
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 gateway_to_mail = 0
 
-# 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.
+# 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&aring;t da 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
+# Moderet, vil en ekstra meddelelse holdes tilbage i
+# godkendelsesprocessen. Alt mail sendt til maillisten skal godkendes
+# f&oslash;r de sendes til nyhedsgruppen, eller til medlemmene af
+# listen.
+# 
+# Vær opm&aelig;rksom p&aring; at hvis mailhovedet i mailen har et
+# Approved: felt med listens administrative password, 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 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 meddelelseshovedet.
 #
-# legal values are:
-#    0 = "None"
-#    1 = "Open list, moderated group"
-#    2 = "Moderated"
+# gyldige værdier:
+#    0 = "Ingen"
+#    1 = "Åben liste, modereret nyhedsgruppe"
+#    2 = "Modereret"
 news_moderation = 0
 
-# 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.
+# Mailman tilføjer normalt en tekst du selv 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 sette denne indstilling
+# til Nej hvis du ikke ønsker emne prefix tilføjet til mail som sendes
+# til Usenet. Sætter du emne prefix for listen til off, vil opsamlet
+# meddelelser heller ikke få præfix tilføjet.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 news_prefix_subject_too = 1
 
 ## Autoreply options
 #
-# Auto-responder characteristics.<p>
+# Indstillinger for automatiske svar.<p>
 # 
-# 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>
+# 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 epostadresse</em>
+# <li><b>owneremail</b> - <em>listens -owner epostadresse</em> </ul>
 # 
-# <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.
+# <p>Du kan enten skrive teksten direkte i tekstboksene, eller du kan
+# angive navnet p&aring; en fil som indeholder teksten. Denne file vil
+# s&aring; blive indl&aelig;st i tekstboksen, fra dit lokale filsystem.
 
-# Should Mailman send an auto-response to mailing list posters?
+# Skal Mailman sende et automatisk svar til dem der sender e-mail til
+# listen?
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 autorespond_postings = 0
 
-# Auto-response text to send to mailing list posters.
+# Automatisk svar der skal sendes.
 autoresponse_postings_text = ''
 
-# Should Mailman send an auto-response to emails sent to the -owner
-# address?
+# Skal Mailman sende et automatisk svar p&aring; e-mail der sendes til
+# -owner adressen?
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 autorespond_admin = 0
 
-# Auto-response text to send to -owner emails.
+# Automatisk svar p&aring; e-mail til -owner adressen.
 autoresponse_admin_text = ''
 
-# 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.
+# 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
+# ogs&aring; skal v&aelig;re med i det automatiske svar.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes, w/discard"
-#    2 = "Yes, w/forward"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja, men uden den originale e-mailn"
+#    2 = "Ja, og medtag den originale e-mail"
 autorespond_requests = 0
 
-# Auto-response text to send to -request emails.
+# Automatisk svar p&aring; e-mail til -request adressen.
 autoresponse_request_text = ''
 
-# 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).
+# Antal dage imellem automatisk svar p&aring; e-mail, fra samme
+# afsender, til listen eller til -request/-owner adressene. S&aelig;t
+# denne v&aelig;rdi til 0 (eller et negativt tal) for at sende
+# automatisk svar hver gang.
 autoresponse_graceperiod = 90
 
 ## Contentfilter options
 #
-# 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.  Then, each
-# <tt>multipart/alternative</tt> section will be replaced by just the
-# first alternative that is non-empty after filtering.
-# 
-# <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?
+# Regler for indhold i e-mail sendt til listen.
+# 
+# <p>Filtrering af indhold fungerer således: når listen modtger en
+# e-mail og du har beskyttelse med filtrering af indhold, sammenlignes
+# først eventuelle ved- hæftelser imod <a
+# href="?VARHELP=contentfilter/filter_mime_types">MIME filtre</a>. Hvis
+# en vedhæftelse passer med et af disse filtre, blir vedhæftelsen
+# fjernet.
+# 
+# <p>Derefter sammenlignes eventuelle vedhæftelser imod <a
+# href="?VARHELP=contentfilter/pass_mime_types">gyldige MIME typer</a>,
+# hvis nogen er defineret. Alle vedhæftelser som ikke passer med de
+# angivne MIME typene, blir fjernet.
+# 
+# <p>Efter disse filtre, vil alle tomme <tt>multipart</tt> vedhæftelser
+# blive fjernet. Hvis selve meddelelsen er helt tom efter denne
+# filtrering, vil meddelelsen bli afvist. Derefter vil hvert
+# <tt>multipart/alternative</tt> vedhæftelse blive erstattet af det
+# første alternative som ikke er tomt.
+# 
+# <p>Til slut vil alle <tt>text/html</tt> vedhæftelser som måtte være
+# tilbage i meddelelsen blive konverteret til <tt>text/plain</tt>
+# såfremt <a
+# href="?VARHELP=contentfilter/convert_html_to_plaintext">konvertere til
+# ren tekst</a> er sat til og serveren er konfigurert til at tillade
+# sådanne konverteringer.
+
+# Skal Mailman filtrere indhold i e-mail sendt til listen som angivet
+# nedenfor?
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 filter_content = 0
 
-# 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.
+# Brug denne instilling til at fjerne vedhæftelser der passer til MIME
+# typer. Hver linie skal her indeholde navnet på en MIME type/subtype,
+# f.eks. image/gif. Såfremt du ønsker at fjerne alle vedhæftelser som
+# har en given hoved MIME type, kan du lade være at angive subtype,
+# f.eks. image.
 # 
-# Blank lines are ignored.
+# Blanke linier medtages ikke.
 # 
-# See also <a href="?VARHELP=contentfilter/pass_mime_types"
-# >pass_mime_types for a content type whitelist.
+# Se også gyldige MIME typer for whitelist af MIME typer.
 filter_mime_types = ''
 
-# 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.
+# Brug denne indstilling for at definere hvilke MIME typer der skal være
+# tilladt. Krav og format for filtrering er identisk med MIME filtre.
 # 
-# 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.
+# Bem&aelig;rk: hvis du lægger noget ind her, men ikke angiver
+# multipart, vil al e-mail med vedhæftelser ikke blive medtaget.
 pass_mime_types = """multipart/mixed
 multipart/alternative
 text/plain"""
 
-# Should Mailman convert text/html parts to plain text?  This conversion
-# happens after MIME attachments have been stripped.
+# Skal Mailman konvertere text/html dele til ren tekst? Denne
+# konvertering vil finde sted efter at MIME filteret har fjernet de
+# ønskede dele.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 convert_html_to_plaintext = 1
 
-# One of these actions is take 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.
+# Her bestemmer du hvad der skal ske når en meddelelse filtreres fra af
+# et filter, altså såfremt vedhæftelsen filtreres fra MIME filteret,
+# eller ent vedhæftelse ikke har en af de gyldige MIME typer, eller
+# meddelelsen ender op med at være tom efter filtrering.
+# 
+# Bemærk at det du vælger her ikke vil ske såfremt en meddelelse stadig
+# indeholder noget efter filtrering. Så vil meddelelsen altid sendes
+# videre til listen.
+# 
+# Når meddelelsen afvises, skrives Message-ID'en til den afviste
+# meddelelse til loggen. Når meddelelsen sendes retur eller videresendes
+# til listens ejer, vil en begrundelse altid blive inkluderet i
+# returmail der sendes til afsenderen. Når meddelelserne skal bevares,
+# gemmes de i en specielt køkatalog på disk sådan at
+# serveradministratoren kan se (og måske gøre noget med) meddelelsen,
+# men ellers fjernet. Dette sidste valg er kun tilgængeligt såfremt
+# serveradministratoren har tilladt det.
 #
-# legal values are:
-#    0 = "Discard"
-#    1 = "Reject"
-#    2 = "Forward to List Owner"
-#    3 = "Preserve"
+# gyldige værdier:
+#    0 = "Kassere"
+#    1 = "Afvis"
+#    2 = "Videresend til Listens Ejer"
+#    3 = "Tag hånd om"
 filter_action = 0
 
 ## Topics options
 #
-# 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.
+# Emneord for listen
+
+# Emnefilteret kategoriserer hver e-mail som kommer til listen, efter
+# regexp-uttrykkene du skriver nedenfor. Hvis feltene Subject: eller
+# Keywords: i mailhovedet i en mail passer imod disse udtryk, blir den
+# placeret under dette emne. Hvert medlem af listen kan vælge kun at
+# modtage mail der passer til de &oslash;nskede emner. e-mail som ikke
+# g&aring;r under noget emne, blir ikke leveret.
+# 
+# Bemerk: Dette fungerer kun i normal-modus, ikke i sammendrag-modus.
+# 
+# Indholdet i len kan ogs&aring; unders&oslash;ges for Subject: og
+# Keyword: felter, alt efter hvad indstillingen topics_bodylines_limit
+# er sat til.
 #
-# legal values are:
-#    0 = "Disabled"
-#    1 = "Enabled"
+# gyldige værdier:
+#    0 = "Ikke tilgængelig"
+#    1 = "Tilgængelig"
 topics_enabled = 0
 
-# 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.
-# 
+# Her opgiver du hvor mange linier af mailens indhold som emnefilteret
+# skal s&oslash;ge igennem. En s&oslash;gning stopper n&aring;r s&aring;
+# mange linier er gennoms&oslash;gt, eller n&aring;r det m&oslash;der en
+# linie som ikke ser ud som et meddelelsesfelt. Ved at sætte denne til
+# null (0), vil ingen linier i indholdet blive unders&oslash;gt (dvs.
+# kun Keywords: og Subject: i meddelelseshovedet unders&oslash;ges). Ved
+# at sætte denne værdi til et negativt tal, vil alle linier blive
+# unders&oslash;gt frem til den f&oslash;rste linie som ikke ser ut som
+# et mailhoved-felt.
 topics_bodylines_limit = 5
 
-# 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.
+# Hvert emneord er faktisk et regexp-udtryk, der sammenlignes imod dele
+# af mailen, nemlig feltene Keywords: og Subject: i meldingshodet.
+# Bem&aelig;rk at de f&oslash;ste linier i mailens indhold ogs&aring;
+# kan best&aring; af s&aring;danne "felter", og kan dermed ogs&aring;
+# bli unders&oslash;gt.
 topics = []
 
diff --git a/mailman/nyheder.py b/mailman/nyheder.py
index 61e63ce..3220d0e 100644
--- a/mailman/nyheder.py
+++ b/mailman/nyheder.py
@@ -1,364 +1,388 @@
-## "nyheder" mailing list configuration settings -*- python -*-
-## captured on Wed Mar 16 02:41:06 2005
+## Indstillinger for maillisten "nyheder"  -*- python -*-
+## Dato: Thu May  5 09:52:43 2005
 
 ## General options
 #
-# 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 :-)
+# Grundlæggende egenskaber for listen, blant andet en beskrivelse af
+# listen, og hvordan den opf&oslash;rer sig.
+
+# Her kan du f.eks. stave navnet med stort forbogstav, eller ændre visse
+# bogstaver til store sådan at navnet kan udtales p&aring; en rigtig
+# m&aring;de eller at forkortelser fremhæves. Bemærk at dette navn
+# bruges i e-maillistens adresse (f.eks. i bekræftigelser ved
+# tilmeldinger), s&aring; der 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 :-)
 real_name = 'Nyheder'
 
-# 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.
+# Der er to roller forbundet med hver mailliste. Listeadministratorene
+# 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.
+# 
+# Listemoderatorene har begrænset adgang; de kan ikke ændre
+# indstillinger for e-maillisten, men de kan tage sig af
+# foresp&oslash;rgsler i forbindlse med listen, f.eks. ans&oslash;gning
+# om medlemskab, eller godkende/afvise meddelelser der skal godkendes
+# for at kunne udsendes til listen. Listeadministratorene kan ogs&aring;
+# udf&oslash;re disse opgaver.
+# 
+# For at aktivere muligheden for at have listemoderatorer, og p&aring;
+# den m&aring;de opdele arbejdsopgaverne forbundet med listen, skal du
+# s&aelig;tte dit eget moderatorpassword, og angive din
+# e-mailadressen(e) til den/de som skal v&aelig;re listemoderator(er).
+# Bemærk at i tekstboksene nedenfor skal du skrive e-mailadressen(e) til
+# listeadministratoren(e).
 owner = ['dr@jones.dk']
 
-# 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.
+# Det er to ejerskab forbundet med hver mailliste. Listeadministratorene
+# er dem der har den endelige kontrol over alle indstillingerne for
+# e-mallisten. De kan &aelig;ndre alle indstillinger der er tilgengelige
+# via disse administrative websider.
+# 
+# Listemoderatorene har begr&aelig;nset adgang; de kan ikke &aelig;ndre
+# indstillinger for e-maillisten, men de kan tage sig af
+# foresp&oslash;rgsler ang&aring;ende listen, f.eks. ans&oslash;gning om
+# medlemskab, eller godkende/afvise meddelelser der skal godkendes for
+# at kunne udsendes p&aring; listen. Listeadministratorene kan selvsagt
+# ogs&aring; udf&oslash;re disse opgaver.
+# 
+# For at aktivere muligheten for at have listemoderatorer, og p&aring;
+# den m&aring;den opdele arbejdsopgaverne der er forbundet med listen,
+# skal du s&aelig;tte dit eget moderatorpassword, og indtaste din
+# e-mailadresse(r) til den/de der skal v&aelig;re listemoderator(er).
+# Bemærk at i tekstboksene nedenfor skal du skrive e-mailadressen(e) til
+# listemoderatoren(e).
 moderator = ['sf@dgi-huset.dk', 'tk@dgi-huset.dk']
 
-# 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.
+# Denne beskrivelsen 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 gj&oslash;re det uklart
+# hvad meningen med maillisten er eller hvad den skal bruges til.
 description = 'Nyheder om DGI-huset i &#197;rhus'
 
-# 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.
+# Teksten tolkes som html bortset fra linieskift, der vil blive
+# &aelig;ndret til html-tag'en '<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. Benytter du html-kode,
+# husk da at gennemse meget grundigt, for fejl (f.eks. manglende
+# slutt-tag's) kan f&oslash;re til at listens informationsside ikke vil
+# vises s&aring;dan som den skal.
 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.
-# 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 er sat ind foran emne-/tittelfeltet i e-mail der sendes
+# til listen, for at skille e-mailliste-meddelelser i e-mailboksen fra
+# dem der er medlem af listen. Denne tekst b&oslash;r holdes p&aring; et
+# absolut minimum, benytter du f.eks. listens navn og navnet er langt,
+# b&oslash;r du stave det endnu kortere her. Men den b&oslash;r fremover
+# v&aelig;re beskrivende for listen.
 subject_prefix = '[Nyheder] '
 
-# Hide the sender of a message, replacing it with the list address
-# (Removes From, Sender and Reply-To fields)
+# Skjule afsenderen af meddelser, ved at erstatte den med e-maillistens
+# adresse (Dette medfører at alle From:, Sender, og Reply-To: felter
+# fjernes)
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 anonymous_list = 1
 
-# 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.
+# Skal eksisterende Reply-To: felt i meddelelseshovedet fjernes? Hvis ja
+# vil dette blive gjort uanset om Mailman tlføjer et Reply-To: felt
+# eller ikke.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 first_strip_reply_to = 1
 
-# 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.org/essays/reply-to-useful.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.
+# Denne indstillling fort&aelig;ller hvad Mailman skal gj&oslash;re med
+# Reply-To: feltet i meddelelseshovedet 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;dan 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 diskusion omkring
+# emnet. Se Reply-To Munging Considered Useful for modsatte meninger.
+# 
+# Nogle maillister har begr&aelig;nset adgang, med en egen parallell
+# liste beregnet til diskutioner. Eksempler p&aring; dette er 'patches'
+# eller 'checkin' lister, som system for revisionskontrol sender
+# &aelig;ndringer i programmet til, men diskusioner omkring udvikling af
+# programmet sendes til udviklerenes 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 diskusionsliste.
 #
-# legal values are:
-#    0 = "Poster"
-#    1 = "This list"
-#    2 = "Explicit address"
+# gyldige værdier:
+#    0 = "Afsender"
+#    1 = "mail listens adresse"
+#    2 = "Egendefineret adresse"
 reply_goes_to_list = 2
 
-# 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.org/essays/reply-to-useful.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.
+# 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 modifikasion af Reply-To:
+# adressen g&oslash;r det vanskeligere at sende svar kun til afsender.
+# Se 'Reply-To' Munging Considered Harmful for en diskusion omkring
+# temaet. Se Reply-To Munging Considered Useful for modsatte meninger.
+# 
+# Nogen maillister har begr&aelig;nset adgang, med en egen parallell
+# liste beregnet for diskusioner. Eksempler p&aring; dette er 'patches'
+# eller 'checkin' lister, som system for revisionskontrol sender
+# &aelig;ndringer til i programmet, men diskusioner rundt udvikling af
+# programmet sendes til udviklerenes egen mailliste. For at
+# st&oslash;tte s&aring;danne maillister, definer Reply-To: adressen
+# her, og vælg Egendefineret adresse i indstillingen reply_goes_to_list.
+# 
+# Bem&aelig;rk at hvis den oprindelige meddelse indeholder et Reply-To:
+# felt, vil det ikke &aelig;ndres.
 reply_to_address = 'info@dgi-huset.dk'
 
-# 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.
+# S&aelig;t denne til 'ja' hvis listen skal bruges som en "paraply" for
+# flere andre lister. N&aring;r denne er sat, vil bekr&aelig;ftigelser
+# og meddelelser med password blive sendt til en egen adresse som
+# beregnes ud fra e-mailadressen som er tilmeldt listen - v&aelig;rdien
+# af indstillingen "umbrella_member_suffix" bruges til dette. Denne
+# v&aelig;rdi tilf&oslash;jes til medlemmets kontonavn (det som
+# st&aring;r f&oslash;r @-tegnet).
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 umbrella_list = 0
 
-# 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".
+# N&aring;r "umbrella_list" indikerer at denne liste har andre
+# maillister som medlemmer, er det som regel &oslash;nskelig at
+# administrative meddelelser som f.eks. bekr&aelig;ftigelser og password
+# reminders ikke sendes til selve listen som er medlem, men til
+# administratoren for listen. Hvis dette er tilf&aelig;ldet, bruges
+# v&aelig;rdien af denne indstilling til at bestemme adressen sådan at
+# 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".
 umbrella_member_suffix = '-owner'
 
-# 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.
+# S&aelig;tt denne til hvis du vil have at password reminder skal sendes
+# til medlemmene en gang hver m&aring;ned. Husk at medlemmene kan
+# ogs&aring; selv frav&aelig;lge dette.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 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.
+# Tekst du skriver her vil blive tilf&oslash;jet &oslash;verst i
+# velkomsthilsenen der sendes til nye medlemmer. Velkomshilsenen
+# indeholder allerede viktige adresser og URLer knyttet til maillisten,
+# s&aring; sådan information er det ikke n&oslash;dvendig at inkludere
+# her. Her kan du indl&oslash;gge f.eks. oplysning om etikette eller
+# regler for brug af listen, o.l.
+# 
+# Bem&oslash;rk: Liniene i denne tekst vil brydes efter f&oslash;lgende
+# regler:
 # 
-# 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.
+# Hvert afsnit udfyldes s&aringdan at ingen linie er lenger en 70 tegn.
+# Enhver linie der begynder med blanke tegn udfyldes ikke. Blanke linier
+# adskiller afsnitt.
 # 
 welcome_msg = ''
 
-# 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.
+# S&aelig;t kun denne til 'Nej' hvis du skal il&aelig;gge nye medlemmer
+# manuelt, og ikke vil have de skal f&aring; dette 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.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 send_welcome_msg = 1
 
-# Text sent to people leaving the list.  If empty, no special text will
-# be added to the unsubscribe message.
+# Tekst der sendes til medlemmer der framelder sig fra listen. Hvis
+# denne er tom, l&aelig;gges det ikke noget tekst til frameldelsen.
 goodbye_msg = ''
 
-# Send goodbye message to members when they are unsubscribed?
+# Sende afskedshilsen til medlemmer n&aring;r de frameldes?
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 send_goodbye_msg = 1
 
-# 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.
+# Der udsendes en reminder til listemoderatoren(e) (og
+# listeadministratoren(e)) dagligt om foresp&oslash;rsler der af en
+# eller anden grund venter p&aring; behandling. V&aelig;lger du "Ja",
+# vil listeadminstratoren ogs&aring; motdtage en meddelelse s&aring;
+# snart en foresp&oslash;rsel kommer ind.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 admin_immed_notify = 1
 
-# Should administrator get notices of subscribes and unsubscribes?
+# Skal listeadministratoren(e) ogs&aring; modtage meddelelse om nye
+# medlemmer der tilmelder sig og gamle medlemmer som framelder sig?
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 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.
+# Besked om at en meddelelse skal godkendes sendes ud til afsenderen
+# s&aring;fremt meddelelsen stoppes pga. noget andet end listemoderation
+# eller spam filtre. S&aelig;ttes denne indstilling til 'Nej', vil
+# afsender overhovedet ikke modtage denne besked.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 respond_to_post_requests = 1
 
-# 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.
+# Når dette valg er aktiveret, vil alt e-mail til listen blive moderert.
+# 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-moderasjon" kan da hjælpe dig at fjerne usaglige meddelelser
+# til listen, og på den måden dysse en ophedet diskusion ned.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 emergency = 0
 
-# When a new member is subscribed to this list, their initial set of
-# options is taken from the this variable's setting.
+# Når et nyt medlem tilmeldes listen, blir medlemmets indstillinger
+# taget herfra.
 new_member_options = 260
 
-# 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.
+# Filter for administrative meddelelser vil unders&oslash;ge om
+# meddelelsen egentligt er ment som en administrativ foresp&oslash;rgsel
+# (f.eks. tilmelding, framelding, o.l.), og is&aring;fald sende
+# meddelelsen til administratoren i stedet.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 administrivia = 0
 
-# Maximum length in kilobytes (KB) of a message body.  Use 0 for no
-# limit.
+# Maximum st&oslash;rrelse i kilobytes (KB) for indholdet i e-mail der
+# sendes til listen. Brug verdien '0' for ikke at have en
+# begr&aelig;nsning.
 max_message_size = 0
 
-# 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.
+# "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; denne maskinen. Denne
+# indstillingen kan v&aelig;re nyttig hvis maskinen har flere navne.
 host_name = 'dgi-huset.dk'
 
-# 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).
+# I RFC 2369 defineres en r&aelig;kke List-* felter i
+# meddelelseshovedet, der normalt tilf&oslash;jes hver meddelelse der
+# sendes ud via listen. Disse felter kan hj&aelig;lpe de brugere af
+# listen der benytter et e-mailprogram som f&oslash;lger denne standard.
+# Disse felter b&oslash;r derfor altid v&aelig;re med.
+# 
+# Ikke alle e-mailprogrammer f&oslash;lger denne standard. Er det mange
+# af medlemmene p&aring; listen der benytter s&aring;danne
+# e-mailprogrammer, der ikke kan h&aring;ndtere disse felter i
+# meddelelseshovedet, kan det v&aelig;re du vil v&aelig;lge at udelade
+# dem. Men du b&oslash;r f&oslash;rst fors&oslash;ge at l&aelig;re og
+# forklare medlemmene 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 disse felter, men dette anbefales ikke (denne
+# muligheten kan faktisk ogs&aring; blive fjernet i senere versioner).
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 include_rfc2369_headers = 1
 
-# 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.)
+# List-Post: feltet er et af felterne anbefalet i RFC 2369. Visse
+# e-maillister (som f.eks. kun bruges til offentligørelser), er det kun
+# visse personer der har lov til at sende til; de som er medlem af
+# listen har generelt ikke lov til at sende til listen. For disse
+# lister, er List-Post: feltet forvirrende. I visse tilf&aelig;lde kan
+# det være forvirrende at s&aelig;tte denne indstilling til Nej,
+# s&aring; feltet ikke tilføjes. (Dette påvirker ikke andre List-*:
+# felter.)
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 include_list_post_header = 1
 
 ## Language options
 #
-# 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.
+# Underst&oslash;ttelse for flere sprog. (Internationalisering)
+
+# Dette er standardsproget som benyttes for denne mailliste. Hvis mer
+# 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.
 preferred_language = 'en'
 
-# These are all the natural languages supported by this list. Note that
-# the default language must be included.
+# Her er alle spr&aring;gene denne listen har underst&oslash;ttelse for.
+# Bem&aelig;rk at standardsproget skal v&aelig;re med.
 available_languages = ['en', 'da']
 
-# 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.
+# Hvis standardsproget for din mailliste benytter et andet tegns&aelig;t
+# end ASCII og tittel prefixet for listen indeholder tegn som ikke
+# findes i ASCII-tegns&aelig;ttet, vil prefixet alltid blive kodet i
+# henhold til den relevante standard. Hvis tittel prefixet kun
+# indeholder ASCII tegn, kan det imidlertid ske at du ønsker at sætte
+# dette valg til Aldrig for at undgå koding. Dette kan gøre titlen lidt
+# mere læselig for brugere med e-mailprogrammer der ikke takler andre
+# tegnsæt end ASCII på en rigtig måde.
+# 
+# Bemærk imidlertid at hvis din mailliste modtager både kodede og
+# ukodede tittel felt, kan det være bedst at vælge Efter behov. Med
+# denne indstilling vil Mailman ikke kode ASCII prefixer hvis resten af
+# tittelfeltet kun indeholder ASCII tegn, men vil kode prefixet hvis det
+# indeholder tegn som ikke er ASCII tegn. På denne måde undgås en [...]
+# i standarderne, som forårsager at visse e-mailprogrammer vil vise
+# ekstra eller manglende mellemrum imellom tittel prefixet og det
+# oprindelige tittelfelt.
 #
-# legal values are:
-#    0 = "Never"
-#    1 = "Always"
-#    2 = "As needed"
+# gyldige værdier:
+#    0 = "Aldrig"
+#    1 = "Altid"
+#    2 = "Efter behov"
 encode_ascii_prefixes = 0
 
 ## Nondigest options
 #
-# Policies concerning immediately delivered list traffic.
+# Regler for levering i normal-modus.
 
-# Can subscribers choose to receive mail immediately, rather than in
-# batched digests?
+# Kan medlemmer vælge normal-modus?
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 nondigestable = 1
 
-# 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:
+# 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:
 # 
 # 
 # real_name - The "pretty" name of the list; usually the list name with
@@ -383,9 +407,10 @@ nondigestable = 1
 # 
 msg_header = ''
 
-# 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:
+# Tekst som tilf&aelig;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:
 # 
 # 
 # real_name - The "pretty" name of the list; usually the list name with
@@ -415,42 +440,44 @@ msg_footer = """_______________________________________________
 
 ## Digest options
 #
-# Batched-delivery digest characteristics.
+# Opsætning af sammendrag-modus.
 
-# Can list members choose to receive list traffic bunched in digests?
+# Kan medlemmer af listen vælge at f&aring; tilsendt sammendrag i stedet
+# for?
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 digestable = 1
 
-# Which delivery mode is the default for new users?
+# Hvilken modus er standard for nye brugere?
 #
-# legal values are:
-#    0 = "Regular"
-#    1 = "Digest"
+# gyldige værdier:
+#    0 = "Normal"
+#    1 = "Sammendrag"
 digest_is_default = 0
 
-# When receiving digests, which format is default?
+# Hvilket format skal benyttes som standard for samle-email?
 #
-# legal values are:
-#    0 = "Plain"
+# gyldige værdier:
+#    0 = "Ren tekst"
 #    1 = "MIME"
 mime_is_default_digest = 0
 
-# How big in Kb should a digest be before it gets sent out?
+# Hvor stor (i Kb) m&aring; en samle-email h&oslash;jst v&aelig;re
+# f&oslash;r den udsendes?
 digest_size_threshhold = 30
 
-# Should a digest be dispatched daily when the size threshold isn't
-# reached?
+# Skal der sendes en samle-email dagligt, selv om st&oslash;rrelsen ikke
+# er opn&aring;et?
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 digest_send_periodic = 1
 
-# Text attached (as an initial message, before the table of contents) to
-# the top of digests. This text can include Python format strings which
+# Tekst som l&aelig;gges til &oslash;verst i samle-emailen, f&oslash;r
+# indholdsfortegnelsen.This text can include Python format strings which
 # are resolved against list attributes.  The list of substitutions
 # allowed are:
 # 
@@ -477,9 +504,10 @@ digest_send_periodic = 1
 # 
 digest_header = ''
 
-# 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:
+# Tekst der tilføjes nederst i hver samle-e-mail, som sidste
+# information.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
@@ -507,278 +535,281 @@ digest_footer = """_______________________________________________
 %(real_name)s@%(host_name)s
 %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s"""
 
-# When a new digest volume is started, the volume number is incremented
-# and the issue number is reset to 1.
+# N&aring;r et nyt volume startes, &oslash;ges volume nummeret, og
+# udgavenummeret s&aelig;ttes til 1.
 #
-# legal values are:
-#    0 = "Yearly"
-#    1 = "Monthly"
-#    2 = "Quarterly"
-#    3 = "Weekly"
-#    4 = "Daily"
+# gyldige værdier:
+#    0 = "&Aring;rlig"
+#    1 = "M&aring;nedlig"
+#    2 = "Kvartalsvis"
+#    3 = "Ugentlig"
+#    4 = "Daglig"
 digest_volume_frequency = 1
 
 ## Privacy options
 #
-# 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.
-
-# Advertise this list when people ask what lists are on this machine?
+# Her kan du bestemme hvad der kr&oslash;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&oslash;lder
+# arkivet og arkivering.
+
+# Vise denne mailliste n&aring;r nogn beder om at se en oversigt over
+# maillister p&aring; denne maskine?
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 advertised = 1
 
-# 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.
+# bek&aelig;ftigelse(*) - bekr&aelig;ftigelse af e-mail er
+# n&oslash;dvendig godkendelse - ans&oslash;gkning om medlemskabp skal
+# godkendes af listeadministrator (eller evt. listemoderator)
+# bekr&aelig;ftigelse+godkendelse - b&aring;de bekr&aelig;ftelse
+# p&aring; e-mail og godkendelse af listeadministrator (evt.
+# listemoderator) er nun&oslash;dvendig
+# 
+# (*) n&aring;r nogen vil tilmelde sig en liste, sender Mailman en
+# meddelelse med et uniktidentifikator som de skal opgive for at
+# bekr&oslash;fte tilmeldingen. P&aring; denne m&aring;den vil det da
+# ikke v&aelig;re muligt at tilmelde nogen til listen imod deres vilje.
 #
-# legal values are:
-#    1 = "Confirm"
-#    2 = "Require approval"
-#    3 = "Confirm and approve"
+# gyldige værdier:
+#    1 = "Bekr&aelig;ftigelse"
+#    2 = "Godkendelse"
+#    3 = "Bekr&aelig;ftigelse og godkendelse"
 subscribe_policy = 1
 
-# 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.
+# N&aring;r medlemmer &oslash;nsker at forlade en mailliste, sender de
+# en ans&oslash;gning om framelding, enten via web, eller via e-mail.
+# Normalt er det best at disse ans&oslash;gninger automatisk godkendes,
+# s&aring; meldemmer kan udmelde sig n&aring;r de &oslash;nsker det
+# (mange &oslash;nsker selv at kunne administrere en frameldelse. For
+# nogen f&aring; maillister kan det aligevel v&aelig;re aktuelt at have
+# kontrol over om medlemmer kan melde sig selv ud eller ikke. En liste
+# som alle ansatte i et firma M&Aring; v&aelig;re medlem af, er et
+# eksempel p&aring; en s&aring;dan liste.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 unsubscribe_policy = 0
 
-# 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.
+# Alle e-mailadresser som angives her vil blive udelukket fra listen, og
+# kan ikke tilmelde sig. Indtast e-mailadresser, en per linie, start
+# linien med tegnet ^ for at angive et regexp-udtryk der skal passe med
+# afsenderadressen.
 ban_list = []
 
-# When set, the list of subscribers is protected by member or admin
-# password authentication.
+# Hvis denne indstilling er sat til, vil listen over medlemmer af
+# e-maillisten blive beskyttet af medlemmenes eller adminstratorens
+# password.
 #
-# legal values are:
-#    0 = "Anyone"
-#    1 = "List members"
-#    2 = "List admin only"
+# gyldige værdier:
+#    0 = "Alle"
+#    1 = "Kun medlemmer af listen"
+#    2 = "Kun listeadministrator"
 private_roster = 2
 
-# 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.
+# V&aelig;lger du 'Ja' her, vil medlemmers e-mailadresse omskrives
+# n&aring;r de vises i en oversigt p&aring; websidene (b&aring;de som
+# tekst og i linker), s&aring; de ikke er nemme at tolke som
+# e-mailadresser. Meningen med dette er at undg&aring; at e-mailsniffere
+# der gennemg&aring;r websider for at finde e-mailadresser (og derefter
+# bruge dem til at udsende spam/junk mail) til ikke at opsamle
+# medlemmenes e-mailadresser.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 obscure_addresses = 1
 
 ## Privacy options
 #
-# 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.
+# N&aring;r en meddelelse sendes til maillisten, g&aring;r den igennem
+# en r&aelig;kke trin for at afg&oslash;re om moderatoren m&aring;
+# godkende meddelelsen eller ikke. Her finder du indstillinger for 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 de sendes til listen.
+# 
+# <p>e-mail som ikke er sendt af medlemmer af listen, kan automatisk bli
+# <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">sendt
+# retur</a>, eller <a
+# href="?VARHELP=privacy/sender/discard_these_nonmembers">afvist</a>,
+# enten individuelt eller som en gruppe. All e-mail fra ikke-medlemmer,
+# som ikke specifikt bliver godkent, sendes retur, eller afvist, 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 il&aelig;gger du en e-mailadresse per
+# linie. Du kan ogs&aring; il&aelig;gge  <a
+# href="http://www.python.org/doc/current/lib/module-re.html">Python
+# regexp-uttrykk</a>. Begynd is&aring;fald linien med tegnet ^ for at
+# markere at det er et s&aring;dan udtryk. N&aring;r du benytter
+# backslash, skriv da lige som i rene strings (Python raw strings)
+# (normalt kun &eacute;n backslash af gangen).
+# 
+# <p>Bem&aelig;rk: match p&aring; 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-mail fra medlemmet kan sendes direkte til e-maillisten, eller om de
+# f&oslash;rst skal godkendes af listemoderatoren. N&aring;r
+# moderationsflaget er sat til, skal e-mail fra medlemmet godkendes af
+# listemoderatoren f&oslash;r det udsendes til alle p&aring; listen. Som
+# listeadminsitrator kan du for hvert enkelt medlem bestemme om
+# medlemmets e-mail skal modereres eller ikke. N&aring;r et nyt medlem
+# tilmeldes til 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
+# Administrere medlemmer siden.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 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.
 # 
-# Discard -- this simply discards the message, with no notice sent to
-# the post's author.
+# Holde tilbage -- meldingen holdes tilbage for godkendelse af
+# listemoderatoren(e). Afslå -- meldingen sendes automatisk retur til
+# afsender. Begrundelsen der sendes kan du skrive selv Slette --
+# meddelelsen blir afvist uden at give besked om dette til afsender.
 # 
 #
-# legal values are:
-#    0 = "Hold"
-#    1 = "Reject"
-#    2 = "Discard"
+# gyldige værdier:
+#    0 = "Holde&nbsp;tilbage"
+#    1 = "Afvis"
+#    2 = "Kassere"
 member_moderation_action = 0
 
-# 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.
+# Tekst som skal sendes med meldingen om retur som sendes til modereede
+# medlemmer af listen.
 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."""
 
-# 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.
+# e-mail fra disse ikke-medlemmer vil automatisk blive godkendt.
+# Il&aelig;g e-mailadresser, en per linie, start linien med tegnet ^ for
+# at angive et regexp-uttryk som skal passe med afsenderadressen.
 accept_these_nonmembers = []
 
-# 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.
+# e-mail fra disse ikke-medlemmer vil automatisk blive holdt tilbage for
+# vurdering af listemoderatorene. Afsenderen vil modtage en meddelelse
+# om dette, med bl.a. instruktioner om hvordan han/hun kan
+# tilbagetr&aelig;kke sin e-mails. Indtast e-mailadresser, en per linie,
+# start linien med tegnet ^ for at angive et regexp-uttrykk som skal
+# passe med afsenderadressen.
 hold_these_nonmembers = ['^.*@dgi-huset.dk']
 
-# 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.
+# 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 spam-afsendere,
+# de b&oslash;r automatisk afvises. Indtast e-mailadresser, en per
+# linie, start linien med tegnet ^ for &aring; angiv et regexp-uttrykk
+# som skal passe med afsenderadressen.
 reject_these_nonmembers = []
 
-# 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.
+# e-mail fra disse ikke-medlemmer vil automatisk blive afvist. Det vil
+# sige at meddelelsen afvises uden nogen form for tilbagemelding, men
+# listemoderatorene kan (om ønskeligt) modtage en kopi af den afviste
+# e-mail. Tilf&oslash;je e-mailadresser, en per linie, start linien med
+# tegnet ^ for at angive et regexp-uttryk der skal passe med
+# afsenderadressen.
 discard_these_nonmembers = []
 
-# 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.
+# N&aring;r en e-mail fra et ikke-medlem blir modtaget, sammenlignes
+# e-mailens afsender med listen over e-mailadresser der skal godkendes,
+# holdes tilbage, afvises (sendes i retur), og afvises. Hvis
+# afsenderadressen ikke passer med den der er opgivet i listene, blir
+# f&oslash;lgende afg&oslash;relse taget.
 #
-# legal values are:
-#    0 = "Accept"
-#    1 = "Hold"
-#    2 = "Reject"
-#    3 = "Discard"
+# gyldige værdier:
+#    0 = "Godkende"
+#    1 = "Holde&nbsp;tilbage"
+#    2 = "Afvis"
+#    3 = "Kassere"
 generic_nonmember_action = 1
 
-# Should messages from non-members, which are automatically discarded,
-# be forwarded to the list moderator?
+# Skal meddelelser fra ikke-medlemmer, som automatisk afvises, også
+# sendes til listemoderatoren?
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 forward_auto_discards = 1
 
 ## Privacy options
 #
-# This section allows you to configure various filters based on the
-# recipient of the message.
+# Her kan du ops&aelig;tte filtrering baseret på modtaeren af
+# meddelelsen.
 
-# 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.
+# Meget (faktisk det meste af) spam/junk mail har ikke de endelige
+# modtagere i modtagerfelterne. Faktisk s&aring; indeholder felterne To:
+# og/eller Cc: oftest en fuldst&aelig;ndig 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(e), men vil
+# aligevel blive fanget og blokkere det meste af spam/junk mail.
 # 
-# 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 ville 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
+# alias for listen.
 # 
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 require_explicit_destination = 1
 
-# 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.
+# Alternative e-mailadresser som godtages n&aring;r
+# 'require_explicit_destination' er sat til. Som v&aelig;rdi for denne
+# indstilling skal du opgive regexp-uttryk ("regular expressions"), et
+# udtryk per linie, der sammenlignes imod 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 imod den f&oslash;rste
+# del (det som st&aring;r f&oslash;r '@') af modtageradressen. Hvis
+# sammenligningen ikke lykkes, eller hvis udtrykket ikke indholder en
+# '@', sammenlignes udtrykket med hele modtageradressen.
+# 
+# Sammenligning kun imod den f&oslash;rste del af en modtageradresse
+# underst&oslash;ttes ikke i fr&aelig;mtidige udgaver af Mailman, vil
+# kun sammenligning imod hele modtageradresser blive
+# underst&oslash;ttet.
 acceptable_aliases = ''
 
-# If a posting has this number, or more, of recipients, it is held for
-# admin approval.  Use 0 for no ceiling.
+# Hvis en mail der er sendt til listen indeholder s&aring; mange
+# modtagere som, eller flere modtagere end, denne værdi, holdes malen
+# tilbage så listeadministratoren eventuelt kan godkende den. Brug
+# værdien 0 for ingen begrænsning.
 max_num_recipients = 10
 
 ## Privacy options
 #
-# 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.
-# 
+# Her kan du opsætte forskellige anti-spam filtre, som kan være til
+# hjælp for 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
@@ -791,16 +822,20 @@ max_num_recipients = 10
 # match.
 header_filter_rules = []
 
-# 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.
+# Brug denne indstilling til at fra-filtrere mail til listen, baseret
+# p&aring; indholdet af et eller flere felter i mailhovedet. Her skal du
+# skrive regexp-uttryk (regular expressions), et per linie, som
+# sammenlignes mod det aktuelle felt. Sammenligningen sk&aelig;lner ikke
+# imellem store og sm&aring; bogstaver. Linier der begynder med '#'
+# sammenlignes ikke.
 # 
-# For example:to: .*@public.com  says to hold all postings with a To:
-# mail header containing '@public.com' anywhere among the addresses.
+# For eksempel: udtrykket to: .*@public.com fort&aelig;ller at alt mail
+# som indeholder '@public.com' i To: feltet, skal holdes tilbage til
+# godkendelse.
 # 
-# 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.
+# Bem&aelig;rk: blanke tegn i starten af regexp-udtrykket fjernes. Dette
+# kan man undg&aring; p&aring; flere m&aring;ter, f.eks. ved at bruge
+# escape-tegn eller parenteser.
 bounce_matching_headers = """
 # Lines that *start* with a '#' are comments.
 to: friend@public.com
@@ -810,54 +845,56 @@ from: .*@uplinkpro.com"""
 
 ## Bounce options
 #
-# 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.
+# Disse regler bestemmer hvordan automatisk behandling af returmails
+# gj&oslash;res. Her er en oversigt over hvordan funktionen er.
+# 
+# <p>N&aring;r Mailman modtager en returmail, blir to ting
+# fors&oslash;kt tolket. Det ene er e-mailadressen til medlemmet som
+# egentlig skulle modtage e-mailen, og det andet er &aring;rsagen til
+# problemet. &Aring;rsagen tolkes til at v&aelig;re <em>alvorlig</em>
+# eller <em>lett</em> alt efter om &aring;rsagen er af kritisk eller af
+# mindre alvorlig art. Såfremt der er tvivl, tolkes &aring;rsaken som
+# alvorlig.
+# 
+# <p>Hvis ingen e-mailadresse kan hentes ud af meddelelsen, blir den
+# normalt afvist. Ellers, vil medlemmet som har e-mailadressen f&aring;
+# en <em>returtal</em>, og hver gang en returmeddelelse kommer vil
+# tallet &oslash;ges. Alvorlige &aring;rsaker f&oslash;rer til at tallet
+# &oslash;ges med 1, lette &aring;rsaker f&oslash;rer til at det
+# &oslash;kes med 0.5. Dette sker kun &eacute;n gang per dag, s&aring;
+# selv om det 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;ttest til igen.
+# Medlemmet vil med j&aelig;vne mellemrum modtage melding 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>Det er en vigtig indstilling til; efter en vis tid -- hvis ingen
+# returmeddelelser dukker op i l&oslash;bet af denne tid -- anses
+# returinformation som <a
+# href="?VARHELP=bounce/bounce_info_stale_after">udg&aring;et</a> og
+# afvises. Ved at justere denne værdi, og sætte en grænse for
+# returantallet, kan du bestemme hvor lang tid der skal gå f&oslash;r
+# levering til et medlem stoppes. Begge disse værdier skal du justere
+# alt efter hvor ofte og hvor meget e-mail der sendes til din liste.
+
+# Ved at sætte denne værdi til Nej, sætter du alt automatisk tolking af
+# returmeddelelser for denne liste fra. Bemærk at såfremt meddelelser
+# afvises vil listeadministratoren ikke blive forstyrret med dem.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 bounce_processing = 1
 
 # Each subscriber is assigned a bounce score, as a floating point
@@ -873,351 +910,345 @@ bounce_processing = 1
 # mailing list.
 bounce_score_threshold = 5.0
 
-# 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.
+# Antal dage f&oslash;r returinformation afvises såfremt der ikke dukker
+# flere returmails op. Dette tal skal v&aelig;re et heltal.
 bounce_info_stale_after = 7
 
-# 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.
+# Hvor mange Levering til dig er stoppet advarsler der skal sendes til
+# et medlem f&oslash;r medlemmet frameldes fra listen. S&aelig;t denne
+# værdi til 0 for at fjerne et medlem fra listen umiddelbart
+# s&aring;fremt der kommer returmails fra medlemmets e-mailadresse.
+# Dette tal skal være et heltal.
 bounce_you_are_disabled_warnings = 3
 
-# The number of days between sending the Your Membership Is Disabled
-# warnings.  This value must be an integer.
+# Antal dage imellem hver gang en Levering til dig er stoppet advarsel
+# skal sendes ud. Dette tal skal være et heltal.
 bounce_you_are_disabled_warnings_interval = 7
 
-# 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.
+# Mailmans automatiske returmailhåndtering er meget robust, men det er
+# aligevel umuligt at genkende alle typer returmails der kommer. Du bør
+# angive Ja her, af to grunde: 1) Hvis det virkelig er en permanent
+# returmail fra et medlem af listen, bør du antageligt manuelt udmelde
+# medlemmet fra listen, og 2) du vil måske sende meddelelse til
+# udviklerne af Mailman sådan at returmails automatisk genkendes af
+# Mailman i senere versioner. Hvis du ikke vil gøre nogen af delene, sæt
+# da denne indstilling til Nej. Så vil alle returmails afvises
+# automatisk uden videre behandling. Bem&aelig;rk: Denne indstilling vil
+# også indvirke på alt e-mail der sendes til listens -admin adresse. Den
+# adresse er gammel og udgået, men det kan være at nogen fortsat vil
+# sende e-mail til den. Hvis nogen gør det, og du har sat denne
+# indstilling til Nej, vil disse mails også blive afvist. Måske vil du
+# også opsætte et automatisk svar på e-mail sendt til -owner og -admin
+# adresserne.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 bounce_unrecognized_goes_to_list_owner = 1
 
-# 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.
+# Ved at sætte denne til Nej, fravælges beskeden der normalt sendes til
+# ejeren(e) af listen, når afsending 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.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 bounce_notify_owner_on_disable = 1
 
-# 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.
+# Ved at sætte denne til Nej, fravælges beskeden der normalt sendes til
+# ejeren(e) af listen, når et medlem frameldes fra listen på grund af
+# for mange returmails. Der vil til gengæld altid blive forsøgt afsendt
+# en e-mail med besked til medlemmet.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 bounce_notify_owner_on_removal = 1
 
 ## Archive options
 #
-# List traffic archival policies.
+# Regler for arkivering
 
-# Archive messages?
+# Arkivere e-mail i et arkiv?
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 archive = 1
 
-# Is archive file source for public or private archival?
+# Skal filen arkiveres i et privat eller i et offentlig arkiv?
 #
-# legal values are:
-#    0 = "public"
-#    1 = "private"
+# gyldige værdier:
+#    0 = "offentlig"
+#    1 = "privat"
 archive_private = 0
 
-# How often should a new archive volume be started?
+# Hvor ofte skal arkivet deles op?
 #
-# legal values are:
-#    0 = "Yearly"
-#    1 = "Monthly"
-#    2 = "Quarterly"
-#    3 = "Weekly"
-#    4 = "Daily"
+# gyldige værdier:
+#    0 = "&Aring;rlig"
+#    1 = "M&aring;nedlig"
+#    2 = "Kvartalsvis"
+#    3 = "Ugentlig"
+#    4 = "Daglig"
 archive_volume_frequency = 1
 
 ## Gateway options
 #
-# Mail-to-News and News-to-Mail gateway services.
+# e-mail-Til-Nyhedsgruppe og Nyhedsgruppe-Til-e-mail tjeneste.
 
-# 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.
+# 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.
 nntp_host = ''
 
-# The name of the Usenet group to gateway to and/or from.
+# Navn p&aring; nyhedsgruppe der skal sendes til og/eller fra.
 linked_newsgroup = ''
 
-# Should new posts to the mailing list be sent to the newsgroup?
+# Skal nye mail til denne liste sendes til nyhedsgruppen?
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 gateway_to_news = 0
 
-# Should new posts to the newsgroup be sent to the mailing list?
+# Skal nye meddelelser til nyhedsgruppen sendes til denne mailliste?
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 gateway_to_mail = 0
 
-# 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.
+# 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&aring;t da 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
+# Moderet, vil en ekstra meddelelse holdes tilbage i
+# godkendelsesprocessen. Alt mail sendt til maillisten skal godkendes
+# f&oslash;r de sendes til nyhedsgruppen, eller til medlemmene af
+# listen.
+# 
+# Vær opm&aelig;rksom p&aring; at hvis mailhovedet i mailen har et
+# Approved: felt med listens administrative password, 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 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 meddelelseshovedet.
 #
-# legal values are:
-#    0 = "None"
-#    1 = "Open list, moderated group"
-#    2 = "Moderated"
+# gyldige værdier:
+#    0 = "Ingen"
+#    1 = "Åben liste, modereret nyhedsgruppe"
+#    2 = "Modereret"
 news_moderation = 0
 
-# 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.
+# Mailman tilføjer normalt en tekst du selv 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 sette denne indstilling
+# til Nej hvis du ikke ønsker emne prefix tilføjet til mail som sendes
+# til Usenet. Sætter du emne prefix for listen til off, vil opsamlet
+# meddelelser heller ikke få præfix tilføjet.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 news_prefix_subject_too = 1
 
 ## Autoreply options
 #
-# Auto-responder characteristics.<p>
+# Indstillinger for automatiske svar.<p>
 # 
-# 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>
+# 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 epostadresse</em>
+# <li><b>owneremail</b> - <em>listens -owner epostadresse</em> </ul>
 # 
-# <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.
+# <p>Du kan enten skrive teksten direkte i tekstboksene, eller du kan
+# angive navnet p&aring; en fil som indeholder teksten. Denne file vil
+# s&aring; blive indl&aelig;st i tekstboksen, fra dit lokale filsystem.
 
-# Should Mailman send an auto-response to mailing list posters?
+# Skal Mailman sende et automatisk svar til dem der sender e-mail til
+# listen?
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 autorespond_postings = 0
 
-# Auto-response text to send to mailing list posters.
+# Automatisk svar der skal sendes.
 autoresponse_postings_text = ''
 
-# Should Mailman send an auto-response to emails sent to the -owner
-# address?
+# Skal Mailman sende et automatisk svar p&aring; e-mail der sendes til
+# -owner adressen?
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 autorespond_admin = 0
 
-# Auto-response text to send to -owner emails.
+# Automatisk svar p&aring; e-mail til -owner adressen.
 autoresponse_admin_text = ''
 
-# 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.
+# 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
+# ogs&aring; skal v&aelig;re med i det automatiske svar.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes, w/discard"
-#    2 = "Yes, w/forward"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja, men uden den originale e-mailn"
+#    2 = "Ja, og medtag den originale e-mail"
 autorespond_requests = 0
 
-# Auto-response text to send to -request emails.
+# Automatisk svar p&aring; e-mail til -request adressen.
 autoresponse_request_text = ''
 
-# 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).
+# Antal dage imellem automatisk svar p&aring; e-mail, fra samme
+# afsender, til listen eller til -request/-owner adressene. S&aelig;t
+# denne v&aelig;rdi til 0 (eller et negativt tal) for at sende
+# automatisk svar hver gang.
 autoresponse_graceperiod = 90
 
 ## Contentfilter options
 #
-# 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.  Then, each
-# <tt>multipart/alternative</tt> section will be replaced by just the
-# first alternative that is non-empty after filtering.
-# 
-# <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?
+# Regler for indhold i e-mail sendt til listen.
+# 
+# <p>Filtrering af indhold fungerer således: når listen modtger en
+# e-mail og du har beskyttelse med filtrering af indhold, sammenlignes
+# først eventuelle ved- hæftelser imod <a
+# href="?VARHELP=contentfilter/filter_mime_types">MIME filtre</a>. Hvis
+# en vedhæftelse passer med et af disse filtre, blir vedhæftelsen
+# fjernet.
+# 
+# <p>Derefter sammenlignes eventuelle vedhæftelser imod <a
+# href="?VARHELP=contentfilter/pass_mime_types">gyldige MIME typer</a>,
+# hvis nogen er defineret. Alle vedhæftelser som ikke passer med de
+# angivne MIME typene, blir fjernet.
+# 
+# <p>Efter disse filtre, vil alle tomme <tt>multipart</tt> vedhæftelser
+# blive fjernet. Hvis selve meddelelsen er helt tom efter denne
+# filtrering, vil meddelelsen bli afvist. Derefter vil hvert
+# <tt>multipart/alternative</tt> vedhæftelse blive erstattet af det
+# første alternative som ikke er tomt.
+# 
+# <p>Til slut vil alle <tt>text/html</tt> vedhæftelser som måtte være
+# tilbage i meddelelsen blive konverteret til <tt>text/plain</tt>
+# såfremt <a
+# href="?VARHELP=contentfilter/convert_html_to_plaintext">konvertere til
+# ren tekst</a> er sat til og serveren er konfigurert til at tillade
+# sådanne konverteringer.
+
+# Skal Mailman filtrere indhold i e-mail sendt til listen som angivet
+# nedenfor?
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 filter_content = 0
 
-# 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.
+# Brug denne instilling til at fjerne vedhæftelser der passer til MIME
+# typer. Hver linie skal her indeholde navnet på en MIME type/subtype,
+# f.eks. image/gif. Såfremt du ønsker at fjerne alle vedhæftelser som
+# har en given hoved MIME type, kan du lade være at angive subtype,
+# f.eks. image.
 # 
-# Blank lines are ignored.
+# Blanke linier medtages ikke.
 # 
-# See also <a href="?VARHELP=contentfilter/pass_mime_types"
-# >pass_mime_types for a content type whitelist.
+# Se også gyldige MIME typer for whitelist af MIME typer.
 filter_mime_types = ''
 
-# 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.
+# Brug denne indstilling for at definere hvilke MIME typer der skal være
+# tilladt. Krav og format for filtrering er identisk med MIME filtre.
 # 
-# 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.
+# Bem&aelig;rk: hvis du lægger noget ind her, men ikke angiver
+# multipart, vil al e-mail med vedhæftelser ikke blive medtaget.
 pass_mime_types = """multipart/mixed
 multipart/alternative
 text/plain"""
 
-# Should Mailman convert text/html parts to plain text?  This conversion
-# happens after MIME attachments have been stripped.
+# Skal Mailman konvertere text/html dele til ren tekst? Denne
+# konvertering vil finde sted efter at MIME filteret har fjernet de
+# ønskede dele.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 convert_html_to_plaintext = 1
 
-# One of these actions is take 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.
+# Her bestemmer du hvad der skal ske når en meddelelse filtreres fra af
+# et filter, altså såfremt vedhæftelsen filtreres fra MIME filteret,
+# eller ent vedhæftelse ikke har en af de gyldige MIME typer, eller
+# meddelelsen ender op med at være tom efter filtrering.
+# 
+# Bemærk at det du vælger her ikke vil ske såfremt en meddelelse stadig
+# indeholder noget efter filtrering. Så vil meddelelsen altid sendes
+# videre til listen.
+# 
+# Når meddelelsen afvises, skrives Message-ID'en til den afviste
+# meddelelse til loggen. Når meddelelsen sendes retur eller videresendes
+# til listens ejer, vil en begrundelse altid blive inkluderet i
+# returmail der sendes til afsenderen. Når meddelelserne skal bevares,
+# gemmes de i en specielt køkatalog på disk sådan at
+# serveradministratoren kan se (og måske gøre noget med) meddelelsen,
+# men ellers fjernet. Dette sidste valg er kun tilgængeligt såfremt
+# serveradministratoren har tilladt det.
 #
-# legal values are:
-#    0 = "Discard"
-#    1 = "Reject"
-#    2 = "Forward to List Owner"
-#    3 = "Preserve"
+# gyldige værdier:
+#    0 = "Kassere"
+#    1 = "Afvis"
+#    2 = "Videresend til Listens Ejer"
+#    3 = "Tag hånd om"
 filter_action = 0
 
 ## Topics options
 #
-# 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.
+# Emneord for listen
+
+# Emnefilteret kategoriserer hver e-mail som kommer til listen, efter
+# regexp-uttrykkene du skriver nedenfor. Hvis feltene Subject: eller
+# Keywords: i mailhovedet i en mail passer imod disse udtryk, blir den
+# placeret under dette emne. Hvert medlem af listen kan vælge kun at
+# modtage mail der passer til de &oslash;nskede emner. e-mail som ikke
+# g&aring;r under noget emne, blir ikke leveret.
+# 
+# Bemerk: Dette fungerer kun i normal-modus, ikke i sammendrag-modus.
+# 
+# Indholdet i len kan ogs&aring; unders&oslash;ges for Subject: og
+# Keyword: felter, alt efter hvad indstillingen topics_bodylines_limit
+# er sat til.
 #
-# legal values are:
-#    0 = "Disabled"
-#    1 = "Enabled"
+# gyldige værdier:
+#    0 = "Ikke tilgængelig"
+#    1 = "Tilgængelig"
 topics_enabled = 0
 
-# 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.
-# 
+# Her opgiver du hvor mange linier af mailens indhold som emnefilteret
+# skal s&oslash;ge igennem. En s&oslash;gning stopper n&aring;r s&aring;
+# mange linier er gennoms&oslash;gt, eller n&aring;r det m&oslash;der en
+# linie som ikke ser ud som et meddelelsesfelt. Ved at sætte denne til
+# null (0), vil ingen linier i indholdet blive unders&oslash;gt (dvs.
+# kun Keywords: og Subject: i meddelelseshovedet unders&oslash;ges). Ved
+# at sætte denne værdi til et negativt tal, vil alle linier blive
+# unders&oslash;gt frem til den f&oslash;rste linie som ikke ser ut som
+# et mailhoved-felt.
 topics_bodylines_limit = 5
 
-# 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.
+# Hvert emneord er faktisk et regexp-udtryk, der sammenlignes imod dele
+# af mailen, nemlig feltene Keywords: og Subject: i meldingshodet.
+# Bem&aelig;rk at de f&oslash;ste linier i mailens indhold ogs&aring;
+# kan best&aring; af s&aring;danne "felter", og kan dermed ogs&aring;
+# bli unders&oslash;gt.
 topics = []
 
diff --git a/mailman/users.py b/mailman/users.py
index 7b05ec4..a605b26 100644
--- a/mailman/users.py
+++ b/mailman/users.py
@@ -1,197 +1,208 @@
-## "users" mailing list configuration settings -*- python -*-
-## captured on Wed Mar 16 02:41:08 2005
+## Indstillinger for maillisten "users"  -*- python -*-
+## Dato: Thu May  5 09:52:44 2005
 
 ## General options
 #
-# 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 :-)
+# Grundlæggende egenskaber for listen, blant andet en beskrivelse af
+# listen, og hvordan den opf&oslash;rer sig.
+
+# Her kan du f.eks. stave navnet med stort forbogstav, eller ændre visse
+# bogstaver til store sådan at navnet kan udtales p&aring; en rigtig
+# m&aring;de eller at forkortelser fremhæves. Bemærk at dette navn
+# bruges i e-maillistens adresse (f.eks. i bekræftigelser ved
+# tilmeldinger), s&aring; der 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 :-)
 real_name = 'Users'
 
-# 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.
+# Der er to roller forbundet med hver mailliste. Listeadministratorene
+# 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.
+# 
+# Listemoderatorene har begrænset adgang; de kan ikke ændre
+# indstillinger for e-maillisten, men de kan tage sig af
+# foresp&oslash;rgsler i forbindlse med listen, f.eks. ans&oslash;gning
+# om medlemskab, eller godkende/afvise meddelelser der skal godkendes
+# for at kunne udsendes til listen. Listeadministratorene kan ogs&aring;
+# udf&oslash;re disse opgaver.
+# 
+# For at aktivere muligheden for at have listemoderatorer, og p&aring;
+# den m&aring;de opdele arbejdsopgaverne forbundet med listen, skal du
+# s&aelig;tte dit eget moderatorpassword, og angive din
+# e-mailadressen(e) til den/de som skal v&aelig;re listemoderator(er).
+# Bemærk at i tekstboksene nedenfor skal du skrive e-mailadressen(e) til
+# listeadministratoren(e).
 owner = ['dr.jones@pobox.com']
 
-# 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.
+# Det er to ejerskab forbundet med hver mailliste. Listeadministratorene
+# er dem der har den endelige kontrol over alle indstillingerne for
+# e-mallisten. De kan &aelig;ndre alle indstillinger der er tilgengelige
+# via disse administrative websider.
+# 
+# Listemoderatorene har begr&aelig;nset adgang; de kan ikke &aelig;ndre
+# indstillinger for e-maillisten, men de kan tage sig af
+# foresp&oslash;rgsler ang&aring;ende listen, f.eks. ans&oslash;gning om
+# medlemskab, eller godkende/afvise meddelelser der skal godkendes for
+# at kunne udsendes p&aring; listen. Listeadministratorene kan selvsagt
+# ogs&aring; udf&oslash;re disse opgaver.
+# 
+# For at aktivere muligheten for at have listemoderatorer, og p&aring;
+# den m&aring;den opdele arbejdsopgaverne der er forbundet med listen,
+# skal du s&aelig;tte dit eget moderatorpassword, og indtaste din
+# e-mailadresse(r) til den/de der skal v&aelig;re listemoderator(er).
+# Bemærk at i tekstboksene nedenfor skal du skrive e-mailadressen(e) til
+# listemoderatoren(e).
 moderator = []
 
-# 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.
+# Denne beskrivelsen 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 gj&oslash;re det uklart
+# hvad meningen med maillisten er eller hvad den skal bruges til.
 description = 'Announcements to users at jones.dk'
 
-# 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.
+# Teksten tolkes som html bortset fra linieskift, der vil blive
+# &aelig;ndret til html-tag'en '<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. Benytter du html-kode,
+# husk da at gennemse meget grundigt, for fejl (f.eks. manglende
+# slutt-tag's) kan f&oslash;re til at listens informationsside ikke vil
+# vises s&aring;dan som den skal.
 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.
 
 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.
-# 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 er sat ind foran emne-/tittelfeltet i e-mail der sendes
+# til listen, for at skille e-mailliste-meddelelser i e-mailboksen fra
+# dem der er medlem af listen. Denne tekst b&oslash;r holdes p&aring; et
+# absolut minimum, benytter du f.eks. listens navn og navnet er langt,
+# b&oslash;r du stave det endnu kortere her. Men den b&oslash;r fremover
+# v&aelig;re beskrivende for listen.
 subject_prefix = '[Users] '
 
-# Hide the sender of a message, replacing it with the list address
-# (Removes From, Sender and Reply-To fields)
+# Skjule afsenderen af meddelser, ved at erstatte den med e-maillistens
+# adresse (Dette medfører at alle From:, Sender, og Reply-To: felter
+# fjernes)
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 anonymous_list = 0
 
-# 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.
+# Skal eksisterende Reply-To: felt i meddelelseshovedet fjernes? Hvis ja
+# vil dette blive gjort uanset om Mailman tlføjer et Reply-To: felt
+# eller ikke.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 first_strip_reply_to = 0
 
-# 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.org/essays/reply-to-useful.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.
+# Denne indstillling fort&aelig;ller hvad Mailman skal gj&oslash;re med
+# Reply-To: feltet i meddelelseshovedet 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;dan 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 diskusion omkring
+# emnet. Se Reply-To Munging Considered Useful for modsatte meninger.
+# 
+# Nogle maillister har begr&aelig;nset adgang, med en egen parallell
+# liste beregnet til diskutioner. Eksempler p&aring; dette er 'patches'
+# eller 'checkin' lister, som system for revisionskontrol sender
+# &aelig;ndringer i programmet til, men diskusioner omkring udvikling af
+# programmet sendes til udviklerenes 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 diskusionsliste.
 #
-# legal values are:
-#    0 = "Poster"
-#    1 = "This list"
-#    2 = "Explicit address"
+# gyldige værdier:
+#    0 = "Afsender"
+#    1 = "mail listens adresse"
+#    2 = "Egendefineret adresse"
 reply_goes_to_list = 0
 
-# 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.org/essays/reply-to-useful.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.
+# 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 modifikasion af Reply-To:
+# adressen g&oslash;r det vanskeligere at sende svar kun til afsender.
+# Se 'Reply-To' Munging Considered Harmful for en diskusion omkring
+# temaet. Se Reply-To Munging Considered Useful for modsatte meninger.
+# 
+# Nogen maillister har begr&aelig;nset adgang, med en egen parallell
+# liste beregnet for diskusioner. Eksempler p&aring; dette er 'patches'
+# eller 'checkin' lister, som system for revisionskontrol sender
+# &aelig;ndringer til i programmet, men diskusioner rundt udvikling af
+# programmet sendes til udviklerenes egen mailliste. For at
+# st&oslash;tte s&aring;danne maillister, definer Reply-To: adressen
+# her, og vælg Egendefineret adresse i indstillingen reply_goes_to_list.
+# 
+# Bem&aelig;rk at hvis den oprindelige meddelse indeholder et Reply-To:
+# felt, vil det ikke &aelig;ndres.
 reply_to_address = ''
 
-# 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.
+# S&aelig;t denne til 'ja' hvis listen skal bruges som en "paraply" for
+# flere andre lister. N&aring;r denne er sat, vil bekr&aelig;ftigelser
+# og meddelelser med password blive sendt til en egen adresse som
+# beregnes ud fra e-mailadressen som er tilmeldt listen - v&aelig;rdien
+# af indstillingen "umbrella_member_suffix" bruges til dette. Denne
+# v&aelig;rdi tilf&oslash;jes til medlemmets kontonavn (det som
+# st&aring;r f&oslash;r @-tegnet).
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 umbrella_list = 0
 
-# 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".
+# N&aring;r "umbrella_list" indikerer at denne liste har andre
+# maillister som medlemmer, er det som regel &oslash;nskelig at
+# administrative meddelelser som f.eks. bekr&aelig;ftigelser og password
+# reminders ikke sendes til selve listen som er medlem, men til
+# administratoren for listen. Hvis dette er tilf&aelig;ldet, bruges
+# v&aelig;rdien af denne indstilling til at bestemme adressen sådan at
+# 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".
 umbrella_member_suffix = '-owner'
 
-# 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.
+# S&aelig;tt denne til hvis du vil have at password reminder skal sendes
+# til medlemmene en gang hver m&aring;ned. Husk at medlemmene kan
+# ogs&aring; selv frav&aelig;lge dette.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 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.
+# Tekst du skriver her vil blive tilf&oslash;jet &oslash;verst i
+# velkomsthilsenen der sendes til nye medlemmer. Velkomshilsenen
+# indeholder allerede viktige adresser og URLer knyttet til maillisten,
+# s&aring; sådan information er det ikke n&oslash;dvendig at inkludere
+# her. Her kan du indl&oslash;gge f.eks. oplysning om etikette eller
+# regler for brug af listen, o.l.
+# 
+# Bem&oslash;rk: Liniene i denne tekst vil brydes efter f&oslash;lgende
+# regler:
 # 
-# 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.
+# Hvert afsnit udfyldes s&aringdan at ingen linie er lenger en 70 tegn.
+# Enhver linie der begynder med blanke tegn udfyldes ikke. Blanke linier
+# adskiller afsnitt.
 # 
 welcome_msg = """This is a mailing list for people with an E-mail account at jones.dk
 
@@ -206,173 +217,186 @@ Kind regards,
 
 Jonas Smedegaard"""
 
-# 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.
+# S&aelig;t kun denne til 'Nej' hvis du skal il&aelig;gge nye medlemmer
+# manuelt, og ikke vil have de skal f&aring; dette 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.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 send_welcome_msg = 1
 
-# Text sent to people leaving the list.  If empty, no special text will
-# be added to the unsubscribe message.
+# Tekst der sendes til medlemmer der framelder sig fra listen. Hvis
+# denne er tom, l&aelig;gges det ikke noget tekst til frameldelsen.
 goodbye_msg = """Hmmm
 Are you sure that was a very smart move?"""
 
-# Send goodbye message to members when they are unsubscribed?
+# Sende afskedshilsen til medlemmer n&aring;r de frameldes?
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 send_goodbye_msg = 1
 
-# 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.
+# Der udsendes en reminder til listemoderatoren(e) (og
+# listeadministratoren(e)) dagligt om foresp&oslash;rsler der af en
+# eller anden grund venter p&aring; behandling. V&aelig;lger du "Ja",
+# vil listeadminstratoren ogs&aring; motdtage en meddelelse s&aring;
+# snart en foresp&oslash;rsel kommer ind.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 admin_immed_notify = 1
 
-# Should administrator get notices of subscribes and unsubscribes?
+# Skal listeadministratoren(e) ogs&aring; modtage meddelelse om nye
+# medlemmer der tilmelder sig og gamle medlemmer som framelder sig?
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 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.
+# Besked om at en meddelelse skal godkendes sendes ud til afsenderen
+# s&aring;fremt meddelelsen stoppes pga. noget andet end listemoderation
+# eller spam filtre. S&aelig;ttes denne indstilling til 'Nej', vil
+# afsender overhovedet ikke modtage denne besked.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 respond_to_post_requests = 1
 
-# 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.
+# Når dette valg er aktiveret, vil alt e-mail til listen blive moderert.
+# 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-moderasjon" kan da hjælpe dig at fjerne usaglige meddelelser
+# til listen, og på den måden dysse en ophedet diskusion ned.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 emergency = 0
 
-# When a new member is subscribed to this list, their initial set of
-# options is taken from the this variable's setting.
+# Når et nyt medlem tilmeldes listen, blir medlemmets indstillinger
+# taget herfra.
 new_member_options = 256
 
-# 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.
+# Filter for administrative meddelelser vil unders&oslash;ge om
+# meddelelsen egentligt er ment som en administrativ foresp&oslash;rgsel
+# (f.eks. tilmelding, framelding, o.l.), og is&aring;fald sende
+# meddelelsen til administratoren i stedet.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 administrivia = 1
 
-# Maximum length in kilobytes (KB) of a message body.  Use 0 for no
-# limit.
+# Maximum st&oslash;rrelse i kilobytes (KB) for indholdet i e-mail der
+# sendes til listen. Brug verdien '0' for ikke at have en
+# begr&aelig;nsning.
 max_message_size = 40
 
-# 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.
+# "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; denne maskinen. Denne
+# indstillingen kan v&aelig;re nyttig hvis maskinen har flere navne.
 host_name = 'jones.dk'
 
-# 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).
+# I RFC 2369 defineres en r&aelig;kke List-* felter i
+# meddelelseshovedet, der normalt tilf&oslash;jes hver meddelelse der
+# sendes ud via listen. Disse felter kan hj&aelig;lpe de brugere af
+# listen der benytter et e-mailprogram som f&oslash;lger denne standard.
+# Disse felter b&oslash;r derfor altid v&aelig;re med.
+# 
+# Ikke alle e-mailprogrammer f&oslash;lger denne standard. Er det mange
+# af medlemmene p&aring; listen der benytter s&aring;danne
+# e-mailprogrammer, der ikke kan h&aring;ndtere disse felter i
+# meddelelseshovedet, kan det v&aelig;re du vil v&aelig;lge at udelade
+# dem. Men du b&oslash;r f&oslash;rst fors&oslash;ge at l&aelig;re og
+# forklare medlemmene 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 disse felter, men dette anbefales ikke (denne
+# muligheten kan faktisk ogs&aring; blive fjernet i senere versioner).
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 include_rfc2369_headers = 1
 
-# 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.)
+# List-Post: feltet er et af felterne anbefalet i RFC 2369. Visse
+# e-maillister (som f.eks. kun bruges til offentligørelser), er det kun
+# visse personer der har lov til at sende til; de som er medlem af
+# listen har generelt ikke lov til at sende til listen. For disse
+# lister, er List-Post: feltet forvirrende. I visse tilf&aelig;lde kan
+# det være forvirrende at s&aelig;tte denne indstilling til Nej,
+# s&aring; feltet ikke tilføjes. (Dette påvirker ikke andre List-*:
+# felter.)
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 include_list_post_header = 1
 
 ## Language options
 #
-# 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.
+# Underst&oslash;ttelse for flere sprog. (Internationalisering)
+
+# Dette er standardsproget som benyttes for denne mailliste. Hvis mer
+# 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.
 preferred_language = 'en'
 
-# These are all the natural languages supported by this list. Note that
-# the default language must be included.
+# Her er alle spr&aring;gene denne listen har underst&oslash;ttelse for.
+# Bem&aelig;rk at standardsproget skal v&aelig;re med.
 available_languages = ['da', 'de', 'en', 'no', 'sv']
 
-# 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.
+# Hvis standardsproget for din mailliste benytter et andet tegns&aelig;t
+# end ASCII og tittel prefixet for listen indeholder tegn som ikke
+# findes i ASCII-tegns&aelig;ttet, vil prefixet alltid blive kodet i
+# henhold til den relevante standard. Hvis tittel prefixet kun
+# indeholder ASCII tegn, kan det imidlertid ske at du ønsker at sætte
+# dette valg til Aldrig for at undgå koding. Dette kan gøre titlen lidt
+# mere læselig for brugere med e-mailprogrammer der ikke takler andre
+# tegnsæt end ASCII på en rigtig måde.
+# 
+# Bemærk imidlertid at hvis din mailliste modtager både kodede og
+# ukodede tittel felt, kan det være bedst at vælge Efter behov. Med
+# denne indstilling vil Mailman ikke kode ASCII prefixer hvis resten af
+# tittelfeltet kun indeholder ASCII tegn, men vil kode prefixet hvis det
+# indeholder tegn som ikke er ASCII tegn. På denne måde undgås en [...]
+# i standarderne, som forårsager at visse e-mailprogrammer vil vise
+# ekstra eller manglende mellemrum imellom tittel prefixet og det
+# oprindelige tittelfelt.
 #
-# legal values are:
-#    0 = "Never"
-#    1 = "Always"
-#    2 = "As needed"
+# gyldige værdier:
+#    0 = "Aldrig"
+#    1 = "Altid"
+#    2 = "Efter behov"
 encode_ascii_prefixes = 0
 
 ## Nondigest options
 #
-# Policies concerning immediately delivered list traffic.
+# Regler for levering i normal-modus.
 
-# Can subscribers choose to receive mail immediately, rather than in
-# batched digests?
+# Kan medlemmer vælge normal-modus?
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 nondigestable = 1
 
-# 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:
+# 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:
 # 
 # 
 # real_name - The "pretty" name of the list; usually the list name with
@@ -397,9 +421,10 @@ nondigestable = 1
 # 
 msg_header = ''
 
-# 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:
+# Tekst som tilf&aelig;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:
 # 
 # 
 # real_name - The "pretty" name of the list; usually the list name with
@@ -428,42 +453,44 @@ msg_footer = """_______________________________________________
 
 ## Digest options
 #
-# Batched-delivery digest characteristics.
+# Opsætning af sammendrag-modus.
 
-# Can list members choose to receive list traffic bunched in digests?
+# Kan medlemmer af listen vælge at f&aring; tilsendt sammendrag i stedet
+# for?
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 digestable = 1
 
-# Which delivery mode is the default for new users?
+# Hvilken modus er standard for nye brugere?
 #
-# legal values are:
-#    0 = "Regular"
-#    1 = "Digest"
+# gyldige værdier:
+#    0 = "Normal"
+#    1 = "Sammendrag"
 digest_is_default = 0
 
-# When receiving digests, which format is default?
+# Hvilket format skal benyttes som standard for samle-email?
 #
-# legal values are:
-#    0 = "Plain"
+# gyldige værdier:
+#    0 = "Ren tekst"
 #    1 = "MIME"
 mime_is_default_digest = 0
 
-# How big in Kb should a digest be before it gets sent out?
+# Hvor stor (i Kb) m&aring; en samle-email h&oslash;jst v&aelig;re
+# f&oslash;r den udsendes?
 digest_size_threshhold = 30
 
-# Should a digest be dispatched daily when the size threshold isn't
-# reached?
+# Skal der sendes en samle-email dagligt, selv om st&oslash;rrelsen ikke
+# er opn&aring;et?
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 digest_send_periodic = 1
 
-# Text attached (as an initial message, before the table of contents) to
-# the top of digests. This text can include Python format strings which
+# Tekst som l&aelig;gges til &oslash;verst i samle-emailen, f&oslash;r
+# indholdsfortegnelsen.This text can include Python format strings which
 # are resolved against list attributes.  The list of substitutions
 # allowed are:
 # 
@@ -490,9 +517,10 @@ digest_send_periodic = 1
 # 
 digest_header = ''
 
-# 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:
+# Tekst der tilføjes nederst i hver samle-e-mail, som sidste
+# information.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
@@ -519,274 +547,277 @@ digest_footer = """_______________________________________________
 %(real_name)s maillist  -  %(real_name)s@%(host_name)s
 %(web_page_url)slistinfo/%(_internal_name)s"""
 
-# When a new digest volume is started, the volume number is incremented
-# and the issue number is reset to 1.
+# N&aring;r et nyt volume startes, &oslash;ges volume nummeret, og
+# udgavenummeret s&aelig;ttes til 1.
 #
-# legal values are:
-#    0 = "Yearly"
-#    1 = "Monthly"
-#    2 = "Quarterly"
-#    3 = "Weekly"
-#    4 = "Daily"
+# gyldige værdier:
+#    0 = "&Aring;rlig"
+#    1 = "M&aring;nedlig"
+#    2 = "Kvartalsvis"
+#    3 = "Ugentlig"
+#    4 = "Daglig"
 digest_volume_frequency = 1
 
 ## Privacy options
 #
-# 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.
-
-# Advertise this list when people ask what lists are on this machine?
+# Her kan du bestemme hvad der kr&oslash;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&oslash;lder
+# arkivet og arkivering.
+
+# Vise denne mailliste n&aring;r nogn beder om at se en oversigt over
+# maillister p&aring; denne maskine?
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 advertised = 1
 
-# 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.
+# bek&aelig;ftigelse(*) - bekr&aelig;ftigelse af e-mail er
+# n&oslash;dvendig godkendelse - ans&oslash;gkning om medlemskabp skal
+# godkendes af listeadministrator (eller evt. listemoderator)
+# bekr&aelig;ftigelse+godkendelse - b&aring;de bekr&aelig;ftelse
+# p&aring; e-mail og godkendelse af listeadministrator (evt.
+# listemoderator) er nun&oslash;dvendig
+# 
+# (*) n&aring;r nogen vil tilmelde sig en liste, sender Mailman en
+# meddelelse med et uniktidentifikator som de skal opgive for at
+# bekr&oslash;fte tilmeldingen. P&aring; denne m&aring;den vil det da
+# ikke v&aelig;re muligt at tilmelde nogen til listen imod deres vilje.
 #
-# legal values are:
-#    1 = "Confirm"
-#    2 = "Require approval"
-#    3 = "Confirm and approve"
+# gyldige værdier:
+#    1 = "Bekr&aelig;ftigelse"
+#    2 = "Godkendelse"
+#    3 = "Bekr&aelig;ftigelse og godkendelse"
 subscribe_policy = 2
 
-# 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.
+# N&aring;r medlemmer &oslash;nsker at forlade en mailliste, sender de
+# en ans&oslash;gning om framelding, enten via web, eller via e-mail.
+# Normalt er det best at disse ans&oslash;gninger automatisk godkendes,
+# s&aring; meldemmer kan udmelde sig n&aring;r de &oslash;nsker det
+# (mange &oslash;nsker selv at kunne administrere en frameldelse. For
+# nogen f&aring; maillister kan det aligevel v&aelig;re aktuelt at have
+# kontrol over om medlemmer kan melde sig selv ud eller ikke. En liste
+# som alle ansatte i et firma M&Aring; v&aelig;re medlem af, er et
+# eksempel p&aring; en s&aring;dan liste.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 unsubscribe_policy = 0
 
-# 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.
+# Alle e-mailadresser som angives her vil blive udelukket fra listen, og
+# kan ikke tilmelde sig. Indtast e-mailadresser, en per linie, start
+# linien med tegnet ^ for at angive et regexp-udtryk der skal passe med
+# afsenderadressen.
 ban_list = []
 
-# When set, the list of subscribers is protected by member or admin
-# password authentication.
+# Hvis denne indstilling er sat til, vil listen over medlemmer af
+# e-maillisten blive beskyttet af medlemmenes eller adminstratorens
+# password.
 #
-# legal values are:
-#    0 = "Anyone"
-#    1 = "List members"
-#    2 = "List admin only"
+# gyldige værdier:
+#    0 = "Alle"
+#    1 = "Kun medlemmer af listen"
+#    2 = "Kun listeadministrator"
 private_roster = 2
 
-# 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.
+# V&aelig;lger du 'Ja' her, vil medlemmers e-mailadresse omskrives
+# n&aring;r de vises i en oversigt p&aring; websidene (b&aring;de som
+# tekst og i linker), s&aring; de ikke er nemme at tolke som
+# e-mailadresser. Meningen med dette er at undg&aring; at e-mailsniffere
+# der gennemg&aring;r websider for at finde e-mailadresser (og derefter
+# bruge dem til at udsende spam/junk mail) til ikke at opsamle
+# medlemmenes e-mailadresser.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 obscure_addresses = 1
 
 ## Privacy options
 #
-# 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.
+# N&aring;r en meddelelse sendes til maillisten, g&aring;r den igennem
+# en r&aelig;kke trin for at afg&oslash;re om moderatoren m&aring;
+# godkende meddelelsen eller ikke. Her finder du indstillinger for 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 de sendes til listen.
+# 
+# <p>e-mail som ikke er sendt af medlemmer af listen, kan automatisk bli
+# <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">sendt
+# retur</a>, eller <a
+# href="?VARHELP=privacy/sender/discard_these_nonmembers">afvist</a>,
+# enten individuelt eller som en gruppe. All e-mail fra ikke-medlemmer,
+# som ikke specifikt bliver godkent, sendes retur, eller afvist, 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 il&aelig;gger du en e-mailadresse per
+# linie. Du kan ogs&aring; il&aelig;gge  <a
+# href="http://www.python.org/doc/current/lib/module-re.html">Python
+# regexp-uttrykk</a>. Begynd is&aring;fald linien med tegnet ^ for at
+# markere at det er et s&aring;dan udtryk. N&aring;r du benytter
+# backslash, skriv da lige som i rene strings (Python raw strings)
+# (normalt kun &eacute;n backslash af gangen).
+# 
+# <p>Bem&aelig;rk: match p&aring; 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-mail fra medlemmet kan sendes direkte til e-maillisten, eller om de
+# f&oslash;rst skal godkendes af listemoderatoren. N&aring;r
+# moderationsflaget er sat til, skal e-mail fra medlemmet godkendes af
+# listemoderatoren f&oslash;r det udsendes til alle p&aring; listen. Som
+# listeadminsitrator kan du for hvert enkelt medlem bestemme om
+# medlemmets e-mail skal modereres eller ikke. N&aring;r et nyt medlem
+# tilmeldes til 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
+# Administrere medlemmer siden.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 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.
 # 
-# Discard -- this simply discards the message, with no notice sent to
-# the post's author.
+# Holde tilbage -- meldingen holdes tilbage for godkendelse af
+# listemoderatoren(e). Afslå -- meldingen sendes automatisk retur til
+# afsender. Begrundelsen der sendes kan du skrive selv Slette --
+# meddelelsen blir afvist uden at give besked om dette til afsender.
 # 
 #
-# legal values are:
-#    0 = "Hold"
-#    1 = "Reject"
-#    2 = "Discard"
+# gyldige værdier:
+#    0 = "Holde&nbsp;tilbage"
+#    1 = "Afvis"
+#    2 = "Kassere"
 member_moderation_action = 0
 
-# 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.
+# Tekst som skal sendes med meldingen om retur som sendes til modereede
+# medlemmer af listen.
 member_moderation_notice = ''
 
-# 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.
+# e-mail fra disse ikke-medlemmer vil automatisk blive godkendt.
+# Il&aelig;g e-mailadresser, en per linie, start linien med tegnet ^ for
+# at angive et regexp-uttryk som skal passe med afsenderadressen.
 accept_these_nonmembers = ['jonas@jones.dk']
 
-# 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.
+# e-mail fra disse ikke-medlemmer vil automatisk blive holdt tilbage for
+# vurdering af listemoderatorene. Afsenderen vil modtage en meddelelse
+# om dette, med bl.a. instruktioner om hvordan han/hun kan
+# tilbagetr&aelig;kke sin e-mails. Indtast e-mailadresser, en per linie,
+# start linien med tegnet ^ for at angive et regexp-uttrykk som skal
+# passe med afsenderadressen.
 hold_these_nonmembers = []
 
-# 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.
+# 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 spam-afsendere,
+# de b&oslash;r automatisk afvises. Indtast e-mailadresser, en per
+# linie, start linien med tegnet ^ for &aring; angiv et regexp-uttrykk
+# som skal passe med afsenderadressen.
 reject_these_nonmembers = []
 
-# 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.
+# e-mail fra disse ikke-medlemmer vil automatisk blive afvist. Det vil
+# sige at meddelelsen afvises uden nogen form for tilbagemelding, men
+# listemoderatorene kan (om ønskeligt) modtage en kopi af den afviste
+# e-mail. Tilf&oslash;je e-mailadresser, en per linie, start linien med
+# tegnet ^ for at angive et regexp-uttryk der skal passe med
+# afsenderadressen.
 discard_these_nonmembers = []
 
-# 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.
+# N&aring;r en e-mail fra et ikke-medlem blir modtaget, sammenlignes
+# e-mailens afsender med listen over e-mailadresser der skal godkendes,
+# holdes tilbage, afvises (sendes i retur), og afvises. Hvis
+# afsenderadressen ikke passer med den der er opgivet i listene, blir
+# f&oslash;lgende afg&oslash;relse taget.
 #
-# legal values are:
-#    0 = "Accept"
-#    1 = "Hold"
-#    2 = "Reject"
-#    3 = "Discard"
+# gyldige værdier:
+#    0 = "Godkende"
+#    1 = "Holde&nbsp;tilbage"
+#    2 = "Afvis"
+#    3 = "Kassere"
 generic_nonmember_action = 3
 
-# Should messages from non-members, which are automatically discarded,
-# be forwarded to the list moderator?
+# Skal meddelelser fra ikke-medlemmer, som automatisk afvises, også
+# sendes til listemoderatoren?
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 forward_auto_discards = 1
 
 ## Privacy options
 #
-# This section allows you to configure various filters based on the
-# recipient of the message.
+# Her kan du ops&aelig;tte filtrering baseret på modtaeren af
+# meddelelsen.
 
-# 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.
+# Meget (faktisk det meste af) spam/junk mail har ikke de endelige
+# modtagere i modtagerfelterne. Faktisk s&aring; indeholder felterne To:
+# og/eller Cc: oftest en fuldst&aelig;ndig 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(e), men vil
+# aligevel blive fanget og blokkere det meste af spam/junk mail.
 # 
-# 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 ville 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
+# alias for listen.
 # 
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 require_explicit_destination = 1
 
-# 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.
+# Alternative e-mailadresser som godtages n&aring;r
+# 'require_explicit_destination' er sat til. Som v&aelig;rdi for denne
+# indstilling skal du opgive regexp-uttryk ("regular expressions"), et
+# udtryk per linie, der sammenlignes imod 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 imod den f&oslash;rste
+# del (det som st&aring;r f&oslash;r '@') af modtageradressen. Hvis
+# sammenligningen ikke lykkes, eller hvis udtrykket ikke indholder en
+# '@', sammenlignes udtrykket med hele modtageradressen.
+# 
+# Sammenligning kun imod den f&oslash;rste del af en modtageradresse
+# underst&oslash;ttes ikke i fr&aelig;mtidige udgaver af Mailman, vil
+# kun sammenligning imod hele modtageradresser blive
+# underst&oslash;ttet.
 acceptable_aliases = ''
 
-# If a posting has this number, or more, of recipients, it is held for
-# admin approval.  Use 0 for no ceiling.
+# Hvis en mail der er sendt til listen indeholder s&aring; mange
+# modtagere som, eller flere modtagere end, denne værdi, holdes malen
+# tilbage så listeadministratoren eventuelt kan godkende den. Brug
+# værdien 0 for ingen begrænsning.
 max_num_recipients = 10
 
 ## Privacy options
 #
-# 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.
-# 
+# Her kan du opsætte forskellige anti-spam filtre, som kan være til
+# hjælp for 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
@@ -799,16 +830,20 @@ max_num_recipients = 10
 # match.
 header_filter_rules = []
 
-# 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.
+# Brug denne indstilling til at fra-filtrere mail til listen, baseret
+# p&aring; indholdet af et eller flere felter i mailhovedet. Her skal du
+# skrive regexp-uttryk (regular expressions), et per linie, som
+# sammenlignes mod det aktuelle felt. Sammenligningen sk&aelig;lner ikke
+# imellem store og sm&aring; bogstaver. Linier der begynder med '#'
+# sammenlignes ikke.
 # 
-# For example:to: .*@public.com  says to hold all postings with a To:
-# mail header containing '@public.com' anywhere among the addresses.
+# For eksempel: udtrykket to: .*@public.com fort&aelig;ller at alt mail
+# som indeholder '@public.com' i To: feltet, skal holdes tilbage til
+# godkendelse.
 # 
-# 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.
+# Bem&aelig;rk: blanke tegn i starten af regexp-udtrykket fjernes. Dette
+# kan man undg&aring; p&aring; flere m&aring;ter, f.eks. ved at bruge
+# escape-tegn eller parenteser.
 bounce_matching_headers = """# Lines that *start* with a '#' are comments.
 to: friend@public.com
 message-id: relay.comanche.denmark.eu
@@ -817,54 +852,56 @@ from: .*@uplinkpro.com"""
 
 ## Bounce options
 #
-# 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.
+# Disse regler bestemmer hvordan automatisk behandling af returmails
+# gj&oslash;res. Her er en oversigt over hvordan funktionen er.
+# 
+# <p>N&aring;r Mailman modtager en returmail, blir to ting
+# fors&oslash;kt tolket. Det ene er e-mailadressen til medlemmet som
+# egentlig skulle modtage e-mailen, og det andet er &aring;rsagen til
+# problemet. &Aring;rsagen tolkes til at v&aelig;re <em>alvorlig</em>
+# eller <em>lett</em> alt efter om &aring;rsagen er af kritisk eller af
+# mindre alvorlig art. Såfremt der er tvivl, tolkes &aring;rsaken som
+# alvorlig.
+# 
+# <p>Hvis ingen e-mailadresse kan hentes ud af meddelelsen, blir den
+# normalt afvist. Ellers, vil medlemmet som har e-mailadressen f&aring;
+# en <em>returtal</em>, og hver gang en returmeddelelse kommer vil
+# tallet &oslash;ges. Alvorlige &aring;rsaker f&oslash;rer til at tallet
+# &oslash;ges med 1, lette &aring;rsaker f&oslash;rer til at det
+# &oslash;kes med 0.5. Dette sker kun &eacute;n gang per dag, s&aring;
+# selv om det 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;ttest til igen.
+# Medlemmet vil med j&aelig;vne mellemrum modtage melding 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>Det er en vigtig indstilling til; efter en vis tid -- hvis ingen
+# returmeddelelser dukker op i l&oslash;bet af denne tid -- anses
+# returinformation som <a
+# href="?VARHELP=bounce/bounce_info_stale_after">udg&aring;et</a> og
+# afvises. Ved at justere denne værdi, og sætte en grænse for
+# returantallet, kan du bestemme hvor lang tid der skal gå f&oslash;r
+# levering til et medlem stoppes. Begge disse værdier skal du justere
+# alt efter hvor ofte og hvor meget e-mail der sendes til din liste.
+
+# Ved at sætte denne værdi til Nej, sætter du alt automatisk tolking af
+# returmeddelelser for denne liste fra. Bemærk at såfremt meddelelser
+# afvises vil listeadministratoren ikke blive forstyrret med dem.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 bounce_processing = 1
 
 # Each subscriber is assigned a bounce score, as a floating point
@@ -880,351 +917,345 @@ bounce_processing = 1
 # mailing list.
 bounce_score_threshold = 5.0
 
-# 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.
+# Antal dage f&oslash;r returinformation afvises såfremt der ikke dukker
+# flere returmails op. Dette tal skal v&aelig;re et heltal.
 bounce_info_stale_after = 7
 
-# 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.
+# Hvor mange Levering til dig er stoppet advarsler der skal sendes til
+# et medlem f&oslash;r medlemmet frameldes fra listen. S&aelig;t denne
+# værdi til 0 for at fjerne et medlem fra listen umiddelbart
+# s&aring;fremt der kommer returmails fra medlemmets e-mailadresse.
+# Dette tal skal være et heltal.
 bounce_you_are_disabled_warnings = 3
 
-# The number of days between sending the Your Membership Is Disabled
-# warnings.  This value must be an integer.
+# Antal dage imellem hver gang en Levering til dig er stoppet advarsel
+# skal sendes ud. Dette tal skal være et heltal.
 bounce_you_are_disabled_warnings_interval = 7
 
-# 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.
+# Mailmans automatiske returmailhåndtering er meget robust, men det er
+# aligevel umuligt at genkende alle typer returmails der kommer. Du bør
+# angive Ja her, af to grunde: 1) Hvis det virkelig er en permanent
+# returmail fra et medlem af listen, bør du antageligt manuelt udmelde
+# medlemmet fra listen, og 2) du vil måske sende meddelelse til
+# udviklerne af Mailman sådan at returmails automatisk genkendes af
+# Mailman i senere versioner. Hvis du ikke vil gøre nogen af delene, sæt
+# da denne indstilling til Nej. Så vil alle returmails afvises
+# automatisk uden videre behandling. Bem&aelig;rk: Denne indstilling vil
+# også indvirke på alt e-mail der sendes til listens -admin adresse. Den
+# adresse er gammel og udgået, men det kan være at nogen fortsat vil
+# sende e-mail til den. Hvis nogen gør det, og du har sat denne
+# indstilling til Nej, vil disse mails også blive afvist. Måske vil du
+# også opsætte et automatisk svar på e-mail sendt til -owner og -admin
+# adresserne.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 bounce_unrecognized_goes_to_list_owner = 1
 
-# 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.
+# Ved at sætte denne til Nej, fravælges beskeden der normalt sendes til
+# ejeren(e) af listen, når afsending 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.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 bounce_notify_owner_on_disable = 1
 
-# 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.
+# Ved at sætte denne til Nej, fravælges beskeden der normalt sendes til
+# ejeren(e) af listen, når et medlem frameldes fra listen på grund af
+# for mange returmails. Der vil til gengæld altid blive forsøgt afsendt
+# en e-mail med besked til medlemmet.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 bounce_notify_owner_on_removal = 1
 
 ## Archive options
 #
-# List traffic archival policies.
+# Regler for arkivering
 
-# Archive messages?
+# Arkivere e-mail i et arkiv?
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 archive = 1
 
-# Is archive file source for public or private archival?
+# Skal filen arkiveres i et privat eller i et offentlig arkiv?
 #
-# legal values are:
-#    0 = "public"
-#    1 = "private"
+# gyldige værdier:
+#    0 = "offentlig"
+#    1 = "privat"
 archive_private = 0
 
-# How often should a new archive volume be started?
+# Hvor ofte skal arkivet deles op?
 #
-# legal values are:
-#    0 = "Yearly"
-#    1 = "Monthly"
-#    2 = "Quarterly"
-#    3 = "Weekly"
-#    4 = "Daily"
+# gyldige værdier:
+#    0 = "&Aring;rlig"
+#    1 = "M&aring;nedlig"
+#    2 = "Kvartalsvis"
+#    3 = "Ugentlig"
+#    4 = "Daglig"
 archive_volume_frequency = 2
 
 ## Gateway options
 #
-# Mail-to-News and News-to-Mail gateway services.
+# e-mail-Til-Nyhedsgruppe og Nyhedsgruppe-Til-e-mail tjeneste.
 
-# 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.
+# 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.
 nntp_host = ''
 
-# The name of the Usenet group to gateway to and/or from.
+# Navn p&aring; nyhedsgruppe der skal sendes til og/eller fra.
 linked_newsgroup = ''
 
-# Should new posts to the mailing list be sent to the newsgroup?
+# Skal nye mail til denne liste sendes til nyhedsgruppen?
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 gateway_to_news = 0
 
-# Should new posts to the newsgroup be sent to the mailing list?
+# Skal nye meddelelser til nyhedsgruppen sendes til denne mailliste?
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 gateway_to_mail = 0
 
-# 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.
+# 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&aring;t da 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
+# Moderet, vil en ekstra meddelelse holdes tilbage i
+# godkendelsesprocessen. Alt mail sendt til maillisten skal godkendes
+# f&oslash;r de sendes til nyhedsgruppen, eller til medlemmene af
+# listen.
+# 
+# Vær opm&aelig;rksom p&aring; at hvis mailhovedet i mailen har et
+# Approved: felt med listens administrative password, 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 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 meddelelseshovedet.
 #
-# legal values are:
-#    0 = "None"
-#    1 = "Open list, moderated group"
-#    2 = "Moderated"
+# gyldige værdier:
+#    0 = "Ingen"
+#    1 = "Åben liste, modereret nyhedsgruppe"
+#    2 = "Modereret"
 news_moderation = 0
 
-# 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.
+# Mailman tilføjer normalt en tekst du selv 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 sette denne indstilling
+# til Nej hvis du ikke ønsker emne prefix tilføjet til mail som sendes
+# til Usenet. Sætter du emne prefix for listen til off, vil opsamlet
+# meddelelser heller ikke få præfix tilføjet.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 news_prefix_subject_too = 1
 
 ## Autoreply options
 #
-# Auto-responder characteristics.<p>
+# Indstillinger for automatiske svar.<p>
 # 
-# 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>
+# 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 epostadresse</em>
+# <li><b>owneremail</b> - <em>listens -owner epostadresse</em> </ul>
 # 
-# <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.
+# <p>Du kan enten skrive teksten direkte i tekstboksene, eller du kan
+# angive navnet p&aring; en fil som indeholder teksten. Denne file vil
+# s&aring; blive indl&aelig;st i tekstboksen, fra dit lokale filsystem.
 
-# Should Mailman send an auto-response to mailing list posters?
+# Skal Mailman sende et automatisk svar til dem der sender e-mail til
+# listen?
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 autorespond_postings = 0
 
-# Auto-response text to send to mailing list posters.
+# Automatisk svar der skal sendes.
 autoresponse_postings_text = ''
 
-# Should Mailman send an auto-response to emails sent to the -owner
-# address?
+# Skal Mailman sende et automatisk svar p&aring; e-mail der sendes til
+# -owner adressen?
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 autorespond_admin = 0
 
-# Auto-response text to send to -owner emails.
+# Automatisk svar p&aring; e-mail til -owner adressen.
 autoresponse_admin_text = ''
 
-# 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.
+# 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
+# ogs&aring; skal v&aelig;re med i det automatiske svar.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes, w/discard"
-#    2 = "Yes, w/forward"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja, men uden den originale e-mailn"
+#    2 = "Ja, og medtag den originale e-mail"
 autorespond_requests = 0
 
-# Auto-response text to send to -request emails.
+# Automatisk svar p&aring; e-mail til -request adressen.
 autoresponse_request_text = ''
 
-# 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).
+# Antal dage imellem automatisk svar p&aring; e-mail, fra samme
+# afsender, til listen eller til -request/-owner adressene. S&aelig;t
+# denne v&aelig;rdi til 0 (eller et negativt tal) for at sende
+# automatisk svar hver gang.
 autoresponse_graceperiod = 90
 
 ## Contentfilter options
 #
-# 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.  Then, each
-# <tt>multipart/alternative</tt> section will be replaced by just the
-# first alternative that is non-empty after filtering.
-# 
-# <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?
+# Regler for indhold i e-mail sendt til listen.
+# 
+# <p>Filtrering af indhold fungerer således: når listen modtger en
+# e-mail og du har beskyttelse med filtrering af indhold, sammenlignes
+# først eventuelle ved- hæftelser imod <a
+# href="?VARHELP=contentfilter/filter_mime_types">MIME filtre</a>. Hvis
+# en vedhæftelse passer med et af disse filtre, blir vedhæftelsen
+# fjernet.
+# 
+# <p>Derefter sammenlignes eventuelle vedhæftelser imod <a
+# href="?VARHELP=contentfilter/pass_mime_types">gyldige MIME typer</a>,
+# hvis nogen er defineret. Alle vedhæftelser som ikke passer med de
+# angivne MIME typene, blir fjernet.
+# 
+# <p>Efter disse filtre, vil alle tomme <tt>multipart</tt> vedhæftelser
+# blive fjernet. Hvis selve meddelelsen er helt tom efter denne
+# filtrering, vil meddelelsen bli afvist. Derefter vil hvert
+# <tt>multipart/alternative</tt> vedhæftelse blive erstattet af det
+# første alternative som ikke er tomt.
+# 
+# <p>Til slut vil alle <tt>text/html</tt> vedhæftelser som måtte være
+# tilbage i meddelelsen blive konverteret til <tt>text/plain</tt>
+# såfremt <a
+# href="?VARHELP=contentfilter/convert_html_to_plaintext">konvertere til
+# ren tekst</a> er sat til og serveren er konfigurert til at tillade
+# sådanne konverteringer.
+
+# Skal Mailman filtrere indhold i e-mail sendt til listen som angivet
+# nedenfor?
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 filter_content = 0
 
-# 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.
+# Brug denne instilling til at fjerne vedhæftelser der passer til MIME
+# typer. Hver linie skal her indeholde navnet på en MIME type/subtype,
+# f.eks. image/gif. Såfremt du ønsker at fjerne alle vedhæftelser som
+# har en given hoved MIME type, kan du lade være at angive subtype,
+# f.eks. image.
 # 
-# Blank lines are ignored.
+# Blanke linier medtages ikke.
 # 
-# See also <a href="?VARHELP=contentfilter/pass_mime_types"
-# >pass_mime_types for a content type whitelist.
+# Se også gyldige MIME typer for whitelist af MIME typer.
 filter_mime_types = ''
 
-# 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.
+# Brug denne indstilling for at definere hvilke MIME typer der skal være
+# tilladt. Krav og format for filtrering er identisk med MIME filtre.
 # 
-# 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.
+# Bem&aelig;rk: hvis du lægger noget ind her, men ikke angiver
+# multipart, vil al e-mail med vedhæftelser ikke blive medtaget.
 pass_mime_types = """multipart/mixed
 multipart/alternative
 text/plain"""
 
-# Should Mailman convert text/html parts to plain text?  This conversion
-# happens after MIME attachments have been stripped.
+# Skal Mailman konvertere text/html dele til ren tekst? Denne
+# konvertering vil finde sted efter at MIME filteret har fjernet de
+# ønskede dele.
 #
-# legal values are:
-#    0 = "No"
-#    1 = "Yes"
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
 convert_html_to_plaintext = 1
 
-# One of these actions is take 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.
+# Her bestemmer du hvad der skal ske når en meddelelse filtreres fra af
+# et filter, altså såfremt vedhæftelsen filtreres fra MIME filteret,
+# eller ent vedhæftelse ikke har en af de gyldige MIME typer, eller
+# meddelelsen ender op med at være tom efter filtrering.
+# 
+# Bemærk at det du vælger her ikke vil ske såfremt en meddelelse stadig
+# indeholder noget efter filtrering. Så vil meddelelsen altid sendes
+# videre til listen.
+# 
+# Når meddelelsen afvises, skrives Message-ID'en til den afviste
+# meddelelse til loggen. Når meddelelsen sendes retur eller videresendes
+# til listens ejer, vil en begrundelse altid blive inkluderet i
+# returmail der sendes til afsenderen. Når meddelelserne skal bevares,
+# gemmes de i en specielt køkatalog på disk sådan at
+# serveradministratoren kan se (og måske gøre noget med) meddelelsen,
+# men ellers fjernet. Dette sidste valg er kun tilgængeligt såfremt
+# serveradministratoren har tilladt det.
 #
-# legal values are:
-#    0 = "Discard"
-#    1 = "Reject"
-#    2 = "Forward to List Owner"
-#    3 = "Preserve"
+# gyldige værdier:
+#    0 = "Kassere"
+#    1 = "Afvis"
+#    2 = "Videresend til Listens Ejer"
+#    3 = "Tag hånd om"
 filter_action = 0
 
 ## Topics options
 #
-# 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.
+# Emneord for listen
+
+# Emnefilteret kategoriserer hver e-mail som kommer til listen, efter
+# regexp-uttrykkene du skriver nedenfor. Hvis feltene Subject: eller
+# Keywords: i mailhovedet i en mail passer imod disse udtryk, blir den
+# placeret under dette emne. Hvert medlem af listen kan vælge kun at
+# modtage mail der passer til de &oslash;nskede emner. e-mail som ikke
+# g&aring;r under noget emne, blir ikke leveret.
+# 
+# Bemerk: Dette fungerer kun i normal-modus, ikke i sammendrag-modus.
+# 
+# Indholdet i len kan ogs&aring; unders&oslash;ges for Subject: og
+# Keyword: felter, alt efter hvad indstillingen topics_bodylines_limit
+# er sat til.
 #
-# legal values are:
-#    0 = "Disabled"
-#    1 = "Enabled"
+# gyldige værdier:
+#    0 = "Ikke tilgængelig"
+#    1 = "Tilgængelig"
 topics_enabled = 0
 
-# 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.
-# 
+# Her opgiver du hvor mange linier af mailens indhold som emnefilteret
+# skal s&oslash;ge igennem. En s&oslash;gning stopper n&aring;r s&aring;
+# mange linier er gennoms&oslash;gt, eller n&aring;r det m&oslash;der en
+# linie som ikke ser ud som et meddelelsesfelt. Ved at sætte denne til
+# null (0), vil ingen linier i indholdet blive unders&oslash;gt (dvs.
+# kun Keywords: og Subject: i meddelelseshovedet unders&oslash;ges). Ved
+# at sætte denne værdi til et negativt tal, vil alle linier blive
+# unders&oslash;gt frem til den f&oslash;rste linie som ikke ser ut som
+# et mailhoved-felt.
 topics_bodylines_limit = 5
 
-# 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.
+# Hvert emneord er faktisk et regexp-udtryk, der sammenlignes imod dele
+# af mailen, nemlig feltene Keywords: og Subject: i meldingshodet.
+# Bem&aelig;rk at de f&oslash;ste linier i mailens indhold ogs&aring;
+# kan best&aring; af s&aring;danne "felter", og kan dermed ogs&aring;
+# bli unders&oslash;gt.
 topics = []