MailPing Research investigates how modern email infrastructure behaves across different platforms and devices. Our studies analyze tracking signals, proxy systems, and privacy protections implemented by major email providers.
View all research →Email Client Protocol Study – Gmail vs Apple vs Outlook
MailPing Research. (2026). Email Client Protocol Study – Gmail vs Apple vs Outlook. MailPing Infrastructure Research. https://mailping.pro/research/email-client-protocol-study
Research Summary
- Gmail generates a receiver-side proxy request before user interaction.
- Apple Mail loads images through a proxy only at open.
- Outlook loads images directly from the recipient device.
- The first receiver-side request reveals whether prefetch occurs.
- Email tracking signals vary significantly across platforms.
Research Context
Email tracking systems rely on remote image requests to detect delivery and open events. However, different email clients generate these requests using fundamentally different infrastructure models.
This study investigates whether image requests occur before user interaction (prefetch), during open, or directly from the recipient device, using controlled MailPing tracking logs.
Methodology
MailPing tracking pixels were embedded into controlled test emails sent across Gmail, Apple Mail, and Outlook environments.
Each test generated structured event sequences. Sender-side events were excluded, and only receiver-side HTTP requests were analyzed.
The first receiver-side request was treated as the primary signal for determining whether prefetch occurs and whether the request originates from proxy infrastructure or the user device.
Observed Behavior
| Client | First Receiver-Side Request | Origin | Interpretation |
|---|---|---|---|
| Gmail | Proxy request before user interaction | Google infrastructure | Prefetch + Proxy |
| Apple Mail | Proxy request at open | Apple relay | Proxy only |
| Outlook | Direct device request at open | Recipient device | Direct signal |
These observations were consistent across multiple controlled test environments and repeated message interactions.
Evidence Examples
Gmail First Receiver-Side Request: IP: 66.249.x.x ASN: Google LLC User-Agent: via ggpht.com GoogleImageProxy Outlook Open Request: IP: 197.x.x.x ASN: Dimension Data User-Agent: Android WebView
In Gmail tests, the first receiver-side request consistently originated from Google proxy infrastructure before any device-origin request appeared.
Apple Mail Proxy Request (Observed at Open Only)
Apple Mail First Receiver-Side Request: IP: 17.x.x.x ASN: Apple Inc. Origin: Apple Privacy Relay Timing: No receiver-side requests observed prior to user interaction. First request occurs only when the email is opened.
In Apple Mail tests, no receiver-side HTTP requests were observed between message delivery and user interaction. The first recorded request consistently occurred only at the moment the email was opened and originated from Apple proxy infrastructure.
Key Findings
- Gmail generates a proxy request before user interaction.
- Apple Mail does not produce a pre-open receiver-side request.
- Outlook generates only direct device-origin requests.
- The first receiver-side request determines tracking signal type.
- Proxy-based systems obscure user identity.
Implications
Email tracking systems must distinguish between proxy-generated and device-generated requests to accurately interpret engagement signals.
Prefetch behavior introduces early signals that are not tied to user interaction, while proxy systems obscure user identity and location.
Direct-loading clients provide accurate open signals but expose recipient network information.
Dataset & Research Evidence
This study is based on MailPing infrastructure logs generated from controlled test sequences across Gmail, Apple Mail, and Outlook environments.
- MailPing Gmail proxy request logs
- MailPing Outlook device request logs
- MailPing cross-platform event sequence dataset
Example event sequences and request traces are documented in the internal dataset.
Disclosure
This research was conducted using MailPing tracking infrastructure. Only standard HTTP request metadata was analyzed. No personal user data was collected.