Limit internal message size on single MSX 5.5 server?

[Jim Mueller]

I have a single NT4 MSX SP3 server. Does a method exist wherein I can limit the size of messages flowing between internal recipients, just like I can restrict message size on the MTA and/or IMS? What I've read so far implies "no" since it's part of the private IS.

Reason I need to do this is that we have about 60 sites which trasfer e-mail via dialup. These intermittent huge messages (9M is the largest I've caught) become a big nuisance for the low-bandwidth sites.

We've tried the written policy fix, and let's just say it hasn't worked...

Thanks!

Jim

[Ramon Pichel]

I 'am also looking for something like that.
At the moment i've found a registry key that will route local messages through the MTA so the restrictions are active.

q239427

Routing Local Messages Through the MTA
To be copied correctly, local messages must be routed through the MTA instead of being delivered directly by the private information store.
Open the following registry key:
HKEY_LOCAL_MACHINE SYSTEM CurrentControlSet Services MSExchangeIS ParametersSystem
NOTE: The above registry key is one path; it has been wrapped for readability.


Add a new DWORD value named No Local Delivery.


Set the value of No Local Delivery to 1.

Please let me know if it works ?
I've not tested it yet.


------------
Jim Mueller at 11/21/2001 4:06:49 PM

I have a single NT4 MSX SP3 server. Does a method exist wherein I can limit the size of messages flowing between internal recipients, just like I can restrict message size on the MTA and/or IMS? What I've read so far implies "no" since it's part of the private IS.

Reason I need to do this is that we have about 60 sites which trasfer e-mail via dialup. These intermittent huge messages (9M is the largest I've caught) become a big nuisance for the low-bandwidth sites.

We've tried the written policy fix, and let's just say it hasn't worked...

Thanks!

Jim

[Garf]

Jim,

Each mailbox has a 'Limits' property page that allows you to specify an maximum size for both outgoing & incoming messages.

You can 'bulk' modify all of of your user's mailboxes by using the Directory Export & Import tools.

Hope this helps :)

Garf
------------
Jim Mueller at 11/21/2001 4:06:49 PM

I have a single NT4 MSX SP3 server. Does a method exist wherein I can limit the size of messages flowing between internal recipients, just like I can restrict message size on the MTA and/or IMS? What I've read so far implies "no" since it's part of the private IS.

Reason I need to do this is that we have about 60 sites which trasfer e-mail via dialup. These intermittent huge messages (9M is the largest I've caught) become a big nuisance for the low-bandwidth sites.

We've tried the written policy fix, and let's just say it hasn't worked...

Thanks!

Jim

[Ramon Pichel]

It's working.


------------
Ramon Pichel at 11/26/2001 7:24:52 AM

I 'am also looking for something like that.
At the moment i've found a registry key that will route local messages through the MTA so the restrictions are active.

q239427

Routing Local Messages Through the MTA
To be copied correctly, local messages must be routed through the MTA instead of being delivered directly by the private information store.
Open the following registry key:
HKEY_LOCAL_MACHINE SYSTEM CurrentControlSet Services MSExchangeIS ParametersSystem
NOTE: The above registry key is one path; it has been wrapped for readability.


Add a new DWORD value named No Local Delivery.


Set the value of No Local Delivery to 1.

Please let me know if it works ?
I've not tested it yet.


------------
Jim Mueller at 11/21/2001 4:06:49 PM

I have a single NT4 MSX SP3 server. Does a method exist wherein I can limit the size of messages flowing between internal recipients, just like I can restrict message size on the MTA and/or IMS? What I've read so far implies "no" since it's part of the private IS.

Reason I need to do this is that we have about 60 sites which trasfer e-mail via dialup. These intermittent huge messages (9M is the largest I've caught) become a big nuisance for the low-bandwidth sites.

We've tried the written policy fix, and let's just say it hasn't worked...

Thanks!

Jim