Re: sendmail error, "MX list for mydomain.com points back to server.mydomain.com"

I'm going to try installing sendmail from ports, as it's a newer 
version,
and will be easier to poke around in.  But first, a sanity check.
It's been a while since I've needed to build ports; been using pkgs.
When I built the sendmail port, it built 60+ other ports, which I 
assumed
were things already installed in some version for the sendmail that came
with the system.

I "think" pkgs and ports both install libraries in the same place, 
right?

If so, is it likely installing sendmail from ports will break other 
things
installed as packages?  I'm thinking it will install newer versions, but
they should be upward compatible for the other pkgs already installed,
correct?  I remember seeing rumblings on the list about if you install
pkgs, only use pkgs; and if you install from ports, do everything from 
ports.

The existing sendmail doesn't appear to have a lot of dependencies:

$ ldd /usr/sbin/sendmail
/usr/sbin/sendmail:
         libutil.so.9 => /lib/libutil.so.9 (0x80024d000)
         libc.so.7 => /lib/libc.so.7 (0x800265000)
$ file !$
/usr/sbin/sendmail: symbolic link to mailwrapper
$ which mailwrapper
/usr/sbin/mailwrapper
$ ldd /usr/sbin/mailwrapper
/usr/sbin/mailwrapper:
         libutil.so.9 => /lib/libutil.so.9 (0x80024d000)
         libc.so.7 => /lib/libc.so.7 (0x800265000)
$ file /usr/sbin/mailwrapper
/usr/sbin/mailwrapper: ELF 64-bit LSB executable, x86-64, version 1 
(FreeBSD), dynamically linked, interpreter /libexec/ld-elf.so.1, for 
FreeBSD 12.4, FreeBSD-style, stripped

So why does the sendmail port build so many other ports?
I don't have the output from the build to refer to; just remember having 
to do
configuration and turn off NLS and DOC on some.

Gary