Can You Send a Newsletter From Your Hosting Email? Why Bulk Mail From a Mailbox Gets Blocked

You have a customer list, a promotion or a monthly update to send, and a perfectly good info@ or sales@ mailbox on your hosting plan. Why not write the email, paste in the addresses and press send? Sometimes that works once. Then messages bounce, the host sends a warning, or ordinary one-to-one emails to customers start landing in spam. This guide is for a small-business owner who wants to know whether a hosting mailbox can send a newsletter, why bulk mail from a mailbox gets limited or blocked, and what to use for campaigns instead. It is general advice: every host sets its own mail rules, and this guide does not state what Gotka’s limits or policies are.

What a hosting mailbox is built for

A mailbox on a hosting plan is built for day-to-day correspondence: a person or a small team writing to customers, suppliers and each other, in conversations that go both ways. Mail sent from it leaves through the hosting server, which is shared with other accounts, and the receiving side (Gmail, Outlook, Yahoo and others) judges that mail partly by the reputation of the server it came from and of your domain.

A newsletter is a different job. It is the same message to hundreds or thousands of people within minutes, most of whom will not reply and a few of whom will press “report spam”. To a receiving system that pattern looks a lot like what spammers do, even when your list is genuine and every person asked to be on it.

Where is the line? A handful of personal notes to people who know you is ordinary correspondence. Once you are writing to a list, want an unsubscribe link, want to see who clicked, or plan to repeat the send every month, you are running a campaign. Blind copy (Bcc) hides the other addresses but does not turn a mailbox into a campaign tool, and putting a whole list in the To or Cc field shows everyone’s address to everyone else, which is a privacy slip as well as a deliverability risk.

What shared hosting generally limits

Shared hosting puts many accounts on one server, so hosts protect it by capping outgoing mail. The details differ by provider, but the same few controls appear again and again in hosts’ public help pages:

Because the numbers and rules belong to the provider, the only reliable sources are your host’s written mail or acceptable-use policy and a written answer from support. Do not rely on a figure from a blog post, including this one.

What happens when you hit the limit

The effects range from irritating to expensive, and they do not always stay inside the newsletter:

• Delay. Part of the send waits in a queue and goes out hours later, or not at all. A promotion can arrive after it has ended.
• Bounces. Messages come back with an error. Some errors are temporary and some are permanent, and someone has to read them to know which addresses are dead.
• A temporary block. Sending from the mailbox or domain is paused until the window resets or support lifts it. Your normal one-to-one mail stops too, including quotes and invoices.
• Reputation damage. Complaints, bounces to dead addresses and sudden spikes in volume teach receiving systems to distrust a sending server or domain. On shared hosting other accounts may send from the same server, which is one reason hosts are strict. Ordinary mail from your domain can land in spam for a while.
• Account action. Repeated bulk sending or spam complaints can fall under a host’s acceptable-use rules and, in the worst case, contribute to a suspended account. Our guide to a suspended hosting account lists an acceptable-use or spam complaint among the common causes.

None of this says your list is bad. It says a mailbox and a campaign are different jobs, and the infrastructure behind a mailbox is not designed for the second one.

Why mail can be blocked even when you stay under the cap

A host’s cap is only the first gate. The second is the receiving provider, which decides for itself whether to deliver, junk or reject each message. It looks at things such as whether the message is authenticated as coming from your domain, how many recipients complain, how many addresses bounce, how suddenly your volume changed and whether the content resembles known spam. A new sender that jumps from ten emails a day to a thousand in an afternoon looks suspicious whatever the intentions.

The big mailbox providers have also written their expectations down. Google (from February 2024) and Yahoo have set requirements for bulk senders. As Google describes them, they apply to senders of more than 5,000 messages a day to Gmail addresses and include SPF, DKIM and DMARC for your domain, one-click unsubscribe plus a visible unsubscribe link for marketing mail, and a spam complaint rate kept below 0.30%. Yahoo publishes similar requirements. A small business with a few hundred subscribers is usually far below that volume, but the same expectations are a sensible standard for any list. These rules change, so confirm the current wording on the official pages: Google’s sender guidelines and Yahoo’s sender best practices.

What to use instead: a dedicated email-sending service

The usual answer is a service built for campaign email. It stores your list, adds the unsubscribe link, handles bounces and complaints, and sends from infrastructure whose reputation it manages, while you still write the message and send it as your own business. This guide does not name or recommend any product. Compare services on the points below and test one with a small list before committing.

Sending from your own domain: the authentication step

Whichever service you choose, you will normally send from an address on your own domain, such as news@yourdomain, so the newsletter looks like it comes from your business. To allow that, the service gives you DNS records to add, usually a pair for SPF and DKIM and sometimes a tracking sub-domain. What those records do is explained in our guide to business email on your own domain; where they live is explained in DNS explained. Three cautions apply when you add them:

