<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2653.12">
<TITLE>RE: [JDEV] File transfers</TITLE>
</HEAD>
<BODY>
<P><FONT SIZE=2>Mike angrily flames:</FONT>
<BR><FONT SIZE=2>> How's that? POP AND IMAP are protocols for Clients to talk to</FONT>
<BR><FONT SIZE=2>> Servers to access stores of messages and attachments. A Pop or</FONT>
<BR><FONT SIZE=2>> IMAP Client DOES NOT talk to another Pop or IMAP Client...EVER...</FONT>
<BR><FONT SIZE=2>> SMTP is the way you SEND messages to those stores and every single</FONT>
<BR><FONT SIZE=2>> email message you send is transferred using SMTP and BTW SendMail</FONT>
<BR><FONT SIZE=2>> is just an SMTP Program for sending mail, it has nothing to do</FONT>
<BR><FONT SIZE=2>> with "bulk".</FONT>
</P>
<P><FONT SIZE=2>Oh dear, I appear to have killed your cat or something with my</FONT>
<BR><FONT SIZE=2>message. I apologize.</FONT>
</P>
<P><FONT SIZE=2>The distinction I was making -- apparently not well enough for you</FONT>
<BR><FONT SIZE=2>to understand -- was that in SMTP, there is usually minimal conversation;</FONT>
<BR><FONT SIZE=2>the conversation is, in 99% of cases, the same between the two partners,</FONT>
<BR><FONT SIZE=2>and the task is a batch-like, bulk task usually involving one transaction.</FONT>
</P>
<P><FONT SIZE=2>By comparison, POP/IMAP are chatty, and they tend to stay connected for multiple</FONT>
<BR><FONT SIZE=2>discrete 'transactions'. This is more 'peer'-like behavior, a la Jabber, etc.</FONT>
<BR><FONT SIZE=2>There isn't a hard-and-fast definition of what a server is and what a client is</FONT>
<BR><FONT SIZE=2>any more; more and more we're talking shades of grey. Certainly it's nothing to</FONT>
<BR><FONT SIZE=2>get screamy about.</FONT>
</P>
<P><FONT SIZE=2>> Have you ever setup an email client? </FONT>
</P>
<P><FONT SIZE=2>I think so. Over the course of my 17 year career as a Unix hacker, I've</FONT>
<BR><FONT SIZE=2>also written about 20 sendmail.cf files, most from scratch (starting with</FONT>
<BR><FONT SIZE=2>a UUCP feed), as well as written about a million lines of Perl, including</FONT>
<BR><FONT SIZE=2>the first opcode-based safe remote execution protocol in any language</FONT>
<BR><FONT SIZE=2>anywhere. Somewhere in there may have been a few e-mail clients on desktops.</FONT>
</P>
<P><FONT SIZE=2>> If you did you had to setup the email server for getting your email</FONT>
<BR><FONT SIZE=2>> and choose POP3 or IMAP4 and then an SMTP server for outgoing,</FONT>
</P>
<P><FONT SIZE=2>Well, maybe on Windows. I distinctly remember not having to do that</FONT>
<BR><FONT SIZE=2>on Xenix, SCO Unix, Unixware, Irix, HP/UX, Domain/OS, RSTS/E, VMS,</FONT>
<BR><FONT SIZE=2>Digital Unix, Linux .96c, QNX, VxWorks, *BSD, BSDI, Netware, or</FONT>
<BR><FONT SIZE=2>PalmOS. For that matter, I didn't have to do that on Windows, either.</FONT>
</P>
<P><FONT SIZE=2>> or</FONT>
<BR><FONT SIZE=2>> if you leave that blank it tries to use the same server you setup</FONT>
<BR><FONT SIZE=2>> for incoming.</FONT>
</P>
<P><FONT SIZE=2>Not all the world is Outlook Express.</FONT>
</P>
<P><FONT SIZE=2>> If YOU want to add value, don't spout about things you obviously know</FONT>
<BR><FONT SIZE=2>> NOTHING about. Read the specifications about POP3, IMAP4 AND SMTP and</FONT>
<BR><FONT SIZE=2>> you can find those at <A HREF="http://www.ietf.org" TARGET="_blank">http://www.ietf.org</A></FONT>
</P>
<P><FONT SIZE=2>Thanks for the pointer. So what exactly is Netscape's MTA again?</FONT>
</P>
<P><FONT SIZE=2>> I completely agree it depends on where you are standing and you are standing in the dark. </FONT>
</P>
<P><FONT SIZE=2>It happens to the best of us. Good luck with AppsAsPeers.com; if you need</FONT>
<BR><FONT SIZE=2>any pointers, I have some work I did in 1996 which could be relevant.</FONT>
</P>
<P><FONT SIZE=2>F.</FONT>
</P>
<CODE><FONT SIZE=3><BR>
<BR>
**********************************************************************<BR>
E-mail sent through the Internet is not secure. Western Asset therefore<BR>
recommends that you do not send any confidential or sensitive information to<BR>
us via electronic mail, including social security numbers, account numbers,<BR>
or personal identification numbers. Delivery, and or timely delivery of<BR>
Internet mail is not guaranteed. Western Asset therefore recommends that<BR>
you do not send time sensitive or action-oriented messages to us via<BR>
electronic mail.<BR>
**********************************************************************<BR>
</FONT></CODE>
</BODY>
</HTML>