Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!usc!cs.utexas.edu!uunet!bu.edu!bu-cs!nntp-read!jbw From: jbw@bucsf.bu.edu (Joe Wells) Newsgroups: gnu.emacs.bug Subject: Re: rmail.el should obey bash's MAILPATH Message-ID: Date: 21 Jan 90 03:11:31 GMT References: <8912261600.AA01743@ouareau.IRO.UMontreal.CA> Sender: news@bu.edu.bu.edu Distribution: gnu Organization: Boston University Computer Science Department Lines: 20 In-reply-to: mcgill-vision!iros1!pinard@EDDIE.MIT.EDU's message of 26 Dec 89 16:00:26 GMT In article <8912261600.AA01743@ouareau.IRO.UMontreal.CA> mcgill-vision!iros1!pinard@EDDIE.MIT.EDU (Francois Pinard) writes: When rmail-primary-inbox-list is nil, rmail.el(rmail) dynamically constructs it using rmail-spool-directory, then $LOGNAME or $USER. Under bash, the user inbox is described by $MAILPATH. I believe rmail should first check for the existence of $MAILPATH first. The contents of the environment variable MAILPATH do not necessarily have anything to do with the mail spool files that should be checked for new mail. MAILPATH is used to have ksh/bash check timestamps on certain files and print certain messages. These files are not necessarily mail spool files, nor do they need to belong to the user. In summary, it is dangerous to presume that the contents of the environment variable MAILPATH point to the user's mail spool files. -- Joe Wells jbw%bucsf.bu.edu@bu-it.bu.edu ...!harvard!bu-cs!bucsf!jbw