• All submissions to this site are governed by Second Life Project Contribution Agreement. By submitting patches and other information using this site, you acknowledge that you have read, understood, and agreed to those terms.
Issue Details (XML | Word | Printable)

Key: SVC-269
Type: Bug Bug
Status: Open Open
Priority: Major Major
Assignee: Unassigned
Reporter: Damanios Thetan
Votes: 4
Watchers: 6
Operations

If you were logged in you would be able to see more operations.
2. Second Life Service - SVC

Sending an instant message to an object using llInstantMessage will result in an email to the owner with IM->Email checked in preferences, regardless of owner's online status

Created: 04/Jun/07 05:04 PM   Updated: 22/Sep/09 11:08 AM
Return to search
Component/s: Scripts
Affects Version/s: 1.16.0, 1.20.0 Server, 1.21.0 Server, 1.22.1 Server, 1.22.2 Server, 1.22.3 Server, 1.22.4 Server, 1.23.4 Server, 1.24 Server, 1.26 Server
Fix Version/s: None

Environment:
Second Life 1.22.11 (113941) Mar 6 2009 12:50:02 (Second Life Release)
Second Life Server 1.26.2.117266
Issue Links:
Relates

Last Triaged: 22/Sep/09 11:08 AM
Linden Lab Issue ID: DEV-40329


 Description  « Hide
Reproducing the current scenario:
  • Create an object that listens for input on channel 0 (chat) and responds with llInstantMessage(); to confirm that it received a message;
  • Create another object that uses llSay(); on channel 0 (chat) and induce it to speak in the vicinity of the listening object
  • Ensure that the owner of the speaking object has IM->Email enabled in Preferences

Expected result:

The listening object responds in chat when the owner of the speaking object is in range, opens an IM tab when the owner is out of range, and emails them when they are offline.

Actual result:

The owner of the speaking object receives the llInstantMessage(); from the listening object in email, regardless of online status and/or proximity to the listening object.

Previous scenario

  • Create a script that sends a (timed) instant message to an object key, instead of an avatar key
  • Make sure the owner of the object has IM->Email switched on in prefs
  • Go offline with the specific account

Result:

IMs to the object will result in emails sent to the owner, as if the actual IMs were directed at the owner. (this is now expected behaviour)
When the owner is online, the IMs are ignored/discarded (correct behaviour)

This behaviour differs from previous versions, so it can cause major overloads of emails (spam) to people's mailboxes, as now any 'misdirected IM' results in an email, instead of being silently ignored. (the current issue is that spam occurs regardless)



 All   Comments   Change History      Sort Order: Ascending order - Click to sort in descending order
Kooky Jetaime added a comment - 14/Oct/07 12:13 PM
I'm having a similar experiance, and I'm wondering if the two are related.

When I'm offline, I am receiving emails from one of my own objects saying:
"
The object 'CoD Welcome System' in Second Life has offered you inventory.
Log in to accept to decline this inventory.
"
(Along with the object name, owner and location which is me)

When I log in, there are no pending requests, and the object is designed to offer inventory on collision_start, and I know I'm not colliding with it when I'm logged off. (Additionally, the object is programmed to ignore me.)

I don't know if these are two related issues or not.


Gigs Taggart added a comment - 15/Nov/07 03:03 PM
Can we get independent confirmation from someone else on this bug?

Damanios, can you still reproduce this in the newest version?


Kitty Barnett added a comment - 17/Apr/08 12:51 AM
Changed affects to current sim version since this is still not fixed.

wildefire walcott added a comment - 02/Jul/08 12:26 PM
I am filing a separate Jira on a problem that may be related to this issue, but I can't tell from the problem description here whether it's the same thing. It's related to object spam that looks like it's delivered by the recipient, even though it originates from objects that the recipient doesn't own on land she doesn't own.

Ashrilyn Hayashida added a comment - 04/Jul/08 05:33 PM
I have IM to email enabled.
If one of my objects sends an IM to another object I own, or to itself, I receive an IM-to-email from it, even when online.

I am online right now. I had an object run the following script, and I soon received an email because of it.

default
{
state_entry()

{ llInstantMessage(llGetKey(),"This is a IM test."); }

}

Second Life Server 1.22.4.90499
(sim: NorthStar Polaris)

The email I received:
"The object 'script test a' has sent you a message from Second Life:
This is a IM test.

= script test a is owned by Ashrilyn Hayashida"


JulioCesarMolina Kayo added a comment - 26/Oct/08 10:14 AM
I have exactly the same behaviour when my object is sending the IM to avatars. Then I got copies of the IM in my mail box when the option is checked in preferences. I am running viewer:
Second Life 1.21.5 (98701) Oct 6 2008 10:27:21 (Second Life Release Candidate)

EddyFragment Robonaught added a comment - 20/May/09 06:23 PM - edited
Forgive my impudence but is this not quite proper? Orther than sending llInstantMessage()'s to objects shouldn't work at all. Is that the bug? Could be expressed more simply I think.

llInstantMessage sends and instant message and if instant messages are sent to e mail then one should surely expect to get an e mail of any IM's right?

I would close this if I wasn't so confused.

Second Life 1.23.1 (119104) May 4 2009 17:53:10 (Second Life Release Candidate)


Imaze Rhiano added a comment - 21/Sep/09 12:09 PM
Correct behaviour: Objects should NOT be able to send messages for other objects are specified in https://wiki.secondlife.com/wiki/LlInstantMessage

"Instant Messaging has the benefit of allowing communication from an object to an avatar anywhere in the Grid. The downside is that an object cannot receive an Instant Message, therefore an avatar cannot send an Instant Message to an object. It's a one-way communication avenue."

All instant messages sended by object to another object should be completly discarded.