From Second Life Wiki
Jump to: navigation, search


Function: llEmail( string address, string subject, string message );

Sends an email to address with subject and message.

• string address
• string subject
• string message

The entire message (including the address, subject and other miscellaneous fields) can't be longer than 4096 bytes combined.


The message is prefixed with information about the prim sending the email.

Template Example
Object-Name: *prim*
Region: *simname* (*simpos.x*, *simpos.y*)
Local-Position: (*primpos.x*, *primpos.y*, *primpos.z*)

Object-Name: Object
Region: Gibson (254976, 256000)
Local-Position: (117, 129, 50)

The real message starts here.


  • This function causes the script to sleep for 20.0 seconds.
  • If you're sending to the object owner, prefer the llTargetedEmail method
  • There is a limit to the number of email messages an object can send in a given amount of time.
  • There is a limit of 500 messages from a single agent's objects in a one hour period.
  • The 4096 byte size limit includes the subject line and automatically added text. The practical maximum body size is approximately 3600 bytes.
  • (Sept-2008) The Email Throttle was modified slightly, Per Prospero Linden's comments: "there has long been a throttle that makes a single script sleep for 20 seconds after sending an email. The new throttle is per user... some were using many, many different scripts to send spam. (the new throttle applies) when the destination is outside of Second Life. I know that messages within the same region were not throttled (beyond the 20-second delay), and I *believe* that messages between different sims were not throttled (between the 20-second delay)."
  • Due to the bug SVC-23 (present since 2005), objects may stop receiving emails completely until either the region is restarted or the object crosses a region boundary (resetting the script doesn't help). Emails sent may eventually be received after a restart/region-cross. Hence, don't rely on this function for reliable inter-region messaging.
  • Due to the bug SVC-391 llEmail will silently fail (no mail will arrive) when non-ascii characters are present in the subject. However, non-ascii characters in the message body will be replaced by "?".

Important Issues

~ All Issues ~ Search JIRA for related Bugs
   llEmail and llHTTPRequest do not handle non-ASCII characters
   Include "Content-Type: text/plain; charset=UTF-8" header in the messages forwarded from second life.
   llEmails to objects not in the same region arrive without a body or do not arrive at all.


string emailAddress = "somebody@example.com";
string emailHeader = "Someone touched me!";
    touch_start(integer num_detected)
        // llSay(PUBLIC_CHANNEL, "Sending eMail report now, this will take ~20 seconds.");
        key id = llDetectedKey(0);
        string name = llDetectedName(0);
        llEmail(emailAddress, emailHeader,
            "I was touched by: '" + name + "' (" + (string)id + ").");
        // llSay(PUBLIC_CHANNEL, "Email has been sent.");

Useful Snippets

email( string time, string address, string subj, string message, integer num_left )
    if(llGetSubString(address, -19, -1) == "@lsl.secondlife.com")//trim the header
        message = llDeleteSubString(message, 0, llSubStringIndex(message, "\n\n") + 1);


  • Because of the long delay on this function, it is often called from a second script triggered by link_message.
  • If you are sending email to a prim within Second Life, its address is [key]@lsl.secondlife.com
    • Which means if the key returned by llGetKey is "a2e76fcd-9360-4f6d-a924-000000000003", then its email address is "a2e76fcd-9360-4f6d-a924-000000000003@lsl.secondlife.com".
    • Agents do not have fixed email addresses, use llInstantMessage or llOwnerSay.

Prim2Prim Email

In LSL you can both send email with llEmail and receive it with the email event.

The email event is triggered with 5 pieces of information.

• string time When the message was sent, in the (string)llGetUnixTime format
• string address Who sent the message
• string subject Subject of the message
• string message Body of the message
• integer num_left The number of emails left in the email queue

When receiving a message sent with llEmail it helps to separate the message from the prefixed header. The header and original message body are separated by "\n\n"

integer divide = llSubStringIndex(message, "\n\n");
string header = llDeleteSubString(message, divide, -1);
message = llDeleteSubString(message, 0, divide + 1);

To get just 1 of the header items, do this:

list lines = llParseStringKeepNulls(header, ["\n"], []);
string objname_line = llList2String(lines, 0);
string region_line = llList2String(lines, 1);
string localpos_line = llList2String(lines, 2);

To get a pure region name, do this:

string region_name = llStringTrim(
                    llDeleteSubString(region_line, 0, 12),
                ), -2, -1), STRING_TRIM);

This application uses email to have objects check with a central server to see if the owner has the latest version. In the objects:

string version = "1"; //
string type = "lolcube";
    on_rez(integer start_param)
            (string)llGetOwner() + "," + type);

The server:

        llGetNextEmail("", "");
    email( string time, string address, string version, string message, integer num_left )
        if ((integer)version < 2)
            list info = llCSV2List( llDeleteSubString(message, 0, llSubStringIndex(message, "\n\n") + 1));
            llGiveInventory(llList2Key(info,0), llList2String(info,1));

See Also


•  email
•  link message


•  llGetNextEmail
•  llMessageLinked


•  IM to email
•  Postcards

Deep Notes

All Issues

~ Search JIRA for related Issues
   Region incoming email queue for objects becomes suspended
   llEmail and llHTTPRequest do not handle non-ASCII characters
   Include "Content-Type: text/plain; charset=UTF-8" header in the messages forwarded from second life.
   llEmails to objects not in the same region arrive without a body or do not arrive at all.


• internal test


function void llEmail( string address, string subject, string message );