-
Notifications
You must be signed in to change notification settings - Fork 39
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
Filtering options #1
Comments
I'm curious: How badly does Matrix mangle the HTML? I wonder if it merits filing an upstream bug with Apprise. As to filtering content, I have a more general solution in mind. How about allowing users to specify template strings to construct the title and body with? This is how they would look assuming the current behavior: configs:
my_matrix:
urls:
- matrix://whatever
mailrise:
title_template: "$subject ($from)"
body_template: "$content" In your case, you could specify |
Hi, So you see the whole HTML code in the message mailrise is forwarding. The solution by using template strings would be nice. Stripping the HTML markup is unnecessary I think. If you have some really fancy HTML mail, the stripping would not be able to make the mail/message readable. |
According to the developer docs, Apprise is supposed to "do the right thing" if it receives HTML or Markdown for a service that only supports plain text:
In my opinion that should include stripping any markup, but Apprise clearly isn't doing that for us. 🤷 I'll leave it to upstream to implement that if there is demand for it. |
Template strings are now implemented and documented! |
Hi,
really great project!
I have some applications which sends HTML encoded mails to mailrise.
Sadly matrix is not able to output the content correct. So I get some random gibbish in the notification.
Would it be possible to only pass through the subject of the mail? Most of the informations are in there so
it's okay when i don't get the body of the message. I think this solution is way easier then removing the HTML content.
The text was updated successfully, but these errors were encountered: