Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!att!linac!pacific.mps.ohio-state.edu!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!ra!emory!hubcap!ncrcae!ncr-sd!simasd!jadpc!jdeitch From: jdeitch@jadpc.cts.com (Jim Deitch) Newsgroups: comp.protocols.tcp-ip Subject: Re: Cost of Internet access Message-ID: <1990Nov10.154401.274@jadpc.cts.com> Date: 10 Nov 90 15:44:01 GMT References: <9011061147.AA20765@ucbvax.Berkeley.EDU> Organization: Network Engineering Technologies Lines: 30 In article peter@ficc.ferranti.com (Peter da Silva) writes: >In article <9011061147.AA20765@ucbvax.Berkeley.EDU> jcurran@SH.CS.NET writes: >> Dialup IP services are quite inexpensive, and if set up with care will >> give all the advantages of a dedicated circuit only with an occasional >> 30 second delay (those times when the line must be brought up.) > >Um, won't this cause problems with SMTP? What does SMTP do when the >destination is only available for brief periods, or should you handle >your mail via an MX? >-- >Peter da Silva. `-_-' >+1 713 274 5180. 'U` >peter@ferranti.com Not at all. SMTP will just hold the message on queue until either sendmail or whatever you are using to smtp with wakes up and tries again to send it. If it can't connect within about 3 days or so then it is returned to the sender. This is the way it works for both directions. Once you have the link up you can invoke sendmail -q to run the queue and deliver what it can. Jim -- UUCP: nosc!jadpc!jdeitch ARPA: jadpc!jdeitch@nosc.mil INET: jdeitch@jadpc.cts.com