Package: mailman
Version: 2.1.5-8
Severity: normal

On a moderately busy mailman list, we've just had an issue where two 
digests were issued with the same digest number, approximately an hour 
apart. There's nothing in the logs to suggest any issue -- specifically 
there is nothing relating to being unable to read the next digest number 
out of the list data, or anything of that sort. (In fact the only errors 
reported in the past couple of days have related to people not being 
able to spell one of the list names.) The next digest (issued approximately 
45 minutes after the second of the pair with the same number) had its 
digest number bumped correctly. 

This is not the first time I've seen this happen but the other time was 
right after upgrading to MM 2.1.5 from 2.0.x so I put it down to that.


-- System Information:
Debian Release: 3.1
Architecture: i386 (i686)
Kernel: Linux 2.6.8-2-686
Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1)

Versions of packages mailman depends on:
ii  apache [httpd]              1.3.33-6     versatile, high-performance HTTP s
ii  apache2-mpm-prefork [httpd] 2.0.54-4     traditional model for Apache2
ii  cron                        3.0pl1-86    management of regular background p
ii  debconf                     1.4.30.13    Debian configuration management sy
ii  libc6                       2.3.2.ds1-22 GNU C Library: Shared libraries an
ii  logrotate                   3.7-5        Log rotation utility
ii  pwgen                       2.03-1       Automatic Password generation
ii  python                      2.3.5-2      An interactive high-level object-o
ii  sendmail-bin [mail-transpor 8.13.4-3     powerful, efficient, and scalable 
ii  ucf                         1.17         Update Configuration File: preserv

-- debconf information:
  mailman/queue_files_present:
  mailman/default_server_language: en
  mailman/gate_news: false
* mailman/site_languages: en
* mailman/used_languages:
* mailman/create_site_list:


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to