On Courvix Mail, we support custom third party domains that are owned and operated by regular users. These domains are not maintained by us and we do not need to have any access or control over the domain. In order to better protect our users and their privacy, the page to sign up with custom domains differs from the page where users are able to register accounts on domains that are not owned by us.
This page can be found at: https://courvix.com/email/custom
As it currently stands, we must add custom domains manually. However, work is underway to support this automatically through a form on our website and when it's ready we will no longer need to add them manually.
To add a custom domain, you may join our Discord and make a request or you may send an email to [email protected]. Please note that you must own the domain and be able to manage its DNS records
Once a domain is added, you must add a DNS record to be able to receive email. If you wish to send email, you may also want to add some additional DNS records to help mitigate the chances of your email going to spam.
To receive email, you'll need to add an MX record with the value box.courvix.com
. It may ask for a priority setting, you may use any. However, the priority setting will make email servers use the lowest number (highest priority) email server first. If you'd like our server to be attempted first, you may simply set the priority to 0
.
In order to improve email delivery, you may want to add an SPF record. This is not required, however there is significant possibility of your email ending up in spam if not used.
You'll need to add a TXT record to your domain with the value v=spf1 a mx ip4:51.68.196.145 ip4:198.244.206.160 ~all
This record tells servers that are receiving your email what servers/IP addresses are authorized to send mail from your domain. In this case, these are the Courvix Mail servers.
In order to improve email delivery, you may want to add a DMARC record. This is not required, however there is significant possibility of your email ending up in spam if not used.
You'll need a TXT record to the _dmarc
sub domain of your email domain, for example: _dmarc.courvix.com
This record should have the following content:
v=DMARC1; p=reject; ruf=mailto:[email protected]; fo=1; aspf=s;
This record tells servers receiving your email what to do if the SPF record check fails and therefore should be used in conjunction with the SPF record. In this example, the DMARC policy is to tell email servers to reject email (which usually means to place in spam). As DMARC will fail typically if there is a lack of an SPF record or if it's incorrect, it would usually mean that email spoofing is taking place. The above DMARC policy will also email us if this is happening, although you may remove it if you desire.
In order to improve email delivery, you may want to add a DKIM record. This is not required, however there is possibility of your email ending up in spam if not used.
You'll need a TXT record to the mail._domainkey
sub domain of your email domain. For example: mail._domainkey.courvix.com
This record should have the following content:
v=DKIM1; k=rsa; s=email; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAxngWboPVU71UZuVCA2nPtqeVXxieFM5L8tkwMWl2UUEB9K3AJM2Vj5nkvZpVaFTWsloEdphxtl+ILp4ba+5LFKBQ69lg6nFxXCilhxYkNUQuRMLMmrAWZotzo4YNw6Z1hSfKrlUl+5EqNr+8ADMpqTuC1Bw45SD4H/yiouytvZox97JcW30kFJ3qhqwbJxNm87z0ry0y8ykOQ//3BLdblqIBCpY1Pbqay4s0iRIjNwEfk2XPhSBBNNNz27iILhE0zYkvRLnmzdaBiTmPANJKYniL+rFpU8l3+co60IocYGCc5PnCOuKfxKzG5DyDbU6b7a++fCm5R0Sts6ENbasaswIDAQAB
This record is a way for receiving email servers to verify the identity of our server and acts as a public signature that can be verified by the receiving email server with our email server. As the encryption portion of DKIM is handled by our server, DKIM records are universally the same across domains on our service and do not need to be changed on a per domain basis.