Some members of the UO community are unable to access UOmail via uomail.uoregon.edu due to a larger problem with Microsoft's Outlook on the web.
Available
Info
On Thursday, June 22, from 6am-8am, UO staff will perform maintenance on a component of the university's email system. The work isn't expected to cause noticeable impacts, but it does have the potential to interrupt mail flow throughout that window.
**********
Separately, the UO recently experienced a partial outage affecting incoming email and other UO services:
Emails sent to affected accounts. During the outage (mainly on Tuesday), some emails sent to affected accounts bounced. However, other messages ended up in a limbo state within our systems. Yesterday our team ran two processes to deliver messages from the latter category into people's UOmail inboxes—first around 12:30 p.m. and again at 5:00 p.m. Depending on your email program, the recovered messages may appear with either yesterday's date or their original send dates.
Incoming email flow. Restored for most affected users early Wednesday, June 7. Restored for remaining users early Thursday morning, June 8.
Teams private channel access. If you've lost access to private Teams channels, the owners or members of those channels should be able to restore your access. If that's not possible, then submit a ticket at Microsoft Teams support.
Teams custom tags. Affected accounts that are missing from manually created tags in Teams can be manually added back.
Teams calling. Service has been restored. If you're still not seeing your dial pad, then log out of Teams and log back in again.
Summary. This outage was inadvertently caused by vendor maintenance on our Duck ID system the evening of Monday, June 5. About 4,600 active accounts were affected. Services impacted included UOmail, Teams, and other Microsoft services, as well as the UO Service Portal, Dropbox, and possibly others. Service has been restored except as noted above.
Update on the partial outage affecting incoming email and other UO services:
Emails sent to affected accounts. During the outage (mainly on Tuesday), some emails sent to affected accounts bounced. However, other messages ended up in a limbo state within our systems. Yesterday our team ran two processes to deliver messages from the latter category into people's UOmail inboxes—first around 12:30 p.m. and again at 5:00 p.m. Depending on your email program, the recovered messages may appear with either yesterday's date or their original send dates.
Incoming email flow. Restored for most affected users early Wednesday, June 7. Restored for remaining users early Thursday morning, June 8.
Teams private channel access. If you've lost access to private Teams channels, the owners or members of those channels should be able to restore your access. If that's not possible, then submit a ticket at Microsoft Teams support.
Teams custom tags. Affected accounts that are missing from manually created tags in Teams can be manually added back.
Teams calling. Service has been restored. If you're still not seeing your dial pad, then log out of Teams and log back in again.
Summary. This outage was inadvertently caused by vendor maintenance on our Duck ID system the evening of Monday, June 5. About 4,600 active accounts were affected. Services impacted included UOmail, Teams, and other Microsoft services, as well as the UO Service Portal, Dropbox, and possibly others. Service has been restored except as noted above.
Update on the partial outage affecting incoming email and other UO services:
Emails sent to affected accounts. During the outage (mainly on Tuesday), many emails sent to affected accounts bounced. However, other messages ended up in a limbo state within our systems. Most messages in the latter category were delivered into people's mailboxes in a process completed around 12:30 p.m. today. UO staff are now doing a round of extended processing to ensure all affected users receive such emails. Depending on your email program, the messages may appear with either today's date or the original send dates.
Incoming email flow. Restored for most affected users early Wednesday, June 7. Restored for remaining users early Thursday morning, June 8.
Teams private channel access. If you've lost access to private Teams channels, the owners or members of those channels can restore your access. If that's not possible, then submit a ticket at Microsoft Teams support.
Teams custom tags. Affected accounts that are missing from manually created tags in Teams can be manually added back.
Teams calling. Service has been restored. If you're still not seeing your dial pad, then log out of Teams and log back in again.
Summary. This outage was inadvertently caused by vendor maintenance on our Duck ID system the evening of Monday, June 5. About 4,600 active accounts were affected. Services impacted included UOmail, Teams, and other Microsoft services, as well as the UO Service Portal, Dropbox, and possibly others. Service has been restored except as noted above.
Update on the partial outage affecting incoming email and other UO services:
Emails sent to affected accounts. During the outage (mainly on Tuesday), many emails sent to affected accounts bounced. However, other messages ended up in a limbo state within our systems. Most messages in the latter category were delivered into people's mailboxes in a process completed around 12:30 p.m. today. UO staff are now doing another round of extended processing to ensure all affected users receive such emails. Depending on your email program, the messages may appear with either today's date or the original send dates.
Incoming email flow. Restored for most affected users early Wednesday, June 7. Restored for remaining users early Thursday morning, June 8.
Teams private channel access. If you've lost access to private Teams channels, the owners or members of those channels can restore your access. If that's not possible, then submit a ticket at Microsoft Teams support.
Teams custom tags. Affected accounts that are missing from manually created tags in Teams can be manually added back.
Teams calling. Service has been restored. If you're still not seeing your dial pad, then log out of Teams and log back in again.
Summary. This outage was inadvertently caused by vendor maintenance on our Duck ID system the evening of Monday, June 5. About 4,600 active accounts were affected. Services impacted included UOmail, Teams, and other Microsoft services, as well as the UO Service Portal, Dropbox, and possibly others. Service has been restored except as noted above.
Update on the partial outage affecting incoming email and other UO services:
Emails sent to affected accounts. During the outage (mainly on Tuesday), many emails sent to affected accounts bounced. However, other messages ended up in a limbo state within our systems. The process to deliver the latter set of emails into people's mailboxes completed around 12:30pm today (Thursday, June 8). Those messages may appear new, or may appear in date order.
Incoming email flow. Restored for most affected users early Wednesday, June 7. Restored for remaining users early Thursday morning, June 8.
Teams private channel access. If you've lost access to private Teams channels, the owners or members of those channels can restore your access. If that's not possible, then submit a ticket at Microsoft Teams support.
Teams custom tags. Affected accounts that are missing from manually created tags in Teams can be manually added back.
Teams calling. Service has been restored. If you're still not seeing your dial pad, then log out of Teams and log back in again.
Summary. This outage was inadvertently caused by vendor maintenance on our Duck ID system the evening of Monday, June 5. About 4,600 active accounts were affected. Services impacted included UOmail, Teams, and other Microsoft services, as well as the UO Service Portal, Dropbox, and possibly others. Service has been restored except as noted above.
Update on the partial outage affecting incoming email and other UO services:
Emails sent to affected accounts. During the outage (mainly on Tuesday), many emails sent to affected accounts bounced. However, other messages ended up in a limbo state within our systems. The process to deliver the latter set of emails into people's mailboxes completed at 12:21pm. Those messages may appear new, or may appear in date order.
Incoming email flow. Restored for most affected users early Wednesday, June 7. Restored for remaining users early Thursday morning, June 8.
Teams private channel access. If you've lost access to private Teams channels, the owners or members of those channels can restore your access. If that's not possible, then submit a ticket at Microsoft Teams support.
Teams custom tags. Affected accounts that are missing from manually created tags in Teams can be manually added back.
Teams calling. Service has been restored. If you're still not seeing your dial pad, then log out of Teams and log back in again.
Summary. This outage was inadvertently caused by vendor maintenance on our Duck ID system the evening of Monday, June 5. About 4,600 active accounts were affected. Services impacted included UOmail, Teams, and other Microsoft services, as well as the UO Service Portal, Dropbox, and possibly others. Service has been restored except as noted above.
Update on the partial outage affecting incoming email and other UO services:
Emails sent to affected accounts. During the outage (mainly on Tuesday), many emails sent to affected accounts bounced. However, other messages ended up in a limbo state within our systems. The process to deliver the latter set of emails into people's mailboxes completed at 12:21pm. Those messages may appear new.
Incoming email flow. Restored for most affected users early Wednesday, June 7. Restored for remaining users early Thursday morning, June 8.
Teams private channel access. If you've lost access to private Teams channels, the owners or members of those channels can restore your access. If that's not possible, then submit a ticket at Microsoft Teams support.
Teams custom tags. Affected accounts that are missing from manually created tags in Teams can be manually added back.
Teams calling. Service has been restored. If you're still not seeing your dial pad, then log out of Teams and log back in again.
Summary. This outage was inadvertently caused by vendor maintenance on our Duck ID system the evening of Monday, June 5. About 4,600 active accounts were affected. Services impacted included UOmail, Teams, and other Microsoft services, as well as the UO Service Portal, Dropbox, and possibly others. Service has been restored except as noted above.
Update on the partial outage affecting incoming email and other UO services:
Emails sent to affected accounts. During the outage (mainly on Tuesday), many emails sent to affected accounts bounced. However, other messages ended up in a limbo state within our systems. The process to deliver the latter set of emails into people's mailboxes has completed. Those messages may appear new.
Incoming email flow. Restored for most affected users early Wednesday, June 7. Restored for remaining users early Thursday morning, June 8.
Teams private channel access. If you've lost access to private Teams channels, the owners or members of those channels can restore your access. If that's not possible, then submit a ticket at Microsoft Teams support.
Teams custom tags. Affected accounts that are missing from manually created tags in Teams can be manually added back.
Teams calling. Service has been restored. If you're still not seeing your dial pad, then log out of Teams and log back in again.
Summary. This outage was inadvertently caused by vendor maintenance on our Duck ID system the evening of Monday, June 5. About 4,600 active accounts were affected. Services impacted included UOmail, Teams, and other Microsoft services, as well as the UO Service Portal, Dropbox, and possibly others. Service has been restored except as noted above.
