UMail Migration - Known Issues

Due to the complex way people and groups use email for sending messages, creating meetings and using shared calendars, this migration from HCI Email to UMail is also... complex.   We expect this project to be "bumpy", though when it's complete all the frustrating challenges we've faced in being on two different email systems will be gone.

Here is a list of known issues, and ways to mitigate their impact, while the email migration is underway.

1.  Meetings - calendar items will be successfully copied from HCI's email to UMail and will appear in your Calendar when you login to Umail, but the links those meetings have to the Meeting Organizer will be broken.  This means that if a Meeting Organizer wants to change the location of a meeting, or the time, recipients who've been migrated won't get those updates.   The workaround is for the Meeting Organizer to send an email to the meeting attendees informing them of the changes, and for recurring meetings instruct attendees to delete the meeting from their calendar and to then re-send invitations to the attendees.

2.  After migration to UMail, some HCI colleagues may be difficult to find in the UMail address book.

 - this can be due to the default naming convention from automatically generated mailboxes, which uses the FIRSTNAME MIDDLENAME LASTNAME format.  (Notify CATG when you see this - we'll change the "display name" of HCI colleagues in the UMail address book).

 - other reasons may be that their name has changed, or that they've elected to be "hidden" in the UMail address book.

The foolproof way to send email to HCI colleagues from UMail is to simply enter their firstname.lastname@hci.utah.edu email address in the "To" window.

3.  Replies to Migrated Messages may "bounce" - if/when this happens, follow this procedure:  Clearing-BadAddresses

4.  Some groups may not appear in the UMail address book.   We are working to have these groups appear in the UMail address group as the groups are migrated.

As additional problems arise, please let us know so we can help navigate around the problem, and help others deal with similar issues, as need be.