High-volume campaign infrastructure with dedicated IP pools, automatic warm-up, per-provider throttling and inbox placement testing. Hosted in India, billed in INR with GST invoices. Plans from ₹528/month.
A bulk email service sends one message to a large list of recipients — newsletters, product announcements, promotional campaigns, re-engagement sequences. That much is obvious. What separates a real bulk email platform from a mail client with a big "to" field is everything that happens around the send.
Mailbox providers do not treat a hundred thousand simultaneous messages the way they treat one. Send them all at once from an unfamiliar IP and Gmail will throttle, Microsoft will defer with 451 errors, and a meaningful share will land in spam regardless of how well written the campaign was. The infrastructure has to pace delivery per provider, respond correctly to pushback, suppress addresses that bounce, honour unsubscribes within hours, and report what actually happened to each message.
Sending millions of emails is easy. Landing them in the inbox is the entire problem, and it is decided long before the send button.
These are often bought together and should almost always be configured apart.
The practical consequence: run them on separate sending domains and separate IP pools. If a poorly targeted campaign generates complaints on the same IP that carries your OTPs, your login codes inherit the damage. Nobody marks an OTP as spam, but they stop arriving anyway — and the failure is rarely diagnosed quickly because few people connect Tuesday's campaign to Thursday's login problems.
neuMails runs both from one account with reputation kept isolated. See transactional email for that side.
Four things, roughly in order of weight. Subject lines are not among them.
1. Authentication. SPF, DKIM and DMARC must be correct for your sending domain. This is now a requirement rather than a best practice — Gmail and Yahoo reject unauthenticated bulk mail at the gateway. Our authentication wizard generates the records.
2. Complaint rate. Gmail asks bulk senders to stay below 0.3 percent and treats 0.1 percent as the warning zone. That is roughly one complaint per thousand emails — an easy line to cross if you mail people who have forgotten who you are.
3. Engagement. Providers weigh whether recipients open, reply, and don't delete without reading. This is why mailing your entire list every time is counterproductive: the unengaged tail drags down the reputation that delivers to the engaged core.
4. IP and domain reputation. Built over time through consistent volume and clean behaviour. New IPs have none, which is what warm-up exists to solve.
Note that three of the four are consequences of who you mail, not what you send. List discipline is the lever.
The instinct with a bulk email list is to grow it and mail all of it. Both halves of that instinct cost you money.
A smaller list that engages outperforms a larger list that doesn't, on both deliverability and revenue. This is the rare case where the compliant option and the profitable option are the same option.
On a shared IP, your deliverability is the average behaviour of everyone sending from it. One careless sender in the pool and your campaign inherits their reputation. On a dedicated IP, mailbox providers evaluate you alone.
Dedicated IPs come with an obligation, though: a new IP has no sending history, and providers treat no history as suspicion. Send 50,000 emails on day one from a cold IP and you will be throttled by Gmail, deferred by Microsoft and possibly blocked by Yahoo — regardless of how legitimate the mail is.
Warm-up is the gradual volume ramp that earns trust. Done by hand it is a spreadsheet of daily caps and per-provider quotas over three to four weeks. neuMails automates it:
High-volume senders get multiple IPs, which raises aggregate throughput and lets you separate campaign reputation from transactional reputation. Details on SMTP relay.
If you send more than roughly 5,000 messages a day to Gmail addresses, you are a bulk sender in Google's terms and three requirements apply:
p=none, with alignment between your From domain and your authenticationYahoo applies comparable requirements. Non-compliant bulk mail is rejected at the gateway rather than filtered to spam, which means you find out through a delivery failure rather than a quiet drop in opens.
Full checklist in our Gmail and Yahoo sender requirements guide.
An email address is personal data, which makes every bulk email list you hold subject to India's Digital Personal Data Protection Act. For campaign sending specifically that means consent which is free, specific, informed and unambiguous, given by clear affirmative action — and a record of when and how each subscriber gave it.
In practice: no pre-ticked subscribe boxes, no consent bundled into terms acceptance, and withdrawal as easy as signing up was. neuMails stores subscription source, timestamp and IP per subscriber, so the record exists when you need it.
Subscriber data is stored and processed on AWS Mumbai. More on the DPDP compliance page, and on on-premise deployment if your requirement is that data never leaves your own network.
Search for bulk email software in India or a mass email service and the results span a wide range of quality. Worth checking before you commit:
Comparisons against the major alternatives: vs Mailchimp · vs SendGrid · vs Brevo · best platforms in India.
Free trial with full sending access. Marketing plans from ₹528/month, billed in INR with GST.
Start Free TrialInfrastructure and software for sending one message to a large list — newsletters, promotions, announcements, re-engagement campaigns. It handles list management, personalisation, per-provider throttling, bounce processing, unsubscribe handling and delivery reporting at volumes an ordinary mail server cannot sustain.
Plans scale from small monthly volumes up to roughly 2.5 crore emails per month, with more available on request. Throughput depends on your plan and IP allocation rather than an arbitrary daily cap, and high-volume accounts get additional dedicated IPs with automated warm-up for each.
Bulk is one message to many recipients, usually promotional and scheduled. Transactional is triggered by an individual's action — OTP, receipt, password reset — and expected within seconds. Use separate sending domains and IP pools, because marketing complaints damage the reputation delivering your OTPs.
No. Pricing is based on volume sent, not contacts stored. You can keep a large list and mail only the engaged portion without paying for contacts you aren't emailing — which is also the correct deliverability practice.
Above roughly 5,000 messages a day to Gmail addresses: authenticate with SPF, DKIM and DMARC; provide one-click unsubscribe headers per RFC 8058 honoured within two days; keep spam complaints under 0.3 percent, treating 0.1 percent as the warning zone. Yahoo applies comparable rules.
Above modest volumes, yes. On a shared IP your deliverability reflects everyone else sending from it. A dedicated IP means providers evaluate your sending alone, which makes reputation predictable and diagnosable. Below a few thousand emails a month a shared pool is usually fine.
New IPs need two to four weeks of warm-up. You can send from day one; the ceiling rises as providers observe consistent, well-received sending. Attempting full volume from a cold IP produces throttling that takes longer to recover from than the warm-up would have taken.
Yes, with a caveat. Lists with documented consent import cleanly. Purchased lists and lists of unknown origin should not be imported — they carry spam traps and generate complaints that damage your reputation, and under the DPDP Act they lack the consent record you're expected to hold. Re-permission anything uncertain first.
Yes. Subscriber lists, campaign content and delivery logs are stored and processed on AWS Mumbai (ap-south-1). Where data must stay inside your own network, the platform can be deployed on-premise in your data centre.