From: wmperry@aventail.com (William M. Perry)
Cc: "Edward J. Sabol" <sabol@alderaan.gsfc.nasa.gov>,
Gnus Mailing List <ding@gnus.org>
Subject: Re: *POP* goes the mail..
Date: 14 Aug 1997 21:13:32 -0700 [thread overview]
Message-ID: <86lo24hymr.fsf@wmperry.oz.net> (raw)
In-Reply-To: joda@pdc.kth.se's message of "15 Aug 1997 02:14:46 +0200"
joda@pdc.kth.se (Johan Danielsson) writes:
> wmperry@aventail.com (William M. Perry) writes:
>
> > 1) You don't have a static IP address
> > 2) Your machine isn't up all the time
> > 3) Your machine is not directly connected to the public network
>
> But why go through the extra step of putting it in local spool file?
Unknown... perhaps so procmail and friends will work.
-Bill P.
next prev parent reply other threads:[~1997-08-15 4:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-08-14 8:02 Andy Eskilsson
1997-08-14 10:01 ` Steinar Bang
1997-08-14 14:55 ` Michael Welsh Duggan
1997-08-14 22:12 ` Karl Kleinpaste
1997-08-14 15:27 ` Jason R Mastaler
1997-08-14 19:03 ` Edward J. Sabol
1997-08-14 20:33 ` Johan Danielsson
1997-08-14 21:54 ` William M. Perry
1997-08-15 0:14 ` Johan Danielsson
1997-08-15 4:13 ` William M. Perry [this message]
1997-08-14 22:30 ` Colin Rafferty
1997-08-14 12:09 ` Johan Danielsson
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=86lo24hymr.fsf@wmperry.oz.net \
--to=wmperry@aventail.com \
--cc=ding@gnus.org \
--cc=sabol@alderaan.gsfc.nasa.gov \
/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 NNTP newsgroup(s).