Mike Bilow wrote in a message to Scott Parks:
 MB> Third, Mercury is not necessarily able to send out mail via
 MB> SMTP except with the aid of a smart remailer which can do
 MB> DNS resolution.  In general, this is a Unix machine running
 MB> Sendmail.  This is sometimes provided by your ISP, although
 MB> it can also be provided locally.
The group that uses POP3 aims it outside our net but somehow they
use our SMTP agent on the way out.  I've not noticed if any incoming
shows up but believe they connect directly to the remote server.
Since the mail they send goes in many directions and not just the 
POP3 address, we seem to be their remailer.   When I first noticed
this certain IP address connecting I couldn't figure out who it
was so I blocked it with REFUSE in Mercury and sure enough it killed 
their ability to send mail.
I assume this is similar to SPAMMERS using dumb remailers that can't
or don't refuse anyone ... but I don't know how to point something
like Eudora in a certain direction.  Maybe I should look at their
Eudora setups?
The main reasons I'm interested is that Mercury won't run with the
Netware 3.11 NLM's that Backup Exec wants and we want to go to 
Exchange anyway as it's a better teaching tool.  With Exchange there
are not any monitor screens that I know of to track SMTP activity
and I don't want to deprive that group that uses it remotely.
Scott Parks
sparks@helix.eskimo.com 
--- GEcho 1.11+
---------------