Why Gmail with IMAP, SMTP and API support
For media buyers, affiliates and SMM teams, email is not just an inbox — it is an infrastructure node. Gmail receives confirmation codes, registration messages, ad cabinet notifications and Google Ads alerts. When you run dozens or hundreds of mailboxes, manual reception is impossible. The solution is Gmail accounts with IMAP/SMTP protocols enabled and access to the Gmail API. They let you read incoming mail programmatically, grab one-time codes, send campaigns and synchronize the state of many mailboxes at once.
The YTMarket catalog offers Gmail accounts of various types: fresh, aged, PVA with a confirmed number, API-ready and bulk batches. Payment is via USDT (TRC20/BEP20/ERC20/Polygon/SOL/TON), CryptoBot or rubles. Every account comes with a 24-hour warranty: if it is invalid on arrival, you get a replacement.
Three protocols: how IMAP, SMTP and API differ
Each protocol solves its own task. IMAP handles reading and syncing messages on the server, SMTP handles sending, and the Gmail API provides extended programmatic access via REST and OAuth2.
| Protocol | Purpose | Host / endpoint | Port |
|---|---|---|---|
| IMAP | Receive and read mail | imap.gmail.com | 993 (SSL) |
| SMTP | Send mail | smtp.gmail.com | 465 / 587 |
| Gmail API | REST access, labels, filters | gmail.googleapis.com | 443 (HTTPS) |
For most code-reception tasks, IMAP alone is enough. If you need bulk operations, labels, watch notifications and high throughput, choose accounts with the API configured.
Setting up access: App Password and OAuth2
Google has disabled plain-password login for third-party clients, so there are two working authorization paths.
- App Password — a 16-character application password. Requires two-factor authentication enabled. Suitable for classic IMAP/SMTP clients and simple scripts.
- OAuth2 — access tokens and refresh tokens. Mandatory for the Gmail API and considered the secure standard for long-running automation.
On YTMarket, API-ready accounts ship with prepared OAuth data (client_id, refresh_token), saving hours of manual Google Cloud Console setup and app publishing.
Example: receiving mail over IMAP
A minimal Python scenario is to fetch the latest unread message and extract a confirmation code. The logic is wrapped in a loop over the account list and routed through a proxy at the network layer.
- Connect:
imaplib.IMAP4_SSL("imap.gmail.com", 993) - Login: e-mail + App Password
- Select folder:
INBOX, searchUNSEEN - Parse the message body with a regular expression to extract the code
The Gmail API works differently: call users.messages.list with a filter, then users.messages.get and decode the base64 body. The API is more resilient to limits and more convenient for processing hundreds of mailboxes in parallel.
Antidetect and proxies: safe work at scale
Mass automated mail reception without environment isolation quickly leads to bans. The best practice is a combination of an antidetect browser and quality proxies.
- Antidetect browsers (Dolphin Anty, AdsPower, GoLogin, Multilogin) — a separate profile with a unique fingerprint per account for manual logins.
- Mobile and residential proxies — pin one IP to one mailbox and avoid data-center subnets.
- Geo matching: the proxy country should match the account's registration region.
- For server-side IMAP/API automation, route traffic through a proxy at the socket or HTTP-client level.
Respecting send limits (SMTP), gradual warm-up and a stable IP are the three pillars of safe operation.
Where to buy and how to choose Gmail accounts
At YTMarket, pick the type that fits your task: fresh or PVA for registrations, aged for long-running projects, and API-ready Gmail for automation. Each account comes with access data (login, password, App Password or OAuth, and where available a recovery email/number). Support is on Telegram: @RegaProvider. Crypto payment in USDT, via CryptoBot or in rubles, instant delivery and a 24-hour replacement warranty make buying bulk batches predictable and safe.