tmo1

> Attached a few examples with a couple of notes I assume the original files end with the `END:VMSG` lines, and everything past that was added by you before uploading?...

Okay, I have written (in Python 3) [an initial attempt at a converter](https://github.com/tmo1/sms-ie/blob/master/tools/vmg-convert.py). It seems to work correctly on the three messages you provided, but I don't know how flexible...

> Hello, first attempt was unsuccessful due to file encoding. On linux (debian 9.9 with python 3.5.3) the original files are seen as data: > > $ file SMS/0001.vmg SMS/0001.vmg:...

On second thought, the problem is clearly that your version of Python is too old - [`datetime.fromisoformat` was introduced in Python 3.7](https://docs.python.org/3/library/datetime.html). Try running the tool using a more recent...

> In the imported file +39338000000 is treated as the number of the sender. I'm not sure what you're seeing, but on my device, it looks correct: +39338000000 is shown...

This can be done in a single line of Python! Run [this script](https://github.com/tmo1/sms-ie/blob/master/tools/csv-convert.py) as follows (`messages.csv` should be your CSV file, and `messages.json` will contain the SMS I/E compatible JSON):...

Please post some of the (redacted) converted JSON, as per [the instructions here](https://github.com/tmo1/sms-ie#posting-json).

Hm. Is your CSV file ASCII, or something else (e.g., UTF encoded Unicode)? If the latter, try saving it as ASCII and seeing if the script produces proper JSON. If...

At this point, I really need to see your original CSV file. Sensitive data can be redacted, if desired, but I need to see the more or less original version...

Well, there's your problem. In your initial report, you said that your file had lines like these: ``` "type","address","body","date" 2,"00447779877777","No, but I am leaving soon!","1120755000000" ``` This is standard CSV,...