Date: Fri, 06 Jun 1997 21:26:19 -0700 From: Scott Blachowicz <scott@plum.statsci.com> To: joelh@gnu.ai.mit.edu Cc: davidn@labs.usn.blaze.net.au, chat@FreeBSD.ORG Subject: Re: uucp uid's Message-ID: <m0waD51-0007QoC@plum.statsci.com> In-Reply-To: Your message of "Fri, 06 Jun 1997 19:13:52 -0400." <199706062313.TAA01198@ethanol.gnu.ai.mit.edu> References: <199706062313.TAA01198@ethanol.gnu.ai.mit.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
Joel Ray Holveck <joelh@gnu.ai.mit.edu> wrote:
> What's the point in augmenting SMTP for a SEND extension? Protocols
> have their purposes for a reason. SMTP is designed to send mail;
> leave it there. If you want to receive mail, you can design a
> different protocol, or use a protocol that's been designed and
> implemented already such as POP.
Depends on your viewpoint...I'm just trying to think of a way for a remote
system to tell an SMTP daemon that the coast is clear and available for it to
send the mail (rather than forcing it to have to endure network timeouts or
some such).
Also, POP is for an individual user, not system-to-system (as my email from
work to home is - my wife doesn't have an account on our work systems which
are effectively just acting as an MX forwarder for home).
> That way, other systems that need to send mail only don't need to mess
> around changing their protocol to meet the needs of extensions added for an
> entirely different purpose.
True...just trolling around for ideas...I'm just fine with using UUCP which
seems to be designed for my purposes and does the job just fine.
Scott Blachowicz Ph: 206/283-8802x240 Mathsoft (Data Analysis Products Div)
1700 Westlake Ave N #500
scott@statsci.com Seattle, WA USA 98109
Scott.Blachowicz@seaslug.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?m0waD51-0007QoC>