From: "Joe Clever" <lists@clevercentral.com>
To: <speakup@braille.uwo.ca>
Subject: RE: Can get but can't send mail from my Red Hat 9
Date: Sun, 26 Oct 2003 12:26:56 -0500 [thread overview]
Message-ID: <000401c39be6$5e4b91a0$6701a8c0@private.network> (raw)
In-Reply-To: <18817405937.20031026155102@bredband.net>
Krister,
If you have both sendmail and postfix installed on your system, there is a
tool in Redhat 9 to switch between them. Run the command
"redhat-switch-mail" and then select postfix, if that is what you want.
My suggestion is that you run the pine mail program to see if you can
communicate with your ISP's MTA, before trying to configure postfix with
mutt or postfix with pine. I think that pine works pretty much right out of
the box with the exceptions of the same things you would have to configure
with any MUA. Within pine there is a setup|configure menu, so no need to
muck with a config file, directly. I prefer to break things down into small
steps, before tackling something more complex, i.e. MUA to ISP, before MUA
to your MTA to ISP's MTA.
I have not used mutt, but someone pointed out in another thread that mutt
may not be capable of sending mail directly to your ISP. One of these days I
will setup mutt because I want threaded mail.
A caveat, make sure that you do not have firewall rules blocking any of the
services that you wish to run. On installation of Redhat 9, you were asked
what kind of security/firewall rules you wanted to run with.
On a personal note, I have been struggling with Linux for several years. At
times, it is frustrating because of the lack of, or the overabundance of
often poor documentation. At times, I wonder if it is worth the effort. At
times, I have had to walk away from it for awhile. As former president
Clinton used to say, "I feel your pain". I really do.
-----Original Message-----
From: speakup-admin@braille.uwo.ca [mailto:speakup-admin@braille.uwo.ca] On
Behalf Of Krister Ekstrom
Sent: Sunday, October 26, 2003 9:51 AM
To: Geoff Shang
Subject: Re: Can get but can't send mail from my Red Hat 9
-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160
Hi Geoff,
On 27 Oct 2003 00:40:57 (my local time 26 okt 2003 15:40:57), you
typed::
GS> Exactly how you do this will depend on which mail server you are running
GS> (for the first method) or which mail program you use (for the
second).
Ok, it looks as if Sendmail is started by default, but i'm planning on
using Postfix, since this should be easier to set up, or so i'm told,
and for mailer i will be using Mutt.
Does this make any sence?
- --
/Krister
crisekstrom@bredband.net
Get pgp keys here: mailto:crisekstrom@bredband.net?subject=get_pgp_keys
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2-nr2 (Windows XP)
iD8DBQE/m99fODlJeoMTOQsRA2SUAKDKu+SQO+FM+uakZbRpoy9mdPk7KwCdHq8r
k1Lbo8STda4Gc0rLUyOqixs=
=Isbb
-----END PGP SIGNATURE-----
_______________________________________________
Speakup mailing list
Speakup@braille.uwo.ca
http://speech.braille.uwo.ca/mailman/listinfo/speakup
prev parent reply other threads:[~ UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
Krister Ekstrom
` Geoff Shang
` Krister Ekstrom
` Joe Clever [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='000401c39be6$5e4b91a0$6701a8c0@private.network' \
--to=lists@clevercentral.com \
--cc=speakup@braille.uwo.ca \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).