public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: "Erik Heil" <eheil@eheil.dns2go.com>
To: <speakup@braille.uwo.ca>
Subject: Re: newsreaders
Date: Tue, 18 Mar 2003 19:14:30 -0500	[thread overview]
Message-ID: <000901c2edac$8412d620$0201a8c0@heilv1037a3gkh> (raw)
In-Reply-To: <Pine.LNX.4.44.0303181802550.236-100000@homerun.midsouth.rr.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hey Adam.  Doesn't Pine get that information via some kind of enviornment
variable?  Bc aht it probably assumes is /var/username/mail, or
/var/spool/username/mail.  Depends on how your distro is configured though.
- ----- Original Message -----
From: "Adam Myrow" <amyrow@midsouth.rr.com>
To: <speakup@braille.uwo.ca>
Sent: Tuesday, March 18, 2003 7:04 PM
Subject: Re: newsreaders


> Tin can do authentication.  I think trn4 and slrn can, but they have to be
> specially set up.  Pine assumes that your login name is the same as your
> login name on the server and I have no idea how to change it.  That's just
> as well, because Pine isn't much as a newsreader.
>
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
-----BEGIN PGP SIGNATURE-----
Version: PGP 8.0

iQA/AwUBPne2ZM6y+CHlb+ZeEQJ7IwCgj3Kjva5+EO45w2MJqUaaKjHmgJ0An2xv
Li7fhz4Q09Ki2FRvyZD+qjmO
=4OJ1
-----END PGP SIGNATURE-----




  reply	other threads:[~ UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 newsreaders Alex Snow
 ` newsreaders Erik Heil
   ` newsreaders Alex Snow
     ` newsreaders Adam Myrow
       ` Erik Heil [this message]
         ` newsreaders Adam Myrow
       ` newsreaders Alex Snow
         ` newsreaders Adam Myrow
           ` newsreaders Travis Siegel
             ` newsreaders Alex Snow
 ` newsreaders William F. Acker WB2FLW +1-303-722-7209
   ` newsreaders Alex Snow

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='000901c2edac$8412d620$0201a8c0@heilv1037a3gkh' \
    --to=eheil@eheil.dns2go.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).