In iOS when you forward a message, bafflingly, it does not copy the original source address, rather just the body so depending on the message you’re likely to be either misleading the recipient, plagiarizing without attribution, or sending spam content firsthand. Contrast with email in which convention is to copy a few headers to preserve context through forwarding.
In the case of 7726, I’m further confused that there seems to be no acknowledgement of this source of ambiguity. Do they want to know the source of the spam, so I should manually add it to the message? Or are they just training a content recognition model and by sending anything other than the original text verbatim I’m throwing it off?
Also, when the forwarded spam contains a URL, iOS often automaticity chops off that part of the message and shows an unhelpfully truncated version of it below the message in a separate bubble. Is iOS treating the forwarded spam as trusted data and probing the spammer’s URL, tracking parameters and all?
In the case of 7726, I’m further confused that there seems to be no acknowledgement of this source of ambiguity. Do they want to know the source of the spam, so I should manually add it to the message? Or are they just training a content recognition model and by sending anything other than the original text verbatim I’m throwing it off?
Also, when the forwarded spam contains a URL, iOS often automaticity chops off that part of the message and shows an unhelpfully truncated version of it below the message in a separate bubble. Is iOS treating the forwarded spam as trusted data and probing the spammer’s URL, tracking parameters and all?