[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bits from the listmaster team (fwd)

questa potrebbe contenere un spiegazione ai problemi di gollum1:

---------- Forwarded message ----------
Date: Tue,  4 Mar 2008 15:49:30 +0000 (UTC)
From: Thomas Viehmann <tv@beamnet.de>
To: debian-devel-announce@lists.debian.org
Subject: Bits from the listmaster team
Resent-Date: Tue,  4 Mar 2008 15:49:42 +0000 (UTC)
Resent-From: debian-devel-announce@lists.debian.org

Hash: SHA1

Hi everyone,

the listmaster team is constantly trying to improve the setup of our
listserver. Thus, quite a few things have happend since our last update
in September of last year. Here are some highlights:

lists.debian.org moved to a new hosting location
lists.debian.org has been moved to man-da[2] to avoid several problems
with DNSBL pointing to our list server. We'd like to thank Brainfood
for hosting lists.debian.org and dealing with the insanity of spam
reporters for so long. After the move of the list service to the new
machine, we also decided to move the list archives to that machine
(which means the list archives are on the same machine as the MX, and
consequently suffer fewer delays).

If you haven't already, please add lists.d.o's new ip,,
to your whitelists.


While reviewing things we found that our bounce handling had some
issues, see the next section for information about that.

Better bounce handling
We checked our bounce handling because we have more than 500 bounces
for some lists, and in the process found that we didn't have working
bounce handling for other lists (other-*, deity, *-digest,
debian-private). There were also problems in handling and recognizing
mailadresses containing = or ! characters.

Bounces of debian-private subscription are still manualy handed by the
listmasters, but we now address these issues and forward such addresses to

To address the other mailing lists we rewrote some parts of our
bounce handler.

While analysing the bounces streaming in, we found that a lot of bounces
are caused by content filters which reject listmail back to us (which
violates the RfC). Even worse: the majority of those are false

To let those people know we'll implement a notification system, which
will notify users about bounces, and remind forcibly removed users about
their unsubscription.

This is a service for those people with a temporarily unavailable or
broken mailbox, so they see that they (or their provider) has a broken
mail setup or resubscribe back to all lists after their mailaddress is
functional again.  These notification will be sent out at a maximum of
once a week, up to a month after the last unsubscription happened.

Both notification systems are in testing now and will be activated
shortly after this mail.


Reply to: