Envora · Bulk email from your iPhone
Envora: dispatch bulk emails without the markup
Cost-efficient bulk email for small businesses, freelancers and marketers, with no per-subscriber traps and no inflated tiers.
App Store · Free to download · iPhone
Which situation are you in?
- Your list is in the hundreds: this fits.
- You need automation or tens of thousands of sends: use a platform.
How we checked
We compared the upload model with the own-mailbox model, using the original guide and Envora’s App Store description (“Gmail and Google Workspace”, “App Passwords with direct SMTP”, “We store NOTHING!”; read 29 Oct 2026, 03:26 IST).
Upload to a platform
- Who holds the list: The provider, as your data processor
- Gains: Managed deliverability, automation, compliance tools
- Costs: Often billed per contact
Send from your own mailbox
- Who holds the list: You
- Gains: No processor relationship for the list
- Costs: Google’s limits, manual unsubscribes, no automation
Comparison at a glance
| Upload to platform | Own mailbox | |
|---|---|---|
| List location | Provider servers | Your device |
| Daily volume | Plan limits | Google account limits |
| Automation | Yes | No |
| Unsubscribe handling | Automatic | Manual |
| Billing | Often per contact | Your mailbox plus the app |
From the guide and the Envora listing.
What "import your contacts" really sets up
Uploading a list makes the provider a processor of personal data on your behalf. That is a normal, lawful arrangement — but it carries obligations and consequences that are easy to skip past during onboarding.
Your list becomes part of their breach surface. Under GDPR you need a processor agreement and a record of where that data sits. If pricing is per subscriber, the thing you are billed on is the size of the list you handed over. And migration later means exporting in their format and hoping the engagement history comes with it.
None of that is a scandal. It is just a structure, and it is worth choosing on purpose.
The other structure: send from your own mailbox
The alternative is to keep the list on your device and use a mailbox you already own as the sending engine. Google Workspace and Gmail both speak SMTP, and Google supports App Passwords for exactly this — a scoped credential that authorises sending without exposing your main account password.
The contacts never move. The provider relationship you already have — with Google — is the only one involved.
What you give up, plainly
This part decides whether the approach suits you, so it is worth being blunt.
Sending limits are real and low. Google caps daily recipients, and the cap is oriented around a person sending mail, not a marketing platform. This works for hundreds of recipients. It does not work for tens of thousands.
No managed IP reputation. Platforms employ deliverability teams and warm dedicated IPs. Sending yourself means your domain reputation is yours to protect, which makes SPF, DKIM and DMARC your responsibility rather than a checkbox.
No automation layer. Behavioural triggers, drip sequences and segmentation by engagement are what the subscription buys. You do not get them here.
Compliance is manual. Suppression lists and unsubscribe handling are automatic on a platform. Sending yourself, honouring an unsubscribe is a process you have to actually run — and it is a legal obligation, not a courtesy.
Who this genuinely fits
A list in the hundreds rather than the tens of thousands. Periodic sending rather than continuous automated campaigns. A sender who already pays for Google Workspace and would rather not pay a second time to store contacts they already have. And anyone for whom "our list never left our own systems" is worth more than a segmentation feature.
Where Envora sits
Envora is built on precisely this model. Its App Store listing describes using your existing Gmail or Google Workspace account as the sending engine, connecting through App Passwords with direct SMTP, and configurable throttle delays so sending stays within Google's limits rather than tripping them. It composes HTML or plain-text campaigns, it is free, and it is iPhone-only.
The constraint is binary, which is the useful part: either your contacts were uploaded to a third party or they were not.
If you want X, take Y
- If you want email list privacy, take the own-mailbox route; on iPhone, Envora.
- If you want automation, take a platform and sign a processor agreement.
Sources are linked inline. Google can change its limits, so check the linked pages before a large send.