From owner-freebsd-hackers Sun Jan 21 1:42: 7 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mailout06.sul.t-online.com (mailout06.sul.t-online.com [194.25.134.19]) by hub.freebsd.org (Postfix) with ESMTP id A94E437B400; Sun, 21 Jan 2001 01:41:46 -0800 (PST) Received: from fwd02.sul.t-online.com by mailout06.sul.t-online.com with smtp id 14KH0I-0005K5-01; Sun, 21 Jan 2001 10:41:42 +0100 Received: from frolic.no-support.loc (520094253176-0001@[217.80.111.50]) by fmrl02.sul.t-online.com with esmtp id 14KH08-05zm7cC; Sun, 21 Jan 2001 10:41:32 +0100 Received: (from bjoern@localhost) by frolic.no-support.loc (8.11.1/8.9.3) id f0L9XPG01498; Sun, 21 Jan 2001 10:33:25 +0100 (CET) (envelope-from bjoern) From: Bjoern Fischer Date: Sun, 21 Jan 2001 10:33:24 +0100 To: Roelof Osinga Cc: freebsd-stable@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: MAIL set by whom? Message-ID: <20010121103324.A297@frolic.no-support.loc> References: <3A6A50F3.307C9E06@nisser.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3A6A50F3.307C9E06@nisser.com>; from roelof@nisser.com on Sun, Jan 21, 2001 at 04:01:07AM +0100 X-Sender: 520094253176-0001@t-dialin.net Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > But what I need is /home/{$USER}/Maildir/ in order for Mutt to > work with Maildirs. The above /etc/login.conf parts don't do the > trick and other occurrences of MAIL I can't find. > > So what gives? (IOW please help! :) You can set MAIL via /etc/login.conf, all applications that use either login(1) or setusercontext(3) should work. Beware of ssh! The OpenSSH client, that is part of FreeBSD is completey buggy here: It sets MAIL to /var/mail/$USER, this is hardcoded. I have a dirty fix, maybe I'll clean it up and send it as a PR or to Kris (Kris, are you still ssh maintainer?) This whole stuff of initial user environment and friends has to be cleaned up to be consistent for all login methods: login(1), xdm, rsh, rlogin, ssh, telnet. I would volunteer(sic!) for a in detail analysis of this issue if I get feedback on this. (i.e. looking for inconsistencies, where to put on solutions (e.g. a pam module that evals /etc/login.conf via setusercontext(3)). To fiddle with user's .bash{rc,_profile}, .tcshrc, .whateverrc is the wrong way. Some rc files are not evaluated for non login shells, so you put it into .bashrc or whatever get executed for non login shells; if you do this you parameters will be overwritten each time you start a new shell (e.g. xterm). The user should have a minimal reasonable environment (even without shell rc files, if you want to go that far), that he/she may optionally extend or adapt. /etc/login.conf, maybe in combination with pam, is the right thing for doing this. Bjoern -- -----BEGIN GEEK CODE BLOCK----- GCS d--(+) s++: a- C+++(-) UB++++OSI++++$ P+++(-) L---(++) !E W- N+ o>+ K- !w !O !M !V PS++ PE- PGP++ t+++ !5 X++ tv- b+++ D++ G e+ h-- y+ ------END GEEK CODE BLOCK------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message