General discussion


Email attachments What's your opinion

By rgun2515 ·
What's the Largest attachment you would include in an email. What limits does your company or your ISP enforce? What are the technical reasons for limiting the size of an email attachment?What do you feel is proper etiquette?

This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Comments

Collapse -

Depends on your equipment and people

by James Schroer In reply to Email attachments What's ...

We use to not have a send and recieving limit. But because of our exchange server growing out of room we are now enforcing a 10 mb limit on send and recieve.

Collapse -

at home

by DC_GUY In reply to Email attachments What's ...

At home I have a dial-up connection, so it bothers me when people send me large attachments which almost invariably turn out to be stuff I didn't want in the first place. It ties up my computer for half an hour and I can't find any way to direct my e-mail software or my ISP to skip that one and trash it.

At the office I'm not sure we have a limit for internal e-mails, but most people try to keep it under 10 mB. There's a limit for mail from outside, but I don't know what it is since I only seem to get that kind of stuff at home.

There's not much "etiquette" in the virtual world. I'd suggest telling people if you have dial-up and asking them to keep you off their forwarding lists. Otherwise, what's the harm in the occasional giant attachment?

Collapse -

We have a 10 mb quota

by house In reply to Email attachments What's ...

We have clients on dial up who often complain about timeouts and disconnects. It's just common sense. I hardly ever send large attachments myself.

Large attachments can cause the receiving party a lot of grief.

Collapse -

Depends on line of business.

by tbragsda In reply to Email attachments What's ...

That and expectations. I would set a limit, but where depends on what people are accustom to, normal business procedures etc. If you company is in a business that large files (video etc) are common, larger limits may be necessary. In that case, a retention, archiving policy needs to be in place. In another case, large attachments may be few, but mandatory archiving/deleting may be bad. I work in financial environments where users should seldom get large emails, but they MUST keep things. As a matter o fact, any email sent or received is kept in a archive, moved to tape, and kept forever!

Point is, it will depend on lots of factors. Don't start too low, it will tick people off. Offer a FTP server for occasional large files. Discuss what limits you want to implement with decision makers, explain your case, and agree on a working policy and communicate it well to the users.

Last, I would spend some time, money and effort on a good spam/virus filter. Again, depending on the business your in, you should filter all executables (batch, scripts etc.) from normal users.

One size does not fit all. Figure out what you need before setting rules.


Collapse -

This is a good answer

by amcol In reply to Depends on line of busine ...

It absolutely does depend on what kind of business you're talking about, but there's a way around the problem.

In my organization we occasionally have the need to share rather large files, up to 1gb. Our policy is that we don't allow any attachment larger than 10mb. We've trained users to create and include hyperlinks for larger files. It's simple, reduces (almost eliminates) network traffic clutter and file redundancy, and I've not only heard no complaints from anyone about inconvenience my customer community actually likes the whole idea.

There's an added benefit...this solution gets users thinking about a more organized approach to file storage, which plays nicely into our document management strategy.

Collapse -

Links to ftp for large files.

by tbragsda In reply to This is a good answer

Bingo. Allowing users to send large files does nothing to insure that the receiving client can. Allowing users to receive same large files may be nice, but the sender could very well have restrictions.

We use lots of FTP, both schedule sending/receiveing and "one-offs". In that case, I have a procedure for creating a temp account that expires within 24hrs.

Collapse -

I use FTP too

by house In reply to Links to ftp for large fi ...

But it's more like - "tell me when you get it so that I can get rid it"

Collapse -

use a script

by Jaqui In reply to I use FTP too

that allows a certain number of download, with some form of security.
( like e-stores that allow 4 downloads then kill access, usually account based )

then you only have to add a setting to the script to generate a download page for that client, which can be sent to them in an email.

Collapse -

More work - but please, elaborate.

by house In reply to use a script

Mock conversation...

me> Yeah I have that. You want it?

associate> Sure.

me> (upload and post link) http://blah.blah/~blah/blah.bla

associate> Thanks

me> let me know when you have it

associate> done

me> gone

I think that developing a small script is overkill in this case. Beside, that's not really my cup-o-tea, so I'd be scratching my head wondering how to design a script to generate a download page for the friend to use. Unless of course... you would like to post reference on the topic.

I'd love to post the message - "This message will self destruct in ten seconds" - Inspector Gadget style.

Collapse -

Post. I would love to see it.

by tbragsda In reply to use a script

In some cases, I give the clients a VB app that download/uploads without the client getting (knowing) their iD/pass, or much of anything. Works well. This is only for outside entities that do a far amount of work with us, but that seems to work well.

I would love a script that for one or two downloads, them disable id.

Related Discussions

Related Forums