Interesting issue with llEmail

I recently updated scripts throughout my places using llRemoteLoadScriptPin and llGiveInventory. The update went fine, but one of the scripts that is supposed to mail to an external e-mail is, instead, sending the e-mail to the owner of the door. Their external address, which is not in the script anywhere.

So far, this is in the case where the script was loaded remotely. The original still sends, as it's supposed to, to the proper external e-mail.

I'm puzzled by this. Only thing I've found in the Jira that sounds plausible is a unicode issue, but that doesn't make a lot of sense given that the e-mail DOES get out, just not to the e-mail address it's supposed to go to.

Any ideas as to where I could look?

sure that the email isn't getting out at all and the 'owner' didn't just receive an automated SL message about receiving inventory or some such?

No, the e-mails sent by the device are formatted. The e-mail received by them is formatted correctly.

The problem seems to have cleared itself up. Which is interesting too.

i had an interesting and similar issue with instant message. i had a welcome mat at my store that used collision. it was supposed to instant message the avatar it detects. but when it got hit with a physical object, it instant messaged me...sorta. i was logged in, but the instant message was sent to my email instead, and it referred to me as Tosser 1

Sounds like there's a "save email" step in state_entry (maybe a read-notecard/read object description)... remember that when you save an object, and then re-rez it, or if you save the object and then sell it.. state_entry is only triggered if the scripts get reset.

That's why ,amy times, people create a "startup" or "init" function, dump all the initializations into it, and then trigger init on_rez, at state_entry, and at other useful times (like change & CHANGE_INVENTORY, CHANGE_OWNER, etc).

A dirty workaround, is to just slap a llResetScript into those other events. (on rez, change, etc).. which would then re-set ALL the variables, and then trigger state_entry.