Closed
Bug 470549
Opened 17 years ago
Closed 16 years ago
quoted-printable content-transfer-encoding breaks lightning
Categories
(Calendar :: E-mail based Scheduling (iTIP/iMIP), defect)
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: sozt65, Unassigned)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.5) Gecko/2008120122 Firefox/3.0.5
Build Identifier: Thunderbird 2.0.0.18 (20081105) + Lightning 0.9 (2008091719)
If an email message has a text/calendar type attachment with a Content-Transfer-Encoding of quoted-printable, Lightning does not recognize it as an invite and offer the options of accepting or declining. In fact, the first time the message opened it shows as a blank message. Moving away from it coming back displays message's text portion and shows the calendar attachment as a ICS attachment. But, still no options to accept or decline. Specifically, these messages are created with the Bynari Insight Connector 3.1.8-iCal plugin for outlook.
Changing the content transfer encoding to 8bit makes lightning work again.
Reproducible: Always
Steps to Reproduce:
1. Send an invite from Bynari Insight Connector with iCal
2. Open the invite message in Thunderbird + Lightning
3.
Actual Results:
Blank message screen.
Expected Results:
The text portion of the message should be shown and accept decline buttons for the invite should be available.
Updated•17 years ago
|
Component: Lightning Only → E-mail based Scheduling (iTIP/iMIP)
QA Contact: lightning → email-scheduling
Comment 1•16 years ago
|
||
Does this still happen with the latest 1.0b2pre nightlies?
| Reporter | ||
Comment 2•16 years ago
|
||
I don't know. I don't use Bynari anymore.
Comment 3•16 years ago
|
||
Selcuk, would it be possible for you to install Bynari to test this?
Comment 4•16 years ago
|
||
no response to questions in previous comment, so => incomplete.
if you still see the problem in the newest version, please comment in the bug.
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•