Date: Thu, 16 Aug 2001 10:32:58 +0100 From: Matthew Seaman <matthew.seaman@tornadogroup.com> To: security@FreeBSD.ORG Subject: Re: cvs commit: src/etc inetd.conf Message-ID: <3B7B934A.67B39698@tornadogroup.com> References: <200108151940.f7FJepc73604@hak.lan.Awfulhak.org> <p0510100cb7a09144a1c3@[128.113.24.47]> <20010815170217.F14206@pir.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Peter Radcliffe wrote:
>
> Garance A Drosihn <drosih@rpi.edu> probably said:
> > "cron'd events", such as if you add your own cron jobs, cron will
> > email you if the process fails, or output from the process when
> > it succeeds (depending on how you have the job setup). Cron itself
> > expects it can send mail. So does lpd (if a user does 'lpr -m',
> > for instance).
>
> So why can't we run sendmail by default, just with no '-bd' option
> so it doesn't listen on port 25. Local mail will get delivered,
> it's not a remote security problem ...
Much of the time you don't even need to do that. You can run quite happily
and send e-mail without any sort of long-lived sendmail process running. Most
processes that want to send mail will invoke /usr/sbin/sendmail directly to
pipe the message into --- it's only if immediate delivery fails (*) that the
message will end up in the queue where it will languish until `sendmail -q'
gets run.
Matthew
(*) or you've altered the sendmail config to queue everything by default, in
which case I'll suppose that you know what you're doing...
--
Matthew Seaman Tel: 01628 498661
Certe, Toto, sentio nos in Kansate non iam adesse.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-security" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3B7B934A.67B39698>