Subject: bin/32279: send-pr doesn't work when sendmail is configured to queue and send via dial-up
To: None <gnats-admin@netbsd.org, netbsd-bugs@netbsd.org>
From: None <david.forrai@gemair.com>
List: netbsd-bugs
Date: 12/11/2005 05:45:00
>Number: 32279
>Category: bin
>Synopsis: send-pr doesn't work when sendmail is configured to queue and send via dial-up
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: bin-bug-people
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Sun Dec 11 05:45:00 +0000 2005
>Originator: David Forrai
>Release: NetBSD 2.0.2_STABLE
>Organization:
Self
>Environment:
NetBSD dpfpc.lan.invalid 2.0.2_STABLE NetBSD 2.0.2_STABLE (DPFPC2) #1: Thu Aug 11 23:07:55 EDT 2005 root@:/usr/src/sys/arch/i386/compile/DPFPC2 i386
>Description:
I have configured sendmail to queue mail until invoked with the -q option while connected through dial-up. I followed the directions specified in the NetBSD Guide. I encounter no problems when sending mail using a MUA but send-pr doesn't work. send-pr indicates that the message was sent successfully but the message does not show up in /var/spool/mqueue and is not sent.
I edited the send-pr script by changing the MAIL_AGENT variable to force reading /etc/mail/sendmail.cf and provide verbose output as shown:
MAIL_AGENT="/usr/sbin/sendmail -C/etc/mail/sendmail.cf -v -oi -t"
This time I received the messages as follows:
dpfpc >send-pr
a)bort, e)dit or s)end? s
gnats.NetBSD.org: Name server timeout
gnats-bugs@gnats.NetBSD.org... Transient parse error -- message queued for future delivery
collect: Cannot write ./dfjB3LE970005971 (bfcommit, uid=1001, gid=100): Permission denied
queueup: cannot create queue file ./qfjB3LE970005971, euid=1001: Permission denied
send-pr: mysterious mail failure.
send-pr: the problem report remains in /tmp/pbad.011967aa and is not sent.
dpfpc >
It appears that when send-pr is invoked, sendmail is not reading the default configuration file. Wheh forced to read it, it does not seem capable of creating the queue files as an ordinary user.
>How-To-Repeat:
I've tried several invocations of send-pr with the same result.
>Fix:
I have not been able to determine a fix.