Developer Forum

Hi All,

Please forgive me if this question has already been asked.

PROBLEM: I have a recurring issue in that occassionally exchange (2003 - SBS
Premium) users send large messages to numerous people - usually 50-500
recipients. Obviously when this happens our 1Mb/1Mb link gets totally stuck
attempting to send messages with a total volume size of sometime over 2Gb. -
individually the message may only be 3Mb or so but times that by 500 and you
can see my problem.

FAILED SOLUTIONS: I've attempted changing the various message limits within
exchange but these only seem to effect the actual message size without taking
into account the number of recipients. Even after fully educating the small
number of users (50) that we have their will always be the one that forgets
and creates havock. I have also attempted the same with Trend Micro Spam
filter - it also has these restrictions.

HELP!!: Any advice on the above would be greatly appreciated.

Our setup is:

1 x Windows 2003 SBS Premium server SP1
- with the Trend Micro Messaging and Security Suite (A/V, Spyware, Spam
and Content filtering)
- Exchange SP2
- ISA 2004
1 x Open BSD Firewall using SpamD to filter messages and IP addresses

Please let me know if you need any more details.

Thanks.

Hi there,

On your default SMTP connector under Exchange System Manager | First Routing
Group | Connectors, right click it and choose Properties | Delivery Options.

From here tick 'Use different delivery times for oversize messages'. Set the
size limit and then the schedule.

You can then configure Exchange to send all these oversize messages outside
of normal office hours, so during normal operation hours you don't ***
your bandwidth.


Hope that helps,

Oliver

Hi Oliver,

Thanks for replying - am I right in assuming that this option will only take
into account the actual message size and not the message size times the no.
of recipients?

Unfortunately some of these messages can be quite small (2Mb even) but
sending to 500 or so people is what creates the issue, not so much the
individual message size. Even sending these outside of office hours would
create a couple of problems as I would need to restrict (if I understand
correctly) all messages above 2Mb or so and even then the whole message would
not be delivered for a few days.

My ideal solution would be to have the originating message bounce back,
based on it's total message size - perhaps implementing a limit of 200Mb,
which could then be sent outside of office hours... But maybe this is just
wishful thinking.

Thanks for trying.

Boyd.