Tips to keep e-mails out of SPAM folder
E-mail can be sent from within i-Reserve and many of our customers have i-Reserve running on their own website with their own domain name. It is possible for i-Reserve to send e-mails on behalf of the customer’s domain name.
However, before this is possible, (technical) permission must be given by the domain holder. Otherwise e-mails sent from i-Reserve on behalf of the customer’s domain will end up in the spam box, or even worse: not arrive at all.
To grant i-Reserve permission to send e-mails from the owner’s domain, a so-called Sender Policy Framework (SPF) must be added to the domain settings (DNS-records) of the customer’s domain. This is the responsibility of the owner of the domain.
SPF is a protocol that aims to help reduce spam by determining whether the sender of a mail message is indeed entitled to send a message. For the fine tuning of SPF-records, you should enquire further with the party who issued the domain or the party that maintains the website (hosting).
You can find more information about SPF-records at:
More information about internet domains can be found at:
To validate SPF-records we recommend you go to:
To be able to send mail, the text "include:_spf.i-reserve.nl", "include:_spf.i-reserve.net" or "include:_spf.i-reserve.com" should be added. This depends on the server (.net .nl .com) on which your i-Reserve subdomain was created.
Example. If you are curently using a SPF TXT record that looks like this:
v=spf1 a:mail.mijnbedrijf.nl ~all
Then you should expand it as follows:
v=spf1 include:_spf.i-reserve.com a:mail.mijnbedrijf.nl ~all
Extended security is advised!
Next to SPF settings it is recomended to setup DKIM and DMARC; Of course we can support U or your web builder with these settings.
With DKIM the transmitting server (i-Reserve) can with the use of a ‘private key’ add a cryptographic signature to the outgoing e-mails a so called DKIM-header. A sort certificate of authenticity.
In the DNS you need to setup the ‘public key’ wich is used by the recieving mail host to check the certificate.
secure._domainkey.example.nl. IN TXT "v=DKIM1; p=yourPublicKey"
After creating the key pairs, the private key can be configured in Setup Outgoing e-mail.
With a DMARC-record, you can communicate what you want to to do based on surtain rules. For example (simplified): “if the DKIM-signature, or if SPF fails, put this mail in the spamfolder”.
Such a record could look like thisin the DNS:
_dmarc.example.nl. IN TXT "v=DMARC1; p=quarantine"
More information on DKIM and DMARC
Sender ID (SPF 2)
In some cases is is neceseray to setup a Sender ID record (or SPF2 record).
Sender ID is independen of the i-Reserve version just like SPF is.