From owner-freebsd-current  Thu Oct 31 16:01:21 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id QAA18002
          for current-outgoing; Thu, 31 Oct 1996 16:01:21 -0800 (PST)
Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id QAA17994
          for <current@freebsd.org>; Thu, 31 Oct 1996 16:01:19 -0800 (PST)
Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.8.2/CET-v2.1) with SMTP id AAA02515; Fri, 1 Nov 1996 00:01:05 GMT
Date: Fri, 1 Nov 1996 09:01:05 +0900 (JST)
From: Michael Hancock <michaelh@cet.co.jp>
To: Terry Lambert <terry@lambert.org>
cc: lada@ws2301.gud.siemens.co.at, dubois@primate.wisc.edu,
        current@freebsd.org
Subject: Re: /var/mail (was: re: Help, permission problems...)
In-Reply-To: <199610312338.QAA26617@phaeton.artisoft.com>
Message-ID: <Pine.SV4.3.95.961101085119.2317C-100000@parkplace.cet.co.jp>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Yes, it's pretty bogus.  These are probably the work-arounds that Mark
was alluding to.

As I mentioned at the bottom of my previous message I prefer flock() and
proper permissions on /var/mail.

What I really like is this.

1) mail.local is replaced by procmail and the system wide configuration is
set to deliver mail to /home/%u/mail/mbox. 

2) pop3 is modified to look in /home/%u/mail/mbox.  Alternatively, use
imapd.

3) Configure or modify all mailer readers to use /home/%u/mail/mbox as the
inbox.

Yeah, I know.  It would be wishful thinking to ever see a distribution
come this way. 

Regards,


Mike Hancock

On Thu, 31 Oct 1996, Terry Lambert wrote:

> > Got me on the first one, but the prankster has to predict names.  It's
> > probably acceptable for a lot of sites.
> > 
> > In the second case use an administrative program that sends mail each time
> > an account is created.
> 
> Bletch.  Now you are encoding state in things which may not match the
> system vendor's idea of defaults.
> 
> This would be bad.
> 
> The choice to send a "welcome" message is an administrative issue, not
> a system usage issue.
> 
> The choice to use something that deletes empty mailboxes by default
> (like -- elm) is a user issue, not a system usage issue.
> 
> 
> 					Terry Lambert
> 					terry@lambert.org
> ---
> Any opinions in this posting are my own and not those of my present
> or previous employers.
>