From owner-freebsd-security Wed Aug 9 0:12:16 2000 Delivered-To: freebsd-security@freebsd.org Received: from nenya.ms.mff.cuni.cz (nenya.ms.mff.cuni.cz [195.113.17.179]) by hub.freebsd.org (Postfix) with ESMTP id 7E30F37BD69 for ; Wed, 9 Aug 2000 00:12:08 -0700 (PDT) (envelope-from mencl@nenya.ms.mff.cuni.cz) Received: from localhost (mencl@localhost) by nenya.ms.mff.cuni.cz (8.9.3+Sun/8.9.1) with ESMTP id JAA05630 for ; Wed, 9 Aug 2000 09:12:03 +0200 (MET DST) Date: Wed, 9 Aug 2000 09:12:03 +0200 (MET DST) From: "Vladimir Mencl, MK, susSED" To: FreeBSD-SECURITY Subject: Re: pine 4.21 port issues? In-Reply-To: <20000808201626.I261@speedy.gsinet> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, 8 Aug 2000, Gerhard Sittig wrote: > Question: How does Pine (or C-Client in this scenario) modify > the mailbox and how does it lock against the MTA delivering into > the box? > Well, does anybody now, how the locking against the MTA is done? How do multiple copies of the MTA lock against each other (e.g., multiple procmails) ? And how does finally an MUA lock against the MTA ? Is there a convention (or a standard) for this locking? Or is it MTA (e.g., sendmail) specific? (I guess no). Really curious Vlada To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message