Link to home
Start Free TrialLog in
Avatar of Frosty555
Frosty555Flag for Canada

asked on

Exchange 2007 on SBS, remove attachments before forwarding

I'm running Exchange 2007 on a Windows SBS 2008 server. Some of my users have blackberries, but we do not have a BES server. Instead we use the BIS service provided by our service provider and forward messages to the users' "blackberry email" (e.g. john.smith@rogers.blackberry.net), which makes it pop up on their blackberry.

Problem is if somebody emails the user and attaches a large picture or something, they get a bounceback error from BIS saying that the message was too large.

The forwarding is done via the Delivery Options in our Exchange server. Is it possible to configure Exchange to strip attachments out of the message before forwarding it to the blackberry?

ASKER CERTIFIED SOLUTION
Avatar of sr1xxon
sr1xxon

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of Frosty555

ASKER

This will not strip the attachment, it will just prevent the email from being sent at all, right?
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Hmmm okay, I'll do some more poking around specifically on attachment filtering rules, message size limit etc but if I really can't find anything appropriate, your solution will at least prevent the ugly bounceback that people who send me emails receive. The user still won't receive the message on their blackberry, but they weren't receiving them on their blackberry in the first place anyways.

Thanks for the tips!
I found this reference article here:

http://technet.microsoft.com/en-us/library/bb124345(EXCHG.80).aspx

In particular, the section on "User Limits" is particularly interesting, it looks like I can set a "Maximum Send Size" for a specific contact in Exchange (e.g. the contact I created for the blackberry email address). So maybe I can set this up just for individual users and not necessarily for the entire organization.

Not sure what it does exactly if a message is too big - maybe it will still issue a Delivery Status Notification error message, but at least it will be from my own Exchange server instead of from the BIS servers provided by Rogers. I can perhaps customize the message so that it is more meaningful.