NetBSD Problem Report #41105

From reed@reedmedia.net  Mon Mar 30 21:56:42 2009
Return-Path: <reed@reedmedia.net>
Received: from mail.netbsd.org (mail.netbsd.org [204.152.190.11])
	by www.NetBSD.org (Postfix) with ESMTP id 39BEB63B8C8
	for <gnats-bugs@gnats.NetBSD.org>; Mon, 30 Mar 2009 21:56:42 +0000 (UTC)
Message-Id: <4679-1238450168@reedmedia.net>
Date: Mon, 30 Mar 2009 16:56:09 -0500
From: reed@reedmedia.net
Reply-To: reed@reedmedia.net
To: gnats-bugs@gnats.NetBSD.org
Subject: NetBSD 5.0_RC3 postfix mail setup
X-Send-Pr-Version: 3.95

>Number:         41105
>Category:       bin
>Synopsis:       postfix mail not setup
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    bin-bug-people
>State:          closed
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Mon Mar 30 22:00:01 +0000 2009
>Closed-Date:    Mon Sep 07 02:22:27 +0000 2015
>Last-Modified:  Mon Sep 07 02:22:27 +0000 2015
>Originator:     reed@reedmedia.net
>Release:        NetBSD 5.0_RC3
>Organization:
>Environment:


System: NetBSD new-host-4 5.0_RC3 NetBSD 5.0_RC3 (GENERIC) #1: Wed Mar 25 17:26:06 CDT 2009  reed@new-host-4:/home/reed/src/sys/arch/amd64/compile/GENERIC amd64
Architecture: x86_64
Machine: amd64
>Description:
Installed 5.0_RC3. Never setup any email on it.

Few days later noticed many postdrop processes and much noise in logs,
like:

Mar 16 22:00:05 new-host postfix/postdrop[18865]: warning: mail_queue_enter: create file maildrop/964063.18865: No such file or directory
Mar 16 22:00:15 new-host postfix/postdrop[18865]: warning: mail_queue_enter: create file maildrop/979657.18865: No such file or directory
...
Mar 30 16:54:03 new-host-4 postfix/postdrop[868]: warning: mail_queue_enter: create file maildrop/992489.868: No such file or directory
Mar 30 16:54:04 new-host-4 postfix/postdrop[8886]: warning: mail_queue_enter: create file maildrop/823024.8886: No such file or directory

$ sudo zgrep 'ning: mail_queue_e' /var/log/maillog* | wc -l
  147731

>How-To-Repeat:
Installed NetBSD 5.0_RC3.
>Fix:
Don't continually log mail problems.
Preferably have some working mail in default install.
(As for me, I will probably install my own SMTP-out "mailout" tool
and don't run any daemon for mail.)

>Release-Note:

>Audit-Trail:

State-Changed-From-To: open->feedback
State-Changed-By: dholland@NetBSD.org
State-Changed-When: Sat, 05 Sep 2015 20:34:46 +0000
State-Changed-Why:
Is this still an issue? (I'm going to assume not if I don't hear anything)


From: "Jeremy C. Reed" <reed@reedmedia.net>
To: gnats-bugs@NetBSD.org
Cc: 
Subject: Re: bin/41105 (postfix mail not setup)
Date: Sat, 5 Sep 2015 20:43:28 -0500 (CDT)

 I don't know if this is still a problem. It is okay to close this 
 ticket.

From: David Holland <dholland-bugs@netbsd.org>
To: gnats-bugs@NetBSD.org
Cc: 
Subject: Re: bin/41105 (postfix mail not setup)
Date: Sun, 6 Sep 2015 05:57:42 +0000

 On Sun, Sep 06, 2015 at 01:45:01AM +0000, Jeremy C. Reed wrote:
  >  I don't know if this is still a problem. It is okay to close this 
  >  ticket.

 mrg says that the same thing still happens if you shut off postfix and
 don't configure some other kind of mail delivery. This is not entirely
 optimal. But I'm not sure if it's really worth carrying around a
 ticket for, either, especially since it's kind of a postfix upstream
 issue.

 -- 
 David A. Holland
 dholland@netbsd.org

State-Changed-From-To: feedback->closed
State-Changed-By: dholland@NetBSD.org
State-Changed-When: Mon, 07 Sep 2015 02:22:27 +0000
State-Changed-Why:
I would say that the real problem here is that the system was broken out of
the box, which is no longer the case. If anyone would like to report upstream
that postfix doesn't react too well to having its daemons not running, that
would be great but I don't think we need a NetBSD ticket for it.


>Unformatted:

Home	PR Database Search