home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!gatech!usenet.ins.cwru.edu!cleveland.Freenet.Edu!ce095
- From: ce095@cleveland.Freenet.Edu (Jeffrey Scott Traigle)
- Newsgroups: comp.mail.elm
- Subject: Re: newmail problem
- Date: 23 Nov 1992 20:39:39 GMT
- Organization: Case Western Reserve University, Cleveland, OH (USA)
- Lines: 14
- Message-ID: <1erfibINNpna@usenet.INS.CWRU.Edu>
- References: <1erf0oINNp8k@usenet.INS.CWRU.Edu>
- Reply-To: ce095@cleveland.Freenet.Edu (Jeffrey Scott Traigle)
- NNTP-Posting-Host: hela.ins.cwru.edu
-
-
- In a previous article, ce095@cleveland.Freenet.Edu (Jeffrey Scott Traigle) says:
- >
- >I set the option during configuration to have newmail run in the
- >background automatically. It isn't working however. I even try running
- >it in the background explicitly, but it replies with "Done" after a
- >second or two. What happened? It worked in earlier versions, I know.
- >
- >Jeff Traigle
-
- A little correction in the behavior that I just discovered. If I run
- newmail explicitly, it does spawn a newmail process that remains active
- and works. In previous versions, this wasn't necessary with the flag
- during configuration set to run newmail automatically.
-