Article View: aus.computers.linux
Article #56105connecting intranet to the Internet
From: Tony Langdon
Date: Tue, 08 Apr 1997 00:00
Date: Tue, 08 Apr 1997 00:00
54 lines
2923 bytes
2923 bytes
It's 05 Apr 97 16:27, We'll return to grep@oriole.sbay.org and All's discussion of connecting intranet to the Internet gr> There are basicly three (or four) ways to do this. gr> a. Stay connected 24hours/day and set up your own gr> mail server. gr> gr> b. Have the DNS server for your domain or subdomain gr> hold an MX record to another host that IS connected gr> 24hours and have them hold the mail for you for pickup gr> by uucp. (a good idea) These two are the optimum alternatives. :-) gr> c. Have your ISP or another MX host put ALL email for gr> your domain in a single pop3 email box. You dial in, gr> pull all of the mail from that box and deliver it to gr> local boxes on a pop3 server on your local network I don't reccommend this, unless care is taken to preserve envelop information. Using procmail would be a must in this scenario. This discussion has been going on in other forums, and to date, only one unproven (and feasible) solution has been put forward (mailing lists and similar really confuse a POP based delivery system, becase the To: header doesn't contain the receipient;s address). Procmail at the ISP's end would be a prime contender to try and eliminate these problems (to preserve the envelope information). gr> d. (not a good idea) Have your ISP accept and queue gr> your mail in their SMTP queue. When you connect, you gr> force them to run their queue and you collect all of gr> your mail. Problems here is that it is a resource hit gr> on the ISP if several customers are doing this and you gr> never can be quite sure when the ISP is done sending mail gr> and you get no indication that the queue run is complete. IMHO, preferable to c. I run a system this way. If it's attended, the end of mail transmission can be determined by studying modem light activity, and you can work out a length of time that will guarantee all mail is delivered. For a full time system, a 24/7 SMTP link would be the best method. For a non-permanently connected system, UUCP is the best option. ... This tagline is confused - it thinks it's a message. -- | Fidonet: Tony Langdon 3:632/367.2 | Internet: tlang@freeway.DIALix.oz.au | | Freeway Internet Gateway, Melbourne, Australia. For information about | our services and conditions of use, e-mail: | info@freeway.DIALix.oz.au, to receive a copy of the FAQ.
Technical Details
Message-ID:
<413_9704090728@freeway.DIALix.oz.au>Path:
arc1-ca.pugleaf.net!unknown!not-for-mailReferences:
<334465e4.4808263@news.wr.com.au> <E85J9M.6LD@oriole.sbay.org>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 102983,cf9d4a1a359f0887 X-Google-Attributes: gid102983,public From: tlang@freeway.DIALix.oz.au (Tony Langdon) Subject: connecting intranet to the Internet Date: 1997/04/08 Message-ID: <413_9704090728@freeway.DIALix.oz.au> X-Deja-AN: 231639537 References: <334465e4.4808263@news.wr.com.au> <E85J9M.6LD@oriole.sbay.org> Organization: Fidonet: Freeway Usenet <=> FTN gateway Newsgroups: aus.computers.linux X-FTN-To: grep@oriole.sbay.org