Using Cloud based spam/email control. Strategies for managing image sizes inbound?

hi guys,

We run Exchange 2010 and we have Symantec's Messagelabs as our spam and email policy controller. I've set a limit of 10MB for attachments coming inbound and for them to be deleted.

However, the issue is that then you create the problem of that email being blocked, then the users need to get in touch to ask why/what has happened, which they come to us for and we have to begin asking questions and then find out 'aha..it was because the image size was too big'.

Are there better ways to manage it? For example, to have the inbound email to go into a mailbox that we can monitor which we release the content?

Do you have any strategies that you use?

Thanks
Yashy
LVL 1
YashyAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

bluebookCommented:
There are two ways of blocking big emails on the MessageLabs service, and from your description I'm not sure which one you are using.

There is a block on the total message size (not the size of attachments), which is configured through the anti-virus settings (oddly enough!).  If you are using this I don't think you have any options for notifying anyone, but I'm not certain.  You can also use the Content Control / Data Protection service to block based either on total size or on size of individual attachments (or both).  This is much more flexible than the AV settings, because you can also limit it to certain users, or provide exceptions, etc.  If you use this service you can create a custom notification associated with the rule, which will send a message to the recipient, and tell them that the message was blocked, why it was blocked, who it was from, etc.  You can also send a notification to the sender if you wish, and a third one to an administrative address.  As an alternative to blocking the message outright you could redirect it to a mailbox from where you can retrieve it, and still provide the custom notification to the user to say this has happened.

The right answer really depends on why you are blocking the message in the first place.  If you want to save bandwidth or storage space then re-directing it to a different mailbox doesn't really help.  So my suggestion would be that you block it, send a notification to sender and recipient, and potentially have a special "exception" email address which goes to a mailbox you control, so that if a user really needs to get this message on a one-off basis it can be addressed to the special address and you can retrieve the message for them.

If you are using the AV service to do the size block I think your options are extremely limited if they exist at all.

Paul
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
YashyAuthor Commented:
Thank you. great response
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Email Servers

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.