Issue generated from Tuleap's migration script. Originally submitted by: Alexandre Lision (alision)

There is an issue with the way text messaging is read/save.

Text messages are stored in a file named after the associated ContactMethod's sha1.

When starting Ring, some ContactMethods are loaded WITHOUT an account.
It was preventing the user from sending a text message to some ContactMethods (see c20da91 in ring-lrc)

We now set an account if none is provided, and this cause the sha1 to be regenerated, and so the text messages are saved under a different sha1.

Problem is when you reopen Ring, the ContactMethod is still not associated with an account, so the sha1 is back to its first value. No file is located under this sha1, so im history appears empty.