> which, according to a post in the archives, indicates that
> vmailmgrd isn't
> Would appreciate any guidance on how to track down the problem.
Never mind....managed to notice that without fail, when entering the command
to start vmailmgrd, I was calling the socket /tmp/.vmailgrd, leaving out the
<searches for hard object to beat head against>