[GH-ISSUE #579] Sent MMS to unsaved contact not getting saved into conversation thread #494

New issue

Closed

opened 2026-02-26 01:30:46 +03:00 by kerem · 2 comments

kerem commented

2026-02-26 01:30:46 +03:00

Owner

Originally created by @tkalus on GitHub (Aug 4, 2015).
Original GitHub issue: https://github.com/jberkel/sms-backup-plus/issues/579

When I send a MMS message to a phone number not in my address book, the sent message (and attached picture) is saved in a different thread in gmail. It appears an issue with the X-smssync-address header and subsequently the generated subject. Only for MMS messages that I send to a phone number that is not in my Contacts, the header is set to my phone number and the Subject is set to my name.

I suspect this block of code is the root of the issue.

For sent SMS messages sent to and SMS & MMS messages received from unsaved numbers, the email message threading is as expected.

Moto G (with 4G/Gen1) with Android 5.1.

Originally created by @tkalus on GitHub (Aug 4, 2015). Original GitHub issue: https://github.com/jberkel/sms-backup-plus/issues/579 When I send a MMS message to a phone number not in my address book, the sent message (and attached picture) is saved in a different thread in gmail. It appears an issue with the `X-smssync-address` header and subsequently the generated subject. Only for MMS messages that I send to a phone number that is not in my Contacts, the header is set to my phone number and the Subject is set to my name. I suspect this [block of code](https://github.com/jberkel/sms-backup-plus/blob/master/src/main/java/com/zegoggles/smssync/mail/MmsSupport.java#L91-L102) is the root of the issue. For sent SMS messages sent to and SMS & MMS messages received from unsaved numbers, the email message threading is as expected. Moto G (with 4G/Gen1) with Android 5.1.

kerem

2026-02-26 01:30:46 +03:00

closed this issue
added the
backup

mms
labels

kerem commented

2026-02-26 01:30:46 +03:00

Author

Owner

@dg4u commented on GitHub (Sep 2, 2015):

This seems to be the same issues as #390 which has gone unaddressed since 2013-11.

@dg4u commented on GitHub (Sep 2, 2015): This seems to be the same issues as #390 which has gone unaddressed since 2013-11.

kerem commented

2026-02-26 01:30:46 +03:00

Author

Owner

@jberkel commented on GitHub (Mar 28, 2018):

Closing as dup of #390

@jberkel commented on GitHub (Mar 28, 2018): Closing as dup of #390