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
Customizable Mail Notification #46
Comments
Good idea👍 This feature is not on the top of priority list, but will get implemented. |
Added in 0616a68 :) This allows you to set the mail message in the config section. This will get released in the next release. |
Wow, that was pretty quick for "not on top of the priority list". Thank you very much 😊. |
Sorry for the late reply, I just had time to test this feature (which works great btw) but I noticed that it would be quite handy to be able to customize the subject of the mail notification too. |
Ah yeah sure, completely forgot that. I've added another config variable cabaee5. I don't release this at the moment because the config table gets now really messy with so many configuration options. I'll officially release this when I've optimized the config page #60 . But I've made a Docker image for you where I already added the subject config variable: |
Nice, thank you very much! |
Added in v0.5.0 :) |
Yeah but the problem is that for some reason the build pipeline takes 1 hour. Could you try to pull again? |
Just pulled again, the |
Right now the name it uses as sender is Also since we already have nice variable like {shareUrl}. Can we please also add {desc} (for the description of share) and {fileList} of the list of files and sizes? And {expires} could show when it would expire. This would bring it on parity with WeTransfer sent e-mails even more I believe. And this way you could personalize the e-mail subject even more by having the {desc} in it, for example. |
Hey,
really love pingvin and the feature to send mail notifications for shares.
Any chance we could define that notification message ourselves in a text box or something?
The text was updated successfully, but these errors were encountered: