From: Colin Rafferty <craffert@ml.com>
Subject: Re: *POP* goes the mail..
Date: 14 Aug 1997 18:30:00 -0400 [thread overview]
Message-ID: <ocrrabwjt3r.fsf@ml.com> (raw)
In-Reply-To: joda@pdc.kth.se's message of "14 Aug 1997 22:33:17 +0200"
Johan Danielsson writes:
> "Edward J. Sabol" <sabol@alderaan.gsfc.nasa.gov> writes:
>> FYI, the best POP solution I've seen is one that uses a program
>> called fetchmail to fetch the e-mail via POP and then feeds it via
>> SMTP to your localhost at port 25.
> Eh, if you want the mail delivered to your computer why don't you just
> have it forwarded there in the first place?
Getting way off topic here...
Here in the States, the typical setup is dynamic SLIP to our ISPs.
Since I am generally not connected, and the IP changes every time I do,
I cannot have mail delivered to my machine.
When I dial-up, I can run fetchmail from my machine to get the mail from
my POP mailbox on my ISP, and fetchmail than delivers each message to
the SMTP port on localhost (no matter what IP address it is).
This then puts everything in the correct mailbox, and even allows for
.forward and .procmail files to be processed correctly.
Of course, the original poster said that the problem is at work, so
delivering to the STMP port is probably not an option (since that would
just drop it right back in the POP-box).
--
Colin
next prev parent reply other threads:[~1997-08-14 22:30 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
1997-08-14 22:30 ` Colin Rafferty [this message]
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=ocrrabwjt3r.fsf@ml.com \
--to=craffert@ml.com \
/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).