• All submissions to this site are governed by Second Life Project Contribution Agreement. By submitting patches and other information using this site, you acknowledge that you have read, understood, and agreed to those terms.
Issue Details (XML | Word | Printable)

Key: SVC-44
Type: Bug Bug
Status: Resolved Resolved
Resolution: Cannot Reproduce
Priority: Major Major
Assignee: Unassigned
Reporter: Marcuw Schnook
Votes: 4
Watchers: 1
Operations

If you were logged in you would be able to see more operations.
2. Second Life Service - SVC

Replying to IMs received is not working

Created: 26/Feb/07 01:03 AM   Updated: 19/Nov/08 06:55 AM
Return to search
Component/s: None
Affects Version/s: None
Fix Version/s: 1.13.4

Issue Links:
Duplicate
 
Relates
 

Linden Lab Issue ID: SL-36853


 Description  « Hide
I received IMs from a friend in SL in my email box. When I respond to it I get an error message in return:
-------------------------------------------------------------------
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

<mailtoim@data.agni.lindenlab.com> (expanded from
<REMOVED-FOR-PRIVACY@im.agni.lindenlab.com>):
Command died with status 100: "/opt/linden/indra/tools/mailglue/mailglue
--grid=agni --system=im". Command output: Invalid instant message session.

------------------------
I can only say that the removed-for-privacy part looks like a long hex64 based number (and not the old ############# etc. number).

 All   Comments   Change History      Sort Order: Ascending order - Click to sort in descending order
[ Permlink | « Hide ]
Lex Neva added a comment - 26/Feb/07 10:12 AM
I think it would help if you actually did show us what the REMOVED-FOR-PRIVACY is. If you have to, generate a new one with an alt, or show us what the old one looked like but change a few key digits. What I'm wondering is whether there are some characters in the email address that are being treated as invalid and not being sent properly to LL's SMTP server.

In the meantime, I'll try replying to an offline IM and see whether I have any luck.


[ Permlink | « Hide ]
Celierra Darling added a comment - 26/Feb/07 09:51 PM
note: initial poster appears to have responded within the issue description.

[ Permlink | « Hide ]
Lex Neva added a comment - 27/Feb/07 10:45 AM
No, that little note was already there before I responded. (You can see when edits happen on an issue by choosing "All" instead of "Comments". I was hoping for a little more detail than what they already included.

[ Permlink | « Hide ]
Merlin Alphabeta added a comment - 06/Mar/07 06:48 AM
The original requester may not want to but I will... this has been affecting me for 3-4 weeks...

(copy of mail follows to end of comment)

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

<mailtoim@data.agni.lindenlab.com> (expanded from
<A1C7Lkqy6IHtNT1qBOQdAoWwRHdpiFkCvwETmjs4-LCPwwR4pkd29w@im.agni.lindenlab.com>):
Command died with status 100: "/opt/linden/indra/tools/mailglue/mailglue
--grid=agni --system=im". Command output: Premature end of base64 data at
/opt/linden/indra/tools/mailglue/../../lib/perl/Indra/IMEmail.pm line 24,
<STDIN> line 45. Premature padding of base64 data at
/opt/linden/indra/tools/mailglue/../../lib/perl/Indra/IMEmail.pm line 24,
<STDIN> line 45. Invalid instant message session.


[ Permlink | « Hide ]
James Linden added a comment - 07/Mar/07 10:31 PM
OK, I know what this is. Thank you for the repro case.

The problem is that some email systems generate "To:" address lines with carriage returns in them. This is perfectly valid per the email RFC, but our incoming email processing script "mailglue" doesn't handle that case.

I've got a patch internally and will test and hopefully deploy it tomorrow.

This may be a different issue than problems starting 3-4 weeks ago. We had a postfix (mail delivery processor) config issue on Feb 22nd and I broke the mailglue script on Feb 23rd but both problems were fixed in under a day.


[ Permlink | « Hide ]
James Linden added a comment - 07/Mar/07 10:33 PM
Oh, and this only affects certain email clients. I'm pretty sure things work with Thunderbird, Yahoo Mail, and Gmail.

There is another bug that prevents Hotmail users from replying to IM to email. (Hotmail slams outgoing email addresses to lower case, which breaks the base64 encoded data in the reply address.)

I believe it happens with the "Horde" web based email client used by universities. If you know of other email clients where this happens please post them here.


[ Permlink | « Hide ]
Torley Linden added a comment - 12/Mar/07 12:48 PM
Related article in Knowledge Base:

Why isn't email-to-IM working for me?
» http://secondlife.com/knowledgebase/article.php?id=411


[ Permlink | « Hide ]
James Linden added a comment - 18/Mar/07 01:36 PM
The code released last week should be able to tolerate capitalization problems in the email address (the Hotmail problem) and carriage returns in the To: address (the Horde problem).

Please reopen or enter another bug if valid inbound email replies to IM bounce.


[ Permlink | « Hide ]
Timo Gufler added a comment - 31/May/07 11:57 PM
It seems there is still something wrong with the email->IM system. I tried to reply to instance message sent me by email but got the following error even if tried many times with different options (utf-8, iso-8859-1, HTML). The message contained french characters which I suppose caused the problem. An attachment contained in the error response can be seen below. I replaced the sender and recipient information with "*" characters.

Reporting-MTA: dns; data.agni.lindenlab.com
X-Postfix-Queue-ID: 961ED25AF5E
X-Postfix-Sender: rfc822; *******************
Arrival-Date: Thu, 31 May 2007 23:22:14 -0700 (PDT)

Final-Recipient: rfc822; mailtoim@data.agni.lindenlab.com
Original-Recipient: rfc822;***************************************************************************
Action: failed
Status: 5.3.0
Diagnostic-Code: x-unix; Fault from http://10.2.245.40:12035/xmlrpc/postmaster:
RPC::XML::fault=HASH(0x8da0eb8)->as_string()


[ Permlink | « Hide ]
Soft Linden added a comment - 09/Jul/07 05:54 PM
Just had this myself. Copying full message to internal JIRA

[ Permlink | « Hide ]
Thraxis Epsilon added a comment - 08/Nov/07 12:02 PM
This has been working for me. If it is still an issue, please provide steps to reproduce

[ Permlink | « Hide ]
Timo Gufler added a comment - 07/Oct/08 11:43 PM
Since Soft Linden was able to reproduce this the status shouldn't be "Cannot Reproduce". I was able to reproduce this too about two weeks ago.

[ Permlink | « Hide ]
Ellla McMahon added a comment - 19/Nov/08 06:53 AM - edited
Timo, I have added your comment to SVC-229 Please add any further comments and vote to that issue. If you could include as much detail as possible, without disclosing private or personal information, that would be very helpful to the LL Developers.

Resolving this as per the original resolution 08/Nov/07
Powered by Atlassian JIRA the Professional Issue Tracker. (Enterprise Edition, Version: 3.13.2-#335) - Bug/feature request - Atlassian news - Contact Administrators