• Keep one SPF record. A domain should publish a single SPF record. If your hosting mail already has one, the new service’s entry is merged into it, not added as a second record, which can make SPF fail. Ask your host which value must stay.
• Copy before you change. Take a screenshot or export of the DNS records first, change one thing at a time and send a test. Never delete the records that route incoming mail (MX records) unless you are certain.
• Separate the jobs. Send the campaign from news@ and keep info@ for conversations. Set the reply address to a mailbox a person reads, so replies come back to you and not to an unwatched sender address.

If you are not sure who manages your DNS, our guide to who hosts your website shows how to find out before you change anything.

Keeping the list clean

Even the best sending service cannot fix a poor list. These habits protect your reputation and your customers’ goodwill:

• Send to people who asked. Use a sign-up form, a tick box that is not pre-ticked or a clear request in person, and keep a note of when and how each person joined.
• Say what to expect. Tell people what they will receive and roughly how often, then do that.
• Make leaving easy. A visible unsubscribe link in every email, honoured quickly. Hiding it only turns unsubscribes into spam complaints.
• Do not buy or scrape lists. People who never heard of you complain, and many addresses on bought lists are dead or are traps set to catch senders.
• Remove dead addresses. Take out addresses that bounce for good, and consider pausing people who have not opened anything for a long time.

Malaysia’s Personal Data Protection Act 2010 (as amended) has rules on using personal data for direct marketing, including a person’s right to ask you to stop. This guide is not legal advice, so confirm what applies to your business with the official source (pdp.gov.my) or a lawyer.

A worked example: splitting one month’s email

Illustration only: the business and every number below are made up. Imagine a small bakery with a monthly update and 1,500 people who signed up for it. Here is how its email could be split between the hosting mailbox and a sending service:

The newsletter leaves the mailbox entirely, while replies still arrive in a mailbox a person reads. Customers see one business, the host’s allowance is kept for everyday mail, and the campaign has the tools a campaign needs. If form notifications ever go missing, our guide to contact form enquiries not reaching your inbox covers the checks.

Questions to ask your host before the first campaign

Send these through your host’s ticket system so the answers are in writing, and keep them:

1. Are newsletters or bulk marketing emails allowed from the mailboxes on my account?
2. What is the limit per hour and per day, per mailbox and per domain, and do recipients, Bcc, webmail and website forms all count towards it?
3. What happens when the limit is reached: is mail queued, bounced or paused, and for how long?
4. Can I see a log of outgoing mail if something goes missing?
5. Which SPF record or value must I keep if I add a sending service to my domain?
6. Who should I contact if my domain’s mail is being blocked by a receiving provider?

If the answer to the first question is no, you have your answer. If it is yes with limits, plan the send inside them or, better, move campaigns to a sending service anyway.

Common mistakes

• Pasting a whole list into Bcc. It hides the addresses but usually still counts every recipient, and it has no unsubscribe, no bounce handling and no record.
• Testing the limit by sending. You find the limit by hitting it, along with a block on everyday mail.
• Adding a second SPF record. Two records can make authentication fail. Merge the entries into one.
• Sending a big first campaign from a new setup. Start with a small group of engaged people and grow the volume gradually.
• Using a bought or old list. Complaints and bounces follow, and they follow your domain.
• Hiding the unsubscribe link. People who cannot leave will report you instead.
• Sending from an address nobody reads. Replies are often the most useful feedback you get.
• Assuming the host’s policy from a blog post. Ask support and keep the answer in writing.

Where Gotka Technologies fits

Gotka runs cPanel hosting, and email accounts come with the plans: Go AI Lite includes 30 email accounts and Go AI Plus includes unlimited email. How many email accounts does your team really need? helps you plan them, and our guides to setting email up on your phone and laptop and to a full mailbox cover everyday use. Gotka also offers domain registration from RM10/yr.

This guide does not state Gotka’s sending limits, rate limits or spam-filtering behaviour, or whether Gotka offers bulk-mail or newsletter tools, because none of that is published in the material it can cite. Ask support about your own account through the client-area ticket system, or call or WhatsApp +60 11-6331 6630, Monday to Friday, 9am to 6pm (MYT), and use the question list above.

Key terms used in this guide

• Hosting mailbox: an email account on a hosting plan, meant for everyday correspondence.
• Bulk or campaign email: the same message sent to many recipients at once, such as a newsletter or promotion.
• Sending limit: a cap on how many messages or recipients a mailbox, domain or account may send in a period; set by the provider.
• Email-sending service: a service built to send campaign email, with list, unsubscribe, bounce and complaint handling.
• SPF: a DNS record listing which servers may send mail for your domain.
• DKIM: a digital signature added to outgoing mail that receivers check against a record on your domain.
• DMARC: a DNS record telling receivers what to do with mail that fails SPF and DKIM checks and where to send reports.
• Bounce: a message returned undelivered, either temporarily or for good.
• Spam complaint: a recipient marking a message as spam, which counts against the sender’s reputation.
• Sender reputation: a receiving provider’s running judgement of how trustworthy a server or domain is as a mail source.
• One-click unsubscribe: an unsubscribe built into the email program so a recipient can leave with a single action.