Message Filter auto reply using template with attachment uses incorrect formatting displays content as html garbage
Categories
(Thunderbird :: Filters, defect)
Tracking
(Not tracked)
People
(Reporter: anjeyelf, Unassigned)
Details
Attachments
(1 file)
|
481.51 KB,
image/jpeg
|
Details |
102.14.0 and 117.0b3.jpg
Windows 10 OS
This bug is still operating in versions 102.14.0, 115.1.0 and in beta 117.0b3
I'm creating this as a new report as the old one bug 326181 is 18 years old.
I know that bug is still active and Magnus says it does not technically need a new report, but I feel this bug needs to be reset as a beta supernova bug.
Users use auto reply, creating a template and choose to include an attachment.
Attachment may be a form for completion etc.
A filter performs the auto reply.
- Compose mesage in Write
- attach file
- save as template.
- Create Message Filter to reply using the template.
- Send an email from another account to trigger filter
- Filter works and email reply is sent.
- Sending options are to send using Both html and Plain text.
The saved copy of Sent email is showing the formatting error.
The received email is identical to the sent email.
Expected
Filter to operate and use Template
Sent copy to show the use of template with correct formatting - attachment to be shown as an attachment.
REceived copy to show correct formatting and attachmnet shown as an attachment.
Actual Result
Filter operated and used Template
Sent copy was incorrect formatting displaying html and attachment seemed to entered as plain text with bad formatting.
REceived copy identical to sent copy.
It is basically garbage to the viewer.
The image I posted shows example of problem.
Template and Message Filter
Example of email sent/received content as user sees it
It's source view.
The new supernova needs to have this fixed.
In Support Forum this problem is still being reported.
https://support.mozilla.org/en-US/questions/1420961
Using version 1.115.0, I'm seeing the same thing. A chunk of HTML seems to be missing at the end of the headers and before the body. So my html body appears to be concatenated with the end of the autocrypt header.
This bug causes issues even with plain text templates with no attachments.
The plain text template may be saved, e.g., using
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
while after the filter is run and auto-reply sent, this auto-reply is encoded using base64, but the salient bit in the message source says Content-Transfer-Encoding: 7bit (instead of Content-Transfer-Encoding: base64).
That is, the recipient sees a base64 garbage instead of the actual plain text message.
Description
•