mirror of
https://github.com/jberkel/sms-backup-plus.git
synced 2026-04-25 17:05:59 +03:00
[GH-ISSUE #647] Backup MMS as emails with multiple recipients #555
Labels
No labels
AM+RCS
FAQ
awaiting response
backup
bespoke
bug
calendar
call log
cannot reproduce
cloudless
device-specific
documentation
dual- & multi-SIM
duplicate
feature-request
fixed in beta
good first issue
half-missing
help wanted
helpful
meta
misattribution
mms
other message sources
pull-request
question
rejuvenation
restore
schedule
security
stale
task
thanks
v1.5.1
v1.5.10
v1.5.11
v1.5.2
v1.5.3
v1.5.3
v1.5.4
v1.5.4
v1.5.5
v1.5.5
v1.5.6
v1.5.7
v1.5.8
v1.5.9
v1.6β
xoauth
~$ bounty $~
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/sms-backup-plus-jberkel#555
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @streeter on GitHub (May 23, 2016).
Original GitHub issue: https://github.com/jberkel/sms-backup-plus/issues/647
When backing up an MMS message, instead of backing up the message from a single recipient, back up the message as part of a thread, where each message includes all the senders in the TO message.
Currently, all MMS messages go into the thread between you and the sender (ie. 1-1 thread), instead of being grouped together.
@jcrben commented on GitHub (Jul 14, 2018):
Posted a $10 bounty at https://www.bountysource.com/issues/34480509-backup-mms-as-emails-with-multiple-recipients
@rsercano commented on GitHub (Jul 15, 2018):
@jcrben an entry point and I'm ready to have a look at this issue :) But still bounty seems a bit low ?
@jcrben commented on GitHub (Jul 15, 2018):
Hey, I don't actually care about this issue all that much. It was kind of an example and it's something that does seem to affect me...
Also I'm not rich, sadly!
@rsercano commented on GitHub (Jul 15, 2018):
I understand you very well, I'm having same issues with my open source project (nosqlclient) then I guess it would be better to remove bounty
@jcrben commented on GitHub (Jul 15, 2018):
Sorry to hear that!
This isn't really my project. I'm just a slightly more involved than usual user.
Maybe another user will add to the bounty - that's sort of how bountysource is designed to work.