Uploaded image for project: 'Sakai'
  1. Sakai
  2. SAK-40684

Email Archive: Sending an email with weird fonts may fail and archive blank message with no sender

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: OPEN
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 10.8 [Tentative], 11.4, 11.5 [Tentative], 12.0, 12.1, 12.2, 12.3, 12.4, 19.0
    • Fix Version/s: None
    • Component/s: Email Archive
    • Labels:
    • Environment:
      https://trunk-mysql.nightly.sakaiproject.org/portal/
      Windows 10 Chrome Version 69.0.3497.100 (Official Build) (64-bit)
    • Test Plan:
      Hide

      To reproduce:

      1. Open up the Word document I've attached here: emailsymboltest.docx and copy the content from it.
      2. In Microsoft Outlook (or another email client that is capable of using the offending Segoe UI Symbol font), open a new email and paste the content with the problematic symbols into your new email (make sure they have not been converted to images - they're only a problem when they are coming through as a font).  Note: Not all symbols generated by fonts are problematic!  You need to be sure to include at least one offending symbol for the email to fail.
      3. Send the message to a site where you have permission to send email.
      4. Go to the site and check the Email Archive. You'll see a blank message with no sender (the blank message will not be received by anyone in the site).
      5. Now copy just the content from the Word document including This one seems ok: .
      6. Paste the content in a new email and send it to the site.  Note that it goes through with no issue.
      Show
      To reproduce: Open up the Word document I've attached here:  emailsymboltest.docx and copy the content from it. In Microsoft Outlook (or another email client that is capable of using the offending Segoe UI Symbol font), open a new email and paste the content with the problematic symbols into your new email (make sure they have not been converted to images - they're only a problem when they are coming through as a font).   Note: Not all symbols generated by fonts are problematic!  You need to be sure to include at least one offending symbol for the email to fail. Send the message to a site where you have permission to send email. Go to the site and check the Email Archive . You'll see a blank message with no sender (the blank message will not be received by anyone in the site). Now copy just the content from the Word document including  This one seems ok: . Paste the content in a new email and send it to the site.  Note that it goes through with no issue.

      Description

      Issue: If certain special characters generated by fonts (e.g. some Microsoft Office emojis from the font called Segoe UI Symbol) are inserted into an email, the email will not send correctly to Email Archive. Instead, the email archive will register a blank message with the subject: No subject and no sender name shown in the From column.

      Email Archive should ignore problematic characters and strip them out of messages (possibly replace them with an indication that something was removed) rather than returning the no subject, no sender semi-silent failure that users see currently.

      At least 10 users at UVA have experienced this issue over the past couple years, with three this month, perhaps due to a general increase in the use of emoticons.

        Gliffy Diagrams

          Zeplin

            Attachments

              Issue Links

                Activity

                  People

                  Assignee:
                  maintenanceteam Core Team
                  Reporter:
                  rainribbon Tiffany Stull
                  Votes:
                  1 Vote for this issue
                  Watchers:
                  5 Start watching this issue

                    Dates

                    Created:
                    Updated:

                      Git Integration