16 replies
by dc_guy
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?
by house
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.
by tbragsda
.
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.
TBR
by amcol
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.
by tbragsda
.
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.
by jaqui
I send links to files instad of files.
the only time I ever attach a file is an image, then only to my wife.
otherwise it is always a link to a webserver.
I also send in plain text, and concider any other format to be spam.
( html, multipart alternative are spam )
and if I get an attachment when I'm not expecting one, then I call it spam, as it's multipart alternative format.
by house
by jaqui
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.
by house
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.
by tbragsda
.
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.
by dafe2
We use a 5 Meg limit on external mail messages and enforce a 20 Meg limit on mail box sizes.
Personally, I'd include a link to a file where possible (or) advise the recipient of the attachment size before sending it if they are on dial up.
by jaqui
they only place I've seen using it is a store,
Daz3D
they also have a time limit that removes the links.
the accounts page is a huge script.
well over limit for posts here.
by tonythetiger
by ramt
Customers often send each other within the domain attachment with over 50MB. We give them up to 100MB.
We see bounce back when the destination is over quota or the SMTP server don't accept mail over certain size.
by scottyuk
I have always worked on the basis that if an email can be composed with a size of 1Kb, then it should be! Adding un-necessary elements should be avoided and I look at this old post with interest.
Parts of the thread do discuss maximum size limits and I expect most of us have had similar limits and increased them since this post originally was made.
With my IT hat on, I would still say that if the same thing can be said in 1Kb rather than 50Kb, then it should be. However when putting a corporate hat on, I have to take on board the fact that marketing want pretty footers with logo, links to Twitter, Facebook et al.
The demo above from Microsoft on creating signatures suggests keeping messages "under 100 KB if possible". Is this suggested size still a little on the heavy side ?
Yes connections are faster and more stable but with the increase of basic emails going from say 5Kb to 50Kb, mailbox quotas get used 10 times quicker and archiving resources need addressing 10 times quicker.
So what opinions are out there?
For me I would say, no images embeded within messages themselves, all elements hyperlinked to the web and the size before adding the meat and bones of the content should be no more than 20Kb.
I'd be interested in the opinions of others out there.
Cheers
Martin
UK
This discussion is closed to new replies.
Trending Desktop posts
Sort by Trending