RIPE ML issue

Dear Marc,

thank you for pointing out to this problem, and please receive apologies
for the delays that happened recently. 

Here is what is causing them: 

RIPE Working Groups mailing lists are moderated lists, so that only
subscribers can post to them (to prevent "spam"). Still, lists are open
for subscription to everyone. 

Bounced messages go to the human moderator, and are being looked into and
manually approved, at least twice a day, during working days.

If the message is sent after working hours, or on the weekend, its
approval will be delayed, and that will indeed confuse the archiving. 

To improve the situation, it would be helpful if mailing list members
would post from the same address that they are subscribed from. 

However, due to the parallel discussions that happen on several mailing
lists, or relevant postings done only once from non-subscribers,
or messages that get bounced because they have a word "subscribe" in the
body, it is inevitable that this kind of behaviour of the mailing list
archiving will sometimes occur.

We are looking at this problem at RIPE NCC, and will improve our archiving
software. 

We apologise again for any inconvenience. 

Vesna Manojlovic
RIPE NCC staff

 Marc Roger <marc at belnet.be> writes:
 * Dear NCC,
 * 
 * I have just received the following messages addressed to the lir-wg
 * mailing-list, that were apparently sent more than four days ago:
 * 
 * Andre Opperman               Fri, 11 May 2001 20:52:19 +0200 <3AFC34E3.5A816
 * A2C at telehouse.ch>
 * Havard Eidnes <he at runit.no>  Fri, 11 May 2001 19:04:45 +0200 <20010511190445
 * J.he at runit.no>
 * 
 * In both messages I see that it was processed by qmail at the RIPE mail
 * server today at 09:44 and that they do not appear in the lir-wg archives
 * at their original posting date, which indicates that the problem is not
 * local: see
 * http://www.ripe.net/ripe/mail-archives/lir-wg/current/mail3.html
 * 
 * This is not the first occurence of this phenomenon, eg on May 9th at 11:31
 * I have received the following announcement:
 * 
 * Return-Path: <owner-sst at belnet.be>
 * Received: from vivaldi.belnet.be (vivaldi.belnet.be [193.190.198.2])
 * 	by dagesh.fw.belnet.be (8.10.2/8.10.2) with ESMTP id f499VvM23656
 * 	for <sst at office.belnet.be>; Wed, 9 May 2001 11:31:57 +0200 (MEST)
 * Received: from postman.ripe.net (postman.ripe.net [193.0.0.199])
 * 	by vivaldi.belnet.be (8.10.2/8.10.2) with SMTP id f499Vuw11762
 * 	for <ir at belnet.be>; Wed, 9 May 2001 11:31:56 +0200 (MEST)
 * Received: (qmail 1707 invoked by alias); 9 May 2001 09:23:44 -0000
 * Delivered-To: lists-local-ir-reg at lists.ripe.net
 * Received: (qmail 1558 invoked by alias); 9 May 2001 09:23:36 -0000
 * Delivered-To: lists-local-ir-out at lists.ripe.net
 * Received: (qmail 1475 invoked by uid 66); 9 May 2001 09:23:31 -0000
 * Message-Id: <200105041452.QAA11314 at office.ripe.net>
 * To: ripe-list at ripe.net
 * Cc: local-ir at ripe.net, lir-wg at ripe.net
 * From: RIPE NCC Document Announcement Service <ncc at ripe.net>
 * Subject: New Document available: RIPE-220
 * X-Phone: +31 20 535 4444
 * X-Fax: +31 20 535 4445
 * Date: Fri, 04 May 2001 16:52:47 +0200
 * Sender: owner-local-ir at ripe.net
 * Precedence: bulk
 * 
 * (which is also archived under "09 May 2001" on the ML archives)
 * 
 * It is not possible to follow a discussion if messages are randomly delayed
 * by several days like this. Can I kindly ask the RIPE NCC to fix this
 * problem ?
 * 
 * --
 * Marc.Roger at belnet.be, BELNET, the National Research Network
 * 
 * 
 * 
 * 
 * 
 *