Your contact form emails started landing in spam. Support says the server IP is fine. Gmail's headers say something about "low reputation of the sending IP." You are on shared hosting, sending through PHP mail() or the host's SMTP, and you did not know you were sharing a mailbox neighborhood with everyone else on the node.
Shared IP reputation is the silent variable in outbound mail from web hosting. It is not about your domain alone. It is about who else has sent mail from that IP before you.
What shared IP means for mail
On shared hosting, many accounts can send outbound mail through the same server IP (or a small pool). Receiving providers (Google, Microsoft, Yahoo) score that IP based on history: spam complaints, bounce rates, malware bursts, open relays in the past.
Your legitimate quote request can get filtered because yesterday someone on the same host sent a phishing blast from a compromised WordPress form.
How outbound mail leaves a typical host
- PHP mail() / sendmail: web app sends directly from the server IP (worst deliverability story for marketing-sensitive mail)
- Host SMTP: authenticated SMTP still often exits from shared pools unless you pay for dedicated sending
- Plugin SMTP (SendGrid, Mailgun, Google): mail leaves via the provider's infrastructure, not your web server IP (usually better)
- Workspace mail (Google/Microsoft): MX and outbound are entirely off the web host
We compared dedicated vs shared sending in shared IP vs dedicated IP for email deliverability. The web server IP and the mail sending IP are not always the same thing. Check headers on a real message.
Symptoms of IP reputation problems
- Mail to Gmail/Microsoft spam with "via yourhost.com" or IP listed on blocklists
- Sudden spam foldering after months of fine delivery, no content change
- Host support mentions outbound mail throttling or disabled mail() on the account
- Blacklists (Spamhaus, etc.) listing the server IP (search carefully; confirm it is yours)
Authentication still matters: SPF, DKIM, DMARC. Bad IP plus bad DNS is double trouble. See SPF, DKIM, and DMARC after hosting change.
What you can do on shared hosting
- Stop using raw PHP mail() for customer-facing mail. Use SMTP through a reputable relay or workspace.
- Fix forms so bots cannot spray thousands of messages (CAPTCHA, rate limits).
- Keep WordPress patched so compromised sites on your account are not sending spam (your problem if it is your site; host problem if neighbor).
- Ask the host if they offer dedicated outbound IP or transactional mail add-on for business accounts.
- Separate marketing mail (newsletters) from transactional (orders, passwords) via proper ESP tools.
When to move mail off the web server entirely
If email is core revenue (quotes, invoices, booking confirmations), treat the web host as a website machine, not an MTA. Google Workspace, Microsoft 365, or transactional APIs exist because shared web IPs were never designed to be Gmail's best friend.
When to separate email from web hosting walks through the split.
Canadian hosting context
Canadian data centres do not magically improve IP reputation. They help with latency and residency conversations. Reputation is built by sending behavior, authentication, and list hygiene. A Montreal IP can be blacklisted same as anywhere if abuse happens.
If clients ask "is mail in Canada," clarify whether outbound transactional mail uses the host IP, a relay, or Microsoft/Google in another region.
What hosts should do (and you should ask)
- Monitor outbound mail volume per account
- Throttle or suspend compromised accounts quickly
- Offer clear path to SMTP auth and optional dedicated sending
- Publish guidance against mail() for production apps
Bottom line
Shared IP reputation affects outbound mail from hosting whether you think about it or not. Route important mail through authenticated SMTP or workspace providers, lock down forms, and escalate to your host when headers point at a tarnished server IP. Your domain's SPF record cannot fix a neighbor's spam problem alone.
Deliverability headaches on Canadian hosting? Talk with Swift Host. We will trace whether the issue is IP, DNS, or the plugin still calling mail().
