Three mechanisms, three different jobs
SPF publishes which servers and IPs may send for the envelope domain. DKIM signs selected headers and the body with a private key; receivers verify it through the public DNS key. DMARC requires the visible From domain to align with SPF or DKIM and provides policy and reporting for failures.
Therefore, “SPF pass” alone does not protect the visible sender. DMARC passes when at least one aligned SPF or aligned DKIM result passes. Forwarding can break SPF, which makes DKIM especially valuable; systems that modify messages can also break DKIM.
Publish Corporate Email records
| Host | Type | Exact value/action |
|---|---|---|
| CNAME | securemail.eurovdc.eu | |
| @ | MX | securemail.eurovdc.eu, priority 10 |
| @ | TXT | v=spf1 mx ip4:45.84.90.12 -all |
| dkim._domainkey | TXT | Your complete wizard-specific DKIM text |
| _dmarc | TXT | Commonly v=DMARC1; p=reject; adkim=r; aspf=r; pct=100 |
The single-SPF-record rule
Publishing two separate v=spf1 records at the domain root causes SPF PermError. When adding a CRM, newsletter, or transactional service, do not create a second record; merge all legitimate mechanisms into one while respecting DNS lookup limits. The base EuroVDC value is v=spf1 mx ip4:45.84.90.12 -all. Verify a provider's documented mechanism and actual need before adding it.
Copy DKIM from the wizard
- Open client area → product → Connection Settings + DNS wizard.
- Enter dkim._domainkey as Host/Name. If the DNS panel appends the domain automatically, do not repeat the FQDN.
- Copy the TXT value completely. A panel may visually split long text; do not alter characters, spaces, or quotation handling.
- Save, wait for cache expiry, then verify through the wizard and an independent DNS query.
DMARC: none, quarantine, reject
- p=none: Suitable for observation/reporting and does not request blocking.
- p=quarantine: Requests spam/quarantine treatment for failures and can be an intermediate step.
- p=reject: Requests rejection and provides the strongest enforcement.
The EuroVDC Corporate Email default/common value is v=DMARC1; p=reject; adkim=r; aspf=r; pct=100. However, do not enforce reject until every sender using your domain—website, CRM, billing, help desk, and newsletters—has been verified. For a new or complex domain, observe with p=none, progress to quarantine, and finally reject.
Test DNS
Use dig, nslookup, or reputable online DNS checkers for TXT/MX/CNAME. Expect one SPF at the root, a public DKIM key at dkim._domainkey, and one policy at _dmarc. Never provide a checker with mailbox passwords or sensitive message content. Read SPF, DKIM, and DMARC results together in a test message's headers.
Delivery hygiene
Authentication does not replace good content and permission-based lists. Never buy addresses; use explicit consent, easy unsubscribe, invalid-address removal, and stable volume. Sudden spikes, high complaints, invalid recipients, misleading subjects, and shortened links damage reputation.
For reputation incidents, continue to blacklist removal.
EuroVDC product note and shared technical reference
First confirm which product hosts the mailbox. Corporate Email (Mailcow) uses securemail.eurovdc.eu for incoming and outgoing mail. Hosting email (DirectAdmin) uses mail.yourdomain.com or the server hostname supplied in the service activation details. Using one product's hostname for the other can cause connection or certificate-name errors even when the password is correct.
| Protocol | Secure port | Encryption | Purpose |
|---|---|---|---|
| IMAP | 993 | SSL/TLS | Recommended; synchronizes folders between devices |
| SMTP | 587 | STARTTLS | Recommended outgoing connection |
| SMTP | 465 | SSL/TLS | Alternative outgoing connection |
| POP3 | 995 | SSL/TLS | Only for specific download requirements |
The username is always the full email address. SMTP authentication is mandatory; use the same full username and mailbox password as incoming mail. Do not select Microsoft 365 or Outlook.com, and do not use Microsoft-hosted server names. Corporate webmail is https://mail.YOURDOMAIN.com/user; replace YOURDOMAIN.com with your domain.
Client area and DirectAdmin path
- Sign in to the EuroVDC client area.
- Open the relevant product, then view Connection Settings and the DNS wizard.
- Record the server name, account-specific DKIM text, and displayed DNS status.
- For Hosting email, sign in at https://SERVER:2222 or https://DOMAIN:2222. Open Email Accounts, create or locate the mailbox, then use “+” → Configure Email Client on its row to obtain the exact hostname and ports.
Corporate Email DNS summary
| Name | Type | Target/value |
|---|---|---|
| CNAME | securemail.eurovdc.eu | |
| @ | MX | securemail.eurovdc.eu, priority 10 |
| @ | TXT | v=spf1 mx ip4:45.84.90.12 -all |
| dkim._domainkey | TXT | Account-specific DKIM value from the DNS wizard |
| _dmarc | TXT | Commonly v=DMARC1; p=reject; adkim=r; aspf=r; pct=100 |
| autodiscover and autoconfig | CNAME | securemail.eurovdc.eu |
Autodiscover and autoconfig help compatible applications propose server settings; they do not remove password security or SMTP authentication. Always compare discovered values with the product screen. DNS changes may appear differently across networks until cached records expire.
Quick checklist
- Corporate Email and Hosting email have been distinguished.
- The full email address is entered as the username.
- 993/SSL-TLS and either 587/STARTTLS or 465/SSL-TLS are paired correctly.
- SMTP authentication is enabled and its password is not blank.
- Webmail, receiving, and sending have been tested separately.
- DNS matches the wizard, and the exact error and test time are recorded.
For a visual reference, download the Email Setup Card from PDF help files. If the issue remains, send the mailbox address, device/application version, complete error, and screenshot to support@eurovdc.eu. EuroVDC services operate from Sofia, EU; never include your password in a support request.