On 02/02/2015 23:08, Nick Maclaren wrote:
In article ,
polygonum wrote:
On 02/02/2015 14:47, PeterC wrote:

it's 25MB (+overheads) so e-mailable(?).

Why would anyone send anything that big by email?

a) Because they don't know of another method

b) Because that's normal, at least for Powerpoint presentations
by marketing departments

Way back when, when wide-area Email was starting (well before the
Internet), I had an argument with our Email people about sending
files via Email. They said that you should never do that, because
Email was like letters, so I said "What about parcel post?" I lost,
and Email didn't support sending files until many years later.

Of course, everyone With Clue knew how to encode files as plain
text (hence uuencode etc.), but it took ages before attachments
appeared. And now people send messages as attachments, so you
can't read them without the right application, and are opening
yourself up to an attack if you do ....

How technology has, er, progressed!


Regards,
Nick Maclaren.


My 2c

Corporate email systems (tend to) revolve around Exchange.
In Exchange, all emails and attachments get merged into one big database
file for access by the Outlook clients.
Databases are great for handling and searching through lots of small
packets of data. They don't fair so well when large files are included.
In database design, images and the like should be included as links in a
database record, rather than including the file itself.
The same approach holds true for Exchange/Outlook and can clearly be
seen by the (slow) speed of search when looking for a message in a
folder which contains many messages with large attachments.

In addition, there are storage and backup considerations..
The user receives an email with a large attachment and saves said file
out to a folder full of similar files. You now need twice the storage
and twice the backup capacity.

Large files should be uploaded to cloud storage and a download link only
distributed.


Phil