-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Content filter to prevent mail text from being stripped #61
Comments
hello @nicolasguenther thank you for opening an issue here. I'll take a look into this. Is this only a problem with markdown interpreted characters? |
Thanks @c-seeger. |
Example mail body 1:
Result: Non printable characters are shown in the mattermost channe Example mail body 2:
Result: Second line is stripped and not displayed in mattermost channel. Note: There is a space character at the end of the first line. |
@nicolasguenther i actually can't reproduce the issue both mail bodys work correctly on the latest build. |
Hi, I also see some text stripped from email, for example this email (in Plain Text Mode in Gmail):
renders like this in Mattermost:
In the mail2most config, we use It seems like the lines after a Any idea how to fix it? Thanks |
Thanks @Philmod for bringing this up. Interesting behavior, I'll take a look on this and check if I can reproduce this. |
Hi @c-seeger, any update on this bug? |
Hey @c-seeger, any update on this issue? |
hello @Philmod sorry not atm will take a look as soon as i find some time |
When using mail2most i encounter problems where mail content is stripped when it contains certain combinations of characters which are interpreted as markdown (colon, hyphen, pipe etc.).
I propose a new setting for a profile that enables me to specify certain characters which will be filtered out before posting the text in a mattermost channel.
An alternative would be to start/end escaping using the prefix/suffix settings. But it seems mattermost is lacking support for such an escape block. Using "```" blocks doesn't fix the problem for me.
The text was updated successfully, but these errors were encountered: