Your message dated Mon, 24 Jan 2005 15:19:20 +0000
with message-id <[EMAIL PROTECTED]>
and subject line Bug#291852: update-basswd (probably) killed user/group mdom
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; 23 Jan 2005 16:53:35 +0000
>From [EMAIL PROTECTED] Sun Jan 23 08:53:35 2005
Return-path: <[EMAIL PROTECTED]>
Received: from mail.gmx.de (mail.gmx.net) [213.165.64.20]
by spohr.debian.org with smtp (Exim 3.35 1 (Debian))
id 1CskzX-0008AL-00; Sun, 23 Jan 2005 08:53:35 -0800
Received: (qmail invoked by alias); 23 Jan 2005 16:53:03 -0000
Received: from dial-195-14-250-107.netcologne.de (EHLO gustav.local)
(195.14.250.107)
by mail.gmx.net (mp023) with SMTP; 23 Jan 2005 17:53:03 +0100
X-Authenticated: #4240698
From: Jan =?iso-8859-1?q?L=FChr?= <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: update-basswd (probably) killed user/group mdom
Date: Sun, 23 Jan 2005 17:53:03 +0100
User-Agent: KMail/1.7.1
MIME-Version: 1.0
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <[EMAIL PROTECTED]>
X-Y-GMX-Trusted: 0
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: base-passwd
Version: 3.5.9
Greetings,
A few weeks ago I did an apt-get dist-upgrade on my sarge server (i386). For
some reason update-basswd wanted to delete the user:group mdom:mdom. I
thought I won't be necessary to keep 'em, so I let update-passwd go one.
Later one, I noticed that my UUCP System was unable to send mail, because It
had no rights to call the sendmail-placeholder (exim).
Recreating mdom:mdom solved the problem.
Keep smiling
yanosz
---------------------------------------
Received: (at 291852-done) by bugs.debian.org; 24 Jan 2005 15:19:24 +0000
>From [EMAIL PROTECTED] Mon Jan 24 07:19:24 2005
Return-path: <[EMAIL PROTECTED]>
Received: from chiark.greenend.org.uk [193.201.200.170] (mail)
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1Ct5zv-0003uW-00; Mon, 24 Jan 2005 07:19:23 -0800
Received: from [192.168.124.112] (helo=riva.lab.dotat.at)
by chiark.greenend.org.uk (Debian Exim 3.35 #1) with esmtp
(return-path [EMAIL PROTECTED])
id 1Ct5zt-0003qX-00
for [EMAIL PROTECTED]; Mon, 24 Jan 2005 15:19:21 +0000
Received: from cjwatson by riva.lab.dotat.at with local (Exim 3.35 #1 (Debian))
for [EMAIL PROTECTED]
id 1Ct5zs-0003kg-00; Mon, 24 Jan 2005 15:19:20 +0000
Date: Mon, 24 Jan 2005 15:19:20 +0000
From: Colin Watson <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Re: Bug#291852: update-basswd (probably) killed user/group mdom
Message-ID: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL
PROTECTED]>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <[EMAIL PROTECTED]>
User-Agent: Mutt/1.3.28i
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=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER
autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level:
On Mon, Jan 24, 2005 at 04:13:40PM +0100, Jan L�hr wrote:
> I grepped my /etc for mdom and noticed that it is used by exim as mail-user.
> I also got a file called passwd.org (maybe before) that introduced
> mdom:x:40:45:majordomo:/usr/local/majordomo:/bin/sh
Sounds like a local majordomo installation. I suggest looking through it
to find out what creates the mdom user, and hitting it hard until it
stops creating it in the 0-99 range reserved for the system. Using
'adduser --system' instead is the standard interface on Debian systems.
Since majordomo isn't a Debian package and there's therefore nowhere for
me to reassign this bug, I have to simply close it.
Thanks,
--
Colin Watson [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
