Date: Mon, 08 Feb 2010 14:08:04 +0000 From: Matthew Seaman <m.seaman@infracaninophile.co.uk> To: John <john@starfire.mn.org> Cc: freebsd-questions@freebsd.org Subject: Re: Breaking the sendmail code / sendmail for dummies Message-ID: <4B701AC4.4010902@infracaninophile.co.uk> In-Reply-To: <20100208071155.B19928@starfire.mn.org> References: <20100207222929.A6166@starfire.mn.org> <alpine.BSF.2.00.1002072217431.74949@wonkity.com> <20100208071155.B19928@starfire.mn.org>
next in thread | previous in thread | raw e-mail | index | archive | help
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 08/02/2010 13:11, John wrote:
> So - I did all that you suggested, and it sure looks like it worked,
> but I still have a question.  It did both the hostname.mc and the
> hostname.submit.mc files and .cf files, but I didn't do anything
> to the hostanme.submit.mc file.  Am I still OK?
Yes.  The submit.mc / submit.cf files very rarely need any sort of
customization.  All of the real processing happens in the sm-mta (mail
transfer agent) instance: the only reason for the sm-msp (mail
submission process) instance to exist is to provide secure user-level
access to the privileged sm-mta process without having to make the
sendmail binary run setuid-root.
	Cheers,
	Matthew
- -- 
Dr Matthew J Seaman MA, D.Phil.                   7 Priory Courtyard
                                                  Flat 3
PGP: http://www.infracaninophile.co.uk/pgpkey     Ramsgate
                                                  Kent, CT11 9PW
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.14 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAktwGsQACgkQ8Mjk52CukIz5uACfcCOVYbgezUTXUVpQOj0dHXnf
lFsAnjXD1uD8vsFuwvJK1ugi9us6B1zl
=eCwJ
-----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4B701AC4.4010902>
