[SunHELP] Sending Mail without sendmailD

[Jim Pennino]

On Thu, May 08, 2003 at 10:02:43AM -0600, Cinense, Mark wrote:
> Ok... so I made a change now to /etc/mail/submit.cf on line 
> 
> D{MTAHost}[smtp.your.domain]
> 
> To my relay host, and client email sends out now.  The only difference is
> now I see sender at host.domain.com as the sender instead of sender at domain.com.
> 
> 
> So what is the difference between sendmail.cf and submit.cf?
> 
> -Mark
> 8o)
> 

>From the sendmail SECURITY file:


Summary
-------

This is a brief summary how the two configuration files are used:

sendmail.cf     For the MTA (mail transmission agent)
        The MTA is started by root as daemon:

                /PATH/TO/sendmail -L sm-mta -bd -q1h

        it accepts SMTP connections (on ports 25 and 587 by default);
        it runs the main queue (/var/spool/mqueue by default).

submit.cf       For the MSP (mail submission program)
        The MSP is used to submit e-mails, hence it is invoked
        by programs (and maybe users); it does not run as SMTP
        daemon; it uses /var/spool/clientmqueue by default; it
        can be started to run that queue periodically:

                /PATH/TO/sendmail -L sm-msp-queue -Ac -q30m


As for the host.domain.com thing, from the sendmail README:

allmasquerade   If masquerading is enabled (using MASQUERADE_AS), this
                feature will cause recipient addresses to also masquerade
                as being from the masquerade host.  Normally they get
                the local hostname.  Although this may be right for
                ordinary users, it can break local aliases.  For example,
                if you send to "localalias", the originating sendmail will
                find that alias and send to all members, but send the
                message with "To: localalias at masqueradehost".  Since that
                alias likely does not exist, replies will fail.  Use this
                feature ONLY if you can guarantee that the ENTIRE
                namespace on your masquerade host supersets all the
                local entries.

limited_masquerade
                Normally, any hosts listed in class {w} are masqueraded.  If
                this feature is given, only the hosts listed in class {M} (see
                below:  MASQUERADE_DOMAIN) are masqueraded.  This is useful
                if you have several domains with disjoint namespaces hosted
                on the same machine.

masquerade_entire_domain
                If masquerading is enabled (using MASQUERADE_AS) and
                MASQUERADE_DOMAIN (see below) is set, this feature will
                cause addresses to be rewritten such that the masquerading
                domains are actually entire domains to be hidden.  All
                hosts within the masquerading domains will be rewritten
                to the masquerade name (used in MASQUERADE_AS).  For example,
                if you have:

                        MASQUERADE_AS(`masq.com')
                        MASQUERADE_DOMAIN(`foo.org')
                        MASQUERADE_DOMAIN(`bar.com')

                then *foo.org and *bar.com are converted to masq.com.  Without
                this feature, only foo.org and bar.com are masqueraded.

                    NOTE: only domains within your jurisdiction and
                    current hierarchy should be masqueraded using this.

local_no_masquerade
                This feature prevents the local mailer from masquerading even
                if MASQUERADE_AS is used.  MASQUERADE_AS will only have effect
                on addresses of mail going outside the local domain.

masquerade_envelope
                If masquerading is enabled (using MASQUERADE_AS) or the
                genericstable is in use, this feature will cause envelope
                addresses to also masquerade as being from the masquerade
                host.  Normally only the header addresses are masqueraded.


These things go in your .mc file that becomes sendmail.cf.

-- 
Jim Pennino