[CountryDevil]

I have been having issue with Picturemail off an on for several days. called Sprint they reset my picmail and all was working again...for only the first fe picture both sent and received.

As stated in thisn thread I have had the same symptoms:

1) Picmail stays in inbox even after sent. I never have anything in my sent folder.
2) Picmail takes forever to send if it sends at all. In most cases I go look at the picmail site and the picture say I have a new picmail (one I just sent to myself.) But I never get in on my TP. I even have had friends send me pics that I never got on the phone but are on the picmail site.
3) Picmail seems to be "threaded"? Simmilar to that of threaded SMS messages. As already stated all mail seems to remain in the Inbox. If I get a picmail from somone other than me and send a replay picmail, they show up as somewhat threaded when you open the message.
4) Picmail seems to work like SNMP protocols... fire and forget. If for some reason that you do not get the notification OR the phone can not be found at the time there is not an other attempt to send the mesage once received in you picmail inbox. (On the picmail site)

I know that some say they have .net 3.5 installed and things are working fine. BUT I thought so too and had both the picmail update AND .net 3.5 installed. All of the above symptoms listed above were with .net 3.5 installed. Once I removed the .net 3.5 most of the above symptoms went away except the threaded message thing. And I am not too sure if this is the way that the picmail is suppose to work. In addition, the picmail application send and receive was much quicker than having .net 3.5 installed.

Now as with some of you I have applications that need .net 3.5 to run. But after I removed .net 3.5 and reinstalled it, all of the symptoms came back. So I think that the post the OP listed is pretty much correct.

If Sprint designed picmail to a spec of .net that was in a lower revision of .net that is no longer in version 3.5 or a spec that has been revised, it is plausable to say the .net 3.5 vould be a contributor of some of the issues we are seeing. I understand that some of the Diamond users are not seeing these issues, but I still am not sure of that since I have no way of testing.

So I am asking those of you to do your own testing that have .net 3.5 installed. See if things improve after the uninstall. If so, I will see if my buddy that works in the lab at Sprint can do his testing to see if we can get this fixed once and for all.