Merge branch 'master' of coreander:/srv/git/source.jones.dk/local-BITBASE.DK

7 files changed, 2979 insertions, 251 deletions

diff --git a/amavis/local_domains b/amavis/local_domains
index f4dcbcb..b314285 100644
--- a/amavis/local_domains
+++ b/amavis/local_domains
@@ -1,6 +1,7 @@
 bitbase.dk
 friis-holm.dk
 himawari.dk
+list.artofhosting.org
 lists.jones.dk
 redpill.dk
 superserver.dk
diff --git a/bind/pri/artofhosting.org b/bind/pri/artofhosting.org
index a4b15a9..65e0637 100644
--- a/bind/pri/artofhosting.org
+++ b/bind/pri/artofhosting.org
@@ -1,6 +1,6 @@
 $TTL    3600
 @		SOA	ns.bitbase.dk.	teknik.bitbase.dk. (
-			2010111001	; serial
+			2010120801	; serial
 			3600		; refresh
 			1800		; retry
 			604800		; expire
@@ -12,9 +12,15 @@ $TTL    3600
 		A	81.95.247.21
 www		CNAME	cray.novicell.dk.
 cms		CNAME	cray.novicell.dk.
-list		A	193.162.142.149
-		MX 20	mx02.pil.dk.
-		MX 30	mx03.pil.dk.
+list		A	80.68.88.141
+		MX 10	mail.bitbase.dk.
+		MX 50	mail.jones.dk.
+		MX 50	mail.dgi-huset.dk.
+		MX 50	mail.homebase.dk.
+		SPF	"v=spf1 mx -all"
+*.list		A	80.68.88.141
+		MX 0	.
+		SPF	"v=spf1 -all"
 testlist	A	80.68.88.141
 		MX 10	mail.bitbase.dk.
 		MX 50	mail.jones.dk.
diff --git a/mailman/aoh.py b/mailman/aoh.py
new file mode 100644
index 0000000..3d2ebba
--- /dev/null
+++ b/mailman/aoh.py
@@ -0,0 +1,1307 @@
+# -*- python -*-
+# -*- coding: us-ascii -*-
+## "aoh" mailing list configuration settings
+## captured on Wed Dec  8 15:30:26 2010
+
+## 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 = 'aoh'
+
+# 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 = ['rowan@kaospilot.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 = 'Art of Hosting (censored, semi-public)'
+
+# The text will be treated as html except that newlines will be
+# translated to <br> - so you can use links, preformatted text, etc, but
+# don't put in carriage returns except where you mean to separate
+# paragraphs.  And review your changes - bad html (like some
+# unterminated HTML constructs) can prevent display of the entire
+# listinfo page.
+info = """Open list for Art of Hosting.
+<ul><li>Anyone can send to the list (non-text parts are stripped).
+<li>Posts are censored for relevancy (except from list members).
+<li>Anyone can subscribe to the list (only members can see member list).
+</ul>Access limitation to the archive avoids search engine registrations, but does not ensure discretion as anyone can gain access by subscribing.
+
+Censorship avoids some noise, but also increase risk of rejection or delay of legitimate posts: Please subscribe to the list and use your subscribed address as sender if you want delivery of your posts ensured."""
+
+# This text will be prepended to subject lines of messages posted to the
+# list, to distinguish mailing list messages in mailbox summaries.
+# Brevity is premium here, it's ok to shorten long mailing list names to
+# something more concise, as long as it still identifies the mailing
+# list. You can also add a sequential number by %d substitution
+# directive. eg.; [listname %d] -> [listname 123] (listname %05d) ->
+# (listname 00123)
+# 
+subject_prefix = '[aoh] '
+
+# 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.net/essays/reply-to.mhtml">Reply-To
+# Munging Considered Useful for a dissenting opinion.
+# 
+# Some mailing lists have restricted posting privileges, with a parallel
+# list devoted to discussions.  Examples are `patches' or `checkin'
+# lists, where software changes are posted by a revision control system,
+# but discussion about the changes occurs on a developers mailing list.
+# To support these types of mailing lists, select Explicit address and
+# set the Reply-To: address below to point to the parallel list.
+#
+# legal values are:
+#    0 = "Poster"
+#    1 = "This list"
+#    2 = "Explicit address"
+reply_goes_to_list = 0
+
+# This is the address set in the Reply-To: header when the <a
+# href="?VARHELP=general/reply_goes_to_list">reply_goes_to_list option
+# is set to Explicit address.
+# 
+# There are many reasons not to introduce or override the Reply-To:
+# header.  One is that some posters depend on their own Reply-To:
+# settings to convey their valid return address.  Another is that
+# modifying Reply-To: makes it much more difficult to send private
+# replies.  See <a
+# href="http://www.unicom.com/pw/reply-to-harmful.html">`Reply-To'
+# Munging Considered Harmful for a general discussion of this issue.
+# See <a
+# href="http://www.metasystema.net/essays/reply-to.mhtml">Reply-To
+# Munging Considered Useful for a dissenting opinion.
+# 
+# Some mailing lists have restricted posting privileges, with a parallel
+# list devoted to discussions.  Examples are `patches' or `checkin'
+# lists, where software changes are posted by a revision control system,
+# but discussion about the changes occurs on a developers mailing list.
+# To support these types of mailing lists, specify the explicit
+# Reply-To: address here.  You must also specify Explicit address in the
+# reply_goes_to_list variable.
+# 
+# Note that if the original message contains a Reply-To: header, it will
+# not be changed.
+reply_to_address = ''
+
+# 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 = """This is an open list for Art of Hosting.
+
+ * Anyone can send to the list (non-text parts are stripped).
+ * Posts are censored for relevancy (except from list members).
+ * Anyone can subscribe to the list (only members can see member list).
+
+Access limitation to the archive avoids search engine registrations, 
+but does not ensure discretion as anyone can gain access by subscribing.
+
+Censorship avoids some noise, but also increase risk of rejection or 
+delay of legitimate posts: Please subscribe to the list and use your 
+subscribed address as sender if you want delivery of your posts ensured.
+
+All emails are archived (only members can read the archive)."""
+
+# 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 = 1
+
+# Send mail to poster when their posting is held for approval?
+#
+# 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 = 0
+
+# Maximum length in kilobytes (KB) of a message body.  Use 0 for no
+# limit.
+max_message_size = 0
+
+# Maximum number of members to show on one page of the Membership List.
+admin_member_chunksize = 30
+
+# 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 = 'list.artofhosting.org'
+
+# 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
+
+# Discard held messages older than this number of days. Use 0 for no
+# automatic discarding.
+max_days_to_hold = 7
+
+## 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 = 'en'
+
+# These are all the natural languages supported by this list. Note that
+# the default language must be included.
+available_languages = ['da', 'de', 'en', 'es', 'fi', 'nl', 'no', 'pt_BR', 'sv']
+
+# If your mailing list's default language uses a non-ASCII character set
+# and the prefix contains non-ASCII characters, the prefix will always
+# be encoded according to the relevant standards.  However, if your
+# prefix contains only ASCII characters, you may want to set this option
+# to Never to disable prefix encoding.  This can make the subject
+# headers slightly more readable for users with mail readers that don't
+# properly handle non-ASCII encodings.
+# 
+# Note however, that if your mailing list receives both encoded and
+# unencoded subject headers, you might want to choose As needed.  Using
+# this setting, Mailman will not encode ASCII prefixes when the rest of
+# the header contains only ASCII characters, but if the original header
+# contains non-ASCII characters, it will encode the prefix.  This avoids
+# an ambiguity in the standards which could cause some mail readers to
+# display extra, or missing spaces between the prefix and the original
+# header.
+#
+# 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. This
+# text can include Python format strings which are resolved against list
+# attributes.  The list of substitutions allowed are:
+# 
+# 
+# real_name - The "pretty" name of the list; usually the list name with
+# capitalization.
+# 
+# list_name - The name by which the list is identified in URLs, where
+# case is significant.
+# 
+# host_name - The fully qualified domain name that the list server runs
+# on.
+# 
+# web_page_url - The base URL for Mailman.  This can be appended with,
+# e.g. listinfo/%(list_name)s to yield the listinfo page for the mailing
+# list.
+# 
+# description - The brief description of the mailing list.
+# 
+# info - The full description of the mailing list.
+# 
+# cgiext - The extension added to CGI scripts.
+# 
+# 
+msg_header = ''
+
+# Text appended to the bottom of every immediately-delivery message.
+# This text can include Python format strings which are resolved against
+# list attributes.  The list of substitutions allowed are:
+# 
+# 
+# real_name - The "pretty" name of the list; usually the list name with
+# capitalization.
+# 
+# list_name - The name by which the list is identified in URLs, where
+# case is significant.
+# 
+# host_name - The fully qualified domain name that the list server runs
+# on.
+# 
+# web_page_url - The base URL for Mailman.  This can be appended with,
+# e.g. listinfo/%(list_name)s to yield the listinfo page for the mailing
+# list.
+# 
+# description - The brief description of the mailing list.
+# 
+# info - The full description of the mailing list.
+# 
+# cgiext - The extension added to CGI scripts.
+# 
+# 
+msg_footer = """-- 
+%(real_name)s mailing list
+%(real_name)s@%(host_name)s
+%(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s"""
+
+# When you scrub attachments, they are stored in archive area and links
+# are made in the message so that the member can access via web browser.
+# If you want the attachments totally disappear, you can use content
+# filter options.
+#
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
+scrub_nondigest = 1
+
+# The list addresses should be written in full mail address format (e.g.
+# mailman@example.com). Do not specify this list address mutually in the
+# exclude list configuration page of the other list, or members of both
+# lists won't get any message. Note also that the site administrator may
+# prohibit cross domain siblings.
+regular_exclude_lists = []
+
+# The list addresses should be written in full mail address format (e.g.
+# mailman@example.com). Note also that the site administrator may
+# prohibit cross domain siblings.
+regular_include_lists = []
+
+## 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. This text can include Python format strings which
+# are resolved against list attributes.  The list of substitutions
+# allowed are:
+# 
+# 
+# real_name - The "pretty" name of the list; usually the list name with
+# capitalization.
+# 
+# list_name - The name by which the list is identified in URLs, where
+# case is significant.
+# 
+# host_name - The fully qualified domain name that the list server runs
+# on.
+# 
+# web_page_url - The base URL for Mailman.  This can be appended with,
+# e.g. listinfo/%(list_name)s to yield the listinfo page for the mailing
+# list.
+# 
+# description - The brief description of the mailing list.
+# 
+# info - The full description of the mailing list.
+# 
+# cgiext - The extension added to CGI scripts.
+# 
+# 
+digest_header = ''
+
+# Text attached (as a final message) to the bottom of digests. This text
+# can include Python format strings which are resolved against list
+# attributes.  The list of substitutions allowed are:
+# 
+# 
+# real_name - The "pretty" name of the list; usually the list name with
+# capitalization.
+# 
+# list_name - The name by which the list is identified in URLs, where
+# case is significant.
+# 
+# host_name - The fully qualified domain name that the list server runs
+# on.
+# 
+# web_page_url - The base URL for Mailman.  This can be appended with,
+# e.g. listinfo/%(list_name)s to yield the listinfo page for the mailing
+# list.
+# 
+# description - The brief description of the mailing list.
+# 
+# info - The full description of the mailing list.
+# 
+# cgiext - The extension added to 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://list.artofhosting.org/admin/aoh/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 = 0
+
+## Privacy options
+#
+# When a message is posted to the list, a series of moderation steps are
+# taken to decide whether 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://docs.python.org/library/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.  A line consisting of the @ character followed by a
+# list name specifies another Mailman list in this installation, all of
+# whose member addresses will be accepted for this list.
+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 = 1
+
+# Should messages from non-members, which are automatically discarded,
+# be forwarded to the list moderator?
+#
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
+forward_auto_discards = True
+
+# Text to include in any rejection notice to be sent to non-members who
+# post to this list. This notice can include the list's owner address by
+# %(listowner)s and replaces the internally crafted default message.
+nonmember_rejection_notice = ''
+
+## Privacy options
+#
+# 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 = 0
+
+## 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.
+# 
+# Note that headers are collected from all the attachments (except for
+# the mailman administrivia message) and matched against the regular
+# expressions. With this feature, you can effectively sort out messages
+# with dangerous file types or file name extensions.
+header_filter_rules = [('X-Spam-Status: Yes', 3, False)]
+
+# 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 = 1
+
+## 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.
+# 
+# <p> Then, each <tt>multipart/alternative</tt> section will be replaced
+# by just the first alternative that is non-empty after filtering if <a
+# href="?VARHELP=contentfilter/collapse_alternatives"
+# >collapse_alternatives</a> is enabled.
+# 
+# <p>Finally, any <tt>text/html</tt> parts that are left in the message
+# may be converted to <tt>text/plain</tt> if <a
+# href="?VARHELP=contentfilter/convert_html_to_plaintext"
+# >convert_html_to_plaintext</a> is enabled and the site is configured
+# to allow these conversions.
+
+# Should Mailman filter the content of list traffic according to the
+# settings below?
+#
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
+filter_content = False
+
+# 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 = ''
+
+# 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/signed
+multipart/mixed
+multipart/alternative
+application/pgp-signature
+application/pkcs7-signature
+text/plain"""
+
+# Remove message attachments that have a matching filename extension.
+filter_filename_extensions = """exe
+bat
+cmd
+com
+pif
+scr
+vbs
+cpl"""
+
+# Remove message attachments that don't have a matching filename
+# extension.  Leave this field blank to skip this filter test.
+pass_filename_extensions = ''
+
+# Should Mailman collapse multipart/alternative to its first part
+# content?
+#
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
+collapse_alternatives = True
+
+# Should Mailman convert text/html parts to plain text?  This conversion
+# happens after MIME attachments have been stripped.
+#
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
+convert_html_to_plaintext = True
+
+# One of these actions is taken when the message matches one of the
+# content filtering rules, meaning, the top-level content type matches
+# one of the <a href="?VARHELP=contentfilter/filter_mime_types"
+# >filter_mime_types, or the top-level content type does not match one
+# of the <a href="?VARHELP=contentfilter/pass_mime_types"
+# >pass_mime_types, or if after filtering the subparts of the message,
+# the message ends up empty.
+# 
+# Note this action is not taken if after filtering the message still
+# contains content.  In that case the message is always forwarded on to
+# the list membership.
+# 
+# When messages are discarded, a log entry is written containing the
+# Message-ID of the discarded message.  When messages are rejected or
+# forwarded to the list owner, a reason for the rejection is included in
+# the bounce message to the original author.  When messages are
+# preserved, they are saved in a special queue directory on disk for the
+# site administrator to view (and possibly rescue) but otherwise
+# discarded.  This last option is only available if enabled by the site
+# administrator.
+#
+# legal values are:
+#    0 = "Discard"
+#    1 = "Reject"
+#    2 = "Forward to List Owner"
+#    3 = "Preserve"
+filter_action = 1
+
+## Topics options
+#
+# List topic keywords
+
+# The topic filter categorizes each incoming email message according to
+# <a href="http://docs.python.org/library/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 2d8348a..3239ad5 100644
--- a/mailman/mailman.py
+++ b/mailman/mailman.py
@@ -1,18 +1,20 @@
-## Indstillinger for maillisten "mailman"  -*- python -*-
-## Dato: Tue Dec  5 14:55:07 2006
+# -*- python -*-
+# -*- coding: iso-8859-1 -*-
+## "mailman" maillistens indstillinger
+## fanget Wed Dec  8 11:38:32 2010
 
 ## General options
 #
-# Grundlæggende egenskaber for listen, herunder en beskrivelse af
+# Grundl&aelig;ggende egenskaber for listen, herunder en beskrivelse af
 # listen. 
 
-# Du kan f.eks. stave navnet med stort forbogstav eller ændre andre
-# bogstaver til store, s&aring; navnet bliver udtalt rigtigt eller at
-# forkortelser fremhæves. Bemærk at dette navn bruges i e-maillistens
-# adresse (f.eks. i bekræftelser ved tilmeldinger), s&aring; navnet kan
-# ikke ændres p&aring; nogen anden m&aring;de. (e-mailadresser er ikke
-# f&oslash;lsomme for store eller sm&aring; bogstaver, men de er
-# f&oslash;lsomme for n&aelig;sten alt andet :-)
+# Du kan f.eks. stave navnet med stort forbogstav eller &aelig;ndre
+# andre bogstaver til store, s&aring; navnet bliver udtalt rigtigt eller
+# at forkortelser fremh&aelig;ves. Bem&aelig;rk at dette navn bruges i
+# e-maillistens adresse (f.eks. i bekr&aelig;ftelser ved tilmeldinger),
+# s&aring; navnet kan ikke &aelig;ndres p&aring; nogen anden m&aring;de.
+# (e-mailadresser er ikke f&oslash;lsomme for store eller sm&aring;
+# bogstaver, men de er f&oslash;lsomme for n&aelig;sten alt andet :-)
 real_name = 'Mailman'
 
 # Der er to roller forbundet med hver mailliste. Listeadministratorerne
@@ -20,7 +22,7 @@ real_name = 'Mailman'
 # for maillisten. De kan &aelig;ndre alle indstillinger der er
 # tilg&aelig;ngelige via disse administrative websider.
 # 
-# Listemoderatorerne har begrænset adgang; de kan ikke ændre
+# Listemoderatorerne har begr&aelig;nset adgang; de kan ikke &aelig;ndre
 # indstillinger for e-maillisten, men de kan tage sig af anmodninger i
 # forbindelse med listen, f.eks. anmodning om medlemskab, eller
 # godkende/afvise meddelelser der skal godkendes for at kunne udsendes
@@ -31,14 +33,14 @@ real_name = 'Mailman'
 # den m&aring;de fordele arbejdsopgaverne i forbindelse med listen, skal
 # du anf&oslash;re din egen moderatoradgangskode, og angive
 # e-mailadresser for den/dem som skal v&aelig;re listemoderator(er).
-# Bemærk at i tekstboksene nedenfor skal du skrive e-mailadresser for
-# listeadministratorer.
-owner = ['postmaster@bitbase.dk']
+# Bem&aelig;rk at i tekstboksene nedenfor skal du skrive e-mailadresser
+# for listeadministratorer.
+owner = ['listmaster@jones.dk']
 
 # Der er to ejer-roller forbundet med hver mailliste.
 # Listeadministratorerne er dem der har den endelige kontrol over alle
 # indstillingerne for e-mallisten. De kan &aelig;ndre alle indstillinger
-# der er tilgængelige via disse administrative websider.
+# der er tilg&aelig;ngelige via disse administrative websider.
 # 
 # Listemoderatorerne har begr&aelig;nset adgang; de kan ikke &aelig;ndre
 # indstillinger for e-maillisten, men de kan tage sig af anmodninger
@@ -51,7 +53,7 @@ owner = ['postmaster@bitbase.dk']
 # den m&aring;de fordele arbejdsopgaverne i forbindelse med listen, skal
 # du anf&oslash;re din egen moderatoradgangskode, og indtaste
 # e-mailadresser for den/dem der skal v&aelig;re listemoderatore(r).
-# Bemærk, at i tekstboksene nedenfor skal du skrive listemoderator
+# Bem&aelig;rk, at i tekstboksene nedenfor skal du skrive listemoderator
 # e-mailadresse(r).
 moderator = []
 
@@ -62,38 +64,42 @@ moderator = []
 description = ''
 
 # Teksten tolkes som html bortset fra linieskift, der vil blive
-# &aelig;ndret til html-tag'et '<br>', sådan at du kan benytte links,
-# forh&aring;ndsformateret tekst, osv. Men brug alts&aring; kun
+# &aelig;ndret til html-tag'et '<br>', s&aring;dan at du kan benytte
+# links, forh&aring;ndsformateret tekst, osv. Men brug alts&aring; kun
 # linieskift der hvor du vil have et nyt afsnit. V&aelig;r meget
 # omhyggelig, hvis du benytter html-kode. Fejl (f.eks. manglende
 # slut-tag's) kan f&oslash;re til at listens informationsside ikke
 # bliver vist s&aring;dan som den skal.
 info = ''
 
-# This text will be prepended to subject lines of messages posted to the
-# list, to distinguish mailing list messages in in mailbox summaries.
-# Brevity is premium here, it's ok to shorten long mailing list names to
-# something more concise, as long as it still identifies the mailing
-# list.
+# Denne tekst vil blive placeret foran emnet i mails sendt til listen
+# for nemmere og kunne skelne mail fra listen i indboksen i
+# postprogrammet. Teksten b&oslash;r holdes kort. Det er iorden og
+# sk&aelig;re et langt listenavn ned til et mere kortfattet navn
+# s&aring;l&aelig;nge det stadig er beskrivende for listen. Du kan
+# ogs&aring; tilf&oslash;je et fortl&oslash;bende nummer ved at bruge %d
+# substitutions direktivet f.eks. [listenavn %d] -> [listenavn 123]
+# (listenavn %05d) -> (listenavn 00123)
+# 
 subject_prefix = '[Mailman] '
 
 # Skjul afsenderen af meddelelser, ved at erstatte den med e-maillistens
-# adresse (Dette medfører at alle From:, Sender, og Reply-To: felter
-# fjernes)
+# adresse (Dette medf&oslash;rer at alle From:, Sender, og Reply-To:
+# felter fjernes)
 #
 # gyldige værdier:
 #    0 = "Nej"
 #    1 = "Ja"
-anonymous_list = 0
+anonymous_list = False
 
 # Skal eksisterende Reply-To: felt i brevhovedet fjernes? Hvis ja, vil
-# dette blive gjort uanset om Mailman tilføjer et Reply-To: felt eller
-# ikke.
+# dette blive gjort uanset om Mailman tilf&oslash;jer et Reply-To: felt
+# eller ikke.
 #
 # gyldige værdier:
 #    0 = "Nej"
 #    1 = "Ja"
-first_strip_reply_to = 0
+first_strip_reply_to = False
 
 # Denne indstillling fort&aelig;ller hvad Mailman skal g&oslash;re med
 # Reply-To: feltet i brevhovedet p&aring; e-mail der sendes til listen.
@@ -119,7 +125,7 @@ first_strip_reply_to = 0
 # af programmet sendes til udviklernes egen mailliste. For at
 # underst&oslash;tte lignende e-maillister, v&aelig;lg Egendefineret
 # adresse og s&aelig;t Reply-To: adressen i indstillingen
-# reply_to_address til at pege på den parallelle diskussionsliste.
+# reply_to_address til at pege p&aring; den parallelle diskussionsliste.
 #
 # gyldige værdier:
 #    0 = "Afsender"
@@ -140,12 +146,12 @@ reply_goes_to_list = 0
 # temaet. Se Reply-To Munging Considered Useful for modsatte meninger.
 # 
 # Nogle maillister har begr&aelig;nset adgang, med en egen parallel
-# liste beregnet for diskussioner. Eksempler p&aring; dette er 'patches'
+# liste beregnet til diskussioner. Eksempler p&aring; dette er 'patches'
 # eller 'checkin' lister, som system for revisionskontrol sender
 # &aelig;ndringer i programmet til, mens diskussioner omkring udvikling
 # af programmet sendes til udviklernes egen mailliste. For at
 # underst&oslash;tte s&aring;danne maillister, kan du definere Reply-To:
-# adressen her, og vælge Egendefineret adresse i indstillingen
+# adressen her, og v&aelig;lge Egendefineret adresse i indstillingen
 # reply_goes_to_list.
 # 
 # Bem&aelig;rk at hvis den oprindelige meddelelse indeholder et
@@ -162,7 +168,7 @@ reply_to_address = ''
 # gyldige værdier:
 #    0 = "Nej"
 #    1 = "Ja"
-umbrella_list = 0
+umbrella_list = False
 
 # N&aring;r "umbrella_list" indikerer at denne liste har andre
 # maillister som medlemmer, skal administrative meddelelser som f.eks.
@@ -208,7 +214,7 @@ welcome_msg = ''
 # gyldige værdier:
 #    0 = "Nej"
 #    1 = "Ja"
-send_welcome_msg = 1
+send_welcome_msg = True
 
 # Tekst der sendes til medlemmer der framelder sig listen. Hvis feltet
 # er tomt, tilf&oslash;jes der ikke nogen speciel tekst til
@@ -220,7 +226,7 @@ goodbye_msg = ''
 # gyldige værdier:
 #    0 = "Nej"
 #    1 = "Ja"
-send_goodbye_msg = 1
+send_goodbye_msg = True
 
 # Der udsendes en p&aring;mindelse til listemoderator (og
 # listeadministrator) dagligt om anmodninger der af en eller anden grund
@@ -231,7 +237,7 @@ send_goodbye_msg = 1
 # gyldige værdier:
 #    0 = "Nej"
 #    1 = "Ja"
-admin_immed_notify = 1
+admin_immed_notify = True
 
 # Skal listeadministrator modtage meddelelse om tilmeldinger og
 # afmeldinger?
@@ -239,30 +245,31 @@ admin_immed_notify = 1
 # gyldige værdier:
 #    0 = "Nej"
 #    1 = "Ja"
-admin_notify_mchanges = 0
+admin_notify_mchanges = False
 
-# Approval notices are sent when mail triggers certain of the limits
-# except routine list moderation and spam filters, for which notices are
-# not sent.  This option overrides ever sending the notice.
+# Send e-mail til afsendere n&aring;r deres e-mail til listen holdes
+# tilbage for godkendelse?
 #
 # gyldige værdier:
 #    0 = "Nej"
 #    1 = "Ja"
 respond_to_post_requests = 1
 
-# Når dette valg er aktiveret, vil al e-mail til listen blive modereret.
-# Dette valg kan være nyttigt når din mailliste f.eks. har en såkaldt
-# "flamewar", altså en "krig" hvor medlemmer kun skælder ud på hinanden.
-# En "nød-moderering" kan da hjælpe dig at fjerne usaglige meddelelser
-# til listen, og på den måde dysse en ophedet diskussion ned.
+# N&aring;r dette valg er aktiveret, vil al e-mail til listen blive
+# modereret. Dette valg kan v&aelig;re nyttigt n&aring;r din mailliste
+# f.eks. har en s&aring;kaldt "flamewar", alts&aring; en "krig" hvor
+# medlemmer kun sk&aelig;lder ud p&aring; hinanden. En
+# "n&oslash;d-moderering" kan da hj&aelig;lpe dig at fjerne usaglige
+# meddelelser til listen, og p&aring; den m&oslash;de dysse en ophedet
+# diskussion ned.
 #
 # gyldige værdier:
 #    0 = "Nej"
 #    1 = "Ja"
 emergency = 0
 
-# Når et nyt medlem tilmeldes listen, bliver medlemmets indstillinger
-# taget herfra.
+# N&aring;r et nyt medlem tilmeldes listen, bliver medlemmets
+# indstillinger taget herfra.
 new_member_options = 256
 
 # Filter for administrative meddelelser vil unders&oslash;ge om
@@ -273,18 +280,21 @@ new_member_options = 256
 # gyldige værdier:
 #    0 = "Nej"
 #    1 = "Ja"
-administrivia = 1
+administrivia = True
 
 # Maximum st&oslash;rrelse i kilobytes (KB) for indholdet i e-mail der
 # sendes til listen. Brug v&aelig;rdien '0' for ikke at have nogen
 # begr&aelig;nsning.
 max_message_size = 40
 
+# Maksimalt antal medlemmer der skal vises pr. side af medlemslisten.
+admin_member_chunksize = 30
+
 # "Maskinnavnet" er det navn som skal benyttes for e-mailadresser
 # relateret til Mailman p&aring; denne maskine, og er normalt navnet der
 # er forbundet med e-mail-servicen p&aring; maskinen. Denne indstilling
 # kan v&aelig;re nyttig hvis maskinen har flere navne.
-host_name = 'bitbase.dk'
+host_name = 'lists.jones.dk'
 
 # I RFC 2369 defineres en r&aelig;kke List-* felter i brevhovedet, der
 # normalt tilf&oslash;jes enhver meddelelse der sendes ud via listen.
@@ -321,6 +331,10 @@ include_rfc2369_headers = 1
 #    1 = "Ja"
 include_list_post_header = 1
 
+# Slet alle tilbageholdte beskeder der er &aelig;ldre end dette antal
+# dage. Brug 0 for at sl&aring; automatisk sletning fra.
+max_days_to_hold = 0
+
 ## Language options
 #
 # Underst&oslash;ttelse af flere sprog. (Internationalisering)
@@ -333,98 +347,99 @@ include_list_post_header = 1
 # selv, vil dette standardsprog blive benyttet. Dette g&aelig;lder
 # b&aring;de web-baserede og e-mail-baserede meddelelser, men ikke
 # meddelelser sendt af listens medlemmer.
-preferred_language = 'en'
+preferred_language = 'da'
 
 # Her er alle sprog, som denne liste har underst&oslash;ttelse for.
 # Bem&aelig;rk at standardsproget skal v&aelig;re med.
-available_languages = ['en', 'da']
+available_languages = ['da', 'en']
 
 # Hvis standardsproget for din mailliste benytter et andet tegns&aelig;t
 # end ASCII og Emne prefixet for listen indeholder tegn som ikke findes
 # i ASCII-tegns&aelig;ttet, vil prefixet altid blive kodet i henhold til
 # den relevante standard. Hvis Emne prefixet kun indeholder ASCII tegn,
-# ønsker du måske at vælge Aldrig for at undgå kodning. Dette kan gøre
-# emnet lidt mere læseligt for brugere med e-mailprogrammer der ikke kan
-# håndtere andre tegnsæt end ASCII.
-# 
-# Bemærk imidlertid, at hvis din mailliste modtager både kodede og
-# ukodede emnefelter , kan det være bedst at vælge Efter behov. Med
-# denne indstilling vil Mailman ikke kode ASCII prefixer hvis resten af
-# titelfeltet kun indeholder ASCII tegn, men vil kode prefixet hvis det
-# indeholder tegn som ikke er ASCII tegn. På denne måde undgås en
-# tvetydighed i standarderne, som forårsager at visse e-mailprogrammer
-# vil vise ekstra eller manglende mellemrum imellem emne prefixet og det
-# oprindelige emne.
+# &oslash;nsker du m&aring;ske at v&aring;lge Aldrig for at undg&aring;
+# kodning. Dette kan g&oslash;re emnet lidt mere l&aelig;seligt for
+# brugere med e-mailprogrammer der ikke kan h&aring;ndtere andre
+# tegns&aelig;t end ASCII.
+# 
+# Bem&aelig;rk imidlertid, at hvis din mailliste modtager b&aring;de
+# kodede og ukodede emnefelter , kan det v&aelig;re bedst at v&aelig;lge
+# Efter behov. Med denne indstilling vil Mailman ikke kode ASCII
+# prefixer hvis resten af titelfeltet kun indeholder ASCII tegn, men vil
+# kode prefixet hvis det indeholder tegn som ikke er ASCII tegn.
+# P&aring; denne m&aring;de undg&aring;s en tvetydighed i standarderne,
+# som for&aring;rsager at visse e-mailprogrammer vil vise ekstra eller
+# manglende mellemrum imellem emne prefixet og det oprindelige emne.
 #
 # gyldige værdier:
 #    0 = "Aldrig"
 #    1 = "Altid"
 #    2 = "Efter behov"
-encode_ascii_prefixes = 0
+encode_ascii_prefixes = 2
 
 ## Nondigest options
 #
 # Regler for levering i normal-modus.
 
-# Kan medlemmer vælge normal-modus?
+# Kan medlemmer v&aelig;lge normal-modus?
 #
 # gyldige værdier:
 #    0 = "Nej"
 #    1 = "Ja"
-nondigestable = 1
+nondigestable = True
 
-# Tekst der tilføjes &oslash;verst i e-mail der sendes til listens
-# medlemmer. This text can include Python format strings which are
-# resolved against list attributes.  The list of substitutions allowed
-# are:
+# Tekst der tilf&oslash;jes &oslash;verst i e-mail der sendes til
+# listens medlemmer. Teksten kan indeholde formateringskoder som
+# udskiftes med v&aelig;rdier fra listens ops&aelig;tning. For detaljer,
+# se Pythons formateringsregler (engelsk). Gyldige koder er:
 # 
 # 
-# real_name - The "pretty" name of the list; usually the list name with
-# capitalization.
+# real_name - Listens formaterede navn; normalt listenavnet med stort
+# forbogstav eller store bogstaver enkelte steder.
 # 
-# list_name - The name by which the list is identified in URLs, where
-# case is significant.
+# list_name - Listens navn som brugt i URLer, hvor det har betydning om
+# den staves med store eller sm&aring; bogstaver. (For
+# bagudkompatibilitet, er _internal_name det samme.)
 # 
-# host_name - The fully qualified domain name that the list server runs
-# on.
+# host_name - Internetadressen (fully qualified domain name) til
+# maskinen som listeserveren k&oslash;rer p&aring;.
 # 
-# web_page_url - The base URL for Mailman.  This can be appended with,
-# e.g. listinfo/%(list_name)s to yield the listinfo page for the mailing
-# list.
+# web_page_url - Basis URL for Mailman. Denne kan kombineres med f.eks.
+# listinfo/%(list_name)s for at danne URLen til en listes infoside.
 # 
-# description - The brief description of the mailing list.
+# description - En kort beskrivelse af listen.
 # 
-# info - The full description of the mailing list.
+# info - Fuld beskrivelse af listen.
 # 
-# cgiext - The extension added to CGI scripts.
+# cgiext - Extension som tilf&oslash;jes CGI scripts.
 # 
 # 
 msg_header = ''
 
 # Tekst som tilf&oslash;jes nederst i e-mail der sendes til listens
-# medlemmer. This text can include Python format strings which are
-# resolved against list attributes.  The list of substitutions allowed
-# are:
+# medlemmer. Teksten kan indeholde formateringskoder som udskiftes med
+# v&aelig;rdier fra listens ops&aelig;tning. For detaljer, se Pythons
+# formateringsregler (engelsk). Gyldige koder er:
 # 
 # 
-# real_name - The "pretty" name of the list; usually the list name with
-# capitalization.
+# real_name - Listens formaterede navn; normalt listenavnet med stort
+# forbogstav eller store bogstaver enkelte steder.
 # 
-# list_name - The name by which the list is identified in URLs, where
-# case is significant.
+# list_name - Listens navn som brugt i URLer, hvor det har betydning om
+# den staves med store eller sm&aring; bogstaver. (For
+# bagudkompatibilitet, er _internal_name det samme.)
 # 
-# host_name - The fully qualified domain name that the list server runs
-# on.
+# host_name - Internetadressen (fully qualified domain name) til
+# maskinen som listeserveren k&oslash;rer p&aring;.
 # 
-# web_page_url - The base URL for Mailman.  This can be appended with,
-# e.g. listinfo/%(list_name)s to yield the listinfo page for the mailing
-# list.
+# web_page_url - Basis URL for Mailman. Denne kan kombineres med f.eks.
+# listinfo/%(list_name)s for at danne URLen til en listes infoside.
 # 
-# description - The brief description of the mailing list.
+# description - En kort beskrivelse af listen.
 # 
-# info - The full description of the mailing list.
+# info - Fuld beskrivelse af listen.
 # 
-# cgiext - The extension added to CGI scripts.
+# cgiext - Extension som tilf&oslash;jes CGI scripts.
 # 
 # 
 msg_footer = """_______________________________________________
@@ -432,30 +447,56 @@ msg_footer = """_______________________________________________
 %(real_name)s@%(host_name)s
 %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s"""
 
+# N&aring;r du fjerner vedh&aelig;ftninger, gemmes de i et arkiv
+# omr&aring;de og der laves istedet links i e-mailen s&aring;ledes at
+# medlemmer kan tilg&aring; vedh&aelig;ftninger via en webbrowser. Hvis
+# du vil have vedh&aelig;ftninger til helt og forsvinde s&aring; kan du
+# bruge et indholdsfilter.
+#
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
+scrub_nondigest = False
+
+# Mailliste e-mail adresser skal skrives i fuldt e-mail adresse format
+# (f.eks. mailman@example.com). Du m&aring; ikke angive denne mailliste
+# e-mail adresse gensidigt p&aring; liste eksklusions konfigurations
+# siden for den anden liste, da medlemmer af begge lister s&aring; ingen
+# meddelelser vil modtage. Bem&aelig;rk ogs&aring; at site administrator
+# kan v&aelig;lge og forbyde s&oslash;skende lister p&aring; tv&aelig;rs
+# af dom&aelig;ner.
+regular_exclude_lists = []
+
+# Mailliste e-mail adresser skal skrives i fuldt e-mail adresse format
+# (f.eks. mailman@example.com). Bem&aelig;rk ogs&aring; at site
+# administrator kan v&aelig;lge at forbyde s&oslash;skende lister
+# p&aring; tv&aelig;rs af dom&aelig;ner.
+regular_include_lists = []
+
 ## Digest options
 #
-# Opsætning af sammendrag-modus.
+# Ops&aelig;tning af sammendrag-modus.
 
-# Kan medlemmer af listen vælge sammendrag-modus?
+# Kan medlemmer af listen v&aelig;lge sammendrag-modus?
 #
 # gyldige værdier:
 #    0 = "Nej"
 #    1 = "Ja"
-digestable = 1
+digestable = True
 
 # Hvilken modus er standard for nye brugere?
 #
 # gyldige værdier:
 #    0 = "Normal"
 #    1 = "Sammendrag"
-digest_is_default = 0
+digest_is_default = False
 
 # Hvilket format skal benyttes som standard for samle-email?
 #
 # gyldige værdier:
 #    0 = "Ren tekst"
 #    1 = "MIME"
-mime_is_default_digest = 0
+mime_is_default_digest = False
 
 # Hvor stor (i KB) m&aring; en samle-email h&oslash;jst v&aelig;re
 # f&oslash;r den udsendes?
@@ -467,60 +508,60 @@ digest_size_threshhold = 30
 # gyldige værdier:
 #    0 = "Nej"
 #    1 = "Ja"
-digest_send_periodic = 1
+digest_send_periodic = True
 
 # Tekst som tilf&oslash;jes &oslash;verst i samle-emailen, f&oslash;r
-# indholdsfortegnelsen.This text can include Python format strings which
-# are resolved against list attributes.  The list of substitutions
-# allowed are:
+# indholdsfortegnelsen.Teksten kan indeholde formateringskoder som
+# udskiftes med v&aelig;rdier fra listens ops&aelig;tning. For detaljer,
+# se Pythons formateringsregler (engelsk). Gyldige koder er:
 # 
 # 
-# real_name - The "pretty" name of the list; usually the list name with
-# capitalization.
+# real_name - Listens formaterede navn; normalt listenavnet med stort
+# forbogstav eller store bogstaver enkelte steder.
 # 
-# list_name - The name by which the list is identified in URLs, where
-# case is significant.
+# list_name - Listens navn som brugt i URLer, hvor det har betydning om
+# den staves med store eller sm&aring; bogstaver. (For
+# bagudkompatibilitet, er _internal_name det samme.)
 # 
-# host_name - The fully qualified domain name that the list server runs
-# on.
+# host_name - Internetadressen (fully qualified domain name) til
+# maskinen som listeserveren k&oslash;rer p&aring;.
 # 
-# web_page_url - The base URL for Mailman.  This can be appended with,
-# e.g. listinfo/%(list_name)s to yield the listinfo page for the mailing
-# list.
+# web_page_url - Basis URL for Mailman. Denne kan kombineres med f.eks.
+# listinfo/%(list_name)s for at danne URLen til en listes infoside.
 # 
-# description - The brief description of the mailing list.
+# description - En kort beskrivelse af listen.
 # 
-# info - The full description of the mailing list.
+# info - Fuld beskrivelse af listen.
 # 
-# cgiext - The extension added to CGI scripts.
+# cgiext - Extension som tilf&oslash;jes CGI scripts.
 # 
 # 
 digest_header = ''
 
-# Tekst der tilføjes nederst i hver samle-email, som sidste
-# information.This text can include Python format strings which are
-# resolved against list attributes.  The list of substitutions allowed
-# are:
+# Tekst der tilf&oslash;jes nederst i hver samle-email, som sidste
+# information.Teksten kan indeholde formateringskoder som udskiftes med
+# v&aelig;rdier fra listens ops&aelig;tning. For detaljer, se Pythons
+# formateringsregler (engelsk). Gyldige koder er:
 # 
 # 
-# real_name - The "pretty" name of the list; usually the list name with
-# capitalization.
+# real_name - Listens formaterede navn; normalt listenavnet med stort
+# forbogstav eller store bogstaver enkelte steder.
 # 
-# list_name - The name by which the list is identified in URLs, where
-# case is significant.
+# list_name - Listens navn som brugt i URLer, hvor det har betydning om
+# den staves med store eller sm&aring; bogstaver. (For
+# bagudkompatibilitet, er _internal_name det samme.)
 # 
-# host_name - The fully qualified domain name that the list server runs
-# on.
+# host_name - Internetadressen (fully qualified domain name) til
+# maskinen som listeserveren k&oslash;rer p&aring;.
 # 
-# web_page_url - The base URL for Mailman.  This can be appended with,
-# e.g. listinfo/%(list_name)s to yield the listinfo page for the mailing
-# list.
+# web_page_url - Basis URL for Mailman. Denne kan kombineres med f.eks.
+# listinfo/%(list_name)s for at danne URLen til en listes infoside.
 # 
-# description - The brief description of the mailing list.
+# description - En kort beskrivelse af listen.
 # 
-# info - The full description of the mailing list.
+# info - Fuld beskrivelse af listen.
 # 
-# cgiext - The extension added to CGI scripts.
+# cgiext - Extension som tilf&oslash;jes CGI scripts.
 # 
 # 
 digest_footer = """_______________________________________________
@@ -544,8 +585,8 @@ digest_volume_frequency = 1
 # Her kan du bestemme hvad der kr&aelig;ves for at tilmelde sig til
 # maillisten, og bl.a. bestemme om maillisten skal v&aelig;re skjult
 # eller ikke. Se ogs&aring; <a
-# href="http://mail.bitbase.dk/mailman/admin/mailman/archive">Indstillinger 
-# for arkivering</a> for egne indstillinger, n&aring;r det g&aelig;lder
+# href="http://lists.jones.dk/admin/mailman/archive">Indstillinger for
+# arkivering</a> for egne indstillinger, n&aring;r det g&aelig;lder
 # arkivet og arkivering.
 
 # Vis denne mailliste n&aring;r nogen beder om at se en oversigt over
@@ -556,9 +597,9 @@ digest_volume_frequency = 1
 #    1 = "Ja"
 advertised = 0
 
-# bekræftelse(*) - bekr&aelig;ftelse via e-mail er n&oslash;dvendig
-# godkendelse - anmodning om medlemskab skal godkendes af
-# listeadministrator (eller evt. listemoderator) bekr&aelig;ftelse +
+# bekr&aelig;ftelse(*) - bekr&aelig;ftelse via e-mail er
+# n&oslash;dvendig godkendelse - anmodning om medlemskab skal godkendes
+# af listeadministrator (eller evt. listemoderator) bekr&aelig;ftelse +
 # godkendelse - b&aring;de bekr&aelig;ftelse via e-mail og godkendelse
 # fra listeadministrator (evt. listemoderator) er n&oslash;dvendig
 # 
@@ -571,7 +612,7 @@ advertised = 0
 #    1 = "Bekr&aelig;ftelse"
 #    2 = "Godkendelse"
 #    3 = "Bekr&aelig;ftelse og godkendelse"
-subscribe_policy = 1
+subscribe_policy = 2
 
 # N&aring;r medlemmer &oslash;nsker at forlade en mailliste, sender de
 # en anmodning om framelding, enten via web, eller via e-mail. Normalt
@@ -606,10 +647,10 @@ private_roster = 1
 # V&aelig;lger du 'Ja' her, vil medlemmers e-mailadresser blive
 # omskrevet n&aring;r de vises i en oversigt p&aring; websiderne
 # (b&aring;de som tekst og som links), s&aring; de ikke er nemme at
-# tolke som e-mailadresser. Formålet er at undg&aring; at medlemmernes
-# mailadresser bliver opsamlet af e-mailsniffere som skanner websider
-# for e-mailadresser (og derefter bruger dem til at udsende spam/junk
-# mail).
+# tolke som e-mailadresser. Form&aring;let er at undg&aring; at
+# medlemmernes mailadresser bliver opsamlet af e-mailsniffere som
+# skanner websider for e-mailadresser (og derefter bruger dem til at
+# udsende spam/junk mail).
 #
 # gyldige værdier:
 #    0 = "Nej"
@@ -643,7 +684,7 @@ obscure_addresses = 1
 # 
 # <p>I tekstboksene nedenfor kan du tilf&oslash;je en e-mailadresse pr.
 # linie. Du kan ogs&aring; tilf&oslash;je  <a
-# href="http://www.python.org/doc/current/lib/module-re.html">Python
+# href="http://docs.python.org/library/re.html">Python
 # regexp-udtryk</a>. Begynd i s&aring; fald linien med tegnet ^ for at
 # markere at det er et s&aring;dant udtryk. N&aring;r du benytter
 # backslash, skriv da lige som i rene strings (Python raw strings)
@@ -693,7 +734,10 @@ member_moderation_notice = ''
 # E-mail fra disse ikke-medlemmer vil automatisk blive godkendt.
 # Tilf&oslash;j e-mailadresser, en pr. linie. Start linien med tegnet ^
 # for at angive et regexp-udtryk som skal stemme overens med
-# afsenderadressen.
+# afsenderadressen. En linie der best&aring;r af et @ tegn efterfulgt at
+# et mailliste navn fra samme Mailman installation, angiver at e-mail
+# fra den maillistes medlemmer vil blive accepteret p&aring; denne
+# mailliste.
 accept_these_nonmembers = []
 
 # e-mail fra disse ikke-medlemmer vil automatisk blive holdt tilbage for
@@ -743,9 +787,15 @@ generic_nonmember_action = 1
 #    1 = "Ja"
 forward_auto_discards = 1
 
+# Tekst der skal inkluderes i en meddelelse om afvisning der sendes til
+# ikke-medlemmer der poster til listen. Denne meddelelse kan inkludere
+# listeejerens adresse vha. %(listowner)s og den erstatter den
+# automatisk konstruerede standard meddelelse.
+nonmember_rejection_notice = ''
+
 ## Privacy options
 #
-# Her kan du ops&aelig;tte filtrering baseret på modtageren af
+# Her kan du ops&aelig;tte filtrering baseret p&aring; modtageren af
 # meddelelsen.
 
 # Meget (faktisk det meste) spam/junk mail har ikke de endelige
@@ -797,18 +847,26 @@ max_num_recipients = 10
 
 ## Privacy options
 #
-# Her kan du opsætte forskellige anti-spam filtre, som kan bidrage til
-# at reducere mængden af spam der distribueres via e-maillisten.
-
-# 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.
+# Her kan du ops&aelig;tte forskellige anti-spam filtre, som kan bidrage
+# til at reducere m&aelig;ngden af spam der distribueres via
+# e-maillisten.
+
+# Hver filterregel best&aring;r af to dele: en liste med regexp-udtryk,
+# et pr. linie, og en aktion der skal udf&oslash;res. Mailman
+# sammenligner meddelelsens brevhoved med alle regexp-udtryk i reglen,
+# og hvis der er overensstemmelse, vil meddelelsen blive afvist,
+# tilbageholdt eller slettet, afh&aelig;ngigt af hvilken aktion du har
+# angivet her. Brug Afvent for midlertidigt at s&aelig;tte en regel ud
+# af kraft.
+# 
+# Du kan have flere end en regel for din liste.  I s&aring; fald vil
+# hver regel blive anvendt efter tur, og processen stopper f&oslash;rste
+# gang der findes overensstemmelse.
+# 
+# Bem&aelig;rk at brevhovedlinier indsamles fra alle vedh&aelig;ftninger
+# (undtagen fra mailman administrivia meddelelser) og sammenlignes med
+# regexp-udtrykkene. Ved brug af denne funktionalitet kan du effektivt
+# sortere meddelelser fra med farlige filtyper eller filnavn-endelser.
 header_filter_rules = []
 
 # Brug denne indstilling til at bortfiltrere mail til listen, baseret
@@ -879,14 +937,15 @@ from: .*@uplinkpro.com"""
 # v&aelig;rdier b&oslash;r tilpasses efter hvor ofte og hvor meget
 # e-mail der sendes til din liste.
 
-# Ved at sætte denne værdi til Nej, slår du al automatisk tolkning af
-# returmeddelelser for denne liste fra. Bemærk at hvis meddelelser
-# afvises vil listeadministratoren ikke blive forstyrret med dem.
+# Ved at s&aelig;tte denne v&aelig;rdi til Nej, sl&aring;r du al
+# automatisk tolkning af returmeddelelser for denne liste fra.
+# Bem&aelig;rk at hvis meddelelser afvises vil listeadministratoren ikke
+# blive forstyrret med dem.
 #
 # gyldige værdier:
 #    0 = "Nej"
 #    1 = "Ja"
-bounce_processing = 1
+bounce_processing = True
 
 # Hvert medlem tildeles et returtal, og hver gang der kommer en
 # returmeddelelse vil dette tal &oslash;ges.  Alvorlige (&aring;rsager
@@ -906,14 +965,14 @@ bounce_score_threshold = 5.0
 bounce_info_stale_after = 7
 
 # Hvor mange Levering til dig er stoppet advarsler der skal sendes til
-# et medlem f&oslash;r medlemmet frameldes listen. S&aelig;t denne værdi
-# til 0 for at fjerne et medlem fra listen straks, hvis der kommer
-# returmails fra medlemmets e-mailadresse. Dette tal skal være et
-# heltal.
+# et medlem f&oslash;r medlemmet frameldes listen. S&aelig;t denne
+# v&aelig;rdi til 0 for at fjerne et medlem fra listen straks, hvis der
+# kommer returmails fra medlemmets e-mailadresse. Dette tal skal
+# v&aelig;re et heltal.
 bounce_you_are_disabled_warnings = 3
 
 # Antal dage imellem hver gang en Levering til dig er stoppet advarsel
-# skal sendes ud. Dette tal skal være et heltal.
+# skal sendes ud. Dette tal skal v&aelig;re et heltal.
 bounce_you_are_disabled_warnings_interval = 7
 
 # Mailmans automatiske returmailh&aring;ndtering er meget robust, men
@@ -927,7 +986,7 @@ bounce_you_are_disabled_warnings_interval = 7
 # indstilling til Nej. S&aring; vil alle returmails afvises automatisk
 # uden videre behandling. Bem&aelig;rk: Denne indstilling vil ogs&aring;
 # indvirke p&aring; al e-mail der sendes til listens -admin adresse. Den
-# adresse er for&aelig;ldet og udg&aring;et, men måske vil nogen
+# adresse er for&aelig;ldet og udg&aring;et, men m&aring;ske vil nogen
 # alligevel fortsat sende e-mail til den. Hvis nogen g&oslash;r det, og
 # du har sat denne indstilling til Nej, vil disse mails ogs&aring; blive
 # afvist. M&aring;ske vil du ogs&aring; ops&aelig;tte et automatisk svar
@@ -936,27 +995,28 @@ bounce_you_are_disabled_warnings_interval = 7
 # gyldige værdier:
 #    0 = "Nej"
 #    1 = "Ja"
-bounce_unrecognized_goes_to_list_owner = 1
+bounce_unrecognized_goes_to_list_owner = True
 
-# Ved at sætte denne til Nej, fravælges beskeden der normalt sendes til
-# ejer(e) af listen, når levering af e-mail til et medlem stoppes på
-# grund af for mange returmails. Der vil til gengæld altid blive forsøgt
-# afsendt en e-mail med besked til medlemmet.
+# Ved at s&aelig;tte denne til Nej, frav&aelig;lges beskeden der normalt
+# sendes til ejer(e) af listen, n&aring;r levering af e-mail til et
+# medlem stoppes p&aring; grund af for mange returmails. Der vil til
+# geng&aelig;ld altid blive fors&oslash;gt afsendt en e-mail med besked
+# til medlemmet.
 #
 # gyldige værdier:
 #    0 = "Nej"
 #    1 = "Ja"
-bounce_notify_owner_on_disable = 1
+bounce_notify_owner_on_disable = True
 
-# Ved at sætte denne til Nej, fravælges beskeden der normalt sendes til
-# ejer(e) af listen, når et medlem frameldes listen på grund af for
-# mange returmails. Der vil til gengæld altid blive forsøgt afsendt en
-# e-mail med besked til medlemmet.
+# Ved at s&aelig;tte denne til Nej, frav&aelig;lges beskeden der normalt
+# sendes til ejer(e) af listen, n&aring;r et medlem frameldes listen
+# p&aring; grund af for mange returmails. Der vil til geng&aelig;ld
+# altid blive fors&oslash;gt afsendt en e-mail med besked til medlemmet.
 #
 # gyldige værdier:
 #    0 = "Nej"
 #    1 = "Ja"
-bounce_notify_owner_on_removal = 1
+bounce_notify_owner_on_removal = True
 
 ## Archive options
 #
@@ -967,7 +1027,7 @@ bounce_notify_owner_on_removal = 1
 # gyldige værdier:
 #    0 = "Nej"
 #    1 = "Ja"
-archive = 1
+archive = True
 
 # Skal arkivet v&aelig;re offentligt eller privat?
 #
@@ -1016,40 +1076,42 @@ gateway_to_mail = 0
 # Denne indstilling fort&aelig;ller Mailman hvilken slags
 # moderationsregler nyhedsgruppen har og hvordan de koordineres med
 # maillistens moderationsregler. Dette g&aelig;lder kun nyhedgrupper du
-# overfører meddelelser til, s&aring; hvis du kun overf&oslash;rer fra
-# en nyhedsgruppe, eller nyhedsgruppen du overf&oslash;rer til ikke er
-# modereret, s&aelig;ttes indstillingen til Ingen.
+# overf&oslash;rer meddelelser til, s&aring; hvis du kun
+# overf&oslash;rer fra en nyhedsgruppe, eller nyhedsgruppen du
+# overf&oslash;rer til ikke er modereret, s&aelig;ttes indstillingen til
+# Ingen.
 # 
 # Hvis nyhedsgruppen er modereret, kan du s&aelig;tte maillisten til at
-# v&aelig;re moderationsadressen for nyhedsgruppen. Ved at vælge
+# v&aelig;re moderationsadressen for nyhedsgruppen. Ved at v&aelig;lge
 # Modereret, vil en ekstra meddelelse holdes tilbage i
 # godkendelsesprocessen. Al mail sendt til maillisten skal godkendes
 # f&oslash;r den sendes til nyhedsgruppen, eller til medlemmerne af
 # listen.
 # 
-# Vær opm&aelig;rksom p&aring; at hvis brevhovedet i mailen har et
+# V&aelig;r opm&aelig;rksom p&aring; at hvis brevhovedet i mailen har et
 # Approved: felt med listens administrative adgangskode, vil denne regel
-# ikke blive benyttet. På den m&aring;de kan priviligerede afsendere
-# sende mail direkte til listen og nyhedsgruppen.
+# ikke blive benyttet. P&aring; den m&aring;de kan priviligerede
+# afsendere sende mail direkte til listen og nyhedsgruppen.
 # 
 # Hvis nyhedsgruppen er modereret, men du alligevel vil have en
-# &aring;ben liste, b&oslash;r du vælge Åben liste, modereret
-# nyhedsgruppe. S&aring; vil de s&aelig;dvanlige mekanismer for
-# moderation blive benyttet i Mailman, men alle meddelelser der sendes
-# til Usenet vil f&aring; et Approved felt i brevhovedet.
+# &aring;ben liste, b&oslash;r du v&aelig;lge &Aring;ben liste,
+# modereret nyhedsgruppe. S&aring; vil de s&aelig;dvanlige mekanismer
+# for moderation blive benyttet i Mailman, men alle meddelelser der
+# sendes til Usenet vil f&aring; et Approved felt i brevhovedet.
 #
 # gyldige værdier:
 #    0 = "Ingen"
-#    1 = "Åben liste, modereret nyhedsgruppe"
+#    1 = "&Aring;ben liste, modereret nyhedsgruppe"
 #    2 = "Modereret"
 news_moderation = 0
 
-# Mailman tilføjer normalt en tekst du selv kan tilrette (emne prefix)
-# foran emnefeltet i mail som sendes til listen, og normalt sker dette
-# også for mail som sendes videre til Usenet. Du kan sætte denne
-# indstilling til Nej hvis du ikke ønsker emne prefix tilføjet til mail
-# som sendes til Usenet. Sættes emne prefix for listen til off, vil
-# videresendte meddelelser heller ikke få prefix tilføjet.
+# Mailman tilf&oslash;jer normalt en tekst du selv kan tilrette (emne
+# prefix) foran emnefeltet i mail som sendes til listen, og normalt sker
+# dette ogs&aring; for mail som sendes videre til Usenet. Du kan
+# s&aelig;tte denne indstilling til Nej hvis du ikke &oslash;nsker emne
+# prefix tilf&oslash;jet til mail som sendes til Usenet. S&aelig;ttes
+# emne prefix for listen til off, vil videresendte meddelelser heller
+# ikke f&aring; prefix tilf&oslash;jet.
 #
 # gyldige værdier:
 #    0 = "Nej"
@@ -1060,10 +1122,10 @@ news_prefix_subject_too = 1
 #
 # Indstillinger for automatiske svar.<p>
 # 
-# I tekstboksene nedenfor kan du bruge følgende variabler: (skriv:
-# %(&lt;variabelnavn&gt;)s ) for at indsætte ønsket information: <p><ul>
-# <li><b>listname</b> - <em>navnet p&aring; listen</em>
-# <li><b>listurl</b> - <em>URL til listens webside</em>
+# I tekstboksene nedenfor kan du bruge f&oslash;lgende variabler:
+# (skriv: %(&lt;variabelnavn&gt;)s ) for at inds&aelig;tte &oslash;nsket
+# information: <p><ul> <li><b>listname</b> - <em>navnet p&aring;
+# listen</em> <li><b>listurl</b> - <em>URL til listens webside</em>
 # <li><b>requestemail</b> - <em>listens -request e-mailadresse</em>
 # <li><b>owneremail</b> - <em>listens -owner e-mailadresse</em> </ul>
 # 
@@ -1117,30 +1179,32 @@ autoresponse_graceperiod = 90
 #
 # Regler for indhold i e-mail sendt til listen.
 # 
-# <p>Filtrering af indhold fungerer således: når listen modtager en
-# e-mail og du har beskyttelse med filtrering af indhold aktiveret,
-# sammenlignes først eventuelle vedh&aelig;ftninger med <a
-# href="?VARHELP=contentfilter/filter_mime_types">MIME filtrene</a>.
-# Hvis en vedh&aelig;ftning passer med et af disse filtre, bliver
-# vedh&aelig;ftningen fjernet.
+# <p>Filtrering af indhold fungerer s&aring;ledes: n&aring;r listen
+# modtager en e-mail og du har beskyttelse med filtrering af indhold
+# aktiveret, sammenlignes f&oslash;rst eventuelle vedh&aelig;ftninger
+# med <a href="?VARHELP=contentfilter/filter_mime_types">MIME
+# filtrene</a>. Hvis en vedh&aelig;ftning passer med et af disse filtre,
+# bliver vedh&aelig;ftningen fjernet.
 # 
 # <p>Derefter sammenlignes eventuelle vedh&aelig;ftninger med <a
 # href="?VARHELP=contentfilter/pass_mime_types">gyldige MIME typer</a>,
-# hvis nogen er defineret. Alle vedh&aelig;ftninger som ikke stemmer
-# overens med de angivne MIME typer, bliver fjernet.
+# hvis nogen er defineret. Alle vedh&aelig;ftninger som <em>ikke</em>
+# stemmer overens med de angivne MIME typer, bliver fjernet.
 # 
 # <p>Efter filtreringen vil alle tomme <tt>multipart</tt>
 # vedh&aelig;ftninger v&aelig;re fjernet. Hvis selve meddelelsen er helt
 # tom efter denne filtrering, vil meddelelsen blive afvist. Derefter vil
 # enhver <tt>multipart/alternative</tt> vedh&aelig;ftning blive
-# erstattet af den første alternative som ikke er tom.
+# erstattet af den f&oslash;rste alternative som ikke er tom. Det sker
+# dog kun hvis <a href="?VARHELP=contentfilter/collapse_alternatives"
+# >sammenfold alternativer</a> er sl&aring;et til.
 # 
-# <p>Til sidst vil alle <tt>text/html</tt> vedh&aelig;ftninger som måtte
-# v&aelig;re tilbage i meddelelsen blive konverteret til
+# <p>Til sidst vil alle <tt>text/html</tt> vedh&aelig;ftninger som
+# m&aring;tte v&aelig;re tilbage i meddelelsen blive konverteret til
 # <tt>text/plain</tt> hvis <a
 # href="?VARHELP=contentfilter/convert_html_to_plaintext">konverter til
 # ren tekst</a> er sat til og serveren er konfigureret til at tillade
-# sådanne konverteringer.
+# s&aring;danne konverteringer.
 
 # Skal Mailman filtrere indhold i e-mail sendt til listen som angivet
 # nedenfor?
@@ -1148,54 +1212,80 @@ autoresponse_graceperiod = 90
 # gyldige værdier:
 #    0 = "Nej"
 #    1 = "Ja"
-filter_content = 0
+filter_content = False
 
 # Brug denne indstilling til at fjerne vedh&aelig;ftninger der passer
-# til MIME typer. Hver linie skal her indeholde navnet på en MIME
-# type/subtype, f.eks. image/gif. Hvis du ønsker at fjerne alle
+# til MIME typer. Hver linie skal her indeholde navnet p&aring; en MIME
+# type/subtype, f.eks. image/gif. Hvis du &oslash;nsker at fjerne alle
 # vedh&aelig;ftninger som har en given hoved MIME type, kan du undlade
 # at angive subtype, f.eks. image.
 # 
 # Tomme linier medtages ikke.
 # 
-# Se også gyldige MIME typer for whitelist af MIME typer.
+# Se ogs&aring; gyldige MIME typer for whitelist af MIME typer.
 filter_mime_types = ''
 
-# Brug denne indstilling for at definere hvilke MIME typer der skal være
-# tilladt. Krav og format for filtrering er identisk med MIME filtre.
+# Brug denne indstilling for at definere hvilke MIME typer der skal
+# v&aelig;re tilladt. Krav og format for filtrering er identisk med MIME
+# filtre.
 # 
-# Bem&aelig;rk: hvis du lægger noget ind her, men ikke angiver
+# Bem&aelig;rk: hvis du l&aelig;gger noget ind her, men ikke angiver
 # multipart, vil ingen e-mail med vedh&aelig;ftninger blive medtaget.
 pass_mime_types = """multipart/mixed
 multipart/alternative
 text/plain"""
 
+# Fjern e-mailvedh&aelig;ftninger med passende filnavn-endelser.
+filter_filename_extensions = """exe
+bat
+cmd
+com
+pif
+scr
+vbs
+cpl"""
+
+# Fjern alle vedh&aelig;ftninger der ikke har en passende
+# filnavn-endelse. Lad dette felt v&aelig;re tomt for at udelade dette
+# filter.
+pass_filename_extensions = ''
+
+# Skal Mailman forkorte mails med flere dele (multipart/alternative) til
+# f&oslash;rste del?
+#
+# gyldige værdier:
+#    0 = "Nej"
+#    1 = "Ja"
+collapse_alternatives = True
+
 # Skal Mailman konvertere text/html dele til ren tekst? Denne
 # konvertering vil finde sted efter at MIME filteret har fjernet de
-# uønskede dele.
+# u&oslash;nskede dele.
 #
 # gyldige værdier:
 #    0 = "Nej"
 #    1 = "Ja"
-convert_html_to_plaintext = 1
-
-# Her bestemmer du hvad der skal ske, når en meddelelse filtreres fra af
-# et filter, altså hvis vedh&aelig;ftningen filtreres fra af MIME
-# filteret, eller en vedh&aelig;ftning ikke har en af de gyldige MIME
-# typer, eller meddelelsen ender med at være tom efter filtrering.
-# 
-# Bemærk at det du vælger her ikke vil ske hvis en meddelelse stadig
-# indeholder noget efter filtrering. Så vil meddelelsen altid blive
-# sendt videre til listen.
-# 
-# Når meddelelsen afvises, skrives Message-ID for den afviste meddelelse
-# til loggen. Når meddelelsen sendes retur eller videresendes til
-# listens ejer, vil en begrundelse altid blive inkluderet i den
-# returmail der sendes til afsenderen. Når meddelelserne skal bevares,
-# gemmes de i et specielt køkatalog på disken, sådan at
-# serveradministrator kan se (og måske gøre noget med) dem, men bliver
-# ellers fjernet. Dette sidste valg er kun tilgængeligt hvis
-# serveradministrator har tilladt det.
+convert_html_to_plaintext = True
+
+# Her bestemmer du hvad der skal ske, n&aring;r en meddelelse filtreres
+# fra af et filter, alts&aring; hvis vedh&aelig;ftningen filtreres fra
+# af MIME filteret, eller en vedh&aelig;ftning ikke har en af de gyldige
+# MIME typer, eller meddelelsen ender med at v&aring;re tom efter
+# filtrering.
+# 
+# Bem&aelig;rk at det du v&aelig;lger her ikke vil ske hvis en
+# meddelelse stadig indeholder noget efter filtrering. S&aring; vil
+# meddelelsen altid blive sendt videre til listen.
+# 
+# N&aring;r meddelelsen afvises, skrives Message-ID for den afviste
+# meddelelse til loggen. N&aring;r meddelelsen sendes retur eller
+# videresendes til listens ejer, vil en begrundelse altid blive
+# inkluderet i den returmail der sendes til afsenderen. N&aring;r
+# meddelelserne skal bevares, gemmes de i et specielt k&oslash;katalog
+# p&aring; disken, s&aring;dan at serveradministrator kan se (og
+# m&aring;ske g&oslash;re noget med) dem, men bliver ellers fjernet.
+# Dette sidste valg er kun tilg&aelig;ngeligt hvis serveradministrator
+# har tilladt det.
 #
 # gyldige værdier:
 #    0 = "Slet"
@@ -1212,9 +1302,9 @@ filter_action = 0
 # regexp-udtryk du skriver nedenfor. Hvis felterne Subject: eller
 # Keywords: i brevhovedet i en mail stemmer overens med et af disse
 # udtryk, bliver mailen placeret under det p&aring;g&aelig;ldende emne.
-# Hvert medlem af listen kan vælge kun at modtage mail der passer til de
-# &oslash;nskede emner. E-mail som ikke h&oslash;rer under noget emne,
-# bliver ikke leveret.
+# Hvert medlem af listen kan v&aelig;lge kun at modtage mail der passer
+# til de &oslash;nskede emner. E-mail som ikke h&oslash;rer under noget
+# emne, bliver ikke leveret.
 # 
 # Bem&aeligrk: Dette fungerer kun i normal-modus, ikke i
 # sammendrag-modus.
@@ -1224,8 +1314,8 @@ filter_action = 0
 # topics_bodylines_limit er sat til.
 #
 # gyldige værdier:
-#    0 = "Ikke tilgængeligt"
-#    1 = "Tilgængeligt"
+#    0 = "Ikke tilg&aelig;ngeligt"
+#    1 = "Tilg&aelig;ngeligt"
 topics_enabled = 0
 
 # Her angiver du hvor mange linier af mailens indhold emnefilteret skal
diff --git a/mailman/mklist.conf b/mailman/mklist.conf
new file mode 100644
index 0000000..e6a3608
--- /dev/null
+++ b/mailman/mklist.conf
@@ -0,0 +1,8 @@
+#!/usr/bin/perl
+
+#$listhost = 'lists.homebase.dk';
+#$senders = 'Homebase-brugere';
+#$senderfilter = '^.*@(frontrunners\\.net|homebase\\.dk|kaospilot\\.(dk|no)|kolbert\\.dk)';
+#$listowner = 'listmaster@homebase.dk';
+
+1;
diff --git a/mailman/mklists b/mailman/mklists
new file mode 100755
index 0000000..1d44ad7
--- /dev/null
+++ b/mailman/mklists
@@ -0,0 +1,9 @@
+#!/bin/sh
+
+set -e
+
+. /etc/local-COMMON/mailman/mklist.inc
+
+refreshlists
+mklist "aoh" team "Art of Hosting" "list members" en "rowan@kaospilot.dk" "list.artofhosting.org" "list.artofhosting.org"
+mklist "test" team "Art TEST of Hosting" "list members" en "" "testlist.artofhosting.org" "testlist.artofhosting.org"
diff --git a/mailman/test.py b/mailman/test.py
new file mode 100644
index 0000000..cd1e195
--- /dev/null
+++ b/mailman/test.py
@@ -0,0 +1,1307 @@
+# -*- python -*-
+# -*- coding: us-ascii -*-
+## "test" mailing list configuration settings
+## captured on Fri Nov 12 03:37:01 2010
+
+## 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 = 'test'
+
+# 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@mail.bitbase.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 = 'Art TEST of Hosting (censored, semi-public)'
+
+# The text will be treated as html except that newlines will be
+# translated to <br> - so you can use links, preformatted text, etc, but
+# don't put in carriage returns except where you mean to separate
+# paragraphs.  And review your changes - bad html (like some
+# unterminated HTML constructs) can prevent display of the entire
+# listinfo page.
+info = """Open list for Art TEST of Hosting.
+<ul><li>Anyone can send to the list (non-text parts are stripped).
+<li>Posts are censored for relevancy (except from list members).
+<li>Anyone can subscribe to the list (only members can see member list).
+</ul>Access limitation to the archive avoids search engine registrations, but does not ensure discretion as anyone can gain access by subscribing.
+
+Censorship avoids some noise, but also increase risk of rejection or delay of legitimate posts: Please subscribe to the list and use your subscribed address as sender if you want delivery of your posts ensured."""
+
+# This text will be prepended to subject lines of messages posted to the
+# list, to distinguish mailing list messages in mailbox summaries.
+# Brevity is premium here, it's ok to shorten long mailing list names to
+# something more concise, as long as it still identifies the mailing
+# list. You can also add a sequential number by %d substitution
+# directive. eg.; [listname %d] -> [listname 123] (listname %05d) ->
+# (listname 00123)
+# 
+subject_prefix = '[test] '
+
+# 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.net/essays/reply-to.mhtml">Reply-To
+# Munging Considered Useful for a dissenting opinion.
+# 
+# Some mailing lists have restricted posting privileges, with a parallel
+# list devoted to discussions.  Examples are `patches' or `checkin'
+# lists, where software changes are posted by a revision control system,
+# but discussion about the changes occurs on a developers mailing list.
+# To support these types of mailing lists, select Explicit address and
+# set the Reply-To: address below to point to the parallel list.
+#
+# legal values are:
+#    0 = "Poster"
+#    1 = "This list"
+#    2 = "Explicit address"
+reply_goes_to_list = 0
+
+# This is the address set in the Reply-To: header when the <a
+# href="?VARHELP=general/reply_goes_to_list">reply_goes_to_list option
+# is set to Explicit address.
+# 
+# There are many reasons not to introduce or override the Reply-To:
+# header.  One is that some posters depend on their own Reply-To:
+# settings to convey their valid return address.  Another is that
+# modifying Reply-To: makes it much more difficult to send private
+# replies.  See <a
+# href="http://www.unicom.com/pw/reply-to-harmful.html">`Reply-To'
+# Munging Considered Harmful for a general discussion of this issue.
+# See <a
+# href="http://www.metasystema.net/essays/reply-to.mhtml">Reply-To
+# Munging Considered Useful for a dissenting opinion.
+# 
+# Some mailing lists have restricted posting privileges, with a parallel
+# list devoted to discussions.  Examples are `patches' or `checkin'
+# lists, where software changes are posted by a revision control system,
+# but discussion about the changes occurs on a developers mailing list.
+# To support these types of mailing lists, specify the explicit
+# Reply-To: address here.  You must also specify Explicit address in the
+# reply_goes_to_list variable.
+# 
+# Note that if the original message contains a Reply-To: header, it will
+# not be changed.
+reply_to_address = ''
+
+# 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 = """This is an open list for Art TEST of Hosting.
+
+ * Anyone can send to the list (non-text parts are stripped).
+ * Posts are censored for relevancy (except from list members).
+ * Anyone can subscribe to the list (only members can see member list).
+
+Access limitation to the archive avoids search engine registrations, 
+but does not ensure discretion as anyone can gain access by subscribing.
+
+Censorship avoids some noise, but also increase risk of rejection or 
+delay of legitimate posts: Please subscribe to the list and use your 
+subscribed address as sender if you want delivery of your posts ensured.
+
+All emails are archived (only members can read the archive)."""
+
+# 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 = 1
+
+# Send mail to poster when their posting is held for approval?
+#
+# 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 = 0
+
+# Maximum length in kilobytes (KB) of a message body.  Use 0 for no
+# limit.
+max_message_size = 0
+
+# Maximum number of members to show on one page of the Membership List.
+admin_member_chunksize = 30
+
+# 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 = 'testlist.artofhosting.org'
+
+# 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
+
+# Discard held messages older than this number of days. Use 0 for no
+# automatic discarding.
+max_days_to_hold = 7
+
+## 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 = 'en'
+
+# These are all the natural languages supported by this list. Note that
+# the default language must be included.
+available_languages = ['da', 'de', 'en', 'es', 'fi', 'nl', 'no', 'pt_BR', 'sv']
+
+# If your mailing list's default language uses a non-ASCII character set
+# and the prefix contains non-ASCII characters, the prefix will always
+# be encoded according to the relevant standards.  However, if your
+# prefix contains only ASCII characters, you may want to set this option
+# to Never to disable prefix encoding.  This can make the subject
+# headers slightly more readable for users with mail readers that don't
+# properly handle non-ASCII encodings.
+# 
+# Note however, that if your mailing list receives both encoded and
+# unencoded subject headers, you might want to choose As needed.  Using
+# this setting, Mailman will not encode ASCII prefixes when the rest of
+# the header contains only ASCII characters, but if the original header
+# contains non-ASCII characters, it will encode the prefix.  This avoids
+# an ambiguity in the standards which could cause some mail readers to
+# display extra, or missing spaces between the prefix and the original
+# header.
+#
+# 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. This
+# text can include Python format strings which are resolved against list
+# attributes.  The list of substitutions allowed are:
+# 
+# 
+# real_name - The "pretty" name of the list; usually the list name with
+# capitalization.
+# 
+# list_name - The name by which the list is identified in URLs, where
+# case is significant.
+# 
+# host_name - The fully qualified domain name that the list server runs
+# on.
+# 
+# web_page_url - The base URL for Mailman.  This can be appended with,
+# e.g. listinfo/%(list_name)s to yield the listinfo page for the mailing
+# list.
+# 
+# description - The brief description of the mailing list.
+# 
+# info - The full description of the mailing list.
+# 
+# cgiext - The extension added to CGI scripts.
+# 
+# 
+msg_header = ''
+
+# Text appended to the bottom of every immediately-delivery message.
+# This text can include Python format strings which are resolved against
+# list attributes.  The list of substitutions allowed are:
+# 
+# 
+# real_name - The "pretty" name of the list; usually the list name with
+# capitalization.
+# 
+# list_name - The name by which the list is identified in URLs, where
+# case is significant.
+# 
+# host_name - The fully qualified domain name that the list server runs
+# on.
+# 
+# web_page_url - The base URL for Mailman.  This can be appended with,
+# e.g. listinfo/%(list_name)s to yield the listinfo page for the mailing
+# list.
+# 
+# description - The brief description of the mailing list.
+# 
+# info - The full description of the mailing list.
+# 
+# cgiext - The extension added to CGI scripts.
+# 
+# 
+msg_footer = """-- 
+%(real_name)s mailing list
+%(real_name)s@%(host_name)s
+%(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s"""
+
+# When you scrub attachments, they are stored in archive area and links
+# are made in the message so that the member can access via web browser.
+# If you want the attachments totally disappear, you can use content
+# filter options.
+#
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
+scrub_nondigest = 1
+
+# The list addresses should be written in full mail address format (e.g.
+# mailman@example.com). Do not specify this list address mutually in the
+# exclude list configuration page of the other list, or members of both
+# lists won't get any message. Note also that the site administrator may
+# prohibit cross domain siblings.
+regular_exclude_lists = []
+
+# The list addresses should be written in full mail address format (e.g.
+# mailman@example.com). Note also that the site administrator may
+# prohibit cross domain siblings.
+regular_include_lists = []
+
+## 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. This text can include Python format strings which
+# are resolved against list attributes.  The list of substitutions
+# allowed are:
+# 
+# 
+# real_name - The "pretty" name of the list; usually the list name with
+# capitalization.
+# 
+# list_name - The name by which the list is identified in URLs, where
+# case is significant.
+# 
+# host_name - The fully qualified domain name that the list server runs
+# on.
+# 
+# web_page_url - The base URL for Mailman.  This can be appended with,
+# e.g. listinfo/%(list_name)s to yield the listinfo page for the mailing
+# list.
+# 
+# description - The brief description of the mailing list.
+# 
+# info - The full description of the mailing list.
+# 
+# cgiext - The extension added to CGI scripts.
+# 
+# 
+digest_header = ''
+
+# Text attached (as a final message) to the bottom of digests. This text
+# can include Python format strings which are resolved against list
+# attributes.  The list of substitutions allowed are:
+# 
+# 
+# real_name - The "pretty" name of the list; usually the list name with
+# capitalization.
+# 
+# list_name - The name by which the list is identified in URLs, where
+# case is significant.
+# 
+# host_name - The fully qualified domain name that the list server runs
+# on.
+# 
+# web_page_url - The base URL for Mailman.  This can be appended with,
+# e.g. listinfo/%(list_name)s to yield the listinfo page for the mailing
+# list.
+# 
+# description - The brief description of the mailing list.
+# 
+# info - The full description of the mailing list.
+# 
+# cgiext - The extension added to 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://testlist.artofhosting.org/admin/test/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 = 0
+
+## Privacy options
+#
+# When a message is posted to the list, a series of moderation steps are
+# taken to decide whether 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://docs.python.org/library/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.  A line consisting of the @ character followed by a
+# list name specifies another Mailman list in this installation, all of
+# whose member addresses will be accepted for this list.
+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 = 1
+
+# Should messages from non-members, which are automatically discarded,
+# be forwarded to the list moderator?
+#
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
+forward_auto_discards = True
+
+# Text to include in any rejection notice to be sent to non-members who
+# post to this list. This notice can include the list's owner address by
+# %(listowner)s and replaces the internally crafted default message.
+nonmember_rejection_notice = ''
+
+## Privacy options
+#
+# 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 = 0
+
+## 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.
+# 
+# Note that headers are collected from all the attachments (except for
+# the mailman administrivia message) and matched against the regular
+# expressions. With this feature, you can effectively sort out messages
+# with dangerous file types or file name extensions.
+header_filter_rules = [('X-Spam-Status: Yes', 3, False)]
+
+# 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 = 1
+
+## 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.
+# 
+# <p> Then, each <tt>multipart/alternative</tt> section will be replaced
+# by just the first alternative that is non-empty after filtering if <a
+# href="?VARHELP=contentfilter/collapse_alternatives"
+# >collapse_alternatives</a> is enabled.
+# 
+# <p>Finally, any <tt>text/html</tt> parts that are left in the message
+# may be converted to <tt>text/plain</tt> if <a
+# href="?VARHELP=contentfilter/convert_html_to_plaintext"
+# >convert_html_to_plaintext</a> is enabled and the site is configured
+# to allow these conversions.
+
+# Should Mailman filter the content of list traffic according to the
+# settings below?
+#
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
+filter_content = False
+
+# 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 = ''
+
+# 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/signed
+multipart/mixed
+multipart/alternative
+application/pgp-signature
+application/pkcs7-signature
+text/plain"""
+
+# Remove message attachments that have a matching filename extension.
+filter_filename_extensions = """exe
+bat
+cmd
+com
+pif
+scr
+vbs
+cpl"""
+
+# Remove message attachments that don't have a matching filename
+# extension.  Leave this field blank to skip this filter test.
+pass_filename_extensions = ''
+
+# Should Mailman collapse multipart/alternative to its first part
+# content?
+#
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
+collapse_alternatives = True
+
+# Should Mailman convert text/html parts to plain text?  This conversion
+# happens after MIME attachments have been stripped.
+#
+# legal values are:
+#    0 = "No"
+#    1 = "Yes"
+convert_html_to_plaintext = True
+
+# One of these actions is taken when the message matches one of the
+# content filtering rules, meaning, the top-level content type matches
+# one of the <a href="?VARHELP=contentfilter/filter_mime_types"
+# >filter_mime_types, or the top-level content type does not match one
+# of the <a href="?VARHELP=contentfilter/pass_mime_types"
+# >pass_mime_types, or if after filtering the subparts of the message,
+# the message ends up empty.
+# 
+# Note this action is not taken if after filtering the message still
+# contains content.  In that case the message is always forwarded on to
+# the list membership.
+# 
+# When messages are discarded, a log entry is written containing the
+# Message-ID of the discarded message.  When messages are rejected or
+# forwarded to the list owner, a reason for the rejection is included in
+# the bounce message to the original author.  When messages are
+# preserved, they are saved in a special queue directory on disk for the
+# site administrator to view (and possibly rescue) but otherwise
+# discarded.  This last option is only available if enabled by the site
+# administrator.
+#
+# legal values are:
+#    0 = "Discard"
+#    1 = "Reject"
+#    2 = "Forward to List Owner"
+#    3 = "Preserve"
+filter_action = 1
+
+## Topics options
+#
+# List topic keywords
+
+# The topic filter categorizes each incoming email message according to
+# <a href="http://docs.python.org/library/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 = []
+