Settings - POPcon SMTP/Exchange server

On this configuration screen you can specify the Exchange™-(SMTP) Server you want the mail to be directed to. Normally this will be the network name of your Exchange™ server.

You need to provide the following fields of information:

Exchange Server: Your Exchange/mail server, typically the machine name of where your Microsoft Exchange Server™ is installed.

SMTP Port: Almost always the TCP/IP port for SMTP transfers is 25. Change this setting only if you know what you are doing. Sometimes Firewalls or routers cause the port number to be changed. Ask your network administrator if you think you need to change this setting.

SMTP Timeout: The time to wait for a non-responding exchange server in seconds.

Advanced: Here you can define the reactions of POPcon to emails that Exchange does not accept. You can choose different reactions to different types of SMTP error messages from Exchange:

User unknown: What to do if Exchange did not accept the mail because the user is unknown.

IP has been blocked: What to do if Exchange did not accept the mail because the sender IP is blocked.

Action not taken: What to do if Exchange did not accept the mail because of the intelligent message filter.

Configure Outlook Web Access (OWA) 2003 Attachment Blocking

There are 2 levels of file attachments for Outlook Web Access. Level1 attachments have file extensions that are prohibited from accessing by OWA. Level2 attachments have file extensions that can be accessed, but only if saved to the client's file system first.



OWA is installed with a default set of file extensions for the two levels as shown in the following registry keys:

Level 1 attachments

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MSExchangeWeb\OWA

Value: Level1FileTypes

Type: REG_SZ
Value Data:

ade,adp,app,asx,bas,bat,chm,cmd,com,
cpl,crt,csh,exe,fxp,hlp,hta,inf,ins,isp,js,jse
,ksh,lnk,mda,mdb,mde,mdt,mdw,mdz,msc
,msi,msp,mst,ops,pcd,pif,prf,prg,reg,scf,scr,
sct,shb,shs,url,vb,vbe,vbs,wsc,wsf,wsh

Level 2 attachments

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MSExchangeWeb\OWA

Value: Level2FileTypes

Type: REG_SZ

Value Data:

ade,adp,asx,bas,bat,chm,cmd,com,cpl,crt,exe,hlp
,hta,htm,html,htc,inf,ins,isp,js,jse,lnk,mda,mdb,mde,
mdz,mht,mhtml,msc,msi,msp,mst,pcd,pif,prf,reg,scf,scr,sct
,shb,shs,shtm,shtml,stm,url,vb,vbe,vbs,wsc,wsf,wsh,xml,dir,dcr,plg,spl,swf

Attachments listed should be separated by a comma with no space.

What do I need to do to make sure Exchange 2000 runs fine on my Windows Server 2003 forest?

If you've installed Exchange 2000 into the forest before running ADPrep, you have to correct some mistakes that were made in the Exchange 2000 schema extensions.

Specifically, both ADPrep and Exchange 2000 define labledURI, houseIdentifier and secretary attributes, but Exchange 2000 does not use the correct LDAP display names (lDAPDisplayName) as defined in RFC 2798.

If you run ADPrep after Exchange 2000 has been installed without fixing these attributes, you can end up with duplicate schema objects with different lDAPDisplayName attributes.

To solve the problem, you must run the inetorgpersonfix.ldf file that is located in \support\ tools\support.cab. This LDIF file fixes the lDAPDisplayName attributes of the three attributes.

First save the inetorgpersonfix.ldf file, then import it using the ldifde utility. Here is an example where we will be importing into the mycorp.com forest:

ldifde.exe /i /f inetOrgPersonFix.ldf /c "DC=X" "DC=mycorp,DC=com"

Note that inetorgpersonfix.ldf uses DC=X as the forest path, which is why we needed to use the /c switch to replace it with our own forest path.

More Information : http://www.petri.co.il/

Administer Exchange 2003 from Windows XP SP1

How can I manage my Exchange 2003 server from a Windows XP/2000/2003 workstation?

This article describes the steps to be taken in order to be able to administer an Exchange 2003 server from a Windows XP Pro computer that is installed with SP1 or SP1a or from a Windows Server 2003 Member Server.

