Adding CGNET directory entries with Exchange

Most Post Offices are set up to automatically replicate changes to their directories to CGNET, where they will be registered and assigned a normalized email address. Accounts are added, and deleted, at CGNET four times a week, and may largely be automated by following certain conventions to interface with directory software at CGNET.

The assigned address -- such as J.DOE@CGNET.COM -- is usually a combination of Last Name and First Name fields, thereby permitting administrators to compose their desired address. For instance, to create the above address, fill the Last Name field with "DOE" and the First Name field with "JOHN". As long as this does not conflict with existing names, the defaults will become active

Note that fields Display Name, Initial, and Alias get ignored.

Additionally, mail boxes created on your Exchange server, may or passed over for two reasons:

1. The Last Name field must have a value. If there is no value, the box is skipped. (The First Name should also be filled out with at least a first initial, except in the case of organization or departmental boxes, listservers, etcetera. The absence of a First Name implies that the box is not related to an individual.)
2. Any box that is a member of the Distribution list "CGNET-INTERNALONLY" in the Recipients container on the server, will be skipped by the directory software. This list provides a means for admins to filter out internal users.

To take advantage of the filtering feature, add a Distribution list CGNET-INTERNALONLY (all upper case) to your local Recipients. When you add boxes to the CGNET-INTERNALONLY distribution list, the list must be unhidden, but to prevent people from accidentally selecting it for mail, you probably want to hide it the rest of the time. You may also want to take the precaution of limiting addresses which can send mail to CGNET-INTERNALONLY.

You may further protect yourself from internal users sending mail externally, by editing their SMTP address. Simply adding the string "restricted" after the @ sign, will signal the PMDF gateway to block all mail originating from that address, or going to that address. For example, an internal user with SMTP address JOHNDOE@CSI.EXCH.CGNET.COM would theoretically still be able to send mail, or receive external mail, if they by-passed the usual gateway. To protect against that, edit this person's SMTP address to read JOHNDOE@restricted.CSI.EXCH.CGNET.COM.

Using a combination of tools, any configuration of external versus internal mail should be possible. Here is a summary of four possible scenarios:

1. Mail box should be registered in the CGNET Directory. It should be listed in the local Recipients container, and allowed access to external mail. This includes a listing in the CGNET-Members container. Leaving all settings to their defaults, will results in the box being added to the CGNET directory.
2. Mail box should not show up in the local Recipient's Container. Edit the box, and click the Advanced tab. Set the HIDEAB field to True for the box, and it will not be displayed in Recipients.
3. Mail box should be listed in local Recipients container, but should not be listed in the CGNET-Members container. Leave HIDEAB unchecked, to allow listing in Recipients. Then use the Admin program to add this box to the Distribution List CGNET-INTERNALONLY in the NOCHUB Recipients container. Instructions for doing so are below.
4. Absolute mail blocking by PMDF. To guarantee that absolutely no internet mail will flow into or out of the box, edit the SMTP address to include "@restricted" in the SMTP address. You may never need to use this option -- it is most likely a rare case.

Also remember, if you have any questions about directory issues, or you have requests for changes to the directory, send mail to CGNET-DIRMASTER@cgnet.com.