It can be an advantage to have a 'Swiss Army Knife' rather than a drawer full of knives & forks [:D]

Hi

Is it possible to get Mercury32 to run a specific program AFTER email has been delivered ??

 
Thanks 

Delivered where - a server? a mailbox? You may be able to do that with a policy or a filter.

Perhaps if you describe what you want to do in more detail, there may be more suggestions.

Sorry should have explained more.

Inbound email -> Once it's been delivered to the correct user I would like to run a script.
But only after it as been delivered to the Internal user.

Thanks
 

[quote user="tomt"]

Sorry should have explained more.

Inbound email -> Once it's been delivered to the correct user I would like to run a script.
But only after it as been delivered to the Internal user.

Thanks
 

[/quote]

Can't see any way at all to do this in Mercury/32.  If you are using WinPMail there is a "Run a program" filter action that will do this for you. 

I have a rule that I setup to check email for a certain subject.  If the message comes in it will reboot the server.  This message is delivered to the mailbox before the reboot command runs.

[quote user="Slab"]I have a rule that I setup to check email for a certain subject.  If the message comes in it will reboot the server.  This message is delivered to the mailbox before the reboot command runs.[/quote]

Not sure why you could not do this with a policy; the policy would pass the message to your application that would run the command to re-boot the system.  That said, one of the beta testers Frank Fesevur <omega@fesevur.com> has just developed a little daemon called MercExec to do just that via an alias.   I believe it will be available to the larger community as soon as it's cleaned up a bit.

Thanks.

Hopefully we'll get to play with MercExec soon [:D]

MercExec can be found at  http://www.fesevur.com/content/view/10/33/

Please let me know what you think it.

I don't mean to "rain on your parade" but doesn't this just duplicate the functionality of the "Run a program" filtering rule?

I have for some time had rules to remotely command my server via email. They trigger on receipt of an email to the 'give me an order' address, check for an allowed From: address, check for an authentication string in the headers &/or subject, then call batch or cygwin scripts to reboot, start/stop services (FTP, VNC, SSH etc.) or anything else, depending on the command(s) given in the body.

It is funny you bring this up. I was not aware of this filter action, and apparently I was not the only one. Thomas didn't mention it here in this thread, and on the beta-testers mailing list nobody mentioned it either.

My daemon is capable of doing more things then just run a program. It can also send you the listing of a directory or send you a specified file. And (as mentioned in the ReadMe.pdf in the archive) more things are planned as well.

But you are right, with filters a lot of this can be done as well. [:S]

[quote user="Frank"] It is funny you bring this up. I was not aware of this filter action, and apparently I was not the only one. Thomas didn't mention it here in this thread, and on the beta-testers mailing list nobody mentioned it either.[/quote]

It was mentioned earlier in relation to the original question - running a program *after* a message has been delivered to a mailbox.

As I understand, no filter rule, policy or daemon in Mercury operates that late in the processing cycle.

[quote]My daemon is capable of doing more things then just run a program. It can also send you the listing of a directory or send you a specified file. And (as mentioned in the ReadMe.pdf in the archive) more things are planned as well.[/quote]

It looks very capable and I'm going to try it out.  :)