From: Don Petrowski <dpetrowski@ci.collierville.tn.us>
To: Daniel Peter Cavanagh <nofsk@vtown.com.au>
Cc: linux-newbie@vger.kernel.org
Subject: Re: beep killing
Date: 11 Oct 2002 08:04:05 -0500 [thread overview]
Message-ID: <1034341446.11653.2.camel@workwatcher> (raw)
In-Reply-To: <3DA6C0D9.3040206@vtown.com.au>
[-- Attachment #1: Type: text/plain, Size: 165 bytes --]
On the email client you could configure fetchmail to pick up the POP3
accounts and deliver it to local user mbox and then pine or mutt to read
and send messages.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 240 bytes --]
next prev parent reply other threads:[~2002-10-11 13:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-11 12:15 beep killing Daniel Peter Cavanagh
2002-10-11 13:04 ` Don Petrowski [this message]
2002-10-13 0:21 ` lawson_whitney
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=1034341446.11653.2.camel@workwatcher \
--to=dpetrowski@ci.collierville.tn.us \
--cc=linux-newbie@vger.kernel.org \
--cc=nofsk@vtown.com.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.