An iMessage doesn't have to come from the phone number or the Apple ID email on the account. A user can add any email address they control to their Apple Account and send iMessages from it. If you only check the Apple ID, you may miss the address the messages actually came from.
I added a new Gmail address to a test iPhone's Apple Account, sent iMessages from it, and then looked at what sms.db, Accounts3.sqlite and Cellebrite Physical Analyzer recorded.
Key findings
destination_caller_idin thesms.dbmessage table showed which of the user's addresses each iMessage was sent from.- The
accountcolumn showed the Apple ID email for every iMessage, no matter which address actually sent it. - The new address was used only for a new conversation. An existing conversation kept the address it already used.
- Once a conversation started from the new address, it kept using it, even after the user switched the setting back to the phone number.
- The secondary email was not in
Accounts3.sqlite. - Creating the Gmail account left its own trace: Google's verification text in
sms.db.
How the setting works
In Settings > Messages > Send & Receive, iOS shows two lists:
- You can receive iMessages to and reply from: every address that can receive iMessages. More than one can be checked.
- Start new conversations from: the single address used as the caller ID for new conversations. Only one can be checked at a time.
Any email address added to the Apple Account (Settings > [name] > Name, Phone Numbers, Email) can appear in both lists once it's verified.
Test setup
| Item | Detail |
|---|---|
| Device | Apple iPhone 7 (A1660) |
| iOS version | 15.8.2 (19H384) |
| Test date | 12 Mar 2025, Eastern Daylight Time (UTC-4). Times below are local. |
| Starting state | Receive from: phone number and iCloud Apple ID email. Start new conversations from: phone number. Send as SMS off. |
| Extraction | Full file system |
| Analysis tools | DB Browser for SQLite, Cellebrite Inseyets Physical Analyzer 10.5.0.1016 |
Actions on the device
| Time | Action |
|---|---|
| 09:03 | Created a new Gmail account. Google sent a verification code by text to the phone. |
| 09:09 – 09:11 | Added the Gmail address under Name, Phone Numbers, Email. Apple emailed a verification code to the Gmail address; entered it, and the address appeared on the account. |
| 09:12 | Opened Settings > Messages. iOS prompted: add this address for iMessage and FaceTime? Chose Yes. All three addresses were now checked under "receive and reply from." |
| ~09:13 | Selected the Gmail address under "Start new conversations from" |
| 09:37 | Sent an iMessage in an existing conversation with Contact 1 |
| 09:41 | Started a new conversation with Contact 2 and sent an iMessage |
| 09:42 | Switched "Start new conversations from" back to the phone number |
| 09:45 | Sent another iMessage to Contact 2 in the same conversation |
What sms.db recorded
This query pulls the columns that matter:
SELECT
datetime(date / 1000000000 + 978307200, 'unixepoch') AS sent_utc,
text,
service,
account,
destination_caller_id
FROM message
ORDER BY date;
| Local time | Message | service | account | destination_caller_id |
|---|---|---|---|---|
| 09:04:12 | Google verification code | SMS | P:+1 (phone number) | +1 (phone number) |
| 09:37:24 | Existing conversation, Contact 1 | iMessage | E:(Apple ID email) | (Apple ID email) |
| 09:41:49 | New conversation, Contact 2 | iMessage | E:(Apple ID email) | (Gmail address) |
| 09:45:15 | Same conversation, after switching back | iMessage | E:(Apple ID email) | (Gmail address) |
destination_caller_id is the sending address
Joshua Hickman showed in 2022 that destination_caller_id records which phone line sent or received a message on a dual-SIM iPhone. This test shows the same column does the same job for email addresses. It changed with the address that was actually used, and it was the only column that did.
The account column is not the sending address
For all three iMessages, account held E: plus the Apple ID email, even when the message went out from the Gmail address. For SMS it held P: plus the phone number. Don't use account to say which address a message came from.
Conversations keep their address
- At 09:37, the Gmail address was selected for new conversations, but the message to Contact 1 went out from the Apple ID email. That conversation had last been used in September 2024, from the Apple ID email, and it stayed that way.
- At 09:41, the new conversation with Contact 2 started from the Gmail address.
- At 09:45, after the setting had been switched back to the phone number, the next message to Contact 2 still went out from the Gmail address.
The setting only applies when a conversation starts. After that, the conversation sticks with its address. So the setting at extraction time tells you very little about which address any given conversation used. Check every message.
What Accounts3.sqlite didn't show
Accounts3.sqlite listed the Apple ID, but the Gmail address wasn't in it, even though it was verified on the Apple Account and active for iMessage and FaceTime. If you use that database to list a user's accounts, you'll miss addresses like this one. This test didn't look for other places the address is stored. The messages themselves were where it showed up.
How Physical Analyzer showed it
Physical Analyzer 10.5 labeled each sent message with the address from destination_caller_id: the Apple ID email for the 09:37 message and the Gmail address for the 09:41 and 09:45 messages, each marked "(owner)." The conversation's participant list included the device owner's addresses alongside the other party.
The chat-level Account field did not track that. It showed the phone number for the Contact 1 conversation and the Apple ID email for the Contact 2 conversation, although every message in the Contact 2 conversation was sent from the Gmail address. Go by the per-message sender, and confirm it against destination_caller_id in the database.
A side effect worth knowing
Creating the Gmail account left its own evidence. Google texted a verification code to the phone, and that SMS sits in sms.db at 09:04:12. Apple's verification code for the new address went to the Gmail inbox, not to Messages, so it won't be in sms.db. If you find an unfamiliar email address in destination_caller_id, look for verification texts and emails around the time it first appears.
How to use this in casework
- Pull
destination_caller_idfor every message, not justaccount. List every distinct value. Each one is an address the device owner used. - Expect email addresses that aren't the Apple ID and aren't in
Accounts3.sqlite. - Work out which address each conversation used. Don't assume the current "Start new conversations from" setting applied to past messages.
- Check how your tool labels the sender and the chat account. They may not agree.
- Look for account creation and verification messages around the first use of a new address.
- To tie an address to an Apple Account, consider legal process to Apple.
Limits of this test
- One device, one iOS version (15.8.2), one added email address.
- Only sent messages were tested. Received messages to the Gmail address were not.
- What the recipient saw as the sender was not checked.
- FaceTime records, IDS preference files and other places the address may be stored were not examined.
- Removing the address from the Apple Account afterward, and what that does to existing records, was not tested.
Run the same test on your own device and iOS version before you rely on this in a report.
Bottom line
An iPhone user can send iMessages from an email address that isn't their Apple ID and doesn't show up in the account database. destination_caller_id records which address each message actually came from, and conversations keep using that address even after the user changes the setting. Read it for every message.
Sources
- Joshua Hickman, Mo' SIMs, Mo' Problems: Examining Phones with Dual SIMs, 2022
Testing completed by Major Ricky Johnson, Richland County Sheriff's Department.