Do I understand correctly that you had 2 rules for each entry? One that sends to the customer and one to the support address? And after the change both are not set to the support address? Why not make just one rule and send to a team, team with 2 members being the customer and support. If the address of one of them changes you just need to change the address of that "person".
dirk. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Barry George Sent: Fri Sep 19 7:57 PM To: Salive List Subject: [SA-list] People email vs. Global change SMTP send to: Here's a pickle, I've set up a customer to get email status alerts for his host checks, using the "People" function. Customer has two emails, one a paging service different times of the day etc. All's good, customer gets emails. Then using Global change Primary SMTP send to: function and make changes to all host because of a local primary support address change. That customers host entry is over-written. Ok by design, fair enough, but is there any way dirk to protect those "unique" instances? Otherwise its resetting all the unique hosts over again. Or could I possibly be missing another option..... :-) Thanks Barry
<<attachment: winmail.dat>>
