Your message dated Sun, 25 Dec 2005 15:52:34 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Bugs fixed with new upload
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--------------------------------------
Received: (at submit) by bugs.debian.org; 6 Apr 2005 06:36:14 +0000
>From [EMAIL PROTECTED] Tue Apr 05 23:36:14 2005
Return-path: <[EMAIL PROTECTED]>
Received: from 5301d.unt0.torres.l21.ma.zugschlus.de
(torres.int.l21.ma.zugschlus.de) [217.151.83.1] (Debian-exim)
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1DJ497-0006qC-00; Tue, 05 Apr 2005 23:36:14 -0700
Received: from lefler.int.l21.ma.zugschlus.de ([192.168.130.38]:54622)
by torres.int.l21.ma.zugschlus.de with esmtp (Exim 4.50)
id 1DJ495-00057d-Mp; Wed, 06 Apr 2005 08:36:11 +0200
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Marc Haber <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: mailman: please consider adding Debian-specific information for exim 4
setup
X-Mailer: reportbug 3.9
Date: Wed, 06 Apr 2005 08:36:11 +0200
Message-Id: <[EMAIL PROTECTED]>
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE
autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level:
Package: mailman
Severity: wishlist
Hi,
the README.EXIM file shipped with the mailman packages is confusing as
it doesn't address the Debian specialities. Please consider including
mailman config for exim 4 as examples files. Here is my config from my
productive mailman installation. I cannot, however, guarantee that it
will work with a stock install.
mailman transport, /etc/exim4/conf.d/transport/30_local_mailman on my
system:
mailman:
driver = pipe
command = /usr/lib/mailman/mail/mailman \
'${if def:local_part_suffix \
{${sg{$local_part_suffix}{-(\\w+)(\\+.*)?}{\$1}}} \
{post}}' \
$local_part
current_directory = /var/lib/mailman
debug_print = "T: mailman for [EMAIL PROTECTED]"
group = list
home_directory = /var/lib/mailman
user = list
mailman routers, /etc/exim4/conf.d/router/255_local_mailman on my
system:
mailman:
driver = accept
debug_print = "D: mailman for [EMAIL PROTECTED]"
domains = CONFDIR/mailman_domains
local_part_suffix = -bounces : -bounces+* : \
-confirm+* : -join : -leave : \
-owner : -request : -admin
local_part_suffix_optional
require_files = /var/lib/mailman/lists/$local_part/config.pck
retry_use_local_part
transport = mailman
bounce_mailman:
driver = redirect
allow_defer
allow_fail
data = :fail: Unknown user
debug_print = "D: bounce_mailman for [EMAIL PROTECTED]"
domains = CONFDIR/mailman_domains
retry_use_local_part
# this director bounces all mail from a mailman domain that hasn't been
# picked up by the mailman director
This assumes that there are no non-lists in domains that are used by
mailman, and that all list domains are listed in
CONFDIR/mailman_domains.
Hope this helps.
Greetings
Marc
-- System Information:
Debian Release: 3.1
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.9-zgserver
Locale: LANG=C, LC_CTYPE=de_DE (charmap=ISO-8859-1)
Versions of packages mailman depends on:
ii apache [httpd] 1.3.33-4 versatile, high-performance HTTP s
ii cron 3.0pl1-87 management of regular background p
ii debconf 1.4.46 Debian configuration management sy
ii exim4-daemon-light [mail-tr 4.50-1 lightweight exim MTA (v4) daemon
ii libc6 2.3.2.ds1-20 GNU C Library: Shared libraries an
ii logrotate 3.7-2 Log rotation utility
ii python 2.3.5-2 An interactive high-level object-o
---------------------------------------
Received: (at 303342-done) by bugs.debian.org; 25 Dec 2005 14:52:36 +0000
>From [EMAIL PROTECTED] Sun Dec 25 06:52:36 2005
Return-path: <[EMAIL PROTECTED]>
Received: from 213-84-114-29.adsl.xs4all.nl ([213.84.114.29]
helo=capsaicin.mamane.lu)
by spohr.debian.org with esmtp (Exim 4.50)
id 1EqXEh-0002FT-QB; Sun, 25 Dec 2005 06:52:36 -0800
Received: from master by capsaicin.mamane.lu with local (Exim 4.60)
(envelope-from <[EMAIL PROTECTED]>)
id 1EqXEg-00089M-7g; Sun, 25 Dec 2005 15:52:34 +0100
Date: Sun, 25 Dec 2005 15:52:34 +0100
From: Lionel Elie Mamane <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED], [EMAIL PROTECTED]
Subject: Bugs fixed with new upload
Message-ID: <[EMAIL PROTECTED]>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
X-Operating-System: GNU/Linux
X-Request-PGP: http://www.mamane.lu/openpgp/rsa_v4_4096.asc
User-Agent: Mutt/1.5.11
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Level:
X-Spam-Status: No, hits=-3.0 required=4.0 tests=BAYES_00 autolearn=no
version=2.60-bugs.debian.org_2005_01_02
X-CrossAssassin-Score: 2
Version: 2.1.5-11
These bugs have been fixed by a new upload, but I forgot to build the
package in a way that would give this information in the changes
file. So I'm doing it manually.
--
Lionel
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
