In the "old days" of Pegasus running with the NLM version of Mercury, the option was a simple click and dialogue and it worked very well.
Nowdays, it takes a few more steps:
Option 1: If you run Mercury with Pegasus, then create your message as Pegasus would in the .101 file that gets written to Mercury's queue folder. Then write a batch file that copies the .101 file to the Mercury queue when called. Create a scheduled task in Windows Scheduler to call the given batch file at the appropriate time.
Option 2: If Mercury queues are not an option, then use Windows Scheduler to call Pegasus, using command line options to create and send a given message at a given time. See the Help pages to find the switches to use.
Perhaps, when David has coded some of the more pressing features into Mercury and Pegasus, the delayed mailing feature (or whatever it was called) might make a reappearance in the Win32 platform.
<p>In the "old days" of Pegasus running with the NLM version of Mercury, the option was a simple click and dialogue and it worked very well.</p><p>Nowdays, it takes a few more steps: </p><p>Option 1: If you run Mercury with Pegasus, then create your message as Pegasus would in the .101 file that gets written to Mercury's queue folder. Then write a batch file that copies the .101 file to the Mercury queue when called. Create a scheduled task in Windows Scheduler to call the given batch file at the appropriate time.</p><p>Option 2: If Mercury queues are&nbsp; not an option, then use Windows Scheduler to call Pegasus, using command line options to create and send a given message at a given time. See the Help pages to find the switches to use.</p><p>Perhaps, when David has coded some of the more pressing features into Mercury and Pegasus, the delayed mailing feature (or whatever it was called) might make a reappearance in the Win32 platform.
&nbsp;</p>