Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Hub Tranport Rule Issue

Status
Not open for further replies.

oyazo

MIS
Apr 14, 2008
47
PT
Hello All,

We use exchange 2007 in my company.

We have configured certain individual (Up to 70 people) to be able to send mail to all staff.

However, we want to restrict them from sending large attachment (say 1MB)to all staff but still want want all staff to be able to send large attachment size (say 5MB) between one another.

Thank you

Oyazo
 
Do you know how Single Instance Store works? It makes it so that for each Mailbox Database, an attachment that is sent to multiple users is only stored once. So there's no real storage benefit to setting up this rule, since even if a user sends a 3mb attachment to 17 different internal users who are in the same mailbox database, only one copy of the attachment will be stored in the database, and only 3mb used.

If you have two mailbox databases and some of the users were in each, then there would be 6mb of storage used, since each database would keep a copy.

Since the point of your question seems to be about how to preserve space, I figured explaining SIS would be a good way to answer this question and save you the hassle of setting up this sort of rule.

Dave Shackelford
Shackelford Consulting
 
Thanks Shackdaddy,

Im quite aware of the SIS and what it does. We are not bothered about space at all because we know SIS takes care of that.

My main concern is Network clogging by sending 3mb of data to 10,000 staff.

We want to restrict users from sending big attachment basicall to free our bandwidth.

once again thanks for your contribution.

Oyazo.
 
My main concern is Network clogging by sending 3mb of data to 10,000 staff.
There is seldom a technological solution to a behavioral problem as Ed Crowley would say.

If you restrict them from going to the DL, a user could pick the DL, expand it, then send it and it would go through.

I played around with some transport rules and I don't see a way to restrict them from going to the DL yet still allow individual members of the DL from receiving them.

Pat Richard MVP
Plan for performance, and capacity takes care of itself. Plan for capacity, and suffer poor performance.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top