Merged Student and Staff email accounts - create a rule to separate student messages from staff messages


If you have an @mail.utoronto.ca or an @alum.utoronto.ca account, it will be merged with your @utoronto.ca account. If you wish to keep incoming messages to each account separate, you will need to create a rule so that messages sent to your @mail.utoronto.ca account are sorted into another folder.

Although it's not required, we recommend that this step be completed before your staff account is migrated. These instructions assume you do not have subfolders within your Inbox.

  1. Log into your UTmail+ account at mail.utoronto.ca.
  2. Create a new folder and name it Student Email. To do this, click on the plus (+) sign beside your Mailbox name in the list of folders, then type Student Email in the field created.
  3. Click the Settings icon in the top right corner, then begin typing rules into the search field. When Inbox rules appears below the field, click on it.

    OWA settings

  4. Under inbox rules, click the + sign to create a new ruleInbox rules 1

  5. In the next screen, name the rule Student UTmail+. 

    Inbox rules 2

  6. Under When the message arrives..., select It was sent or received and then Sent.

    Select Rule Options


  7. In the field beside It was sent to, insert your cursor and type your @mail.utoronto.ca email address. If you have an @alum.utoronto.ca address, type that in as well. Click Save.

    Select Rule Options 2


  8. Under Do all of the following: select Move, copy, or delete and then Move the message to folder.

    Select Bulk Rule Options 3


  9. Choose the Student Email folder you created in step 1.
  10. Uncheck the option Stop processing more rules and click OK.
  11. Click Save and the rule will be active.
  12. Select all the email in your Inbox and move it to the Student Email folder.
  13. Remember to check the Student Email folder and manage its content.
Tags: Office 365, UTmail+
Last update:
2017-09-26 14:42
Author:
Amanda Wagner
Revision:
1.6
Average rating:0 (0 Votes)

You can comment this FAQ