From: "Victor Tsaran" <vtsaran@nimbus.ocis.temple.edu>
To: <speakup@braille.uwo.ca>
Subject: Re: Standalone E-Mail
Date: Sun, 25 Jun 2000 13:00:05 -0700 [thread overview]
Message-ID: <002201bfdedf$f898cce0$92125b80@wang> (raw)
In-Reply-To: <Pine.LNX.4.21.0006251142020.999-100000@adsl-151-200-20-29.bellatlantic.net>
Hi, Janina!
I just wrote the same advice to Brad on another list. What a coincidence!
Regards,
Vic
----- Original Message -----
From: "Janina Sajka" <janina@afb.net>
To: <speakup@braille.uwo.ca>
Sent: Sunday, June 25, 2000 8:48 AM
Subject: Standalone E-Mail
> Hi, Brett:
>
> I just wanted to drop you note about how I handle mail on my notebook
> computer. Needless to say, it's off-line a lot. First, it's not my main
> machine when I'm in the office, and it's off-line a lot when I travel
> because I'm on a plane, or something. Becides, in places like Europe, it's
> far too expensive to just leave it up online from one's hotel room.
>
> So, here's what I do. I hope it helps you:
>
> 1.) I use fetchmail to get all of my incoming mail from my isp after
> establishing a ppp connection;
>
> 2.) Since I use sendmail as my mailor, I then issue the command --
>
> sendmail -q0
>
> that's send mail dash q zero
>
> to dump the messages that have been qued for transmittal.
>
> This works because sendmail is not loaded as a daemon on my system. It's
> only active when I issue the command above, or another specific sendmail
> command.
>
> This way, I can write all the messages I want in Pine without trouble,
> whether or not I'm writing on the airplane, or at my desk in my room, and
> whether or not I'm online when I write them. They're simply qued for later
> transmittal, which is accomplished by the sendmail -q0 command once I'm
> online.
>
> PS: I've also set the smtp address in my Pine configuration to my isp.
>
>
>
> --
>
> Janina Sajka, Director
> Information Systems Research & Development
> American Foundation for the Blind (AFB)
>
> janina@afb.net
>
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
Janina Sajka
` Victor Tsaran [this message]
` Janina Sajka
` Victor Tsaran
` Janina Sajka
` brent harding
[not found] ` <Pine.LNX.4.21.0006251851050.11743-100000@adsl-151-200-20-2 9.bellatlantic.net>
` brent harding
` Janina Sajka
[not found] ` <Pine.LNX.4.21.0006251908110.11743-100000@adsl-151-200-20-2 9.bellatlantic.net>
` brent harding
[not found] <Pine.LNX.4.21.0006251142020.999-100000@adsl-151-200-20-29. bellatlantic.net>
` brent harding
` Charles Hallenbeck
` Janina Sajka
[not found] ` <Pine.LNX.4.21.0006251734310.999-100000@adsl-151-200-20-29. bellatlantic.net>
` brent harding
` Janina Sajka
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='002201bfdedf$f898cce0$92125b80@wang' \
--to=vtsaran@nimbus.ocis.temple.edu \
--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).