I tried to set the Alarm Procedure for an event to something like: /usr/bin/sendmail some@address.com < /path/to/somemessage.html This did not work, because only the "/usr/bin/sendmail" part was being run. When looking at ~/.local/share/orage/orage.ics, I see that the Alarm procedure has been placed in the saved event as follows: ACTION:PROCEDURE ATTACH:/usr/sbin/sendmail DESCRIPTION: some@address.com < /path/to/somemessage.html For some reason, the "Description" part is not passed to /usr/sbin/sendmail. I get around this easily by writing a shell script, but I wasn't sure if the "Description" part was really supposed to contain parts of the Alarm Procedure to be run, so I thought I would submit a bug. Thank you.
Yes, the format is as it should be. The problem is that I am using simple g_spawn_async function, which is not able to use standard input redirection (<). I believe you do get the email? but it is empty?
I was not able to find a quick fix for this. Patches welcomed. The problem is handling redirection for standard input: mail -s koe first.last@address < file_tosend.txt How to get mail to read the file. I will document this BUG as a limitation as first aid.
Fixed in Orage 4.5.13.9 revision 27355. Replaced g_spawn_async by linux system, which can handle redirection.
fixed in 4.6.0