[Raw Msg Headers][Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: File locking broken with 2.99.45 on FreeBSD 2.1
On Sun, 26 Jan 1997, Dario Alcocer wrote:
> Is anyone using ZMailer on FreeBSD? I've installed it on my PC,
> 486DX80 with 32MB. After installation, I tried testing it by sending
> a message to another local address, but I did not see the message
> delivered to the local mailbox, nor did I recieve a bounce message.
> I went rummaging in $POSTOFFICE/queue to see if I could figure out
> what went wrong, and I found this in one of the message files:
> % channel error
> % todsn ORCPT=rfc822;postoffice
> % to <postoffice>
> % env-end
> % To: dummy:; (error trapped source)
> % From: The Post Office <postmaster>
> % Sender: mailer-daemon
> % Subject: Double-fault: Delivery reports about your email
> % Cc: The Post Office <postoffice>
> % MIME-Version: 1.0
> % Content-Type: multipart/report; report-type=delivery-status;
> % boundary="A41C6D020.854311499=_/pino.connectnet.com"
> % --A41C6D020.854311499=_/pino.connectnet.com
> % Content-Type: text/plain
> % This is a collection of reports about email delivery
> % process concerning a message you originated:
> % <local root alcocer 0>: can't dotlock "/var/spool/mail/alcocer": Permission deni
> % ed (this is abnormal, investigate!)
> How should file locking be configured on FreeBSD? In case it matters,
> I *was* running 2.99.26 with HOSTENV (in Config) set to FreeBSD-2.0,
> and I was not encountering file locking problems before.
Don't do dot locking when delivering to the standard BSD mboxes.
flock() locking is quite safe on FreeBSD (and faster than dotlocking).
The way Zmailer does mailbox dotlocking it appears that the mail spool
directory needs to be mode 1777, which I would not recommend.
> Any advice/suggestions appreciated.
> Dario Alcocer