Mercury/32 was never written to be run as a service in the first place. So
we don't officially support it in that mode. Something to consider for a
future release.
--
+--------------------------------------------------+
| David J. Kocmoud (Official Pegasus Mail Tech Support Member)
| ** I can only return your call collect to toll phone numbers **
| 2403 Colgate Circle, College Station, Texas 77840-4615 USA
| Voice: (409) 696-8586 (evenings)
| E-Mail: david-...@bigfoot.com
| Home Page: http://sago.tamu.edu/users/davek/
+--------------------------------------------------+
In article <3829AE52...@uhen.com>, on Wed, 10 Nov 1999 11:41:38 -
0600, David A. Uhen (d...@uhen.com) says...
> I've installed Mercury on NT4.0 as a service and the POP3 server is
> working fine. I've also got the SMTP and POP3 Clients to work with my
> local ISP. I can send and receive external mail as long as the Mercury
> GUI is up and running. I can see the polls occuring as scheduled and
> mail being transferred in and out. My problem is that when I log off of
> NT the client apps seem to halt while the POP3 server is unaffected. If
> I log back on and bring up the Mercury GUI the pending polls happen
> immediately and the mail is transferred. Any suggestions on how I can
> keep the Clients running while logged off of NT?
I heard that if you're running as a service you want to specify all the
pathnames as drive:directory rather than in UNC format since the service
starts before the network.
See http://bama.ua.edu/cgi-bin/wa?A2=ind9910C&L=Mercury&P=R161
--
'Bread and Circuses' is the cancer of democracy,
the fatal disease for which there is no cure.
-- Jubal Harshaw, 'To Sail Beyond the Sunset'
(Robert Heinlein)