From: "Thomas Ward" <tward@bright.net>
To: <speakup@braille.uwo.ca>
Subject: Re: Popping mail or fetchmail
Date: Mon, 4 Feb 2002 12:08:57 -0500 [thread overview]
Message-ID: <003501c1ad9e$a506aa40$0100a8c0@tward> (raw)
In-Reply-To: <Pine.LNX.4.44.0202040455360.197-100000@rocky.nycap.rr.com>
As I understand it when you move the inbox path to the pop server you are
viewing the mail on the server, nd not on your local machine.
fetchmail actually moves the mail from the server to the local machine.
----- Original Message -----
From: Dan Murphy <mweeby@nycap.rr.com>
To: Speakup mailing list <speakup@braille.uwo.ca>
Sent: Monday, February 04, 2002 4:58 AM
Subject: Popping mail or fetchmail
> Hi all.
> I recently tried the thing where I changed the in box path in Pine to
> reflect my ISP's pop server, and it works great, but what are the pros and
> cons regarding this technique over using fetchmail, which I've also used
> quite successfully?
> Thanks.
>
>
> Dan Murphy
> mailto:mweeby@nycap.rr.com
> http://home.nycap.rr.com/mweeby
> Let us not look back in anger or forward
> in fear, but around us in awareness.
> -- James Thurber
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
prev parent reply other threads:[~ UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
Dan Murphy
` Thomas Ward [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='003501c1ad9e$a506aa40$0100a8c0@tward' \
--to=tward@bright.net \
--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).