🚀 go-pugleaf

In article <1992Dec31.034803.15192@acme.gen.nz>, kilroy@acme.gen.nz (earthbound misfit, I) writes:
|> don@zl2tnm.gen.nz (Don Stokes) writes:
|> 
|> > [...dialup IP...]
|> >
|> > Other gotchas include the issue of what to do with mail -- the nature of
|> > SMTP is that it expects that a host is going to be there all the time, and
|> > if it isn't, it'll come back Real Soon Now.  That assumption is going to
|> > be false with a dialup SLIP or PPP connection, so alternative arrangements
|> > need to be made.  Those arrangements are probably going to cost money.
|> 
|> You could use POP, which appears to be receiving enthusiastic support (if
|> the whizzy client I'm using on a PC at work is an indication). The problem
|> it does cause of course is that your server then has to provide spool space
|> for my mail until I bother to call and grab it.

Of course, the sendmail daemon that was acting as a secondary MX for the
SLIP/PPP connected site would be doing that anyway! It's an easily solvable
problem. The downstream site talks to an "I'm here again, please run the
sendmail queue while I'm connected" server.

I don't think POP is the answer in this case unless there is only a limited
number of recipients at the downstream site.