Exchange 2007, increasing e-mail rule limit

Exchange 2007 rule sizes by default is set to 64kb (rather than 32kb for Exchange 2003).
You may change this using Exchange 2007 Management Shell (PowerShell) to max 256kb

To check setting on specific account: (to display RulesQuota : xxKB)
get-mailbox userlogin | fl rulesquota



To change setting to 256kb for specific account:
set-mailbox userlogin -rulesquota 256kb



To change setting to 256kb for all account:
get-mailbox | set-mailbox -rulesquota 256kb

Renewing the self-signed certificate Exchange Server 2007:

Exchange Server 2007 need to renewal a self-signed certificate for use with services like SMTP,IMAP, POP, IIS and Um every one year.


1. Find out your exchange certificate thumbprint with full information and services list
Get-ExchangeCertificate -domain “yourdomain.com” | fl


2. Get a new certificate with a new expiration date and an exportable private key:
Get-ExchangeCertificate -thumbprint “your_old_thumb_print” | New-ExchangeCertificate -PrivateKeyExportable $true


3. Type Y to continue creation of certificate. It'll show new thumbprint


4.  Check services of new certificate:
Get-ExchangeCertificate -thumbprint “your_new_thumb_print” |fs


5. To add required/missing services:
Enable-ExchangeCertificate -thumbprint “your_new_thumb_print” -services IIS


6. To remove invalidates/expired certificate
Remove-ExchangeCertificate -thumbprint “your_old_thumb_print”




You need to Publish them to ISA for WebMail user
1. Using MMC from your mailserver
2. Add/Remove Snap-in > Add > Certificates > Local
3. Under Personal/Certificates, Select Your New Certificate
4. Right Click > All Tasks > Export > Next
5. Select Yes to export  the private key
6. Provide password and check required option
7. It generated PFX file
8. Generated CER and/or P7B if required
9. Import to Trust
10. Under Trust/Certificate Right Click > All Tasks > Import > Next
11. Chose the CER file
12. Same Snap-in for your ISA server
13. Right Click > All Tasks > Import > Next
14. Chose the PFX file
15. Import to trust
16. Open ISA Server Management
17. ISAServer > Firewall Policy > Webmail
18. Double click Mail Listener
19. From Certificate tab, Select Certificate
20. Select your new and active certificate then Apply

How to Configure Exchange 2007 Anti-Spam Automatic Updates

After Enabling Auto updates, we need to make sure our Exchange 2007 Anti-Spam have those updates

To check:
From cmdlet run get-antispamupdates

This show you the currently installed update version.
UpdateMode : Automatic
LatestContentFilterVersion : 3.3.8414.660
SpamSignatureUpdatesEnabled : True
LatestSpamSignatureVersion : 3.3.8611.1336
IPReputationUpdatesEnabled : True
LatestIPReputationVersion : 3.3.8611.063
MicrosoftUpdate : Configured

You can then compare that to the latest version shown at:
http://catalog.update.microsoft.com/v7/site/Rss.aspx?q=exchange+server+2007+anti-spam&lang=en

If you find that its not updated or not properly configured you need to run:
Enable-AntispamUpdates -Identity SERVER01 -IPReputationUpdatesEnabled $True -MicrosoftUpdate RequestNotifyDownload -UpdateMode Automatic -SpamSignatureUpdatesEnabled $True

Then open Windows Update to check new updates

More info:
http://technet.microsoft.com/en-us/library/aa997658(EXCHG.80).aspx
http://technet.microsoft.com/en-us/library/bb125199(EXCHG.80).aspx

Postmaster In Exchange Server

Symptoms:
By default, the postmaster is used to transmit non delivery reports and any other messages that are generated internally by Exchange. However, Exchange 2007 does not contain a postmaster mailbox. This means that those who receive non delivery reports cannot reply back and ask for help.

Solution:
Get-TransportServer
To check and make sure that the postmaster has not already been assigned

Set-TransportServer servername –ExternalPostmasterAddress postmaster@yourdomain.com
You must assign an e-mail address to the postmaster

Get-TransportServer command again to verify that Exchange has been configured to use the postmaster address that you have assigned

You can create the postmaster mailbox in the same manner as you would create any user mailbox or just assign to existing user using add email address

Anti-Spam for Exchange Server 2007 with Hub Transport

Symptoms:
After Installing new Exchange 2007 server with Hub Transport, you realized it is not Anti-Spam Enabled. Many information and Best Practice only refer to Edge Transport. What if you don't have any budged to created Edge server or you only run small organization but must have Anti-Spam mechanism?

Solution:
Actually the Anti-Spam features can be installed directly into the Hub Transport module on the Exchange Server using Power Shell.
1. Run the Install-AntispamAgents.ps1 script. This script is located in the %system drive%/Program Files/Microsoft/Exchange Server/Scripts
2. Restart the Microsoft Exchange Transport service:
Restart-Service MSExchangeTransport
3. Specify the internal SMTP servers by using the InternalSMTPServers parameter on the Set-TransportConfig cmdlet
set-transportconfig –internalsmtpserver x.x.x.x
4. Check 'Server Configuration\Hub Transport', notice the 'Anti-spam Updates Enabled' set to 'True'. If it's not you need to run:
Enable-AntispamUpdates -SpamSignatureUpdatesEnabled $true -UpdateMode Automatic
5. Add quarantine mailbox for administrator to check, deleted, and send again (Approved) quarantined email
6. Do required configuration (SCL and custom configuration) for Anti-Spam features:
- Content Filtering
- IP Allow List
- IP Allow List Providers
- IP Block List
- IP Block List Providers
- Recipient Filtering
- Sender Filtering
- Sender ID
- Sender Reputation

More info: http://technet.microsoft.com/en-us/library/bb201691.aspx

Exchange 2003 to new Exchange 2007 server sending failure

After introducing first Exchange Server 2007 server into an existing Exchange Server 2003 organization, you may encounter an mail flow issue between the two servers.

Symptoms:
- Emails sent from Exchange 2007 to Exchange 2003
- Emails not sent from Exchange 2003 to Exchange 2007 and might be seen in the queue of the Exchange 2003 server.

Solutions:
Remove the smart host from the Default SMTP Virtual Server and instead configure a new SMTP Connector for the Routing Group to send internet email (the namespace of “*”) to the smart host.