Who Reads sales@ Now? The Shared Inbox Audit Your SME Hasn’t Done
Most small businesses have an email address that nobody can quite explain. It might be sales@, info@ or accounts@. It still works. Clients still use it. The odd invoice still lands there. But ask who owns it and the room goes quiet.
That silence is the problem. An email alias is not just a forwarding rule. It is a public doorway with your company name on it. If the person behind it left two years ago, or the mailbox is shared by six people with no clear owner, you have a quiet security gap dressed up as normal business admin.
The alias is not the same as the mailbox
A lot of the confusion starts here. An alias is usually just another address that delivers into a real mailbox. So sales@ might land in Priya’s inbox. info@ might go to a shared mailbox called Enquiries. accounts@ might forward to the outsourced bookkeeper. None of these are necessarily bad. The risk is when nobody can draw that map from memory.
This matters because password resets, supplier invoices, client queries and contract attachments all follow the same path. If the destination is a mailbox with loose permissions, stale forwarding, or an ex-employee’s login still attached, the alias becomes a way in rather than a front door.
Start with a list, not a panic
You do not need a security consultant to begin. You need a list of every public-facing address your organisation uses or has ever used. Check your website, email signatures, invoices, old brochures, social profiles, directory listings and the “contact us” page you forgot was still live.
Include the obvious ones: sales@, info@, enquiries@, accounts@, admin@, support@, hello@. Then add the less obvious: orders@, bookings@, reception@, jobs@, privacy@ and any address tied to a former trading name. If you use Microsoft 365 or Google Workspace, your admin centre will show aliases and shared mailboxes. Ask your IT provider for a current export rather than relying on memory.
Trace where each address actually lands
For each alias, answer three questions in writing. First, which mailbox receives it? Second, who can read that mailbox? Third, who can send as or on behalf of it?
That second question is where SMEs get caught out. A shared mailbox might have five members, but only two people still work there. One might be a contractor who needed access for a fortnight in 2023 and never lost it. Another might be a director who dips in occasionally but never checks the spam folder. The alias is live, but ownership is fuzzy.
Also check forwarding rules. A mailbox that quietly forwards to a personal Gmail address is not a shared inbox. It is a data leak with good manners. Look for external forwarding, auto-replies that reveal internal names, and rules that send copies to addresses you do not recognise. The same applies to calendar invitations and file-sharing links that arrive at these addresses.
Check the permissions before you check the inbox
Once you know where the mail goes, look at access. Shared mailboxes should have a named owner and a short list of members. Former staff should be removed. Contractors should have time-limited access. Passwords should not be shared in a WhatsApp group, and multi-factor authentication should apply to the account that controls the mailbox.
It is also worth checking whether the mailbox can be accessed from outside your normal systems. If someone can log in from a personal device with only a password, that is a weak point. If an old device still has the mailbox synced, removing the account from the user list is not enough. You need to revoke sessions and wipe the device if it is still in circulation.
Retire what you do not need, control what you keep
Not every alias deserves to survive. If sales@ has not received a genuine enquiry in eighteen months, retire it carefully. Put a short auto-reply in place for a month or two, telling senders the new address. Update the website and any directory listings. Then remove the alias. Do not simply let it forward into a mailbox nobody checks.
If you keep an address, give it a job. Info@ should have an owner and a response time. Accounts@ should be limited to finance staff. Enquiries@ should be a shared mailbox with named members and a rule for who triages what. Public addresses should not be personal inboxes in disguise.
Make this a yearly habit, not a one-off
Aliases accumulate quietly. People create them for campaigns, events, old product lines and temporary projects. Then the project ends and the address lives on. A simple yearly review, perhaps alongside your password and joiners-leavers checks, keeps the list honest.
The test is simple: if a client emailed sales@ this afternoon, could you name the person who would read it, the person who owns the mailbox, and the person who could remove access? If any of those answers is “I think so”, it is worth an hour of someone’s time. Old email addresses are cheap to keep and expensive to ignore.