App issues #90
Description
Hi!
I'm interested in having the mailrise app as a middleware for all applications and manage there all the accesses to other notification systems, but I'm encountering some issues. I have multiple questions about the app:
- When using the wildcard "@" with sendgrid:// or mailto:// (mailtos://) connections the "${to}" field is not setup properly and thus cannot forward the email. Could you add the feature for the "${to}" variable to be used also in the "urls" config section? This would make the app much more dynamic
- I have an email address for which I want to use a different notification connection, but the email has a dot "." in the string. How to add the full email (a workaround is to use the wildcard sign, but that might filter other emails too)?
- Could you add a feature to relay / modify / template the email notification based on the source app sending the notification instead of the recipient? (usage: I don't want that all source apps send the same subject string)
- The source email received in the mailrise app is most probably formatted in HTML and I didn't find any documentation that the relaying connection has to convert the input to the format "text" (using tgram:// I HAD to use "?format=text), if not there were errors in the app. Why don't you use by default the HTML type of source, thus eliminating the option to set the "mailrise.body_format: html" option in the config?
Additionally, you could add in the documentation for debugging purposes to use the following docker-compose command:
entrypoint: ["mailrise","-vv","/etc/mailrise.conf"]
Thanks for your answers!