Update all Mailman lists.

18 files changed, 2900 insertions, 70 deletions

diff --git a/mailman/absynthe.py b/mailman/absynthe.py
index 6f6197f..4d4d2e7 100644
--- a/mailman/absynthe.py
+++ b/mailman/absynthe.py
@@ -1,5 +1,5 @@
 ## "absynthe" mailing list configuration settings -*- python -*-
-## captured on Thu Mar 11 02:10:36 2004
+## captured on Wed Mar 16 02:40:55 2005
 
 ## General options
 #
@@ -317,7 +317,7 @@ preferred_language = 'en'
 
 # These are all the natural languages supported by this list. Note that
 # the default language must be included.
-available_languages = ['en']
+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
@@ -853,8 +853,17 @@ from: .*@uplinkpro.com"""
 #    1 = "Yes"
 bounce_processing = 1
 
-# The maximum member bounce score before the member's subscription is
-# disabled.  This value can be a floating point number.
+# 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
diff --git a/mailman/assilissat.members b/mailman/assilissat.members
index c00b1cc..d717ed3 100644
--- a/mailman/assilissat.members
+++ b/mailman/assilissat.members
@@ -1,16 +1,12 @@
-a.overgaard@idg.dk
 a_funch@post12.tele.dk
-Kenneth Rasmussen <aarnuaa@greennet.gl>
 arnaaraq_85@hotmail.com
 assilissat@film.dk
-aviaja@greennet.gl
 elsenuna@greennet.gl
 gant@cfk.hum.aau.dk
 georg@knr.gl
 imondrup@hotmail.com
 inuk@jones.dk
 inukmedia@greennet.gl
-inuks@hotmail.com
 jacobsenmiki@hotmail.com
 jessie@greennet.gl
 jrs@asiaq.gl
@@ -18,15 +14,9 @@ kaneq@hotmail.com
 knudps@knr.gl
 lucas@greennet.gl
 mazz@ofir.dk
-mudi@hotmail.com
-ns@legalink.dk
 olekrist@greennet.gl
-otto@jones.dk
 polarjan@hotmail.com
 puilasoq@hotmail.com
 silamiut@greennet.gl
-silis@greennet.gl
 susievito@hotmail.com
-svend@hardenberg.dk
-tidaravn@image.dk
 tv.aasiaat@hotmail.com
diff --git a/mailman/assilissat.py b/mailman/assilissat.py
index 1ae984e..c0167e6 100644
--- a/mailman/assilissat.py
+++ b/mailman/assilissat.py
@@ -1,5 +1,5 @@
 ## "assilissat" mailing list configuration settings -*- python -*-
-## captured on Thu Mar 11 02:10:37 2004
+## captured on Wed Mar 16 02:40:56 2005
 
 ## General options
 #
@@ -317,7 +317,7 @@ preferred_language = 'en'
 
 # These are all the natural languages supported by this list. Note that
 # the default language must be included.
-available_languages = ['en']
+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
@@ -566,7 +566,7 @@ unsubscribe_policy = 0
 # mailing list, with no further moderation required.  Add addresses one
 # per line; start the line with a ^ character to designate a regular
 # expression match.
-ban_list = ['afygrobo@hotmail.com']
+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.
@@ -693,7 +693,7 @@ reject_these_nonmembers = []
 # 
 # Add member addresses one per line; start the line with a ^ character
 # to designate a regular expression match.
-discard_these_nonmembers = ['afygrobo@hotmail.com']
+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
@@ -854,8 +854,17 @@ from: .*@uplinkpro.com"""
 #    1 = "Yes"
 bounce_processing = 1
 
-# The maximum member bounce score before the member's subscription is
-# disabled.  This value can be a floating point number.
+# 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
diff --git a/mailman/bestyrelse.members b/mailman/bestyrelse.members
new file mode 100644
index 0000000..e69de29
--- /dev/null
+++ b/mailman/bestyrelse.members
diff --git a/mailman/bestyrelse.py b/mailman/bestyrelse.py
new file mode 100644
index 0000000..737eec3
--- /dev/null
+++ b/mailman/bestyrelse.py
@@ -0,0 +1,1236 @@
+## "bestyrelse" mailing list configuration settings -*- python -*-
+## captured on Wed Mar 16 02:40:57 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 = '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.
+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)
+#
+# 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 (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."""
+
+# 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 = '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).
+#
+# 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/bestyrelse/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 = 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.
+#
+# 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 = 1
+
+# 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/debian.members b/mailman/debian.members
index b299947..dfffcec 100644
--- a/mailman/debian.members
+++ b/mailman/debian.members
@@ -1,18 +1,12 @@
 Anders Kr?yer <anders@homebase.dk>
-andy@firman.us
-bernhard@intevation.de
-Carl Perry <caperry+debjones@edolnx.net>
-Daniel Schildt <daniel@autiomaa.org>
-Christen Hansen <dr@hippie.dk>
+bjarke nielsen <berico@tiscali.dk>
 Jonas Smedegard <dr@jones.dk>
-fizban@tamos.net
-garth@utmail.to
 gaudenz@soziologie.ch
 Hari Seldon <hseldon@aeren.net>
-janus@netcetera.dk
+JLF <jfranc46@ford.com>
 jones@cos.user.lysator.liu.se
 Juri Jensen <juri@xenux.dk>
 kun.stoej@stoej.org
-maneatingcow@mac.com
 ruggero@jones.dk
 Robert Spencer <shodan@iz.org>
+Thijs Kroesbergen <thijs@brokenwire.net>
diff --git a/mailman/debian.py b/mailman/debian.py
index 32b80a5..52b50d4 100644
--- a/mailman/debian.py
+++ b/mailman/debian.py
@@ -1,5 +1,5 @@
 ## "debian" mailing list configuration settings -*- python -*-
-## captured on Thu Mar 11 02:10:38 2004
+## captured on Wed Mar 16 02:40:59 2005
 
 ## General options
 #
@@ -317,7 +317,7 @@ preferred_language = 'en'
 
 # These are all the natural languages supported by this list. Note that
 # the default language must be included.
-available_languages = ['en']
+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
@@ -854,8 +854,17 @@ from: .*@uplinkpro.com"""
 #    1 = "Yes"
 bounce_processing = 1
 
-# The maximum member bounce score before the member's subscription is
-# disabled.  This value can be a floating point number.
+# 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
diff --git a/mailman/friends.members b/mailman/friends.members
index dbf2c88..504f555 100644
--- a/mailman/friends.members
+++ b/mailman/friends.members
@@ -2,6 +2,7 @@ Mette.Kaspersen@sas.dk
 Senrik@post3.tele.dk
 agnes@jones.dk
 ai@jones.dk
+aj@jones.dk
 allan@ohms.dk
 alo@jones.dk
 anarres@postmaster.co.uk
@@ -9,6 +10,7 @@ anders@jones.dk
 ane@jones.dk
 anne@jones.dk
 ascanius@jones.dk
+assenbjerg@jones.dk
 awh@jones.dk
 benny@jones.dk
 bering@binx.com
@@ -25,6 +27,7 @@ cpoll@get2net.dk
 cro@kaosman.com
 daenzer@debian.org
 dewd@jones.dk
+diva@jones.dk
 dolmer@jones.dk
 donvet1@hotmail.com
 dreijer@jones.dk
@@ -63,6 +66,7 @@ jason@jones.dk
 jens@jones.dk
 jfe@jones.dk
 jgh@jones.dk
+joachim@jones.dk
 jonas@jones.dk
 jorgen@jones.dk
 jourand.jorgensen@get2net.dk
@@ -111,6 +115,7 @@ mette_sn99@yahoo.com
 michael@jones.dk
 micky_007@hotmail.com
 miriam@langstrumpf.ch
+miv@jones.dk
 mnharris@comfortable-usa.com
 mogens@jones.dk
 morgan@jones.dk
@@ -118,6 +123,7 @@ mortenp@tuba.dk
 mp@jones.dk
 mr@jones.dk
 nahumury@xs4all.nl
+nancy@jones.dk
 negon@pop.agora.dk
 nelle@chaos.wit.no
 nicolai@jones.dk
@@ -136,6 +142,7 @@ paul@jones.dk
 pelle@jones.dk
 pepper@jones.dk
 per@jones.dk
+pernille@jones.dk
 peter@jones.dk
 podhot@hotmail.com
 propel149@hotmail.com
@@ -156,8 +163,10 @@ saturn@jones.dk
 scn73@hotmail.com
 sebwijk@jones.dk
 sg@jones.dk
+sj@jones.dk
 skafte75@hotmail.com
 skkh@jones.dk
+sm@jones.dk
 smedegaard@12move.dk
 snovz@hotmail.com
 spannung@post7.tele.dk
diff --git a/mailman/friends.py b/mailman/friends.py
index 79d7028..37cab57 100644
--- a/mailman/friends.py
+++ b/mailman/friends.py
@@ -1,5 +1,5 @@
 ## "friends" mailing list configuration settings -*- python -*-
-## captured on Thu Mar 11 02:10:40 2004
+## captured on Wed Mar 16 02:41:00 2005
 
 ## General options
 #
@@ -321,7 +321,7 @@ preferred_language = 'en'
 
 # These are all the natural languages supported by this list. Note that
 # the default language must be included.
-available_languages = ['en']
+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
@@ -855,8 +855,17 @@ from: .*@uplinkpro.com"""
 #    1 = "Yes"
 bounce_processing = 1
 
-# The maximum member bounce score before the member's subscription is
-# disabled.  This value can be a floating point number.
+# 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
diff --git a/mailman/info.members b/mailman/info.members
new file mode 100644
index 0000000..e69de29
--- /dev/null
+++ b/mailman/info.members
diff --git a/mailman/info.py b/mailman/info.py
new file mode 100644
index 0000000..c11f4b3
--- /dev/null
+++ b/mailman/info.py
@@ -0,0 +1,1236 @@
+## "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 8802446..839b49e 100644
--- a/mailman/mailman.py
+++ b/mailman/mailman.py
@@ -1,5 +1,5 @@
 ## "mailman" mailing list configuration settings -*- python -*-
-## captured on Thu Mar 11 02:10:41 2004
+## captured on Wed Mar 16 02:41:03 2005
 
 ## General options
 #
@@ -317,7 +317,7 @@ preferred_language = 'en'
 
 # These are all the natural languages supported by this list. Note that
 # the default language must be included.
-available_languages = ['en']
+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
@@ -693,7 +693,7 @@ reject_these_nonmembers = []
 # 
 # Add member addresses one per line; start the line with a ^ character
 # to designate a regular expression match.
