From: Tommy Moore <tmoore@cmrc.org>
To: speakup@braille.uwo.ca
Subject: Mutt help.
Date: Thu, 4 Oct 2001 20:23:48 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.40.0110042019310.8369-100000@athena> (raw)
Hi guys. Am wanting to switch from pine to mutt as my mailer and I have a
few questions.
How do I define a different address that mails are comming from that's
different from the system hostname?
Right now what I have is a different account for each address I send from
on this machine.
tmoore@cmrc.org and stp@flite.net.
I don't mind using different accounts for the two mails because this helps
me keep everything in different accounts for the mail.
What happens when I send mail from the stp account is it tries to send it
from stp@athena instead of stp@flite.net.
When I used pine I could just set the return address to stp@flite.net and
everything worked. I'm wanting to start using gpg for sendming mail to
some users and from what I've seen mutt works quite well with it.
Also is there any way to convert my pine mail folders over to the format
used for mutt?
And lastly how do I do converting of the address book?
Thanks guys.
Tommy
reply other threads:[~ UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=Pine.LNX.4.40.0110042019310.8369-100000@athena \
--to=tmoore@cmrc.org \
--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).