System Administrator wrote:
> I was not aware my suggestion might break usages of MIME encoded
> content for purposes other than message attachments. Perhaps these
> other usages could be identified differently than attachments and the
> "filter" that I'm suggesting act only on attachment encoded content.
>
> Alas! Not all of us are fourtunate enough to live in an area served
> by affordable high speed Internet service. I presently have a T1 at
> my home location which costs my landlord $470 per month. He has
> decided to drop the service due to the cost. DSL and cable TV service
> are not available at my address. From pervious experience with
> satellite Internet, its reliability is not all that great and
> obtaining requires committing to a 2-year contract. So, I will be
> relegated to having to use a dial-up service which only achieves
> 25Kbps.
>
> On Thu, 18 Feb 2010 06:38:11 -0500, Carmel <(E-Mail Removed)>
> wrote:
>
>>On Wed, 17 Feb 2010 22:26:08 -0800
>>System Administrator <(E-Mail Removed)>
>>articulated:
>>
>>> Thanks, to both respondents. I was aware of the download headers only
>>> facility and the ability to set a message size limit for download. I
>>> was also aware of attachments being MIME encoded and contained in the
>>> message body. I was hoping that there was a way to exclude the MIME
>>> content of the message body from the downloading since that section of
>>> the body is clearly coded as being MIME encoded content and, I
>>> believe, follows all other message content in the body.
>>>
>>> Oh, well! So much for that idea. Thanks for your responses.
>>>
>>> Seems to me that would be a nice addition to the POP3 protocol
>>> structure.
>>
>>I sincerely hope that no moron takes your suggestion seriously. An
>>implementation of that sort would surely break GPG signatures, not to
>>mention DKIM, etc.
>>
>>A more favorable solution would be for you to obtain a different
>>Internet connection.
>>
>>--
>>Carmel |::::=======
>> |::::=======
>> |===========
>> |===========
>> |
>>
Technical solutions cannot compensate for user stupidity. You know the real
problem, and that is your senders are the morons for trying to use e-mail as
a file transfer mechanism for which is was not designed. The solution is
telling your senders to stop being rude by sending oversized e-mails. As I
stated before, have them store their files in online storage and provide a
*link* to it in their message.
When you get a memo from your secretary about a missed call, do you expect
to get an encyclopedia-sized memo? No, you expect to get a short note with
some critical information.
Below is my typical canned response to some boob that wants to use e-mail
for file transfers.
----------
E-mail is NOT a reliable file transfer mechanism. It wasn't intended or
designed for that. It was designed to send lots of small messages. There
is no CRC check on the file to ensure integrity. There is no resume to
re-retrieve the file if the e-mail download fails. There is no guarantee
the e-mail will arrive uncorrupted. Large e-mails can generate timeouts and
retries due to the delay when anti-virus programs interrogate their content.
Do not use e-mail to send large files. It is rude to the recipient. Not
every recipient might want your large file. Not every recipient has
high-speed broadband Internet access. Many users still use slow dial-up
access, especially if all they do is e-mail. You waste your e-mail
provider's disk space and their bandwidth to send a huge e-mail. You waste
the e-mail provider's disk space and bandwidth at the recipient's end. You
eat up the disk quota for the recipient's mailbox (which could render it
unusable so further e-mails get rejected due to a full mailbox). You
irritate users still on dial-up that have to wait eons waiting to download
your huge e-mail. Some users have usage quotas (i.e., so many bytes/month)
and you waste it with a file that they may not want. Don't be insensitive
to recipients of your e-mails. Take the large file out of the e-mail.
Save the file in online storage and send the recipient a URL link to the
file. Your e-mail remains small. It is more likely to arrive. It is more
likely to be seen. The recipient can decide whether or not and when to
download your large file. Be polite by sending small e-mails.
Your ISP probably allows many gigabytes of online storage for personal web
pages. Upload your file there and provide a URL link to it. Other methods
(of using online storage), all free, are:
http://www.adrive.com/ (50GB max quota, 2GB max file size)
http://www.driveway.com/ (500MB max file size)
http://www.filefactory.com/ (300MB max file size)
http://www.megashares.com/ (10GB max file size)
http://www.sendspace.com/ (300MB max file size)
http://www.spread-it.com/ (500MB max file size)
http://www.transferbigfiles.com/ (1GB max file size)
http://zshare.net/ (500MB max file size)
http://www.zupload.com/ (500MB max file size)
If it is sensitive content and when storing it online in a public storage
area or to guard it against whomever operates the online storage service,
remember to encrypt it.