Sprint Messages aren't parsing

[jpmcgrath]

It seems a bit coincidental that Sprint has suddenly stopped working for me at the same time as Verizon (see issue #20) but I will report this anyway.

I am currently seeing a very different structure for sprint messages. Sprint is now including a text file attachment that contains the text of the message. Something that is also interesting is that messages received on June 13 are now expired on Sprint's servers when they should be accessible for 30-60 days.

Below is a mail message that exhibits the behavior:

Return-Path: 5131100000@pm.sprint.com
Received: by 10.229.28.19 with SMTP id k19csp59935qcc; Tue, 26 Jun 2012 12:25:37 -0700
Received: by 10.68.213.234 with SMTP id nv10mr55008636pbc.56.1340738736898; Tue, 26 Jun 2012 12:25:36 -0700
Received: from smtp03.sun3.lightsurf.net (smtp.sun3.lightsurf.net. [63.215.195.131]) by mx.google.com with ESMTPS id qf1si16849177pbc.85.2012.06.26.12.25.36 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 26 Jun 2012 12:25:36 -0700
Received: from pcs-nams008 (pcs-mmsc.sun3.lightsurf.net [10.0.0.152]) by smtp03.sun3.lightsurf.net (8.12.11.20060308/8.12.11) with ESMTP id q5QJNHru005820 for testaddress@gmail.com; Tue, 26 Jun 2012 12:25:36 -0700
Date: Tue, 26 Jun 2012 12:25:36 -0700
From: 5131100000@pm.sprint.com
To: testaddress@gmail.com
Message-ID: 31878575.1340738736299.JavaMail.lsadm@pcs-nams008
Subject: New Message
Mime-Version: 1.0
Content-Type: multipart/related;
boundary="----=_Part_321104_6797832.1340738736299";
charset=UTF-8
Content-Transfer-Encoding: 7bit
Delivered-To: testaddress@gmail.com
Received-SPF: neutral (google.com: 63.215.195.131 is neither permitted nor
denied by best guess record for domain of 5131100000@pm.sprint.com)
client-ip=63.215.195.131;
Authentication-Results: mx.google.com; spf=neutral (google.com: 63.215.195.131
is neither permitted nor denied by best guess record for domain of
5131100000@pm.sprint.com) smtp.mail=5131100000@pm.sprint.com
X-Priority: 3
X-MSMail-Priority: Normal
Importance: Normal

------=_Part_321104_6797832.1340738736299
Date: Tue, 26 Jun 2012 19:28:32 +0000
Mime-Version: 1.0
Content-Type: multipart/alternative;
boundary="----=_Part_321103_10226250.1340738736298";
charset=UTF-8
Content-Transfer-Encoding: 7bit
Content-ID: 4fea0d60abb12_2aa10adb8c768a8@cb6b861e-2b86-42be-be96-3e7f701daf10.mail

------=_Part_321103_10226250.1340738736298
Date: Tue, 26 Jun 2012 19:28:32 +0000
Mime-Version: 1.0
Content-Type: text/plain;
charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-ID: 4fea0d60a9b15_2aa10adb8c766ad@cb6b861e-2b86-42be-be96-3e7f701daf10.mail

You have received a Picture Mail from 5131100000@pm.sprint.com

------=_Part_321103_10226250.1340738736298
Date: Tue, 26 Jun 2012 19:28:32 +0000
Mime-Version: 1.0
Content-Type: text/html;
charset=UTF-8
Content-Transfer-Encoding: 7bit
Content-ID: 4fea0d60aac01_2aa10adb8c767a0@cb6b861e-2b86-42be-be96-3e7f701daf10.mail

<title>You have new Picture Mail!</title>

<tr>
   <td colspan="2">
       <img src="http://pictures.sprintpcs.com/images/x.gif" width="5" height="45"/>
   </td>
</tr>
<tr>
   <td VALIGN="top" colspan="2" width="590">
      <img src="http://pictures.sprintpcs.com/images/x.gif" height="5"/>
   </td>
</tr>
<tr>
   <td VALIGN="top" colspan="2" width="100%">
       <table width="100%" border="0" cellspacing="0" cellpadding="0">
              <tr>
                  <td bgcolor="#ffffff" width="100%">
                        <div style="border-top:1px solid rgb(156, 154, 156)">&nbsp;</div>
                  </td>
              </tr>
                              <tr>
                                    <td>    
                                            <div style="float:right; padding-right:5px"><span style="font-family:trebuchet ms, Helvetica, Arial, Verdana; Font-size: 11px; Color: #000000">&#169; 2012 Sprint. All rights reserved.</span></div>
                                    </td>
                              </tr>
              <tr>
                  <td bgcolor="#ffffff" width="100%"><img src="http://pictures.sprintpcs.com/images/x.gif" border="0" height="10"/></td>
              </tr>
       </table>
   </td>
</tr>

You have a picture / video message from 5131100000@pm.sprint.com

------=_Part_321103_10226250.1340738736298--

------=_Part_321104_6797832.1340738736299
Date: Tue, 26 Jun 2012 19:28:32 +0000
Mime-Version: 1.0
Content-Type: application/octet-stream;
charset=UTF-8;
name=textplain_2.txt
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
filename=textplain_2.txt
Content-ID: 4fea0d60acc5f_2aa10adb8c76960@cb6b861e-2b86-42be-be96-3e7f701daf10.mail

@testweek "fail forward fast" - Testweek

------=_Part_321104_6797832.1340738736299--

[jpmcgrath]

I'm happy to help come up with a fix for the two issues I have submitted, but would love some feedback on whether these problems are affecting more people than just me.

[jpmcgrath]

Have finally got my hands on some new Sprint MMSs (sent in a private email).
Looks like sprint have cleaned up their act and are now making their
mail format a lot nicer. Instead of linking to page where they host
and expire images they include the images as an attachment and text as
a text file attachment. Not sure if this is system wide, but it looks
like mms2r might be able to simplify a bit.

So, I think that with this new format the MMS2R gem is processing
everything nicely again. I'm not sure what was going on with those
weird MMSs I was receiving for a brief time, my best guess is that Sprint was transitioning from
their old crappy format to this new one and some messages got
swallowed/borked during the process.

Thanks for you help with all of this.

Kind regards,

James.