All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ray Olszewski <ray@comarre.com>
To: linux-newbie@vger.kernel.org
Subject: Re: smtp vs sendmail query
Date: Thu, 10 Aug 2006 12:55:46 -0700	[thread overview]
Message-ID: <44DB8F42.8030604@comarre.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0608101339210.15749@localhost.localdomain>

James Miller wrote:
> I think I'm finally ready to abandon Pine as my e-mail client and to 
> start using Mutt. I thought of doing this a few years ago, but looking 
> over Mutt documentation and config files left me bewildered. I'm sure I 
> will still be confused about some of the program's workings, but it 
> seems, after 4 years or so of using and admin'ing my Linux system(s), I 
> have good enough grasp of the program's basics and related e-mail 
> workings now that I'm ready to give it a serious go. This switch is also 
> partly precipitated by certain ways in which Pine has been failing me. 
> Despite what I've said above, the present message is not a Mutt-specific 
> query: I'll probably be directing those to the Mutt user list. What I'm 
> wondering about is something more fundamental about e-mail technology.
> 
> One of the things that kept me from using Mutt previously was the fact 
> that it does not do smtp, but rather apparently relies on other programs 
> such as sendmail for passing mail to servers that in turn pass it to 
> other servers and eventually to recipients. I don't care how stupid I 
> might sound to the initiated in saying this, but for the 
> technically-challenged such as myself, having an extra layer of program 
> activity between the e-mail client and the outgoing server is confusing: 
> it's just another set of configuration files to edit and keep current, 
> and another place to look for errors should problems arise. At the same 
> time, I suppose there are good reasons for having a separate program to 
> do mail passing to outgoing servers. The most sensible reason I can 
> think of is that e-mailing is often done in an institutional 
> environment, one that has a machine on its network dedicated to mailing 
> functions. I have no experience of working in such an environment, so 
> I'm guessing at this, but that seems like it could provide a sensible 
> explanation for the separation between e-mail client and outgoing mail 
> server.
> 
> Anyway, Pine does do smtp: you enter info about your smtp server in its 
> config file, and away you go with sending out your mail. Mutt, as I 
> understand it "will never do smtp" (quotation from a Mutt information 
> site I haven't checked for a couple years but which I assume to reflect 
> the current state of affairs). I will thus, I assume, need to look into 
> getting and setting up a program to interact with the smtp server I will 
> be sending mail through. Sendmail is one I recall reading about: can 
> anyone supply names of, and recommendations about, others? I want the 
> simplest possible program for this one-user (Debian) machine.
> 
> Finally, can anyone enlighten me as to why a program like Mutt--which is 
> actually the only e-mail client I know of that won't interact with smtp 
> servers--will not do smtp? Is it for puristic reasons, i.e., because it 
> would somehow contaminate the program's perceived function by 
> introducing extra functionality? I.e., a line in the sand against 
> feature-creep? Could it be for some sort of security reasons?
> 
> Sorry for the long message. Input will be appreciated.
> 
> Thanks, James
> 
> PS Recommendations for other text-mode e-mail clients would also be 
> appreciated.

James -- I don't know why (or even if, really) the authors of Mutt don't 
build in smtp support. I could guess, but you don't need uninformed 
guessing.

I'm replying only because you reminded us that you are a Debian user. 
The off-the-shelf smtp program for Debian is exim, and if you did 
anything resembling a standard install of any recent version of Debian, 
you already have exim4 on your system, along with a symlink that lets 
you run it as "sendmail":

	new-flagg:/home/autovcr# ls -l /usr/sbin/sendmail
	lrwxr-xr-x  1 root root 5 Aug 30  2005 /usr/sbin/sendmail -> exim4

The details on setting this up (this HowTo is for Debian-Sarge, but I 
expect Etch and Sid are almost the same) are at 
http://pkg-exim4.alioth.debian.org/README/README.Debian

The short version (for Sarge or Sid, probably Etch too): as root, run 
"dpkg-reconfigure exim4-config" and tell it (I think, if I understand 
your setup right) "mail sent by smarthost; no local mail". The 
"smarthost" is the "smtp server" you identified to Pine.

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

      reply	other threads:[~2006-08-10 19:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-07 18:10 How to make KDE default windows manager? Jesse
     [not found] ` <1152306806.7439.4.camel@localhost>
     [not found]   ` <000301c6a21b$7a4bea10$6900a8c0@ANCHORMAN>
2006-07-08  7:37     ` Chris Largret
2006-07-11 11:35       ` Jesse
2006-07-09 20:43 ` cr
2006-07-12 17:38 ` transfer OS from failing HD questions James Miller
2006-07-12 18:21   ` Ray Olszewski
2006-08-10 19:07 ` smtp vs sendmail query James Miller
2006-08-10 19:55   ` Ray Olszewski [this message]

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=44DB8F42.8030604@comarre.com \
    --to=ray@comarre.com \
    --cc=linux-newbie@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.