Are you still emailing from a free ISP address?
If your business emails come from [email protected] or an ISP address like @telenet.be, switch to [email protected]. A domain-based address carries your brand on every message and gives you control: with a domain you control, you decide which services send your mail and how it's authenticated — with a provider's domain, the provider decides.
Why the free address costs you
- Credibility. A free-webmail address on a business card or invoice can look less established to some customers; a domain address gives your communications consistent branding.
- Control over authentication. Mail sent normally through Gmail or an ISP is authenticated — by the provider, for the provider's domain. What you can't do is set the policy for
gmail.com, or authorize your invoicing tool, website or newsletter service to send aligned mail from it: an unrelated service using a free-provider From address without provider-authorized authentication is likely to fail DMARC and be filtered. Your own domain removes that ceiling — you authorize every legitimate sender yourself. Authentication helps receivers verify your domain and reduces rejection and spam placement; it doesn't guarantee the inbox. - Brand reinforcement. Every email quietly advertises your domain.
- Continuity. Change mail providers and you usually keep the same address — as long as you retain and renew the domain and update its mail settings. The address is portable because the domain is yours to point; it isn't automatic, and it lapses with the domain.
Takeaway: Send from your own domain, not a free ISP account — it carries your brand, you control who may send and how it's authenticated, and it stays portable for as long as you keep the domain alive.
What to do
- Register your domain (if you haven't) and set up mailboxes or aliases on it —
info@,sales@, plus personal addresses. - Configure your mail client with the provider's encrypted settings — IMAP
993(implicit TLS) for receiving and SMTP465(implicit TLS) or587(STARTTLS) with authentication for sending. That encrypts the client-to-server hop, not the message end to end. - Authenticate the domain. Inventory every legitimate sender first — mailbox provider, website forms, invoicing, newsletter tool — then publish one SPF record covering them, enable DKIM per service, and add DMARC, monitoring reports before enforcing (the full setup).
- Use IMAP, not POP, if you read mail on more than one device — mailboxes and message state stay synced on the server.
- Keep a consistent signature with your name, role, domain email, and phone number, so recipients can recognize and contact your business.
- Don't send bulk marketing from your main mailbox. Use an ESP with a dedicated domain or subdomain you control and authenticate — separating marketing from mailbox traffic reduces reputation spillover, though it doesn't excuse bad lists. And bulk mail has legal duties of its own: recipients you're permitted to contact, a clearly identified sender, and a working unsubscribe.
Frequently asked questions
- Should I use IMAP or POP3?
- Use IMAP if you read mail on more than one device — it synchronizes server-side mailboxes and read/unread state across phone, laptop and webmail. POP downloads messages and can be configured to remove the server copies; either way it doesn't provide full mailbox synchronization.
- Which email ports should I use?
- Use your provider's encrypted client settings — typically IMAP 993 with implicit TLS for receiving, and SMTP 465 (implicit TLS) or 587 (required STARTTLS) with authentication for sending. Port 25 is primarily for server-to-server relay and normally shouldn't be configured in an end-user mail client. Note these settings encrypt the client-to-server connection; they are not end-to-end message encryption.
- Can I authenticate mail sent from a gmail.com address?
- Mail sent normally through Gmail is authenticated by Google for gmail.com. What you can't do is publish or change SPF, DKIM or DMARC for gmail.com — or authorize an unrelated service to send aligned mail from that domain. A domain you control lets you choose and authenticate your own sending services, which is a key reason to send from your own domain.
Was this helpful?
Questions about your own site? Get in touch — we read every message.
Source: “Are you still emailing from a free ISP address?” — https://www.siteadvice.be/tips/use-a-domain-email-address/ · © 2026 EUREGIO.NET AG. All rights reserved.