Introduction
When we launch or maintain your website, we create a unique email alias—yourcompany@37solutions.com—that collects automated alerts and log files from your site. This alias keeps system traffic away from personal inboxes, lets us fine-tune deliverability settings, and gives us a quick “kill switch” if you migrate elsewhere or a plugin goes rogue. You still get every alert in your own inbox, but our team can manage, monitor, or disable the alias without asking you to dig through settings.
TL;DR
We give each site its own disposable alias at 37SOLUTIONS: it funnels system alerts to us, copies you, and can be shut off instantly if needed. Never send mail to that address; rely on the copy you already receive.
Why we create aliases
| Concern | How the custom alias helps |
|---|---|
| Runaway mail after a host change | If you move the site and forget to remove our address from cron jobs, plugins, or log handlers, the site will still fire emails. Because each client’s alias is unique, we can shut off the alias in seconds, stopping the noise with no action required on your end. |
| Staff inbox overload | Re-using real employee mailboxes (firstname.lastname@37solutions, system@37solutions) invites spam and phishing if a plugin leaks the address. Dedicated aliases are disposable and isolated, a best practice for managing automated traffic. |
| Compliance & privacy | Personal mailboxes fall outside documented retention and legal-hold rules. Role-based aliases keep automated traffic out of personal folders, reducing audit risk. |
| Deliverability | Aliases can be DNS-tuned (SPF/DKIM/DMARC) without touching staff mail records, improving the odds that genuine alerts reach us and copies reach you. |
How the alias works
Format – yourdomainname@37solutions.com.
Scope – Used only by your site for status messages, backups, uptime alerts, and log exports.
Copies to you – Your address is always on the CC/BCC line; you already see every message the alias sees.
Lifecycle – Active while we manage the site. Disabled when you cancel service or stop sending legitimate traffic. Deleted if it becomes a spam target or we cannot reach you.
Client do’s and don’ts
| ✔ Do | ✘ Don’t |
|---|---|
| Rely on your own inbox copy for testing. | Send “just checking” or “test” emails to the alias. |
| Remove the alias from plugins before you leave 37SOLUTIONS. | Forward sales or support questions to it. |
| Tell new vendors your site already forwards alerts to you; no extra setup needed. | White-list the alias in your help-desk or CRM; it is not a support channel. |
FAQ
Q. What happens if the alias starts bouncing?
A. Your site will still copy you, so no alerts are lost. We close the alias only after a site migration or after repeated spam bursts.
Q. Can we whitelist the alias for monitoring tools?
A. No. Use your own address or a list you control. The alias exists only for internal maintenance mail.
Q. We have multiple sites—do we get multiple aliases?
A. Yes. Each site gets its own alias for the same reasons above: containment and quick shut-off.
Keep this alias out of your address books and ticket systems. If you need to test or review logs, use the messages already reaching your own inbox; that copy is identical to ours.
Comments
0 comments
Please sign in to leave a comment.