That's what I did and I know running ps -eaf shows sendmail is not
runnning. Sorry for not making it clearer but was wondering if it was
the "right" way to do it. :-)
I havn't used Solaris for several years and belive svcadm is new to
Solaris 10, well its new to me.
Paul

My hint meant almost the same: Verify that there is no more sendmail
running by checking if you can get a connection on 127.0.0.1:25.
[color=blue]
> Sorry for not making it clearer but was wondering if it was
> the "right" way to do it. :-)
> I havn't used Solaris for several years and belive svcadm is new to
> Solaris 10, well its new to me.[/color]

You're right: The Service Management Framework (SMF) came up with
Solaris 10.

Christian Schmidt <ChriSchmiLi@gmx.de> wrote:[color=blue]
> Paul Johnston schrieb/wrote:[color=green]
>> That's what I did and I know running ps -eaf shows sendmail is not
>> runnning.[/color]
>
> My hint meant almost the same: Verify that there is no more sendmail
> running by checking if you can get a connection on 127.0.0.1:25.[/color]

This way your machine also won't be able to send mail (or clean up the local
mail queue if there network problems). If you don't want the machine be able
to receive mail, but it should be able to send mail out a better solution
would be:

Create or modify the file /etc/default/sendmail. Add or edit the following
line:

OPTIONS=-ODaemonPortOptions=Addr=localhost

This way the daemon will only listen on the loopback interface. Then the
above test doesn't work any more. Instead check with a telnet connection
on the public interface: