Archiving users and redirecting mail
In order to retrieve new incoming emails sent to an employee who has left the organization, you have two options:
- forward their mail to another user: this implies adding the email address of the user who has left the organization (email@example.com in this example) as an alias of the target user
- forward their mail to a shared mailbox: this implies creating a shared mailbox whose address is firstname.lastname@example.org or whose alias matches this address.
To archive a user, save their data and redirect their mail, you must:
- Rename the user as user1.bck
- Set "user1.bck" as an alias for user1's address
2'. OR: Create a shared mailbox "bp.userbck"
- Redirect (with or without local copy) messages from user1.bck to userCS
- Wait for the next global backup.
- To retrieve email messages - 3 ways:
- Use a thick email client such as Thunderbird to copy all messages to the shared mailbox "bp.userbck".
- Use a thick email client such as Thunderbird to retrieve all messages via POP.
- Use the Restoring user or mailshare mailbox contents procedure
- To retrieve contacts and the calendar:
- In the admin console, go to "DataProtect Navigator"
- Click the last backup
- Select the user "user1.bck"
- Click the links to retrieve VCard files (address books) and the ICS file (calendar data).
- Delete the user "user1.bck"
- Create an alias "user1" for the user "userCS"
Sometimes, you might not want to have all of an employee's messages forwarded to another for confidentiality issues and have an auto-reply message sent to senders asking them to contact someone else in the organization.
In that case you have two options:
- Create a new user "user2.out" with the departed user's address "email@example.com" as an alias and set up a custom out-of-the-office message. The advantage of this approach is that you are able to set up a user-specific message, the downside is that this user will be removed from the subscription's user count.
- Create one user "user.deactivated" with the addresses and aliases of all departed employees as aliases and set up a common message for all users. With this method, one user allows you to manage all departed users.
Deletion and AD synchronization
When a user is deleted in the Active Directory, it is automatically archived in BlueMind during synchronization.
Users can therefore be deleted in the Active Directory at any time. This will result in the user being disabled in BlueMind and stop them from logging in but will not delete their data.
This means you can follow the procedure described above and then delete the user from the Active Directory.