Note: For an Exchange 2000 version of this page and for more background on this issue (with detailed screenshots) click on the following article: Administer Exchange 2000 from Windows XP SP1.

You can administer Exchange Server 2003 servers from a Windows computer by using Exchange Setup to install only Microsoft Exchange System Management Tools.

Note: If you have not installed an Exchange 2003 server in your organization, you must first run ForestPrep. ForestPrep extends the Active Directory schema to include Exchange-specific classes and attributes, and creates the container object for the Exchange organization in Active Directory.

To install Exchange System Management Tools ensure that the computer meets the following requirements:

*
The computer is running Windows XP, Windows Server 2003, Windows 2000 Professional, or Windows 2000 Server SP3.
*
The computer name does not contain unsupported characters.
*
The language version matches any previous installation of Exchange 2000 System Management Tools (except for upgrades from English to Korean, Traditional Chinese, or Simplified Chinese).
*
Log onto the domain with an account that has local machine administrator permissions.

Depending on the version of Windows that is running on the computer, install the required services.

Windows XP Service Pack 1

*
Internet Information Services Snap-In component
*
SMTP Service component
*
World Wide Web Service
*
Windows Server 2003 Administration Tools Pack, AdminPak.msi

Windows XP SP2

*
Internet Information Services Snap-In component
*
Windows Server 2003 Administration Tools Pack (AdminPak.msi)

Windows Server 2003

*
Internet Information Services Manager component

Windows 2000 Professional SP3

*
Internet Information Services Snap-In component
*
Windows Server 2000 Administration Tools Pack (AdminPak.msi)

Windows 2000 Server SP3

*
Internet Information Services Snap-In component
*
Windows Server 2000 Administration Tools Pack (AdminPak.msi)
*
SMTP Service component
*
NNTP Service component

Next, run Exchange Setup, located in the SETUP\I386 folder. On the Component Selection page, set the installation action to Custom, and then select Microsoft Exchange System Management Tools.



After the installation is complete go to the Start menu and see if the Microsoft Exchange folder and shortcuts have been successfully created.



Finally, you must install the latest Exchange 2003 Service Pack:

Exchange 2003 Service Pack 2 (SP2) was released on the 19th of October 2005. You can download SP2 for Exchange 2003 right here:

Download Exchange 2003 SP2 (109mb)

Defragment Exchange 2003 Server Databases

Exchange databases run a defragmentation process once a day by default. This process rearranges mailbox store and public folder store data more efficiently, eliminating unused storage space. Exchange database online defragmentation occurs automatically as part of the database maintenance process. Online defragmenting is performed automatically at 2:00 AM every day by default. Online defragmentation makes additional database space available by detecting and removing database objects that are no longer being used. The defragmentation process provides more database space without actually changing the file size of the database.



The following are two ways to schedule database defragmentation:

1. To schedule database defragmentation for an individual database, on the Database tab of a mailbox store or public folder store object, configure the maintenance interval using the Maintenance interval option.

2. To schedule database defragmentation for a collection of mailbox stores and public folder stores, on the Database (Policy) tab of a mailbox store or a public folder store policy, configure the maintenance interval using the Maintenance interval option.

Although online defragmentation provides some additional database space, you should also defragment your Exchange database offline to reduce the physical size of your Exchange database. You can perform offline defragmentation by using the ESE utility (ESEUTIL) while your mailbox stores and public folder stores are offline.

You would perform offline defragmentation, for instance, if you had recently moved a large number of users from a server running Exchange 2000/2003. In that case, defragmenting offline decreases the size of your Exchange databases by rearranging the data on the server’s Exchange databases, and discarding any unused database pages.

Note that the length of time that the defragmentation will take will depend on the amount of white space in the database, as well as the size of the transactions recorded in the database, and your hardware specifications.