-discard_these_nonmembers = ['bounce@gaintrafficfast.com', 'loteria_espana@zwallet.com', 'nijie101@fsmail.net']
+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
@@ -854,8 +854,17 @@ from: .*@uplinkpro.com"""
 #    1 = "Yes"
 bounce_processing = 1
 
-# The maximum member bounce score before the member's subscription is
-# disabled.  This value can be a floating point number.
+# 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
diff --git a/mailman/nilsstaerk.members b/mailman/nilsstaerk.members
index b87022c..3f97417 100644
--- a/mailman/nilsstaerk.members
+++ b/mailman/nilsstaerk.members
@@ -9,10 +9,12 @@ Christiane_Paul@whitney.org
 Clausbjerre@sol.dk
 Detroitmona@aol.com
 Diana_Pulling@moma.org
+Dr.Reinhold.Nagel.Praxis@telemed.de
 ErnestoPujol@aol.com
 FraserAR@aol.com
 HUO@compuserve.com
 Heike.Suetter@t-online.de
+Holckworld@get2net.dk
 Houhrparis@aol.com
 Infor@ingerlam.dk
 Jensina@mpiri.org
@@ -23,6 +25,8 @@ MArzak@guggenheim-bilbao.es
 Mail@peterfunch.com
 Manuel.E.Gonzalez@chase.com
 Maria_Montalva@moma.org
+MarieIrmgard@hotmail.com
+Martina.Weinhart@schirn.de
 Michael_hall@gmx.net
 Michel.ricard@culture.gouv.fr
 Miriam_Basilio@moma.org
@@ -33,12 +37,16 @@ PACOPE@teleline.es
 Phelguera@guggenheim.org
 Priamo@prodigy.net.mx
 RosenblumRb@netscape.net
+Sabine.oelze@onlinehome.de
 Stilling@generaldanmark.dk
+Thomas.Knaack@enskilda.dk
+Timhinman@hotmail.com
 Zdenka.Badovinac@mg-lj.si
 aa0email@yahoo.com
 aaronlevinelaw@aol.com
 abbeloos11@hotmail.com
 abildgaard@dca-cdb.dk
+acolvin2@earthlink.net
 adamjavlatham@hotmail.com
 adammcarr@hotmail.com
 ads2@nyu.edu
@@ -60,19 +68,26 @@ amattirolo@darc.beniculturali.it
 amcarlson@mindspring.com
 ames.afrique@wanadoo.fr
 amg@trivium.gh.ub.es
+ammitz.com@mail.dk
 anamc@w3art.es
 anders@arttactic.com
 anders@blaagaard.net
+anders@nymark.com
 anders_ellegaard@ofir.dk
 andrea.domesle@museumdermoderne.at
 andrea@jespersen.co.uk
 andrea@mfs.museum.no
 andrea@mso13.com
+andrew@andrewmummery.com
+andrewkreps@rcn.com
 anette.wingaard@skolekom.dk
 anettehansen@hotmail.com
 angelkal@adinet.com.uy
 anjafranke@e-kobenhavn.dk
+anna.holmbom@malmo.se
+anna@this.is
 annahermansson@hotmail.com
+anne.kielgast@mail.dk
 anne@senstad.com
 annebirte@artlink.no
 annickb@altern.org
@@ -86,6 +101,7 @@ art-venture@skynet.be
 art.stpdal@mail.tele.dk
 art@artpublic.ch
 artbox@hol.gr
+artiskok@webspeed.dk
 artluv6@aol.com
 artopia_net@yahoo.com
 artpublic@hotmail.com
@@ -93,10 +109,18 @@ asa.nacking@rooseum.se
 asa.nacking@swipnet.se
 asnigallery@telecom.net.et
 assistente@mam.org.br
+astrid_kruse_jensen@mail.dk
+astridlacour@hotmail.com
 athordal@hotmail.com
+audiovisuales.coordinacion.mncars@cars.mcu.es
+awieder@pro-qm.de
+axeliberti@hotmail.com
 b-guided@b-guided.com
+b.beutler@m-s-u.de
 b2dk@yahoo.fr
+bartschi@worldcom.ch
 batkin@bard.edu
+baungaard@mail.dk
 bellet@lemonde.fr
 benmonga@yahoo.fr
 benteelisabeth@private.dk
@@ -108,25 +132,35 @@ birgitteanderberg@mail.tele.dk
 bitsch@tdcadsl.dk
 bob@bobvanorsouw.ch
 bobokrabbe@hotmail.com
+bodild@dragoer.dk
+bogh@hum.ku.dk
 brammer@os.dk
 bryggebladet@mail.dk
+bt@danx.dk
+c.asprey1@ntlworld.com
 c.elgiz@tnn.net
 c_taplin@bellsouth.net
+cabs@dr.dk
+cal@kunststyrelsen.dk
 cameron@fuseproject.com
 camilla@aub.dk
+camillarohdemadsen@yahoo.co.uk
 camouflage@skynet.be
 can@kb.dk
 capsengirl@hotmail.com
 carlazaccagnini@yahoo.com.br
+carlchristian@jacc.dk
 carlesguerra@hotmail.com
 carlsonsarah81@hotmail.com
 carstenhall@go.com
 cascino6@hotmail.com
 catertoart@aol.com
+cb@nordeuropa.nu
 cba@vestkunst.dk
 cbasualdo@aol.com
 cbecker@artic.edu
 ceamon@frequencylabs.com
+cecid@bway.net
 cecilia.pereira.marimon@xunta.es
 ceinstein@daileyads.com
 cemetiah@indosat.net.id
@@ -136,41 +170,62 @@ charlotte.s@smk.dk
 charlotte.sprogoe@mail.dk
 charlotte.thiis.evensen@nrk.no
 charlotte@charlottenborg-art.dk
+charlotte@fjeldal.dk
 charlotteboudon@hotmail.com
 charlottekrenk@hotmail.com
 charlottmarkus@mail.com
 chat@afribone.net.ml
 chilie@post.tele.dk
+christa@charlottenborg-art.dk
+christian.damgaard@gmail.com
 christian@farmfreshfilms.com
 christian@skovbjerg.com
 christine.maes@gent.be
-christine@nilstaerk.dk
+christine@etnahem.com
+christineclemmesen@hotmail.com
 christoph.ruys@belgacom.net
+cjalving@hum.ku.dk
 cjennow@hotmail.com
 clairecanning@tankmagazine.com
+clau0111@hotmail.com
+claus.carstensen@pc.dk
+clausen@kunst.dk
 cleocaf@yahoo.com
 cmedin@yahoo.com
 columnadearena@hotmail.com
+contact@meyerkainer.at
+contact@paulknight.com.au
+contact@photography-now.com
 cooperhall@aol.com
 couchot@club-internet.fr
 cr253@columbia.edu
 cristianasartorio@opportunity4u.it
+cs@hummel.dk
 cs@vestkunst.dk
 cw@christinawilson.net
+cw@la-familia.dk
 d.dekerckhove@utoronto.ca
 d.elliott@mori.art.museum
+dack9245@aol.com
 dalgaspanda@yahoo.com
 dangermouse1@earthlink.net
+danpty@fastwebnet.it
 daross222@earthlink.net
+david@dlg-gallery.com
 davisof@get2net.dk
 db@damonbrandt.com
+dbeitzel@nyc.rr.com
 dboalds@ozcap.com
 dcameron@newmuseum.org
+dckr@novonordisk.com
 dcorrie@cisneros.com
 debliek@vmw.nl
 deliverance@dial.pipex.com
+deplacebjoern@hotmail.com
 derek@rammevaerk.dk
+design@jacobravn.com
 deste@idealcom.net
+dh@berlinbiennale.de
 dhenry@risd.edu
 diana@visao.com.br
 direccion.mncars@cars.mcu.es
@@ -183,20 +238,28 @@ doritma@t0.or.at
 dorte@nilsstaerk.dk
 dortehb@yahoo.dk
 dotkorn@gone.dk
+dplaton@brandeis.edu
 dr_ravn@hotmail.com
 dv@tdc.dk
 dvir_g@inter.net.il
+e-post@wanas.se
 e@katyasander.net
+eafrandsen@os.dk
 earmstrong@ocma.net
 eb@brandstrup.no
 ebbe_stub@hotmail.com
 edith@lacoleccionjumex.org
 editor@indexmagazine.com
+ef@djh.dk
+efeuerhake@chiledk.dk
+eggesboe@hotmail.com
 ehalpryn@twinvestment.com
 eimas@malba.org.ar
 eis.bonde@mail.tele.dk
 eis@gimm-eis.com
 eivind@fotogalleriet.no
+eivind@standardart.no
+eivindlentz@hotmail.com
 ejoo69@hotmail.com
 ejoo@calarts.edu
 ejoo@socrates.berkeley.edu
@@ -206,13 +269,19 @@ elbab@retemail.es
 eleni.x@eudoramail.com
 elf.langsted@get2net.dk
 elg@mail.tele.dk
+elisabeth.byre@chello.no
 elisabeth.harmitt@oamp.fr
 els@hanappe.com
+email@stereobar.dk
 emif@micronet.it
+emma.lequeux@free.fr
 enarmstrong@cox.net
 enrique.juncosa@modernart.ie
+eriksenpeter@mail.dk
+eriksteffensen@mail.dk
 ernandez@wanadoo.es
 eva@sggallery.com
+eva@svanenet.dk
 evaskibsted@hotmail.com
 ewehrmann@gmx.de
 fabiofaisal@hotmail.com
@@ -220,23 +289,40 @@ fashionfood@myself.com
 fchaimovich@hotmail.com
 fer_inc@hotmail.com
 ferariarte@tin.it
+ferdinand@muter.dk
+fietanderup@hotmail.com
+finn.agger@private.dk
 finnbogi@finnbogi.com
+finnbrod@khio.no
+fmaufras@mageos.com
+foghmar@hum.ku.dk
+forbath@yahoo.dk
 forest@imaginet.fr
+forsyningsmodul@hotmail.com
 fos@city.dk
+francesca.pia@bluewin.ch
+frank.gerritz@gmx.de
 frank_franzen@hotmail.com
+fransjacobi@tdcspace.dk
 frellsen@hotmail.com
 fridacornell@hotmail.com
 fridakahlo@guerrillagirls.com
+fuji@bennedsen.dk
 galegro@data.net.mx
+galeria@espaciominimo.com
 galeria@helgadealvear.net
 galeria@olivarauna.com
 galerialuisserpa@mail.telepac.pt
+galerie-beckers@t-online.de
 galerie-graesslin@t-online.de
 galerie.beckers@t-online.de
 galerie.neu@snafu.de
 galerie@de-expeditie.com
 galerie@krobathwimmer.at
 galeriegraesslin@compuserve.com
+galerieneff@t-online.de
+galleri@bouhlou.no
+galleri@susanneottesen.dk
 galleriaminini@numerica.it
 galleriarubin@libero.it
 gallery@praz-delavallade.com
@@ -246,21 +332,26 @@ gbuntix@hotmail.com
 gdt@mail.dk
 gemma.testa@libero.it
 gen@cca-glasgow.com
+gerd.laugesen@jp.dk
 gewi@tiscali.dk
 gfonti@tin.it
 gg@guerrillagirls.com
+giannimercurio@libero.it
 gimm@gimm-eis.com
+ginatornatore@btinternet.com
 gitte.tjellesen@skolekom.dk
 gitteoglars@get2net.dk
 glinder@tiscali.net
 gny@dav.egmont.com
 gorm@mbox301.get2net.dk
 goski@sol.dk
-gperezb@mail.utexas.edu
 gr@postmedia.net
+graffenried@steinlex.ch
 granat@kagsaa.dk
+groennov@mobilixnet.dk
 grosenbe@iupui.edu
 grynet76@hotmail.com
+gudrunand@yahoo.com
 gunnar@kjems.com
 gustavomarrone.arte@b-guided.com
 habres@nacpool.at
@@ -268,22 +359,34 @@ halbergemilie@hotmail.com
 halldor@netcom.ca
 hanaltc@hotmail.com
 hanuta77@hotmail.com
-havetraktor@nilsstaerk.dk
 hb@emerge.dk
 heide.kramer@basis-wien.at
 heike.munder@mgb.ch
 helene.mustad@artlink.no
+helga-marie@nordby.to
 helle-peter@get2net.dk
 helle.qvistgaard@smk.dk
 helle_sommer@hotmail.com
 helleland@hotmail.com
 henar@helgadealvear.net
 henbie@hotmail.com
+hennadeluxe@cool.dk
+henningschultz@hotmail.com
+henrik@norholt.dk
+hh@brandeddesign.dk
+hhf@city.dk
+hjordisa@mac.com
 hjort@hum.auc.dk
+hk@dyrbergkern.com
+hlaura@hum.ku.dk
+hnr@codan.dk
 hoffmann@sophie-gips.de
 honor@gagosian.com
+horst.koehn@wienkav.at
 hotlot1@hotmail.com
+hughiebb@aol.com
 ibp@berlingske.dk
+idak@fotogalleriet.no
 idaunsgaard@hotmail.com
 ihansen@ingridhansengallery.com
 info@annetgelink.com
@@ -292,40 +395,66 @@ info@arsfutura.com
 info@artagents.de
 info@artecontexto.com
 info@cca-glasgow.com
+info@elasticprojects.org
+info@fondazionemarconi.org
 info@frithstreetgallery.com
 info@galeriat4.com
+info@galleriafrancescakaufmann.com
+info@galleriasogospatty.com
 info@gallericharlottelund.com
+info@galleriflach.com
 info@giomarconi.com
 info@hammersidi.com
 info@i8.is
 info@kug.dk
 info@marcovigo.com
 info@maxprotetch.com
+info@mexican-embassy.dk
 info@mobilehomegallery.com
 info@modernartinc.com
 info@nicolafornello.com
 info@outlook.gr
 info@patrickseguin.com
+info@rubin-stuk.dk
 info@soniarosso.com
 info@suite106.com
 info@thetownhousegallery.com
+info@trondhugo.no
+info@uks.no
 infocav@cav.net4b.pt
+infos@jousse-enterprise.com
+ingeborg@shinegallery.co.uk
+irinairina@hotmail.com
+izumi@yahoo.it
 j.skjoldborg@mail.dk
 jacobfabricius@wanadoo.dk
+jacobrantzau@hotmail.com
+jacobweinberger@adr.dk
 jade@dr.dk
+jahn@wkv-stuttgart.de
+jakob_witt@hotmail.com
 jakobjakobsen@adr.dk
+jakobjensen@gmx.net
 jalvaer@yahoo.com
 jandol@get2net.dk
 jane.burton@tate.org.uk
 jane.burton@virgin.net
+janmot@skynet.be
+janne@jacc.dk
 jasonrubell@rubellhotels.com
 jbchristensen@dlf.org
+jbh@oem.dk
 jc@dlf.org
+jdconley@bellsouth.net
 jdurana@artium.org
 jegerjulia@hotmail.com
 jelkins@artic.edu
+jens.jacobsen@ft.dk
+jeppehein@web.de
+jer@kb.dk
 jesper@artaround.com
 jesper@nilsstaerk.dk
+jf@spacepoetry.dk
 jfdr@eresmas.net
 jhanhardt@earthlink.net
 jhanhardt@guggenheim.org
@@ -342,39 +471,54 @@ joel@interimart.net
 john@baldessari.org
 jonekvie@telia.com
 jonfp@mail1.stofanet.dk
+jose@kurzimanzutto.com
 jphol@hotmail.com
 jputnam@british-museum.ac.uk
 jrocaaco@banrep.gov.co
+jspensieri@corestrategies.com
 jt@dtv.dk
+jth@sollerod.dk
 juanmartinprada@w3art.es
 jucarpa@inwind.it
 judelson@i-20.com
+judith.quentel@fracdespaysdelaloie.com
 julie.damgaard@tdcadsl.dk
 julieta68@bellsouth.net
 julieta68@yahoo.com
 jvaliaga@hotmail.com
+jw@cphid.dk
+k.bjerrekaer@oncable.dk
 kaj.nyborg.isoplant@teliamail.dk
 kaldender@kopenhagen.dk
 kantorart@earthlink.net
 karaoke@karaoke.dk
 karen.lohrmann@berlin.de
 karro_p@hotmail.com
+kasparoppen@yahoo.com
+kasper@pp.dk
 katalog@brandts.dk
 katerinagregos@hotmail.com
 katharsis_arts@hotmail.com
+katja@casa.as
 katja@it-c.dk
 katja@pp.dk
 kayxmellish@yahoo.com
+kb@dynaudio.dk
 kea@post5.tele.dk
 keli.esja@wanadoo.nl
+kellykyst@hotmail.com
 kerstin.knepper@tate.org.uk
+kf@kunstforeningen.dk
 kim@kbvin.com
 kim@ndreasen.private.as
+kipo@kipo.dk
+kirse.junge-stevnsborg@helsingborg.se
 kirsi.vakiparta@av-arkki.fi
 kirsten.mathiesen@jp.dk
 kjelman@online.no
 kkanatani@guggenheim.org
 kkern@worldonline.dk
+kkr@codan.dk
 koenig@museum-ludwig.de
 kolovskaya@proarte.ru
 konjitseyoum@hotmail.com
@@ -384,47 +528,70 @@ krag_egemose@email.dk
 krisni77@hotmail.com
 kristian@online.no
 kristinask@gmx.net
+kristoferpaetau@web.de
 krueger@rpi.edu
+ks@kunststyrelsen.dk
 kthejll@image.dk
 kultur@dr.dk
+kunst.kultur@borsen.dk
+kunst@listserv.hum.ku.dk
 kystol@hotmail.com
 l.jakob@mail.dk
+la@livingarch.com
 laneeley@adelphia.net
 laneeley@mac.com
 lar@ntadvokater.dk
+lars.nilsson@khm.lu.se
 lars@textkontor.dk
 lauraskoler@aol.com
+le@erhvervsraadet.dk
 leeagibstein@yahoo.com
 leeagibsteinmd@yahoo.com
 leif@hoexbroe.dk
 leif_78@hotmail.com
 leif_M_Tangen@yahoo.no
 lemans@vmw.nl
+lemmerz@wake.dk
 lenbroch@12move.dk
+lengel@ifi.ku.dk
 leopar@tin.it
 lh@fs.dk
+li@pol.dk
 liamgillick@compuserve.com
 lieberaxel@telia.com
+liliana@swipnet.se
+line.jannik@elvis.dk
+line.rosenvinge@mail.dk
+line.voutsinos@privat.dk
 linetindkristensen@hotmail.com
 linus.voncastelmur@cop.rep.admin.ch
 lis@kunde.dk
+lisa_flood_@hotmail.com
 liseharlev@gmx.net
+lisette_ve@hotmail.com
+lisjan@webspeed.dk
+listen@listen.no
 litvinenkova@proarte.ru
 liz@pennymccallfoundation.org
 llagnado@nw.com.br
+lmiller@fluentcollab.org
 lone@jones.dk
-lone@nilsstaerk.dk
 lonedan@centrum.dk
 lose@postman.dk
+lotte.n@dgmedia.dk
 lottenburger@worldonline.dk
 lphillips@newmuseum.org
 lst@arkmail.dk
+luchal@iol.it
+luisa@franconoero.com
 luisahedo@telefonica.net
+lutzachill@gmx.de
 lwaters@berkeleyrep.org
 lzippay@eai.org
 m.gestsson@ntlworld.com
 m.kataoka@mori.art.museum
 m.m.basilio@att.net
+maaretta.jaukkuri@kit.ntnu.no
 mads@dadlnet.dk
 magdacurator@yahoo.com
 magdflur@cubarte.cult.cu
@@ -433,38 +600,60 @@ mail@daedala.com
 mail@dittebolt.dk
 mail@epi-gram.com
 mail@galleriamaze.it
+mail@janfalkborup.net
+mail@mcortmann.dk
+mail@millikengallery.com
+mail@mogadishni.com
 mail@re-magazine.com
-mail@stathatos.net
+mail@ronnierocket.com
 mail@themoderninstitute.com
+mail@thomasandersen.dk
 mailkim@kimsmai.com
 maillistetest@nilsstaerk.dk
+maj.allin@austrade.gov.au
 majbritt.loeland@privat.dk
+malene_ratcliffe@webspeed.dk
 mam.presidencia@mam.org.br
 mamilliet@uol.com.br
+mancus@volny.cz
 mangerman@hotmail.com
+manucerda@hotmail.com
 map@pls.dk
 margrit.brehm@museumdermoderne.at
 mari.s@online.no
 mari.shaw@obermayer.com
+maria.angerman@welho.com
+maria.borja@dagbladet.no
 marialuzcardenas@cantv.net
 marianne.torp@smk.dk
 mariannejarolics@web.de
 maribus@hotmail.com
 mariebuskov@ofir.dk
+mark.oedum@tietoenator.com
 marlene-ninabeth-skouboe@mail.dk
+martin.schwander@bluewin.ch
 martin@drdante.dk
 maryann@insite2000.org
 matcook@matcook.homechoice.co.uk
+mathias_seeberg@hotmail.com
 mats.eriksson@brevet.nu
 matthew@frieze.com
+matti.bekkevold@pol.dk
+me@thorbjoernkoenig.com
+melissaneumann@verizon.net
 mepacheco@malba.org.ar
 meraso@kultura.gipuzkoa.net
 mestrom@mindspring.com
 mette@aok.dk
 mette@skjoedt.com
+mia@fryland.org
+michaelbach@wanadoo.es
 michaelrooks@earthlink.net
+mikael.petersen@barclayscapital.com
 mikeskovgaard@hotmail.com
+milovanfarronato@hotmail.com
 milu@itau.com.br
+mirandavcm@yahoo.com.mx
 mkrichman@insite2000.org
 mlubar@earthlink.net
 mmanuel47@aol.com
@@ -472,43 +661,61 @@ mn@waffel.dk
 mollefc@hotmail.com
 monica@gjesdal.larsen.ms
 morelllars@hotmail.com
+morten.boye@get2net.dk
 mortenkirk9@hotmail.com
+mortenvammen@gmail.com
+mosholt@mail.dk
 mosvold@kool.no
+mow@swissinstitute.net
 mponsa.fundacio@lacaixa.es
 mrooks@tcmhi.org
 mrush@palmbeachica.org
+mss@kvuc.dk
 mt2187@columbia.edu
 mtho@dr.dk
 musbh@horsens.dk
+nadja@reflexioner.org
 napoleo@iname.com
 nathalie.oliveira@culture.gouv.fr
 nce@concorde-us.com
 nextsaturday@yahoo.com
 nicmed@yahoo.com
 niklas@vonbartha.com
+nils@drylab.no
 nils@nilsstaerk.dk
 nilsj@krafwerk.no
-nilsstaerk@kunst.dk
 nindityo@yahoo.com
+ninechristensen@hotmail.com
 nith@dr.dk
+nivagrill@aol.com
 njullien@noos.fr
 nmirzoeff@notes.cc.sunysb.edu
 noel@jacobnoel.dk
+nourbakhsch@t-online.de
+nsc@ddc.dk
+nstrands@online.no
 nw@nicolaiwallner.com
 ockenholt@wanadoo.dk
 ofa@3falke.dk
 office@brandstromstene.se
 office@klosterfelde.de
+office@nu-e.nu
 office@schipper-krome.com
 oguibe@camwood.org
 ohs@mail.dk
+oldorp@xs4all.nl
 oldspice90@hotmail.com
+ole_bundgaard@ofir.dk
 orandi@skill.com.br
+orkr@dr.dk
 orod1313@hotmail.com
 osvaldito@cox.net
+otto.rydbeck@setterwalls.se
 p_kapperwilliams@hotmail.com
 panaesthetik@lycos.com
+patric@moreau.se
 patricia-o@mail.dk
+pe@louisiana.dk
 pedro@trucatriche.com
 pedroalonzo@hotmail.com
 pedrosa.adriano@uol.com.br
@@ -522,16 +729,24 @@ per.andreasen@tacky.dk
 per@flydal.no
 perch@dadlnet.dk
 perezoramas@vzavenue.net
+pernille@thura.com
+pernillegrane@aol.com
+peter.friis@mercuriurval.com
 peter.rohleder@lavandoo.com
 peter@alpgallery.com
+peter@lind-damkjaer.dk
+petercallesen@yahoo.com
 peterdoroshenko@mac.com
 peterhaisler@get2net.dk
+petermw@dgh.dk
 petter@gpchannel.com
 petter@mediafront.no
 petter@snare.no
+pf@abmosegaarden.dk
 pf@bruunsbazaar.com
 pgarciavelez@efcholdings.com
 phelguera@aol.com
+philip.nelson@galerie-nelson.com
 photo@artists.fi
 pia.kristoffersson@chello.se
 piras.michelle@libero.it
@@ -541,20 +756,33 @@ plh@framfab.dk
 pm154@columbia.edu
 pmacalau@harbourfront.on.ca
 pmartin@lacoleccionjumex.org
+pontus.kyander@svt.se
+pontusky@yahoo.se
 post@ffkd.dk
+pr@rosendahls.dk
 pr@silkeborg-gym.dk
 prcact@hol.gr
 press@outlook.gr
 prh6@neosoft.com
+pri@svane.com
+programme@balticmill.com
 projecto@mindspring.com
+ps@kunstforeningen.dk
 pschou@post7.tele.dk
+pst@eb.dk
 ptst@dadlnet.dk
+pwamby@yahoo.dk
 r01sbp@af-dk.dk
 ramon.esparza@euskalnet.net
+ratio3@mac.com
 raucciesantamaria@interfree.it
+raymoon@niew.nl
 rbasha@tfaa.org
 rcembalest@artnewsonline.com
 rebeca@noguerasblanchard.com
+redaktion@bryggebladet.dk
+redaktion@lettre.dk
+redaktion@oxygenavis.dk
 reginebasha@hotmail.com
 regkunst@uol.com.br
 reviews@frieze.com
@@ -563,26 +791,36 @@ rhill@guggenheim.org
 ricardo@amaste.com
 richarddorment@dial.pipex.com
 rikke@artlover.com
+rikke@kridt.biz
+ritterzamet@blueyounder.co.uk
 rivalowe@mindspring.com
 rlowe@projectrowhouses.org
 rmalina@ssl.berkeley.edu
 rmoss2100@aol.com
+roald-dy@frisurf.no
+rob@modernartinc.com
 robert.rosenblum@nyu.edu
 robert@filler.demon.co.uk
 roberta.furcolo@libero.it
+roberto.furcolo@libero.it
 robertobertacc@tin.it
 robertsandtilton@earthlink.net
 roderic@rodericsteinkamp.com
 rosa@rosamartinez.com
+rosamund@gte.net
 rosmith@nytimes.com
 rossellaterzolo@hotmail.com
 rromero@cisneros.com
+rspeyer@tishmanspeyer.com
+rthorisson@yahoo.com
+rui@ard-system.com
 rwasko@muzart.infocentrum.com
 s.win@tdcadsl.dk
 sabinespaehn@hotmail.com
 saibottt@hotmail.com
 sallyt@serpentinegallery.org
 sandra@transmag.org
+sara@christinawilson.net
 saskia79@yahoo.com
 sbm5@cornell.edu
 schachter@mindspring.com
@@ -590,6 +828,7 @@ schivara@mcachicago.org
 scuesta@w3art.es
 sedrul@grn.es
 seeart@pacbell.net
+sehsan@web.de
 senebetennelse@hotmail.com
 serexhe@zkm.de
 sevgiz@ttnet.net.tr
@@ -597,41 +836,62 @@ sfk.sebastian.deisen@t-online.de
 shannon.fitzgerald@contemporarystl.org
 shirley_suki_1981@yahoo.com.hk
 signal.galleri@swipnet.se
+signe@storstein.dk
 signen@tiscali.dk
 sigveland@hotmail.com
 simon.njami@free.fr
 simon@metamute.com
 simone.molitor@bancosantos.com.br
+simone@303gallery.com
+simonmoller@hotmail.com
 sjmw@wxs.nl
 smallin@artic.edu
 smarchan@fsof.uned.es
 snozke@hotmail.com
+snutarm@hotmail.com
+soerensiggaard@yahoo.dk
+sofiethorsen@web.de
 sonia@colors.it
+sophienholm@sophienholm.dk
 sophiepucill@hotmail.com
+sorenbisgard@hotmail.com
 staffan_boije@yahoo.com
-stathatos@daedala.com
+stauning@aol.com
+steenson.hjortsoe@get2net.dk
 steffen@steffenmartin.dk
 steinunn@amp.is
 stelarc@va.com.au
 stellasig70@hotmail.com
+sten.faerch.jensen@bryggemail.dk
 stenka@fald.dk
 stephan.granhaug@schibsted.no
+steve.wilson@chevrontexaco.com
 stf913@hotmail.com
 stmiller@hiwaay.net
 straede@vip.cybercity.dk
 strousa@yahoo.com
+sus.petersen@oncable.dk
+susgre@sol.dk
 sylvie_betard@hotmail.com
+sylviebetard@noos.fr
 t.gammelgaard@mail.dk
 t.nagano@mori.art.museum
+tb@eventforce.dk
 tbeck@mobilixnet.dk
 tbrugera@cubarte.cult.cu
 tbruguera@aol.com
 tchiarelli@uol.com.br
+tdy@novo.dk
+tellmemore@theshowroom.org
 teraqueiroz@hotmail.com
+terje@sandengen.dk
 therese12@hotmail.com
+thomas.locher@t-online.de
+thomas.miessgang@kunsthallewien.at
 thomas@ovlisen.com
 thyrahilden@hotmail.com
 tiloschulz@hotmail.com
+tim@voldsted.dk
 tine.orth@arken.dk
 tinevindfeld@mail.tele.dk
 tmch@mail.dk
@@ -640,13 +900,23 @@ toni@bigmagazine.com
 toqster@excite.com
 tore-bahnson@mobilixnet.dk
 torrente63@telefonica.net
+tow@berlingske.dk
+tra@budweg.com
 trine@isness.org
+trine@paintbox.dk
 trompetfisk@hotmail.com
+trude@officeline.no
 trude@oslokunstforening.no
 truls@diplomatique.net
+tsn@le34.dk
+tsultan@uh.edu
 u_fredriksson@hotmail.com
 ube@neg-micon.dk
+udsen@city.dk
 ulla@lyme.biz
+ulth-aarhus@fdir.dk
+umadsen@stofanet.dk
+unijoh@online.no
 urbanpurban@hotmail.com
 v.g@c.dk
 valentine@artasia.com.my
@@ -659,6 +929,7 @@ vitaminabc@mail.com
 vnoorthoorn@hotmail.com
 vnoorthoorn@malba.org.ar
 vp@museumhojskole.dk
+weinberger@adr.dk
 wjtm@uchicago.edu
 wlam@cubarte.cult.cu
 wstover@newmuseum.org
@@ -667,6 +938,9 @@ wyckhuys@hotmail.com
 xmel@xmel.com
 yamatomichael@earthlink.net
 ysg@nyc.rr.com
+yvonne.quirmbach@t-online.de
 zamudiotaylor@hotmail.com
 zaya-leo@eresmas.net
+zjer@nybolig.dk
 zorro8204@supereva.it
+zsp@mac.com
diff --git a/mailman/nilsstaerk.py b/mailman/nilsstaerk.py
index 63e1a87..f427431 100644
--- a/mailman/nilsstaerk.py
+++ b/mailman/nilsstaerk.py
@@ -1,5 +1,5 @@
 ## "nilsstaerk" mailing list configuration settings -*- python -*-
-## captured on Thu Mar 11 02:10:42 2004
+## captured on Wed Mar 16 02:41:04 2005
 
 ## General options
 #
@@ -246,7 +246,7 @@ respond_to_post_requests = 1
 # legal values are:
 #    0 = "No"
 #    1 = "Yes"
-emergency = 0
+emergency = 1
 
 # When a new member is subscribed to this list, their initial set of
 # options is taken from the this variable's setting.
@@ -317,7 +317,7 @@ preferred_language = 'en'
 
 # These are all the natural languages supported by this list. Note that
 # the default language must be included.
-available_languages = ['en']
+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
@@ -566,7 +566,7 @@ unsubscribe_policy = 0
 # 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 = []
+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.
@@ -682,7 +682,7 @@ hold_these_nonmembers = []
 # 
 # Add member addresses one per line; start the line with a ^ character
 # to designate a regular expression match.
-reject_these_nonmembers = []
+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
@@ -853,8 +853,17 @@ from: .*@uplinkpro.com"""
 #    1 = "Yes"
 bounce_processing = 1
 
