Re: Accepting external sendmail on 2.0.2

From: Frederick Bruckman (fredb_at_immanent.net)
Date: 07/03/05 

Date: Sat, 02 Jul 2005 23:40:53 -0500

In article <1gz3830.o1bbhyvudhqgN%rlange@mindspring.com>,
        rlange@mindspring.com (Richard Lange) writes:
> Hello, I installed 2.0.2 this week on my internal lan to look at sendmail, and
> spent today trying to figure out why I could only listen on localhost.
>
> After going down a wrong path with the new configs in rc.conf, and playing with
> hosts.allow, I finally found
>
> /usr/share/sendmail/cf/netbsd-proto.mc and copied it to my-netbsd-proto.mc and
> added the line
>
> DAEMON_OPTIONS(`Family=inet, address=192.168.0.50, Name=MTA, Modifiers=0')dnl
>
> under a similar line about 127.0.0.1 ( copied that line and pasted it in, and
> put in the 192 address ), and then "make" that file.

If you only have one interface, or if you don't mind listening on all
the ones you do have, "address=0.0.0.0" should work, too -- or simply
comment out that line. The point of that line in the default config
is to let programs such as "cron" invoke "sendmail" or "mail", and
let them "just work", without enabling a listener on the network. Of
course, if you're setting up a mail server, it's a different story.
 
> So now it seems to work, but is this the correct thing to do? Could an
> explanation of this step not be in a faq or the guide or something? The only
> clue I found that tipped me off, was a faq at sendmail.org about a redhat issue.

It sounds reasonable. It may be better, for a completely internal
server, to comment out all DAEMON_OPTIONS, while gateway hosts may
want to set CLIENT_OPTIONS, too (to set the outgoing interface).

Appendix B of the NetBSD Guide tells how to submit changes. 

-- 
Frederick