MESSAGING DEEP CORE
Exchange Recipients, Mailboxes, Groups and Address Books Deep Core
Email objects are directory-backed business identities, not isolated entries inside a mail server.
Chapter purpose
Tie recipient administration to the identity lifecycle so addresses, mailboxes, groups and address books stay consistent.
Learning objectives
- Distinguish mailbox, mail user, mail contact and group.
- Explain primary and proxy SMTP addresses.
- Understand address lists as filtered directory views.
- Build a joiner/mover/leaver messaging process.
Why this matters in a real company
Poor recipient management causes misaddressed mail, duplicate identities, privacy mistakes and lingering access after staff leave.
3.1 Recipient types represent different business objects
A mailbox-enabled user has an AD identity and mailbox. A mail user has an internal identity but external mail destination. A mail contact represents an external person without normal internal sign-in. Distribution groups deliver messages to members.
Choose the object type from the business identity and mail requirement, not from whichever wizard is easiest.
3.2 Addresses are lifecycle data
A recipient can have multiple proxy addresses while one SMTP address is primary. During a rename, an old address may need to remain as an alias so customers and applications continue to reach the user.
Address policy should be documented and exceptions should have owners.
3.3 Address lists are filtered directory views
Microsoft describes address lists as collections of mail-enabled recipient objects based on filters. They update dynamically as recipient properties change.
Custom address lists can be useful for business separation but should not be created without a clear reason.
3.4 Useful inventory
Get-Mailbox -ResultSize Unlimited | Select-Object DisplayName,PrimarySmtpAddress
Get-DistributionGroup | Select-Object Name,PrimarySmtpAddress
Get-AddressList | Select-Object Name,RecipientFilterRecipient data and Active Directory
On-premises Exchange recipient configuration is stored in Active Directory. That is why recipient administration and directory administration are closely connected. Changing a user account without understanding Exchange attributes can create incomplete or inconsistent recipient state.
Address policies, proxy addresses and recipient filters should be treated as managed configuration. They are not merely cosmetic because external systems and users may depend on stable addresses.
Delegates, forwarding and hidden relationships
Mailbox lifecycle includes more than the mailbox object. Delegates, Send As, Send on Behalf, forwarding rules, group membership and shared-mailbox access can preserve access after a user changes roles or leaves.
A leaver checklist should therefore query those relationships explicitly. Disabling the account is necessary, but it does not by itself document who can still read or send through the mailbox.
Employee changes surname and department
The business wants a new primary email address but old senders must still reach the person. The employee also moves from Sales lists to Finance.
Decision: Change primary address while retaining the appropriate old alias, update groups and verify address-list visibility.
Evidence: Test old/new addresses, displayed primary address and group membership.
Hands-on lab
Create a recipient lifecycle worksheet covering identity, mailbox, aliases, groups, delegates, forwarding and retention.
Troubleshooting exercise
- Recipient not in expected address list: check properties/filter.
- Old alias fails after rename: verify proxy address.
- Leaver still receives mail through forwarding/delegation: review relationships.
Field checklist
- Recipient type intentional.
- Address naming policy documented.
- Aliases deliberate.
- Group ownership defined.
- Leaver mailbox process exists.
- Address-list filters understood.
Current technical references
The supplied PDF books are used as a historical curriculum map. Current implementation guidance is checked against current Microsoft documentation.