Scott Parks wrote in a message to all:
 SP> I understand what Mercury is doing when it is dealing directly 
 SP> with our Netware server .... such as pulling mail from a QUEUE 
 SP> and sending it out _and_ receiving mail ..... but .....
Mercury, since it runs as a suite of NLMs, accesses the MHS queue on the 
local disk, through the appropriate NetWare API.
 SP> we have a group in our building that only uses POP3 to access 
 SP> mail from an outside provider and they too are using our SMTP 
 SP> server according to the Mercury monitor.  The question becomes, 
 SP> do they need ours or would their software go out and find 
 SP> another one?  I know there is nothing pointing their mailers at 
 SP> ours and there are others available with no retrictions but  
 SP> not on our local net. They'd have to go through two routers to 
 SP> the district DNS machine.
I'm not sure I understand.  First, POP3 can be used either bidirectionally 
for your clients to send and receive mail, or unidirectionally for your 
clients to receive mail.  In the latter case, they would use SMTP to send 
mail.  By default, the client software probably expects to send and receive 
mail using the same server, regardless of the protocols.
Second, Mercury can support POP3 clients in addition to MHS clients if the 
appropriate POP support NLM (MERCURYP.NLM or MERCNDSP.NLM) is loaded.  If 
SMTP support is also loaded, your clients can retrieve via POP3 the same mail 
that comes in via SMTP, never touching MHS directly.
Third, Mercury is not necessarily able to send out mail via SMTP except with 
the aid of a smart remailer which can do DNS resolution.  In general, this is 
a Unix machine running Sendmail.  This is sometimes provided by your ISP, 
although it can also be provided locally.
 
-- Mike
--- 
---------------