The Alarm tab "Procedure" text field is run correctly at alarm time. But, it is run incorrectly when tested with the "Execute" button. The tool tip for the "Execute" button is "Test this alarm by raising it now." But, this doesn't properly run the Alarm Procedure component of the alarm. For example, my procedure command is /bin/mailx -s "subject" <my username> </dev/null This works fine at the scheduled alarm time, but when I click the "Execute" button, I see this in .xsession-errors: Heirloom Mail version 12.5 7/5/10. Type ? for help. "/var/spool/mail/<my username>": 1 message > 1 Mail System Internal Mon Jul 18 10:35 13/572 "DON'T DELETE THIS MES" Held 1 message in /var/spool/mail/<my username> Somehow, mailx is being run without any options, which causes it to open my mailbox for editing. I spent a while trying to figure out what was wrong with the command because the "Execute" button wasn't working, when, in fact, the command is fine. It's very convenient to be able to test alarms; good feature. But, this part is broken.
Yes, I can reproduce this.
This is now fixed in 4.8.1.9 available in git. Indeed parameters wer missing from the test (=execute) procedure alarm.
Awesome. Many thanks.
Fix in 4.8.2