Offline defragmentation creates a new database by copying all records and tables from the old database into the new database. Because this is a copy, defragmentation requires free disk space equal to the size of the database (actually, you'll need 110% of free space).

Very important note: After defragmentation is complete, ESE considers the new database to be a different database from the original. Therefore, the original database is deleted and its member log files cannot be replayed into the successor database.

A full backup should be completed as soon as possible!

Prior incremental or differential backups are no longer useful because they reference database pages that were reordered by the defragmentation process. ESEUTIL defragments a database by creating a new database, copying the old database records to the new one, and discarding unused database pages, which results in a newly organized compact database file.

Microsoft recommends a conservative 5 - 7 GB per hour for a defrag operation, which means that your server will be offline for as long as it takes, assuming no hardware failures will occur.

When you run ESEUTIL /d against a database to defragment it, the streaming file associated with the database is automatically defragmented. This is the default behavior.

For example, if you run the following command at a command prompt:

eseutil /d "c:\program files\exchsrvr\mdbdata\priv1.edb"

The Priv1.edb and Priv1.stm files are defragmented. If you do not want the streaming file to be defragmented, include the /i option.

Run ESEUTIL with the /p switch to configure ESEUTIL to create the new defragmented database on an alternate location (for example, to a location on a different hard disk). This switch lets you preserve your original defragmented database (which lets you revert back to your original database if necessary). This switch also significantly reduces the amount of time it takes to defragment a database, because you are rebuilding to a new location, rather then rebuilding the database in place.

Note: The database you wish to defragment must be taken offline (i.e. dismounted) before attempting to perform the defragmentation operation. When you run ESEUTIL against a Microsoft Exchange computer where it's database is still mounted you will receive the following error message:

Operation terminated with error -550

If the database is still mounted, use the following steps to dismount the database, and then run ESEUTIL:

1. Start Exchange System Manager.

2. Right-click the database that you want to dismount.

3. Click All Tasks, and then click Dismount Store.

Grant Full Mailbox Rights to an Administrator on Exchange 2003

Use the following procedure to grant access to an Exchange 2003 mailbox:

Note: You must have the appropriate Exchange administrative permissions to do so.

1. Start Active Directory Users and Computers.
2. On the View menu, ensure that the Advanced Features check box is selected.
3. Right-click the user whose mailbox you want to give permissions to and choose Properties.
4. On the Exchange Advanced tab, click Mailbox Rights.
5. Notice that the Domain Admins and Enterprise Admins have both been given Deny access to Full Mailbox access.
6. Click Add, click the user or group who you want to have access to this mailbox, and then click OK.
7. Be sure that the user or group is selected in the Name box.
8. In the Permissions list, click Allow next to Full Mailbox Access, and then click OK.
9. Click Ok all the way out.

Granting right to a mailboxes located within a specific mailbox store

Use the following procedure to grant access to Exchange 2000 or an Exchange 2003 mailboxes found on a specific mailbox store:

Note: You must have the appropriate Exchange administrative permissions to do so.

1. Start Exchange System Manager.
2. Drill down to your server object within the appropriate Administrative Group. Expand the server object and find the
required mailbox store within the appropriate Storage Group. Right-click it and choose Properties.
3. In the Properties window go to the Security tab.
4. Click Add, click the user or group who you want to have access to the mailboxes, and then click OK.
5. Be sure that the user or group is selected in the Name box.
6. In the Permissions list, click Allow next to Full Control, and then click OK.
7. Click Ok all the way out.

Granting right to a mailboxes located on a specific server

Use the following procedure to grant access to Exchange 2000 or an Exchange 2003 mailboxes found on a specific server:
Note: You must have the appropriate Exchange administrative permissions to do so.

1. Start Exchange System Manager.
2. Drill down to your server object within the appropriate Administrative Group. Right-click it and choose Properties.
3. In the Properties window go to the Security tab.
4. Click Add, click the user or group who you want to have access to the mailboxes, and then click OK.
5. Be sure that the user or group is selected in the Name box.
6. In the Permissions list, click Allow next to Full Control, and then click OK.
7. Click Ok all the way out.

Note: It might take some time before the changes you've made will take effect. The amount of time needed is influenced by the number of domain controllers, Global Catalogs and site replication schedules and intervals. On one domain with one site containing multiple domain controllers it might take up to 15 minutes before you can begin using these new permissions. On
single servers that are also DCs you can speed up the process by restarting the Information Store service.