mirror of
https://github.com/cypht-org/cypht.git
synced 2026-04-25 04:56:03 +03:00
[GH-ISSUE #308] 🐛 Reply to a html message will not be displayed #268
Labels
No labels
2fa
I18N
PGP
Security
Security
account
advanced_search
advanced_search
announcement
api_login
authentication
awaiting feedback
blocker
bug
bug
bug
calendar
config
contacts
core
core
devops
docker
docs
duplicate
dynamic_login
enhancement
epic
feature
feeds
framework
github
github
gmail_contacts
good first issue
help wanted
history
history
imap
imap_folders
inline_message
installation
keyboard_shortcuts
keyboard_shortcuts
ldap_contacts
mobile
need-ssh-access
new module set
nux
pop3
profiles
pull-request
question
refactor
release
research
saved_searches
smtp
strategic
tags
tests
themes
website
wordpress
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/cypht#268
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @ulfgebhardt on GitHub (Nov 30, 2018).
Original GitHub issue: https://github.com/cypht-org/cypht/issues/308
Originally assigned to: @jasonmunro on GitHub.
🐛 Bugreport
This describes a very rare bug, which might be due to a problem in the sending client.
If a

Personreplies to a HTML EMail, the response is in some cases not visible.If you press reply, the Response becomes visible

Raw Mail:
base64 decoded and shortened content
Notes:
The HTML does not contain then
<p dir="ltr">..., but starts with the<table border="0" cellpadding="0"...which is the first tag in thebodytag within the EMailVersion & Environment
Rev: [
db4e50c7e0]OS: [Chrome]
Configuration: [using Inline-View]
@jasonmunro commented on GitHub (Nov 30, 2018):
@ulfgebhardt could you either send me or post the full raw E-mail so I can drop it in a maildir and run a local test? Thanks!
@ulfgebhardt commented on GitHub (Nov 30, 2018):
I am afraid that i cannot give you this specific email, since the author is complaining about how we did not respect his privacy by sending him a newsletter :(. Therefore i would not like to share this specific email with you - just in case some test goes wrong and he receives an email, hell will break lose.
I will try to recreate the issue myself tho and provide the appropriate data once i successfully did that.
Thank you for developing this awesome software <3
@jasonmunro commented on GitHub (Nov 30, 2018):
@ulfgebhardt no problem, I totally understand. I rigged up a test with what you posted and can reproduce, though I'm not sure how to fix it. HTMLPurifier is removing the content outside the html tags it would seem. What is really odd is that if I remove the closing body tag before filtering it - it works!
@ulfgebhardt commented on GitHub (Dec 1, 2018):
Text version displaying Text:

HTML version missing Text:

Reply to HTML using HTML Editor - no Text either:

I set the client to HTML EMails for this Test. If you reply to the HTML-Version of the EMail and you use HTML as EMail format the original Message is never displayed
Steps i used to reproduce this:
This is not a major Issue - This occurred with someone using a broken EMail-Client as it seems.
I am just reporting this in case you find an easy way to fix it. It is not a problem for me.
If the EMail contains HTML only and the EMail Client is set to HTML the Response can not be displayed in any way.
If you don't want to fix this/can't due to Security Limitations etc. feel free to close this. Just a report what I found ;-).
<3
@jasonmunro commented on GitHub (Dec 1, 2018):
Did some more testing on this (and while I was at it made it easier to rig up manual CLI tests). This behavior in HTMLPurifier is caused by content outside a body tag (regardless of an html tag). Interestingly if we remove the closing body tag - content outside the body is no longer discarded.
Output:
We don't want body or html tags in the final output anyway, and I don't see any reason not to remove the closing body tag to make this work better. Yes the format of the message HTML is obviously bad, but we should try to work around that as much as we can.
@jasonmunro commented on GitHub (Dec 1, 2018):
fix is pushed! :)
@ulfgebhardt commented on GitHub (Dec 2, 2018):
confirming fix