linux-admin.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Yuri Csapo <ycsapo@exchange.mines.edu>
To: Glynn Clements <glynn@gclements.plus.com>
Cc: Yuri Csapo <ycsapo@mines.edu>, linux-admin <linux-admin@vger.kernel.org>
Subject: Re: sendmail blues
Date: Sat, 7 Nov 2009 05:49:19 -0700	[thread overview]
Message-ID: <4AF56CCF.9060608@exchange.mines.edu> (raw)
In-Reply-To: <19189.21952.988653.496177@cerise.gclements.plus.com>

Glynn,

Thank you for the thorough answer - reminded me of "the good old days."

Glynn Clements wrote:
> Sendmail only uses submit.cf if it exists, otherwise it uses
> sendmail.cf. Also, you can force a particular configuration with the
> -Ac and -Am switches.

I was not aware of this. I'll do some tests Monday.

> FWIW, the rationale behind having a separate MSP is to eliminate the
> need for sendmail to be setuid-root; instead, the sendmail binary is
> setgid to the "smmsp" group.

I understand the rationale. And I suppose it makes sense these days when 
a lot of people running Linux are desktop users who have no idea and no 
desire to learn better. Sendmail was hit hard in the early days of the 
Eternal September because of this, so they had to do something. OTOH I 
always thought it very silly how everybody runs away from the root user, 
designing mechanisms to prevent its use (i.e. root can't log on to a 
default install of Ubuntu). It ends up turning sudo into Linux's version 
of Microsoft's OK button - people use without reading, understanding or 
caring, compounding the problem. Of course you shouldn't be root for 
your day-to-day tasks but there's nothing wrong with using root when 
that's required. It's a matter of common sense and best practices. Sorry 
for the rant, you just happened to push one of my buttons... <sm>

> 
> BTW, Local delivery shouldn't require that anything is listening on
> port 25. However, you may have to tell sendmail what constitutes
> "local"; it's possible that sendmail is treating "localhost" as a
> normal (remote) domain rather than a local one.
> 

Local delivery is not what I'm looking for. I want this box to forward 
along to our smart host.

Thanks

Yuri

  reply	other threads:[~2009-11-07 12:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-06 21:54 sendmail blues Yuri Csapo
2009-11-06 22:48 ` Gerardo Juarez-Mondragon
2009-11-06 23:51   ` Yuri Csapo
2009-11-06 23:51 ` Max Gribov
2009-11-06 23:53   ` Yuri Csapo
2009-11-07  0:08     ` Max Gribov
2009-11-07 11:10 ` Glynn Clements
2009-11-07 12:49   ` Yuri Csapo [this message]
2009-11-08  7:13     ` Glynn Clements

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4AF56CCF.9060608@exchange.mines.edu \
    --to=ycsapo@exchange.mines.edu \
    --cc=glynn@gclements.plus.com \
    --cc=linux-admin@vger.kernel.org \
    --cc=ycsapo@mines.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).