Here's the theory:
When protecting your computer from unwanted access (cracking) you want to know
_for sure_ that the daemons you are running are /secure/. Well, the larger the
daemon, the less possible it is to guarantee that you've taken care of all
buffer overruns, and whatever other attack a script-kiddie can come up with.
Sendmail is a _/huge/_ program. We're talkin' _monstrous_. Obviously very
difficult to protect against attacks (they've done an admirable job, despite
the amount of code). So - to protect your system, you run smapd, this handles
the incoming connections and stores the mail file so that sendmail can take
care of it. It handles relay control (e.g. stopping people from using your
server to spam) and it takes care of people tryin' to crack your machine.
smapd is relatively small (maybe 200 or so lines of code) and this code has
been darn near guaranteed to be crack-free. So, people run smapd to protect
their sendmail system.
smapd is NOT an outgoing proxy in the sense that you have http proxies and
such. If you're not running a sendmail server, you do _not_ need smapd. Your
provider might, but that's their problem, dig it?
> I set up a POP3 proxy server on a linux server with pop3gwd.
> Now I want to install a SMTP proxy server for my users to be able to send
> Squid doesn't do that so I was advised to use smap and smapd from TIS.
> The documentation doesn't talk about the way I do to enter the IP address of
> the SMTP server of my internet provider.
> Does it happen in the netperm-table file ?
> Do I need to modify the sendmail.conf ?
> I would be very grateful if someone could explain me th process to do.
"The use of COBOL cripples the mind; its teaching should,
therefore, be regarded as a criminal offense."
-- E. W. Dijkstra (1982)