🚀 go-pugleaf

In article <494rs2$7o7@rzsun02.rrz.uni-hamburg.de>, senoucci@informatik.uni-hamburg.de (Karim 'Kasi Mir' Senoucci) writes:
|> Hello all,
|> We still have problems using MHS and FirstMail on our one-server Netware
|> 4.1-System. We now got so far:
|> 
|> -- MHS seems to be installed correctly; we even can *use* the MHS features
|>    via WinFirstMail (i.e. we can send and receive mail using it).
|> -- The DOS-Version, however, till complains that "the Supervisor" has con-
|>    figuered the system so that the mailbox homedir must be local and won't
|>    run until you set this to a local directory. If you do this, I`ll work
|>    fine until you quit and restart it, when the problems reappear. 
|> -- newmail, a supplement for MHS which shall display the numder of new msgs,
|>    doesn't do anything, no matter how many unread (or unseen) msgs there are
|>    for the respective user.
|> All this makes the MHS pretty unusable for us, but we don't want to switch
|> to a third-party system whitch is not that well supported by the adminis-
|> tration tools unless we really have to. So, does anyone know, why MHS be-
|> haves like this? Is there any switch/option/file we didn't find to solve 
|> this problem? FirstMail and Newmail are version 1.2 (R1), the MHS is 1.00a.

Can't answer your questions in detail, but I do know that MHS stuff is poorly
documented and the installation tools for it do a poor job.  I was able to get
the system at our church working after fiddling off and on for a couple of
months, but I'm afraid I can't remember any details.

NEWMAIL is reported by others to be unreliable.  On the advice of someone in one
of these newsgroups some months back, I created a BAT file that checks for the
existence of certain files and throws the user into FirstMail if the check shows
that mail is present.  This approach seems to work fine.

Dan Hicks 

IBM   Rochester, Minnesota