Sending From a Shared Server

The address you are sending from

When a site or a mailbox on shared hosting sends a message, it leaves from the server's network address.

That address is shared with every other account on the same machine, which can be dozens or hundreds of unrelated businesses.

Receiving systems judge mail partly on the standing of the address it came from.

So the sending behaviour of businesses you have never heard of contributes directly to whether your quotes reach an inbox.

What that means in practice

• Somebody else's bulk sending affects your delivery.
• A compromised account on the server damages everybody.
• You cannot see who your neighbours are.
• You cannot influence what they do.
• Delivery can change with no action on your part.
• Recovery is not yours to perform.

The last is the one that makes this different from other deliverability problems: your own configuration can be perfect and the outcome still poor.

The characteristic symptom

Worth recognising, since it distinguishes this from the problems you can fix yourself.

Delivery is normal for months, then deteriorates suddenly with no change at your end: no new tool, no bulk send, no configuration change.

It affects everything you send rather than mail from one particular system, which distinguishes it from an authentication problem.

And your authentication checks all pass, because nothing is wrong with your setup.

That combination points at the sending address rather than at you, and it is worth checking before spending a day auditing your own records.

How to check

Two things, both quick.

Find the network address your mail is actually sending from, which appears in the technical headers of any message you have sent, visible through a show-original or view-source option in most mail clients.

Then check that address against public blocklists, which takes a minute and tells you whether it is listed.

A listed address that is not yours to fix is the confirmation, and it is worth raising with your host, who can see the account responsible and will usually act.

Hosts vary considerably in how quickly they deal with this, and their response is itself information about the host.

The fix is usually to move email out

Rather than to change host, which trades one shared address for another.

Email and website hosting do not have to live together, and separating them is generally the right arrangement for a small business regardless of this problem.

A dedicated mail provider sends from infrastructure managed specifically for deliverability, with reputation actively maintained and abusive accounts removed quickly.

That removes the dependency on your neighbours entirely and it also makes future website migrations considerably simpler, since email stops being part of them.

The cost is a small monthly figure per mailbox, which for most businesses is less than an hour of the time this problem consumes.

Send bulk mail through a service either way

A separate point that applies regardless of your hosting.

Newsletters and any bulk sending should go through a mailing service rather than from your own server or mailbox.

Those services manage sending reputation as their core business, handle unsubscribes and bounces properly, and warm up sending gradually.

They also keep bulk sending separate from your ordinary correspondence, so a poorly received newsletter does not affect your quotes.

Sending several hundred messages from a shared hosting server is the combination most likely to produce a listing, since it looks exactly like the abuse those systems exist to detect.

A worked example

A business found that their email to two large providers had started going to spam, over about a week, with nothing changed at their end.

Their authentication was correctly configured and passing.

Checking the sending address from a message header showed it listed on two blocklists.

Their host confirmed another account on the same server had been compromised and was sending spam, and it had been dealt with the previous day.

Delivery improved over the following fortnight without them doing anything.

They then moved their mailboxes to a dedicated provider, which took an afternoon, on the reasoning that the next occurrence was a matter of when rather than whether.

Website mail is the other half

The part people forget when they move their mailboxes.

Contact forms, order confirmations, and password resets are sent by the website, which is still on the shared server and still using its address.

So moving your mailboxes fixes your correspondence and leaves every automated message on the shared address.

Configure the site to send through your mail provider or a dedicated sending service, which most platforms support with a plugin or a settings change.

That also fixes the common problem of contact form messages disappearing, since mail sent by a website from a shared server is exactly what filters treat most harshly.

A dedicated address is not automatically better

Worth knowing before anybody sells you one, since it is the obvious-sounding remedy.

A dedicated sending address has no history, and a receiving system that has never seen mail from it has no reason to trust it.

Building that standing requires consistent volume over weeks, which a small business sending a few dozen messages a day will accumulate slowly.

So a dedicated address suits a high-volume sender and can be worse than a well-managed shared one for a low-volume business.

The right answer for most small businesses is a reputable shared arrangement run by a provider whose business depends on keeping it clean, which is what a dedicated mail provider is.

The counter-case

Shared sending is not automatically bad.

Reputable hosts monitor their servers, act on abuse quickly, and maintain addresses in good standing, and plenty of businesses send from shared hosting for years without a problem.

A shared address with a large volume of legitimate mail across it is also more stable than a low-volume dedicated one, which has no established standing at all.

There is also a cost to separating things: another supplier, another bill, and a migration with its own risks.

Move bulk sending off immediately, move website mail off when convenient, and move mailboxes when the problem occurs or when you are migrating anyway.

What to do

1. Find your sending address in a message header.
2. Check it against blocklists.
3. Raise a listing with your host.
4. Send bulk mail through a service, always.
5. Move mailboxes to a dedicated provider.
6. Configure the website to send through it too.
7. Test the contact form after any change.

Step six is the one people miss, since moving mailboxes leaves every automated message from the website on the shared address it was sent from before.

What else you share on that machine is covered in shared hosting and who else is on it.

Frequently asked questions

West Coast Media Solutions Inc. provides web design, web development, hosting, digital marketing, and business consulting to organisations across Canada, drawing on more than twenty-five years in the field.