Server Bugs

• Use concise, precise descriptions
• Do not include sensitive information.
• Create a support ticket at https://support.secondlife.com for individual account issues or sensitive information.
Auto-reply emails from Gmail (and similar services) are sent to @amazonses.com instead of @im.agni.lindenlab.com, breaking in-world delivery
When a user sets up an automatic email reply (e.g., vacation responder or canned response in Gmail) for incoming Second Life emails, the auto-reply is incorrectly addressed to an Amazon SES bounce/proxy address (something like xxxxxxx@amazonses.com ) instead of the original Second Life IM gateway address ( username@im.agni.lindenlab.com ). As a result, the auto-reply never reaches the sender in-world, and the original sender receives no indication that their IM triggered an out-of-office or automated response. Steps to reproduce (Gmail example): In Gmail, enable “Canned Responses” / Templates (Labs/Settings → Advanced). Create a new template with your desired auto-reply text. Create a filter that matches incoming emails from @im.agni.lindenlab.com (or specifically the Second Life IM address). In the filter actions, choose “Send template” and select the template created in step 2. From another Second Life account, send an in-world IM to the avatar whose email has the auto-reply configured. The IM arrives as an email → Gmail sends the canned response automatically. Observe the “To:” address of the sent auto-reply: it is an @amazonses.com address, not @im.agni.lindenlab.com . Expected behavior: The Reply-To or the effective destination should preserve the original @im.agni.lindenlab.com address (or provide a correct Reply-To header) so that auto-replies from users’ mail clients are delivered back into Second Life as IMs. Impact: Users who rely on out-of-office replies, support bots, or automated responses cannot inform senders that they are away or that messages are being handled automatically. This breaks a long-standing and heavily used feature of the email-to-IM system. Thank you for looking into this!
10
·
tracked
"Too many objects with large inventory are selected. Please select fewer objects and try again." gets triggered easily while returning, taking combined and deleting objects like furniture sets
It is quite understandable if the 10,000 limit applies to the objects we are taking combined/deleting/returning as we might rezz the same at some point and cause overload to the server but applying 10K limit to the content of the objects is quite hard to work around, especially when we are dealing with objects with large content. I had noticed this error appearing but I never really thought about finding the limit till yesterday. When I was trying to return a house, including its furniture, so it would be easier to rezz at the new spot, I had to keep reducing my selection until it was down to 12 objects! It was then I felt doubt; it's probably not the objects themselves but the content of the objects that is causing this issue, as I was able to select almost everything else worth thousands of prims at once and return. Upon further testing, I found that the furniture pieces I was trying to return had approximately 800-1000 animations in their content. As we all know, there are many furniture creators who include thousands of animations in their products and with this limit it would be almost impossible to delete/take/copy a bunch of furniture at once. I am aware of the possibility of using the return option with both land and region tools to avoid this limitation. However, when we wish to rebuild something at a different location or create a backup there is no real alternative in this situation. I kindly request LL to bless us with a workaround or reconsider how the limit is applied to make things easier for serious builders and those in service sector. Thank you for your time and attention
4
·
tracked
Load More