Talk:Email

Strife, I would think that a reader would look for examples on how to process incoming email in an entry on incoming email, rather than an entry on how to *send* email... but rather than spend 9 days debating that, I've made the reader aware (under examples ) that tips on how to process incoming email are now in the outgoing entry (llEmail.) -- Chaz. 11 October 2008. 11 am SLT.

Prims can receive email from not just prims but from outside of SL. By having the examples on email only detail how to handle prim2prim email confuses the situation. By having the the examples on llEmail, the function that in fact places the headers (that complicates the parsing) in the emails sent in the first place, eliminates that confusion. Having a note about this on email is totally appropriate. -- Strife ^{(talk|contribs)} 11:54, 11 October 2008 (PDT)

The information could be on both articles as long as it was properly described and encapsulated; so that the user knew they were learning about emails sent with llEmail. The problem with it originally was that the text didn't make it clear that it was only describing email sent with llEmail. -- Strife ^{(talk|contribs)} 12:00, 11 October 2008 (PDT)

Strife, can you add then pls a note to llEmail covering how emails from out-of-world might look, and be handled? So that we have info for people on processing emails whatever their source? The note might be as simple as just saying how out of world email differs in not having the Linden headers, etc? -- Chaz. 11 October 2008. 12:15 PM SLT.

I'm working on it as we speak (didn't even see your note here until after the edit conflict, which I will review now). Why should llEmail have information about external emails? Assuming typo and you ment email, then yes I will. -- Strife ^{(talk|contribs)} 12:45, 11 October 2008 (PDT)

Think I've made all the changes I'm going to make at this point. -- Strife ^{(talk|contribs)} 17:47, 11 October 2008 (PDT)

Character Limit

Anyone care to offer an explanation for the result of this?

<lsl>default {

   state_entry()
   {
       string msg;
       integer count;
       while((++count) < 1001)
       msg += "KGJTDkuygd"; // 10 chars of various byte counts.
       llEmail((((string)llGetKey()) + "@lsl.secondlife.com"), "", msg);
       llSetTimerEvent(5.0);
   }
   timer()
   {
       llGetNextEmail("", "");
   }
   email(string time, string address, string subject, string msg, integer num)
   {
       llSetTimerEvent(0.0);
       llOwnerSay(((string)llStringLength(msg)));
   }   // Object: 10084

}</lsl>Believe me; It's not the 84 chars I'm interested in (they are probably the header right?). -- Fred Gandt ^{(talk|contribs)} 17:29, 19 May 2010 (UTC)

while((++count) < 3001) returns Object: 30084

Stack heap collisions much beyond that for obvious reasons. -- Fred Gandt ^{(talk|contribs)} 17:35, 19 May 2010 (UTC)

Looks like the limit is broken. Or it was changed to an insane value. -- Strife ^{(talk|contribs)} 19:36, 21 May 2010 (UTC)

Or it depends on the kind of mail... I remember that LL distinguishes 3 different kind of mails. Those which are send within the same region, those which are send between different regions and those which got their origin/destination outside of the grid. The former two aren't actually processed as mails. Maybe it influences the limits?

-- ^{(talk|contribs)} 19:52, 21 May 2010 (UTC)

I feel some testing comming on. I don't fancy counting the outside email chars...996, 997, 999....grrrr! I'll come back with results. -- Fred Gandt ^{(talk|contribs)} 20:21, 21 May 2010 (UTC)

Ok. This is already weird. llEmail to my hotmail weighed in at 3745 chars including header and newlines. The header and newlines from my parcel measures 84 chars (the actual header has 80 chars). Bytes seemed to make no odds. 3745 chars seems like a very odd limit to me. But that's what it is. I am continuing to test but may sleep before I'm done. -- Fred Gandt ^{(talk|contribs)} 23:34, 21 May 2010 (UTC)