-# The maximum member bounce score before the member's subscription is
-# disabled.  This value can be a floating point number.
+# 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
diff --git a/mailman/nord-utte.py b/mailman/nord-utte.py
index 6e971d7..0628dfa 100644
--- a/mailman/nord-utte.py
+++ b/mailman/nord-utte.py
@@ -1,5 +1,5 @@
 ## "nord-utte" mailing list configuration settings -*- python -*-
-## captured on Thu Mar 11 02:10:43 2004
+## captured on Wed Mar 16 02:41:05 2005
 
 ## General options
 #
@@ -317,7 +317,7 @@ preferred_language = 'en'
 
 # These are all the natural languages supported by this list. Note that
 # the default language must be included.
-available_languages = ['en']
+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
@@ -853,8 +853,17 @@ from: .*@uplinkpro.com"""
 #    1 = "Yes"
 bounce_processing = 1
 
-# The maximum member bounce score before the member's subscription is
-# disabled.  This value can be a floating point number.
+# 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
diff --git a/mailman/nyheder.py b/mailman/nyheder.py
index 47d855f..61e63ce 100644
--- a/mailman/nyheder.py
+++ b/mailman/nyheder.py
@@ -1,5 +1,5 @@
 ## "nyheder" mailing list configuration settings -*- python -*-
-## captured on Thu Mar 11 02:10:45 2004
+## captured on Wed Mar 16 02:41:06 2005
 
 ## General options
 #
@@ -319,7 +319,7 @@ preferred_language = 'en'
 
 # These are all the natural languages supported by this list. Note that
 # the default language must be included.
-available_languages = ['en']
+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
@@ -860,8 +860,17 @@ from: .*@uplinkpro.com"""
 #    1 = "Yes"
 bounce_processing = 1
 
