Administrators of Exchange Server 2007 can use the command line as a simple way to customize message quota warnings and messages that report notification of the results of an attempt to deliver an e-mail message. The correct pronunciation of "cmdlets" should be "commandlests", a technology that uses Microsoft PowerShell technology and works in a command-line way.
In order to resolve the "notification of the results of an attempt to deliver an e-mail message" DSN5.2.2 This error (which prompts you to "mail Box full"), you can do this simply by using a simple command line such as the following:
New-systemmessage–dsncode 5.2.2–language en–internal $false –text "Sorry, that mailbox are filled to bursting and other Messages. You'll have to try again later when they ' ve read a few things. "
The syntax here is very simple:
1. Dsncode: Lets you specify which specific error you need to customize for a string message.
2. Language: Here is a description of the language in which you are using the string (in this case, of course, we are using English).
3. Internal: This is set to $false, which means that only external users (such as SMTP) are specified here.
4. Text: Describes the error message, but be sure to enclose the words you want to say with quotes.
If you want to modify the quota information, you'd better use the syntax as follows:
New-systemmessage–quotamessagetype warningmailbox–language en–text "Your mailbox is becoming full. Please remove some messages or talk to your administrator about has your mail account upgraded. "
Quotamessagetype: Describes what type of quota mail information This is, and uses Warningmailbox to tell the user that this is one of the possibilities that has been validated.
Other options are self-evident, for example, the interal option, which is not listed here, because the message quota information itself is the default interal. If you want a breakdown of the complete order, you have everything you need in the New-systemmessage entries in TechNet's collection.
It is noteworthy that new-systemmessage only takes effect in one case, that is, on a server that is configured with the Hub Transport server role or an Exchange server that is the Edge Transport server role.