the easiest way to send email is to setup exim to use a smarthost and then point that to your isp's smtp server then you can just use the mail command and just point mutt to use local host which it may all ready be doing if if you setup a mail server on the install. a good way to config this from the command line is to use dpkg-reconfigure exim4 as root

also to find a path of a command just use the whereis then the command your looking for like whereis esmtp

Try MUTT

Thanks for the whereis command info -- I need "Linux in a Nutshell" opened up on my desk when I do this stuff.

I think it would be worth your time to look at using Pine as your email client. I'd advise against setting up a mail server, fetchmail and other utilities just to run an IMAP client. Pine is simple to setup and use. Mutt is great, but not simple.

I just went through the thrilling ordeal of setting up mutt myself. "Ordeal" because it was - it took me a couple of days - but "thrilling" because I now know a whole lot more about mail handling than I used to.
Initially, I intended to use the IMAP options within mutt, but I ended up using the longer chain through getmail (to fetch mail from the server with a cron-job); and procmail for the filtering to the spool directory (which I set to be my regular inbox).
Apart from that, my setup includes mairix for searching in all mailboxes, urlview for extracting urls, vim for composing mail, muttprint for - uh - printing (in full LaTeX glory - wonderful!), and abook for the address book; further: antiword and pdftotext for viewing attachments inline (great!).
It was a hassle, but I now have a system which (a) I can configure precisely to my liking, and (b) I understand each single element of.
I use the maildir format, and I've set up kmail to use the same folders, so that I can view the same mails there, should I need some of the functionality of a GUI.
I'd be happy to send you my config files if you want to. It was a hassle to set it up, but once it's in place, I can't imagine using another email reader. I can really recommend mutt.

I've spent days trying to get mutt/esmtp and pine to do IMAP mail from both Fastmail.fm and DSL Extreme. I've been able to receive mail, no problem, but the whole thing falls apart when I try to SEND mail. I just can't seem to get the SMTP servers to do my bidding.

I've tried the few configuration file hints I've seen on the Web, but I've just hit a wall. Maybe POP mail will be better, but I was really hoping to do IMAP.

Even though this is "A Month on the Command Line," I booted into Xubuntu today to see how easy it was to use Thunderbird. Pretty easy -- I got both IMAP accounts to work (and with different SMTP servers for each).

Getting back to the command line, I've seen some VERY detailed config files for mutt and pine, and I wonder where in the hell people come up with this stuff.

And regarding Thunderbird, it's pretty much like Netscape Communicator's e-mail/news reader. It drove me to install the Pan newsreader (I don't read all that much USENET news, but I figured I'd try it), and that was much better -- and snappier.

But going from mutt to Thunderbird, from Elinks to Firefox, I really miss the speed of the command line, so I will live to fight another day at the console ...

Regarding pine, with copious instructions, I put together my own .deb package and installed it ... and when I couldn't get outgoing mail to work, I hastily removed and deleted the whole thing. ... That's what impatience will get you.

Again, I love the speed of the command line -- it's great for e-mail, where you can really zip right through it.

Right now I just have to regroup and rethink how I'm going about this.

I use Fetchmail, Mutt, Procmail and Postfix to handle my mail, and have also
changed my mind several times over the last few years over which anti-spam
tool to use.

Here's a brief summary of how it works:

• Fetchmail retrieves incoming messages from my accounts on IMAP servers, and delivers them via SMTP (port 25) to Postfix. Fetchmail configuration involves creating a ~/.fetchmailrc file.
• Postfix queues the messages and invokes Procmail to deliver them .
  mailbox_command = procmail -a "$EXTENSION" in /etc/postfix/main.cf
• If there is a ~/.procmailrc file, Procmail applies the rules in it to filter the incoming messages into various folders. This implies that you don't need a ~/.procmailrc file for this setup to work, but by having one you can filter out spam and duplicate messages, filter various mailing lists into different folders, etc.
• Mutt accesses the local mail folders (/var/mail/username as the primary inbox, and folders under ~/mail) to read the mail. Of course, mail is delivered and filtered entirely in the background.
• For outgoing messages, you can configure Postfix with the relayhost command, as in relayhost=mail.isp.domain to deliver outbound e-mail via your ISP's SMTP server. Alternatively, you can just let Postfix deliver mail to the destination directly, without any additional configuration required. Some spam filtering services may filter out your messages if you do this. In my case, I can't tell the difference between the two alternatives, so I just let Postfix handle outgoing messages itself (without relaying via my ISP).

The point to emphasize here is that all of this isn't too difficult to set up (a certain investment in reading manual pages and setting up configuration files is needed, especially for Procmail and to a lesser extent Fetchmail), but once set up, it works really well - year after year - with only incremental improvements. That's why some of us are so addicted to this way of working. I can't remember how long it took to set up the first time, but given how well it has worked ever since, it was well worth it.

Thanks for all the suggestions, everybody. I thought that I could get by with just mutt and esmtp, but it looks like it'll take more than than.

This is not at all something I'm going to give up on -- but I would love to find a book, Web site or some other reference that covers the topic of e-mail in Linux in detail, with lots of examples and sample configuration files.

Curiously, most of the "votes" so far have been for mutt and its various helper apps, and fewer for pine.

As far as editors go, I'm already getting better with vi, though I'm growing to like nano.

And ... Midnight Commander makes things so easy, I almost feel like I'm cheating.

The one thing that is inspiring yet maddening about this is that by virtue of all the choices out there in both applications and configuration, you really can have a custom-tailored system that serves your needs.

And the other thing I'm learning from using the command line is that these apps, which work so quickly and on computers many, many years old, are still being improved and updated. It's very inspiring to someone who loves old hardware.