-# The maximum member bounce score before the member's subscription is
-# disabled.  This value can be a floating point number.
+# 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
diff --git a/mailman/users.members b/mailman/users.members
index 63e57a4..4f86ef2 100644
--- a/mailman/users.members
+++ b/mailman/users.members
@@ -1,5 +1,6 @@
 agnes@jones.dk
 ai@jones.dk
+aj@jones.dk
 alboy@jones.dk
 alo@jones.dk
 alsinger@jones.dk
@@ -10,6 +11,7 @@ ann@jones.dk
 anne@jones.dk
 anwar@jones.dk
 ascanius@jones.dk
+assenbjerg@jones.dk
 awh@jones.dk
 banana@jones.dk
 benny@jones.dk
@@ -21,9 +23,10 @@ bolette@jones.dk
 borking@jones.dk
 bsi@jones.dk
 camilla@jones.dk
-ccl@jones.dk
+cfo@jones.dk
 chr.h@pobox.com
 chrois@jones.dk
+claude@jones.dk
 cm@jones.dk
 concept@jones.dk
 dewd@jones.dk
@@ -66,9 +69,9 @@ hvam@jones.dk
 id@jones.dk
 ida@jones.dk
 idaadm@jones.dk
+inarosing@jones.dk
 ingersme@jones.dk
 inuk@jones.dk
