A @gmail or @yahoo address on a professional invoice quietly costs business. But an address at your own domain, badly configured, costs more still: messages land in spam, clients do not reply, and nobody understands why.
The difference comes down to three DNS records — SPF, DKIM, DMARC — that almost nobody configures and that every major provider now checks. We create your addresses, configure them on all your devices, and put in place what makes a message unambiguously yours.
The problems this actually solves
Five email problems we see most often, and their real cause.
Your messages arrive in the spam folder
In the vast majority of cases it is not the content: it is the absence of SPF, DKIM and DMARC. Without them the recipient's provider has no way to verify that the message really came from your domain. We publish them and verify the result with a real test.
Someone is sending invoices in your name
Without DMARC, spoofing your sender address is trivial. Your clients receive false bank details under your name. DMARC lets you ask providers to reject those messages.
Mail is set up as POP, and messages vanish from the other devices
POP downloads messages and removes them from the server. The phone empties the mailbox and the computer sees nothing. We switch to IMAP, where every device sees the same mailbox.
One address for the whole company
Everything goes through contact@, nobody knows who is handling what, and a departure takes the history with it. We create named addresses and shared mailboxes for collective functions.
The mailbox is full and refuses new messages
The quota was reached weeks ago and senders get an automatic rejection. We archive, resize, and set an alert before saturation.
What we build
Three areas: create the addresses, make them arrive, protect them.
Addresses and hosting
- Professional addresses at your own domain name
- Hosting on OVH, Microsoft 365 or Exchange, to suit usage and budget
- Named mailboxes, shared mailboxes, aliases and distribution lists
- Quota resizing and archiving of older messages
- Domain name registration or transfer where needed
- Consistent signatures across the whole company
Configuration and migration
- IMAP, POP and SMTP settings as appropriate
- Outlook, smartphone and mail client configuration
- Migration of existing mailboxes with the history preserved
- Transfer of folders, contacts, calendars and rules
- Configuration of printers and applications that send mail
- MX switchover with no interruption to incoming mail
Deliverability and security
- SPF records published and verified
- DKIM signing put in place
- DMARC policy, first in monitoring mode then in reject
- Real deliverability test against the main providers
- Multi-factor authentication on the accounts
- Detection of forwarding rules created by an intruder
How a project runs
Four stages, and no interruption to incoming mail at any point.
SPF, DKIM, DMARC — and the rest
These three records are not a technical nicety: they decide whether your mail is read, and whether anyone can impersonate you.
- SPF: lists the servers allowed to send on behalf of your domain
- DKIM: signs each message to prove it was not altered
- DMARC: tells providers what to do with messages failing both checks
- DMARC moved to reject in stages, after a monitoring period
- Multi-factor authentication on every mailbox
- Automatic forwarding rules checked — an intruder’s first move
- Leaver procedure: access blocked, mailbox converted to shared
Moving DMARC to reject too quickly blocks your own legitimate senders — your accountant, your invoicing tool, your website form. That is why we monitor first and only harden once the list is complete.
Who it is for
Any organisation that sends quotes, invoices or proposals by email — which is nearly all of them.
Freelancers and professionals
Moving from a personal address to one carrying the business name.
Small businesses and shops
Named addresses, shared mailboxes for collective functions, consistent signatures.
Organisations that invoice by email
The impersonation risk is direct and measurable: false bank details inside a genuine thread.
Associations
Addresses that outlive the committee, without depending on a personal account.
Real use cases
Five concrete requests.
-
Your request:
“Our quotes land in our clients’ spam”
Ivory Coast Connect
Deliverability test, SPF and DKIM published, DMARC configured, then a fresh test against the main providers.
-
Your request:
“A client received a fake invoice in our name”
Ivory Coast Connect
Compromise check, DMARC moved to reject, and a procedure for validating changes of bank details.
-
Your request:
“My mail disappears from my computer when I read it on my phone”
Ivory Coast Connect
POP switched to IMAP, all devices reconfigured, whatever is still on the server recovered.
-
Your request:
“We are leaving our current host”
Ivory Coast Connect
Mailboxes migrated with the full history, MX switched without interruption, old mailbox kept while we check.
-
Your request:
“A colleague is leaving, what about her mailbox?”
Ivory Coast Connect
Access blocked, converted to a shared mailbox or redirected, history transferred to her manager.
Why give us this work
Nothing unverifiable: no years in business, no client count, no certification. Only the way we work.
We test deliverability, before and after
The result is verifiable: a message sent to several providers, and the authentication report read line by line.
No interruption to incoming mail
Both environments run side by side during the switch. You do not lose a message.
We harden in stages
DMARC moves to reject when the list of your legitimate senders is complete, not on day one.
Our other services
One point of contact for all of your IT.
Email to create, migrate or repair?
Deliverability test and a reading of your DNS records, then an itemised quote — free of charge.