ICON Known Issue Details

Submit Issue Report (ICON Instructors Only)

Basic Information

Issue ID: 93	Issue Type: Bug	Report Date: 08/28/2008
Tool Type: Email	Severity: High	Resolution Date: 09/08/2008
Issue Status: Completed	Anticipated Fix Release: Unknown

Description:

[RESOLVED] ICON Email Bug

Recently we informed you of an obscure but nasty bug in ICON's email tool, related to students whose uiowa.edu email addresses had not been properly set up.

Thanks to the combined efforts of ITS Systems & Platforms and the ICON Support Team, a workaround for this bug has been implemented.

Emails sent to a group (such as classlist emails) are now correctly delivered to recipients with good addresses; if any recipients have bad addresses a "bounce" message will be returned to the sender.

Note that there are still several hundred students who have not yet set up their uiowa.edu email addresses. While this no longer triggers the bug, it does mean that they won't receive any email you send to them. Please remind your students to visit ISIS to set up their email!

-------------------------

Original announcement:

-------------------------

There is a fairly obscure but frustrating in ICON's email tool. The bug prevents delivery of mail from ICON to a class list if a single student's email address has not been set up. This affects relatively few students and instructors, but when it happens it can be very confusing.

Unfortunately, instructors cannot see which students have not set up their uiowa.edu email, and ICON does not return an error to let you know what went wrong.

The ICON team is working to resolve the bug, but in the meantime, please consider the following workarounds:

1. Add your own address to the CC: list when sending mail from ICON. If you don't receive a copy of the mail, you have probably encountered the bug.

2. Remind your students to go to ISIS (http://isis.uiowa.edu) and set up their uiowa.edu email if they have not already done so.

3. Consider sending class emails either via your desktop email client or via OSIRIS for now.

We have communicated this issue to the vendor, and are working with them to resolve this bug.

Issue Responses

No responses have been published for this issue.