[37888] in North American Network Operators' Group
Re: EMAIL != FTP
daemon@ATHENA.MIT.EDU (Shawn McMahon)
Fri May 25 11:12:58 2001
Date: Fri, 25 May 2001 11:08:37 -0400
From: Shawn McMahon <smcmahon@eiv.com>
To: nanog@merit.edu
Message-ID: <20010525110837.B17149@eiv.com>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-md5;
protocol="application/pgp-signature"; boundary="RASg3xLB4tUQ4RcS"
Content-Disposition: inline
In-Reply-To: <Pine.LNX.4.21.0105250944110.6184-100000@Overkill.EnterZone.Net>; from nanog@Overkill.EnterZone.Net on Fri, May 25, 2001 at 10:01:52AM -0400
Errors-To: owner-nanog-outgoing@merit.edu
--RASg3xLB4tUQ4RcS
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Fri, May 25, 2001 at 10:01:52AM -0400, John Fraizer wrote:
>=20
> Have you thought about that before sending a large file via email to
> someone?
John, you seem to be assuming that the transfer of files via email is
done on a whim to randomly-selected individuals around the net.
While that may be the case for a large number of people, nobody involved
in this discussion is that clueless. Hint: they'd probably have an aol.com
or msn.com email address, and no clue what NANOG is.
> OK. How is that any different that the time it takes you to send the file
> to the SMTP server? MOOT!
John, here's the steps involved in sending the file to the SMTP server:
Click "attach".
Select the appropriate directory.
Click on the file.
Or are you assuming that the folks in this discussion don't have LANs, and
are using uuencode and piping through /bin/mail? I think your information
is about 15 years out of date.
> No. That's what the uneducated newbie does. The regular user uploads it
> to their http/ftp server and sends a link to the file via email.
And yet, I continue to exchange files with other system administrators
of Fortune 500 companies. Guess we're all "uneducated newbies".
> Please don't breed.
When you reach the point where every paragraph contains an ad-hominem,
we can only conclude you don't have a technical argument, and are instead
engaged in knee-jerk reaction.
> If you educate your users, you have no problems.
"Don't use this feature that SMTP was specifically designed to allow, and
that sendmail is default configured to facilitate. Instead, jump through
a bunch of extra hoops, so that John Frazier will not call you a clueless
newbie. Trust me, you'll be happier. <click> Hello? Hello?"
--RASg3xLB4tUQ4RcS
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.4 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iEYEARECAAYFAjsOdXUACgkQEcl9bQ0RMt0c5QCg6p53q5B1oh2LeGYqLQVCNEPO
aD8An2CYmcw/WgYeVDX1HXNBS0/sBJTh
=BUP3
-----END PGP SIGNATURE-----
--RASg3xLB4tUQ4RcS--
