Is Object Email Currently Down? (2/20/08)

heyas;

not exactly a scripting question, per se, but you guys would be the ones to notice this.... i have a mailbox with remote drop boxes it communicates with via email... for the past two weeks.... they haven't been communicating, that i can tell.


as an ancillary... anybody got a routine that will check if an object is getting its email? or has email or... something? its all pretty black-box to me right now. (yes, i code stuff beyond my understanding.)

thanks, guys!

Object email is working, far as I know.

Check UUID's (object keys) for the objects which receive email. If you've re-rezzed or drag-copied one of those, the UUID has changed. The UUID is the email address, so if it changes, then you need to make sure to adjust the sender scripts so they 'know' the new email address.

Another problem could be a script that has crashed, usually because it has run out of memory. If you're sure it's safe to reset the scripts (and if permissions allow it), then reset the scripts and re-test your system.

As for a check routine... that's easy if you're able to modify the scripts or objects. In the receiver, add a line immediately below your email() event:

email(string time, string address, string subj, string message, integer num_left)
{
llOwnerSay(time + "\n" + address + "\n" + subj + "\n" + message);
... }

As far as I can tell, E-mail out of sim has been wonky at best.
When used inside the same sim, e-mail works perfectly.
I found a jira entry about it, but they said the issue has been resolved. P_P
Looks like someone needs to start up a new one?

heyas;

i made the objects/scripts, and they are pretty careful about registering with the right uuid. i even cleared the registry in the main and re-registered the remote.

i'll test one in the same sim... come to think of it, that's where i HAVE been testing them. crap. ::sigh::

thanks guys!



...wait...

they're sending EMAIL. y'know? smtp? whatever? its not going through sl. how the dip could it matter if they're in the same sim or not???

http://www.lslwiki.net/lslwiki/wakka.php?wakka=llEmail

Read @ the bottom of what kelley Linden has to say about how llEmail is handled.
I guess that it has trouble trying to leave the machine that it is on and getting to the other machine hosting the target object.

There doesn't seem to be any error handling with the mail, so if there are any temporary network issues, llEmail appears to silently fail sim-to-sim. This has been a problem for about a year, actually, but gets worse than normal once in a while. A lot of folks have been moving away from llEmail-dependent vending systems, for example.

oh, i see.

so, basically... to do region to region email effectively, i'd pretty much have to.... say, create a free email account, have object one email me at my account, then somehow have the email account automatically forward the email to the other object?

bah!


btw, yesterday, i had my remote email its UUID back to the main again, and when it did, THEN it apparently got the email to send ME its contents (or at least one of those emails), and so it sent them to me.



then again, i've noticed that pretending to hit group ims with a plunger seemed to make clogged messages go through. no, really!


okay, thanks guys.

:\ can confirm; this will happen once in awhile if you use email to network boxes. this week has been especially bad with the server updates going on; i've had the worst outages yet this week (and yeah, this has been a prob especially for a year now). usually the best solution is for a landowner on the problem sim to request a sim reset.

p.s. as i once read it, it seems that using other networking hooks (umm, what's it called, xhp or something? lol) can have the same prob once in a while? how much better/worse has it been to using other networking methods?

please vote for some attention to this bug from ll, on the jira.

http://jira.secondlife.com/browse/SVC-1453



since llemail is the ONLY way two objects can communicate with each other in different sims. it would be nice if it were actually reliable, y'know?

thank you.