Create an email address
A professional email address is configured in two steps: create the mailbox in KeyHelp, then publish the DNS records that authorize the server to send and receive for your domain. Without SPF, DKIM and DMARC, your messages risk the spam folder.
1. Create the mailbox
In KeyHelp, open the email section and create an address, for example [email protected]. Provide:
- a long, unique password stored in a password manager;
- a sufficient but not unlimited quota;
- one mailbox per person or role, never a shared account.
Note the IMAP and SMTP servers shown by the panel. These are the only values to use in your client: do not guess a host name.
2. Publish DNS records
| Record | Role | Value |
|---|---|---|
MX |
receives mail | server shown by KeyHelp, displayed priority (often 10) |
SPF |
authorizes sending servers | v=spf1 include:... -all |
DKIM |
signs messages | public key, provided selector |
DMARC |
policy and reports | v=DMARC1; p=none; rua=mailto:... |
Copy the exact values shown in KeyHelp, especially the DKIM selector. Only one SPF record per domain: two TXT records starting with v=spf1 cause a failure. Start DMARC with p=none to observe, then move to quarantine when reports look clean.
3. Configure the mail client
Usual settings:
- IMAP: port
993, SSL/TLS. - SMTP: port
587, STARTTLS. - Username: the full address.
- Password: the mailbox password.
Avoid port 25 for client sending: it is often blocked by access providers. Test receiving first, then sending. If sending fails, check SMTP authentication and port, not just the password.
4. Improve deliverability
- One clearly identified sending domain.
- SPF, DKIM and DMARC aligned with that domain.
- No bulk sending from a shared mailbox without provider approval.
- Content without surprising attachments or suspicious shortened links.
- Stable reputation: do not alternate between several sending servers.
Reverse DNS belongs to the IP address operator; you cannot change it from KeyHelp. If a message is rejected, read the Authentication-Results headers and send them to support instead of resending in a loop.
5. Verify
- Send a message to an external mailbox (Gmail, Outlook) and inspect the headers.
- Confirm
spf=pass,dkim=passanddmarc=pass. - Reply from the external mailbox and check receipt.
- Check quota and aliases.
- Delete test mailboxes and forgotten redirects.
An address that receives but sends to spam is not "broken": it is almost always a DNS authentication problem.
Advertisement