incoming email interface incorrectly decodes RFC 2047 non-ASCII subject
Bug #305051 reported by
Anders Kaseorg
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Triaged
|
Low
|
Unassigned | ||
Bug Description
I recently reported bug #305047 by email to <email address hidden>, with the subject
[patch] linux-restricte
(note the Unicode apostrophe). My email client correctly encoded the subject according to RFC 2047:
Subject: [patch] linux-restricte
on Jaunty
However, this was incorrectly parsed by Malone as
[patch] linux-restricte
which is missing some spaces. (I then manually corrected the bug title; see the bug activity log.)
Revision history for this message
| Curtis Hovey (sinzui) wrote | #1 |
| affects: | malone → launchpad-foundations |
| Changed in launchpad-foundations: | |
| importance: | Undecided → Low |
| status: | New → Triaged |
| tags: | added: email |
| summary: |
- Malone email interface incorrectly decodes RFC 2047 non-ASCII subject + incoming email interface incorrectly decodes RFC 2047 non-ASCII subject |
To post a comment you must log in.
This problem is well below Launchpad and may be in Zope.