Welcome to the Second Life Forums Archive

These forums are CLOSED. Please visit the new forums HERE

Emails and inworld objects.

PC Andrews
Registered User
Join date: 2 Jul 2005
Posts: 2
08-14-2007 23:39
Is forwarding email not allowed to objects inworld?

I getting all the time this error email.

**************************************************************************
This is the mail system at host data.agni.lindenlab.com.

I'm sorry to have to inform you that your message could not
be delivered to one or more recipients. It's attached below.

For further assistance, please send mail to postmaster.

If you do so, please include this problem report. You can
delete your own text from the attached returned message.

The mail system

<mailtolsl@data.agni.lindenlab.com> (expanded from
<110fe7cfe-5242-9f26-a6dc-17852bfbf675@lsl.secondlife.com>;): Command died
with status 100: "/opt/linden/indra/tools/mailglue/mailglue --grid=agni
--system=lsl". Command output: Your email must be addressed to an object
key or an IM session identifier.

Final-Recipient: rfc822; [email]mailtolsl@data.agni.lindenlab.com[/email]
Original-Recipient: rfc822;110fe7cfe-5242-9f26-a6dc-17852bfbf675@lsl.secondlife.com
Action: failed
Status: 5.3.0
Diagnostic-Code: x-unix; Your email must be addressed to an object key or an IM
session identifier.

*************************************************************************

this is the server im using:

**************************************************************************
default
{
state_entry()
{
llSetTimerEvent(2);
}

timer()
{
llGetNextEmail("", "";);
}

email(string time, string address, string subj, string message, integer num_left)
{
llSay(0, message);
}
}
**************************************************************************
Jillian Callahan
Rotary-winged Neko Girl
Join date: 24 Jun 2004
Posts: 3,766
08-14-2007 23:54
Assuming "110fe7cfe-5242-9f26-a6dc-17852bfbf675" is the UUID to the object in question...

It may just be the troubles SL has been having lately - I get that message occasionally too on objects that have been working fine to that point, and do again a bit later.

Try making a new prim and seeing if that eliviates it. Double check the UUID, too.
PC Andrews
Registered User
Join date: 2 Jul 2005
Posts: 2
more...
08-15-2007 01:21
110fe7cfe-5242-9f26-a6dc-17852bfbf675" is the UUID to the object in question, yes.

i tryed a lot of times with differents objects.
always checking and rechecking the keys.

****
what im trying to do is this:

object A: send a email to a gmail account.(this work, im getting the emails from the obj)

gmail account: automatic forward to object b.

object b: email receiver.


i also tryed:

object A: (sender and receiver) send a email to a gmail account.

gmail account: automatic forward to object A.

object A: email receiver.


neither of those worked.


////
i tryed too:

object A: send a email to a gmail account.

gmail account: forward and reply by clicking manually the buttons of forward and reply to object A.

object b: email receiver.


and...


object A: (sender and receiver) send a email to a gmail account.

gmail account: forward and reply manually.

object A: email receiver.


and in this 4 cases worked perfectly!


****
finally i tryed:

object A: send email to object B (without gmail acount).

this worked too.


////
Seems like there is a problem with the auto forward. Maybe a security filter?

I tryed it with a yahoo acount too, with the same results.

Also I set the auto forward to my personal email acount, to check if there was something weird in the fowarded email, and there is nothing weird, just a clean email, like if it was sent to my personal acount and not to the acount im using for this.

tyvm!!!
Masakazu Kojima
ケロ
Join date: 23 Apr 2004
Posts: 232
08-15-2007 05:35
/54/0a/172787/1.html
/54/27/87789/1.html

objdns is not taking new registrations now, but the information still applies. Basically, Second Life relies on the recipient address on the message envelope, and not the address it is actually delivered to. So, when it's forwarded from gmail, it's kind of like sending it to the gmail address and BCC'ing the object, and SL has no idea where it's supposed to go.

As it turns out, this is a bad idea anyway, because external emails have to get routed back into SL through a single server which fails pretty frequently, and support is completely impossible to get. Recently the email server was refusing/hanging connections for nearly 10 days and I didn't get a response to my support request until a month later (with the 'high priority' concierge-level support). It is a much better idea to use something like httpdb ( http://w-hat.com/httpdb ) or a file on your own web host to fetch the target object's key with llHTTPRequest, and email it from the object directly - this avoids the broken incoming mail server, and possibly the email system entirely.