sending to multiple email addresses

[Andytec]

How can I send the same data to multiple email addresses on an alarm event without having to create the same macros for each email address ?

Thanks

[Tuicemen]

AHP doesn't allow multi address selection.
However you can still send to multiple users using one macro.
there are a couple of ways to do this:
1:Drag  the email notification into the macro command for each recipient.

2:In the email address type the first recipient followed by a ; then the next address

Note: this works for sending pictures to multiple addresses too!

[Andytec]

Thanks very much - that works ! - great. Any idea why I get two emails to each address for each email action in the macro.

[Tuicemen]

It may have something to do with your email settings in AHP I have mine set to send using SMTP.

[Noam]

Thanks very much - that works ! - great. Any idea why I get two emails to each address for each email action in the macro.

Is AHP open when you are doing this? I'm pretty sure that as long as the PC is on, and the X10nets service is running, AHP no longer needs to be open.
HOWEVER, there is a bug that got introduced a few version ago. This bug seems to run all macro (and timer) actions twice, BEFORE AHP is opened for the first time after the Pc is booted/rebooted, or the x10nets service is started/restarted.

I don't know if that's the explanation for your symptoms, but if you are booting (or rebooting) the Pc, and NOT opening AHP, then you might see this behavior. The fix is as simple as opening AHP after you boot or reboot the PC. You can then close it right away, if you want. The act of opening it stops the duplicate actions. I'm not sure why it is happening, but it was reported to the developers already (and it is on the Bug List - located here: http://forums.x10.com/index.php?topic=22373.0)

[Andytec]

SMPT _ yes thats what I have set up

I only have AHP running on the laptop. I always open AHP and leave it open after start-up

a

[Noam]

Are other commands in the macro running twice?
There is a bug in the list (that I'd forgotten about) where macros triggered by security events run twice.