Re: EMAIL != FTP

[John Fraizer <nanog () Overkill EnterZone Net>]

On Fri, 25 May 2001, Mitch Halmu wrote:

> > http://www.mhsc.com/~rmeyer/Document-I-Promised.zip
> >
> > ftp://ftp.mhsc.com/pub/users/rmeyer/Document-I-Promised.zip
> > "
> >
> >
> > Very simple concept.  It not only uses the right tool for the job but,
> > also affords them the opportunity to retrieve the document when it is
> > CONVENIENT for them.  If I were a dialup user and somone sent me some HUGE
> > attachment like that, I would consider it very rude.
> >
> > Note to all salesdroids:  If you want to be sure that I will NEVER do
> > business with you, send me an email attachment.
> >
> >
> > ---
> > John Fraizer
> > EnterZone, Inc
>
> If you were a dial-up user, chances are you wouldn't be able to do that.

REALLY? Lets check this out.

> A few simple reasons come to mind: first, you wouldn't have any or not
> enough disk space on your system account (limited by quota) to store the
> file.

Have you thought about that before sending a large file via email to
someone?  Many provides include your email spool in your quota.  Beyond
that, there are TONS of free hosting providers out there so your arguement
there is moot.

> Second, an average user probably wouldn't have the skill.

Huh?  You're joking, right?  Believe it or not Mitch, the rest of the
internet population isn't just sitting around sucking up oxygen from
brain-children like you.  If they're competent enough to create a large
presentation, they're competent enough to upload it somewhere.  They can
drag and drop with any number of FTP applications.  Moot arguement.


> Third, a .zip file will usually display as funny characters on a web
> browser - that's why ftp is needed. 

Only if they're running REALLY, REALLY old browsers or the server itself
is sending an incorrect mime-type for the .zip extension.  Beyond that,
they can right-click on the link and do a "save-as" so, this one is moot
as well.

> Fourth, you probably wouldn't have shell access and ftp space from
> your provider with a regular account.

Please see "free hosting providers" above.  MOOT.


> Fifth, assuming you would have all the toys, you would have to spend
> yourself the time to first upload the file, so that another may
> retrieve it. 

OK.  How is that any different that the time it takes you to send the file
to the SMTP server?  MOOT!


> Sixth, if your file was a sensitive document, others
> would have public access to it, etc.

Ever hear of .htaccess?  It's REALLY neat.  If you think your file is safe
from prying eyes in email, you've got more problems than not understanding
basic authentication on a webserver though.  You should stop argueing your
invalid, moot points and spend that precious time reevaluating your
security policy.

> So what's a regular user to do? Email it!

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.

> Hence the legitimate use of email for transmission of large files.

Please don't breed.


> Most ISPs know that if they start limiting this privilege, users will
> migrate to someone that allows it.

If you educate your users, you have no problems.


---
John Fraizer
EnterZone, Inc