-it@jones.dk
 izi@jones.dk
 janus@netcetera.dk
 jas@jones.dk
@@ -80,6 +83,7 @@ jfe@jones.dk
 jgh@jones.dk
 jnj@jones.dk
 jo@jones.dk
+joachim@jones.dk
 jones@jones.dk
 jorgen@jones.dk
 joy@jones.dk
@@ -130,6 +134,7 @@ matti@jones.dk
 mayu@jones.dk
 melba@jones.dk
 michael@jones.dk
+miv@jones.dk
 mj@jones.dk
 mje@jones.dk
 mls@jones.dk
@@ -138,6 +143,7 @@ morgan@jones.dk
 morten@jones.dk
 mp@jones.dk
 mr@jones.dk
+nancy@jones.dk
 nanna@jones.dk
 negon@jones.dk
 nicolai@jones.dk
@@ -146,6 +152,7 @@ nils@jones.dk
 nina@jones.dk
 nors@jones.dk
 nrl@jones.dk
+ns@jones.dk
 obs@jones.dk
 ohms@jones.dk
 ole@jones.dk
@@ -155,6 +162,7 @@ paul@jones.dk
 pelle@jones.dk
 pepper@jones.dk
 per@jones.dk
+pernille@jones.dk
 pha@jones.dk
 pls@jones.dk
 propel@jones.dk
@@ -179,7 +187,9 @@ sg@jones.dk
 sine@jones.dk
 siri@jones.dk
 sita@jones.dk
+sj@jones.dk
 skkh@jones.dk
+sm@jones.dk
 soren@jones.dk
 stef@jones.dk
 steinbach@jones.dk
diff --git a/mailman/users.py b/mailman/users.py
index 6feff4f..7b05ec4 100644
--- a/mailman/users.py
+++ b/mailman/users.py
@@ -1,5 +1,5 @@
 ## "users" mailing list configuration settings -*- python -*-
-## captured on Thu Mar 11 02:10:46 2004
+## captured on Wed Mar 16 02:41:08 2005
 
 ## General options
 #
@@ -333,7 +333,7 @@ preferred_language = 'en'
 
 # These are all the natural languages supported by this list. Note that
 # the default language must be included.
-available_languages = ['en']
+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
@@ -867,8 +867,17 @@ from: .*@uplinkpro.com"""
 #    1 = "Yes"
 bounce_processing = 1
 
-# The maximum member bounce score before the member's subscription is
-# disabled.  This value can be a floating point number.
+# 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